2006/2/14, Graham Dumpleton <[EMAIL PROTECTED]>:
[...]
> If we want to go down the path of having interim 3.2 bug rollup releases
> while 3.3 is being developed, might I suggest that we target the following
> for such a release in the near future.
>
> MODPYTHON-77
>
> The Simplified GIL Aquisitio
It seems that bu dfdefault Perl is not thread safe, and that they have
to jump through all those hoops to ensure thread safety. There is no
real lesson for mod_python, I just wanted to know how they solved this
rather difficult problem.
Not instantiating one interpreter per name per thread and usi
Jim Gallacher wrote ..
> Jorey Bump wrote:
> > Jim Gallacher wrote:
> >
> >> This is how I would set priorities:
> >
> >
> >> Try and assign most of the issues to someone. This is a bit of PR
> >> spin, but I think it looks bad when there are a large number of open
> >> issues with no assignee.
[
http://issues.apache.org/jira/browse/MODPYTHON-63?page=comments#action_12366270
]
Graham Dumpleton commented on MODPYTHON-63:
---
In what will be the grand unified theory for the module importer, there will be
no explicit modification of sys.path,
[
http://issues.apache.org/jira/browse/MODPYTHON-29?page=comments#action_12366267
]
Graham Dumpleton commented on MODPYTHON-29:
---
Whether one allows this means making some sort of policy decision about what
the purpose of mod_python.publisher is.
[
http://issues.apache.org/jira/browse/MODPYTHON-47?page=comments#action_12366265
]
Graham Dumpleton commented on MODPYTHON-47:
---
The simplest way of fixing this problem may be that after changes related to
MODPYTHON-124 are made that the publishe
This has been discussed before, and I think it came down to that it wasn't
clear how this is any better than simply generating your httpd.conf with
an outside Python script.
I think some other arguments were that this changes the syntax of the
config file very radically and therefore this is
On Mon, 13 Feb 2006, Nicolas Lehuen wrote:
http://perl.apache.org/docs/2.0/user/intro/overview.html#Threads_Support
Which part of it - the pool of interpreters? Are they doing it out of
necessity, i.e. there is no way to run multiple threads in Perl like we do
in Python because of Python's
http://perl.apache.org/docs/2.0/user/intro/overview.html#Threads_Support
Regards,
Nicolas
Hi,
I'm currently reading the feature section from mod_perl. Initially, I
was trying to find information about how they cope with
multithreading, multiple interpreter instantiation and code reloading,
but I stumbled upon this :
http://perl.apache.org/start/tips/config.html
Now, I can't stand Per
The Apache Software Foundation and The Apache HTTP Server Project are
pleased to announce the 3.2.7 release of mod_python. Mod_python 3.2.7
is considered a stable release, suitable for production use.
Mod_python is an Apache HTTP Server module that embeds the Python
language interpreter within t
Graham Dumpleton wrote:
As Jim pointed out a while back, we need to get going on mod_python 3.3
before I fill up JIRA with another page of bug reports or suggestions.
I think you already *have* filled another page since I made that comment. ;)
That said, how do we want to proceed on this? Do
Mike Looijmans wrote:
Oh and if we are refactoring the tests, I want a "make tests" rule. I'm
tired of doing: ./configure; make; sudo make install; make tests; DOH!
cd test; python test.py. :)
Make that "make check" (like autotools), to not confuse old-skool
autoconfers like myself.
That w
13 matches
Mail list logo
