[IPython-dev] iPython binary wheels for OS-X
Aaron Meurer
asmeurer at gmail.com
Mon Dec 9 03:01:28 EST 2013
On Sun, Dec 8, 2013 at 11:02 PM, Chris Barker <chris.barker at noaa.gov> wrote:
> On Sun, Dec 8, 2013 at 9:24 PM, MinRK <benjaminrk at gmail.com> wrote:
>
>>
>> readline should be a dependency on OS X, I know it used to be. The logic
>> may have gotten confused a bit.
>
>
> Does pip support a way to do platform-dependent dependencies? Anyway, pip
> isn't lookeing for it for me. Frankly, no biggie, auto-dependencies are
> nice, but I don't mind hand-installing something if ti's easy to install.
>
> But wouldn't it be a dependency o Windows, too?
>
>>
>> The warning is still correct, and I still recommend that all OS X users
>> easy_install (not pip) readline. The issue has been discussed in various
>> places (here is one), but it's a sys.path priority issue. Nobody should ever
>> use pip to install readline. But since people still do, incorrectly
>> believing that pip is actually a replacement for easy_install,
>
>
> well, I'm pretty sure that is the goal -- really we don't want to almost the
> same package installer for Python....
What's the reason you can't pip install readline? Is it because pip
insists on compiling it? If so, wouldn't wheels solve this issue?
>
>
>
>>
>> IPython has an unadvertised hack to make the normally never importable pip
>> installed readline available, as long as IPython is the first to try to
>> import it.
>>
> hmm -- pretty cool, and it sure works for me, but a bit fragile ;-)
>
>>
>> pyzmq, the only binary dependency of IPython, has had wheels on OS X and
>> Windows for a few releases now, so `pip install --use-wheel ipython[all]`
>> should already work on a fresh OS X system without any help (after
>> installing pip and wheel, of course).
>>
>
> It sure would be nice if that were advertised a bit.....I really did loo,
> but of course I never thought just try it!
>
>>
>>
>> > By the way, the wheels themselves are trivially easy to build, once
>> > setup.py build works....
>>
>> Yes, they are easy to build for yourself, and are typically reusable for
>> machines sufficiently similar to yours. But it's a lot more delicate to be
>> sure that the eggs actually self-identify correctly, and will be properly
>> ignored on systems where they won't work. This is why IPython has decided
>> against building (official) wheel bdists for at least another release.
>
>
> There has been a lot of discussion about this on the distutils list, and I
> _think_ there is more or less a consensus that we should put binary wheels
> up on PyPi for the python.org builds for Windows and OS-X. Those should work
> at this point (sse issues asside for numpy/scipy)
>
> Doing it for Macports or HomeBrew, or what have you is pretty much alost
> cause, but that's not a big deal -- those are systems designed for people to
> compile there own stuff anyway. similar for Linux.
>
> So what's missing?
>
> And, as you say, zmq is really the only one we need anyway, what exactly is
> iPython not doing?
>
>
>>
>> I am 100% behind a semi-not-so-official-wheels-for-osx effort a la Gohlke,
>> that's actually why I started publishing my own wheels.
>
>
> nice! but not that useful if we don't get the word out.
>
>>
>> But honestly,
>> in a student environment, I would recommend anaconda (or just conda).
>>
> non starter for now -- Again, these are NOT scipy stack classes -- and I do
> want wx, and the guy teaching the next class on web development really wants
> virtualenv.
For wx, if you can figure out how to build a conda recipe for it, that
would help a lot. Basically, you could just host your own recipe on
binstar, and if it works, it's pretty likely that Continuum would pick
it up and ship it with Anaconda. I tried it a while back but I didn't
get very far. But if you're actually familiar with it you might get
further.
As for virtualenv, I really recommend trying conda environments. You
can alias virtualenv="conda create -p" if you want. If you have to
have virtualenv, I was able to get it working inside Anaconda (see
https://github.com/ContinuumIO/conda-recipes/tree/master/virtualenv
and https://binstar.org/asmeurer/virtualenv), but only in Python 2.
Python 3 segfaults for some reason (but in Python 3, you really should
use pyvenv instead of virtualenv).
Aaron Meurer
>
> Anocanda does not work (for now) on those.
>
> Anyway -- I feel very strongly that we should play well with the rest of the
> Python word, and that mean pip and wheels ... and we really can do it now.
>
> I guess I need to do a pull request for the "installing" page of the iPython
> web sire next...
>
> -Chris
>
> --
>
> Christopher Barker, Ph.D.
> Oceanographer
>
> Emergency Response Division
> NOAA/NOS/OR&R (206) 526-6959 voice
> 7600 Sand Point Way NE (206) 526-6329 fax
> Seattle, WA 98115 (206) 526-6317 main reception
>
> Chris.Barker at noaa.gov
>
> _______________________________________________
> IPython-dev mailing list
> IPython-dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-dev
>
More information about the IPython-dev
mailing list