[issue44930] super-Matlab-style ranged list literal initialization

[Steven D'Aprano]

Steven D'Aprano  added the comment:

As a new feature, the absolute earliest we could add this would be Python 3.11. 
As new syntax, it would need a PEP.

https://www.python.org/dev/peps/

--
versions: +Python 3.11

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44930] super-Matlab-style ranged list literal initialization

[Steven D'Aprano]

Steven D'Aprano  added the comment:

> Python 3 has removed the capability to create a list from a range.

That's incorrect. You can do `list(range(1,100,2))`. But generally, why create 
a list? range objects support many of the list APIs:

- iteration
- fast containment tests `x in range(1, 100, 2)`
- indexing (subscripts) and slicing
- reversal using a slice
- count and index methods


Range objects support the full sequence API, so why do you need to convert to a 
list?

>>> from collections.abc import Sequence
>>> isinstance(range(1, 100, 2), Sequence)
True


For the unusual or rare cares where you do need a list, why do you need special 
syntax? Just call the list constructor.

--
nosy: +steven.daprano

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44930] super-Matlab-style ranged list literal initialization

[wang xuancong]

New submission from wang xuancong :

Different from Python 2, Python 3 has removed the capability to create a list 
from a range. In Python 2, we can use range(1,100,2) to create a list [1, 3, 5, 
..., 99], but in Python 3, we can only use list(range(1,100,2)) or 
[*range(1,100,2)] where the latter is even slower. I would like to propose to 
use something like [1:100:2] to initialize a list, moreover, you can use 
[1:100:2, 1000:1200:5, 5000:6000, :10] to create a list of multiple segments of 
ranges, i.e., 
[1,3,5,...,99,1000,1005,1010,...,1195,5000,5001,5002,...,5999,0,1,2,...,9]. 
Ranged list creation is quite useful and is often used in 
multi-thread/multi-processing scheduling or tracked sorting. This is especially 
useful in deep learning where you want to shuffle the training data but keep 
track of their corresponding labels. In deep RNN, where every training instance 
has a different length, after shuffling/sorting, you also need to keep track of 
their corresponding lengths information and etc. Thanks!

--
components: Interpreter Core
messages: 399707
nosy: xuancong84
priority: normal
severity: normal
status: open
title: super-Matlab-style ranged list literal initialization
type: enhancement

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue14156] argparse.FileType for '-' doesn't work for a mode of 'rb'

[Owen T. Heisler]

Change by Owen T. Heisler :


--
nosy: +owenh

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue41102] ZipFile.namelist() does not match the actual files in .zip file

[Xiaolong Liu]

Xiaolong Liu  added the comment:

Dear Andrei,

It's about 63MB. I reshared it on Google Drive. Please check the following link.
https://drive.google.com/file/d/1534MdIcGbXtMwYfuo2zeFxm6BVgHa4XX/view?usp=sharing
 

Bruce / Xiaolong Liu / 刘小龙

From: Andrei Kulakov
Date: 2021-08-14 20:49
To: liuxiaolong125
Subject: [issue41102] ZipFile.namelist() does not match the actual files in 
.zip file

Andrei Kulakov  added the comment:

Xiaolong: The file no longer exists on the google drive. How big was the file?

--
nosy: +andrei.avk

___
Python tracker 

___

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

[Jack DeVries]

Jack DeVries  added the comment:

I am pretty sure that Mozilla moved to a new content management system
and they've been refreshing a lot of content on their site. I would
assume that any lingering presence of this article is just growing pains
and it'll all be removed in due time.

I might be wrong, though. I suppose we could submit a bug report to
Mozilla to find out if we can ever figure out how to write a bug
report again, that is!

On Mon, Aug 16, 2021 at 10:43:16PM +, Terry J. Reedy wrote:
> 
> Terry J. Reedy  added the comment:
> 
> https://support.mozilla.org/en-US/kb/contributors-guide-writing-good-bug
> still has a link to
> https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines
> but the fact that they moved the latter to
>  
> https://github.com/mdn/archived-content/blob/main/files/en-us/mozilla/qa/bug_writing_guidelines/index.html
> does not think highly of it now.  The github archived document says last 
> modified in 2013.  The Wayback copy has an additional box saying last 
> modified a year ago by 'MDM contributors'.  I don't know what that means, 
> even after clicking the link.
> 
> --
> 
> ___
> Python tracker 
> 
> ___

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue42560] Improve Tkinter Documentation

[Mark Roseman]

Mark Roseman  added the comment:

I would most definitely echo the concern about the massive size of such a 
project as well as future maintainability. I don't know anyone who would be 
able to do such a thing on a volunteer basis, and I think it would be highly 
unlikely that anyone would step up to pay someone to do it. 

I imagine we all agree that we would love to have such a complete reference, 
but I have a hard time seeing how it's even remotely feasible.

As the effort supporting Tcl/Tk core development is fairly small, and most of 
the people involved are far more interested in the Tcl side of things rather 
than Tk, the odds of huge changes on the Tk front are small, beyond keeping it 
working, fixing bugs, and the odd little isolated burst of new stuff once in a 
while.

Based on previous history with that community, I think you can safely assume 
any licensing issues won't be an impediment to whatever needs to be done on 
this end, though I'm sure there are details to sort out.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44920] Support UUIDv6, UUIDv7, and UUIDv8 from the new version of RFC4122

[Logan Jones]

Change by Logan Jones :


--
nosy: +loganasherjones

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue33896] Document what components make up the filecmp.cmp os.stat signature.

[Ned Deily]

Change by Ned Deily :


--
resolution:  -> duplicate
stage: needs patch -> resolved
status: open -> closed
superseder:  -> filecmp.cmp(shallow=True) isn't actually shallow when only 
mtime differs
versions: +Python 3.10, Python 3.11, Python 3.9 -Python 2.7, Python 3.7, Python 
3.8

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue32937] Multiprocessing worker functions not terminating with a large number of processes and a manager

[Ned Deily]

Change by Ned Deily :


--
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44895] refleak test failure in test_exceptions

[Pablo Galindo Salgado]

Pablo Galindo Salgado  added the comment:

>> x = list(range(100))

Is creating a lot of objects, and the gc has a chance to run on every object 
creation so maybe what's happening there is that you are inadvertently 
triggering the gc

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44587] argparse BooleanOptionalAction displays default=SUPPRESS unlike other action types

[Maximilian Hils]

Change by Maximilian Hils :


--
keywords: +patch
nosy: +mhils
nosy_count: 2.0 -> 3.0
pull_requests: +26259
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/27672

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue34882] f(a=1, *args) should be a SyntaxError

[Pablo Galindo Salgado]

Pablo Galindo Salgado  added the comment:

Also, just to make it clear: changing this would be backwards incompatible, so 
if someone is interested, a bigger discussion is needed (starting with 
python-ideas/python-dev).

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue34882] f(a=1, *args) should be a SyntaxError

[Pablo Galindo Salgado]

Change by Pablo Galindo Salgado :


--
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue34882] f(a=1, *args) should be a SyntaxError

[Pablo Galindo Salgado]

Pablo Galindo Salgado  added the comment:

This is not a bug, check the thread that Serhiy attached. The grammar is, in 
principle, correct. For instance, you can do:

def f(a,b,c):

pass
def wrapper(*args, **kw):
return f(c=1, *args, **kw)

wrapper(2,b=2)

And you don't want that to be a syntax error.

--
resolution:  -> not a bug

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44895] refleak test failure in test_exceptions

[Irit Katriel]

Irit Katriel  added the comment:

It's midnight, so just one last weirdness before I turn into a pumpkin:

If I add this assignment to x the issue seems to go away (or become less 
frequent so I don't see it?)   But if I assign x to a small constant it still 
leaks. 


def test_no_hang_on_context_chain_cycle2():
x = list(range(100))
class A(Exception):
pass
class B(Exception):
pass

--
keywords:  -patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue34882] f(a=1, *args) should be a SyntaxError

[Irit Katriel]

Irit Katriel  added the comment:

Reproduced in 3.11:

>>> f(a=1, 2, 3)
  File "", line 1
f(a=1, 2, 3)
   ^
SyntaxError: positional argument follows keyword argument
>>> f(a=1, *(2, 3))
Traceback (most recent call last):
  File "", line 1, in 
TypeError: f() got multiple values for argument 'a'
>>>

--
nosy: +iritkatriel
versions: +Python 3.10, Python 3.11, Python 3.9 -Python 3.6, Python 3.7, Python 
3.8

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

[Terry J. Reedy]

Terry J. Reedy  added the comment:

https://support.mozilla.org/en-US/kb/contributors-guide-writing-good-bug
still has a link to
https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines
but the fact that they moved the latter to
 
https://github.com/mdn/archived-content/blob/main/files/en-us/mozilla/qa/bug_writing_guidelines/index.html
does not think highly of it now.  The github archived document says last 
modified in 2013.  The Wayback copy has an additional box saying last modified 
a year ago by 'MDM contributors'.  I don't know what that means, even after 
clicking the link.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44895] refleak test failure in test_exceptions

[Irit Katriel]

Irit Katriel  added the comment:

I meant refleaks.py, not reflinks.py.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44895] refleak test failure in test_exceptions

[Irit Katriel]

Irit Katriel  added the comment:

I've reproduced the leak in 3.10 (with the reflinks.py script).

In 3.9 the double-recursion segfaults:

Fatal Python error: _Py_CheckRecursiveCall: Cannot recover from stack overflow.
Python runtime state: initialized

--
versions: +Python 3.10

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

[Thomas Grainger]

Thomas Grainger  added the comment:

It looks like it got archived here 
https://github.com/mdn/archived-content/blob/main/files/en-us/mozilla/qa/bug_writing_guidelines/index.html

--
nosy: +graingert

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue42560] Improve Tkinter Documentation

[Terry J. Reedy]

Terry J. Reedy  added the comment:

It seems premature to worry about 8.7.0, as it might still be years away.  
8.7.0a1 was 4 years ago.  8.6.0 spent 5 years in beta.  
https://sourceforge.net/projects/tcl/files/Tcl/.
I'd like to see improved tkinter docs within a year.

I don't think that license should be an issue.  Tkinter, as well as our 
distribution of tcl/tk binaries and the Perl and Ruby tk wrappings, must be 
allowed by the tcl/tk license.  At least by implication, we must be allowed to 
document the licensed wrapper and its usage from Python.  

The tkinter-docs listing of widget options is close to what I want to see*, 
except that I want to separately document shared options, as in the ttk doc.  
To the extent that I would prefer your versions, you have already done a big 
chunk of the work for that.  Did you exactly copy the tk manual wordings or 
rewrite in your own words?  Do you intend to contribute what you wrote?

* In particular, you added OS-specific info.  It seems to be mostly absent from 
*tkinter* doc and not knowing those facts has caused grief.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1596321] KeyError at exit after 'import threading' in other thread

[Irit Katriel]

Irit Katriel  added the comment:

The output is different now. 

I update the script for python 3:

-
import _thread as thread
import time

def start():
print("Secondary thread ID:", thread.get_ident())
import threading

print("Main thread ID:", thread.get_ident())
thread.start_new_thread(start, ())
time.sleep(1)

-

and the output is:

-

Main thread ID: 4432801280
Secondary thread ID: 123145384259584
Exception ignored in: 
Traceback (most recent call last):
  File "/Users/iritkatriel/src/cpython-perf/Lib/threading.py", line 1512, in 
_shutdown
assert tlock.locked()
^
AssertionError: 

-

--
nosy: +iritkatriel

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44929] Some RegexFlag cannot be printed in the repr

[Pablo Galindo Salgado]

Change by Pablo Galindo Salgado :


--
keywords: +patch
pull_requests: +26258
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/27789

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44929] Some RegexFlag cannot be printed in the repr

[Pablo Galindo Salgado]

Pablo Galindo Salgado  added the comment:

This looks incorrect:

https://github.com/python/cpython/blob/1512bc21d60f098a9e9f37b44a2f6a9b49a3fd4f/Lib/enum.py#L1399

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44929] Some RegexFlag cannot be printed in the repr

[Pablo Galindo Salgado]

Pablo Galindo Salgado  added the comment:

Simpler reproducer:

>>> import re
>>> re.RegexFlag(0)
Traceback (most recent call last):
  File "", line 1, in 
  File "/home/pablogsal/github/cpython/Lib/enum.py", line 1399, in 
global_flag_repr
return "%x" % (module, cls_name, self._value_)
   ~^~
TypeError: %x format: an integer is required, not str

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44929] Some RegexFlag cannot be printed in the repr

[Pablo Galindo Salgado]

Pablo Galindo Salgado  added the comment:

(Deleted last message because it was incorrect)

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44929] Some RegexFlag cannot be printed in the repr

[Pablo Galindo Salgado]

Change by Pablo Galindo Salgado :


--
Removed message: https://bugs.python.org/msg399689

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44929] Some RegexFlag cannot be printed in the repr

[Pablo Galindo Salgado]

Pablo Galindo Salgado  added the comment:

Same happens when printing a enum.Flag with some values:

>>> enum.Flag(1)
Traceback (most recent call last):
  File "", line 1, in 
  File "/home/pablogsal/github/cpython/Lib/enum.py", line 597, in __call__
return cls.__new__(cls, value)
   ^^^
  File "/home/pablogsal/github/cpython/Lib/enum.py", line 944, in __new__
raise exc
^
  File "/home/pablogsal/github/cpython/Lib/enum.py", line 921, in __new__
result = cls._missing_(value)
 
  File "/home/pablogsal/github/cpython/Lib/enum.py", line 1185, in _missing_
raise ValueError(
^
ValueError: Flag: invalid value: 1
given 0b0 1
  allowed 0b0 0

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44929] Some RegexFlag cannot be printed in the repr

[Pablo Galindo Salgado]

New submission from Pablo Galindo Salgado :

When printing some instance of RegexFlag **in the REPL** it fails to print:

>>> import gc
# This prints a ton of objects, including the bad enum RegexFlag one
>>> gc.get_referrers(None) 
Traceback (most recent call last):
  File "", line 1, in 
  File "/home/pablogsal/github/cpython/Lib/enum.py", line 1399, in 
global_flag_repr
return "%x" % (module, cls_name, self._value_)
   ~^~
TypeError: %x format: an integer is required, not str

--
messages: 399688
nosy: ethan.furman, pablogsal
priority: normal
severity: normal
status: open
title: Some RegexFlag cannot be printed in the repr
versions: Python 3.10, Python 3.11

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue38956] argparse.BooleanOptionalAction should not add the default value to the help string by default

[Łukasz Langa]

Change by Łukasz Langa :


--
pull_requests: +26257
pull_request: https://github.com/python/cpython/pull/27788

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue38956] argparse.BooleanOptionalAction should not add the default value to the help string by default

[miss-islington]

Change by miss-islington :


--
nosy: +miss-islington
nosy_count: 7.0 -> 8.0
pull_requests: +26256
pull_request: https://github.com/python/cpython/pull/27787

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue38956] argparse.BooleanOptionalAction should not add the default value to the help string by default

[Łukasz Langa]

Łukasz Langa  added the comment:


New changeset 1512bc21d60f098a9e9f37b44a2f6a9b49a3fd4f by Maximilian Hils in 
branch 'main':
bpo-38956: don't print BooleanOptionalAction's default twice (GH-27672)
https://github.com/python/cpython/commit/1512bc21d60f098a9e9f37b44a2f6a9b49a3fd4f


--
nosy: +lukasz.langa

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44881] Consider integration of PyObject_GC_UnTrack() with the trashcan C API

[Neil Schemenauer]

Neil Schemenauer  added the comment:

Another small correction, _PyType_IS_GC() checks only the type flag 
(Py_TPFLAGS_HAVE_GC).  _PyObject_IS_GC() checks both the type flag and calls 
tp_is_gc(), if it exists.  tp_is_gc() is wart, IMHO, and it would be nice if we 
can kill it off so only the type flag is needed.  That's a topic for a 
different issue though.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue40608] PY3.8 GC segfault (Py_TRASHCAN_SAFE_BEGIN/END are not backwards compatible)

[Irit Katriel]

Irit Katriel  added the comment:

Re GH-20104 - What I did there was to simply revert the change that git bisect 
showed caused my segfault.

It's been a year since then, and I don't understand this stuff well enough to 
say that reverting this brings us to a good state, with respect to everything 
else that has changed. So let's be careful about that.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44928] async generator missing unawaited coroutine warning

[Thomas Grainger]

New submission from Thomas Grainger :

demo program:

```
def test_async_fn():
async def async_fn():
pass

async_fn()


def test_async_gen_fn():
async def agen_fn():
yield

agen_fn().aclose()
agen_fn().asend(None)

test_async_fn()
test_async_gen_fn()
```

output:

```
/home/graingert/projects/anyio/foo.py:5: RuntimeWarning: coroutine 
'test_async_fn..async_fn' was never awaited
  async_fn()
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
```

expected:


```
/home/graingert/projects/anyio/foo.py:5: RuntimeWarning: coroutine 
'test_async_fn..async_fn' was never awaited
  async_fn()
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
/home/graingert/projects/anyio/foo.py:12: RuntimeWarning: coroutine 
'' was never awaited
  agen_fn().aclose()
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
/home/graingert/projects/anyio/foo.py:13: RuntimeWarning: coroutine 
'' was never awaited
  agen_fn().asend(None)
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
```

--
components: Interpreter Core
messages: 399684
nosy: graingert
priority: normal
severity: normal
status: open
title: async generator missing unawaited coroutine warning
versions: Python 3.10, Python 3.11, Python 3.6, Python 3.7, Python 3.8, Python 
3.9

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue40608] PY3.8 GC segfault (Py_TRASHCAN_SAFE_BEGIN/END are not backwards compatible)

[Łukasz Langa]

Łukasz Langa  added the comment:

Agreed with Irit. GH-12607 is conflicting with `main` and in an unclear review 
state. Irit's got both GH-20104 which fixes the segfault and GH-27693 which 
deprecates the old macros.

It's sad we missed the train for either GH-20104 or the original GH-12607 to 
get merged to 3.10 but it's a C API change so there's no discussion.

There's no hurry then in deciding for 3.11 if we leave the old macros as is and 
just deprecate them OR we both fix them using GH-20104 and deprecate them 
anyway. What are your thoughts, Pablo?

--
nosy: +lukasz.langa

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44895] refleak test failure in test_exceptions

[Irit Katriel]

Irit Katriel  added the comment:

(Pdb) test_no_hang_on_context_chain_cycle2.__code__.co_consts[1]

(Pdb) 
sys.getrefcount(test_no_hang_on_context_chain_cycle2.__code__.co_consts[1])
2
(Pdb) 
gc.get_referrers(test_no_hang_on_context_chain_cycle2.__code__.co_consts[1])
[]

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44895] refleak test failure in test_exceptions

[Irit Katriel]

Irit Katriel  added the comment:

The leak seems to be due to the nested definitions of the Exception types A and 
B. It goes away if I move them out of the function so that it's like:


class A(Exception):
pass
class B(Exception):
pass

def test_no_hang_on_context_chain_cycle2():
try:
try:
raise A()
except A as _a:
a = _a
try:
raise B()
except B as _b:
b = _b
raise b
except B:
pass

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44852] Add ability to wholesale silence DeprecationWarnings while running the test suite

[Łukasz Langa]

Łukasz Langa  added the comment:


New changeset c7c4cbc58e18ef5a6f4f377b1ece0a84a54335a7 by Łukasz Langa in 
branch '3.9':
[3.9] bpo-44852: Support ignoring specific DeprecationWarnings wholesale in 
regrtest (GH-27634) (GH-27785)
https://github.com/python/cpython/commit/c7c4cbc58e18ef5a6f4f377b1ece0a84a54335a7


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44924] logging.handlers.QueueHandler does not maintain the exc_text

[Mikael Koli]

Mikael Koli  added the comment:

I did subclass the QueueHandler and it did circumvent the issue for me. But 
after spending some time to find out why I could not access the exc_text I 
thought maybe there is something that could be done to make it more intuitive 
and save others' time. I find the current behaviour somewhat confusing.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue42560] Improve Tkinter Documentation

[E. Paine]

E. Paine  added the comment:

> I don't see the tcl/tk versions as an issue

My main concern was when Tcl/Tk has a major new release with new kwargs. If 
MacOS was shipped with one version and Windows another, I suspect we would have 
to hold back an update to the docs. I am slightly less concerned now, because 
so far there are no new kwargs in the 8.7 highlights: 
https://www.tcl.tk/software/tcltk/8.7.html

