You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
nicoa opened this issue
May 27, 2021
· 3 comments
· Fixed by #1405
Assignees
Labels
bugSomething is not workingciRelated to continuous integration taskspipRelated to pipPR wantedFeature is discussed or bug is confirmed, PR neededtestsTesting and related things
There is a deprecation leading to failing CI since a few days, namely the one discussed in pypa/pip#7555:
DEPRECATION: A future pip version will change local packages to be built in-place without first copying to a temporary directory. We recommend you use --use-feature=in-tree-build to test your packages with this new behavior before it becomes the default.
pip 21.3 will remove support for this functionality. You can find discussion regarding this at https://github.com/pypa/pip/issues/7555.
I'm not sure about the options here - i.e. if this should be filtered out or tested as suggested by pip maintainers in that message and where / how to do this in the tests when the cli is invoked.
Further, a second problem are the pip deprecation warnings for the "previous" pip test setup.
So, the obvious solution would be to do the following on each pip-call: use feature flag in recent pip (as suggested in the warning above) and suppress version warnings in previous pip (export PIP_DISABLE_PIP_VERSION_CHECK=1).
Unfortunately I'm not sure how to proceed here or how to move the warnings from the pytest error section to the pytest warnings section.
If the solution is easy to implement and one could guide me to the proper place and has a bigger vision of what should happen and has the time for this, I'd be happy to get some guidance to file a PR.
The text was updated successfully, but these errors were encountered:
webknjaz
added
bug
Something is not working
ci
Related to continuous integration tasks
pip
Related to pip
PR wanted
Feature is discussed or bug is confirmed, PR needed
tests
Testing and related things
labels
May 27, 2021
Regarding pytest, this can be suppressed with the filterwarnings option. But of course, it's best to test pip in different modes, especially since the default is going to get flipped at some point.
One could consider adding another env for piplatest with suppressed warning about new feature, but imho this wouldn't be necessary.
If nobody says this would be the wrong approach or should be done differently, I'd be happy to file a PR and test if that works out properly - let me know if you have any objections!
Seems that it is not only related to the above issues, but as well to now the fake-with-deps package gets output for wheel built, opposed to before. Not sure if this is related to the latest updates to setuptools (there was a new release recently).
EDIT: okay, seems I tracked it down to setuptools release. with 56.2.0 it works on my local machine, with 57.0.0 it is broken. Will continue investigating, let me know if the traceback of the failing code (not included in the CI output) would help you.
bugSomething is not workingciRelated to continuous integration taskspipRelated to pipPR wantedFeature is discussed or bug is confirmed, PR neededtestsTesting and related things
There is a deprecation leading to failing CI since a few days, namely the one discussed in pypa/pip#7555:
I'm not sure about the options here - i.e. if this should be filtered out or tested as suggested by pip maintainers in that message and where / how to do this in the tests when the cli is invoked.
Further, a second problem are the pip deprecation warnings for the "previous" pip test setup.
So, the obvious solution would be to do the following on each pip-call: use feature flag in recent pip (as suggested in the warning above) and suppress version warnings in previous pip (
export PIP_DISABLE_PIP_VERSION_CHECK=1
).Unfortunately I'm not sure how to proceed here or how to move the warnings from the pytest error section to the pytest warnings section.
If the solution is easy to implement and one could guide me to the proper place and has a bigger vision of what should happen and has the time for this, I'd be happy to get some guidance to file a PR.
Links
The text was updated successfully, but these errors were encountered: