workon-poetry
Bash and Python scripts to make switching and starting projects more efficient and less error-prone by automating some of the boring stuff and incorporating some opinions about best practices.
Dependencies
- poetry
- virtualenv
Setup your Python environment
Launch a terminal on Linux (or git-bash on Windows) then:
- Update your pip and virtualenv packages
- Clone the
workon-poetryproject - Create a virtualenv within the
workon-poetrydir - Activate your new Python virtual environment
- Install this Python package in "--editable" mode
Any Python version greater than 3.7 should work.
As of 2023 most Linux systems use Python 3.9 or higher:
pip install --upgrade virtualenv poetry
git clone git@gitlab.com:tangibleai/community/workon-poetry
cd workon-poetry
python -m virtualenv --python 3.9 .venv
ls -hal
You should see a new .venv/ directory.
It will contain your python interpreter and a few site-packages like pip and distutils.
Now activate your new virtual environment by sourcing .venv/bin/activate (on Linux) or .venv/scripts/activate (on Windows).
# bin/activate on Linux OR `Scripts/activate` in git-bash on Windows
source .venv/bin/activate || source .venv/Scripts/activate
Developer install
Once you have a shiny new virtual environment activated you can install workon-poetry in --editable mode.
This way, when you edit the files and have the package change immediately.
Make sure you are already within your cloned workon-poetry project directory.
And makes sure your virtual environment is activated.
You should see the name of your virtual environment in parentheses within your command line prompt, like (.venv) $.
Then when you install workon-poetry it will be available for import within any other Python application in that virtual environment.
pip install --editable .
User install
If you don't want to contribute, and you just want to USE workon-poetry the MathText modules, you can install it from a binary wheel on PyPi:
pip install workon-poetry
Metadata
Release files for workon-poetry 0.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| workon_poetry-0.0.4.tar.gz | 2.9 kB | Without provenance | Details for workon_poetry-0.0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| workon_poetry-0.0.4-py3-none-any.whl | Python 3 | none | any | Details for workon_poetry-0.0.4-py3-none-any.whl |
Total release size: 6.6 kB
Release files / workon_poetry-0.0.4.tar.gz
| Download URL | workon_poetry-0.0.4.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
73855acb29b3180e3a0f484d72bef663a3b0dddc09771d68a80bda53619e8084
|
|
BLAKE2b-256 checksum How to use checksums |
23fc965fd41f08228f69609767196ceb3c265772f843dd20c993eefb9215e1d2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.4.1 CPython/3.9.16 Linux/5.19.0-35-generic
|
Release files / workon_poetry-0.0.4-py3-none-any.whl
| Download URL | workon_poetry-0.0.4-py3-none-any.whl |
|---|---|
| Size | 3.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8a396c75539d309a76c3dbae12e86b2475847a61aac9abba624ee7de55386974
|
|
BLAKE2b-256 checksum How to use checksums |
94769f68f9d7cc41e52136633427c063e75c1bf3d137c90f258c1d294a93dcd1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.4.1 CPython/3.9.16 Linux/5.19.0-35-generic
|
Security for workon-poetry 0.0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.