2007/9/1, Sean DiZazzo <[EMAIL PROTECTED]>:
> How should we replace in our code:
>
> for k,v in dict.iteritems():
for k, v in dict.items():
--
Lino Mastrodomenico
E-mail: [EMAIL PROTECTED]
___
Python-3000 mailing list
Python-3000@
ries that prefer a simpler interface, even if it may
be slightly less efficient in some, hopefully rare, cases).
--
Lino Mastrodomenico
E-mail: [EMAIL PROTECTED]
___
Python-3000 mailing list
Python-3000@python.org
http://mail.python.org/mailman/listinfo/pyth
(including at least PIL,
wxPython and pygame) to implement the new protocol in their image
classes without breaking compatibility with existing code. The only
blatant conflicts between the image protocol and NumPy arrays are
the value of the ``size`` attribute and the coordinates order in the
PEP is accepted, I'll backport the new
classes to Python 2.6.
Any suggestion or criticism is welcome; I'll also solicit feedback
from external libraries developers that might be interested in
implementing the new protocol.
Regards
--
a non caderne fuori!
http://python.it/doc/Python-Docs/html/tut/node4.html
Please note the "รจ" character in the variable name. And yes, this code
used to work out of the box (AFAIK at least until Python 2.2).
--
Lino Mastrodomenico
E-mail: [EMAIL PROTECTED]
__
real method or the "fake" default_method.
I think this can be useful when a method *doesn't know* if it's the
last in the MRO because it may depend on the inheritance hierarchy of
its subclasses: you can always simply call super.meth(...) and if the
current method is the last this
