[issue44663] Possible bug in datetime utc

y: normal severity: normal status: open title: Possible bug in datetime utc type: behavior versions: Python 3.9 ___ Python tracker <https://bugs.python.org/issue44663> ___ ___ Pytho

[issue42626] readline history, vi-editingmode and ANSI color codes bug

Andrei Kulakov added the comment: I can't reproduce on MacOS in both Py 3.9.1 and in dev version. Works fine, I can erase everything after '2' and before it. -- nosy: +andrei.avk ___ Python tracker

[issue44619] Bug in Python 3.7.10

Steven D'Aprano added the comment: numpy is a third-party library, you will have to report it to them, we can't do anything about it. -- nosy: +steven.daprano resolution: -> third party stage: -> resolved status: open -> closed ___ Python

[issue44619] Bug in Python 3.7.10

New submission from Prakash : Hello - I wish to bring to your kind notice a bug in Python. Given any matrix X. While trying to compute the CoVariance matrix of that matrix X, Python does NOT compute the CoVarianceof the given matrix X. Instead, Python comptes the CoVariance of the Transpose

[issue44557] It's a bug? Dict

Steven D'Aprano added the comment: This is not a bug. Assignment in Python does not make a copy, it creates a second name for the same object. -- nosy: +steven.daprano resolution: -> not a bug stage: -> resolved status: open -> closed _

[issue44557] It's a bug? Dict

Karthikeyan Singaravelan added the comment: This is not a bug since in this case assignment is referring to the same object and thus mutating one variable reflects change in other variable. Relevant FAQ : https://docs.python.org/3/faq/programming.html#why-did-changing-list-y-also-change

[issue44557] It's a bug? Dict

New submission from Matheus Oliveira : a = {"a":1} b = a a["a"]=33 print(b, a) # {"a":33}, {"a":33} -- components: Interpreter Core messages: 396899 nosy: ymatheus63 priority: normal severity: normal status: open title: It's a bug? Dict t

[issue44538] ast.Slice 3.9.6 documentation bug

Tim added the comment: I was using 3.8. I followed the same steps on 3.9 and confirmed it worked - closing now. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue44538] ast.Slice 3.9.6 documentation bug

Serhiy Storchaka added the comment: What Python version did you tried? -- nosy: +serhiy.storchaka ___ Python tracker ___ ___

[issue44538] ast.Slice 3.9.6 documentation bug

