Log file Viewer

[05:55:34] <abadger1999> paulproteus: Idle curiosity, are you from somewhere near philadelphia?

[05:56:10] <dstufft> oh hey

[05:56:22] <dstufft> Fastly is gonna give some CDN to *.pypa.io

[05:56:29] <dstufft> so I guess I'll finish setting that up tomorrow

[06:20:15] <Ivo> dstufft: know if the tox / python stuff got fixed on travis yet?

[06:20:35] <dstufft> Ivo: yes it's fixed

[06:20:47] <Ivo> w000t, thanks

[14:25:36] <Ivo> pf_moore: regarding https://bitbucket.org/pypa/wheel/commits/ea7a96017 I just found a valid use of pyXX tag is if you make an asyncio-compatible project, you would want to use py33 tag, not py3

[14:26:03] <Ivo> same if someone was making something that built ontop of pyvenv

[14:26:59] <Ivo> Also, generally you limit your python 2 project to 2.6+2.7 only comptability with py26

[14:27:04] <Ivo> *you could

[14:27:31] <Ivo> I'd say close to a majority of project are 2.6+2.7 compatible only at this point

[14:29:09] <dstufft> well

[14:29:21] <dstufft> the thing is you can't really use python tags to exclude a python version

[14:29:40] <dstufft> if you put a wheel with py33, and someone tries to install on 3.2 they'll just get the sdist

[14:30:54] <dstufft> the wheel version selectors are best used to match against things that actually affect the output, like 2to3, if you'd get the same wheel on 3.2 as you would on 3.3, even if that wheel doesn't work, then there's no reason to do the py33 thing

[18:33:31] <yusuket> dstufft: https://github.com/pypa/warehouse/pull/299 fixed with your suggestions

[20:23:51] <pf_moore> Ivo: what dstufft says. The tags are only really useful when you have 2 wheels *with different contents* (which pretty much never happens except for 2to3 or C extensions).