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

Change by junyixie : -- components: +Subinterpreters -Interpreter Core title: mutilcorevm: global variable next_version_tag cause method cache bug -> [Subinterpreters]: global variable next_version_tag cause method cache bug ___ Python trac

[issue27820] Possible bug in smtplib when initial_response_ok=False

Pandu E POLUAN added the comment: Hi Senthil, You're right, it does need a guard. According to my knowledge there is no AUTH mechanism that will send more than 3 challenges; they should fail afterwards with 535 or similar. Servers that don't do that should be considered buggy/broken. So

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

Change by junyixie : -- type: -> crash ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue27820] Possible bug in smtplib when initial_response_ok=False

Senthil Kumaran added the comment: Hello Pandu, Thank you for this patch and the explanation. Does client blocking on repeated challenge from the server (using of while loop) look okay here? The conversation here indicates to me that it is fine. Is there any recommendation or

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

junyixie added the comment: fix: only main interpreter fini, clear method cache. void _PyType_Fini(PyInterpreterState *interp) { if (_Py_IsMainInterpreter(interp)) { clear_slotdefs(); _PyType_ClearCache(>type_cache); } } when python4.0? type isolate, each interpreter

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

junyixie added the comment: when sub interpreter finalize. _PyType_ClearCache set next_version_tag = 0. Type shared between interpreters. another interpreter assign_version_tag "1" for a type, the type is first assign. the dealloc interpreter had assign_version_tag "1" for another type.

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

New submission from junyixie : type->tp_version_tag = next_version_tag++; when sub interpreters parallel, next_version_tag++ is thread-unsafe. may cause different type has same tp_version_tag. cause method cache bug in _PyType_Lookup #define MCACHE_HASH_METHOD(type, n

[issue43366] Unclosed bracket bug in code.interact prevents identifying syntax errors

Change by Pablo Galindo Salgado : -- nosy: +lys.nikolaou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43366] Unclosed bracket bug in code.interact prevents identifying syntax errors

Pablo Galindo Salgado added the comment: > "If mode is 'repl', compile returns None to indicate that the code is > incomplete as is but might become valid if more lines (or maybe just more > code) were added" That would be ideal, but my guess is that is not trivial because even if you can

[issue43366] Unclosed bracket bug in code.interact prevents identifying syntax errors

Terry J. Reedy added the comment: Add compile(..., mode='repl')? "If mode is 'repl', compile returns None to indicate that the code is incomplete as is but might become valid if more lines (or maybe just more code) were added" Deprecate _maybe_compile (and stop trying to patch it).

[issue43366] Unclosed bracket bug in code.interact prevents identifying syntax errors

Pablo Galindo Salgado added the comment: In any case, the underlying problem here is the fact that codeop is deciding to continue asking for input of not depending on the repr() of the syntax error exception itself, which is the major hack here. Previously, it worked because for unclosed

[issue43366] Unclosed bracket bug in code.interact prevents identifying syntax errors

Pablo Galindo Salgado added the comment: > Maybe we need to add an API (e.g. a flag to compile()) so that we can ask the > actual parser the question we're interested in, rather than having to use > hacks and heuristics? I was thinking about that, but we need to fix some inconsistencies

[issue43366] Unclosed bracket bug in code.interact prevents identifying syntax errors

Guido van Rossum added the comment: Maybe we need to add an API (e.g. a flag to compile()) so that we can ask the actual parser the question we're interested in, rather than having to use hacks and heuristics? -- ___ Python tracker

[issue43366] Unclosed bracket bug in code.interact prevents identifying syntax errors

Pablo Galindo Salgado added the comment: This is a change I implemented and is explicitly deactivated in the reprl: https://github.com/python/cpython/blob/master/Parser/pegen.c#L1191 The problem here is that when you call compile() there is no way to know if you are doing it to simulate a

[issue43366] Unclosed bracket bug in code.interact prevents identifying syntax errors

Terry J. Reedy added the comment: #43163 was about the opposite problem of raising SyntaxError too soon, when a valid continuation to imcomplete code is possible. As with that issue, IDLE has the same problem, which is not in code.interact() itself but in codeop._maybe_compile.. Calling

[issue28259] Ctypes bug windows

as not a bug. ctypes and libffi have been used in a broad range of cases in 32-bit Windows for many years, and I wasn't able to reproduce the problem with a function of the given call signature when I checked in 2016. -- resolution: -> not a bug stage: test needed -> resolved status

