This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author georg.brandl
Recipients Michael.Gilbert, georg.brandl
Date 2010-07-29.14:42:50
SpamBayes Score 0.0027431855
Marked as misclassified No
Message-id <1280414574.96.0.221139710292.issue9401@psf.upfronthosting.co.za>
In-reply-to
Content
This might work for (normally) commutative operations like multiplication and addition, but what about those like subtraction?  If the interpreter uses the non-reversed method automatically, it has to apply semantics, but the semantics depend on the type and cannot be guessed by the interpreter.  Also, even for normally commutative operations some type may want to behave non-commutative.  With this in mind, this cannot be implemented without major headaches both for the implementation and backwards compatibility.
History
Date User Action Args
2010-07-29 14:42:55georg.brandlsetrecipients: + georg.brandl, Michael.Gilbert
2010-07-29 14:42:54georg.brandlsetmessageid: <1280414574.96.0.221139710292.issue9401@psf.upfronthosting.co.za>
2010-07-29 14:42:51georg.brandllinkissue9401 messages
2010-07-29 14:42:50georg.brandlcreate