Log file Viewer
#pypa logs for Tuesday the 12th of November, 2019
[14:55:12] <pombreda_> toad_polo: re "What does "all the packages with native I use" mean?" --> I have projects that depend on wheel with native C/C++ code as in https://github.com/nexB/scancode-toolkit/tree/develop/thirdparty
[14:57:43] <pombreda_> toad_polo: in particular integer sets, bit sets and arrays and aho-corasick code (in addition of usual suspects such as lxml, etc)
[15:23:08] <sumanah> https://pyfound.blogspot.com/2019/11/seeking-developers-for-paid-contract.html Freelancers and consulting companies: take a look at the 2 paid roles available working on pip
[17:48:31] <zware> pombreda_: So you're looking to create a build of third-party projects that will work on multiple versions of Python?
[19:29:53] <zware> pombreda_: Sounds like a weird thing to do, but it got me curious enough to try it :). Looks like you should be able to accomplish it by basically building a wheel for each version and merging them together. As long as the extension modules are tagged properly (and the final wheel itself is too), it ought to work
[19:49:44] <zware> pombreda_: It's has a manual step with `kdiff3` in the middle of it, but this test with psycopg2 worked for me for 3.6 and 3.7: `for v in 3.6 3.7; do rm -rf dist/; python$v setup.py bdist_wheel; wheel unpack -d ${v}wheel dist/*.whl; done; kdiff3 *wheel -o combined_wheel; wheel pack combined_wheel/*`
[21:32:47] <Wulf> Is it okay to have one base distribution with files "pkg/__init__.py", "pkg/sth/__init.py" and multiple extension distributions with "pkg/ext/foo/__init__.py" where "foo" is the name of my extension? It appears to work like this. But so far I only used namespace packages that had no common base files.
[22:27:36] <sumanah> Wulf: not sure, but https://mail.python.org/mailman3/lists/distutils-sig.python.org/ might know