[issue43366] Unclosed bracket bug in code.interact prevents identifying syntax errors

Andre Roberge added the comment: I understand the challenge of reproducing the behaviour of the Python interpreter for this case. If it cannot be reproduced, then the documentation for https://docs.python.org/3/library/code.html#code.InteractiveConsole.interact and others on that page

[issue43289] step bug in turtle's for loop

the message being > responded to, so it does not get repeated when posted to the web page. > > -- > nosy: +terry.reedy > resolution: -> not a bug > stage: -> resolved > status: open -> closed > > ___

[issue43289] step bug in turtle's for loop

: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue43289> ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue27820] Possible bug in smtplib when initial_response_ok=False

Pandu E POLUAN added the comment: PR available on GitHub and it's already more than one month since the PR was submitted, so I'm pinging this issue. -- ___ Python tracker

[issue22302] Windows os.path.isabs UNC path bug

Eryk Sun added the comment: > figure out whether to do `Path.cwd() / path` Thus a UNC path is absolute, i.e. any path that starts with 2 or more slashes, and all other paths are relative unless they have both a drive and a root. For example: def isabs(s): """Test whether a path

Re: Bug report

On 24/02/2021 22:03, Dan Stromberg wrote: On Wed, Feb 24, 2021 at 12:58 PM Peter Otten <__pete...@web.de> wrote: On 24/02/2021 20:36, Carla Molina wrote: This is not a bug. Have a look at the array's dtype: >>> n = 60461826 >>> a = np.array([1, 50, 100, 150, 200,

Re: Bug report

On Wed, Feb 24, 2021 at 12:58 PM Peter Otten <__pete...@web.de> wrote: > On 24/02/2021 20:36, Carla Molina wrote: > This is not a bug. Have a look at the array's dtype: > > >>> n = 60461826 > >>> a = np.array([1, 50, 100, 150, 200, 250, 300]) > >>

Re: Bug report

14285715 So the difference is tiny for me, and can be imputed to rounding error. Multiplying the big terms first before dividing naturally gives less rounding error. As far as why your install is having problems, I don't really know. What version of numpy are you using? On Wed, Feb 24, 2021 at 12

Re: Bug report

On 24/02/2021 20:36, Carla Molina wrote: I found the following bug (python 3.9.1) when multiplying an array by several variables without parentheses; look at the following example: import numpy as np NR = 0.25 N = 60461826 initialINCIDENCE = np.array([1, 50, 100, 150, 200, 250, 300

Bug report

I found the following bug (python 3.9.1) when multiplying an array by several variables without parentheses; look at the following example: import numpy as np NR = 0.25 N = 60461826 initialINCIDENCE = np.array([1, 50, 100, 150, 200, 250, 300]) initialINCIDENCE = initialINCIDENCE*N/(10*7*NR

[issue43289] step bug in turtle's for loop

> dot(5*rad, col[index % 2]) > > In the future, I would suggest asking questions like this on > StackOverflow, since this is not a bug in Python itself. > > -- > nosy: +Dennis Sweeney > &g

[issue43289] step bug in turtle's for loop

0, so col[rad % 2] is always "black". You could try: for index, rad in enumerate(range(40, 0, -2)): dot(5*rad, col[index % 2]) In the future, I would suggest asking questions like this on StackOverflow, since this is not a bug in Python itself. -- n

[issue43289] step bug in turtle's for loop

Yehuda Katz added the comment: Correction to my msg387472: Every *even* step crashes the code. -- ___ Python tracker ___ ___

[issue43289] step bug in turtle's for loop

uda priority: normal severity: normal status: open title: step bug in turtle's for loop type: behavior versions: Python 3.9 ___ Python tracker <https://bugs.python.org/issue43289> ___ __

[issue29249] Pathlib glob ** bug

Julien Palard added the comment: I'm +1 on adding ** to match. My first bet would be to add it to match, not adding a new method, nor a flag, as it should not break compatibility: It would only break iif someone have a `**` in a match AND does *not* expect it to be recursive (as it would

[issue43157] Bug in methods of creating the 2d list

Steven D'Aprano added the comment: There is also an FAQ about this: https://docs.python.org/3/faq/programming.html#how-do-i-create-a-multidimensional-list See also: https://docs.python.org/3/faq/programming.html#why-did-changing-list-y-also-change-list-x By the way, for future bug reports

[issue43157] Bug in methods of creating the 2d list

Steven D'Aprano added the comment: This is not a bug, it is working correctly, as designed. List multiplication does not *copy* the list, it replicates the reference to the same list object. So [[0]]*5 does not make five different sublists, but the same list repeated five times. Exactly

[issue43157] Bug in methods of creating the 2d list

sandeep kumar added the comment: def generateMatrix(A): d=A-1 data=1 B=[[0]*A]*A for l in range(int(A/2)): i=l j=l for a in range(d): B[i][j]=data print("{0}:{1}:{2}".format(i,j,B[i][j]),end=" ") data+=1

[issue43157] Bug in methods of creating the 2d list

Change by sandeep kumar : -- title: Bug in methods of creating the list -> Bug in methods of creating the 2d list ___ Python tracker <https://bugs.python.org/issu

[issue43157] Bug in methods of creating the list

nd getting wrong output . A is positive integer. ##If i'm using for i in range(A-1): B.append([0]*A) then i'm getting correct output. but the 2d list generated using both the approach are same. 2d list from approach 1== 2d list from approach 2 --->it is true -- messages: 386602 nosy:

[issue40070] GCC crashed on AMD64 RHEL7 LTO + PGO 3.7 (compiler bug)

STINNER Victor added the comment: I didn't see the compiler bug recently, and Python 3.7 no longer accept bug fixes anymore. -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker <https://bug

[issue42989] Bug

majority of syntax errors are problems in user code, not Python itself. This is not a forum for getting help with your own program, but you can try out discuss.python.org or the python-l...@python.org mailing list for that. -- resolution: -> not a bug stage: -> resolved status

[issue42989] Bug

New submission from Andrew C : if playerChoice == "2": reports the ":" as a "syntax error" -- components: Windows messages: 385427 nosy: ASCRong, paul.moore, steve.dower, tim.golden, zach.ware priority: normal severity: normal status: open title: Bug type:

[issue42944] random.Random.sample bug when counts is not None

Raymond Hettinger added the comment: Thanks for the report and the PR. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue42944] random.Random.sample bug when counts is not None

Raymond Hettinger added the comment: New changeset a90539f5723a4c34430761be8cba97daa8474abf by Miss Islington (bot) in branch '3.9': bpo-42944 Fix Random.sample when counts is not None (GH-24235) (GH-24243) https://github.com/python/cpython/commit/a90539f5723a4c34430761be8cba97daa8474abf

[issue42944] random.Random.sample bug when counts is not None

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

[issue42944] random.Random.sample bug when counts is not None

Raymond Hettinger added the comment: New changeset f7b5bacd7a0b2084ce699eda6f6f4b1adfa16590 by jonanifranco in branch 'master': bpo-42944 Fix Random.sample when counts is not None (GH-24235) https://github.com/python/cpython/commit/f7b5bacd7a0b2084ce699eda6f6f4b1adfa16590 --

[issue42944] random.Random.sample bug when counts is not None

Jon FRANCO added the comment: PR submitted. Let me know if I missed something, this is also my first PR. Regards. -- ___ Python tracker ___

[issue42944] random.Random.sample bug when counts is not None

Change by Jon FRANCO : -- keywords: +patch pull_requests: +23058 stage: -> patch review pull_request: https://github.com/python/cpython/pull/24235 ___ Python tracker ___

[issue42944] random.Random.sample bug when counts is not None

Raymond Hettinger added the comment: Would you like to submit a PR for this? -- ___ Python tracker ___ ___ Python-bugs-list

[issue42944] random.Random.sample bug when counts is not None

Change by Raymond Hettinger : -- assignee: -> rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue42944] random.Random.sample bug when counts is not None

New submission from Jon FRANCO : Hello, If I am reading right, random.Random.sample method has a bug if counts is not None. Line 482 (of master): """ selections = sample(range(total), k=k) """ this is calling the module function 'sample' and

[issue27820] Possible bug in smtplib when initial_response_ok=False

Change by Pandu E POLUAN : -- components: +Tests ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue42890] bug float to int

Christian Heimes added the comment: Rounding errors are to be expected. Python uses IEEE-754 double precision floats. See https://docs.python.org/3/tutorial/floatingpoint.html -- nosy: +christian.heimes resolution: -> not a bug stage: -> resolved status: open -> cl

[issue42890] bug float to int

> print("float=%f, float_2=%f, int(float_2)=%d" % (f, f2, int(f2))) float=0.001234, float_2=123400.00, int(float_2)=123399 -- components: Library (Lib) messages: 384807 nosy: wlodek priority: normal severity: normal status: open title: bug float to int versions: Python

[issue27820] Possible bug in smtplib when initial_response_ok=False

Change by Pandu E POLUAN : -- keywords: +patch pull_requests: +22948 stage: -> patch review pull_request: https://github.com/python/cpython/pull/24118 ___ Python tracker ___

[issue27820] Possible bug in smtplib when initial_response_ok=False

Pandu E POLUAN added the comment: Okay, I finally figured out what's wrong. This piece of code in `test_smtplib.py`: if self.smtp_state == self.AUTH: line = self._emptystring.join(self.received_lines) print('Data:', repr(line), file=smtpd.DEBUGSTREAM)

[issue15106] Potential Bug in errors.c

Change by Pablo Galindo Salgado : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue15106] Potential Bug in errors.c

Pablo Galindo Salgado added the comment: Adding extra checks to PyErr_SetExcInfo doesn't have a lot of value because is already out of of contract. If you pass an invalid object (let's say a list) to any of the specific APIs (like PyDict_GetItem) it will crash anyway. We could add some

[issue15106] Potential Bug in errors.c

stack). If there is a bug here, I think it is the silent conversion of traceback to NULL in the case where it is neither NULL nor Py_None. (The case in PyErr_Restore that the comment says should not happen). Otherwise, the difference is that PyErr_Restore transforms Py_None to NULL for the tra

[issue27820] Possible bug in smtplib when initial_response_ok=False

Pandu E POLUAN added the comment: I tried adding the code below to test_smtplib.py: def testAUTH_LOGIN_initial_response_notok(self): self.serv.add_feature("AUTH LOGIN") smtp = smtplib.SMTP(HOST, self.port, local_hostname='localhost',

[issue42793] Bug of round function

Serhiy Storchaka added the comment: It works as documented. https://docs.python.org/3/library/functions.html#round -- nosy: +serhiy.storchaka resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracke

[issue42793] Bug of round function

Dennis Sweeney added the comment: This is not a bug. See https://stackoverflow.com/a/10825998/11461120 -- nosy: +Dennis Sweeney ___ Python tracker <https://bugs.python.org/issue42

[issue42793] Bug of round function

s: 384101 nosy: Narek2018 priority: normal severity: normal status: open title: Bug of round function type: performance versions: Python 3.9 Added file: https://bugs.python.org/file49711/main.py ___ Python tracker <https:

[issue27820] Possible bug in smtplib when initial_response_ok=False

Pandu E POLUAN added the comment: I tried creating a PR, but for the life of me I couldn't wrap my head around how testAUTH_LOGIN is being performed (it's in Lib/test/test_smtplib.py) All I know is, the test doesn't AT ALL test for situations where initial_response_ok=False. ALL tests are

[issue42720] << operator has a bug

resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue42720> ___ ___ Python-bugs-list mailing

[issue42720] << operator has a bug

Nandish added the comment: I took print(100>>3), I dropped last 3 bits and added value ‘0’ to first 3 bits. Both manual calculation and python result was correct. How can << shit operator and >> shit operator work differently , with different logic ? Thanks Nandish On Wed, Dec 23, 2020 at

[issue42720] << operator has a bug

Eric V. Smith added the comment: Why do you think the first 3 bits should be dropped? That's not the documented behavior of <<. -- nosy: +eric.smith ___ Python tracker ___

[issue42720] << operator has a bug

t they added value '0' to last 3 bits. Where as print(100>>3) , worked perfect. I did manual calculation and cheked the print result from python. It worked correctly. Dropped last 3 bits and added value '0' to first 3 bits. Looks like (100<<3) , left shift operator has a bug on Pyth

[issue27820] Possible bug in smtplib when initial_response_ok=False

Change by Rahul Kumaresan : -- nosy: +rahul-kumi ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue1289136] distutils extension library path bug on cygwin

Change by Irit Katriel : -- resolution: -> out of date stage: needs patch -> resolved status: pending -> closed ___ Python tracker ___

[issue37572] email lib bug

Change by Raymond Hettinger : -- nosy: +rhettinger nosy_count: 5.0 -> 6.0 pull_requests: +22712 pull_request: https://github.com/python/cpython/pull/23849 ___ Python tracker

Re: Fwd: bug in download

On 12/16/2020 12:15 PM, Erick Willum wrote: Begin forwarded message: From: Erick Willum Date: 16 December 2020 at 15:53:40 GMT To: python-list@python.org Subject: bug in download Hallo and good afternoon, Having installed python (big thank you) and sublime text, i get the next message

[issue42661] Hashlib Bug

Zachary Ware added the comment: `hashlib` is part of the standard library and thus does not need to be (and should not be :)) installed via pip. -- nosy: +zach.ware resolution: -> not a bug stage: -> resolved status: open -> closed _

Fwd: bug in download

Begin forwarded message: > From: Erick Willum > Date: 16 December 2020 at 15:53:40 GMT > To: python-list@python.org > Subject: bug in download > > Hallo and good afternoon, > > Having installed python (big thank you) and sublime text, i get the next > message wh

[issue42661] Hashlib Bug

gg_info Check the logs for full command output. -- components: Library (Lib) messages: 383198 nosy: samit.mohnot.018 priority: normal severity: normal status: open title: Hashlib Bug type: compile error versions: Python 3.10 ___ Python trac

[issue41473] test_gdb fails on AMD64 Fedora Rawhide 3.x [gdb 9.2 bug]

STINNER Victor added the comment: test_gdb pass again on AMD64 Fedora Rawhide 3.x with "GNU gdb (GDB) Fedora 10.1-2.fc34": https://buildbot.python.org/all/#/builders/285/builds/348 0:02:52 load avg: 11.34 [242/426] test_gdb passed (1 min 28 sec) (...) I close the issue. --

[issue42632] Reassgining ZeroDivisionError will lead to bug in Except clause

Eric V. Smith added the comment: And thanks, Dennis, for the explanation as to why it's the expected behavior. -- ___ Python tracker ___

[issue42632] Reassgining ZeroDivisionError will lead to bug in Except clause

Eric V. Smith added the comment: This code is working as expected, so I'm closing this. -- nosy: +eric.smith resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue42632] Reassgining ZeroDivisionError will lead to bug in Except clause

Dennis Sweeney added the comment: This is just how local/nonlocal/global/builtin variables work in Python. When you assign to a name anywhere inside of a function, all occurrences of that name refer by default to a local variable. So the line "ZeroDivisionError = 1" tells the foo() function

[issue27820] Possible bug in smtplib when initial_response_ok=False

Pandu E POLUAN added the comment: This issue is still a bug for Python 3.6 and Python 3.8 I haven't checked on Python 3.7 and Python 3.9 -- versions: +Python 3.6, Python 3.8 ___ Python tracker <https://bugs.python.org/issue27

[issue27820] Possible bug in smtplib when initial_response_ok=False

Pandu E POLUAN added the comment: Hi, I'm one of the maintainers of aio-libs/aiosmtpd. This issue also bit me when trying to write unit tests for aio-libs/aiosmtpd AUTH implementation But I partially disagree with Dario D'Amico's changes, specifically the suggested change in the

[issue42632] Reassgining ZeroDivisionError will lead to bug in Except clause

Xinmeng Xia added the comment: Similar bugs exist in other exceptions. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue42632] Reassgining ZeroDivisionError will lead to bug in Except clause

ariable 'Exception' referenced before assignment -- components: Interpreter Core messages: 382953 nosy: xxm priority: normal severity: normal status: open title: Reassgining ZeroDivisionError will lead to bug in Except clause type: compile error versions: Python 3.10

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

New submission from Joakim Nilsson : Tested on Debian Bullseye with Python 3.9. If 'set editing-mode vi' is used in .inputrc and the attached program is run, a bug occurs when navigating the readline history. It seems only to occur when ANSI color escape characters are input to the 'input

[issue15898] OSX TTY bug

Ronald Oussoren added the comment: Closing this issue, because this is a platform bug. The reproducer in msg170147 works reliably for me on macOS 10.15 with Python 3.9, the system bug may have been fixed in the meantime. -- components: +macOS resolution: not a bug -> third pa

[issue29249] Pathlib glob ** bug

Miroslav Šedivý added the comment: Today when porting some random project from os.path to pathlib I encountered a homemade filename matching method that I wanted to port to pathlib.Path.match. Unfortunately >>> pathlib.Path('x').match('**/x') False although if I have a file called `x` in

[issue41473] test_gdb fails on AMD64 Fedora Rawhide 3.x [gdb 9.2 bug]

miss-islington added the comment: New changeset c7cf66d2fe1b85cc02153be6422dfc5e34811638 by Miss Islington (bot) in branch '3.9': bpo-41473: Reenable test_gdb on gdb 9.2 and newer (GH-23637) https://github.com/python/cpython/commit/c7cf66d2fe1b85cc02153be6422dfc5e34811638 --

[issue41473] test_gdb fails on AMD64 Fedora Rawhide 3.x [gdb 9.2 bug]

miss-islington added the comment: New changeset 8e8f82dd9459b9f62c21480528d737cffd6146bc by Miss Islington (bot) in branch '3.8': bpo-41473: Reenable test_gdb on gdb 9.2 and newer (GH-23637) https://github.com/python/cpython/commit/8e8f82dd9459b9f62c21480528d737cffd6146bc --

[issue41473] test_gdb fails on AMD64 Fedora Rawhide 3.x [gdb 9.2 bug]

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

[issue41473] test_gdb fails on AMD64 Fedora Rawhide 3.x [gdb 9.2 bug]

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

[issue41473] test_gdb fails on AMD64 Fedora Rawhide 3.x [gdb 9.2 bug]

STINNER Victor added the comment: New changeset 066394018a8463643cc63d933493f0afa99d72cc by Victor Stinner in branch 'master': bpo-41473: Reenable test_gdb on gdb 9.2 and newer (GH-23637) https://github.com/python/cpython/commit/066394018a8463643cc63d933493f0afa99d72cc --

[issue41473] test_gdb fails on AMD64 Fedora Rawhide 3.x [gdb 9.2 bug]

Change by STINNER Victor : -- pull_requests: +22505 pull_request: https://github.com/python/cpython/pull/23637 ___ Python tracker ___

[issue42510] Tuple Slice Bug

serhiy.storchaka resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue42510> ___ ___ Python-

[issue42510] Tuple Slice Bug

New submission from Sathvik Rao Poladi : >>>a=1,2,3,4 >>>a[1:2] (2,) Expected output -> (2) bug -> , -- components: Build messages: 382118 nosy: p.saisathvikrao priority: normal severity: normal status: open title: Tuple Slice Bug type: behav

[issue42397] lstrip 处理出现bug

Eryk Sun added the comment: Python 3.9 added str.removeprefix() and str.removesuffix() [1]: >>> "data_prj_t_suffix".removeprefix('data_prj_').removesuffix('_suffix') 't' [1] https://docs.python.org/3/library/stdtypes.html#str.removeprefix -- nosy: +eryksun

[issue42397] lstrip 处理出现bug

tdtypes.html?highlight=lstrip#str.lstrip -- nosy: +christian.heimes resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracke

[issue42397] lstrip 处理出现bug

381323 nosy: wsqat priority: normal severity: normal status: open title: lstrip 处理出现bug type: behavior versions: Python 3.7 ___ Python tracker <https://bugs.python.org/issue42397> ___ ___

[issue1289136] distutils extension library path bug on cygwin

Irit Katriel added the comment: I see that the erroneous "is string.find..." condition is no longer in the code: https://github.com/python/cpython/blob/master/Lib/distutils/command/build_ext.py#L220 Is this issue out of date or is there something still to do on it? -- nosy:

[issue38495] print built-in function docs bug

Julien Palard added the comment: Hi! Thanks Alex for reporting, and everyone involved. This has been fixed in python-docs-theme, so it's fixed for >=3.8. As 3.7 is in security-only (and embeds python-docs-theme), better not touch it. Bests. -- resolution: -> fixed stage: patch

[issue42303] I found a bug while checking string with find()

Serhiy Storchaka added the comment: str.find() does not work like you think. Please read the documentation. In your case you likely need to use the "in" operator. -- nosy: +serhiy.storchaka resolution: wont fix -> not a bug stage: -> resolved status

[issue42303] I found a bug while checking string with find()

DongwonTTuna added the comment: That was a mistake. upload another picture file. -- resolution: -> wont fix Added file: https://bugs.python.org/file49586/스크린샷 2020-11-10 16.14.28.png ___ Python tracker

[issue42303] I found a bug while checking string with find()

natity'; legal range is"): It should be run with print("yes"), but It shows print(E.message). But If I run with if E.message.find("'quanatity'; legal range is") == True: It's now run with print("yes") not the print(E.message). I th

[issue42276] Bug in adfuller test and a suggested fix

Ronald Oussoren added the comment: Statsmodel is not part of the Python standard library. The issue tracker for this packages seems to be at: https://github.com/statsmodels/statsmodels/issues -- nosy: +ronaldoussoren resolution: -> third party stage: -> resolved status: open ->

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