Implement the Build Backend Interface described in PEP 517

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?

[sdispater]

A PEP-517 compliant build system is now available: https://poetry.eustace.io/docs/pyproject/#poetry-and-pep-517

[Victor-Savu]

@ambv whoops, I have indeed been dreaming (Present and future were intermingling. Electric sheep were jumping around). pip only added support for PEP 518 and not for PEP 517 (here is the tracking issue for PEP 517 support: https://github.com/pypa/pip/issues/5407) This is mainly because PEP 517 is only provisionally accepted (pending real-world experience from tools such as pip).

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.