durusmail: quixote-users: Call for help
Call for help
2007-01-21
2007-01-21
Re: Call for help
2007-01-30
2007-01-21
2007-01-30
2007-01-30
2007-01-30
2007-01-30
2007-02-01
2007-02-01
2007-02-01
2007-02-02
2007-02-02
2007-02-02
2007-02-02
2007-02-02
2007-02-03
Re: Call for help
2007-02-06
Re: Call for help
2007-02-05
2007-01-30
Call for help
Mike Orr
2007-01-30
I have been using the Quixote/QPY hack on my production

On 1/30/07, David Binger  wrote:
>
> On Jan 30, 2007, at 3:14 AM, Titus Brown wrote:
> > -> C. Titus Brown :
> > ->     Added quixote.html.use_qpy to switch Quixote over to using qpy
> > ->     instead of htmltext.
> >
> > whups.  This code was *contributed* by Mike Orr; I just integrated it
> > and wrote a test.
>
> I think it is necessary to commit to using either qpy or ptl
> at the time that "quixote.html" is imported.  Otherwise, you open
> the door for having, in your application, htmltext that is
> in some places from qpy and in some places from ptl.
> These two classes of quoted text are very similar, but they are
> not written to coexist in an application.  If they do, you will
> probably observe either over-quoting or exceptions.

I would delete htmltext entirely and make Quixote depend on QPY and
the htmltext-compatibility stubs.  We may as well do it now and give
Quixote proper Unicode support.  I also needed it to make Quixote
compatible with Cheetah.  (Otherwise I couldn't use a form.render() or
href() result in a template.)

I've been using the Quixote/QPY hack on my production sites since
November 7 and have not seen any errors.  My version is a module that
imports quixote and qpy and patches quixote.  I make sure to import it
at the beginning of my applications before importing quixote, to
minimize the possibility of any stray htmltext objects being created.

We can release a beta version of Quixote so that people can verify
it's compatible with their applications.

--
Mike Orr 
reply