`, `Slice` inherits from `slice` which appears to be a deprecated type. -- assignee: docs@python components: Documentation messages: 396765 nosy: c3-timjbaer, docs@python priority: normal severity: normal status: open title: ast.Slice 3.9.6 documentation bug type: behavior versions: Python

[issue44481] Tkinter config() minor documentation bug for shorthand options

he relieve to 'groove' in order for this to make more sense. Or, instead use example with 2- and 5-tuples. {..., 'fg': ('fg', '-foreground'), ..., 'foreground': ('foreground', 'foreground', 'Foreground', 'SystemButtonText', 'SystemButtonText'), ...} --- Side note: the third me

[issue44481] Tkinter config() minor documentation bug for shorthand options

sy: spirko priority: normal severity: normal status: open title: Tkinter config() minor documentation bug for shorthand options type: behavior versions: Python 3.6, Python 3.9 ___ Python tracker <https://bugs.python.o

Re: How Do I Get A Bug In Multiprocessing Fixed?

On 6/17/2021 5:02 PM, Michael Boom wrote: The below issue is pretty serious and it is preventing me from using a system I wrote on a larger scale. How do I get this bug fixed? Thanks. https://bugs.python.org/issue43329 Reduce your code to the minimum needed to exhibit the problem. Then run

[issue32581] A bug of the write funtion of ConfigParser.py

Irit Katriel added the comment: I trued this on 3.11/Windows and 3.10/Linux and could not reproduce the issue. The Password remained "" in both cases. -- nosy: +iritkatriel resolution: -> out of date stage: -> resolved status: open -> closed ___

Re: How Do I Get A Bug In Multiprocessing Fixed?

On Fri, 18 Jun 2021 at 15:27, Michael Boom wrote: > The below issue is pretty serious and it is preventing me from using a > system I wrote on a larger scale. How do I get this bug fixed? Thanks. > https://bugs.python.org/issue43329 On Fri, 18 Jun 2021 at 06:07, Alexander Neils

Re: How Do I Get A Bug In Multiprocessing Fixed?

der\AppData\Local\Programs\Python\Python37\lib\multiprocessing\connection.py", > line 492, in Client >c = SocketClient(address) > File > "C:\Users\Alexander\AppData\Local\Programs\Python\Python37\lib\multiprocessing\connection.py", > line 619, in SocketCl

Re: How Do I Get A Bug In Multiprocessing Fixed?

ing me from using a > system I wrote on a larger scale. How do I get this bug fixed? Thanks. > https://bugs.python.org/issue43329 > -- > https://mail.python.org/mailman/listinfo/python-list > -- https://mail.python.org/mailman/listinfo/python-list

How Do I Get A Bug In Multiprocessing Fixed?

The below issue is pretty serious and it is preventing me from using a system I wrote on a larger scale. How do I get this bug fixed? Thanks. https://bugs.python.org/issue43329 -- https://mail.python.org/mailman/listinfo/python-list

[issue44374] PyThreadState_IsCurrent bug under building Python with --with-experimental-isolated-subinterpreters

onents: Subinterpreters messages: 395517 nosy: JunyiXie, vstinner priority: normal severity: normal status: open title: PyThreadState_IsCurrent bug under building Python with --with-experimental-isolated-subinterpreters versions: Python 3.11 ___ Python tracker &

Re: Neither pdb or print() displays the bug [FIXED]

On Tue, 1 Jun 2021, Rich Shepard wrote: I'm stuck with neither approach (pdb, print()) working. I moved the database code to a separate module, datasource.py, and when I run the activitytypes.py module (using pdb and having entered print() statements at various places in both the datasource and

Re: Neither pdb or print() displays the bug

On Sun, 6 Jun 2021, Fabio Zadrozny wrote: Hint: you should be able to use https://pypi.org/project/pytest-qt/ to unit-test a PyQt application... Fabio, Thank you for confirming this. I hadn't remembered the name so your URL is really helpful. Regards, Rich --

Re: Neither pdb or print() displays the bug

Em qua., 2 de jun. de 2021 às 09:34, Rich Shepard escreveu: > On Wed, 2 Jun 2021, Peter Otten wrote: > > > Do you have unit tests? Those are an excellent tool to ensure that the > > components of an application work as expected and that those components > > have well-defined interfaces.

[issue29249] Pathlib glob ** bug

Change by Christian Heimes : -- nosy: -christian.heimes ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue29249] Pathlib glob ** bug

Change by Barney Gale : -- nosy: +barneygale ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue29249] Pathlib glob ** bug

Change by wim glenn : -- nosy: +wim.glenn ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

Re: Interpreter Bug

> On 2 Jun 2021, at 10:34, Alice Braim wrote: > > Good morning- > > > > I am having some very serious issues with Python, and I was hoping you > could help? > > I downloaded both Python and PyCharm, and the 2 do not seem to be working. > Every time I select Python as an

Interpreter Bug

Good morning- I am having some very serious issues with Python, and I was hoping you could help? I downloaded both Python and PyCharm, and the 2 do not seem to be working. Every time I select Python as an interpreter, the whole thing crashes. Obviously, I went onto repairs,

Re: Neither pdb or print() displays the bug

On Wed, 2 Jun 2021, Peter Otten wrote: Do you have unit tests? Those are an excellent tool to ensure that the components of an application work as expected and that those components have well-defined interfaces. Debugging a failing unittest is usually easier than to debug a complex application.

Re: Neither pdb or print() displays the bug

On 01/06/2021 23:32, Rich Shepard wrote: On Tue, 1 Jun 2021, Ethan Furman wrote: Well, you only had two logging statements in that code -- logging is like print: if you want to see it, you have to call it: Ethan, Got it, thanks. I believe Do you have unit tests? Those are an excellent

Re: Neither pdb or print() displays the bug

tivitytypes.py(32)()->None > -> app.exec_() > (Pdb) n I'm not sure why you got that twice. I'd expect you to only see it once. > > and there it sits. No (Pdb) prompt, nothing. And no printed statements. It's waiting while the app runs and for you to terminate it. > I'd appreciate recommendations

Re: Neither pdb or print() displays the bug

On Tue, 1 Jun 2021, Dennis Lee Bieber wrote: I suspect you really should be stepping INTO the calls, not just invoking the functions completely and going to the next LOCAL statement. $ /development/business_tracker/activitytypes.py(1)() -> import sys (Pdb) s $

Re: Neither pdb or print() displays the bug

On Tue, 1 Jun 2021, Ethan Furman wrote: Well, you only had two logging statements in that code -- logging is like print: if you want to see it, you have to call it: Ethan, Got it, thanks. I believe my problem is with the datasource module. I'm focused on making it work (using logging to

Re: Neither pdb or print() displays the bug

On 6/1/21 1:42 PM, Rich Shepard wrote: > When I run it this is the output: > $ python activitytypes.py 2021-06-01 13:39:10,219 -DEBUG - Start of Program > 2021-06-01 13:39:15,229 -DEBUG - End of Program Well, you only had two logging statements in that code -- logging is like print: if you

Re: Neither pdb or print() displays the bug

On Tue, 1 Jun 2021, Ethan Furman wrote: Sounds like a console issue. Try using `logging` with a file... you could even use `print` with a file if you wanted to. Ethan, Not before using logging I found a reference/example page

Re: Neither pdb or print() displays the bug

On Tue, 1 Jun 2021, Rich Shepard wrote: The QSize() statement is never reached. Correction: the window is 800 x 600, but it's still empty. Rich -- https://mail.python.org/mailman/listinfo/python-list

Re: Neither pdb or print() displays the bug

On 6/1/21 1:18 PM, Rich Shepard wrote: > I'd appreciate recommendations on the process to find where the bug lives > since I can't seem to find it with print() or line-by-line in pdb. Sounds like a console issue. Try using `logging` with a file... you could even use `print` with a file

Neither pdb or print() displays the bug

on the process to find where the bug lives since I can't seem to find it with print() or line-by-line in pdb. TIA, Rich -- https://mail.python.org/mailman/listinfo/python-list

[issue44216] Bug in class method with optional parameter

Steven D'Aprano added the comment: This is not a bug, this is working as the language is designed, and the behaviour occurs for all functions, not just class methods. Default values are only evaluated once, when the function is defined, not every time the function is called. This is even

[issue44216] Bug in class method with optional parameter

William Pickard added the comment: This is not a bug but a side-affect at how defaulted parameters are stored. The rule of thumb is to never use mutable values as default values for parameters. When a method is created in the Python runtime, it checks if the signature has defaulted keyword

[issue44216] Bug in class method with optional parameter

we append 'a' directly to 'b'. Instead, if we create a copy of parameter 'b', and append 'a' to the copy, there are no such side effects -- messages: 394199 nosy: shevaleashish priority: normal severity: normal status: open title: Bug in class method with optional parameter type: behavio

[issue44152] [not a bug] .isupper() does not support Polytonic Greek (but .islower() does)

Change by Jelle Zijlstra : -- stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue44152] [not a bug] .isupper() does not support Polytonic Greek (but .islower() does)

E G added the comment: Oops: this is not a bug. The isupper() method tests ALL chars. Only the first char in the examples was a capital. All of the logic/tests succeed. Sorry for the error. Thanks to Serhiy S. for swift attention on this. -- resolution: -> not a bug ti

[issue44139] Unparenthesized tuple doc bug in what's new

Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue44139] Unparenthesized tuple doc bug in what's new

Pablo Galindo Salgado added the comment: New changeset 67729a91a5fe6ad06fb5f2cc4f91ad99876e431a by Miss Islington (bot) in branch '3.10': bpo-44139: Use a more descriptive syntax error comprehension case in the What's New for 3.10 (GH-26145) (GH-26146)

[issue44139] Unparenthesized tuple doc bug in what's new

Change by miss-islington : -- nosy: +miss-islington nosy_count: 3.0 -> 4.0 pull_requests: +24782 stage: -> patch review pull_request: https://github.com/python/cpython/pull/26146 ___ Python tracker

[issue44139] Unparenthesized tuple doc bug in what's new

Pablo Galindo Salgado added the comment: Great idea, I have opened a PR to change it -- stage: patch review -> ___ Python tracker ___

[issue44139] Unparenthesized tuple doc bug in what's new

Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +24781 stage: -> patch review pull_request: https://github.com/python/cpython/pull/26145 ___ Python tracker

[issue44139] Unparenthesized tuple doc bug in what's new

Change by Ned Deily : -- nosy: +pablogsal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44139] Unparenthesized tuple doc bug in what's new

the great work on making error messages better! This prof. who often has to help students with Python errors heartily approves! -- assignee: docs@python components: Documentation messages: 393704 nosy: docs@python, mscuthbert priority: normal severity: normal status: open title: Unparenth

[issue35663] webbrowser.py firefox bug [python3, windows 10]

Gregory P. Smith added the comment: Others are reporting this works. if that is not true on the most recent python 3.9 release, please reopen with more detailed reproduction instructions. -- nosy: +gregory.p.smith resolution: -> works for me stage: -> needs patch status: open ->

[issue35663] webbrowser.py firefox bug [python3, windows 10]

pavan kumar punna added the comment: Your code is working fine on windows 10 64-bit and returning True as it opens firefox. python-3.9.2. The issue should be closed. -- nosy: +punnapavankumar9 ___ Python tracker

[issue44018] Bug in random.seed

Shreyan Avigyan added the comment: One solution to these would be making a copy of the parameter using copy.deepcopy and then performing operations on that copy. (The downside of this solution is that it will change the behavior.) -- nosy: +shreyanavigyan

[issue44018] Bug in random.seed

Miguel Brito added the comment: The problem is that random seed will do ``` if isinstance(a, str): a = a.encode() a += _sha512(a).digest() a = int.from_bytes(a, 'big') ``` and that will modify the bytearray in place. >>> a =

[issue44018] Bug in random.seed

Eugene Rossokha added the comment: I find the following behaviour very confusing: >>> import random >>> a = bytearray("1234", "utf-8") >>> b = bytearray("1234", "utf-8") >>> a == b True >>> random.seed(a) >>> a == b False >>> a

[issue44018] Bug in random.seed

Raymond Hettinger added the comment: I don't see a bug here. As documented, "a str, bytes, or bytearray object gets converted to an int and all of its bits are used." The various input types are converted to an integer and it doesn't really matter how it is do

[issue44018] Bug in random.seed

Change by Karthikeyan Singaravelan : -- nosy: +mark.dickinson, rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue44018] Bug in random.seed

: arjaz priority: normal severity: normal status: open title: Bug in random.seed versions: Python 3.9 ___ Python tracker <https://bugs.python.org/issue44018> ___ ___ Python-bug

[issue27820] Possible bug in smtplib when initial_response_ok=False

Senthil Kumaran added the comment: Please open a new issue. It has better chances of being fixed quickly. On Mon, Apr 26, 2021 at 10:02 PM junpengruan wrote: > > junpengruan <632077...@qq.com> added the comment: > > Hi > I think there is another bug when initial_re

[issue27820] Possible bug in smtplib when initial_response_ok=False

junpengruan <632077...@qq.com> added the comment: Hi I think there is another bug when initial_response_ok=False. When using AUTH PLAIN, the server will response like: -- C: AUTH PLAIN S: 334 ok. go on -- and it's not base64 encoding, while in th

[issue20290] inspect module bug for modules with same filename

Change by Irit Katriel : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> inspect.findsource raises IndexError ___ Python tracker ___

[issue43907] pickle.py bytearray memoization bug with protocol 5

Antoine Pitrou added the comment: Thanks for the report and fix! -- components: +Library (Lib) resolution: -> fixed stage: patch review -> resolved status: open -> closed type: -> behavior versions: +Python 3.10 ___ Python tracker

[issue43907] pickle.py bytearray memoization bug with protocol 5

Antoine Pitrou added the comment: New changeset 1e9f0933095403b215c2c4a0be7915d034ff7026 by Carl Friedrich Bolz-Tereick in branch 'master': bpo-43907: add missing memoize call in pure python pickling of bytearray (GH-25501)

Re: The split() function of Python's built-in module has changed in a puzzling way - is this a bug?

ption of the > function in the split documentation, and it is also strange that after > replacing * with +, the behavior is still the same as in 3.6.8. > >1. why is this change not in the documentation? Is it because I didn’t >find it? > 2. Why did the be

Re: The split() function of Python's built-in module has changed in a puzzling way - is this a bug?

ior is still the same as in 3.6.8. 1. why is this change not in the documentation? Is it because I didn’t find it? 2. Why did the behavior change this way? Was a bug introduced, or was it a bug fix? -- https://mail.python.org/mailman/listinfo/python-list

[issue43919] Potential bug in the "request" package.

Karthikeyan Singaravelan added the comment: The tracker is for issues related to CPython. requests is not part of stdlib so I am closing this as a third party issue. It seems this was already raised in requests repo https://github.com/psf/requests/issues/3017 . -- nosy: +xtreak

[issue43919] Potential bug in the "request" package.

any data as it probably the new URL with the added space was the issue. I think this is a bug and the URL should be checked from any possible empty strings, especially in the end and in the start of the URL. -- components: Extension Modules files: bug.PNG messages: 391658 nosy: edgj4718

The split() function of Python's built-in module has changed in a puzzling way - is this a bug?

as in 3.6.8. 1. why is this change not in the documentation? Is it because I didn’t find it? 2. Why did the behavior change this way? Was a bug introduced, or was it a bug fix? -- https://mail.python.org/mailman/listinfo/python-list

[issue43907] pickle.py bytearray memoization bug with protocol 5

Change by Karthikeyan Singaravelan : -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43907] pickle.py bytearray memoization bug with protocol 5

Change by Carl Friedrich Bolz-Tereick : -- keywords: +patch pull_requests: +24221 stage: -> patch review pull_request: https://github.com/python/cpython/pull/25501 ___ Python tracker

[issue43907] pickle.py bytearray memoization bug with protocol 5

edrich.Bolz priority: normal severity: normal status: open title: pickle.py bytearray memoization bug with protocol 5 ___ Python tracker <https://bugs.python.org/issue43907> ___ _

[issue40804] Bug report in python3.6.8 using argparse module

code that demonstrates the problem. There is some documentation on bug reporting that might be helpful: https://docs.python.org/3/bugs.html#using-the-python-issue-tracker -- nosy: +iritkatriel resolution: -> rejected stage: -> resolved status: open -&g

[issue43630] unittest use dir(module) to load test cases. Run unittest file by _PyRun_SimpleFileObject, have bug

ttest file by _PyRun_SimpleFileObject, have bug ___ Python tracker <https://bugs.python.org/issue43630> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/opt

[issue43512] Bug in isinstance(instance, cls) with cls being a protocol? (PEP 544)

Change by Paul : -- nosy: +Jukka Lehtosalo, lukasz.langa ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43512] Bug in isinstance(instance, cls) with cls being a protocol? (PEP 544)

Paul added the comment: @kj Thank you, Ken! I'll try it on the list as advised by you! -- ___ Python tracker ___ ___

[issue43512] Bug in isinstance(instance, cls) with cls being a protocol? (PEP 544)

Ken Jin added the comment: @paul-dest Anyone can add them using the bug tracker Web interface in the "Nosy List" field above the message box. Yes they will receive a notification. Adding people sends them an email and subscribes them to this issue (even if closed). I don't kno

[issue43512] Bug in isinstance(instance, cls) with cls being a protocol? (PEP 544)

Paul added the comment: The authors of PEP 544 are Ivan Levkivskyi, Jukka Lehtosalo, and Łukasz Langa. I think their opinion should count. I can see "levkivskyi" in the noisy list, but not the other two. And don't see any possibility to add them. Who can add them? And if added: will they

[issue43512] Bug in isinstance(instance, cls) with cls being a protocol? (PEP 544)

Guido van Rossum added the comment: To be honest, I just don’t have time to deal,with this, so I’m hoping some other core dev has an opinion. But I can’t help you find one either. Sorry, but that’s the reality of open source development. -- --Guido (mobile) --

[issue43512] Bug in isinstance(instance, cls) with cls being a protocol? (PEP 544)

Paul added the comment: Regarding "At runtime, protocol classes will be simple ABCs." (PEP 544): Unfortunately, this is currently not the case. Actually, there is an extra metaclass for protocols, solely to provide an __instancecheck__.

[issue43512] Bug in isinstance(instance, cls) with cls being a protocol? (PEP 544)

Guido van Rossum added the comment: Yes, discussion on a close issue is still read, unless people explicitly unsubscribe (which they rarely do unless the chatter is spam). -- ___ Python tracker

[issue43512] Bug in isinstance(instance, cls) with cls being a protocol? (PEP 544)

Paul added the comment: That's the very first issue I've reported in bugs.python.org and I'm completely new to the Python dev process: I have some further remarks at the issue (especially about consistency with the current treatment of Protocols vs. ABCs). Will they be read if placed here

[issue43512] Bug in isinstance(instance, cls) with cls being a protocol? (PEP 544)

o indicate mandatory features. For attributes, there is no guarantee. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker <https://bugs

[issue43512] Bug in isinstance(instance, cls) with cls being a protocol? (PEP 544)

Ken Jin added the comment: Apologies if I misunderstood something, but doesn't PEP 544 also state in its "Rationale", "Non-goals" subsection that """ At runtime, protocol classes will be simple ABCs. There is no intent to provide sophisticated runtime instance and class checks against

[issue43512] Bug in isinstance(instance, cls) with cls being a protocol? (PEP 544)

ce P did not provide a default value pass assert isinstance(C(), P) # violates the PEP 544 requirement cited above C().pm # raises: AttributeError: 'C' object has no attribute 'pm' ``` -- components: Library (Lib) messages: 388827 nosy: paul-dest priority: normal severity: normal sta

