-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Installing local packages with a pyproject.toml fails #6824
Comments
I'm actually thinking that this could be related to: #6375 Wondering if this should be closed. |
Thanks for filing this issue! We've stopped importing typing on master, to avoid issues like this. This is fixed in master and you can expect it to be fixed in the next release of pip. 🙃 |
I'm also curious if this is supposed to be supported? We use |
I believe this is supposed to work; a pyproject.toml file in this case (missing build-system specification) is simply ignored. |
Nope -- we opt-in packages with pyproject.toml to build isolation, and use the PEP 517 interface to build their package. Functionally, it doesn't matter to most packages, unless they're doing cross-compilation or linking between two C extensions in different packages. |
Closing since this is fixed in master. Expect this to be fixed in the next release. That said, I'm not sure why you're seeing a failure with the typing import, so you might want to investigate the same. |
Environment
Description
When installing a package locally with a
pyproject.toml
a typing exception is thrown.Expected behavior
Package is installed successfully.
How to Reproduce
Install the sampleproject(I've included the pyproject.toml file) locally.
Output
The text was updated successfully, but these errors were encountered: