[issue39993] Language Reference - Function definition parameter_list item definition not equivalent to implementation.

Change by Serhiy Storchaka : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue39993] Language Reference - Function definition parameter_list item definition not equivalent to implementation.

Michael S added the comment: Thanks Pablo, sorry, I was just stupid. > Do you think that adding these explicit parentheses would help with help > making this more clear? Maybe. I read the BNF documentation the first time today, but since it's not intended for beginners, I think it's

[issue39990] help should evaluate forward reference

) However, is is not aware of globals and especially locals of help caller, so I guess more sophisticated solution is required. -- title: help output should make use of typing.get_type_hints -> help should evaluate forward reference ___ Python tracker <

[issue39993] Language Reference - Function definition parameter_list item definition not equivalent to implementation.

Pablo Galindo Salgado added the comment: > Did I miss something? Yep, what you are missing is that the rule is really: (defparameter ("," defparameter)* "," "/" ["," [parameter_list_no_posonly]]) | (parameter_list_no_posonly) which means that is either defparameter ("," defparameter)*

[issue39993] Language Reference - Function definition parameter_list item definition not equivalent to implementation.

New submission from Michael S : I just read https://docs.python.org/3/reference/compound_stmts.html#function-definitions The item parameter_list is defined as: parameter_list::= defparameter ("," defparameter)* "," "/" [&

[issue39879] Update language reference to specify that dict is insertion-ordered.

Furkan Önder added the comment: I sent pr. All tests passed successfully. If accepted, this will be my first contribution :) https://github.com/python/cpython/pull/19027 -- ___ Python tracker

[issue39879] Update language reference to specify that dict is insertion-ordered.

Change by Furkan Önder : -- nosy: +furkanonder nosy_count: 4.0 -> 5.0 pull_requests: +18375 pull_request: https://github.com/python/cpython/pull/19027 ___ Python tracker ___

[issue39879] Update language reference to specify that dict is insertion-ordered.

Lahfa Samy added the comment: Following the guide, I've send a patch with the fix, I'm waiting for a review. Once the patch will be reviewed and accepted. My patch will need to be backported from 3.9 to 3.7. -- ___ Python tracker

[issue39879] Update language reference to specify that dict is insertion-ordered.

Change by Lahfa Samy : -- keywords: +patch pull_requests: +18351 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/19006 ___ Python tracker

[issue39879] Update language reference to specify that dict is insertion-ordered.

Mariatta added the comment: Patch are submitted as pull request on our GitHub repo. Here's a write-up on how to do it https://devguide.python.org/pullrequest/#step-by-step-guide -- nosy: +Mariatta ___ Python tracker

[issue39879] Update language reference to specify that dict is insertion-ordered.

Lahfa Samy added the comment: Hi, I would like to take this issue as my first contribution to Python, I'm currently subscribed to the python-core-mentorship list. I do not know exactly how to submit a patch for an issue. Kind regards. -- nosy: +AkechiShiro

[issue17422] language reference should specify restrictions on class namespace

Ned Deily added the comment: New changeset 22448149a05b5bc3e3a2ffdc0682bcd01995ce2a by Ned Deily (Miss Islington (bot)) in branch '3.7': bpo-17422: slightly more precise language (GH-18682) https://github.com/python/cpython/commit/22448149a05b5bc3e3a2ffdc0682bcd01995ce2a -- nosy:

[issue39868] Stale Python Language Reference docs (no walrus).

Change by SHANKAR JHA : -- keywords: +patch pull_requests: +18213 stage: -> patch review pull_request: https://github.com/python/cpython/pull/18851 ___ Python tracker ___

[issue39831] Reference leak in PyErr_WarnEx()

Serhiy Storchaka added the comment: New changeset 89fabe51af27a16ae7174ad94921e3980e28 by Serhiy Storchaka in branch '3.7': [3.7] bpo-39831: Fix a reference leak in PyErr_WarnEx(). (GH-18750). (GH-18765) https://github.com/python/cpython/commit/89fabe51af27a16ae7174ad94921e3980e28

[issue39831] Reference leak in PyErr_WarnEx()

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue39868] Stale Python Language Reference docs (no walrus).

SHANKAR JHA added the comment: I have added the pull request: https://github.com/python/cpython/pull/18851. Please check it out and let me know if I need to change anything. Thank you everyone for your guidance. -- ___ Python tracker

[issue39868] Stale Python Language Reference docs (no walrus).

should be adding my code. Do I have to add code > here > https://github.com/python/cpython/blob/master/Doc/reference/expressions.rst > and push it? Yes, you'll add the new documentation to line 1652, where the "TODO" comment is. You should make the changes in your own fo

[issue39868] Stale Python Language Reference docs (no walrus).

. Please tell me where I should be adding my code. Do I have to add code here https://github.com/python/cpython/blob/master/Doc/reference/expressions.rst and push it? 2. I am working on the master branch only. Is there any specific branch I have to select

[issue39868] Stale Python Language Reference docs (no walrus).

Brandt Bucher added the comment: Great. Just replacing the TODO line with your new description (and maybe an example) should be perfect! -- keywords: -patch stage: patch review -> ___ Python tracker

[issue17422] language reference should specify restrictions on class namespace

Eric Snow added the comment: Thanks for fixing that, Caleb! FWIW, I've opened a separate issue (#39879) for adding a note in the language reference about dict ordering. Sorry for the confusion. -- resolution: -> fixed stage: patch review -> resolved status: open -&g

[issue39879] Update language reference to specify that dict is insertion-ordered.

New submission from Eric Snow : As of 3.7 [1], dict is guaranteed to preserve insertion order: the insertion-order preservation nature of dict objects has been declared to be an official part of the Python language spec. However, at least one key part of the language reference [2

[issue17422] language reference should specify restrictions on class namespace

miss-islington added the comment: New changeset 6df0c47669031c6a8e9b1a07ec2c5813e4c10ee0 by Miss Islington (bot) in branch '3.8': bpo-17422: slightly more precise language (GH-18682) https://github.com/python/cpython/commit/6df0c47669031c6a8e9b1a07ec2c5813e4c10ee0 --

[issue17422] language reference should specify restrictions on class namespace

miss-islington added the comment: New changeset f1b79645cf18b2c212cd26d547cd1762fd534d4b by Miss Islington (bot) in branch '3.7': bpo-17422: slightly more precise language (GH-18682) https://github.com/python/cpython/commit/f1b79645cf18b2c212cd26d547cd1762fd534d4b --

[issue17422] language reference should specify restrictions on class namespace

Change by miss-islington : -- pull_requests: +18170 pull_request: https://github.com/python/cpython/pull/18812 ___ Python tracker ___

[issue17422] language reference should specify restrictions on class namespace

Change by miss-islington : -- pull_requests: +18171 pull_request: https://github.com/python/cpython/pull/18813 ___ Python tracker ___

[issue17422] language reference should specify restrictions on class namespace

miss-islington added the comment: New changeset e59334ebc9308b0f3ad048ef293c6b49e6456d1a by Caleb Donovick in branch 'master': bpo-17422: slightly more precise language (GH-18682) https://github.com/python/cpython/commit/e59334ebc9308b0f3ad048ef293c6b49e6456d1a --

[issue39868] Stale Python Language Reference docs (no walrus).

SHANKAR JHA added the comment: I got it that I have to fill the "Assignment expression" section in the code. I am working on it and send you the for review once I am done. -- ___ Python tracker

[issue39868] Stale Python Language Reference docs (no walrus).

SHANKAR JHA added the comment: I am also checking your commit for this: (https://github.com/python/cpython/commit/8bae21962bab2fac7630982abd73676b89930902) and see that you are changing the "expression: to "assignment_expression". Do I have to fill what assignment expression does with some

[issue39868] Stale Python Language Reference docs (no walrus).

SHANKAR JHA added the comment: Thank you for helping me out brandtbucher. As per my understanding, I am looking into the code (https://github.com/python/cpython/blob/master/Doc/reference/expressions.rst) and finding where the code doesn't follow the pattern described in (https

[issue39868] Stale Python Language Reference docs (no walrus).

Brandt Bucher added the comment: Thanks for offering to help, Shankar! For this change, you can look at the other sections of the Doc/reference/expressions.rst file for an idea of what we're looking for. I think a few sentences and maybe a small code snippet should probably be fine

[issue39868] Stale Python Language Reference docs (no walrus).

miss-islington added the comment: New changeset 0c717709c1b19b6f146b56db5f10bab3f09c by Miss Islington (bot) in branch '3.8': bpo-39868: Update Language Reference for PEP 572. (GH-18793) https://github.com/python/cpython/commit/0c717709c1b19b6f146b56db5f10bab3f09c

[issue39868] Stale Python Language Reference docs (no walrus).

Guido van Rossum added the comment: New changeset 8bae21962bab2fac7630982abd73676b89930902 by Brandt Bucher in branch 'master': bpo-39868: Update Language Reference for PEP 572. (#18793) https://github.com/python/cpython/commit/8bae21962bab2fac7630982abd73676b89930902 -- nosy

[issue39868] Stale Python Language Reference docs (no walrus).

Change by miss-islington : -- nosy: +miss-islington nosy_count: 5.0 -> 6.0 pull_requests: +18153 pull_request: https://github.com/python/cpython/pull/18797 ___ Python tracker

[issue39868] Stale Python Language Reference docs (no walrus).

SHANKAR JHA added the comment: This is my first contribution to Python. This is why I am looking for some guidance, just point me to some resource, and then I will look into it thoroughly. I am reading this https://www.python.org/dev/peps/pep-0572/ for better understanding. --

[issue39868] Stale Python Language Reference docs (no walrus).

Brandt Bucher added the comment: Of course. After my PR is merged, you can make another PR that replaces the ".. TODO: BPO-39868" line with a description of how assignment expressions work. Likely much of the language can be borrowed from the PEP. Let me know if you need help with any of

[issue39868] Stale Python Language Reference docs (no walrus).

SHANKAR JHA added the comment: Thank you for that!!! Can you please provide some pointers to what exactly I have to do? -- ___ Python tracker ___

[issue39868] Stale Python Language Reference docs (no walrus).

Change by Brandt Bucher : -- keywords: +patch pull_requests: +18151 stage: -> patch review pull_request: https://github.com/python/cpython/pull/18793 ___ Python tracker ___

[issue39868] Stale Python Language Reference docs (no walrus).

Brandt Bucher added the comment: Sorry, I hadn't seen your comment... :( I've already finished the grammar specification bit, but not the prose description of how assignment expressions work, etc. How about I leave that empty in my PR and you can actually do the documentation part

[issue39868] Stale Python Language Reference docs (no walrus).

SHANKAR JHA added the comment: Can I take this issue? -- nosy: +shankarj67 ___ Python tracker ___ ___ Python-bugs-list mailing

[issue39868] Stale Python Language Reference docs (no walrus).

New submission from Brandt Bucher : It looks like https://docs.python.org/3/reference/expressions.html and https://docs.python.org/3/reference/compound_stmts.html were never updated for named expressions. Because this change has to be backported, it's sort of a blocker for my PEP 614 doc

[issue33347] zlibmodule undefined reference

Martin Ni added the comment: Hello sir! I got exactly same issue when compile some ipk in Openwrt. Would tell how to add "-lz" to python-config? I am not so familiar with Python coding. Thanks! -- nosy: +Martin Ni ___ Python tracker

[issue39831] Reference leak in PyErr_WarnEx()

Ned Deily added the comment: Is the 3.7.x backport (PR 18765) ready to merge? -- nosy: +ned.deily ___ Python tracker ___ ___

[issue39831] Reference leak in PyErr_WarnEx()

Pablo Galindo Salgado added the comment: > It is not so easy for 3.7. Apologies Serhiy, I thought it was more straightforward and just wanted to stop the mail storm that the refleak buildbots were causing :( -- ___ Python tracker

[issue39831] Reference leak in PyErr_WarnEx()

miss-islington added the comment: New changeset 57fb29219f09ee705065e39ad488334a9c7e3d71 by Miss Islington (bot) in branch '3.8': bpo-39831: Remove outdated comment. (GH-18764) https://github.com/python/cpython/commit/57fb29219f09ee705065e39ad488334a9c7e3d71 --

[issue39831] Reference leak in PyErr_WarnEx()

Serhiy Storchaka added the comment: New changeset ae75a294352e9b9487f5dc8e88f068e7e6974dc2 by Serhiy Storchaka in branch 'master': bpo-39831: Remove outdated comment. (GH-18764) https://github.com/python/cpython/commit/ae75a294352e9b9487f5dc8e88f068e7e6974dc2 --

[issue39831] Reference leak in PyErr_WarnEx()

Change by miss-islington : -- nosy: +miss-islington nosy_count: 2.0 -> 3.0 pull_requests: +18129 pull_request: https://github.com/python/cpython/pull/18770 ___ Python tracker

[issue39831] Reference leak in PyErr_WarnEx()

Change by Serhiy Storchaka : -- pull_requests: +18120 pull_request: https://github.com/python/cpython/pull/18765 ___ Python tracker ___

[issue39831] Reference leak in PyErr_WarnEx()

Change by Serhiy Storchaka : -- pull_requests: +18119 stage: -> patch review pull_request: https://github.com/python/cpython/pull/18764 ___ Python tracker ___

[issue39831] Reference leak in PyErr_WarnEx()

Serhiy Storchaka added the comment: It is not so easy for 3.7. -- resolution: fixed -> stage: resolved -> status: closed -> open ___ Python tracker ___

[issue39831] Reference leak in PyErr_WarnEx()

Pablo Galindo Salgado added the comment: Closing this as the backports are merged. Thanks, Serhiy, for finding the leak and for the fix :) -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue39831] Reference leak in PyErr_WarnEx()

Pablo Galindo Salgado added the comment: New changeset 394dc0db878c08d003772de163a57ac12046d865 by Pablo Galindo in branch '3.8': [3.8] bpo-39831: Fix a reference leak in PyErr_WarnEx(). (GH-18750) (GH-18761) https://github.com/python/cpython/commit/394dc0db878c08d003772de163a57ac12046d865

[issue39831] Reference leak in PyErr_WarnEx()

Pablo Galindo Salgado added the comment: New changeset 499c926fbeafa7e4c15d925fea27fe8a65cc3b25 by Pablo Galindo in branch '3.7': [3.7] bpo-39831: Fix a reference leak in PyErr_WarnEx(). (GH-18750). (GH-18760) https://github.com/python/cpython/commit/499c926fbeafa7e4c15d925fea27fe8a65cc3b25

[issue39831] Reference leak in PyErr_WarnEx()

Pablo Galindo Salgado added the comment: I made the backports to 3.7 and 3.8 manually to calm down the refleak buildbots as the automatic backports failed :) -- ___ Python tracker

[issue39831] Reference leak in PyErr_WarnEx()

Change by Pablo Galindo Salgado : -- pull_requests: +18116 pull_request: https://github.com/python/cpython/pull/18761 ___ Python tracker ___

[issue39831] Reference leak in PyErr_WarnEx()

Change by Pablo Galindo Salgado : -- nosy: +pablogsal nosy_count: 1.0 -> 2.0 pull_requests: +18115 pull_request: https://github.com/python/cpython/pull/18760 ___ Python tracker

[issue39831] Reference leak in PyErr_WarnEx()

Serhiy Storchaka added the comment: New changeset 2d2f85517f8216146a2f888d1ad4d765b3be2339 by Serhiy Storchaka in branch 'master': bpo-39831: Fix a reference leak in PyErr_WarnEx(). (GH-18750) https://github.com/python/cpython/commit/2d2f85517f8216146a2f888d1ad4d765b3be2339

[issue39831] Reference leak in PyErr_WarnEx()

Change by Serhiy Storchaka : -- keywords: +patch pull_requests: +18105 stage: -> patch review pull_request: https://github.com/python/cpython/pull/18750 ___ Python tracker

[issue39831] Reference leak in PyErr_WarnEx()

New submission from Serhiy Storchaka : The test added for issue38913 exposed a reference leak in PyErr_WarnEx(). -- components: Interpreter Core messages: 363203 nosy: serhiy.storchaka priority: normal severity: normal status: open title: Reference leak in PyErr_WarnEx() type: resource

[issue17422] language reference should specify restrictions on class namespace

Change by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue17422] language reference should specify restrictions on class namespace

Change by Caleb Donovick : -- pull_requests: +18041 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/18682 ___ Python tracker ___

[issue17422] language reference should specify restrictions on class namespace

Caleb Donovick added the comment: While It is perfectly fine behavior for CPython to use a dict, as dict is an ordered mapping. I think Eric is right that the data model should not specify that a dict is necessarily used in the absence of __prepare__. --

[issue17422] language reference should specify restrictions on class namespace

Guido van Rossum added the comment: As I mentioned in my response on the PR, dict *is* required to be ordered since 3.7. So I think it is okay as is. -- ___ Python tracker

[issue17422] language reference should specify restrictions on class namespace

Eric Snow added the comment: Thanks for working on this. Sorry I didn't get a chance to see your PR sooner. There was one small thing that needs to be changed back, as I implied in my comment on the PR [1]. Please undo the change in the text from "ordered mapping" to "dict". The

[issue17422] language reference should specify restrictions on class namespace

miss-islington added the comment: New changeset 36a120d343c1cb69b8d02913569c153e8bb969c8 by Miss Islington (bot) in branch '3.7': bpo-17422: Language reference should specify restrictions on class namespace (GH-18559) https://github.com/python/cpython/commit

[issue17422] language reference should specify restrictions on class namespace

miss-islington added the comment: New changeset 91ba44623e5cb8f4a7b0d3fc1fab8ff8d8a849c2 by Miss Islington (bot) in branch '3.8': bpo-17422: Language reference should specify restrictions on class namespace (GH-18559) https://github.com/python/cpython/commit

[issue39139] Reference to depricated collections.abc class in collections is unnecessary and confusing

Khalid Mammadov added the comment: Looks like this is covered in greater detail in the other PRs. So, closing the PR and the issue -- stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue39139] Reference to depricated collections.abc class in collections is unnecessary and confusing

Change by Khalid Mammadov : -- resolution: -> duplicate ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue17422] language reference should specify restrictions on class namespace

Change by miss-islington : -- pull_requests: +17976 pull_request: https://github.com/python/cpython/pull/18611 ___ Python tracker ___

[issue17422] language reference should specify restrictions on class namespace

Change by miss-islington : -- pull_requests: +17975 pull_request: https://github.com/python/cpython/pull/18610 ___ Python tracker ___

[issue17422] language reference should specify restrictions on class namespace

Change by Guido van Rossum : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue17422] language reference should specify restrictions on class namespace

Guido van Rossum added the comment: New changeset fbe2e0bb8a7ee75d0f9d57682436dac7d69e202e by ananthan-123 in branch 'master': bpo-17422: Language reference should specify restrictions on class namespace (#18559) https://github.com/python/cpython/commit

[issue6083] Reference counting bug in PyArg_ParseTuple and PyArg_ParseTupleAndKeywords

Tal Einat added the comment: Please do, Ananthakrishnan! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue6083] Reference counting bug in PyArg_ParseTuple and PyArg_ParseTupleAndKeywords

Ananthakrishnan added the comment: I want to do a PR,if this is still needeed. -- nosy: +Ananthakrishnan ___ Python tracker ___ ___

