pip 23.1 removed the "setup.py install" fallback for projects that do not have pyproject.toml and now uses a pyproject.toml which is vendored in pip [1][2]. pip 24.2 has now deprecated a similar fallback to "setup.py develop" and plans to fully remove this in pip 25.0 [3][4][5]. pbr supports editable installs since 6.0.0 so we can get ahead of this by adding our own minimal pyproject.toml to ensure we are using the correct build system. [1] https://pip.pypa.io/en/stable/news/#v23-1 [2] https://github.com/pypa/pip/issues/8368 [3] https://pip.pypa.io/en/stable/news/#v24-2 [4] https://github.com/pypa/pip/issues/11457 [5] https://ichard26.github.io/blog/2024/08/whats-new-in-pip-24.2/ Change-Id: I3407c8aa26d4ee96747cbca45e85894f193fc625 Co-Authored-By: Sean Mooney <work@seanmooney.info> Signed-off-by: Ivan Anfimov <lazekteam@gmail.com>
13 lines
361 B
Plaintext
13 lines
361 B
Plaintext
# Hacking already pins down pep8, pyflakes and flake8
|
|
hacking>=7.0.0,<7.1.0 # Apache-2.0
|
|
coverage>=4.0 # Apache-2.0
|
|
fixtures>=3.0.0 # Apache-2.0/BSD
|
|
mock>=2.0,<4.0 # BSD
|
|
python-subunit>=0.0.18 # Apache-2.0/BSD
|
|
sphinx>=1.5.1,<2.0.0 # BSD
|
|
sphinxcontrib-httpdomain # BSD
|
|
stestr>=2.0.0 # Apache-2.0
|
|
testtools>=2.2.0 # MIT
|
|
setuptools<82.0.0 # MIT
|
|
jinja2<3.1.0 # BSD
|