[Zope-Coders] setup.py

[Guido van Rossum]

>     GvR> The docstring says:
> 
>     GvR> Common usage: python setup.py build_ext --build-lib
>     GvR> `pwd`/lib/python
> 
> How does that differ from
> 
>     python setup.py build_ext --inplace
> 
> ?

Dunno, but that's what the docstring says.

>     >> 3.  I'm not building anything that's not in the Zope module
>     >> within the Zope setup.py.  So anything ZEO, etc. needs to be
>     >> built in its own setup.py-age.
> 
>     GvR> I don't understand what you're saying here.  Are you just
>     GvR> telling us that you're not creating a setup.py for ZEO?
> 
>     GvR> Question: how does your setup.py affect standalone ZODB?
> 
> Does it make sense for the top setup.py to search subdirectories for
> setup.py's and "call" them?  That would allow you to drop add-ons like
> bsddb3Storage into place and have them built and installed
> automatically.

That's what Zope3's stupid_build.py does.

> Currently, I believe the test runners do find bsddb3Storage's test
> subdir and it executes those tests automatically.  setup.py should
> work similarly, I think.

I'll leave this to Matt Behrens to answer.

--Guido van Rossum (home page: http://www.python.org/~guido/)