> I would like a complete, in some sense, internal reference, which we would be 
> able to correct and further improve

Despite being more relaxed about the version issue above, my other major 
concern is the size of such a project. I started working on some reference 
documentation I named “tkinter-docs” (https://github.com/E-Paine/tkinter-docs / 
https://tkinter-docs.readthedocs.io/en/latest/widgets/canvas.html) but as you 
can see I haven’t worked on it since mid-May (I simply lost steam given the 
number of hours I’d have to invest to finish it).

My thinking is that an open-source documentation would be much easier to 
maintain going forward (rather being up to a single person to keep up-to-date) 
without filling Serhiy’s inbox with *a lot* of inevitable docs fixes. IMO, such 
documentation (regardless of a community to help) would still require a large 
amount of dedication from a single person to be checking and merging patches.

Another thing I think we would need to work out is how we respect the Tk 
licence’s requirement for attribution while allowing the PSF to relicense the 
docs as they please (I ‘m assuming that any work we produce would be based 
heavily enough on the Tk man pages to require the attribution). With 
tkinter-docs, this was easy enough as I could just include the full Tk license 
on a somewhat out-of-the-way page. Since the PSF would (probably) want to 
relicense the entire docs rather than just whatever modifications we’ve made, 
we may need legal advice or written exemption from the TCT (is there anyone 
more knowledgeable on the subject that we can nosy?).

> My 'biggest' idea is that we should document tk and ttk widgets together.

That does sound like a very good idea, so long as we make it obvious which 
module to find the specific widget in.

> someone posted a link to a site with distribution versus tcl/tk information

https://pkgs.org/download/tk

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44926] typing.get_type_hints() raises for type aliases with forward references

[Guido van Rossum]

Guido van Rossum  added the comment:

I think it's fine for get_type_hints() to give up in some cases. It's not fine 
if it were to look in the wrong namespace (e.g. if the caller of 
get_type_hints() were to happen to have an unrelated class named "Foo" in its 
namespace, that should *not* be found if the type alias was defined in a 
different file).

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44895] refleak test failure in test_exceptions

[Irit Katriel]

Irit Katriel  added the comment:

I've attached an even shorter script (refleak.py) that reproduces the leak.

--
Added file: https://bugs.python.org/file50224/refleak.py

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44926] typing.get_type_hints() raises for type aliases with forward references

[Maximilian Hils]

Maximilian Hils  added the comment:

@Guido van Rossum: Yes, GH-27017 is the same as #41249 in the initial post. 
There are also some cases where we don't even have a ForwardRef though:

foo.py:
```
import typing

FooType: typing.TypeAlias = "Foo"

class Foo:
pass

```

bar.py:
```
import typing
import foo

def func3(x: foo.FooType):
pass

print(typing.get_type_hints(func3))  # NameError: name 'Foo' is not defined.

```

In this example, `FooType` is just a regular str (with unknown origin). That's 
a case where get_type_hints just needs to give up?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44924] logging.handlers.QueueHandler does not maintain the exc_text

[Vinay Sajip]

Vinay Sajip  added the comment:

Why can you not subclass QueueHandler and override the prepare method to do 
what you want/need?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44927] [sqlite3] proposal: add sqlite3.Cursor.insert() method

[AR]

AR  added the comment:

There is no good solution to this. Either a move to all-in-one solution and ORM 
at the end, or limited scope hack that allow for a convenient "just insert". I 
do not insist due to this controversy

I just didn't realize the difference until I've noticed that one line of my 
pymongo code corresponds to many lines of sqlite code. I'm perfectly fine using 
direct SQL statements, but would happily use a shortcut.

It's up to you to decide as you see a broader picture. Thank you in any case!

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44927] [sqlite3] proposal: add sqlite3.Cursor.insert() method

[Erlend E. Aasland]

Change by Erlend E. Aasland :


--
title: [sqlite3] insert -> [sqlite3] proposal: add sqlite3.Cursor.insert() 
method

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44926] typing.get_type_hints() raises for type aliases with forward references

[Guido van Rossum]

Guido van Rossum  added the comment:

Is GH-27017 at all relevant here?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44914] tp_version_tag is not unique when test runs with -R :

[Mark Shannon]

Mark Shannon  added the comment:


New changeset d84d2c4985457733602d46dc4ee77290da4e9539 by Ken Jin in branch 
'main':
bpo-44914: Add tests for some invariants of tp_version_tag (GH-27774)
https://github.com/python/cpython/commit/d84d2c4985457733602d46dc4ee77290da4e9539


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44897] Integrate trashcan mechanism into _Py_Dealloc

[Neil Schemenauer]

Change by Neil Schemenauer :


--
nosy: +pablogsal, tim.peters, vstinner

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44927] [sqlite3] insert

[Erlend E. Aasland]

Erlend E. Aasland  added the comment:

The INSERT statement comes in many varieties. What about INSERT OR 
[ABORT,FAIL,IGNORE,REPLACE,ROLLBACK], INSERT WITH RECURSIVE, INSERT INTO table 
SELECT, etc.? Why only add such an API for insert; why not replace() as well?

I'm not convinced this is a good idea. It sounds to me like a project specific 
need that would need a project specific implementation. And as you showed, the 
implementation is pretty straight-forward.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44897] Integrate trashcan mechanism into _Py_Dealloc

[Neil Schemenauer]

Neil Schemenauer  added the comment:

Based on some testing, I think an extra type slot is not worth the extra 
complication.  I made some small improvements to _Py_Dealloc and now the 
performance seems a bit better.  Basically, I expanded _PyObject_IS_GC() to put 
the most common branches first.  See pypref-trashcan2.txt for benchmark.  
Overall I think might be a bit slower (less than 1%?)  but we have gained 
trashcan protection for the dealloc of all GC objects.  

If we are okay with the performance, here are other questions to answer:

A) is it safe to untrack GC objects before calling tp_dealloc?

B) is it safe to have PyObject_CallFinalizerFromDealloc() track objects that 
are resurrected?


We might have to look at 3rd party extensions to decide on those.  I.e. maybe 
in theory it is not safe but in practice there is no extension code that would 
actually break.

--
Added file: https://bugs.python.org/file50223/pyperf-trashcan2.txt

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue16379] SQLite error code not exposed to python

[Erlend E. Aasland]

Change by Erlend E. Aasland :


--
pull_requests: +26255
pull_request: https://github.com/python/cpython/pull/27786

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

[Terry J. Reedy]

Terry J. Reedy  added the comment:

Problems with linking to archive.org Wayback machine.
1. They have limited bandwidth. 
2. Production linking, as opposed to research like Jack did to find the 
'missing' page, stretches the meaning of 'fair use'.

Potential problems with external docs.
1. Don't directly fit our needs.
2. Cannot be edited by us.
3. Can disappear.

