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
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(""
out that idea.
> Mike Looijmans
> Philips Natlab / Topic Automation
>
>
> Graham Dumpleton wrote:
> > Mike, I have a feeling that Apache has ways of generating those date/time
> > strings for last modified for you. Thus, the routine shouldn't be required.
>
My only comment is that, especially if tests are being split into
separate files, that the access/error log files be distinct for each
test with a name incorporating the name of the test. I always
found it a pain to try and dig through a big log of multiple tests
trying to work out which was the o
On 11/02/2006, at 7:22 AM, Daniel J. Popowich wrote:
Gregory (Grisha) Trubetskoy writes:
On Thu, 9 Feb 2006, Jim Gallacher wrote:
Depending on Grisha's preference, I think we should either put the
content in svn and have a cron job on modpython.org do a nightly
update,
or start using the
I know the subject line doesn't mean much, but I want to outline an
idea I have for an addition to mod_python which would help solve
a few problems. The mail is likely to be long, but if people can
understand
what I am going on about, I would appreciate some feedback.
Some background informati
On 12/02/2006, at 2:40 PM, Jim Gallacher wrote:
Graham Dumpleton wrote:
Thus we come to my actual idea that I want some feedback on.
The idea is to provide a new directive in mod_python that allows
you to mark
an arbitrary point in the directory hierarchy as a context point
or base
As Jim pointed out a while back, we need to get going on mod_python 3.3
before I fill up JIRA with another page of bug reports or suggestions.
That said, how do we want to proceed on this? Do we want to draw up an
initial list of things to do with priorities, discuss them to make sure
all are okay
Jim Gallacher wrote ..
> Jorey Bump wrote:
> > Jim Gallacher wrote:
> >
> >> This is how I would set priorities:
> >
> >
> >> Try and assign most of the issues to someone. This is a bit of PR
> >> spin, but I think it looks bad when there are a large number of open
> >> issues with no assignee.
Grisha wrote ..
>
> On Tue, 14 Feb 2006, Nicolas Lehuen wrote:
>
> > 2006/2/14, Graham Dumpleton <[EMAIL PROTECTED]>:
> > [...]
> >> If we want to go down the path of having interim 3.2 bug rollup releases
> >> while 3.3 is being developed, might I
Grisha wrote ..
>
> On Tue, 14 Feb 2006, Jim Gallacher wrote:
>
> > I wonder if we should generalize this, so rather than PythonMutexDir,
> we have
> > PythonModuleConfig. Usage might look like:
> >
> > PythonModuleConfig mutex_dir /path/to/mutexs
> > PythonModuleConfig max_mutex_locks 8
>
> I
to
> release this in a month or two (given that the Win32 source code is
> not even available right now).
>
> Regards,
> Nicolas
>
> 2006/2/14, Nicolas Lehuen <[EMAIL PROTECTED]>:
> > 2006/2/14, Graham Dumpleton <[EMAIL PROTECTED]>:
> > [...]
&g
Jim Gallacher wrote ..
> Graham Dumpleton wrote:
> > Is my list of suggested JIRA items then seen as being reasonable for
> > such a projected release?
>
> This seems reasonable, since we have either already committed the fixes
> or have patches available (I think).
I
Hmmm, somehow I managed to vapourise an email, didn't even get
to my sent mail box. Let me try this again.
Jim Gallacher wrote ..
> Graham Dumpleton wrote:
> > Correct, is actually done from the mod_python module init function.
> >
> > The only way one could have
On 15/02/2006, at 5:29 PM, Nicolas Lehuen wrote:
Hi,
I've built Apache 2.2 and tested mod_python SVN trunk with it.
The two register_cleanup tests fail. Apparently it's because the test
code registers a cleanup function giving the current request as
parameter. Of course when the cleanup funct
I have already noted that apache.register_cleanup() and
req.server.register_cleanup() are prone to failure. The problem
is that they are run in the context of a signal handler. See:
http://issues.apache.org/jira/browse/MODPYTHON-109
I suggested in the JIRA issue that these functions may need t
Jim Gallacher wrote ..
> > If the settings are going to be a generic key/value like in
> > PythonOption, but only for purposes of the mod_python system itself,
> > maybe it should be called PythonSystemOption. Prefer PythonSystemOption
> > as "Module" is too confusing to me given you have both Apac
Jim Gallacher wrote ..
> > I have a better option (pun intended). :-)
> >
> > We do not need a new directive. Instead use existing "PythonOption"
> > directive.
>
> That could work.
>
> > In the handler code for the directive, it can look at the
> > value of the "cmd_parms->path" and determine i
Graham Dumpleton wrote ..
> > How does req.server.get_options() differ from req.server.get_config(),
> > which already exists?
>
> I still see what is in get_config() as special, ie., the values for
> actual directives. Just don't think it is good to mix them.
Lo
Graham Dumpleton wrote ..
> Graham Dumpleton wrote ..
> > > How does req.server.get_options() differ from req.server.get_config(),
> > > which already exists?
> >
> > I still see what is in get_config() as special, ie., the values for
> > actual directives.
Just sending this while I remember ...
A while back there was long discussion on constructing a URL for
location
redirect. While digging through Apache stuff, I stumbled across the
function:
ap_construct_url()
This takes an absolute path and constructs a full URL based on
information
Daniel J. Popowich wrote ..
>
> Graham Dumpleton (JIRA) writes:
> > If mod_python is to still support Python 2.2, which it looks like we
> > are still because of Nokia work, then can't use the Python bool type
> > yet as that was only added to Python 2.3.
>
&g
On 17/02/2006, at 10:01 AM, Jim Gallacher wrote:
The ap_check_cmd_context function may also be of interest.
http://docx.webperf.org/group__ap__check__cmd__context.html
For example, lets say we wanted to disallow the use of PythonDebug
in
const char *err;
if ((err = ap_check_cmd_con
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
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
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
but I think this is a big enough change that we need to
either jump the version to 4.0 or offer an easy transition path.
Jim
Deron Meranda wrote:
On 2/17/06, Graham Dumpleton <[EMAIL PROTECTED]> wrote:
When you get a chance, can you read through the JIRA issue:
http://issues.apach
On 19/02/2006, at 9:35 AM, Jim Gallacher wrote:
I just noticed that "write" is declared twice in request_methods
[] . What's up with that??
src/requestobject.c
static PyMethodDef request_methods[] = {
...
... line 1075
{"write", (PyCFunction) req_write, METH_VARARGS
I already fixed the test and checked it in. :-)
On 20/02/2006, at 5:15 AM, Jim Gallacher wrote:
Yes, this test seems to be broken. I'll create a JIRA issue for it.
We need unit tests for the unit tests. :)
Jim
For my WTF moment, have a look at test_req_get_basic_auth_pw in the
test suite. I
ng the revision may be helpful when someone
wants to perhaps backport changes to an older version. This may be us,
or someone who needs to do it for themselves.
Graham
> Graham Dumpleton (JIRA) wrote:
> > [
> > http://issues.apache.org/jira/browse/MODPYTHON-124?page=comment
Jim Gallacher wrote ..
> Jim Gallacher wrote:
> > Now that 3.2.7 is out, should we be changing the status resolved issues
> > to closed in JIRA.
If that is what closed implies. Is there somewhere which states what we
should interprete the different status as meaning? I don't recollect seeing
anyth
Jim Gallacher wrote ..
> >>Other JIRA thoughts:
> >>
> >>Should we have a "unit test" component for bugs in the actual unit test
> >>code?
> >>
> >>Since we plan on having 3.2.x bugfix releases, should create new JIRA
> >>versions starting with 3.2.7?
> >
> >
> > No harm in doing so. Probably wou
Jim Gallacher wrote ..
> All very interesting, except that JIRA does record the svn commit info,
> and with great detail. It just doesn't treat the commit as a comment.
>
> For example:
> http://issues.apache.org/jira/browse/MODPYTHON-124?page=all
>
> Personally I think the Subversion commit info
Jim Gallacher wrote ..
> I don't have alot more to say on these last 2 emails. I think you are on
> the right path here.
Okay, I think I have a good plan now.
To summarise the whole issue, the way Apache treats multiple handlers in
a single phase for non content handler phases is as follows:
P
+1 core vote
Nicolas Lehuen wrote ..
> +1 core vote
>
> 2006/2/20, Jim Gallacher <[EMAIL PROTECTED]>:
> > +1 core vote
> >
> > Jim
> >
> > Gregory (Grisha) Trubetskoy wrote:
> > >
> > > Based on summary below, +1 from for pu
On 21/02/2006, at 7:08 AM, Jim Gallacher wrote:
The Apache 2.2 support will likely go into the 3.2.9 bugfix release.
We just wanted to get the security problem out of the way first.
Jim, if we are again going to aim for a bug rollup release for 3.2.9
do I
need to stop or hold off on doing a
t is created and put in req.session. This is a lot cleaner
than what most people do, which is to put a call to the session manager
code in every single published function.
Graham
> On Tue, 21 Feb 2006, Jim Gallacher wrote:
>
> > Nice summary.
> > +1 for the change.
> >
Jim Gallacher wrote ..
> Justin Erenkrantz wrote:
> > On 2/19/06, Jim Gallacher <[EMAIL PROTECTED]> wrote:
> >
> >>I just notice that a few files still say that mod_python uses Apache
> >>License 1.1 (eg htdocs/tests.py, src/psp_string.c). Can I assume this
> is
> >>an error and that *everything*
On 26/02/2006, at 5:58 AM, Jim Gallacher wrote:
Since we are discussing Python*Filter, can someone explain why it
is only allowed in the server config context, whereas
SetInputFilter and related directives are allowed in any context?
Is this a mod_python feature or a bug, or is it just the
One of the problems when I am looking at making changes to mod_python
is knowing that there is some consensus that changes are a good
thing, or
at least that there is no objection.
So far if a change was trivial, I would commit it without
consultation. I have
also committed some changes whi
On 20/02/2006, at 4:22 AM, Jim Gallacher wrote:
I just notice that a few files still say that mod_python uses
Apache License 1.1 (eg htdocs/tests.py, src/psp_string.c). Can I
assume this is an error and that *everything* should be version 2.0?
Jim, I think you managed to delete the Copyrig
Jim Gallacher wrote ..
> > https://issues.apache.org/jira/browse/MODPYTHON-104
> > Allow Python code callouts with mod_include (SSI).
>
> The unit test fails for the applied patch. It looks like it's missing
> LoadModule in the config section. I've attached a patch. I'd attach it
> to the i
On 04/03/2006, at 4:59 AM, Jim Gallacher wrote:
More in the way of a general observation rather than on these
specific issues, but I wouldn't necessarily mark things as resolved
just on the basis of the fix being committed. For the big changes
at least, I think we should see some testing
On 04/03/2006, at 4:59 AM, Jim Gallacher wrote:
More in the way of a general observation rather than on these
specific issues, but I wouldn't necessarily mark things as resolved
just on the basis of the fix being committed. For the big changes
at least, I think we should see some testing on
On 05/03/2006, at 12:55 PM, Graham Dumpleton wrote:
Although changing the workflow to add new status values is
interesting, in reality
not sure this could be done as workflow is probably global across
all projects.
Actually, if want to get that pedantic and formalised, it does look
like
A bit more information. This may actually be a problem with the "ab"
tool
used for this test. I have actually seen the "ab" program give
problems on
Mac OS X before even with Apache 2.0.
On 06/03/2006, at 9:02 PM, Graham Dumpleton wrote:
Traceback (most recent call la
ates to:
#define EBADF 9 /* Bad file descriptor */
Maybe when I am really bored I'll pursue further as to why.
Graham
On 06/03/2006, at 10:27 PM, Graham Dumpleton wrote:
Don't even need to rewrite test to use threads to fire off
requests. If
I hardwire test to use
Nicolas
A while back you made the following change:
r378072 | nlehuen | 2006-02-16 06:41:25 +1100 (Thu, 16 Feb 2006) | 5
lines
- Fixed the unit tests for apache.register_cleanup
server.register_cleanup. Ther
e is not way it could have passed before, yet it did ???
- Corrected the documentat
yway, I'll fix this all up as am going to do some stuff to fix at
least
the Py_Finalize() issue anyway, so working in related code.
Graham
On 08/03/2006, at 8:50 PM, Graham Dumpleton wrote:
Nicolas
A while back you made the following change:
r378072 | nlehuen | 2006-02-16 06:
Jim Gallacher (JIRA) wrote ..
> I think part of the problem with process_auth() is the uncertainty of meaning
> associated with auth and __auth__. Does it mean authenticate or authorize?
> If it's authorize, then there is no reason to call __auth__ with the password.
> Likewise, you shouldn't need
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 filter. More
commonly this is kn
This bit is going to change anyway when I add the PythonOption
mod_python.mutex_directory support. I have the changes ready, but I
think I'll review them in the morning rather than committing now.
I decide to do this stuff in 2 steps:
1. configure option
2. PythonOption mod_python.mutex_dir
I would rather we not go ahead with adding req.get_session() at
this time. At least not how it was envisaged to be done previously.
I'll come back with a bit of analysis after I review where we were
up to previously.
Graham
On 12/03/2006, at 8:47 AM, Jim Gallacher (JIRA) wrote:
[ http://
URL: http://issues.apache.org/jira/browse/MODPYTHON-131
Project: mod_python
Type: Improvement
Components: core
Versions: 3.2.7
Reporter: Graham Dumpleton
Assignee: Jim Gallacher
Fix For: 3.3
Creating an issue for this so it can be tracked.
Been pointed
m getting thick with age).
I think it'd be great if those who send in +1's (or -1's) would
explain why they think this is good, and even if it's not so useful,
then is it worth being supported and maintained in the future.
Grisha
On Fri, 10 Mar 2006, Jim Gallacher wrote:
On 12/03/2006, at 8:25 PM, André Malo wrote:
* Graham Dumpleton wrote:
Not seeing any negatives, I am going to go ahead and commit the SSI
stuff. Comments that this is just another way to skin a cat are true,
even if a small cat. I guess the reason for doing it is to fill out
those basic
On 12/03/2006, at 9:04 PM, Graham Dumpleton wrote:
On 12/03/2006, at 8:25 PM, André Malo wrote:
* Graham Dumpleton wrote:
Not seeing any negatives, I am going to go ahead and commit the SSI
stuff. Comments that this is just another way to skin a cat are true,
even if a small cat. I guess
's a gentle reminder when I list my assigned issues -
resolve it one way or another.
I still think we need some sort of solution to the problem of people
trying to create 2 session instances in the same request, but I agree
that the original concept of req.get_session() was not quite right.
Grisha wrote ..
>
> On Mon, 13 Mar 2006, Graham Dumpleton wrote:
>
> > Thus I want a documented convention that if a handler is going to use
> > util.FieldStorage, that it should before doing so, first check whether
> > an existing instance resides as req.form and use
Jim Gallacher wrote ..
> The idea of something like req.get_session() is to give users an obvious
> way to grab a session object without the deadlock concerns. How many
> times have we seen this kind of problem-code on the mailing list?
>
> def index(req):
> sess = Session.Session(req)
>
Jim Gallacher wrote ..
> Which is all good, but you are assuming that people are only using
> sessions for authentication purposes. Consider a shopping cart
> implemented as session: the user may not be authenticated until *after*
> they have filled their cart and are ready to checkout. Perhaps
On 15/03/2006, at 8:45 AM, Gregory (Grisha) Trubetskoy wrote:
Could folks with access to different OS's try the following:
Compare output of "apxs -q CPPFLAGS" with the value of
_FILE_OFFSET_BITS in pyconfig.h.
For example, on my Fedora Core 4 i386 system (stock httpd and python):
$ /usr
On 14/03/2006, at 7:33 PM, André Malo wrote:
* Graham Dumpleton <[EMAIL PROTECTED]> wrote:
Do you have examples of SSI tag handlers that you might implement
this
way if such a feature were available? I ask as it all good to
speculate
on such a feature, but like this generic "#
I know this is the wrong list to be asking this, but thought I
would ask before I go and get my self subscribed to some Apache
server list just to ask the question as I know some more involved
in Apache core lurk here. :-)
I have been looking at a way of solving:
https://issues.apache.org/jira
Following may or may not be relevant.
BTW, have you tried your sample code outside of context of mod_python.
Ie., extract out main bit and run it as command line script.
Patty wrote ..
> This is the piece of code:
>
> # Connect to the database
> conn = MySQLdb.connect(host = "localhost", user =
complain the file already exists as a non versioned file.
You will need to remove the file before doing "svn update".
Graham
On 17/03/2006, at 3:17 PM, Graham Dumpleton (JIRA) wrote:
[ http://issues.apache.org/jira/browse/MODPYTHON-118?page=all ]
Grah
On 14/03/2006, at 12:23 PM, Jim Gallacher wrote:
I find I work more effectively when I have deadlines to worry about
(being a procrastinator by nature), so I thought I'd propose the
following roadmap.
Mar 20: 3.3-dev - snapshot for testing
Apr 1: 3.2.9 - bugfix release
May 1: 3.3-dev
Now can you explain why one would want to do this?
Unless you provide some justification of why it is necessary it is
less likely
to be accepted as although the reasons may be obvious to you, it may not
be to us. There also may be better ways of achieving the same end.
Also, describe why this
Firat KUCUK wrote ..
> Hi,
>
> i have a little problem about Directory Index.
>
> this is our .htaccess file:
>
> Allow from All
>
> AddHandler mod_python .py
> PythonHandlerwepy.handler
> PythonDebug On
>
> DirectoryIndex index.htm index.html index.php index.py index.pl
input
parameter.
Thus, there wouldn't need to be a reason for a specific Python option
to disable writing of cookie.
So, can you explain what the original problem is you are trying to
solve. On first appearances, your solution would seem to be going
about it the wrong way.
A question for oth
Firat KUCUK wrote ..
> Graham Dumpleton yazmýþ:
> >What is the actual problem you are trying to solve?
> >
> >The "len(req.path_info) > 0" is actually redundant because when
> >req.path_info is a string and has length 0, the "req.path_info"
> &
Nicolas Lehuen wrote ..
> 2006/3/22, Nicolas Lehuen <[EMAIL PROTECTED]>:
> > However I have a -1 on Python 2.2 with a LOT of test failures, but I
> > guess we won't support Python 2.2 for mod_python 3.3 ?
>
> Sorry, my -1 was due to a configuration problem, everything works on Python
> 2.2.
>
> +
Graham Dumpleton wrote ..
>
> On 23/03/2006, at 5:06 AM, Jim Gallacher wrote:
> > That's another reason to rewrite the unit tests. It's too hard to
> > sort out the wheat from the chaff.
> >
> > I don't think this is related to your failing test
Now the mailing list is a bit quiet, I would like to see if I can get
some explicit feedback on some issues related to the inability to update
the req.finfo attribute.
Grisha, would be nice if you could respond on this issue and give some
guidance else I fear I'll never be able to progress a solu
mod_python
> rather
> > than its "apache-ness", and most would never notice if we deviate slightly
> > from the apache C api. Adding a method or attribute to the request object
> for
> > example, if it's useful to *our* users, shouldn't be rejected out of
> han
In:
http://issues.apache.org/jira/browse/MODPYTHON-117
I describe the idea of having a means of using PythonImport to define a
module to be imported into any interpreter that may be created. For some
cases where there are a lot of virtual hosts, this may be simpler than
having to list a directi
Nicolas
Are you okay with:
http://issues.apache.org/jira/browse/MODPYTHON-81
Pickling/unpickling top-level functions defined in published
module no longer works in mod_python 3.2
being resolved as "Won't Fix" and then closed?
As I describe in:
http://www.dscpl.com.au/articles/modpytho
Grisha wrote ..
>
> On Sun, 26 Mar 2006, Graham Dumpleton wrote:
>
> > One use for it that I already have is to get around the DirectoryIndex
> > problems in mod_python caused by Apache's use of the
> > ap_internal_fast_redirect() function to implement that fea
As pointed out by someone else, it is probably a versioning issue
with expat.
See the following article for how to debug which versions of expat
are being
used and thus whether there might be a conflict.
http://www.dscpl.com.au/articles/modpython-006.html
Graham
On 30/03/2006, at 9:00 PM,
FWIW, mod_python (from subversion) passes all tests with the Apache
2.2.1
release candidate on Mac OS X 10.4.
Previously the test_global_lock test failed with Apache 2.2.0 because
of a
bug in the APR library on Mac OS X. Apache 2.2.1 has newer version of
APR library which fixes problem.
Gra
I have just added to mod_python in subversion a req.discard_request_body()
method. This is a direct wrapper for underlying ap_discard_request_body()
function in C API.
The purpose of the underlying function is as described in documentation
attached to prorotype in headers.
/**
* In HTTP/1.1, an
On 03/04/2006, at 4:53 PM, Mike Looijmans wrote:
My question is, should mod_python.publisher and mod_python.psp be
enhanced and call req.discard_request_body() for a GET request to
avoid
the posibilities of any problems arising due to a client sending
content
for a GET request?
-1 on tha
With FieldStorage being discussed on main user mailing list, came across
this old post of the mailing list:
http://www.modpython.org/pipermail/mod_python/2001-November/012256.html
What it is saying is that some HTTP clients use multi line headers in sections
of multipart/form postings and that
Graham Dumpleton wrote ..
> Jim Gallacher wrote ..
> > WRT to 3.2.9, I've been bogged down with other stuff and will likely
> be
> > fairly busy this week as well. How be we aim for a release somewhere
> > around April 22? I'd like to sort out why the apac
Is there any of these you would like me to do, perhaps 77, 94 or 137
since I am familiar with the code?
Not knowing what you are up to, wary of just going ahead and doing
any in case you are already doing it.
Any hints on how to use subversion to merge diff automatically from
the other branch?
On 11/04/2006, at 12:47 PM, Jim Gallacher wrote:
Here is the list of things I still need to backport. Fixes have
already been committed to trunk.
MODPYTHON-77
The Simplified GIL Aquisition patches.
Jim, you must be coding in your sleep and thus not knowing what you are
doing as MODPYTHON
On 11/04/2006, at 12:47 PM, Jim Gallacher wrote:
Here is the list of things I still need to backport. Fixes have
already been committed to trunk.
MODPYTHON-77
The Simplified GIL Aquisition patches.
Was already done.
MODPYTHON-94
Support for optional mod_ssl functions on request obje
On 13/04/2006, at 5:26 AM, Firat KUCUK wrote:
Hi,
i wrote a simple connection script.
It works as a command line script or cgi script.
But does not work in mod_python.
import MySQLdb
conn = MySQLdb.connect(
host = '127.0.0.1',
user = 'pismikrop',
passwd = 'pas
Nicolas Lehuen wrote ..
> Just as a note, I'm still struggling with Apache 2.2 to make the test suite
> run with the latest svn version (everything seems OK with Apache 2.0.55).
>
> I still have a problem while testing req.auth_type(). It looks like the
> authentication system was changed in Apac
Graham Dumpleton wrote ..
> What is interesting now is that when doing that, I note that on Mac OS
> X there are some worrying error messages which follow that:
>
> [Thu Apr 13 11:09:37 2006] [error] Internal error: pcfg_openfile() called
> with NULL filename
> [Thu Apr 13 11:
Apache doesn't probably run as any of the users which your database
allows access to. Add lines in your CGI which says:
import os
print os.getuid()
and then see what user that UID actually is and give it access. User
may be something like "apache", "www", "wwwroot" or possibly even
"nobody" d
. :-(
Someone who knows what they are talking about should step in
and save me now. :-)
Graham
Graham Dumpleton wrote ..
> Apache doesn't probably run as any of the users which your database
> allows access to. Add lines in your CGI which says:
>
> import os
> print os.getuid
handler which made use of such features.
Let me know if things look better and I will back port req_requires
changes to 3.2.x branch.
Thanks.
Graham
Graham Dumpleton wrote ..
> Graham Dumpleton wrote ..
> > What is interesting now is that when doing that, I note that on Mac OS
> > X
The util.FieldStorage class, plus parse_qs and parse_qsl functions
take a
parameter called strict_parsing. All the documentation says is:
The \var{strict_parsing} argument is not yet implemented.
Ie., it doesn't even say what it is meant to be for.
Does anyone know what it is meant to be fo
On 13/04/2006, at 8:33 PM, Firat KUCUK wrote:
i think it is related with:
http://www.modpython.org/FAQ/faqw.py?req=show&file=faq02.013.htp
but i didn't understand.
If that is the case, it is easy to check. This is done by disabling
the loading
into Apache of PHP support. If after commenti
On 12/04/2006, at 10:13 PM, Graham Dumpleton wrote:
On 11/04/2006, at 12:47 PM, Jim Gallacher wrote:
MODPYTHON-93
Improved FieldStorage
Not yet done.
Also haven't done logging additions listed under MODPYTHON-158.
Now also both done.
At this point, if there is anything else
On 13/04/2006, at 9:30 PM, Firat KUCUK wrote:
Hi Guys,
php5 uses libmysqlclient12 as default
i made symbolic link like this:
ln -s libmysqlclient.so.14.0.0 libmysqlclient.so.12
problem fixed.
I would strongly recommend against doing this as any difference in
the API or object
layouts wil
I am sure I asked this a long time ago, but have forgotten all the
details.
On Win32 systems does req.filename set by Apache always use POSIX
style forward slashes, ie., '/', to separate components of a
directory? Thus:
/some/path
How does Apache indicate a drive letter when one is neces
C:/apache22/htdocs/index.html
So req.filename seems always normalized while req.hlist.directory
reflects what was entered in the Directory tag. Both POSIX and
Windows forms are allowed, unfortunately, but the backslash forms
needs C-style escaping, and IIRC the Apache documentation
recommends us
On 20/04/2006, at 12:39 AM, Jim Gallacher wrote:
[EMAIL PROTECTED] wrote:
Author: grahamd
Date: Sun Apr 16 03:49:39 2006
New Revision: 394455
> URL: http://svn.apache.org/viewcvs?rev=394455&view=rev
+1 Debian Sid, apache 2.2.0, python 2.4.2
-1 Debian Sid, apache 2.0.55, python 2.3.5
Compil
1 - 100 of 1069 matches
Mail list logo
