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 ethan.furman
Recipients ethan.furman, michael.foord
Date 2015-07-18.00:48:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1437180484.75.0.469707638561.issue24656@psf.upfronthosting.co.za>
In-reply-to
Content
Per Nick's suggestion here is the patch to remove the "assret" check, but leave the "assert" check in place.

As Terry summarized:
> 1. It is false that 'assret' is necessarily a typo. Someone might quite
> legitimately use it as an attribute. Aside from the fact that it might be an
> *intentional* misspelling to avoid a clash with 'assert', I found the following
> on Google.
>   a. It appears to be both a (person) name (Turkey?) and a username.
>   b. It can be a contraction, abbreviation, or pair of acronym: ass-et
>      ret-ention, ass-istant ret-ired (?), and something in connection with
>      high-pressure oil lines.  Python usage is not restricted to English-
>      speaking geeks.
>
> 2. It gives the impression that 'assret' is a legitimate alias for 'assert'.
> See https://stackoverflow.com/questions/31382895/any-core-real-reference-to-assret-as-alias-to-assert
>
> If the doc is revised to counter this impression, then I predict that this will
> join the list of Python warts and reasons to ridicule Python.
>
> 3. It violates Python design principles. To many, the beauty of Python is that
> it is relatively clean and simple, and not filled with hundreds of nitpicky
> exceptions and special cases.
History
Date User Action Args
2015-07-18 00:48:05ethan.furmansetrecipients: + ethan.furman, michael.foord
2015-07-18 00:48:04ethan.furmansetmessageid: <1437180484.75.0.469707638561.issue24656@psf.upfronthosting.co.za>
2015-07-18 00:48:04ethan.furmanlinkissue24656 messages
2015-07-18 00:48:02ethan.furmancreate