Problems with PythonPath directive.
---
Key: MODPYTHON-114
URL: http://issues.apache.org/jira/browse/MODPYTHON-114
Project: mod_python
Type: Bug
Components: core
Versions: 3.2, 3.1.4
Reporter: Graham Dumpleton
The
On 26/01/2006, at 11:48 PM, Mike Looijmans wrote:
Two comments:
1. (bug): The acquire() call should be *outside* the try ... finally
block. You do not want to release a lock that you did not aquire.
Whoops. Quite agree. One hopes that acquiring a simple mutex lock never
fails though. If it
2006/1/26, Mike Looijmans [EMAIL PROTECTED]:
Two comments:
1. (bug): The acquire() call should be *outside* the try ... finally
block. You do not want to release a lock that you did not aquire.
2. (optimization): If you are not planning to change the path, you do
not have to aquire the lock.
Graham Dumpleton wrote:
Thus, trade off of speed versus correctness is probably reasonable as it
will
not cause a failure. In general I tend towards robustness and unexpected
surprises and that is why the code was written as it was.
Personally I tend towards robustness and *away* from
Jim Gallacher wrote ..
Graham Dumpleton wrote:
Thus, trade off of speed versus correctness is probably reasonable as
it
will
not cause a failure. In general I tend towards robustness and unexpected
surprises and that is why the code was written as it was.
Personally I tend towards
