You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mod_python-dev@quetz.apache.org by Greg Stein <gs...@lyra.org> on 2003/08/14 21:29:30 UTC
automated snapshots (was: Status)
On Thu, Aug 14, 2003 at 11:42:08AM -0400, Gregory (Grisha) Trubetskoy wrote:
>
> I just added another snapshot
>
> http://www.modpython.org/tmp/httpd-python-20030814.tgz
Normally, (automated) snapshots are kept on cvs.apache.org under the
snapshots directory. See http://cvs.apache.org/snapshots/
I'm not sure what creates those, but infrastructure@ ought to know. I'd very
much recommend to simply plugging into that system.
Cheers,
-g
--
Greg Stein, http://www.lyra.org/
Re: automated snapshots (was: Status)
Posted by "Gregory (Grisha) Trubetskoy" <gr...@apache.org>.
On Fri, 15 Aug 2003, Thom May wrote:
> ~apmail/bin/taritup is the script - let me know if I should do this; and
> I'll get it set up.
If you know how, please, that would be really wonderful. I was thinking of
looking at it, but don't have much time atm.
Thanks,
Grisha
Re: Building on Windows...
Posted by David Fraser <da...@sjsoft.com>.
David Fraser wrote:
> Gregory (Grisha) Trubetskoy wrote:
>
>> Given that there isn't a lot of feedback on this list, and given that I
>> can't think of any changes/additions to the code as it is right now, I
>> propose that we release it as 3.1.0 alpha with an announcement to a
>> wider
>> audience (the other list, and may be comp.lang.python), so that it
>> can get
>> more exposure and better testing.
>>
>> Grisha
>>
>>
>>
> Sounds great... While we're at releasing 3.1 alpha...
> I'm trying to build modpython latest CVS for Windows from source.
> However my standard build of apache 2.0.47 following
> http://httpd.apache.org/docs-2.0/platform/win_compiling.html doesn't
> seem to produce a variety of apxs, which modpython seems to need for
> configure...
> I've got Visual C++ 6.0, so I can't simply use the mod_python.vcproj in
> src (which is for 7.0)
Hi
Just found this great tool:
http://www.codeproject.com/tools/prjconverter.asp?print=true
Which converts VC++ 7.0 projects to VC++ 6.0 projects.
I'll try it out on mod_python and see if I can get it to build...
David
Re: Build system
Posted by "Gregory (Grisha) Trubetskoy" <gr...@apache.org>.
On Thu, 21 Aug 2003, David Fraser wrote:
> David Fraser wrote:
>
> On a related note, would it be possible to produce a distutils-style
> setup.py that:
> 1) Doesn't require running configure
It's probably possible, given that the only thing setup.py.in uses is the
mod_python version, and it should be farily easy to make that part of
setup.py itself.
> 2) Can build mod_python.so on Windows
Well, distutils does not know much about how to build applications that
embed Python (although that might be supported in the future), and
certainly it doesn't know how to build an Apache module, which is what
mod_python is. So this isn't going to be possible on _any_ operating
system.
> 3) Can produce a Windows installer on Windows
I am almost sure it already can.
> 4) Doesn't require Make files
It doesn't. It's convenient to invoke it _from_ make, but you don't have
to.
Grisha
Re: Build system
Posted by David Fraser <da...@sjsoft.com>.
David Fraser wrote:
> Gregory (Grisha) Trubetskoy wrote:
>
>> Given that there isn't a lot of feedback on this list, and given that I
>> can't think of any changes/additions to the code as it is right now, I
>> propose that we release it as 3.1.0 alpha with an announcement to a
>> wider
>> audience (the other list, and may be comp.lang.python), so that it
>> can get
>> more exposure and better testing.
>>
>> Grisha
>>
>>
>>
> Sounds great... While we're at releasing 3.1 alpha...
> I'm trying to build modpython latest CVS for Windows from source.
> However my standard build of apache 2.0.47 following
> http://httpd.apache.org/docs-2.0/platform/win_compiling.html doesn't
> seem to produce a variety of apxs, which modpython seems to need for
> configure...
> I've got Visual C++ 6.0, so I can't simply use the mod_python.vcproj in
> src (which is for 7.0)
> I do have mingw and cygwin though
> There doesn't seem to be any documentation around on how to build
> mod_python for Windows.
> (I need to do this because I want to test with Python 2.3)
> I'm not saying we neccessarily need heaps of documentation for the Alpha
> release, but if someone can help me through it, I can test it.
> And also, that would generate some documentation itself!
>
> David
>
On a related note, would it be possible to produce a distutils-style
setup.py that:
1) Doesn't require running configure
2) Can build mod_python.so on Windows
3) Can produce a Windows installer on Windows
4) Doesn't require Make files
5) Any of the above!
I know that configure etc make things much easier on Unix, but how many
of the requirements for building mod_python are really neccessary?
I'm keen to help set this up if it is feasible and someone can point me
in the right direction
David
Re: Alpha release?
Posted by "Gregory (Grisha) Trubetskoy" <gr...@apache.org>.
Thanks, Barry, I think this is good - it didn't occur to me to do it this
way. I checked the patch in and also removed the paragraph you mention
from the docs.
Grisha
On Thu, 21 Aug 2003, Barry Pederson wrote:
> Gregory (Grisha) Trubetskoy wrote:
> > Given that there isn't a lot of feedback on this list, and given that I
> > can't think of any changes/additions to the code as it is right now, I
> > propose that we release it as 3.1.0 alpha with an announcement to a wider
> > audience (the other list, and may be comp.lang.python), so that it can get
> > more exposure and better testing.
>
> I've got another suggestion ...
>
> Right now, mod_python mixes in some data with the user's data that get
> pickled, and the docs mention:
>
> ---------
> (A few key names are used by the BaseSession
> class itself for storing session metadata, they are preceeded with
> an underscore, so if you stay away from key names beginning with an
> underscore, you should be safe.)
> ---------
>
> That seems unnecessary. I'd suggest storing the metadata in a
> dictionary, and having the user's dictionary stored as a member of the
> metadata dictionary, say under the key name "_data". That way there's
> no worries about keyname conflicts, makes the thing a bit more
> bulletproof.
>
> I'll attach a patch showing what I have in mind - the only cost should
> be a few more bytes in the pickle. The subclass implementations of
> do_load() and do_save() are simplified a bit, and the session cleanup
> code doesn't need to be changed at all.
>
> I also tried moving checking for expired sessions down into the
> BaseSession.load() method, instead of completely loading the session and
> then later on deciding in __init__() that you have to undo what you did
> in load().
>
> Barry
>
Re: Alpha release?
Posted by Barry Pederson <bp...@barryp.org>.
Gregory (Grisha) Trubetskoy wrote:
> Given that there isn't a lot of feedback on this list, and given that I
> can't think of any changes/additions to the code as it is right now, I
> propose that we release it as 3.1.0 alpha with an announcement to a wider
> audience (the other list, and may be comp.lang.python), so that it can get
> more exposure and better testing.
I've got another suggestion ...
Right now, mod_python mixes in some data with the user's data that get
pickled, and the docs mention:
---------
(A few key names are used by the BaseSession
class itself for storing session metadata, they are preceeded with
an underscore, so if you stay away from key names beginning with an
underscore, you should be safe.)
---------
That seems unnecessary. I'd suggest storing the metadata in a
dictionary, and having the user's dictionary stored as a member of the
metadata dictionary, say under the key name "_data". That way there's
no worries about keyname conflicts, makes the thing a bit more
bulletproof.
I'll attach a patch showing what I have in mind - the only cost should
be a few more bytes in the pickle. The subclass implementations of
do_load() and do_save() are simplified a bit, and the session cleanup
code doesn't need to be changed at all.
I also tried moving checking for expired sessions down into the
BaseSession.load() method, instead of completely loading the session and
then later on deciding in __init__() that you have to undo what you did
in load().
Barry
Re: Alpha release?
Posted by David Fraser <da...@sjsoft.com>.
Gregory (Grisha) Trubetskoy wrote:
>So any plus ones on this?
>
>Grisha
>
>On Thu, 21 Aug 2003, Gregory (Grisha) Trubetskoy wrote:
>
>
>
>>Given that there isn't a lot of feedback on this list, and given that I
>>can't think of any changes/additions to the code as it is right now, I
>>propose that we release it as 3.1.0 alpha with an announcement to a wider
>>audience (the other list, and may be comp.lang.python), so that it can get
>>more exposure and better testing.
>>
>>Grisha
>>
>>
>>
>
>
>
+1 From me, particularly if that means a downloadable installer so I can
test it on Windows :-)
David
Re: Alpha
Posted by David Fraser <da...@sjsoft.com>.
Gregory (Grisha) Trubetskoy wrote:
>Thanks for the patch, I'll add that in. BTW - if you need more things to
>do, setup.py could dig out the version from ../src/include/mpversion.h,
>then we wouldn't need to have it autoconf-generated. :-)
>
>
Patch attached :-) This is just a patch to setup.py.in, so the rename to
setup.py can presumably take place (though I'm not sure about the @APXS@)
I used a regular expression to search it in the hope that it will be
fairly robust.
I hope I have got the paths right - you do run it from the parent as
dist/setup.py, right?
>On Wed, 27 Aug 2003, David Fraser wrote:
>
>
>>Basically it provides an alternative method which is still easier than
>>manually copying (it's not as nice as the tk method because
>>it doesn't guide you to the expected directory in the first place -
>>because there doesn't seem to be a nice way to do that in the win32 api!)
>>
>>
>I wonder if it might be the current working directory, but that's just a
>guess.
>
>
No, it actually just displays the entire directory tree, and you have to
start from My Computer.
You can pass in a Root but then it only displays subdirectories of that!
Actually we should really look up the directory in the registry I guess
David
Re: Alpha
Posted by "Gregory (Grisha) Trubetskoy" <gr...@apache.org>.
Thanks for the patch, I'll add that in. BTW - if you need more things to
do, setup.py could dig out the version from ../src/include/mpversion.h,
then we wouldn't need to have it autoconf-generated. :-)
On Wed, 27 Aug 2003, David Fraser wrote:
> Basically it provides an alternative method which is still easier than
> manually copying (it's not as nice as the tk method because
> it doesn't guide you to the expected directory in the first place -
> because there doesn't seem to be a nice way to do that in the win32 api!)
I wonder if it might be the current working directory, but that's just a
guess.
Grisha
Re: Alpha
Posted by David Fraser <da...@sjsoft.com>.
Gregory (Grisha) Trubetskoy wrote:
>On Wed, 27 Aug 2003, David Fraser wrote:
>
>
>>One question - is it really neccessary to have the tkinter dependency in
>>the install?
>>
>>
>Well... You have to give the user some way to specify where Apache is, so
>that the installer can place mod_python in the right location. The stock
>installer from python.org includes tk by default, so I thought it was
>safe.
>
>
Yes, it's just that we try do a minimal Python install for our end users...
>>It seems it is only required to ask for the directory of Apache in the
>>postinstall process...
>>
>>
>Pretty much.
>
>
>>Would you be happy to accept a patch that removes it, or provides an
>>alternate way of specifying the directory if Tkinter is not installed?
>>
>>
>
>If you can some up with something, that'd be great. In
>win32_postinstall.py, if you make askForApacheDir() fail gracefully if
>Tkinter is not there (with try/except), and then perhaps place
>mod_python.so into the Python directory instead (since you wouldn't know
>where Apache is), and adjust LoadModule in the final message accordingly.
>
>Grisha
>
>
I think the current handling is fine, it makes more sense for the user
to copy mod_python to the right place as it currently does.
But I've added a patch which will use the win32 extensions to let the
user browse to the right path if tk isn't installed.
I guess this just matches exactly what our users tend to have, so it
might not help anyone else, but I'd be grateful if it could be included.
Basically it provides an alternative method which is still easier than
manually copying (it's not as nice as the tk method because
it doesn't guide you to the expected directory in the first place -
because there doesn't seem to be a nice way to do that in the win32 api!)
The patch is attached. If I get time, I'll have a look at automatically
modifying the httpd.conf...
David
Re: Alpha
Posted by "Gregory (Grisha) Trubetskoy" <gr...@apache.org>.
On Wed, 27 Aug 2003, David Fraser wrote:
> One question - is it really neccessary to have the tkinter dependency in
> the install?
Well... You have to give the user some way to specify where Apache is, so
that the installer can place mod_python in the right location. The stock
installer from python.org includes tk by default, so I thought it was
safe.
> It seems it is only required to ask for the directory of Apache in the
> postinstall process...
Pretty much.
> Would you be happy to accept a patch that removes it, or provides an
> alternate way of specifying the directory if Tkinter is not installed?
If you can some up with something, that'd be great. In
win32_postinstall.py, if you make askForApacheDir() fail gracefully if
Tkinter is not there (with try/except), and then perhaps place
mod_python.so into the Python directory instead (since you wouldn't know
where Apache is), and adjust LoadModule in the final message accordingly.
Grisha
Re: Alpha
Posted by David Fraser <da...@sjsoft.com>.
Gregory (Grisha) Trubetskoy wrote:
>Check it out:
>
>http://www.modpython.org/dist/mod_python-3.1.0a.tgz
>http://www.modpython.org/dist/mod_python-3.1.0a.win32-py2.3.exe
>
>The docs are here:
>
>http://www.modpython.org/live/mod_python-3.1.0a/doc-html/
>http://www.modpython.org/live/mod_python-3.1.0a/modpython.pdf
>
>
Great, thanks for the release.
One question - is it really neccessary to have the tkinter dependency in
the install?
It seems it is only required to ask for the directory of Apache in the
postinstall process...
Would you be happy to accept a patch that removes it, or provides an
alternate way of specifying the directory if Tkinter is not installed?
David
Re: Alpha
Posted by "Gregory (Grisha) Trubetskoy" <gr...@apache.org>.
On Tue, 26 Aug 2003, Thom May wrote:
> I'd tend to argue we should so we can get it into apache's mirroring
> system. Although, I'm ambivalent for the alpha. Certainly for the full
> release this would seem to be goodness. Also, moving to daedalus makes
> it obvious to all concerned that this is an ASF sponsored project, which
> I think is no bad thing.
OK, moving them is easy, I just did it (*i think* - it's minotaur that
serves www.apache.org now?).
But I don't remember what to do to make download.cgi pick it up. Or should
we not bother with that at all and just point to www.apache.org/dist -
since there is probably only going to be a handful downloads.
Grisha
RE: Alpha
Posted by Sander Striker <st...@apache.org>.
> From: Thom May [mailto:thommay@apache.org]
> Sent: Tuesday, August 26, 2003 9:58 PM
>> To the Apache folks on this list: before announcing this to a wider
>> audience - do you think we should move the tgz and windist files to
>> daedalus?
>
> I'd tend to argue we should so we can get it into apache's mirroring system.
> Although, I'm ambivalent for the alpha. Certainly for the full release this
> would seem to be goodness.
> Also, moving to daedalus makes it obvious to all concerned that this is an
> ASF sponsored project, which I think is no bad thing.
+1. Start using the mirroring system early and get used to its workings.
It will be usefull to have some experience with it prior hitting 1.0.
Sander
Re: Alpha
Posted by Thom May <th...@apache.org>.
* Gregory (Grisha) Trubetskoy (grisha@apache.org) wrote :
>
> Check it out:
>
> http://www.modpython.org/dist/mod_python-3.1.0a.tgz
> http://www.modpython.org/dist/mod_python-3.1.0a.win32-py2.3.exe
>
> The docs are here:
>
> http://www.modpython.org/live/mod_python-3.1.0a/doc-html/
> http://www.modpython.org/live/mod_python-3.1.0a/modpython.pdf
>
>
> To the Apache folks on this list: before announcing this to a wider
> audience - do you think we should move the tgz and windist files to
> daedalus?
I'd tend to argue we should so we can get it into apache's mirroring system.
Although, I'm ambivalent for the alpha. Certainly for the full release this
would seem to be goodness.
Also, moving to daedalus makes it obvious to all concerned that this is an
ASF sponsored project, which I think is no bad thing.
-Thom
Alpha
Posted by "Gregory (Grisha) Trubetskoy" <gr...@apache.org>.
Check it out:
http://www.modpython.org/dist/mod_python-3.1.0a.tgz
http://www.modpython.org/dist/mod_python-3.1.0a.win32-py2.3.exe
The docs are here:
http://www.modpython.org/live/mod_python-3.1.0a/doc-html/
http://www.modpython.org/live/mod_python-3.1.0a/modpython.pdf
To the Apache folks on this list: before announcing this to a wider
audience - do you think we should move the tgz and windist files to
daedalus?
I'm inclined to think that it's OK on www.modpython.org, but mainly
because I'm lazy and I'd like to see how many people actually download it.
Grisha
Re: Alpha release?
Posted by Barry Pederson <bp...@barryp.org>.
Gregory (Grisha) Trubetskoy wrote:
> So any plus ones on this?
>
> Grisha
>
> On Thu, 21 Aug 2003, Gregory (Grisha) Trubetskoy wrote:
>
>
>>Given that there isn't a lot of feedback on this list, and given that I
>>can't think of any changes/additions to the code as it is right now, I
>>propose that we release it as 3.1.0 alpha with an announcement to a wider
>>audience (the other list, and may be comp.lang.python), so that it can get
>>more exposure and better testing.
+1 Sure, I've been stopping, starting, gracefuly and otherwise, and it
seems OK now. Had FreeBSD 5.1 completely hang before, but since you've
made that change to the pool it's working well.
Barry
Re: Alpha release?
Posted by "Gregory (Grisha) Trubetskoy" <gr...@apache.org>.
So any plus ones on this?
Grisha
On Thu, 21 Aug 2003, Gregory (Grisha) Trubetskoy wrote:
>
> Given that there isn't a lot of feedback on this list, and given that I
> can't think of any changes/additions to the code as it is right now, I
> propose that we release it as 3.1.0 alpha with an announcement to a wider
> audience (the other list, and may be comp.lang.python), so that it can get
> more exposure and better testing.
>
> Grisha
>
Re: Building on Windows...
Posted by David Fraser <da...@sjsoft.com>.
Gregory (Grisha) Trubetskoy wrote:
>Given that there isn't a lot of feedback on this list, and given that I
>can't think of any changes/additions to the code as it is right now, I
>propose that we release it as 3.1.0 alpha with an announcement to a wider
>audience (the other list, and may be comp.lang.python), so that it can get
>more exposure and better testing.
>
>Grisha
>
>
>
Sounds great... While we're at releasing 3.1 alpha...
I'm trying to build modpython latest CVS for Windows from source.
However my standard build of apache 2.0.47 following
http://httpd.apache.org/docs-2.0/platform/win_compiling.html doesn't
seem to produce a variety of apxs, which modpython seems to need for
configure...
I've got Visual C++ 6.0, so I can't simply use the mod_python.vcproj in
src (which is for 7.0)
I do have mingw and cygwin though
There doesn't seem to be any documentation around on how to build
mod_python for Windows.
(I need to do this because I want to test with Python 2.3)
I'm not saying we neccessarily need heaps of documentation for the Alpha
release, but if someone can help me through it, I can test it.
And also, that would generate some documentation itself!
David
PS Sorry Grisha, forgot to include the list in the first reply
Alpha release?
Posted by "Gregory (Grisha) Trubetskoy" <gr...@apache.org>.
Given that there isn't a lot of feedback on this list, and given that I
can't think of any changes/additions to the code as it is right now, I
propose that we release it as 3.1.0 alpha with an announcement to a wider
audience (the other list, and may be comp.lang.python), so that it can get
more exposure and better testing.
Grisha
Re: automated snapshots (was: Status)
Posted by Thom May <th...@apache.org>.
* Greg Stein (gstein@lyra.org) wrote :
> On Thu, Aug 14, 2003 at 11:42:08AM -0400, Gregory (Grisha) Trubetskoy wrote:
> >
> > I just added another snapshot
> >
> > http://www.modpython.org/tmp/httpd-python-20030814.tgz
>
> Normally, (automated) snapshots are kept on cvs.apache.org under the
> snapshots directory. See http://cvs.apache.org/snapshots/
>
> I'm not sure what creates those, but infrastructure@ ought to know. I'd very
> much recommend to simply plugging into that system.
>
~apmail/bin/taritup is the script - let me know if I should do this; and
I'll get it set up.
Cheers
-Thom