[ http://issues.apache.org/jira/browse/MODPYTHON-46?page=all ]
Graham Dumpleton updated MODPYTHON-46:
--
Attachment: silent.diff.txt
This fixes the wrong logic problem in the definition of SILENT/NOTSILENT.
It avoids the infinite loop bug described
[
http://issues.apache.org/jira/browse/MODPYTHON-68?page=comments#action_12318143
]
Graham Dumpleton commented on MODPYTHON-68:
---
I add my own -1 to this patch to add req.script_name. It is just as easy to
stick it in a root level handler
This raise this issue : under Win32, the preferred way to build mod_python is to run :
python setup.py.in bdist_wininst --install-script win32_postinstall.py
This leaves no room to specify a MAX_LOCK definition override, but I
guess we could put it in setup.py, since extension modules can have
On Tue, 9 Aug 2005, Jim Gallacher wrote:
My question is : should we keep on with ./configure ; make ; make install
or try to do everything in setup.py ?
As long as we can put setup.py in a Makefile. ;)
Seriously though, ./configure --help; ./configure; make; make install; is
just such
Jim Gallacher writes:
Daniel Popowich wrote:
The recent discussion of max locks and deadlocking issues with
_apache._global_(un)?lock() are timely for me:
I'm in the middle of writing a caching module for mod_python servlets
so a developer can have the output of a servlet cached,
Daniel Popowich wrote:
Jim Gallacher writes:
Daniel Popowich wrote:
The recent discussion of max locks and deadlocking issues with
_apache._global_(un)?lock() are timely for me:
I'm in the middle of writing a caching module for mod_python servlets
so a developer can have the output of a
