[17:33:38] <cerivera> with my custom package, when i do pip install —upgrade PACKAGE. it tells me it's downloading version 0.12.6 (latest). i verify the version after install in ipython using PACKAGE.__version__
[17:33:45] <cerivera> however, when i do pip freeze | grep PACKAGE
[17:33:50] <cerivera> it shows an older package version
[17:34:34] <cerivera> basically, pip install —upgrade always downloads and installs 0.12.6 because it thinks an older version is installed
[18:10:43] <nedbat> there used to be download stats on the PyPI pages, but I don't see them now. Are they gone, or just harder to find?
[18:11:38] <dstufft> nedbat: which download stats? there are ones that say the daily/week/ymonthly download numbers is that what you mean?
[18:12:13] <nedbat> dstufft: I want to know how many people are downloading the 3.2 kit for coverage.py compared to the 3.3 and 3.4
[18:12:56] <dstufft> nedbat: you mean the per file download counts?
[19:31:16] <josePhoenix> that information is hard to discover
[19:31:55] <dstufft> I more or less recommend RTD not upoading docs to pypi
[19:32:12] <josePhoenix> RTD doesn't work for our docs
[19:32:43] <josePhoenix> I talked to someone about it and they basically said "yeah, we'd like to support scientific python packages better, eventually"
[19:32:49] <ionelmc> dstufft: well i guess i can just take the wheels (they'd be artifacts) and upload them myself
[19:33:52] <ionelmc> dstufft: is this really needed https://raw.githubusercontent.com/pypa/python-packaging-user-guide/master/source/code/run_with_compiler.cmd ?
[19:34:11] <ionelmc> it seemed to compile just fine on 3.4 on appveyor (without that)
[19:34:13] <dstufft> I know very little about Windows
[20:38:26] <pf_moore> ionelmc: if it's about that run_with_compiler script, it's needed for C extensions. If you don't have them, you don't need it (but you also don't need to build the wheels on Appveyor)
[20:40:58] <pf_moore> It also isn't needed if you only do 32-bit builds, as VC express 2010 includes the 32-bit compilers
[20:41:42] <pf_moore> But it is needed for 64-bit, maybe it's a bit complicated but it's known to work so why mess with it?
[20:46:00] <ionelmc> pf_moore: will the ps script make the last install the "default" python ?
[20:46:34] <pf_moore> Honestly, I don't know. You should specify the full path to avoid uncertainty
[20:47:52] <pf_moore> The silent MSI install is not very well documented and I didn't have the time or inclination to experiment just so users could take a risk doing "python" without a path...
[20:49:20] <pf_moore> BTW, the script also avoids trying to install pip if it's present (3.4, 2.7.9). So it doesn't do more work than it needs, shouldn't impact build speed much.
[20:49:51] <pf_moore> If setting up the env is taking up too much of the build time, write more tests ;-)