Graham Dumpleton wrote:
On 12/02/2006, at 2:40 PM, Jim Gallacher wrote:
Graham Dumpleton wrote:
get_directories could have several meanings in the context of a
request. Would req.get_module_directories() be a better alternative?
Does that capture the concept that you are trying to achie
Justin Erenkrantz wrote:
On 2/11/06, Jim Gallacher <[EMAIL PROTECTED]> wrote:
No, I was not aware that it is auto-generated, but I'm hardly suprised.
:) The point was mostly to kick off a discussion.
The point is that you needn't muck with HTML directly and can focus on
the content instead.
On 2/12/06, Jim Gallacher <[EMAIL PROTECTED]> wrote:
> If we decide this is the route we want to take I'll commit the files to
> my svn sandbox and we can get to work on the content.
Looks good. +1. -- justin
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
I don't at all mean to sound confrontational, but would simple xml + xsl
be a bit easier to implement? If we're just going to have a few pages,
a simple shell script could loop thru them calling xsltproc. Then
again, I'm a fan of using simple tools for simple needs?
Here's an example of document
John McFarlane wrote:
I don't at all mean to sound confrontational, but would simple xml + xsl
be a bit easier to implement? If we're just going to have a few pages,
a simple shell script could loop thru them calling xsltproc. Then
again, I'm a fan of using simple tools for simple needs?
No,
Yes, I was thinking in fact to use the same xml structure/schema :)
Let me mock up something tomorrow which might provide a better feel for
how an alternate approach might feel... I'll use the same xml files.
I'll report back :)
John M.
Jim Gallacher wrote:
> John McFar
HandlerDispatch doesn't treat OK/DECLINED result properly for all phases.
-
Key: MODPYTHON-129
URL: http://issues.apache.org/jira/browse/MODPYTHON-129
Project: mod_python
Type: Bug
Components:
[ http://issues.apache.org/jira/browse/MODPYTHON-129?page=all ]
Graham Dumpleton updated MODPYTHON-129:
---
Description:
Todays daily bug report, or is it? ;-)
The Python*Handler documentation says:
"""Multiple handlers can be specified on a single
[
http://issues.apache.org/jira/browse/MODPYTHON-129?page=comments#action_12366149
]
Graham Dumpleton commented on MODPYTHON-129:
Content handlers also seem to work differently in mod_python than Apache itself
when using C handlers or even mod_
Improvements associated with modifications times.
-
Key: MODPYTHON-130
URL: http://issues.apache.org/jira/browse/MODPYTHON-130
Project: mod_python
Type: Improvement
Components: core
Versions: 3.3
Reporte
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
Oh and if we are refactoring the tests, I want a "make tests" rule. I'm
tired of doing: ./configure; make; sudo make install; make tests; DOH!
cd test; python test.py. :)
Make that "make check" (like autotools), to not confuse old-skool
autoconfers like myself.
13 matches
Mail list logo
