welbornprod / requirementz Goto Github PK

Just noting quite a few levels beneath this is a Python 3.7 bug
welbornprod/colr#7

Since you are actively maintaining this tool, maybe you are interested in subsuming the use-cases of many other less maintained tools which I have found.

You can find my 'list' at

https://build.opensuse.org/project/show/home:jayvdb:py-new

and filter for 'pip'.

Not all of them are building, often they have no tests, so are probably failing.

Or list only green builds and find 'pip' in the page.

Many seem to have been built without intention that other people might also use them, and often they are bitrotting because of the constant pip breakages.

I have raised issues about some

• https://github.com/defjaf/pip_upgrade_outdated/issues
• https://github.com/bartTC/pip-check/issues
• https://github.com/ambitioninc/pip-conflict-checker/issues
• https://github.com/OpticGenius/download-tarball/issues

(and lots more, but those are a decent sample)

Checking a requirements file with a comment (e.g. #comment) causes the following error:

not enough values to unpack (expected 1, got 0)

Comments should be allowed according to this:
https://pip.pypa.io/en/latest/reference/pip_install/#requirements-file-format

And it looks like the official example files also currently fails
https://pip.pypa.io/en/latest/reference/pip_install/#example-requirements-file

Currently running on an empty file result in the following error: "Requirements file is empty." and and exitcode 1.

According to this: pypa/pip#343 pip now allows for empty requirements files, so would be logical that the same behaivor is adopted here.