F
Frank Benkstein
Hi,
is there any possibility to see PEP 3115 implemented for Python 2.6?
AFAICS there's nothing about it that should limit it's implementation
to Python 3000 if backwards compatibility with '__metaclass__' is
preserved. At least the '__prepare__' in metaclasses method would be
very useful. Keyword parameters to the class statement are not so
important IMHO.
Best regards
Frank Benkstein.
--
GPG (Mail): 7093 7A43 CC40 463A 5564 599B 88F6 D625 BE63 866F
GPG (XMPP): 2243 DBBA F234 7C5A 6D71 3983 9F28 4D03 7110 6D51
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGCBSmiPbWJb5jhm8RAmMbAJ9QG8osxcgn9LYCApHO/8SzgQPWUQCeIaNt
aF9ruvmpYKQ/1eeF1HotXMk=
=34gQ
-----END PGP SIGNATURE-----
is there any possibility to see PEP 3115 implemented for Python 2.6?
AFAICS there's nothing about it that should limit it's implementation
to Python 3000 if backwards compatibility with '__metaclass__' is
preserved. At least the '__prepare__' in metaclasses method would be
very useful. Keyword parameters to the class statement are not so
important IMHO.
Best regards
Frank Benkstein.
--
GPG (Mail): 7093 7A43 CC40 463A 5564 599B 88F6 D625 BE63 866F
GPG (XMPP): 2243 DBBA F234 7C5A 6D71 3983 9F28 4D03 7110 6D51
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGCBSmiPbWJb5jhm8RAmMbAJ9QG8osxcgn9LYCApHO/8SzgQPWUQCeIaNt
aF9ruvmpYKQ/1eeF1HotXMk=
=34gQ
-----END PGP SIGNATURE-----