Python declarative

Matěj Cepl mcepl at redhat.com
Fri Jan 24 11:28:41 EST 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2014-01-24, 11:18 GMT, you wrote:
> Write your rendering engine as a few simple helper functions, 
> and then put all the rest in as code instead of XML. The 
> easiest way to go about it is to write three forms, from 
> scratch, and then look at the common parts and figure out 
> which bits can go into helper functions.

Perhaps what's missing is full acknowledgment that Python has 
dual-inheritance and thus it can have mixin classes (which seems 
to me to be the only useful use of dual inheritance). You know 
you can have mixins in Python, right?

Also, I wrote my share of XML parsing/writing code, but more and 
more I am persuaded that if the answer is “XML” then there is 
some wrong with the question. Python is a way more expressive 
language than XML, so it is almost always more useful to write 
in Python, than to pass any problems to XML.

Matěj

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iD8DBQFS4pS54J/vJdlkhKwRApdcAJ48PRgDz6ccnq1YFD9zx8EDDH3JjgCghU2x
3CV+D0LvquzgYRux2GslZ0E=
=Y3/F
-----END PGP SIGNATURE-----



More information about the Python-list mailing list