Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecation warning about in-place builds is confusing/ambiguous #10128

Closed
1 task done
maresb opened this issue Jul 4, 2021 · 1 comment · Fixed by #10129
Closed
1 task done

Deprecation warning about in-place builds is confusing/ambiguous #10128

maresb opened this issue Jul 4, 2021 · 1 comment · Fixed by #10129
Labels
type: bug A confirmed bug or unintended behavior

Comments

@maresb
Copy link
Contributor

maresb commented Jul 4, 2021

Description

I have trouble understanding the text of the deprecation message:

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 #7555.

Expected behavior

I would expect that after reading the deprecation message once, I understand roughly what is going to be changed, what will be removed in pip 21.3, and what I can do about it.

For more details, see #7555 (comment)

pip version

21.1.3

Python version

3.9.5

OS

Linux

How to Reproduce

Run pip install .

Output

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.

Code of Conduct

@maresb maresb added S: needs triage Issues/PRs that need to be triaged type: bug A confirmed bug or unintended behavior labels Jul 4, 2021
@pradyunsg
Copy link
Member

Whee! Thanks for filing this issue and PR separately @maresb! Much appreciated! ^>^

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 24, 2021
@pradyunsg pradyunsg removed the S: needs triage Issues/PRs that need to be triaged label Mar 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: bug A confirmed bug or unintended behavior
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants