PEP 517 Supported Builds #3
Description
Problem
The pyproject.toml format, defined in PEP 518 and elaborated in here has become the dominant interface for packaging. PEP 517 build systems, such as poetry-core and its build backend poetry.core.masonry.api are unable to install python-libsnark via the PyPi package as well as direct from source given that python-libsnark does not currently support PEP 517 builds. So far, even direct pip installs into environments which were managed by Poetry are also failing.
Proposed Next Steps
Utilizing setuptools to help with compatibility it appears that utilizing the existing setup.py is still an option as long as a minimal pyproject.toml is present and the project metadata is present. See Building Extension Modules on the setuptools documentation for a reference. Additional backwards compatibility with setup.py and setup.cfg methods while supporting PEP 517 systems can be seen in the pip repository.
It seems that this should help in maintaining backwards compatibility while supporting modern build systems. As such I would propose a minor version bump, pushing the version to 0.4.0 given that PEP 517 build is the added functionality, and a dividing line would be formed between PEP 517 and non-PEP 517 builds of python-libsnark