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

Option to use pip install --use-feature=in-tree-build #3982

Closed
2 tasks done
fx-kirin opened this issue Apr 20, 2021 · 4 comments
Closed
2 tasks done

Option to use pip install --use-feature=in-tree-build #3982

fx-kirin opened this issue Apr 20, 2021 · 4 comments
Labels
kind/feature Feature requests/implementations status/triage This issue needs to be triaged

Comments

@fx-kirin
Copy link

  • I have searched the issues of this repo and believe that this is not a duplicate.
  • I have searched the documentation and believe that my question is not covered.

Feature Request

pypa/pip#9091

The option of pip --use-feature=in-tree-build will be added on the version 21.1.

I want to use it with poetry because of this problem.

@fx-kirin fx-kirin added kind/feature Feature requests/implementations status/triage This issue needs to be triaged labels Apr 20, 2021
@abn
Copy link
Member

abn commented Apr 23, 2021

@fx-kirin how do you think this be used within the poetry context? Is this for cases where nested local path dependencies refer to relative paths within their own dependencies?

@fx-kirin
Copy link
Author

I'm not sure what it should be because I"m not a heavy user of poetry. But I hope I can set an option with something like poetry config because I think normally, local packages doesn't need to be copied to temporary folder to build the package.

Sorry I couldn't get the meaning of what you said "cases" exactcly. But if you use the relative path to outside of the package in Cargo.toml, it should be happened.

@fx-kirin
Copy link
Author

fx-kirin commented Dec 2, 2022

in-tree-build is now default with pip.

@fx-kirin fx-kirin closed this as completed Dec 2, 2022
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 29, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/feature Feature requests/implementations status/triage This issue needs to be triaged
Projects
None yet
Development

No branches or pull requests

2 participants