[issue17422] language reference should specify restrictions on class namespace

Ananthakrishnan added the comment: I just addded a PR for this issue. -- nosy: +Ananthakrishnan ___ Python tracker ___ ___

[issue17422] language reference should specify restrictions on class namespace

Change by Ananthakrishnan : -- pull_requests: +17939 pull_request: https://github.com/python/cpython/pull/18559 ___ Python tracker ___

[issue39139] Reference to depricated collections.abc class in collections is unnecessary and confusing

Karthikeyan Singaravelan added the comment: The removal in 3.9 was reverted and postponed to 3.10 in issue39674. -- ___ Python tracker ___

[issue25753] Reference leaks in test_smtplib

Dong-hee Na added the comment: +1 for me to close this issue. On the master branch, this issue is not reproducible. I am closing this issue, if someone wants to open this issue, please re-open this :) -- nosy: +corona10 resolution: -> out of date stage: -> resolved status: open ->

[issue39614] Documentation of attribute reference is unclear

New submission from Dirk Herrmann : Trying to understand attribute reference in Python, I was lost: * In the "Python Language Reference" (I will refer to this as PLR, sorry if that is uncommon, did not find an abbreviation in the glossary): Chapter 6.3.1 is about attribute refer

[issue39451] enum.Enum reference count leaks

