>> 4. One of the example insets shows Unix users executing generate as
>> "generate", when it should read "./generate", or "python2 generate".
> Depends on your path - frequently normal users have
> current directory as the last part of their path.
> This should never be the case for root user.
True, but "./generate" will work 100% of the time, whereas otherwise you're
dependent on that particular user's path setup, so I think the docs ought to
cover all cases.
I know what you mean about root -- I don't even like putting $PWD in path
for my regular user, because I actually want to hold on to what's in my home
>> 8. The main.py example won't run under python 1.x either, because it imports
>> MySQLObjectStore, which has syntax requiring python2.
> I think Webware itself won't run under 1.x - even
> in the install script there are python2 dependencies.
That's correct, which leads me to a tangential question: Webware won't even
run (in the full range of configurations) unless I've changed the first line
of the install script, AppServer, WebKit.cgi, OneShot.cgi, and perhaps
something else I can't remember, to point to python2.
So if Webware 0.7 requires python2, have these first lines not been changed
because many users' python2 installations are accessed by the command
"python", not "python2?"
If this is the case, I think this is something the install script should
account for and change as needed, because as much as some may dislike
Redhat, "python2" is what you need to invoke Python 2.2.1, and right now,
out of the box, Webware just crashes without those changes on this distro.
Since RH is the 800 pound gorilla of Linux distros, and Webware breaks out
of the box with it, I think this is ripe for correction.
I know if I were a casual user, and I installed webware and it crashed right
at startup, not only would it give me an (unjustified) feeling that Webware
is fragile, but it would also give me another hoop to jump through before I
could use it.
So is there some way Webware can internally account for the fact that some
distros call Python 2.2.x "python2", and deal with those vagaries instead of
crashing out of the box?
>> BTW, if anybody wants to rewrite main.py for python2, I'd sure appreciate
>> it, as I can get on with this business. I don't know what python2's
>> equivalent for 1.x's mx.DateTime is, but I'm sure one of you does! :-)
> I believe just comment out the import mx line,
> and when passing a date, send