Add support for non pure python projects

[sdispater]

We should have a way to build non pure-python projects (from instance if they need to build C extensions).

[feluxe]

Hi!

Does this work with poetry?

Impressive work by the way! :)

[sdispater]

Thanks for your interest in poetry!

Yes, it works even though it's not currently documented because I do not know if it will stay this way since it relies on adding kwargs to the setup.py.

Anyway, it you want to test this, you have to specifiy a build script in your pyproject.toml:

[tool.poetry]
build = 'build.py'

that will define a build function that will add the necessary build keyword arguments to the call to setup() in the generated setup.py.

An example of this is in my pendulum project:

• pyproject.toml
• build.py

[feluxe]

This look promising! Thanks!

I'll give it a shot for my next package.

[bruxisma]

I know this issue is closed at this point, but I wanted to say I'm so glad this is here. I've been struggling with pipenv so much that I've stared into the abyss and we're now on a first name basis.

I'm currently working a library called brujería, that lets you treat your C and C++ modules as if they were python modules (both for REPL imports as well as setuptools builds). I'm still working out the kinks (I have to write another library so it can be decoupled from all of CMake's garbage), but I think it might help others in this situation. It's not in a working state at the moment as I'm doing janitorial work on both repos, but I still wanted to mention it also, @sdispater thank you for poetry. It's been so nice and I've only been using it for 10 minutes so far. :)

[salotz]

Here is an example for building a cython module https://github.com/ADicksonLab/geomm/blob/master/build.py.

[shimil]

Hey @sdispater, I love Poetry!
We want to adopt it as part of our tech stack, but consider support for C extensions an important feature. Can we count on continued support for it?

Many thanks