Build fails without Python2 headers about streaming-form-data

[patrislav1]

seems related to #32 where the C code is compiled with Python 2.7 headers, but linked against 3.x

[BenBE]

Seems to be an issue with poetry used in the setup script:
python-poetry/poetry#655 (comment)

Forcing /usr/bin/python to symlink to /usr/bin/python3 resolved the issue. Didn't try the virtualenv solutions as I'm not using a virtualenv.

[siddhantgoel]

@patrislav1 could you try installing inside a virtualenv and see if that works?

Ideally I'd love to be able to publish binary wheels so users wouldn't need to compile the package locally. Unfortunately at the moment Poetry does not support this. I would also be open to switching away from Poetry due to this reason in favor of a simple setup.py. In that case though, I would only be able to push wheels for Linux as I don't have other OSs installed (building wheels for a given platform requires access to that platform).

If you can think of a workaround, let me know!

[patrislav1]

I guess there could be complications to shipping binaries as well - different versions of glibc and of other dependencies on users' systems for example.

For the Python version issue, one workaround would be to temporarily change the system-wide symlink, as @BenBE pointed out.
Another possible workaround could be to use poetry env use to specify the Python executable used by poetry, however I can't check that at the moment.

[siddhantgoel]

I guess there could be complications to shipping binaries as well - different versions of glibc and of other dependencies on users' systems for example.

Good point. My guess is that if pip allows uploading and installing binary packages, it should be able to figure those things out. I haven't tried it though.

Anyway, I feel this is more of a local environment issue and has less to do with this package itself. I'm going to mark this issue as closed. If you feel that I could change something in how I build and upload this package, feel free to reopen.