Hello Pythonistas.

We are about to update pip in rawhide to 21.3. It does in-tree builds by default and hence if your package sues pyproject-rpm-macros, you won't find it the built stuff in %{_pyproject_builddir} anymore.

The following packages will need changes:

python-numcodecs.spec
72:PYTHONPATH=$(ls -d %{_pyproject_builddir}/pip-req-build-*/build/lib.%{python3_platform}-%{python3_version}) sphinx-build-3 docs html

python-pikepdf.spec
60:PYTHONPATH=$(ls -d %{_pyproject_builddir}/pip-req-build-*/build/lib.%{python3_platform}-%{python3_version}) sphinx-build-3 . ../html

python-matplotlib.spec
302:PYTHONPATH=$(ls -d %{_pyproject_builddir}/pip-req-build-*/build/lib.%{python3_platform}-%{python3_version}) \

rpm-specs/python-pydata-sphinx-theme.spec
81:PYTHONPATH=$(ls -1d $PWD/.pyproject-builddir/pip-req-build-*) make -C docs 
html

Note that %{_pyproject_builddir} was prefixed with underscore exactly for this reason (packages that use it might need changes).

With pip 21.3+, replacing %{_pyproject_builddir}/pip-req-build-*/build with ${PWD}/build should do. However, that will loose compatibility with older pip.

We only plan to do this change in rawhide.

You can use this copr for testing:

https://copr.fedorainfracloud.org/coprs/churchyard/pip-21.3/

(Pull Request integration is set, so if you send a PR to your pckage, you can observe the results in https://copr.fedorainfracloud.org/coprs/churchyard/pip-21.3/builds/?dirname=pip-21.3:pr:<number>

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Reply via email to