Jim Gallacher wrote:
Interestingly, section 5.1.1 says that The methods GET and HEAD MUST be
supported by all general-purpose servers., so it would seem that
mod_python has not been compliant to the RFC.
FWIW, the Debian Woody package of mod_python (libapache-mod-python
2.7.8-0.0woody5)
Juha-Matti Tapio wrote:
On Wed, Aug 10, 2005 at 09:04:04AM -0400, Jim Gallacher wrote:
Nicolas Lehuen wrote:
Having some contact with them directly is probably a good idea anyway.
Subscribing to a bunch of mailing lists could result in a lot of
uninteresting mail. ;)
I think it would be
Nicolas Lehuen wrote:
Hi,
Could we focus on Apache 2.0 for the 3.2 release ? Put 2.1 on the
agenda for a later release (why not 3.3 ?).
For the moment I don't see any quick and easy way to support both 2.0
and 2.1, from what you wrote. I'd rather we try to get 3.2 out with a
proper 2.0
+1 (slightly patched for Apache 2.1.x)
Slackware Linux 10.1
gcc version 3.3.4
Python 2.4.1
Apache 2.1.6 Alpha
Jim Gallacher wrote:
A new mod_python 3.2.2 beta tarball is now available for testing.
Hopefully this will be the last beta before the official 3.2 release.
Here are the rules:
In
Where do I file a documentation bug? Rule #6 appears to be missing. ;)
Sydney Nolan
Nick wrote:
In that case, let us just apply Rule #6 to this situation.
Bruce
Jim Gallacher wrote:
Well, this is python, so everyone really should be called Bruce. Maybe
that will help.
Regards,
Bruce
Jim Gallacher wrote:
Nick wrote:
More info:
python 2.4.2 on Linux:
import tempfile
t = tempfile.TemporaryFile()
t
open file 'fdopen', mode 'w+b' at 0xb7df07b8
type(t)
type 'file'
dir(t)
['__class__', '__delattr__', '__doc__', '__getattribute__',
'__hash__', '__init__', '__iter__',
Jim Gallacher wrote:
Gregory (Grisha) Trubetskoy wrote:
I don't know what the specific issue is with parsed_uri, if this is a
mod_python bug it should just be fixed BUT if this is an issue with
httpd, I don't think we should cover the problem up by having
mod_python fix it. Since we are
Nicolas Lehuen wrote:
Is there a wait to use macro directives so that we don't need to
maintain two separate branches ? A define that we could pass when
building mod_python to select the Apache version we're building against,
maybe ?
If it's possible to make the code in connobject.c
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?
Specifically, the SetInputFilter, SetOutputFilter, AddInputFilter and
+1 Slackware 10.1, Apache 2.0.55 (mpm-prefork), Python 2.4
Jim Gallacher wrote:
$ ./configure --with-apxs=/wherever/it/is
$ make
$ (su)
# make install
Then (as non-root user!)
$ cd test
$ python test.py
What are the chances of enhancing the procedure as follows:
$ ./configure
Mike Looijmans wrote:
Since I have a CoLinux instance on my machine here, I wanted to give it
a go with mod_python as well (need a linux test environment for
mod_python anyway).
It's running a Debian distro, I have gcc-3.3 on it, as well as
apache2-dev and python-dev (version 2.3).
Can't
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 task and testing and voting and preparing
Jim Gallacher wrote:
Jorey Bump wrote:
IOW, could you guys list the OS on which you run, and not merely test,
mod_python?
By you guys I assume you mean the above 4 people?
Yeah, youse 4 guys. :)
On the other hand, you may mean *all* the people on python-dev who test
a release candidate
Graham Dumpleton (JIRA) wrote:
On a virtual hosting environment such as OpenVPS, localhost does not map to the IP
address 127.0.0.1 but the actual IP of the host.
import socket
socket.gethostbyname(localhost)
'207.126.122.36'
This fact causes the connection handler test to fail
Jim Gallacher wrote:
The generated output can be found at
http://people.apache.org/~jgallacher/mod_python/website-test.
The only links that you should really trust are under the Get Involved
meun heading. There is likely all sorts of incorrect or missing content.
This is only intended as a
Gregory (Grisha) Trubetskoy wrote:
If you see any problems with this text, let me know.
-- Forwarded message --
Date: Sat, 12 Feb 2005 22:00:56 -0500 (EST)
From: Gregory (Grisha) Trubetskoy [EMAIL PROTECTED]
To: announce@httpd.apache.org, [EMAIL PROTECTED]
Cc:
+1
Graham Dumpleton wrote:
I have had patches for adding server side include support into
mod_python ready for a while now. See:
https://issues.apache.org/jira/browse/MODPYTHON-104
In short, it would add the ability to add Python code into files
being served up through the INCLUDES output
-1 Slackware 10.1, Apache 2.2.0 (mpm-prefork), Python 2.4
My applications are working, but make check produces these errors:
==
FAIL: test_req_auth_type (__main__.PerRequestTestCase)
+1
But I think any example functions in the documentation should return
apache.AUTH_DENIED by default, with the conditionals checking for
success, not failure:
def authbasicprovider(req, user, password):
if user in users:
if users[user] == password:
return
+1 Linux Slackware 10.1, Apache 2.0.55, Python 2.4.1
+1 Linux Slackware 10.2, Apache 2.2.0, Python 2.4.1
+1 Linux Zenwalk 2.6, Apache 2.2.2, Python 2.4.3
Jim Gallacher wrote:
The mod_python 3.2.9-rc3 tarball is available for testing. This release
adds support for apache 2.2 as well as some
Jim Gallacher wrote:
Mike Looijmans wrote:
I think this surprised many of us, as no one on the list seems to have
thought of that use case. Trac subclasses FieldStorage to get behaviour
more in line with cgi.py. We don't have any prohibitions on subclassing,
so although we didn't foresee this
Jim Gallacher wrote:
Graham Dumpleton wrote:
On 29/06/2006, at 9:29 PM, Jim Gallacher wrote:
+1 Linux Slackware 10.1, Apache 2.0.55, Python 2.4.1
+1 Linux Slackware 10.2, Apache 2.2.0, Python 2.4.1
+1 Linux Zenwalk 2.6, Apache 2.2.2, Python 2.4.3
These 3 were all prefork.
In respect of
Gregory (Grisha) Trubetskoy wrote:
(we'll just have to make a
3.2.11 then).
Let's call that one the Spinal Tap version. :)
+1 Linux Slackware 10.1, Apache 2.0.55 (mpm-prefork), Python 2.4.1
Jim Gallacher wrote:
The mod_python 3.2.10 tarball is available for testing.
Part way through the release process for 3.2.9 a fix was found for
several memory leaks (MODPYTHON-172). We've decided to skip the official
3.2.9
Graham Dumpleton wrote:
The only area I guess one may have to be careful with is if you have used
PythonPath directive to extend module search path, especially if you
reference directories in the document tree. This may result in mod_python
complaining in the Apache error log at you and in
Jim Gallacher wrote:
The mod_python 3.3-0-dev-20061109 tarball is available for testing.
As this is a minor version bump, is there a link to the changelog so we
know what new behaviour to expect/test?
Graham Dumpleton wrote:
There are two things you can do to gauge where any loss arises. First is to
ensure that module reloading is turned off and see how that changes things.
PythonAutoReload Off
The second is to reenable the old module importer as a comparison. This needs
to be done at
Jim Gallacher wrote:
Jorey Bump wrote:
I've installed it on a lightly used production server so I can test it
against some real-world apps. Initial testing indicates that it's
10-20% slower than 3.2.10; I'm not sure why.
Ouch. Is that from a benchmark or just a gut feeling?
It was from
Hi, Jim:
Jim Gallacher wrote:
The following page has been changed by JoreyBump:
http://wiki.apache.org/mod_python/MostMinimalRequestHandler
--
Let's begin at the beginning. Here is the most minimal request
It might be prudent to test against Apache 2.2.4, which was released two
days ago. I'll try to do this over the weekend and submit the results.
Jim Gallacher wrote:
We don't seem to be getting any more feedback on 3.3.0b (+1's across the
board), so how does everyone feel about rolling out
+1 Slackware Linux 10.2, Apache 2.2.3 (mpm-prefork), Python 2.4.1
Jim Gallacher wrote:
The mod_python 3.3.1 tarball is available for testing. Hopefully
Nicolas will have a chance to create Windows installers for testing in
the next couple of days.
There have been no changes in the code since
Gregory (Grisha) Trubetskoy wrote:
1. Python is not a good name for this project because Apache Python
will just be too confusing and probably infringes on a PSF trademark. So
if you have any creative suggestions, send them in, don't be shy, even
if you think they may sound a little stupid at
Mike Looijmans wrote:
Apache includes a feather in its logo, and Python is associated with a
snake. Quetzalcoatl means feathered snake and does not appear to
be used by any other software project.
Which I can fully understand, because Quetzalcoatl is harder to
pronounce than the 16 character
For me, it's a tie between Quetzalcoatl Scales.
Gregory (Grisha) Trubetskoy wrote:
So I think we've got (in no particular order):
PythonScript
Pythonidae
PyPache
pythonalia
Quetzalcoatl
Asphyxia
Scales
Pythonistas
PigeonPy
Pungi
Would people (ANYONE here on the list, yes, that includes
34 matches
Mail list logo
