If target handler found but evaluates false, there should still be an error if
not silent.
--
Key: MODPYTHON-101
URL: http://issues.apache.org/jira/browse/MODPYTHON-101
Project: mod_pyth
[ http://issues.apache.org/jira/browse/MODPYTHON-101?page=all ]
Graham Dumpleton updated MODPYTHON-101:
---
Description:
If one specifies PythonHandler directive and the target is mistakenly set to be
something like:
handler = 0
handler = None
[
http://issues.apache.org/jira/browse/MODPYTHON-101?page=comments#action_12360713
]
Graham Dumpleton commented on MODPYTHON-101:
Whoops, to be as precise as possible, instead of the suggested:
if not hlist.silent or object:
i
Hi Graham,
It looks like this can't break anything since the init() function is
called once per interpreter (no multithreading problem). So +1 for me.
Regards,
Nicolas
2005/12/18, Graham Dumpleton <[EMAIL PROTECTED]>:
>
> On 18/12/2005, at 3:09 AM, Jim Gallacher wrote:
>
> > We had talked about
Introspection of mp_request and some other built-in classes usually
crashes Apache on my system (Win XP SP1).
My Python version (as reported by sys.version) is '2.4.1 (#65, Jun 20
2005, 17:01:55) [MSC v.1310 32 bit (Intel)]'. sys.api_version is 1012.
(All of those values are through mod_python/Apa
This also comes up when using eval().
On 12/19/05, Jamie Bliss <[EMAIL PROTECTED]> wrote:
> Introspection of mp_request and some other built-in classes usually
> crashes Apache on my system (Win XP SP1).
>
> My Python version (as reported by sys.version) is '2.4.1 (#65, Jun 20
> 2005, 17:01:55) [M
I swear, this is the last one.
An access violation occurs in Python24.dlll when this python code executes:
eval("reg.boundary")
I don't know the internals of apache, so I can't say why or how.
On 12/19/05, Jamie Bliss <[EMAIL PROTECTED]> wrote:
> Introspection of mp_request and some other built-
Hi Jamie,
This is a known bug :
http://issues.apache.org/jira/browse/MODPYTHON-96
What's weird is that this bug has existed for a long time now, but has
been discovered this month only - and reported twice since !
It is this is the subversion repository, and the fix will be released
in the next
