New submission from Ethan Furman: 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. ---------- files: remove_assret.stoneleaf.01.patch keywords: patch messages: 246873 nosy: ethan.furman, michael.foord priority: normal severity: normal status: open title: remove "assret" from mock error checking versions: Python 3.5 Added file: http://bugs.python.org/file39939/remove_assret.stoneleaf.01.patch _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue24656> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
