[03:15:26] <buck1> all the people stuffing readme.md into long-description are doing it wrong yes? https://github.com/search?utf8=%E2%9C%93&q=filename%3Asetup.py+readme.md&type=Code&ref=searchresults
[07:55:17] <ychaouche> I need help understanding why uninstall can't remove one of my packages
[07:55:21] <ychaouche> it's installed in /usr/local/
[07:55:28] <ychaouche> Please see command output here : https://gist.githubusercontent.com/ychaouche/76f8088955d4744f012b/raw/1e50177fa556c69c41fd4e087e9246e4982733b0/gistfile1.txt
[07:56:17] <ychaouche> I don't remember how it was installed, I think I used pip install -e but I'm not sure.
[08:07:47] <ychaouche> Here's a grep on local https://gist.githubusercontent.com/anonymous/505e795dc294333d1514/raw/5663f5185b9ec4766a51f08c497ad5b3d87ace39/gistfile1.txt
[08:08:58] <ychaouche> mm.. I should have nl'ed it
[08:09:56] <ychaouche> and this is a grep on infomaniak https://gist.githubusercontent.com/anonymous/50bdc07ee348f9195439/raw/f1b6402f7fcb8bdc26ed6dcd59201da49c52fe99/gistfile1.txt
[08:11:24] <ychaouche> what do you think of -e file ? (maybe some stat and fstat calls would be relevant)
[09:05:08] <mgedmin> actually I'm not sure about the 1st; perhaps the setuptools version of setup.py install writes a manifest file that pip can read
[09:09:16] <ychaouche> ok, how do I install using pip ? here's what I tried : pip install --src infomaniak/ infomaniak and ychaouche@ychaouche-PC ~/REPOS/INFOMANIAK $ pip install -r .
[13:53:40] <moldy> was it ever considered to warn the user if pip is run as root?
[13:56:15] <ionelmc> isn't sudo enough of a warning?
[14:41:23] <moldy> ionelmc: not everyone uses sudo
[14:42:06] <moldy> ionelmc: pip has a bad repuration for breaking user's systems, because people who are not-so-familiar with python run pip as root and end up with broken systems
[14:43:13] <moldy> to a naive user, it's not obivous that running pip as root is usually a very bad idea
[14:43:18] <ionelmc> well yeah, that's how debian got their dist-packages patch to python
[14:43:28] <ionelmc> and we all know how terrible that is
[14:43:35] <moldy> ionelmc: i am not familiar with that patch
[14:44:13] <moldy> i think a big fat warning and a 5 seocnd wait or so would be a good idea :)
[14:44:17] <ionelmc> they added a custom install scheme in distutils
[14:44:31] <ionelmc> so now virtualenv needs special handling for that
[14:44:45] <ionelmc> cause virtualenvs have no dist-packages, and no local/lib
[14:45:19] <moldy> hmm, ok. though i don't see the connection yet.
[14:45:34] <ionelmc> basically their patch makes packages install (via pip or setuptools) in a different place than where the apt-provided packages install to
[16:13:33] <edrahn> Hello, I can't seem to use a python version older than 2.7.8 with virtualenv
[16:13:42] <edrahn> I get CertificateError traceback's
[20:33:18] <tdsmith> does a new package on pypi need to be explicitly registered before upload or is "twine upload" sufficient to register a package?
[20:34:41] <dstufft|vpn> tdsmith: I think currently right now you need to reigster it once, you can do it via the webui though and just type in the name with a version 0 or something
[21:25:39] <Moult> Yasumoto: any ideas what could be causing pex: Failed to translate SourcePackage('file:///var/lib/jenkins/.pex/build/numpy-1.9.1.zip'): 'UUID' object has no attribute 'get_hex
[21:26:36] <Yasumoto> I've seen https://github.com/pantsbuild/pex/issues/9 before
[21:33:05] <Yasumoto> brutal, if you can file a new issue, that'd be rad
[21:35:08] <Moult> Yasumoto: i will do a bit of digging first, because this is a very similar environment the my previous one where the same command worked completely
[21:40:16] <Moult> Yasumoto: by the way, when will the master branch be available in my pypi? i'd like to make sure the pex i install has my fix
[21:43:34] <Yasumoto> hm, I think we just convince wickman to cut a new release
[21:44:05] <Yasumoto> I can file an issue, but now you're motivating me to finally land https://github.com/pantsbuild/pex/pull/20 :D
[21:44:21] <Moult> Yasumoto: i've been doing a nasty hack - building pex manully then symlinking it to /usr/bin/pex
[21:50:15] <Moult> Yasumoto: slightly unrelated, but globally i can do python, and it'll drop me into an interpreter with python 3.4.1, and i can import wheel. however if i do pyvenv-3.4 foo and do source foo/bin/activate, and do python (also 3.4.1) and import wheel it says module wheel not found. isthat normal behavior?
[21:50:53] <Yasumoto> after you source foo/bin/activate
[21:50:56] <Yasumoto> you'll need to pip install wheel
[21:51:14] <Yasumoto> only the distributions available from within that virtualenv will be available- you're isolating yourself from the system that way
[21:52:26] <Moult> Yasumoto: so once i'm in the pyvenv, i want to build pex, i just do python setup.py install, but i need to have pip install wheel before that otherwise i build a useless pex. is there anything else i'm forgetting to install?
[21:52:44] <Yasumoto> I think we can also add wheel to the setup.py
[21:52:48] <Yasumoto> not sure why that wasn't included in there
[21:53:29] <Moult> Yasumoto: good point, i will add it, but do you know if i might be missing anything else?
[21:54:50] <Yasumoto> ah, it's specified in extras: https://github.com/pantsbuild/pex/blob/master/setup.py#L54
[21:55:33] <Yasumoto> kinda looking at https://bitbucket.org/tarek/distribute/issue/130
[21:56:25] <Moult> Yasumoto: ok, so it's already in there, and you're right it shoudl be in extras as it technically isn't required for all packages
[22:20:45] <Moult> Yasumoto: the error doesn't really make sense as it suggests i'm not on python3