Change by hongweipeng : -- nosy: +hongweipeng ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue25753] Reference leaks in test_smtplib

hai shi added the comment: > I cannot reproduce these leaks. I think this issue should be closed. +1, I have run 15+ times in my vm but not found these leaks:( -- nosy: +shihai1991 ___ Python tracker

[issue17422] language reference should specify restrictions on class namespace

Change by Caleb Donovick : -- nosy: +donovick ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39480] referendum reference is needlessly annoying

Change by Raymond Hettinger : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue39480] referendum reference is needlessly annoying

Mark Dickinson added the comment: Speaking as a British, UK-based Python contributor who's unhappy with recent political developments in the UK, I say let's close this. -- nosy: +mark.dickinson ___ Python tracker

[issue39480] referendum reference is needlessly annoying

Change by Aurora : -- type: -> enhancement ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39492] reference cycle affecting Pickler instances (Python3.8+)

Antoine Pitrou added the comment: New changeset 17236873392533ce0c5d7bbf52cbd61bca171c59 by Antoine Pitrou in branch '3.8': [3.8] bpo-39492: Fix a reference cycle between reducer_override and a Pickler instance (GH-18266) (#18316) https://github.com/python/cpython/commit

[issue39492] reference cycle affecting Pickler instances (Python3.8+)

Antoine Pitrou added the comment: Thank you for the PR! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue39492] reference cycle affecting Pickler instances (Python3.8+)