The Mozilla doc is obviously framed in terms of problems with Firefox, which is 
quite a different beast from Python.  In my opinion, it is too long, somehow 
seems repetitious, and is a bit hard to read.  I find it hard to imagine that 
many Python beginners will read the whole thing.

Some of the advice, such as "Version: select the earliest Version with what the 
problem can be reproduced:" is wrong for our workflow.

I would like our doc to recommend that real beginners, with less than a couple 
of months of experience, and anyone else with doubts, post first on 
python-list, asking "Is this a bug, and if not, please explain.

Version: select the earliest Version with what the problem can be reproduced:

A doc that we might link to, perhaps as a supplement to anything we write, is 
https://stackoverflow.com/help/minimal-reproducible-example.

--
nosy: +terry.reedy

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue16379] SQLite error code not exposed to python

[Erlend E. Aasland]

Erlend E. Aasland  added the comment:

>> What would it take to get this merged?
>
> I've rebased Aviv's PR (GH-1108) onto main and resolved the conflicts.
> If I get his blessing, I'll open a PR try to land this.

I asked Aviv on GH eight days ago, and I haven't heard anything yet, so I'm 
going forward with this. For the record, here's a link to my question on the PR:
https://github.com/python/cpython/pull/1108#issuecomment-894506420

I would also like to see this feature; it makes sqlite3 development slightly 
more convenient :)

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44852] Add ability to wholesale silence DeprecationWarnings while running the test suite

[Łukasz Langa]

Change by Łukasz Langa :


--
pull_requests: +26254
pull_request: https://github.com/python/cpython/pull/27785

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44698] Undefined behaviour in Objects/complexobject.c's complex_pow

[Mark Dickinson]

Mark Dickinson  added the comment:

Thanks, Pablo!

> could you add me as a reviewer for the backport

Will do! I'll waiting on review for the PR against the main branch, but hope to 
get the backport PR up by this coming weekend at the latest.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44852] Add ability to wholesale silence DeprecationWarnings while running the test suite

[Łukasz Langa]

Łukasz Langa  added the comment:


New changeset a0a6d39295a30434b088f4b66439bf5ea21a3e4e by Łukasz Langa in 
branch 'main':
bpo-44852: Support ignoring specific DeprecationWarnings wholesale in regrtest 
(GH-27634)
https://github.com/python/cpython/commit/a0a6d39295a30434b088f4b66439bf5ea21a3e4e


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44926] typing.get_type_hints() raises for type aliases with forward references

[Maximilian Hils]

Maximilian Hils  added the comment:

> For your specific use case (where the user is using Python 3.6), you could 
> pass in globalns and localns to get_type_hints as a temporary workaround. Off 
> the top of my head:
get_type_hints(func2, globalns=foo.__dict__) might work. Would that work for 
your library?

I guess the hard part is knowing that the type annotation comes from `foo`. In 
the example here we can of course hardcode it, but that doesn't work in the 
general case or for pdoc, the documentation generator I'm working on 
(https://pdoc.dev). I have experimented quite a bit with walking the AST to 
figure out where type aliases are imported from to then re-executing 
ForwardRefs with that globalns. Long story short, trying to reverse-engineer 
__forward_module__ quickly becomes a tangled hot mess where you need to adjust 
for import aliases, reimports, and so on.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44852] Add ability to wholesale silence DeprecationWarnings while running the test suite

[Łukasz Langa]

Change by Łukasz Langa :


--
pull_requests: +26253
pull_request: https://github.com/python/cpython/pull/27784

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44927] [sqlite3] insert

[Erlend E. Aasland]

Change by Erlend E. Aasland :


--
nosy: +erlendaasland

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44927] [sqlite3] insert

[AR]

New submission from AR :

I propose to add an insert method to a SQLite cursor object, believe this could 
greatly improve readability of python code when you have to do a lot of insert 
operations to a different tables. 

