durusmail: quixote-users: Generalizing form/widget API a bit
Generalizing form/widget API a bit
2003-11-25
2003-11-25
2003-11-25
2003-11-25
2003-11-25
2003-11-26
2003-11-26
2003-11-26
2003-11-26
2003-11-26
2003-11-26
2003-11-26
2003-11-26
2003-11-26
2003-11-26
2003-11-26
2003-11-29
2003-11-30
2003-11-26
2003-11-26
2003-11-26
Patch: add html_attrs keyword arg to widget classes
2003-11-30
Patch: add html_attrs keyword arg to widget classes
2003-12-01
Patch: add html_attrs keyword arg to widget classes
2003-12-01
Patch: add html_attrs keyword arg to widget classes
2003-12-01
2003-12-02
2003-12-03
2003-12-02
Patch: add html_attrs keyword arg to widget classes
2003-12-01
Patch: add html_attrs keyword arg to widget classes
2003-12-01
Generalizing form/widget API a bit
Michael Watkins
2003-11-26
On Wed, 2003-11-26 at 08:05, Nicola Larosa wrote:
> Public attributes should have no leading or trailing
> underscores, unless they conflict with reserved words, in which
> case, a single trailing underscore is preferrable to a leading
> one, or a corrupted spelling, e.g. class_ rather than klass.
> (This last point is a bit controversial; if you prefer klass
> over class_ then just be consistent. :)."

How about we just require that attrs passed be a dict and be done with
it. Leave the creation of the dict the responsibility of the application
developer.

Then the pre 2.3 folks can write their own make_dict; 2.3 folks can use
the new construct, and all is well.

Or is the simple answer too... er... simple?


--
Mike Watkins
mw@mikewatkins.net


"Apathy is not the problem, it's the solution"


reply