[12:36:54] <tos9> `python2.6 -m pip install WebTest==2.0.17` properly installs the dependency on ordereddict, but `python2.6 -m pip install WebTest==2.0.18` does not, and there is 0 suspicious looking things in the diff between them.
[12:48:25] <ronny> tos9: as far as i can tell nothing, what pip version, is there a wheel cache?
[13:51:12] <ionelmc> tos9: wheel caching then, cause webtest doesn't use environment markers for the ordereddict conditional dependency
[14:16:27] <tos9> ronny / ionelmc: tox is handling the install, let's see -- I also checked for those.
[14:16:35] <tos9> But I also know that tox does funny things about creating sdists.
[14:17:15] <ionelmc> tos9: tox just caches the sdist within a single run (eg: when you run multiple envs) afaik
[14:17:24] <ionelmc> but on the next run it rebuilds it
[14:17:58] <tos9> ionelmc: I think it also runs sdists with different pythons sometimes, at least I have that written down in my list of tox idiosyncracies
[14:27:25] <ionelmc> maybe there should be a --no-binary=:sdist:
[14:28:16] <ronny> ionelmc: what i'd like is a --disable-wheel-cache
[18:41:44] <preyalone> help, i deleted the old release, but i can't republish it. i get Submitting dist/liquidnitrogen-0.0.tar.gz to https://pypi.python.org/pypi; error: HTTP Error 400: This filename has previously been used, you should use a different version.
[18:42:07] <tos9> that looks like a 0.0 release -- you really want to republish that?
[18:42:31] <tos9> I don't know if that's actually possible -- someone will chime in from PyPI I'm sure though.
[18:43:16] <preyalone> python packaging syntax is incredibly difficult to get right, and there are almost no checks on publish. so i'm wasting version numbers just to get my requirements.txt included, for example.
[18:45:41] <tos9> What's wrong with wasting version numbers :P
[18:46:01] <tos9> (Also yes you're correct -- but you can test your sdists before you upload them)
[18:46:08] <tos9> correct that packaging is difficult to get right that is.
[18:46:54] <preyalone> the fact that requirements.txt was missing wasn't even caught by pip install -e ., nor by the upload process
[18:47:52] <preyalone> i'll take republishing as impossible due to the filenames being cached somewhere as a given, and start using 0.0.x while i debug this crap
[18:50:41] <preyalone> heh, 0.0.0 works flawlessly: https://github.com/mcandre/liquidnitrogen
[18:54:28] <tos9> well yeah requirements.txt isn't required, so it won't be caught by pip install -e . or by anything else
[18:54:33] <tos9> it shoudl be caught by running your tests though
[18:54:55] <tos9> generally my process is to create an sdist, unzip it, create a venv, install it in there, run the tests, they pass, I upload