Cython Extensions

[frnkvieira]

Hello! Firstly, this project is awesome.

I'm a heavy user of C extensions and Cython modules but they are specified in the setup.py file to be compiled to native code at install time. I'm not sure if they should be specified in "pyproject.toml" because even in the PEP there are no mentions to it. I'm willing to do a pull request if needed so I just need a direction :)

Keep the great work, many thanks!

[emmatyping]

AIUI, this would require Cython to create a build backend as specified in https://www.python.org/dev/peps/pep-0517. Then poetry would "just" need to add support for PEP 517.

[emmatyping]

It seems like currently you can use the undocumented (unstable) build.py like in #11.

[salotz]

I added an example on using cython in #11. Cython probably wouldn't have to have the build backend (except as a library which it basically already has in the form of cythonize). From how I understand PEP 517 only one build backend is allowed anyhow since the 'build-backend' is just a single string and Cython would never be the only build backend. So poetry, flit, or (more likely) pip will be the build backend. That is unless poetry takes the place of pip. For instance if you try to install that package I made with pip from source you need to have Cython already installed without the PEP 518 requires = ['setuptools', 'wheel' 'Cython'] which pip supports now and installs cython before building.

[salotz]

So this issue can be closed if poetry can be used as a build backend. How that is implemented (build.py etc.) is another issue probably.

[kasteph]

Closing this issue, see solutions (by @sdispater and @salotz in #11).

[github-actions]

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.