Log file Viewer

[06:41:05] <pdobrogost> jaraco: Thanks for information. Btw, do you remember what made separation infeasible?

[09:27:46] <jaraco> @pdobrogost: http://setuptools.readthedocs.io/en/latest/history.html#v36-0-0 was the change and 34.0.0 was the original intention to allow dependencies. I think there's also a ticket where I describe challenges taking pkg resources out of Setuptools while vendoring is present

[16:26:30] <agronholm> could someone point out a project on github that builds a C extension using the limited ABI?

[16:26:43] <agronholm> I would like to see how that works out with pypy3

[17:14:05] <agronholm> pypy folks said pypy doesn't support the limited API

[17:22:20] <agronholm> dstufft: are you around? I have a few questions about ABI tags and https://github.com/pypa/wheel/issues/187

[17:22:41] <dstufft> agronholm: half way

[17:23:10] <agronholm> dstufft: nice! first off – is pip the canonical source for the pep425tags module?

[17:23:43] <dstufft> there isn't really a cannonical source atm, and I think wheel and pip have slgihtly different implementations

[17:23:51] <dstufft> I'd love to do something in packaging that both could consume though

[17:24:05] <agronholm> sure

[17:24:48] <agronholm> next I'm wondering if, when building binary wheels on linux, it should use "manylinux1_x64_64" etc for the ABI tag, or linux_x86_64

[17:25:17] <agronholm> I tried replacing pep425tags into wheel from pip but then the first supported combo used manylinux1

[17:25:41] <agronholm> or should manylinux1 only be manually set?

[17:27:17] <dstufft> agronholm: probably manylinux1 should only be manually set, because building a manylinux1 wheel is non trivial and requires doing things carefully

[17:27:29] <agronholm> yup

[17:27:48] <agronholm> okay, so regarding #187, all I have to do is remove the special casing for pypy...?

[17:28:05] <agronholm> I'm kinda confused as to what the proper tagging should be for pypy

[17:28:17] <dstufft> I'm not sure anyone knows for sure atm :)

[17:28:34] <agronholm> let me put this another way: I'm not sure what I need to do to close #187

[17:29:46] <dstufft> it looks like, from a reading of the issue, the primary thing isn't compiled modules, but for pure python wheels they're currently getting tagged as PyPy specific?

[17:30:03] <pdobrogost> agronholm: You might find https://github.com/pypa/pip/issues/3844 interesting

[17:30:27] <agronholm> dstufft: not according to https://github.com/pypa/wheel/issues/187#issuecomment-317889348

[17:30:35] <agronholm> but that should be easy to test

[17:33:55] <dstufft> agronholm: I think WRT binary extesions, talking it out with the PyPy folks to figure out what makes sense for them is probably the next step

[17:34:07] <agronholm> dstufft: I just confirmed that wheels get the proper py2/py3/py2.py3 tags on pypy

[17:34:08] <agronholm> and pypy3

[17:34:18] <agronholm> w/o extensions

[17:35:43] <agronholm> pdobrogost: yeah that does look relevant

[17:36:53] <agronholm> oh boy, looks like serious drama

[17:38:45] <pdobrogost> like most things in python packaging… :/