-
Notifications
You must be signed in to change notification settings - Fork 2.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
Implement the Build Backend Interface described in PEP 517 #191
Comments
The point is not to have setup.py anymore. Instead, the next version of pip will be able to install packages that have |
Oh, I see. Isn't there an issue regarding this? Should I close this and open one? |
@ambv I am a little confused. I thought that:
|
@Victor-Savu, oh, if pip 10 already does that then great. What do you put in your |
@ambv whoops, I have indeed been dreaming (Present and future were intermingling. Electric sheep were jumping around). Sorry for the confusion! Indeed, poetry would need to be prepared to implement the Build Backend Interface described in PEP 517 in order to be used by pip. |
I need this feature and create simple tool for this: poetry-setup. Try it, if someone want it too :) |
With This would allow us to use |
@bertjwregeer This has been added in commit 8055bcf. It will be officially available in the next I will try to make another alpha build this week so that it can be tested. |
@sdispater Awesome. I am sorry I missed the commit! |
A PEP-517 compliant build system is now available: https://poetry.eustace.io/docs/pyproject/#poetry-and-pep-517 |
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. |
I think it would help adoption if we could use poetry without requiring our users to also use it. I see that
poetry publish
already generates it. Is there any reason not to include a flag in, for example,poetry build
to write it in the project root?The text was updated successfully, but these errors were encountered: