Penvy - Pyfony development environment
for the Pyfony framework
What it does:
- Prepares the Conda-based python dev environment in the project's .venv directory
- Installs the Poetry package manager into the user's home dir
- Installs all the dependencies defined in project's poetry.lock file
- Sets conda activation & deactivation scripts (mostly setting environment variables based on the project's .env file)
- Copies the project's .env file from the .env.dist template file
- Adds
poetry install --no-rootto post-merge GIT hook
Metadata
Release files for penvy 1.4.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| penvy-1.4.3-py3-none-any.whl | Python 3 | none | any | Details for penvy-1.4.3-py3-none-any.whl |
Release files / penvy-1.4.3-py3-none-any.whl
| Download URL | penvy-1.4.3-py3-none-any.whl |
|---|---|
| Size | 50.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
53c2192a3f896a35d8a1ba1cfa03a7b0081ee58baee9fffcb1779b01f683852e
|
|
BLAKE2b-256 checksum How to use checksums |
95d9225b2dbf180161a4ae620b29532b67337f1da012766d576c48f4b928b758
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.5.1 CPython/3.8.18 Linux/6.8.0-1021-azure
|
Security for penvy 1.4.3
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.