# Wracker
(PRE-ALPHA DO NOT USE) A Python clone of bundler. The wheel racker!
## Commands
wracker install installs packages from a requirements.in file (in your CWD or parent directories) and writes the specific versions to requirements.txt
wracker exec sets $PYTHONPATH to use only the packages in your requirements.txt, nothing more. It also modifies $PATH to point to a ‘clean’ virtualenv, which wracker manages for you. These virtualenvs do not have pip installed so hopefully they never become polluted (although there are no hard locks in place or anything like that).
It also adds entrypoints to your $PATH, so wracker exec pep8 will use a frozen pep8 if available.
## Todo
(Presented in no particular order.)
[ ] Support installation with Python 3
[ ] VCS URLs
[ ] -r includes
[ ] Verification that all versions are compatible (similar to pip-tools)
[ ] Tests
Metadata
Release files for wracker 0.4.1
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 |
|---|---|---|---|---|
| wracker-0.4.1.tar.gz | 35.7 kB | Without provenance | Details for wracker-0.4.1.tar.gz |
Release files / wracker-0.4.1.tar.gz
| Download URL | wracker-0.4.1.tar.gz |
|---|---|
| Size | 35.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e775ba688c9157fdb48643619d5f2e56f6c35d5cb9d045ab1ab9db3d80298fdc
|
|
BLAKE2b-256 checksum How to use checksums |
86ae0d01172d6e5a957713b0e9ffa40c1d1caec253cc9b923b25eb31bf0d5190
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for wracker 0.4.1
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.