On Wed, Oct 7, 2009 at 9:45 AM, Alan Kennedy <jython-dev@...> wrote:
> > > But I think that it should not be standard behaviour; I'd prefer to
> > > make it optional behaviour, so that it doesn't interfere with WAR
> > > deployments.
> > Out of curiosity: Why would it interfere with WAR deployments?
> > [I'm the most interested on keeping the stand-alone WAR deployments
> > working, but not realizing why importing site would break them make me
> > feel stupid ;-)]
> Indeed, that is the key question.
> My thinking is that importing site i.e. processing Lib/site-packages,
> would require a jython installation on the machine, i.e. an absolute
> setting for python.home.
> But I suppose that if python.home is set to WEB-INF/lib-python, then
> the site import should still work.
> I'm leaning now to having a "load_site_packages" parameter, but
> defaulting it to true, to emulate the behaviour of the interactive
> interpreter as much as possible.
> Any further thoughts, or objections, before I go checking this in?
Not from me. I'll test if doj WAR deployment have any issue with the
change later (but before 2.5.2, of course).
Leo Soto M.