Re: [matplotlib-devel] Adding optional setuptools to setup.py

If we're going to use setuptools (actually already required for Python=20
2.3), I think we need to do it completely and not optionally --=20
otherwise users will start to depend on its features, which simply won't =

be there in some cases. In particular, I suspect they will make use of=20
the dependency resolution mechanisms. As I suggested on the ipython-dev=20
list this will do what you want without requiring a change to setup.py:

python -c "import setuptools; execfile('setup.py')" develop

Gael Varoquaux wrote:
> Hi,
>
> I just sent a similar e-mail to the ipython-def mailing list:
> I am not a big proponent of setuptools, but I must admit they have real=
ly
> nice feature for developpers: "python setup.py develop", which does the=

> Python equivalent of a symlink during the install so that it uses the
> source code from the check out to run.
>
> I would like to add these lines to the setup.py:
>
> """
> try:
>     from setuptools import setup, find_packages
> except ImportError:
>     pass
> """
>
> I cannot see waht harm this can do, and I can see the benefit: I instal=
l
> an svn checkout of MPL with:
>
> """
> sudo python setup.py develop --prefix /usr/local
> """
>
> and then maintain this check out by doing "svn up", and this even in
> windows.
>
> What do you think?
>
> Ga=EBl
>
> -----------------------------------------------------------------------=
--
> SF.Net email is sponsored by:=20
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>  =20