On Thu, 4 Nov 2004 11:12:30 -0500, Neil Schemenauer
 wrote:
> On Thu, Nov 04, 2004 at 12:39:13PM +0100, Michele Simionato wrote:
> > 1. Fist of all, FIX_TRAILING_SLASH
> > should be set to 1 by default, it made
> > me waste some time until I figured out
> > what was happening by trial and errors.
>
> Having it enabled leads to confusion as well.  I still think it's
> better to have it disabled but perhaps there should be a prominent
> note in the docs explaining it.

Well, I would like it the other way around (enabling it by default and
explaining
in a prominent note in the docs what it is going on). What happened to me is
that I went into http://localhost/cgi-bin/demo.cgi, I saw the demo page and
I clicked on the links: they did not work. I discovered after some time that
the links of type http://localhost/cgi-bin/demo.cgi/ worked; finally I
understood that I had to call http://localhost/cgi-bin/demo.cgi/ and
not http://localhost/cgi-bin/demo.cgi in order to have the demo
working.
It is pretty confusing to have http://localhost/cgi-bin/demo.cgi and
http://localhost/cgi-bin/demo.cgi/ display the same page, but with the
first form
not working properly with the links. If we enable FIX_TRAILING_SLASH by
default, the user will see slashes automagically inserted, but at
least the demo
will work.

> > I also have a question/curiosity about
> > PTL files; I would imagine PTL
> > files to be converted into regular
> > python at import time and bytecompiled
> > once. So I would expect .pltc files to be
> > actually .pyc files. Is that true? And
> > if not, what is the difference?
>
> They are not actually the same although the bytecode is the same.
>

Care to expand? What's the rationale for having .ptlc files different from
..pyc files?


 Michele Simionato