Log file Viewer

[10:33:18] <iElectric> how can I pass the --compiler flag to bdist_wheel?

[10:35:41] <iElectric> right https://github.com/pypa/pip/issues/881

[10:47:08] <apollo13> iElectric: maybe CC=gcc …

[11:42:57] <angular_mike_> how do I install a specific pip for python 2.7 in a user's home folder?

[11:43:37] <angular_mike_> `pip install --user pip` yields "Requirement already satisfied" because it detects the system-wide pip

[11:43:52] <nedbat> angular_mike_: try with -U ?

[11:44:39] <angular_mike_> nedbat: "Requirement already up-to-date: pip in /usr/lib/python2.6/site-packages"

[11:45:16] <angular_mike_> as I said, it keeps detecting the system-wide pip installation

[11:45:32] <angular_mike_> hm

[11:45:38] <angular_mike_> il ltry -I

[11:47:40] <angular_mike_> strange, now `which` still shows it pointing at system folder `/user/bin`, but --version shows it to be located in my home folder

[11:51:50] <angular_mike_> I've got python2.6 installed system-wide and python2.7 locally for my user and I want it to have installed and use the appropriate pip version

[12:00:38] <angular_mike_> when I try to install a package with pip it fails with "Only python 2.7 and later is supported" even though I have 2.7 installed locally. HOw do I make pip detect it?

[12:01:03] <angular_mike_> how does pip check installed python version>]

[12:07:30] <angular_mike_> ehh, I gave up and created a virtualenv

[12:52:18] <tos9> angular_mike_: Every Python gets its own pip.

[12:52:36] <tos9> pip install --user pip will of course always be satisified already :)

[12:58:27] <iElectric> dstufft: how does numpy build wheels with build flags like --compiler?

[12:58:35] <iElectric> I don't see a way to pass arguments to bdist_wheel

[12:59:01] <dstufft> iElectric: they probably are building wheels using setup.py bdist_wheel?

[12:59:37] <iElectric> are or arent?

[13:01:08] <iElectric> dstufft: your statement contradicts with mine

[13:01:30] <dstufft> iElectric: Oh I thought you meant via pip wheel

[13:01:48] <dstufft> I think you can do ``python setup.py build_ext --compiler foo bdist_wheel``

[13:01:59] <dstufft> could be wrong though

[13:03:35] <iElectric> hmmm

[13:03:41] <iElectric> I'll play around, thanks

[14:08:10] <ronny|tablet> Hi

[14:09:46] <ionelmc> sup

[14:19:18] <ronny|tablet> Still recovering from the removal of my wisdom teeth

[14:19:51] <ronny|tablet> And waiting for the last parts of my replacement pc to arrive

[21:19:23] <tos9> how do you use requirements.txt's in coordination with setuptools extras

[21:19:55] <tos9> specifically how do you have pinned versions of extras for deployments -- do you *have* to have a separate requirements.txt for the version of the package with the extra?