[12:50:16] <DanielHolth> Ha! I think I've finally cracked pip & virtualenv's "install into non-ASCII paths" problem.
[15:02:12] <DanielHolth> so are we still promoting virtualenv for, say, py34?
[15:43:09] <tomprince> Supporting, certainly. Since pepole will continue using it until every version they use supports venv.
[17:45:50] <aclark> dstufft: any reason why twine can't work with .exes? Pillow binaries are killing me
[17:46:14] <aclark> dstufft: i forked and started working on it and ran in to… something. Just want to make sure conceptually it makes sense.
[17:48:29] <dstufft> aclark: so I've never created an exe in my life, nor do I have access to a sane windows machine. If the .exe's contain a emtadata file that twine can read, then sure it makes sense
[17:51:31] <aclark> dstufft: they're binary so I doubt they contain anything like that
[17:52:20] <aclark> dstufft: However "File type: MS Windows Installer" is an option TTW…
[17:53:23] <aclark> Seems like it should be possible to punt on all but the minimum metadata and/or use the filename to gather py version
[17:54:31] <tomprince> Well, it would certainly be possible to make build_exe or whatever makes them add the appropriate metadata.
[17:55:16] <aclark> (And… I'm so tired I just uploaded a half dozen 2.5.1 exes to Pillow 1.7.8 :-\. Grrr.)
[17:55:26] <dstufft> aclark: sorry I'm sick so i'm not really thinking all that well. So far we send all of the metadata when we upload to ensure the correct metadata. I'm not sure if that's a requirement or not i'd have to think about it
[17:56:21] <aclark> dstufft: i'll go with what tomprince suggested and send you a PR
[18:04:47] <DanielHolth> The Pillow .exes are bdist_wininst, they can be unzipped to obtain PLATLIB/Pillow-2.5.1-py3.4.egg-info/
[18:05:11] <DanielHolth> Not terrifically different than wheels actually. Except they have an .exe prepended.