I have finally got myself sorted out to start committing changes into
the
repository. The list as it stands for mod_python 3.2.8 bug rollup
release is:
MODPYTHON-77
The Simplified GIL Aquisition patches.
MODPYTHON-78
Apache 2.2 patches.
MODPYTHON-94
Support for optional mod_ssl funct
torsdagen den 16 februari 2006 22.48 skrev Jim Gallacher:
> Oden Eriksson wrote:
> > tisdagen den 14 februari 2006 13.17 skrev Oden Eriksson:
> >>Hello.
> >
> > [...]
> >
> > I am no programmer, but can't you just look at how this is handled in the
> > core mod_ssl and ldap code?
>
> That would be
req.user is writable (delete read-only claim)
-
Key: MODPYTHON-136
URL: http://issues.apache.org/jira/browse/MODPYTHON-136
Project: mod_python
Type: Bug
Components: documentation
Versions: 3.2
Reporter: Bud
[ http://issues.apache.org/jira/browse/MODPYTHON-136?page=all ]
Jim Gallacher resolved MODPYTHON-136:
-
Fix Version: 3.2
Resolution: Fixed
This was fixed in svn trunk yesterday. The change will not be reflected on the
website until the next
Nicolas, Jim, Grisha (and others who might understand this issue)
When you get a chance, can you read through the JIRA issue:
http://issues.apache.org/jira/browse/MODPYTHON-129
and provide some feedback on whether you think my analysis is correct
and
thus whether mod_python really needs to
On 2/17/06, Graham Dumpleton <[EMAIL PROTECTED]> wrote:
> When you get a chance, can you read through the JIRA issue:
>
>http://issues.apache.org/jira/browse/MODPYTHON-129
>
> and provide some feedback on whether you think my analysis is correct
> and thus whether mod_python really needs to be
Thanks for the feedback. At least I am not wacko. Further comments
below.
On 18/02/2006, at 5:44 PM, Deron Meranda wrote:
I guess the positive thing is that because of this I don't have
any existing code which actually uses multiple mod_python
handlers in the same phase; so this change in behav
