Martin Stoufer wrote:
Jim Gallacher wrote:
Apache Wiki wrote:
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Mod_python
Wiki for change notification.
The following page has been changed by MartinStoufer:
The comment on the change is:
A good start.
Once you understand this framework, you can then add your own
- First, lets augment a directory element in the ''httpd.conf'' to
enable session support.
+ First, lets augment a directory element in the ''httpd.conf'' to
enable both the Publisher model and session support.
+ PythonOption session MemorySession
I'm not sure about the most elegant way to handle this in the wiki,
but we likely need to make the reader aware of differences between
Using this PythonOption session as an example, we actually have 3
PythonOption session is not used. When calling Session.Session(req)
you get the default session type for your platform: DbmSession with
the prefork-mpm and worker-mpm, MemorySession with the winnt-mpm.
PythonOption session was introduced to allow the default session
type to be overridden at run time.
Version 3.3 (real soon now)
We started using PythonOption much more heavily in 3.2 to control the
run time configuration of mod_python. It quickly became apparent that
the potential for key conflicts with user code was rather high, so for
3.3 we adopted a new PythonOption namespace. Thus PythonOption
session has been deprecated in favour of PythonOption
So my question is How do we handle this in general?. At the very
least any of the Wiki authors should note which version of mod_python
they used when creating their examples.
I honestly didn't even think of this. As I started with v.3.2, my
example would of ended up being rather myopic in scope. My suggestion
for the time being is to split my page up into SubPages; one per
version. Adding these disclaimers (or sanitized versions that don't
disclose and secrets/non-finalized ideas) at the top will help alot.
Since I don't have any examples from 3.1.4 or 3.3, I will put a call out
to the list and see if anyone is willing to post some small examples.
I wouldn't create separate pages just yet. My guess is that your actual
code will be compatible across versions 3.1 to 3.3 as the session api
has not changed so your usage will be the same. Version = 3.2 just
gives some flexibility in the session configuration through a bunch of
I think Graham's suggestion is best - avoid the problem all together by
not using PythonOption session in your configuration. :) On the other
hand being able to set the session timeout and some other options in the
apache configuration is pretty handy so you might want to mention them.
I've appended the relevant 3.3 PythonOptions to bottom of the this email
for your reference.
Also, I wouldn't worry too much about 3.1.4 support. It's getting pretty
long in the tooth.
As for how to deal with this issue at the wiki-wide level, I am very
hesitant to promote a required style guide on pages that discuss topics
that vary across releases. Those looking to post a quick nugget of
valuable info won't if the process requires too much effort. It may well
suffice by having a minimal requirement that posters say upfront what
version(s) their examples/info is valid for.
Some sort of detailed style guide is likely not realistic, but I suspect
if new authors always see the same sort of boiler plate at the beginning
of each example they'll take the hint. Something simple like Works with
version 3.x.x may be sufficient. If someone comes along and tries it
with a different version it'll be easy enough for them to amend that to
Works with version 3.1, 3.2.
Version 3.3 PythonOption reserved keywords
mod_python.legacy.importer * - Enables the obsolete importer.
session - Deprecated, use mod_python.session.session_type