Change by Antoine Pitrou : -- pull_requests: +17692 pull_request: https://github.com/python/cpython/pull/18316 ___ Python tracker ___

[issue39492] reference cycle affecting Pickler instances (Python3.8+)

miss-islington added the comment: New changeset 0f2f35e15f9fbee44ce042b724348419d8136bc5 by Pierre Glaser in branch 'master': bpo-39492: Fix a reference cycle between reducer_override and a Pickler instance (GH-18266) https://github.com/python/cpython/commit

[issue39480] referendum reference is needlessly annoying

Terry J. Reedy added the comment: I concur with Steven and Raymond. The 2016 Brexit votes were Leave 17.4 million and Remain 16.1 million. No resemblence to the hypothetical example. I think that this should be closed as 'not a bug'. -- nosy: +terry.reedy

[issue39492] reference cycle affecting Pickler instances (Python3.8+)

Change by Pierre Glaser : -- keywords: +patch pull_requests: +17643 stage: -> patch review pull_request: https://github.com/python/cpython/pull/18266 ___ Python tracker ___

[issue39492] reference cycle affecting Pickler instances (Python3.8+)

New submission from Pierre Glaser : The new Pickler reducer_override mechanism introduced in `Python3.8` generates a reference cycle: for optimization purposes, a the pickler.reducer_override bound method is referenced into the reducer_override attribute of the Pickler's struct. Thus, until

[issue39480] referendum reference is needlessly annoying

Aurora added the comment: This example is practically against Python's diversity statement. -- nosy: +opensource-assist ___ Python tracker ___

[issue39480] referendum reference is needlessly annoying

Raymond Hettinger added the comment: I concur with Steven. The association with Brexit is specious and the CoC wasn't intended to apply to second guessing technical examples. -- assignee: docs@python -> willingc nosy: +rhettinger, willingc priority: normal -> low

[issue39480] referendum reference is needlessly annoying

Steven D'Aprano added the comment: Oh come on now, this is such a trivialisation of the CoC that I cannot believe that it is a good-faith bug report and not a troll. I'm surprised you didn't toss in the words "triggered" and "micro-aggression" while you're at it. The example has nothing to

[issue39480] referendum reference is needlessly annoying

Change by Fred Drake : -- nosy: +fdrake ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39480] referendum reference is needlessly annoying

Change by Serhiy Storchaka : -- nosy: +akuchling ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39480] referendum reference is needlessly annoying

s) >>> '{:-9} YES votes {:2.2%}'.format(yes_votes, percentage)' 42572654 YES votes 49.67%' -- assignee: docs@python components: Documentation messages: 360883 nosy: diziet, docs@python priority: normal severity: normal status: open title: referendum refe

[issue39451] enum.Enum reference count leaks

Dan Gass added the comment: Sorry for not thinking of trying this sooner. Running garbage collection, import gc; gc.collect(), releases the resources and restores the expected reference counts. >From my perspective, this is satisfactory and could justify closing this bug >

[issue39451] enum.Enum reference count leaks

Change by Raymond Hettinger : -- assignee: -> ethan.furman priority: normal -> low ___ Python tracker ___ ___ Python-bugs-list

[issue37955] mock.patch incorrect reference to Mock

Change by Chris Withers : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

<    2   3   4   5   6   7   8   9   10   11   >