Terry MacDonald
terry.macdonald at dsl.pipex.com
Wed Sep 22 14:54:14 EDT 2004
Can anyone put me right on my understanding of the way mod_python works in an apache forked process environment. Each process has its own embedded interpreter and therefore its own sys.path variable. How is it possible for an apache instance/process with its own embedded interpreter to 'reach' across and use/inherit another processes/interpreters sys.path? On Wed, 2004-09-22 at 09:58, Brian Bird wrote: > Might be best to try it: Write a cgi script which prints the sys.path at the > start and at the end. Put a long sleep in the middle then you can visit your > script twice with a browser (start the second visit while the first one is > still running) and see what the sys.path is of your second visit. > > My gut feeling would be that it would be possible but I'm pretty new to > mod_python so I wouldn't rely on that! :-) > > Brian > > -----Original Message----- > From: mod_python-bounces at modpython.org > [mailto:mod_python-bounces at modpython.org] On Behalf Of Terry MacDonald > Sent: 21 September 2004 23:44 > To: mod_python user mailing list > Subject: Re: [mod_python] sys.path shared? > > > Each apache instance/process has its own interpreter therefore its own > sys.path. So I would say it is not possible. > > On Tue, 2004-09-21 at 23:24, Adrian Holovaty wrote: > > I have mod_python code that appends a directory to sys.path and > > deletes that > > directory from sys.path at the end of the handler. Is it possible that, > > between that push and pop, another Apache instance running the same code > > might get the non-popped sys.path, making its sys.path out of sync with > the > > other Apaches? > > > > Adrian > > _______________________________________________ > > Mod_python mailing list > > Mod_python at modpython.org > > http://mailman.modpython.org/mailman/listinfo/mod_python -- Terry Registered Linux User # 311806 www.taumu.com
|