[IPython-dev] Python 3 single codebase - merged

Aaron Meurer asmeurer at gmail.com
Tue Oct 29 20:22:29 EDT 2013

I think an even better way is to use a .pth file
(http://docs.python.org/2/library/site.html#module-site). This has the
advantage that they are environment specific, so, for instance, I can
put IPython dev in one environment and IPython stable in another. If
you modify $PYTHONPATH and $PATH globally, it's a mess.

I personally use conda environments, and so I think this strategy is
the best in that situation (hopefully conda will gain the ability to
manage this stuff soon too). If it works with virtualenv, it would
probably be the best there too.

Aaron Meurer

On Tue, Oct 29, 2013 at 6:11 PM, Fernando Perez <fperez.net at gmail.com> wrote:
> On Tue, Oct 29, 2013 at 2:26 PM, Aaron Meurer <asmeurer at gmail.com> wrote:
>> This seems to be a general problem with setup.py develop. It only
>> supports developing into one Python environment at a time, which is
>> annoying if you have a ton of environments (e.g., with conda). I'm
>> very interested in how you end up fixing this.
> One alternative (what I do) is to *not* use `setup.py develop` and instead
> just manually symlink the IPython directory somewhere in $PYTHONPATH and the
> `ipython` entry point somewhere in $PATH.  Then it's a trivial matter of
> aliasing
> ipy3 = python3 `which ipython`
> and you're off to the races, always running from source.
> Cheers,
> f
> --
> Fernando Perez (@fperez_org; http://fperez.org)
> fperez.net-at-gmail: mailing lists only (I ignore this when swamped!)
> fernando.perez-at-berkeley: contact me here for any direct mail
> _______________________________________________
> 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