requirements

History

Elod Illes 28248c2d01 Workaround for unittests

Probably with the latest virtualenv [1] (which bundles setuptools), the
unit tests started to fail with this error:

  File "/home/zuul/src/opendev.org/openstack/requirements/.tox/py310/lib/python3.10/site-packages/pkg_resources/_vendor/packaging/requirements.py", line 37, in __init__
    raise InvalidRequirement(str(e)) from e
pkg_resources.extern.packaging.requirements.InvalidRequirement: Expected end or semicolon (after version specifier)
    lesscpy>=0.9h

It seems that the parser have become more strict and now it does not
accept other than 0.9a, 0.9b (alpha, beta) releases when parsing
constraints. This patch updates the global requirements test file to
not break the parser.

Also the test_match_without_python3_markers test caused the same error
(with: withmarker>=1.5') and needed an update.

[1] virtualenv (20.19.0) released at Tue, 07 Feb 2023 20:16:53 GMT

Change-Id: Ia2ba3f38a83216abc430ed754bb7d8cbe8c564d3

2023-02-13 17:45:13 +01:00

files

Workaround for unittests

2023-02-13 17:45:13 +01:00

__init__.py

Move tests into openstack_requirements.

2015-06-08 22:07:01 +12:00

common.py

do not sync the blacklist to projects

2017-06-15 16:26:53 -04:00

test_build_lower_constraints.py

Ignore empty requirements/constraints when building lower-constraints