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 gvanrossum
Recipients barry, brandon-rhodes, docs@python, gvanrossum
Date 2016-04-16.21:12:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1460841152.81.0.460743121792.issue26780@psf.upfronthosting.co.za>
In-reply-to
Content
Patch LGTM.

Note that the and/or example was in the PEP before this discussion broke out.

The discussion also at some point (before your Knuth quote was discovered) veered in the direction of making and/or a special case, perhaps because it's more likely that a long expression must be broken around and/or operators. And there were already examples of breaking after binary arithmetic operators elsewhere in the PEP (I think).
History
Date User Action Args
2016-04-16 21:12:32gvanrossumsetrecipients: + gvanrossum, barry, brandon-rhodes, docs@python
2016-04-16 21:12:32gvanrossumsetmessageid: <1460841152.81.0.460743121792.issue26780@psf.upfronthosting.co.za>
2016-04-16 21:12:32gvanrossumlinkissue26780 messages
2016-04-16 21:12:32gvanrossumcreate