[Zope3-dev] Re: [Zope-Coders] Re: z3 i18n MessageId class backport to 2.7

[Chris McDonough]

Zope 2.7 already allows for this feature via the "path" directive in the
config file, which allows you to add arbitrary paths to the PYTHONPATH
after minimal startup (before products are loaded, but after the ZConfig
machinery has built a configuration).

On Mon, 2003-08-25 at 17:59, Philipp von Weitershausen wrote:
> Godefroid Chapelle wrote:
> > Hi all,
> > 
> > What we came to on IRC would be to add an src directory at the same 
> > level as lib and to add this src directory to PYTHONPATH besides 
> > lib/python from now on. This would allow to have a natural place for new 
> > (to 2.x) packages coming from zope3 and being able to import names 
> > equally under 2.x and 3.
> 
> +1
> 
> This could indeed allow us to backport much stuff from Zope3 right into 
> Zope2. The benefit is that files can go almost unchanged which makes 
> diffing a lot easier. Actually, I dare to ask whether we would have to 
> maintain two copies of the same files at all, or not simply do one of 
> those famous repository symlinks, for example from Zope/src/zope/i18n to 
> Zope3/src/zope/i18n. The zope.interface package comes into mind as well.
> 
> Philipp
> 
> 
> 
> _______________________________________________
> Zope-Coders mailing list
> Zope-Coders at zope.org
> http://mail.zope.org/mailman/listinfo/zope-coders