prequ
prequ copied to clipboard
suutari
Tools for Python requirement handling
Latest pip causes this error: > File "/Users/panu/shuup-dev/owl/venv/lib/python3.7/site-packages/prequ/_pip_compat.py", line 35, in > from pip._internal.download import is_file_url, path_to_url, url_to_path > ModuleNotFoundError: No module named 'pip._internal.download'
Currently, if wheel build fails to produce the wheel file (e.g. because of some build error), a very confusing `IndexError` is generated. It should rather generate a proper error message...
When adding an URL entry with `#egg` part to source requirements the resulting generated requirements will contain two eggs. E.g. following `requirements.in` (l: ``` # Following is really just a...
If source requirements contains directory requirements with extras (e.g. `.[extra1,extra2]` or `./some-dir[extra]`), the generated requirements will have the dependencies of the extras, but the extras are not present in the...
Add a package to setup.cfg. Would work like `yarn` in the sense that when `prequ add` is being ran the package is added to setup.cfg/requirements files and be installed. By...
Had a case where a package version was set as `>==` instead of `>=` by accident, and prequ didn't raise any messages about this, nor update the requirement files for...
When installing new packages with `prequ sync` and there is some hashes specified in the generated `requirements.txt`, the hashes should be checked before installing, but that's currently not done. See...
Implement an "-a" or "--all" option to "prequ sync". The option would sync all known `requirements*.txt` files. The lack of this feature can be worked around by doing `prequ sync...
Implement a command for upgrading the requirements to newer versions, either all or just specified package(s).
The sync command should report parse errors of the requirement files rather than just fail with a traceback. E.g. when doing `prequ sync -n *.txt` in a directory where there...