Currently we have to create a dictionary with SQL's for each table:
insert_sql = {'form_a': """INSERT INTO table_a (field_a1, field_a2) VALUES(:f1, 
:f2)""",
  'form_b': """INSERT INTO table_b (field_b1, field_b2, field_b3) 
VALUES(:f1, :f2, :f3),
   other SQL statements }"""
or we may use version with unnamed parameters:
insert_sql = {'form_a': """INSERT INTO table_a (field_a1, field_a2) VALUES(?, 
?)""",
  'form_b': """INSERT INTO table_b (field_b1, field_b2, field_b3) 
VALUES(?, ?, ?),
   other SQL statements }"""
The first one is conveniently compatible with cx_Oracle bind variable syntax, 
rows that are inserted are essentially dictionary. As dictionary is a mutable 
type, some extra freedom during construction of the row is allowed.

The second syntax(qmark style) is specific to SQLite, rows that are inserted 
should have tuple type (namedtuple for us to be able to extract field names at 
later stage).
entries_dict = [{'field_a1': 100, 'field_a2': 'sample1'},
{'field_a1': 500, 'field_a2': 'sample2'}]
DataRow = namedtuple('DataRow', ['field_a1', 'field_a2'])
entries_namedtuple = [DataRow(101, 'sample3'), DataRow(505, 'sample4')]

In order to do an insert, you have to use either execute, or executemany:
cursor.executemany(insert_sql['form_a'], entries_dict)
or
cursor.execute(insert_sql['form_a'], entries_dict[0])

Now let's move towards future insert method of cursor. As a first step, lets 
create SQL statement on the fly:
table_name = 'table_a'

#in case of a list of dictionaries:
sql = """INSERT INTO {} ({}) VALUES({})""".format(table_name, ', 
'.join([str(key) for key in entries_dict[0]]),
', '.join([':' + str(key) for key in 
entries_dict[0]]))
#currently, to do an insert operation, we have to:
cursor.executemany(sql, entries_dict)

#in case of a list of namedtuples:
sql = """INSERT INTO {} ({}) VALUES({})""".format(table_name, ', 
'.join([str(field) for field in entries_namedtuple[0]._fields]),
', '.join(['?' for field in 
entries_namedtuple[0]._fields]))
#currently, to do an insert operation, we have to:
cursor.executemany(sql, entries_namedtuple)

Now back to the proposal of insert method with unified syntax (one/many and 
dict/namedtuple). Let's do a second step and add an Insert method to a Cursor. 
The idea is to provide this method with table name, extract column names from 
supplied dict/namedtuple and use SQL generators from above. Than we could 
replace old cursor.executemany syntax with:

cursor.insert(table_name, entries_dict)
or 
cursor.insert(table_name, entries_dict[0])
or 
cursor.insert(table_name, entries_tuple)

Since we may insert all, or any row of two types, this looks even more pythonic 
than pymongo(MongoDB) approach:
collection.insert_many(entries_dict)
Actually, the fact that pymongo insert code is so much cleaner and concise drew 
my attention. Other aspects of that lib are totally different story.

I do not propose to generalize, or to move towards ORM or pymongo way of doing 
things. The scope is limited - lets do a convenient insert.

Simplified implementation could be like this:

def insert(self, table_name, entries):
if(type(entries) == list): # several records(rows) need to 
be inserted
do_insert = self.executemany
if(hasattr(entries[0], '_fields')): #NamedTuple
sql = "INSERT INTO {} ({}) VALUES({})".format(table_name, ', 
'.join([str(field) for field in entries[0]._fields]),
', '.join(['?' for field in 
entries[0]._fields]))
elif(type(entries[0] == dict)): #dict
sql = "INSERT INTO {} ({}) VALUES({})".format(table_name, ', 
'.join([str(key) for key in entries[0]]),
', '.join([':' + str(key) for key in 
entries[0]]))
else:   #just one record(row)
do_insert = self.execute
if(hasattr(entries, '_fields')):#NamedTuple
sql = "INSERT INTO {} ({}) VALUES({})".format(table_name, ', 
'.join([str(field) for field in entries._fields]),
', '.join(['?' for field in 
entries._fields]))
elif(type(entries == dict)):
sql = "INSERT INTO {} ({}) VALUES({})".format(table_name, ', 
'.join([str(key) for key in entries]),
', '.join([':' + str(key) for key in 
entries]))
do_insert(sql, entries)


If proposal is not feasible/doesn’t fit to a broad concept, I suggest to 
mention in documentation
- list comprehension one-line SQL-generators (see above)
- 

[issue44926] typing.get_type_hints() raises for type aliases with forward references

[Ken Jin]

Ken Jin  added the comment:

> 1. func1 doesn't crash, but also doesn't resolve the forward reference. I am 
> not sure if this expected behavior.

Good observation! That's indeed the current behavior. The reason is a little 
subtle - list[...] is using a special builtin type 
(https://docs.python.org/3/library/stdtypes.html#types-genericalias), while 
typing.List is the one from typing. The typing version wraps all strings in 
ForwardRef(), while the builtin version shouldn't import from typing, so it 
doesn't have that luxury. get_type_hints could probably support the builtin 
version, though I'd imagine we'd need some rework.

Re: 2. You're right there too. Storing the defined module in __forward_module__ 
is an interesting proposal.

For your specific use case (where the user is using Python 3.6), you could pass 
in globalns and localns to get_type_hints as a temporary workaround. Off the 
top of my head:
get_type_hints(func2, globalns=foo.__dict__) might work. Would that work for 
your library?

--
nosy: +gvanrossum, kj

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

[Jack DeVries]

Jack DeVries  added the comment:

> If Jack wants to pick this up, I'd merge it.

I might be interested but I'm not sure if I will have the time. I'm not 
"calling dibs" if anyone else wants to go ahead with this solution.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44926] typing.get_type_hints() raises for type aliases with forward references

[Maximilian Hils]

New submission from Maximilian Hils :

Someone reported this rather interesting issue where typing.get_type_hints 
crashes on type aliases with forward references. The original report is at 
https://github.com/mitmproxy/pdoc/issues/290. Here's an extended minimal 
example:

foo.py:
```
import typing

FooList1: typing.TypeAlias = list["Foo"]
FooList2: typing.TypeAlias = typing.List["Foo"]

class Foo:
pass

```

bar.py:
```
import typing
import foo

def func1(x: foo.FooList1):
pass

def func2(x: foo.FooList2):
pass

print(typing.get_type_hints(func1))  # {'x': list['Foo']}
print(typing.get_type_hints(func2))  # NameError: name 'Foo' is not defined.

```


Observations:

1. func1 doesn't crash, but also doesn't resolve the forward reference. I am 
not sure if this expected behavior.
   If it isn't, this should eventually run in the same problem as func2.
2. func2 crashes because "Foo" is evaluated in the context of bar.py (where 
class Foo is unknown) and not in the context of foo.py. ForwardRef._evaluate 
would
   somehow need to know in which context it was defined. #41249 (TypedDict 
inheritance doesn't work with get_type_hints) introduced 
   ForwardRef.__forward_module__, which would be a logical place for that 
information. I'm not sure if it is a good idea
   to use __forward_module__ more widely.
3. This may end up as quite a bit of complexity for an edge case, I'm fine if 
it is considered wontfix. 
   The reason I'm bringing it up is that PEP 613 (Explicit Type Aliases) 
decidedly allows forward references in type aliases.


For the record, PEP 563 (postponed evaluations) does not change the outcome 
here. However, postponed evaluations often make it possible to avoid the 
forward references by declaring the aliases last.

--
components: Library (Lib)
messages: 399660
nosy: mhils
priority: normal
severity: normal
status: open
title: typing.get_type_hints() raises for type aliases with forward references
type: crash
versions: Python 3.10, Python 3.7, Python 3.8, Python 3.9

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44921] dict subclassing is slow

[Carol Willing]

Change by Carol Willing :


--
nosy: +willingc

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44924] logging.handlers.QueueHandler does not maintain the exc_text

[Zachary Ware]

Change by Zachary Ware :


--
nosy: +vinay.sajip, zach.ware
versions:  -Python 3.6, Python 3.7, Python 3.8

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44916] Random behaviour when importing two modules with the same name but different source files

[Brett Cannon]

Brett Cannon  added the comment:

So first, don't import from threads. It's non-deterministic as you have seen. 
You should do all imports **before** you start running multi-threaded code if 
multiple threads are going to access the 

Second, tossing in pickle is just asking for more trouble. 

The key thing to know is the master copy of a module is kept in `sys.modules`. 
But classes keep a reference to the module they were loaded from, not what 
`sys.modules` happens to have at that moment. So due to threading indeterminism 
it's quite possible to end up unpickling in such a way that the module that 
eventually ends up in `sys.modules` is not what your unpickled class is 
referencing.

As such, I'm closing as "wont fix".

--
resolution:  -> wont fix
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44850] Could operator.methodcaller be optimized using LOAD_METHOD?

[Antony Lee]

Change by Antony Lee :


--
keywords: +patch
pull_requests: +26252
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/27782

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44925] [docs] Confusing deprecation notice for typing.IO

[Ken Jin]

Ken Jin  added the comment:

@rittneje, would you like to submit a PR for this? We can help if you'd like to.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44925] [docs] Confusing deprecation notice for typing.IO

[Ken Jin]

Change by Ken Jin :


--
assignee:  -> docs@python
components: +Documentation -Library (Lib)
keywords: +easy, newcomer friendly
nosy: +docs@python, gvanrossum, kj, srittau
title: Confusing deprecation notice for typing.IO -> [docs] Confusing 
deprecation notice for typing.IO
versions:  -Python 3.8

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35203] Windows Installer Ignores Launcher Installer Options Where The Python Launcher Is Already Present

[Steve Dower]

Steve Dower  added the comment:

Timothy - are you able to share your install logs? Look for all log files 
starting with "Python" in your %TEMP% directory.

We definitely do not (and without an installer rewrite, cannot) support 
simultaneous per-user and per-machine installs of the same version.