[issue43491] Windows filepath bug

parsa mpsh added the comment: Yes. i checked it more. looks problem was from other thing, not the path. -- ___ Python tracker ___

[issue43491] Windows filepath bug

e complete traceback, I may be able to help diagnose the problem, but not here. Please ask for help on https://discuss.python.org/c/users or https://mail.python.org/mailman/listinfo/python-list. -- nosy: +eryksun resolution: -> not a bug stage: -> resol

[issue43491] Windows filepath bug

Change by parsa mpsh : -- components: +IO ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43491] Windows filepath bug

parsa mpsh added the comment: I think this bug should be fixed by converting all of `/`s to `\` in file paths automatic **When os is windows**. -- ___ Python tracker <https://bugs.python.org/issue43

[issue43491] Windows filepath bug

parsa mpsh added the comment: Update: i only tested this bug in `3.6` and `3.7` i'm not sure about newer versions. but i think this bug also is in them. -- ___ Python tracker <https://bugs.python.org/issue43

[issue43491] Windows filepath bug

New submission from parsa mpsh : I was testing my program in github workflow and i detected a bug. i was opening a file in windows: ``` f = open(os.path.dirname(__FILE__) + '/some/file.txt') ``` means the file path will be `C:\some\path/some/file.txt`. but i received OSError. why? because

[issue43441] [Subinterpreters]: global variable next_version_tag cause method cache bug

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

[issue43441] [Subinterpreters]: global variable next_version_tag cause method cache bug

STINNER Victor added the comment: New changeset 75048c8a38005845f10f8cb1dd33a31e0052cae0 by junyixie in branch 'master': bpo-43441: Fix _PyType_ClearCache() for subinterpreters (GH-24822) https://github.com/python/cpython/commit/75048c8a38005845f10f8cb1dd33a31e0052cae0 -- nosy:

[issue27820] Possible bug in smtplib when initial_response_ok=False

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

[issue27820] Possible bug in smtplib when initial_response_ok=False

Senthil Kumaran added the comment: New changeset 8cadc2c9cacfa1710cb5ca28a70f7782cacf09aa by Senthil Kumaran in branch '3.8': [3.8] bpo-27820: Fix AUTH LOGIN logic in smtplib.SMTP (GH-24118) (#24833) https://github.com/python/cpython/commit/8cadc2c9cacfa1710cb5ca28a70f7782cacf09aa

[issue27820] Possible bug in smtplib when initial_response_ok=False

Senthil Kumaran added the comment: New changeset 32717b982d3347e30ae53eb434e2a32e0d03d51e by Miss Islington (bot) in branch '3.9': bpo-27820: Fix AUTH LOGIN logic in smtplib.SMTP (GH-24118) (#24832) https://github.com/python/cpython/commit/32717b982d3347e30ae53eb434e2a32e0d03d51e

[issue27820] Possible bug in smtplib when initial_response_ok=False

Change by Senthil Kumaran : -- pull_requests: +23599 pull_request: https://github.com/python/cpython/pull/24833 ___ Python tracker ___

[issue27820] Possible bug in smtplib when initial_response_ok=False

Change by miss-islington : -- nosy: +miss-islington nosy_count: 8.0 -> 9.0 pull_requests: +23598 pull_request: https://github.com/python/cpython/pull/24832 ___ Python tracker

[issue27820] Possible bug in smtplib when initial_response_ok=False

Senthil Kumaran added the comment: New changeset 7591d9455eb37525c832da3d65e1a7b3e6dbf613 by Pandu E POLUAN in branch 'master': bpo-27820: Fix AUTH LOGIN logic in smtplib.SMTP (GH-24118) https://github.com/python/cpython/commit/7591d9455eb37525c832da3d65e1a7b3e6dbf613 --

[issue43441] [Subinterpreters]: global variable next_version_tag cause method cache bug

junyixie added the comment: under building Python with --with-experimental-isolated-subinterpreters -- ___ Python tracker ___ ___

[issue43441] [Subinterpreters]: global variable next_version_tag cause method cache bug

junyixie added the comment: This is a simple fix. https://github.com/python/cpython/pull/24822/commits/e61ce1dd28a48534ee497aaacb4439193bedfd42 -- ___ Python tracker ___

[issue43441] [Subinterpreters]: global variable next_version_tag cause method cache bug

Change by junyixie : -- keywords: +patch pull_requests: +23588 stage: -> patch review pull_request: https://github.com/python/cpython/pull/24822 ___ Python tracker ___

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