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.

classification
Title: remove "assret" from mock error checking
Type: behavior Stage: resolved
Components: Versions: Python 3.5
process
Status: closed Resolution: rejected
Dependencies: Superseder:
Assigned To: Nosy List: ethan.furman, kushal.das, michael.foord, ncoghlan, rbcollins
Priority: normal Keywords: patch

Created on 2015-07-18 00:48 by ethan.furman, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
remove_assret.stoneleaf.01.patch ethan.furman, 2015-07-18 00:48 review
remove_assret.stoneleaf.02.patch ethan.furman, 2015-07-18 15:19 review
remove_assret.stoneleaf.03.patch ethan.furman, 2015-07-18 23:46 review
Messages (5)
msg246873 - (view) Author: Ethan Furman (ethan.furman) * (Python committer) Date: 2015-07-18 00:48
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.
msg246902 - (view) Author: Ethan Furman (ethan.furman) * (Python committer) Date: 2015-07-18 15:19
Better patch: fixes NEWS, tests, and docs, as well as the code.
msg246924 - (view) Author: Ethan Furman (ethan.furman) * (Python committer) Date: 2015-07-18 23:46
Addressed comments from berker.peksag.
msg246925 - (view) Author: Michael Foord (michael.foord) * (Python committer) Date: 2015-07-18 23:48
-1

The whole thread is absurd. I'm travelling for europython and only have
internet access on my phone until tomorrow at the earliest.

On Saturday, 18 July 2015, Berker Peksag <report@bugs.python.org> wrote:
>
> Changes by Berker Peksag <berker.peksag@gmail.com>:
>
>
> ----------
> nosy: +kushal.das, ncoghlan, rbcollins
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue24656>
> _______________________________________
>

-- 

http://www.voidspace.org.uk/

May you do good and not evil
May you find forgiveness for yourself and forgive others
May you share freely, never taking more than you give.
-- the sqlite blessing http://www.sqlite.org/different.html
msg246953 - (view) Author: Nick Coghlan (ncoghlan) * (Python committer) Date: 2015-07-20 04:19
Marking as rejected by the module maintainer.
History
Date User Action Args
2022-04-11 14:58:18adminsetgithub: 68844
2015-07-20 04:19:34ncoghlansetstatus: open -> closed
resolution: rejected
messages: + msg246953

stage: patch review -> resolved
2015-07-18 23:48:53michael.foordsetmessages: + msg246925
2015-07-18 23:46:59ethan.furmansetfiles: + remove_assret.stoneleaf.03.patch

messages: + msg246924
2015-07-18 21:45:44berker.peksagsetnosy: + ncoghlan, rbcollins, kushal.das
2015-07-18 19:31:55ethan.furmansettype: behavior
stage: patch review
2015-07-18 15:19:21ethan.furmansetfiles: + remove_assret.stoneleaf.02.patch

messages: + msg246902
2015-07-18 00:48:04ethan.furmancreate