If you're just looking for the latest version for your own use, you may prefer 
to get it from the Windows Store instead. That one is per-user, won't interfere 
with other installs, and will give you global "python/python3/pip/pip3/etc." 
commands.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

[Jack DeVries]

Jack DeVries  added the comment:

I agree that linking to the wayback machine is clunky. I just sent a
message out to the python-ideas mailing list to solicit more
suggestions. The discourse thread didn't get much response.

I guess that at some point, if there is no consensus, it wouldn't be a
bad idea to ask the python-dev mailing list. I would think that core
devs would be the most opinionated when it comes to how people should
write bug reports! I don't want to ping that mailing list
unnecessarily, though.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44925] Confusing deprecation notice for typing.IO

[Jesse Rittner]

New submission from Jesse Rittner :

The docs for typing.IO, typing.TextIO, and typing.BinaryIO include a confusing 
deprecation notice. https://docs.python.org/3/library/typing.html#typing.IO

> Deprecated since version 3.8, will be removed in version 3.12: These types 
> are also in the typing.io namespace, which was never supported by type 
> checkers and will be removed.

As per the discussion on https://github.com/python/typing/issues/834, this 
deprecation notice only refers to the typing.io package, which is confusing. It 
would be helpful to rephrase it for clarity.

--
components: Library (Lib)
messages: 399655
nosy: rittneje
priority: normal
severity: normal
status: open
title: Confusing deprecation notice for typing.IO
type: enhancement
versions: Python 3.10, Python 3.11, Python 3.8, Python 3.9

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44914] tp_version_tag is not unique when test runs with -R :

[Ken Jin]

Change by Ken Jin :


--
pull_requests: +26251
pull_request: https://github.com/python/cpython/pull/27774

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue15373] copy.copy() does not properly copy os.environment

[Stéphane Blondon]

Stéphane Blondon  added the comment:

I think an asdict() method is not necessary. Instanciating a dict from 
os.environ is enough: 

>>> import os
>>> os.environ
environ({'SHELL': '/bin/bash', ...})
>>> dict(os.environ)
{'SHELL': '/bin/bash', ...})

With 'dict()', it's obvious there is no side effect.


I think os._Environ should not be pickable too because there is an ambiguity 
too when it will be unpicked: should we set the unpickled data to a basic dict 
(or another _Environ instance) or to the environment variables?

It seems there are more maintainers in favour of the removal. Removing the copy 
is a breaking change so it should be done on several releases.

Are you interested by a PR which adds DeprecationWarning when 
copy.copy(os.environ) or os.environ.copy() are called? It seems to be the first 
step to implement.

--
nosy: +sblondon
versions: +Python 3.11 -Python 3.10

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44905] Abstract instance and class attributes for abstract base classes

[Jacob Nilsson]

Jacob Nilsson  added the comment:

Could one possible downside of this suggestion be, if implemented like in 
https://newbedev.com/python-abstract-class-shall-force-derived-classes-to-initialize-variable-in-init,
 a slowdown in code creating a lot of instances of a class with metaclass 
ABCMeta?

I have personally never experienced that the current behavior is an issue, I've 
only occasionally got confused by the error messages until I read the traceback.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44900] Implement superinstructions

[Mark Shannon]

Change by Mark Shannon :


--
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44900] Implement superinstructions

[Mark Shannon]

Mark Shannon  added the comment:


New changeset 4f51fa9e2d3ea9316e674fb9a9f3e3112e83661c by Mark Shannon in 
branch 'main':
bpo-44900: Add five superinstructions. (GH-27741)
https://github.com/python/cpython/commit/4f51fa9e2d3ea9316e674fb9a9f3e3112e83661c


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44914] tp_version_tag is not unique when test runs with -R :

[Mark Shannon]

Mark Shannon  added the comment:


New changeset 1a511dc92dd10ee8fc2e5da9f52f795924bdc89a by Mark Shannon in 
branch 'main':
bpo-44914: Maintain invariants of type version tags. (GH-27773)
https://github.com/python/cpython/commit/1a511dc92dd10ee8fc2e5da9f52f795924bdc89a


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44905] Abstract instance and class attributes for abstract base classes

[Alex Waygood]

Alex Waygood  added the comment:

^And, that only works for class attributes, not instance attributes.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44905] Abstract instance and class attributes for abstract base classes

[Alex Waygood]

Alex Waygood  added the comment:

Tomasz -- as discussed in the original BPO issue for `abstractmethod` 
implementations (https://bugs.python.org/issue1706989), this works as a 
workaround:

```
>>> from abc import ABCMeta
>>> class AbstractAttribute:
... __isabstractmethod__ = True
... 
>>> class Foo(metaclass=ABCMeta):
... abstract_attribute_to_be_overriden = AbstractAttribute()
... 
>>> class Bar(Foo): pass
... 
>>> b = Bar()
Traceback (most recent call last):
  File "", line 1, in 
TypeError: Can't instantiate abstract class Bar with abstract method 
abstract_attribute_to_be_overriden
```

It would be nice to have something like this in the `abc` module, though.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44240] Incorrect behavior of LOAD_ATTR due to overflow in tp_version

[Mark Shannon]

Change by Mark Shannon :


--
resolution:  -> duplicate
stage: needs patch -> resolved
status: open -> closed
superseder:  -> tp_version_tag is not unique when test runs with -R :

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44915] Python keywords as string keys in TypedDict

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

You can use the functional form of TypedDict:

C = TypedDict("C", {"to": int, "from": int})

--
nosy: +serhiy.storchaka

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44920] Support UUIDv6, UUIDv7, and UUIDv8 from the new version of RFC4122

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

It is a new feature, and we usually do not backport new features to old Python 
versions, so it can only be included in Python 3.11 (backports can be provided 
by third-party libraries). Do you want to create a PR?

--
nosy: +serhiy.storchaka

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44923] Unittest incorrect result with argparse.ArgumentError in self asserRaises context

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

You raise ArgumentTypeError, but expect ArgumentError. ArgumentTypeError is not 
a subclass of ArgumentError.

--
nosy: +serhiy.storchaka
versions: +Python 3.8 -Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44911] Leaked tasks cause IsolatedAsyncioTestCase to throw an exception

[Łukasz Langa]

Łukasz Langa  added the comment:

Thanks, Bar! ✨  ✨

--
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44923] Unittest incorrect result with argparse.ArgumentError in self asserRaises context

[Irit Katriel]

Irit Katriel  added the comment:

What is the output of the failed test?

--
nosy: +iritkatriel
versions: +Python 3.6 -Python 3.8

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44924] logging.handlers.QueueHandler does not maintain the exc_text

[Mikael Koli]

Mikael Koli  added the comment:

And the reason why overriding attribute 'record.msg' with the formatted message 
is problematic is that the method 'record.getMessage' (which is used by 
Formatter) fetches the log message from the variable 'record.msg'. Therefore 
the exc_text needs to be set to None as Formatter checks the existence of this 
attribute to decide whether or not to format the exception. Otherwise the 
exception text may be formatted multiple of time.

