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 terry.reedy
Recipients arno, docs@python, rhettinger, terry.reedy
Date 2010-09-04.18:31:56
SpamBayes Score 0.000438319
Marked as misclassified No
Message-id <>
Since Raymond has grabbed this, I will let him decide on its scope.
I agree with sectioning the operator doc and intended to suggest that.

The term 'in-place operation' is fine when accurate. The term 'in-place operator', which is what you wrote and what I criticized, is not as it is never accurate and has confused and mislead people. For one thing, it leads them to forget that augmented assignment statements are statements that *always* do an assignment. For another, they forget that the operation can only be in-place for mutables. That is my observation based on years of reading c.l.p./python-list. An 'in-place operator' would do an operation in-place without any assighment and would only work for mutables. Python has neither operators nor functions nor syntax with those characteristics.
Date User Action Args
2010-09-04 18:31:59terry.reedysetrecipients: + terry.reedy, rhettinger, arno, docs@python
2010-09-04 18:31:59terry.reedysetmessageid: <>
2010-09-04 18:31:56terry.reedylinkissue9717 messages
2010-09-04 18:31:56terry.reedycreate