[jira] Resolved: (MODPYTHON-85) ./configure does not find the correct PY_STD_LIB for x86-64 platform

2005-10-28 Thread Jim Gallacher (JIRA)
[ http://issues.apache.org/jira/browse/MODPYTHON-85?page=all ] Jim Gallacher resolved MODPYTHON-85: Fix Version: 3.2 Resolution: Fixed > ./configure does not find the correct PY_STD_LIB for x86-64 platform >

[jira] Resolved: (MODPYTHON-86) Multiple session cookies created when ApplicationPath is set to /

2005-10-28 Thread Jim Gallacher (JIRA)
[ http://issues.apache.org/jira/browse/MODPYTHON-86?page=all ] Jim Gallacher resolved MODPYTHON-86: Fix Version: 3.2 Resolution: Fixed > Multiple session cookies created when ApplicationPath is set to / > ---

Re: mod_python 3.2.3b available for testing

2005-10-28 Thread Jim Gallacher
Indrek Järve wrote: Graham Dumpleton wrote: Jim Gallacher wrote .. Indrek Järve wrote: Jim Gallacher wrote: And see if any tests fail. If they pass, send a +1 to the list, if they fail, send the details (the versions of OS, Python and Apache, the test output, and suggestions,

Move changes from README to CHANGES file

2005-10-28 Thread Jim Gallacher
Hi Grisha, Any objection if I split the "changes" from README to a new CHANGES file? Jim

Re: Move changes from README to CHANGES file

2005-10-28 Thread Gregory (Grisha) Trubetskoy
Why not refer people to the docs, just like it was done for 3.2? Otherwise this is yet another file to maintain. On Fri, 28 Oct 2005, Jim Gallacher wrote: Hi Grisha, Any objection if I split the "changes" from README to a new CHANGES file? Jim

Re: Move changes from README to CHANGES file

2005-10-28 Thread Jim Gallacher
Gregory (Grisha) Trubetskoy wrote: Why not refer people to the docs, just like it was done for 3.2? Otherwise this is yet another file to maintain. Couple of reasons. 1. I forgot to update the changes in Doc/appendixc.tex when I created the 3.2.3b tarball. I figure if it was right in front

Re: Field.file issue [was Re: mod_python 3.2.3b available for testing]

2005-10-28 Thread Jim Gallacher
Nick wrote: Jim Gallacher wrote: Are you sure there is anything to correct? In both cases, the object has the same methods available for manipulating files (t.write('a'), for example). They are not the same type of object, so they have different dir() output, but don't they have the same func

Re: Field.file issue [was Re: mod_python 3.2.3b available for testing]

2005-10-28 Thread Nick
Jim Gallacher wrote: How about this? (Excuse the LateX) \class{Field} instances have the following attributes: ... \begin{memberdesc}{file} This is a file-like object. For file uploads it points to a \class{TemporaryFile} instance. (For more information see TemporaryFile in the s