2005/6/8, Graham Dumpleton <[EMAIL PROTECTED]>:
> > c) the apache.import_module() function, which is frankly a strange
> > beast. It knows how to approximately reload some modules, but has many
> > tricks that makes it frankly dangerous, namely the one that causes
> > modules with the same name but
Gregory (Grisha) Trubetskoy wrote:
On Tue, 7 Jun 2005, Jim Gallacher wrote:
What's the mechanism for this, since the generated docs are not in
subversion?
The docs _are_ in subversion, but in .tex format. The html is included
in the distribution tar file for convenience, but I don't think
On Tue, 7 Jun 2005, Barry Pearce wrote:
I'm not opposed to providing some sort of module or function for psp or
publisher or whatever "example" handlers that come with mod_python, just
so long as it's not in the core of mod_python itself. To me this is an
application/framework issue, not a m
On Tue, 7 Jun 2005, Jim Gallacher wrote:
What's the mechanism for this, since the generated docs are not in
subversion?
The docs _are_ in subversion, but in .tex format. The html is included in
the distribution tar file for convenience, but I don't think it'd make
sense to have both tex and
On 08/06/2005, at 7:19 AM, Jim Gallacher wrote:
MODPYTHON-37
Add apache.register_cleanup()
According to the FAQ entry linked by Graham, this probably can't
be done, so change it's status to closed?
Actually, I still believe it can be done, but from memory Grisha
expressed
reservations a
An update on a few things that I have managed to get working in
Vampire in respect of some of the issues below, plus a few other
comments.
On 08/06/2005, at 6:33 AM, Nicolas Lehuen wrote:
One last thing that we should prepare is a clear and definite answer
to the zillion users who need to impor
On 08/06/2005, at 8:33 AM, Barry Pearce wrote:
Indeed Im for fixing it...its on my list of things to do...right after
'do everything the company want RSN'
I do believe it should be mod_python that is fixed. I have a VERY big
need for reload of modules *without* taking down my server - en
Hi All,
Sorry for the long post, but I think I have a nice contribution to the
session handling mechanism, but I've got a bug I just can't track down.
Make yourself a cup of coffee, sit down and have a read.
In an effort to make session handling more transparent and less error
prone, I've ad
Indeed Im for fixing it...its on my list of things to do...right after
'do everything the company want RSN'
I do believe it should be mod_python that is fixed. I have a VERY big
need for reload of modules *without* taking down my server - end users
are using it and credit card transactions
On Tue, 7 Jun 2005, Nicolas Lehuen wrote:
Grisha, can you tell us what is the process to release a new version,
including the update of the web site ?
Updating the site is trivial, I can do it, that's the last thing to worry
about. Releasing a new version is a bit more complicated.
The ins
2005/6/7, Jim Gallacher <[EMAIL PROTECTED]>:
> Nicolas Lehuen wrote:
> > Grisha, can you tell us what is the process to release a new version,
> > including the update of the web site ?
> >
> > Maybe include the web site source files in the subversion repository,
> > so that we can edit it ?
> >
>
One last thing that we should prepare is a clear and definite answer
to the zillion users who need to import a custom utility module.
Today, we have 4 ways of importing code :
a) the standard "import" keyword. Today, it works unchanged
(mod_python doesn't install any import hook). The consequence
Nicolas Lehuen wrote:
Grisha, can you tell us what is the process to release a new version,
including the update of the web site ?
Maybe include the web site source files in the subversion repository,
so that we can edit it ?
As for building the HTML documentation out of the LaTeX files, I'm a
I'd especially like to have your advice (do not hesitate to be harsh
:) on the new publisher module loading system.
It does not uses apache.import_module, and fixes a lot of nasty bugs.
However, the new system means that standard Python modules and
published pages are not the same things anymore.
As you can see on
http://issues.apache.org/jira/secure/BrowseProject.jspa , there are
only two bugs still scheduled for 3.2.0 ; the rest is not scheduled.
Should we schedule all bugs for 3.2.0 and only release it once all the
bugs are released, or could we make an intermediary release ? I'm in
fav
Grisha, can you tell us what is the process to release a new version,
including the update of the web site ?
Maybe include the web site source files in the subversion repository,
so that we can edit it ?
As for building the HTML documentation out of the LaTeX files, I'm a
bit at a loss... Has an
Hi folks -
We have a new committer - Jim Gallacher. Thanks Jim for all your
contributions to mod_python and for accepting the invitation to become a
committer!
Cheers,
Grisha
17 matches
Mail list logo
