Here is the announcement draft - if you see anything that needs changing,
let me know, otherwise i'll send it out in a couple of days.
From: "Gregory (Grisha) Trubetskoy" <[EMAIL PROTECTED]>
To: [email protected], [EMAIL PROTECTED]
Cc: [email protected]
Newsgroups: comp.lang
Looks good. As soon as you make the official announcement I'll create
branches/3.2.x in svn and we can start on 3.3.
Jim
Gregory (Grisha) Trubetskoy wrote:
Here is the announcement draft - if you see anything that needs
changing, let me know, otherwise i'll send it out in a couple of days.
Will you also be putting the new 3.2.7 HTML/PDF docs on
http://modpython.org/ ?
It also might be useful if you provide a link to Appendix C along
with the announcement so people can easily find the "what's new"
information.
Oh, and for the older docs on the website, is the "3.2" documentation
rea
On Thu, 9 Feb 2006, Jim Gallacher wrote:
Looks good. As soon as you make the official announcement I'll create
branches/3.2.x in svn and we can start on 3.3.
I don't think we need to wait for the announcement - 3.2.7 is already out
if you look on the download page, the announcement is more
Gregory (Grisha) Trubetskoy wrote:
More infromation about mod_python is available at:
sp^
I've created the a 3.2.x branch. Just so we are all clear, the
branches/3.2.x branch gets bug fixes *only*. This will be the source
repository for future 3.2 bug fix releases. New features and major code
modifications continue to go into trunk.
I think any other new branches we create such as
It looks like Grisha has updated the html and pdf docs on the website so
we are good to go.
I'd like to see a change in the way the website is handled so the
maintenance burden no longer falls on Grisha. He has paid his dues after
all. :)
Depending on Grisha's preference, I think we should
PythonHandler in directive sets req.hlist.directory to useless value.
-
Key: MODPYTHON-126
URL: http://issues.apache.org/jira/browse/MODPYTHON-126
Project: mod_python
Type: Bug
Components:
Use namespace for mod_python PythonOption settings.
---
Key: MODPYTHON-127
URL: http://issues.apache.org/jira/browse/MODPYTHON-127
Project: mod_python
Type: Improvement
Components: core
Versions: 3.3
Rep
Have assigning req.filename automatically update req.finfo.
---
Key: MODPYTHON-128
URL: http://issues.apache.org/jira/browse/MODPYTHON-128
Project: mod_python
Type: Improvement
Components: core
Versions:
Jim Gallacher wrote ..
> I'd like to checkin my patch to support apache 2.2. It doesn't add any
> new functionality. Any objections?
If I recollect, the only real issue was the implications on Win32 platform
of changing the APR_STATUS_IS_SUCCESS(s) test to (s == APR_SUCCESS),
because of Win32 the
[
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 a
[
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 added to the
Graham Dumpleton wrote:
Jim Gallacher wrote ..
I'd like to checkin my patch to support apache 2.2. It doesn't add any
new functionality. Any objections?
If I recollect, the only real issue was the implications on Win32 platform
of changing the APR_STATUS_IS_SUCCESS(s) test to (s == APR_SUCCE
Jim Gallacher wrote ..
> Graham Dumpleton wrote:
> > The next section of code has:
> >
> > b = APR_BRIGADE_FIRST(self->bb_in);
> >
> > if (b == APR_BRIGADE_SENTINEL(self->bb_in))
> > return PyString_FromString("");
> >
> > Now I am assuming here that the check with APR_BRIGADE_SE
I've read through the documentation. I like the interface - just call
ap_update_mtime for every object your response depends on (and another
great feature: It starts with the mtime of the file, so that updates to
the script also invalidate the cached response).
Exposing those three functions w
16 matches
Mail list logo
