However, requirements.parse() fails on line "psycopg2>=2.7.4 --no-binary psycopg2".
Please advise if this is a bug in requirements or if this shouldn't be supported.
If it's a bug, I would be glad to create a PR for this one.
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/pkg_resources/_vendor/packaging/requirements.py", line 90, in __init__
req = REQUIREMENT.parseString(requirement_string)
File "/usr/local/lib/python3.7/site-packages/pkg_resources/_vendor/pyparsing.py", line 1654, in parseString
raise exc
File "/usr/local/lib/python3.7/site-packages/pkg_resources/_vendor/pyparsing.py", line 1644, in parseString
loc, tokens = self._parse( instring, 0 )
File "/usr/local/lib/python3.7/site-packages/pkg_resources/_vendor/pyparsing.py", line 1402, in _parseNoCache
loc,tokens = self.parseImpl( instring, preloc, doActions )
File "/usr/local/lib/python3.7/site-packages/pkg_resources/_vendor/pyparsing.py", line 3417, in parseImpl
loc, exprtokens = e._parse( instring, loc, doActions )
File "/usr/local/lib/python3.7/site-packages/pkg_resources/_vendor/pyparsing.py", line 1406, in _parseNoCache
loc,tokens = self.parseImpl( instring, preloc, doActions )
File "/usr/local/lib/python3.7/site-packages/pkg_resources/_vendor/pyparsing.py", line 3205, in parseImpl
raise ParseException(instring, loc, self.errmsg, self)
pkg_resources._vendor.pyparsing.ParseException: Expected stringEnd (at char 16), (line:1, col:17)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/pkg_resources/__init__.py", line 2963, in __init__
super(Requirement, self).__init__(requirement_string)
File "/usr/local/lib/python3.7/site-packages/pkg_resources/_vendor/packaging/requirements.py", line 94, in __init__
requirement_string[e.loc:e.loc + 8]))
pkg_resources.extern.packaging.requirements.InvalidRequirement: Invalid requirement, parse error at "'--no-bin'"
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File ".dev/bump-requirements.py", line 25, in <module>
asyncio.run(generate_fresh_requirements(args.file))
File ".dev/bump-requirements.py", line 20, in generate_fresh_requirements
for req in requirements.parse(fd):
File "/usr/local/lib/python3.7/site-packages/requirements/parser.py", line 50, in parse
yield Requirement.parse(line)
File "/usr/local/lib/python3.7/site-packages/requirements/requirement.py", line 220, in parse
return cls.parse_line(line)
File "/usr/local/lib/python3.7/site-packages/requirements/requirement.py", line 198, in parse_line
pkg_req = Req.parse(line)
File "/usr/local/lib/python3.7/site-packages/pkg_resources/__init__.py", line 3009, in parse
req, = parse_requirements(s)
File "/usr/local/lib/python3.7/site-packages/pkg_resources/__init__.py", line 2956, in parse_requirements
yield Requirement(line)
File "/usr/local/lib/python3.7/site-packages/pkg_resources/__init__.py", line 2965, in __init__
raise RequirementParseError(str(e))
pkg_resources.RequirementParseError: Invalid requirement, parse error at "'--no-bin'"
It is recommended to use
--no-binary
in psycopg2 docs: http://initd.org/psycopg/docs/install.htmlHowever,
requirements.parse()
fails on line "psycopg2>=2.7.4 --no-binary psycopg2". Please advise if this is a bug inrequirements
or if this shouldn't be supported. If it's a bug, I would be glad to create a PR for this one.