We added "setupegg.py" a long time ago which does exactly this.  The
line below would then be:

python setupegg.py develop

On Dec 12, 2007 12:35 PM, Gael Varoquaux <[EMAIL PROTECTED]> wrote:
> On Wed, Dec 12, 2007 at 09:32:04AM -0800, Andrew Straw wrote:
> > If we're going to use setuptools (actually already required for Python
> > 2.3), I think we need to do it completely and not optionally --
> > 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
> > the dependency resolution mechanisms. As I suggested on the ipython-dev
> > list this will do what you want without requiring a change to setup.py:
>
> > python -c "import setuptools; execfile('setup.py')" develop
>
> OK, I'll settle for this.
>
> Gaƫl
>
> -------------------------------------------------------------------------
> SF.Net email is sponsored by:
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services
> for just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Reply via email to