This bug makes Pylons-dev unusable with formencode validation. I've
had to revert to the Jan 12th revsion to get something usable.
http://pylonshq.com/project/pylonshq/ticket/367
#367: @validate broken after Request/Response changes
--
Mike Orr <[EMAIL PROTECTED]>
--~--~-~--~~--
I finally started making forms in my app this week. I found Mako more
convenient than any of the form libraries. I use a call-with-content
to format an input control with its title, hint, and error message.
Then htmlfill to set both the initial values and the error messages.
ToscaWidgets has to
On Jan 25, 2008 8:24 AM, Andrew Smart <[EMAIL PROTECTED]> wrote:
>
>
> > -Ursprüngliche Nachricht-
> > Von: pylons-devel@googlegroups.com
> > [mailto:[EMAIL PROTECTED] Im Auftrag von Mike Orr
> > Gesendet: Freitag, 25. Januar 2008 17:06
> > An: pylons-devel@googlegroups.com
> > Betreff: Re
> -Ursprüngliche Nachricht-
> Von: pylons-devel@googlegroups.com
> [mailto:[EMAIL PROTECTED] Im Auftrag von Mike Orr
> Gesendet: Freitag, 25. Januar 2008 17:06
> An: pylons-devel@googlegroups.com
> Betreff: Re: Routes and WebHelpers status, and lxml
>
> That may be doable. I haven't lo
On Jan 25, 2008 2:54 AM, Andrew Smart <[EMAIL PROTECTED]> wrote:
> But AFAIK does lxml mimick the ElementTree API. Maybe a "workaround" for the
> time beeing
> would be that Pylons itself uses only API features common in both packages,
> and let the
> users/developers decide what package (and addi
> Just my 2cents: I just decided after some research to use lxml in all of my
> projects,
> and I guess my decission tree is comparable to that many other Python
> developers out
> there. I would bet lxml is the emerging standard.
I hope so too, but it's C-dependency is not the best for mass depl
> -Ursprüngliche Nachricht-
> Von: pylons-devel@googlegroups.com
> [mailto:[EMAIL PROTECTED] Im Auftrag von Philip Jenvey
> Gesendet: Donnerstag, 24. Januar 2008 22:31
> An: pylons-devel@googlegroups.com
> Betreff: Re: Routes and WebHelpers status, and lxml
>
>
>
> On Jan 22, 2008, at
