[IPython-dev] Announcing shrubbery
Sun Aug 21 13:51:42 CDT 2011
According to the guide, pip install pyzmq didn't work because I had to
pass --zmq="/usr/local/" to the setup.py install command. This was a
couple of weeks ago when I did this, so I don't remember the details
(that's why I wrote it all down). I guess this is the result of
compiling zeromq from git. I seem to remember `pip install pyzmq` not
working without zeromq installed already, but I could be wrong.
I did make the choice to install zeromq from git, when I'm sure that
installing from a source tarball would have been easier (this is just
because "git clone" is easier for me, and having the git clone will
make things much easier in the future). And I used homebrew only as a
last resort, where likely I could have gotten more done with it.
Anyway, it's perhaps not the best way to do it, but it's the way that
worked for me, and I wanted to document it publicly in case any of the
tips were helpful to someone else.
On Sun, Aug 21, 2011 at 12:33 PM, MinRK <firstname.lastname@example.org> wrote:
> Your pyzmq steps make it look more complicated than I think it is, if
> users want released versions. There are eggs for osx 2.6,2,7, and
> 3.2, so `easy_install pyzmq` works on osx under most circumstances,
> and includes 32+64b UB libzmq, so you don't need to build and install
> it separately.
> If you do want to build libzmq, you can use homebrew: `brew install
> zeromq --universal` (the universal flag for specifying 32+64b). Since
> this (as well as the default `./configure && make && make install`)
> put libzmq in /usr/local, then pyzmq *is* pip-installable at this
> On Aug 21, 2011, at 11:03, Aaron Meurer <email@example.com> wrote:
>> This is good. Mac OS X users are usually treated like Linux users in
>> that they're expected to be command line savvy to install software
>> (actually more than average, since Linux users at least have package
>> managers). But really we should treat most of them the same as we do
>> Windows users: people who may know Python, or at least are learning
>> it, but aren't very comfortable with the "./configure;make;make
>> install" process.
>> By the way, if anyone's interested, I detailed the steps I took to
>> install the qtconsole in Python 2 in Lion with the XCode 4 developer
>> tools at https://github.com/sympy/sympy/wiki/Installing-the-IPython-qtconsole-in-Mac-OS-X.
>> There's nothing too complicated; you just have to make sure that you
>> get the right things from the right places.
>> Some questions about shrubbery:
>> First, how easy is it to add new packages? It looked to me like you
>> have to edit several places throughout the file to do it, so that it's
>> not trivial, especially if you don't know everywhere to edit the file.
>> Second, I noticed that you are getting everything from git. Have you
>> considered using git submodules?
>> Third, are you considering to just include Python 3 with the installer?
>> Aaron Meurer
>> On Sun, Aug 21, 2011 at 3:18 AM, Grahame Bowland <firstname.lastname@example.org> wrote:
>>> Hi everyone
>>> I've spent the last few days coming up with a Python 3 distribution of
>>> iPython and friends for Mac OS X. It now works (mostly), and I thought
>>> I'd share it.
>>> The home page is here:
>>> and I've put an experimental installer image here:
>>> For a long time I've maintained my Python setup by hand, installing
>>> packages into /usr/local and eventually having a huge mess. Hence this
>>> project - a distribution of software for Mac OS to make it easier for
>>> people to get started with iPython.
>>> I've targeted Python 3 in the hope it'll encourage the porting of more
>>> software to the new version of the language.
>>> There's not too much Mac OS specific about this, except that on Linux
>>> you'd probably want to get packages from your distribution. If anyone
>>> wants to make it work on other platforms that'd be great.
>>> IPython-dev mailing list
>> IPython-dev mailing list
More information about the IPython-dev