Grisha wrote ..
>
> On Thu, 8 Dec 2005, Gregory (Grisha) Trubetskoy wrote:
>
> > def index(req)
> > req.content_type = 'text/plain'
> > yield '1\n'
> > yield '2\n'
> > yield '3\n'
> > yield '4\n'
> >
> > When published, this module should return a text content with
> >
Just to make sure, are you using PythonImport directive at all? Want
to eliminate
this as these get run regardless of whether a request against a
mod_python
handler is received. If the code associated with PythonImport took
some time
to run, that might be a contributor.
Anyway, not sure wha
On 18/12/2005, at 3:09 AM, Jim Gallacher wrote:
We had talked about doing a 3.2 final release just after ApacheCon.
A couple of things have cropped up which we have (or should) fix, but
these will not be substantial changes from 3.2.5b. As such I think we
should do another beta followed very
The other bug:
http://issues.apache.org/jira/browse/MODPYTHON-99
also recently found and related, may also be a contributor to the
problems
you are seeing. As Nicolas pointed out, doing introspection on the
request
object seems to be the flavour of the month.
BTW, has anyone though to do
Sorry if this is a duplicate. Resending as am noticing that some of my
python-dev mails are disappearing into a black hole of late and am
trying to work out why.
The other bug:
http://issues.apache.org/jira/browse/MODPYTHON-99
also recently found and related, may also be a contributor to the
Anyone know if there are any technical reasons why input/output filters
as they exist at the moment, applying only to body content and not
headers, can not be specified in a .htaccess files?
Specifically, the SetInputFilter, SetOutputFilter, AddInputFilter and
AddOutputFilter directives of Apache
Jorey Bump wrote ..
> Graham Dumpleton wrote:
> > Anyone know if there are any technical reasons why input/output filters
> > as they exist at the moment, applying only to body content and not
> > headers, can not be specified in a .htaccess files?
> >
> > ...
>
direct sub requests against
other mod_python handlers or static files which include stuff like
common page layouts etc.
Anyway, just toying with ideas.
Graham
> On Tue, 20 Dec 2005, Graham Dumpleton wrote:
>
> > Anyone know if there are any technical reasons why input/output filt
On 21/12/2005, at 3:32 PM, Graham Dumpleton wrote:
Grisha wrote ..
This sounds like a good idea, but it's probably better to push this
off
to
3.3 just to veer on the side of caution.
My $0.02
Grisha
Grisha, do you remember why the following warning is prese
If someone has the time, would you be able to check out the following
scenario for me. It causes a segfault in Apache 2.0.51 on Mac OS X with
mod_python 3.2.5b.
What I am playing with is connection handlers. Specifically, I have a code
file containing:
from mod_python import apache
def conne
I agree with Nicolas, nothing in the new round of issues I have reported
are significant enough to warrant that they be addressed immediately.
Grisha, I have though asked for a small change to be made which will
allow me to make available a proposed new module importer when its done
and for peopl
In a hurry, so a quick note. In 3.2, mod_python.publisher was changed
to read:
if req.method!='HEAD':
# TODO : the problem is that a handler can still use
req.write
# and break the assumption that nothing should be written
with the
# HEAD method.
Just noticed something with PythonAutoReload. It doesn't seem like it
can actually be turned off, unless I am missing the obvious. Can some
one validate this and prove I am not insane.
PythonAutoReload can be set to values of "On" or "Off". The value of
the option is reflected in table object ret
Grisha wrote ..
> > As an an example of an Apache module that uses output filters to do
> > stuff, there is mod_cache. Luckily in that case, a HEAD request is one
> > of various cases where mod_cache decides it will not use the output.
> > This does not mean though that some other output filter th
You are a few weeks too late. :-)
See:
http://issues.apache.org/jira/browse/MODPYTHON-98
There are whole bunch of little issues with adding handlers using
req.add_handler(). For this one you seem to have tread much the
same path as I did.
Graham
Joseph Barillari wrote ..
> Hi,
>
> So far, I
Grisha wrote ..
>
> On Wed, 4 Jan 2006, Graham Dumpleton wrote:
>
> > Either way, we agree that mod_python.publisher should still output
> > content for HEAD.
>
> Yep.
>
> > I would also propose as a change that the req.write() call not cause
> > outp
On 05/01/2006, at 3:15 PM, Gregory (Grisha) Trubetskoy wrote:
On Wed, 4 Jan 2006, Graham Dumpleton (JIRA) wrote:
This makes one wander if there should be a configurable option for
mod_python.psp to tell it not to flush output as well so that
CONTENT_LENGTH could be used in that case as
Jim Gallacher wrote ..
> Howdy gang.
>
> I got distracted by some other stuff for a while there and didn't push
> the 3.2.6 forward. So much for the master plan of releasing 3.2 before
> the end of 2005. :(
>
> There is quite a bit of mail to catch up on, but a quick perusal
> indicates that the
Graham Dumpleton wrote ..
> The only other candidates that one might seriously consider are:
>
> http://issues.apache.org/jira/browse/MODPYTHON-105
>
> Simple change and Grisha agreed that should truncate output for HEAD.
That should have said "should NOT truncate".
Graham
On 12/01/2006, at 11:10 AM, Jim Gallacher wrote:
Jim Gallacher (JIRA) wrote:
[
http://issues.apache.org/jira/browse/MODPYTHON-98?
page=comments#action_12362399 ] Jim Gallacher commented on
MODPYTHON-98:
Applied Graham's suggestions so all these
[Thu Jan 12 20:11:25 2006] [notice] mod_python: (Re)importing module
> 'tests'
> > [Thu Jan 12 20:11:25 2006] [error] [client 127.0.0.1]
> > accesshandler_add_handler_to_empty_hl
> >
> > Regards,
> > Nicolas
> > 2006/1/12, Jim Gallacher <[EMAIL PROTECTE
Jim Gallacher wrote ..
> It's a strange one. When I move site-packages/PIL to
> site-packages/PIL.bak (leaving PIL.pth as is) and run the tests I get
> the same output as Graham and Nicolas. I'm just going to ignore this for
> the time being and go with a refactored unit test.
I am making a gues
Jorey Bump wrote ..
> Roy T. Fielding wrote:
> > It looks like mod_python is making good progress and everyone
> > is collaborating in the Apache way of testing and voting.
> > That's great!
> >
> > Unfortunately, I have almost no insight into who these great people
> > are that are doing the RM t
A few weeks back I created a JIRA entry relating to integrating server
side includes with Python. The entry is:
http://issues.apache.org/jira/browse/MODPYTHON-104
I finally got around to having a go at implementing it and have some
initial code now working. The point of this email is to get fe
On 23/01/2006, at 4:59 PM, Deron Meranda wrote:
I like the SSI feature. It would fill a nice gap between using
plain HTML files and having to go to a more featured template
or engine. Some things are simple enough that the SSI concept
should be enough, and having Python would be nice.
I do n
On 24/01/2006, at 3:07 AM, Deron Meranda wrote:
On 1/23/06, Graham Dumpleton <[EMAIL PROTECTED]> wrote:
Using "print" like that can't be done in an "eval", would need to
use "exec".
Sorry, I probably didn't mean to use the print in my
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
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 writte
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
Barry Pederson wrote ..
> As I mentioned in another message, I did some experimenting with
> disabling other unittests and found if you disable just
> "test_fileupload", all the remaining tests including
> "test_connectionhandler" pass.
>
> If you disable everything except "test_fileupload" and
Grisha wrote ..
>
> On Sun, 29 Jan 2006, Jim Gallacher wrote:
>
> > I don't know if this is the answer to the problem, but it looks like
> a bug
> > anyway. In connobject.c starting at line 133:
> >
> >/* time to grow destination string? */
> >if (len == 0 && bytes_read == bufsiz
Grisha wrote ..
>
> On Sun, 29 Jan 2006, Graham Dumpleton wrote:
>
> > Grisha wrote ..
> >>
> >> buffer = bufsize;
> >>
> >
> > I suspect you mean't:
> >
> > buffer += bufsize;
>
> buffer = bu
Changed subject heading. See more of what I have uncovered below.
Not sure where to go next.
Graham Dumpleton wrote ..
> > > Unlike suggestions by someone else that "self" seemed to be getting
> corrupted,
> > > it looks fine to me, and code simply crashed down in:
On 30/01/2006, at 9:11 PM, Matt Carpenter wrote:
Hi,
Not sure if this is best posted here, or to mod_dav mailing list.
But here goes.
Has anyone looked at using mod_python to backend mod_dav, with a
similar usage to FUSE's python binding. Basically mod_dav_python.
Others may know what you
Getting a bit closer now, have next part of puzzle worked out.
Graham Dumpleton wrote ..
> This is starting to look really ugly.
>
> In _conn_read(), it first creates a bucket brigade from the connection
> objects pool object. No chance of this being destroyed prematurely
&
Graham Dumpleton wrote ..
> Returning back up to _conn_read() in mod_python source code, we have
> where core_input_filter() was called ap_get_brigade():
>
> Py_BEGIN_ALLOW_THREADS;
> rc = ap_get_brigade(c->input_filters, bb, mode, APR_BLOCK_READ, bufsize);
>
Graham Dumpleton wrote ..
> Extending the above code as:
>
> Py_BEGIN_ALLOW_THREADS;
> rc = ap_get_brigade(c->input_filters, bb, mode, APR_BLOCK_READ, bufsize);
> Py_END_ALLOW_THREADS;
>
> if (! APR_STATUS_IS_SUCCESS(rc)) {
> Py
An initial few comments from a first pass through.
def _write(self, request, response, content_type='text/xml'):
request.send_http_header()
request.content_type = content_type
request.write(response)
This is technically wrong, although it doesn't matter on mod_python >
I am having problems with posts to python-dev mailing list from home
occassionally disappearing in a black hole. Thus my post on this topic
before Jim brought it up in the first place vanished. What I has said was:
>> this code runs smoothly, i.e. no segfaults, all tests passed:
>> FreeBSD 4.9:
>>
This is a resend to python-dev list of an email I sent yesterday. For
some reason oaccsional email I am sending to list from home is
dissappearing, although people cc'd it are getting it. Apologies if
this is a duplicate.
On 30/01/2006, at 9:49 PM, Matt Carpenter wrote:
> Graham Dumplet
And another one that seemed to vanish into thing air.
On 31/01/2006, at 10:11 PM, Matt Carpenter wrote:
>
>
> Graham Dumpleton wrote:
>> Regardless of how you might use it, from a technical standpoint I
>> would say that
>> it is not going to be possible at prese
On 02/02/2006, at 6:52 AM, Deron Meranda wrote:
Actually it seems that this is yet another case of trying to get
mod_python to hook into more places in the Apache framework;
specifically to hook into other modules.
We've already been discussing specific-module hooks for
mod_ssl - http://iss
Again this is a resend. I post one message via my secure SMTP and it
vanishes. Post one via normal SMTP and it goes to list straight away.
This sort of confirms what I suspected which is that my ISPs secure
SMTP is busted somehow in that randomly drops email. :-(
Sorry for the duplicate if first
I was looking at the new module importer used by mod_python.publisher in
3.2.6 to see whether it reloaded a module if file was replaced with an
older file and have come across some code that worries me a bit. Can
someone else (not just Nicolas) check this code and how it is used in
the context of t
y open the file to stat it?
Graham
Graham Dumpleton wrote ..
> I was looking at the new module importer used by mod_python.publisher in
> 3.2.6 to see whether it reloaded a module if file was replaced with an
> older file and have come across some code that worries me a bit. Can
>
Graham Dumpleton wrote ..
> Okay, false alarm (I think). Have got myself worked up over nothing.
> I missed something very important:
>
> timestamp = fstat(opened.fileno())[-2]
>
> That is the '[-2]' in the above.
>
> I feel like a goose now.
Now for some e
Nicolas Lehuen wrote ..
> Well, I thought that if the file was modified, we needed to open it
> anyway, but you're right, that's optimising for a minority case. We
> might as well use stat and open the file only if it has changed.
>
> I've wrote an alternative publisher a few months ago that overl
Nicolas Lehuen wrote ..
> 2006/2/2, Graham Dumpleton <[EMAIL PROTECTED]>:
> > Note that up until now I hadn't even looked over how this new module
> > importer was implemented. I knew it wasn't going to solve various of
> the
> > existing module importer p
Nicolas Lehuen wrote ..
> OK, I've changed cache.py so that it uses stat() then open() the file
> if it needs to be reloaded. I've also added a unit test that makes
> sure the module cache is behaving as expected.
>
> Graham, I don't think the stat() / open() / fstat() sequence is
> required. How
Nicolas Lehuen wrote ..
> 2006/2/2, Graham Dumpleton <[EMAIL PROTECTED]>:
> > > The only
> > > problem is that apache.import_module is still as crappy as ever and
> > > that we don't have any grand unified theory of module importing that
> > >
Nicolas Lehuen wrote ..
> OK, I've reverted my changes. I left python22.py in place, because I
> still hope to be able to use it with PythonImport. The only problem is
> being able to define it in the unit tests.
I plead dumb. What is the connection to PythonImport?
My only guess at the moment is
On 02/02/2006, at 5:42 PM, Nicolas Lehuen wrote:
That's it ! People with Python 2.2 could use "PythonImport
mod_python.python22 INTERPRETER_NAME" in their configuration file to
make sure mod_python supports Python 2.2. The only problem is the need
to provide an interpreter name, which complicat
On 02/02/2006, at 5:54 PM, Nicolas Lehuen wrote:
Having read your work on Vampire (and its
module importing mechanism) I'm pretty sure it won't be long.
The new importer is actually a complete rewrite and some things
are done quite differently to what was done in Vampire. I have in
effect rew
On 03/02/2006, at 4:48 AM, Daniel J. Popowich wrote:
My gut says any major release of mod_python be based on one
major.minor release lower than the currently available python. So,
mod_python 3.2 is based on python 2.3; mod_python 3.3 will probably be
based on python 2.4 (because 2.5 will be out
Daniel J. Popowich wrote ..
> PS
> If it's not obvious I'm gearing up to get way more involved...I've
> been waiting (patiently) for 3.2 to be released and jump in with new
> 3.3 development...I guess I'm chomping at the bit...
We probably want to defer until after 3.2.7 (final) is released to hav
Very interesting. I'll only comment on one issue right now.
Daniel J. Popowich wrote ..
> o And...no suprise...I'd like to try to sell mpservlets for
> inclusion in the main distro. No tears if it's not, but I think
> it fills a void and I'd like to make a case for its inclusion.
I con
Jim Gallacher wrote ..
> > It is because you probably have a prefork/worker MPM.
> >
> >> The test as written will only reliably work for winnt MPM.
> >
> >
> > Doh! Prefork bites us in the a** yet again. :)
> >
> >> On UNIX boxes
> >> the subsequent requests could be handled by a different c
On 03/02/2006, at 2:54 PM, Jim Gallacher wrote:
Graham Dumpleton wrote:
To confirm Jim's arithmetic anyway, I say -1 on 3.2.6 as it stands.
As to 3.2.7, I say +1, subject to removal of problematic test case
as already raised and with us at least confirming tests run OK for
version out o
Jim, Nicolas
Would it make sense to change test_Session_Session_conf() function in
unit tests to something like:
def test_Session_Session_conf(self):
import tempfile
tempdir = tempfile.gettempdir()
database = os.path.join(tempdir,"mp_sess_test.dbm")
c = Virt
What version of BASH shell are you using? Can't remember the version,
but a
particular patch level revision of BASH released recently has a bug in
it
which causes configure to error. Ie., it is a BASH bug and not
mod_python.
Have to run now, so more later.
Graham
On 07/02/2006, at 6:46 AM, S
Grisha
I have a really obscure question for you.
Was there a specific reason that mod_python did not allow a handler
to be hooked using ap_hook_map_to_storage()?
I know that the reasons for wanting to do this would be very limited,
such as if you wanted to implement some sort of equivalent to mo
Graham Dumpleton wrote ..
> Grisha
>
> I have a really obscure question for you.
>
> Was there a specific reason that mod_python did not allow a handler
> to be hooked using ap_hook_map_to_storage()?
>
> I know that the reasons for wanting to do this would be very l
Nicolas Lehuen wrote ..
> OK so my core group vote is +1 for this release.
>
> It has been tested on a wide array of OSes, both threaded and forked
> MPMs, Python 2.2, 2.3 and 2.4, so I guess it's okay. A threaded test
> on MacOSX and Solaris would have been great but maybe the recommended
> MPM o
Versions: 3.3
Reporter: Graham Dumpleton
One purpose of the type checker phase in Apache, as able to be hooked using the
PythonTypeHandler directive, is to use it to make decisions as to which actual
handler should be used to deliver up the content for a request. It is also
intended
[
http://issues.apache.org/jira/browse/MODPYTHON-125?page=comments#action_12365686
]
Graham Dumpleton commented on MODPYTHON-125:
Forgot to mention that req.content_languages is not documented in mod_python
HTML documentation for request
: core
Versions: 3.2
Reporter: Graham Dumpleton
When you have Apache ".htaccess" configuration like:
SetHandler mod_python
#PythonPath "['/Users/grahamd/Sites/auth']+sys.path"
PythonHandler page1::handler_txt
PythonHandler page2::hand
Reporter: Graham Dumpleton
In the interests of avoiding name clashes, I want to push that where mod_python
uses its own PythonOption settings, that they use a namespace. For example:
PythonOption mod_python.session_cookie_name ...
PythonOption mod_python.ApplicationPath
: 3.3
Reporter: Graham Dumpleton
Although it is possible to assign a new value to "req.filename", it is not
possible to update "req.finfo" based on the new filename.
Suggest that if "req.filename" is assigned a new value, that apr_stat() be
automatically ca
[
http://issues.apache.org/jira/browse/MODPYTHON-109?page=comments#action_12365805
]
Graham Dumpleton commented on MODPYTHON-109:
The problem is actually bigger than just Py_Finalize(). When a server cleanup
handler is registered using either
[
http://issues.apache.org/jira/browse/MODPYTHON-126?page=comments#action_12365820
]
Graham Dumpleton commented on MODPYTHON-126:
It is impossible to fix this in a way that wouldn't require additional
configuration directives to be add
nents: core
Versions: 3.2
Reporter: Graham Dumpleton
Todays daily bug report, or is it? ;-)
The Python*Handler documentation says:
"""Multiple handlers can be specified on a single line, in which case they will
be called sequentially, from left to right. Same handl
[ http://issues.apache.org/jira/browse/MODPYTHON-129?page=all ]
Graham Dumpleton updated MODPYTHON-129:
---
Description:
Todays daily bug report, or is it? ;-)
The Python*Handler documentation says:
"""Multiple handlers can be specif
[
http://issues.apache.org/jira/browse/MODPYTHON-129?page=comments#action_12366149
]
Graham Dumpleton commented on MODPYTHON-129:
Content handlers also seem to work differently in mod_python than Apache itself
when using C handlers or even
Reporter: Graham Dumpleton
In order to be able to more easily maintain last modified response header and
ETag, should expose:
ap_set_etag()
ap_update_mtime()
ap_set_last_modified()
through the request object. Ie.,
req.set_etag()
req.update_mtime()
req.set_last_modified()
Direct
[
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
[
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-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-126?page=comments#action_12366319
]
Graham Dumpleton commented on MODPYTHON-126:
FWIW, I think I know how to fix the above so it works. This time I stumbled
onto the fact that in Apache one can
[
http://issues.apache.org/jira/browse/MODPYTHON-94?page=comments#action_12366727
]
Graham Dumpleton commented on MODPYTHON-94:
---
The attached patch uses Python native bool type.
+is_https = optfn_is_https && optfn_is_https(self->
Make name of mutex directory configurable.
--
Key: MODPYTHON-131
URL: http://issues.apache.org/jira/browse/MODPYTHON-131
Project: mod_python
Type: Improvement
Components: core
Versions: 3.2
Reporter: Graham
Expose ap_construct_url() in request object.
Key: MODPYTHON-132
URL: http://issues.apache.org/jira/browse/MODPYTHON-132
Project: mod_python
Type: Improvement
Components: core
Versions: 3.3
Reporter: Graham
nents: core
Versions: 3.2
Reporter: Graham Dumpleton
If you put:
PythonDebug On
in your main Apache configuration file, one would assume that you can then in a
.htaccess file say:
PythonDebug Off
and that in the .htaccess file would override that in the main Apache
configur
Reporter: Graham Dumpleton
As announced on the mailing list:
http://www.modpython.org/pipermail/mod_python/2006-February/020284.html
If you are using the recently released mod_python 3.2.7 please beware that a
security issue was discovered in the FileSession code.
You are vulnerable only if you
[
http://issues.apache.org/jira/browse/MODPYTHON-124?page=comments#action_12366957
]
Graham Dumpleton commented on MODPYTHON-124:
Changes to add req.auth_name(), req.auth_type() and make req.ap_auth_type
writable commited into mod_python SVN
[
http://issues.apache.org/jira/browse/MODPYTHON-76?page=comments#action_12367168
]
Graham Dumpleton commented on MODPYTHON-76:
---
Latest update on this issue is that the change of not flushing if filter closed
does not in itself fix the
sions: 3.3
Reporter: Graham Dumpleton
Even after running a distclean, the following files are left in test directory.
? test/testconf.pyc
? test/httpdconf.pyc
? test/Makefile
? test/htdocs/dummymodule.pyc
? test/htdocs/cgitest.pyc
? test/htdocs/tests.pyc
Shou
[ http://issues.apache.org/jira/browse/MODPYTHON-112?page=all ]
Graham Dumpleton updated MODPYTHON-112:
---
Attachment: grahamd_20060223_1.diff
Attached patch "grahamd_20060223_1.diff".
Would like confirmation on final solution for this is
[
http://issues.apache.org/jira/browse/MODPYTHON-128?page=comments#action_12367490
]
Graham Dumpleton commented on MODPYTHON-128:
Here is link to discussion of similar change being ported from mod_perl 1 to
mod_perl 2.
http://www.gossamer
[
http://issues.apache.org/jira/browse/MODPYTHON-138?page=comments#action_12367799
]
Graham Dumpleton commented on MODPYTHON-138:
Suggest this be put on hold anyway until original poster actually attaches here
the original output from the
[ http://issues.apache.org/jira/browse/MODPYTHON-104?page=all ]
Graham Dumpleton reassigned MODPYTHON-104:
--
Assign To: Graham Dumpleton
> Allow Python code callouts with mod_include (
[ http://issues.apache.org/jira/browse/MODPYTHON-104?page=all ]
Work on MODPYTHON-104 started by Graham Dumpleton
> Allow Python code callouts with mod_include (SSI).
> --
>
> Key: MODPYTHON-104
>
[ http://issues.apache.org/jira/browse/MODPYTHON-104?page=all ]
Graham Dumpleton updated MODPYTHON-104:
---
Attachment: grahamd_20060226_MP104_1.diff
Attached "grahamd_20060226_MP104_1.diff" which is more up to date patch against
head of
[ http://issues.apache.org/jira/browse/MODPYTHON-133?page=all ]
Graham Dumpleton reassigned MODPYTHON-133:
--
Assign To: Graham Dumpleton
> req.server.get_config() table object populated wron
[ http://issues.apache.org/jira/browse/MODPYTHON-137?page=all ]
Graham Dumpleton reassigned MODPYTHON-137:
--
Assign To: Graham Dumpleton
> Add req.server.get_options() for obtain PythonOption values set at global
>
[ http://issues.apache.org/jira/browse/MODPYTHON-134?page=all ]
Graham Dumpleton reassigned MODPYTHON-134:
--
Assign To: Graham Dumpleton
> Setting PythonDebug to Off, doesn't override On setting in pare
[ http://issues.apache.org/jira/browse/MODPYTHON-129?page=all ]
Graham Dumpleton reassigned MODPYTHON-129:
--
Assign To: Graham Dumpleton
> HandlerDispatch doesn't treat OK/DECLINED result properly for al
[ http://issues.apache.org/jira/browse/MODPYTHON-109?page=all ]
Graham Dumpleton reassigned MODPYTHON-109:
--
Assign To: Graham Dumpleton
> Signal handler calling Py_Finalize() when child processes being kil
[ http://issues.apache.org/jira/browse/MODPYTHON-133?page=all ]
Work on MODPYTHON-133 started by Graham Dumpleton
> req.server.get_config() table object populated wrongly.
> ---
>
> Key: MODPYTHON-133
>
[ http://issues.apache.org/jira/browse/MODPYTHON-133?page=all ]
Graham Dumpleton updated MODPYTHON-133:
---
Attachment: grahamd_20060226_MP133_1.diff
Attached "grahamd_20060226_MP133_1.diff" containing proposed changes.
> req.serv
[ http://issues.apache.org/jira/browse/MODPYTHON-133?page=all ]
Graham Dumpleton updated MODPYTHON-133:
---
Fix Version: 3.3
> req.server.get_config() table object populated wron
301 - 400 of 1069 matches
Mail list logo
