I agree with Graham on the whole, but I'd like to point out a few things.
1) The current publisher implementation, with its own dynamic loading
mechanism, already fixes
http://issues.apache.org/jira/browse/MODPYTHON-9
http://issues.apache.org/jira/browse/MODPYTHON-10
http://issues.apache.org/jira/
I don't have a really have a clear understanding of all the issues with
the import mechanism, but I'd rather see a correct fix rather than a
quick fix.
Nicolas Lehuen wrote:
4) Graham, I don't know what it takes to be a member of the
development team, but to me you are one :).
+1 on that. I'
[
http://issues.apache.org/jira/browse/MODPYTHON-52?page=comments#action_12314508
]
Jim Gallacher commented on MODPYTHON-52:
Support for flex detection has now been committed, including documentation.
This issue can be closed.
> path to flex used
Nicolas Lehuen wrote:
Hi Jim,
I don't have much time now but there should be a complete list here :
http://issues.apache.org/jira/secure/ReleaseNote.jspa?version=11060&styleName=Html&projectId=10640&Create=Create
Nice. That will certainly make things easier.
What you should add to your list
[
http://issues.apache.org/jira/browse/MODPYTHON-58?page=comments#action_12314514
]
Jim Gallacher commented on MODPYTHON-58:
Fix committed to subversion. This issue can now be closed.
> _apache._global_lock results in segfault when index > number o
On Sun, 26 Jun 2005, Nicolas Lehuen wrote:
2) The only thing I'm not too proud of, retrospectively, is
publisher.get_page.
One thing we can do is leave it undocumented and put a comment in the code
warning people not to rely on it as it is not a "sure thing".
Grisha
[ http://issues.apache.org/jira/browse/MODPYTHON-52?page=all ]
Nicolas Lehuen resolved MODPYTHON-52:
-
Fix Version: 3.2.0
Resolution: Fixed
> path to flex used in compiling mod_python is hard coded
> -
