Re: [Zope3-Users] Buildout and custom python

[Zvezdan Petkovic]

On Dec 21, 2007, at 9:28 AM, Christian Theune wrote:



Am Freitag, den 21.12.2007, 09:15 -0500 schrieb Benji York:

Christian Theune wrote:
And you can mix-and match: have buildout profiles that use your  
personal `good` Python for development and production profiles  
that build it themselves. OTOH this is somewhat controversial  
regarding test what you fly, fly what you test ... ;)


As long as you also run your tests in production, it seems fine to  
me.


True. OTOH you really don't want your development environment to be  
far off your production environment. Joel (Spolsky) wrote a good  
article about leaking abstractions. It can be rather nasty to find a  
failing test when wanting to put something into production. (Of  
course this is way better than going in production and not seeing  
failing tests.)



If that clean python is built as a package (e.g., an rpm) and the  
product is also built as a package (see zc.sourcerelease) which  
declares to depend on the clean python package, the development and  
production environments will be the same.  It'll fly what it tested.

:-)

--
Zvezdan Petkovic [EMAIL PROTECTED]

___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users

Re: [Zope3-Users] Buildout and custom python

[Zvezdan Petkovic]

On Dec 21, 2007, at 10:18 AM, David Pratt wrote:
I really would like to see a two stage buildout that does the python  
construction with a python.cfg and then the main buildout with  
buildout.cfg file as part of the standard fare. I'm trying a few  
things today to see if a simple event class and callback can be used  
to create the python first and have the callback's handler run the  
main buildout as an experiment.



In other words you want to build two products with one buildout.
Python is a language your product depends on.  It does not need to be  
a part of your product as the C language and libc are not part of the  
Python.


As I mentioned in the previous post in this thread one can get the  
same development and production environments by properly packing clean  
python and their product(s).  The added advantage is that N products  
can use the same clean python instead of having it deployed N times as  
a part of their buildout.


--
Zvezdan Petkovic [EMAIL PROTECTED]

___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users