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 "Py
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. Aquiring a lock is quite expensive, so the
do
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 d
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 th
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 unexpect
It seems like any 3.2.6 testing that is going to be done, has been done.
How long do we wait before making a decision for an official release.
If we don't get cracking on 3.3 soon Graham's gonna fill another couple
of pages on JIRA and we'll never catch up. :)
Jim
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
Jim Gallacher wrote ..
> It seems like any 3.2.6 testing that is going to be done, has been done.
> How long do we wait before making a decision for an official release.
>
> If we don't get cracking on 3.3 soon Graham's gonna fill another couple
> of pages on JIRA and we'll never catch up. :)
You
On Thu, 26 Jan 2006, Jim Gallacher wrote:
It seems like any 3.2.6 testing that is going to be done, has been done.
I've been kinda swamped with unrelated things past two weeks, so I wasn't
paying much attention. Perhaps an e-mail summarizing the +1's so far and a
quick vote of the core grou
Gregory (Grisha) Trubetskoy wrote:
On Thu, 26 Jan 2006, Jim Gallacher wrote:
It seems like any 3.2.6 testing that is going to be done, has been done.
I've been kinda swamped with unrelated things past two weeks, so I
wasn't paying much attention. Perhaps an e-mail summarizing the +1's so
Gregory (Grisha) Trubetskoy wrote:
On Thu, 26 Jan 2006, Jim Gallacher wrote:
It seems like any 3.2.6 testing that is going to be done, has been done.
I've been kinda swamped with unrelated things past two weeks, so I
wasn't paying much attention. Perhaps an e-mail summarizing the +1's so
[
http://issues.apache.org/jira/browse/MODPYTHON-114?page=comments#action_12364176
]
Graham Dumpleton commented on MODPYTHON-114:
Note that the call to acquire the mutex lock should be moved outside of the try
block.
if config.has_key("Pyt
import_module() and multiple modules of same name.
--
Key: MODPYTHON-115
URL: http://issues.apache.org/jira/browse/MODPYTHON-115
Project: mod_python
Type: Bug
Components: core
Versions: 3.1.4, 3.2
Report
Attributes removed from module code file still accessible until restart.
Key: MODPYTHON-116
URL: http://issues.apache.org/jira/browse/MODPYTHON-116
Project: mod_python
Type: Bug
Components: co
[
http://issues.apache.org/jira/browse/MODPYTHON-116?page=comments#action_12364187
]
Graham Dumpleton commented on MODPYTHON-116:
Whoops, forgot to reference back to my problem list for completeness. :-)
This problem is listed as ISSUE 13 in my
Wow - I wonder how many programs are leaking memory today because of
this double-check issue. I've been using it myself for years (yes, also
in Java)...
Having read the article, I've come to the following conclusions:
- Python indeed won't suffer from this problem. But I agree to keep on
the sa
16 matches
Mail list logo