I think it may be more correct solution to not override the record.msg and let 
the other formatters down the queue reformat the message if required.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44924] logging.handlers.QueueHandler does not maintain the exc_text

[Mikael Koli]

New submission from Mikael Koli :

The reason why logging.handlers.QueueHandler does not maintain exc_text is 
obvious:

def prepare(self, record):
...
record = copy.copy(record)
record.message = msg
record.msg = msg
record.args = None
record.exc_info = None
record.exc_text = None
return record

The record.exc_text is set to None. The reason for this is to prevent the 
exception text showing up multiple times to the message. See 
https://bugs.python.org/issue34334.

However, there are a couple of situations this may cause a problem. First, it's 
not currently possible to format the exception of the record in a handler on 
the other side of the queue. Second, it's not possible to let the handler on 
the other side of the queue utilize exc_text. The default handlers do not 
behave in such a way but one could prefer to create their own handler that does 
so, such as log the records to a database with a column for the exception text.


Possible solution:
Don't override the record.msg and don't set the record.exc_text to None. I 
think it could be done simply:

def prepare(self, record):
...
record = copy.copy(record)
record.message = msg
# record.msg = msg
record.args = None
record.exc_info = None
# record.exc_text = None
return record

 
This way one can format the record later again without multiple exception text 
showing up in the message. Doing so will fail the test 
'test_logging.QueueHandlerTest.test_formatting' as this tests the record.msg is 
the same as record.message. This may cause issues if someone relies on 
record.msg. On the other hand, now other formatters and handlers down the line 
could use the exc_text attribute. I'm not sure if this is too breaking change 
or not.

The failing test:

def test_formatting(self):
msg = self.next_message()
levelname = logging.getLevelName(logging.WARNING)
log_format_str = '{name} -> {levelname}: {message}'
formatted_msg = log_format_str.format(name=self.name,
  levelname=levelname, message=msg)
formatter = logging.Formatter(self.log_format)
self.que_hdlr.setFormatter(formatter)
self.que_logger.warning(msg)
log_record = self.queue.get_nowait()
self.assertEqual(formatted_msg, log_record.msg) # 
self.assertEqual(formatted_msg, log_record.message)



I tested this issue with the following test (which is a pass with the current 
build):

class QueueHandlerTest(BaseTest):

def test_formatting_exc_text(self):
formatter = logging.Formatter(self.log_format)
self.que_hdlr.setFormatter(formatter)
try:
raise RuntimeError('deliberate mistake')
except:
self.que_logger.exception('failed', stack_info=True)
log_record = self.queue.get_nowait()
self.assertTrue(log_record.exc_text.startswith('Traceback (most recent '
   'call last):\n'))

--
components: Library (Lib)
messages: 399642
nosy: Miksus
priority: normal
severity: normal
status: open
title: logging.handlers.QueueHandler does not maintain the exc_text
type: behavior
versions: Python 3.10, Python 3.11, Python 3.6, Python 3.7, Python 3.8, Python 
3.9

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44911] Leaked tasks cause IsolatedAsyncioTestCase to throw an exception

[miss-islington]

miss-islington  added the comment:


New changeset 8516ca500eb45ecf997a471f003df02a9eb767ce by Miss Islington (bot) 
in branch '3.10':
bpo-44911: Fixed IsolatedAsyncioTestCase from throwing an exception on leaked 
tasks (GH-27765)
https://github.com/python/cpython/commit/8516ca500eb45ecf997a471f003df02a9eb767ce


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44923] Unittest incorrect result with argparse.ArgumentError in self asserRaises context

[Troulet-lambert Odile]

New submission from Troulet-lambert Odile :

When passed an Argparse.ArgumentError in the self.assertRaises context 
uniittest does not recognize the exception and raises an exception.
As a consequence the test fails whereas it should pass

--
components: Tests
files: bug_unittest_exception.py
messages: 399640
nosy: piscvau
priority: normal
severity: normal
status: open
title: Unittest incorrect result with argparse.ArgumentError in self 
asserRaises context
type: behavior
versions: Python 3.8
Added file: https://bugs.python.org/file50222/bug_unittest_exception.py

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44895] refleak test failure in test_exceptions

[miss-islington]

miss-islington  added the comment:


New changeset 1960409a6dcbd1e3527f02b523bd27df9086dd77 by Miss Islington (bot) 
in branch '3.10':
bpo-44895: skip test_no_hang_on_context_chain_cycle2 until the refleak is fixed 
(GH-27761)
https://github.com/python/cpython/commit/1960409a6dcbd1e3527f02b523bd27df9086dd77


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

[Łukasz Langa]

Łukasz Langa  added the comment:


New changeset b6a6d99a0ba3796a9d7d4fe8612b640f90e6d7f9 by Senthil Kumaran in 
branch '3.10':
[3.10] bpo-44830 - Remove the broken Broken Mozilla devguide link. (GH-27664) 
(GH-27666)
https://github.com/python/cpython/commit/b6a6d99a0ba3796a9d7d4fe8612b640f90e6d7f9


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

[Łukasz Langa]

Łukasz Langa  added the comment:

I merged the 3.10 backport but leaving the bug open since only removing the 404 
link isn't really fixing the problem.

Linking to the Wayback Machine feels off to me. I would rather support making a 
similar document in our own docs, using the removed document as inspiration. If 
Jack wants to pick this up, I'd merge it.

--
nosy: +lukasz.langa

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44895] refleak test failure in test_exceptions

[miss-islington]

Change by miss-islington :


--
pull_requests: +26250
pull_request: https://github.com/python/cpython/pull/27778

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44895] refleak test failure in test_exceptions

[Łukasz Langa]

Łukasz Langa  added the comment:


New changeset 62bc716fde20fcb7b47416c7959be9e66df93212 by Irit Katriel in 
branch 'main':
bpo-44895: skip test_no_hang_on_context_chain_cycle2 until the refleak is fixed 
(GH-27761)
https://github.com/python/cpython/commit/62bc716fde20fcb7b47416c7959be9e66df93212


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44911] Leaked tasks cause IsolatedAsyncioTestCase to throw an exception

[Łukasz Langa]

Łukasz Langa  added the comment:


New changeset 2cb1a6806c0cefab0c3a40fdd428a89a4392570e by Bar Harel in branch 
'main':
bpo-44911: Fixed IsolatedAsyncioTestCase from throwing an exception on leaked 
tasks (GH-27765)
https://github.com/python/cpython/commit/2cb1a6806c0cefab0c3a40fdd428a89a4392570e


--
nosy: +lukasz.langa

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44911] Leaked tasks cause IsolatedAsyncioTestCase to throw an exception

[miss-islington]

Change by miss-islington :


--
nosy: +miss-islington
nosy_count: 3.0 -> 4.0
pull_requests: +26249
pull_request: https://github.com/python/cpython/pull/2

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com