[issue40204] Docs build error with Sphinx 3.0 due to invalid C declaration

[STINNER Victor]

STINNER Victor  added the comment:

I'm now able to build the Python documentation with Sphinx 3.2.1 without 
modifying the Doc/Makefile, so using -W option (treat warnings as errors): 
there are no more Sphinx 3 warnings.

When Sphinx 3 will be more widely available (ex: in Linux distributions), we 
will be able to consider removing c_allow_pre_v3=True and 
c_warn_on_allowed_pre_v3=False in doc/conf.py. For that, we should update the 
documentation to use the Sphinx 3 syntax, see PR 19397 written by Jakob Lykke 
Andersen.

For now, I prefer to keep Sphinx 2 support and so keep Sphinx 2 syntax in the C 
domain, since it allows supporting Sphinx 2 and Sphinx 3.

--

___
Python tracker 

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

[issue40204] Docs build error with Sphinx 3.0 due to invalid C declaration

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests: +21019
pull_request: https://github.com/python/cpython/pull/21901

___
Python tracker 

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

[issue41564] Cannot access member "hex" for type "ByteString"

[Eric V. Smith]

Eric V. Smith  added the comment:

Without some example code that shows the problem we can't help you. Have you 
considered that this is a bug with pyright, not a bug with python itself?

--
nosy: +eric.smith
status: open -> pending

___
Python tracker 

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

[issue40204] Docs build error with Sphinx 3.0 due to invalid C declaration

[STINNER Victor]

STINNER Victor  added the comment:


New changeset 1abeda80f760134b4233608e2c288790f955b95a by Victor Stinner in 
branch 'master':
bpo-40204: Fix duplicated productionlist names in the doc (GH-21900)
https://github.com/python/cpython/commit/1abeda80f760134b4233608e2c288790f955b95a


--

___
Python tracker 

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

[issue40204] Docs build error with Sphinx 3.0 due to invalid C declaration

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests: +21018
pull_request: https://github.com/python/cpython/pull/21900

___
Python tracker 

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

[issue41521] Replace whitelist/blacklist with allowlist/denylist

[STINNER Victor]

STINNER Victor  added the comment:

I don't think that it's worth it to backport these changes, so I close the 
issue.

Again, to avoid reintroducing such terms, I proposed 
https://github.com/python/devguide/issues/605 to define some general guidelines 
on the terminology.

Thanks for reviews.

--
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

[issue41521] Replace whitelist/blacklist with allowlist/denylist

[STINNER Victor]

STINNER Victor  added the comment:


New changeset fbf43f051e7bf479709e122efa4b6edd4b09d4df by Victor Stinner in 
branch 'master':
bpo-41521: Rename blacklist parameter to not_exported (GH-21824)
https://github.com/python/cpython/commit/fbf43f051e7bf479709e122efa4b6edd4b09d4df


--

___
Python tracker 

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

[issue41565] from os.path import join join('3', '{:3') return '{:3' in windows

[song super]

New submission from song super <2262720...@qq.com>:

python3.6 
from os.path import join 
join('3', '{:3') 
return  '{:3' in  windows,However,join('3', '{:3') return  '3//{:3' in linux,I 
think this is a bug

--
components: Windows
files: python bug.zip
hgrepos: 391
messages: 375524
nosy: 2262720766, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: from os.path import join join('3', '{:3') return  '{:3' in  windows
type: compile error
versions: Python 3.6
Added file: https://bugs.python.org/file49400/python bug.zip

___
Python tracker 

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

[issue41564] Cannot access member "hex" for type "ByteString"

[Matt Joiner]

New submission from Matt Joiner :

I get this error when running pyright for a type of typing.ByteString. All the 
implementations of ByteString (bytes, bytearray, memoryview) have the hex 
method, so this seems unexpected?

--
components: Library (Lib)
messages: 375523
nosy: anacrolix
priority: normal
severity: normal
status: open
title: Cannot access member "hex" for type "ByteString"
type: behavior
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

[issue40424] AIX: makexp_aix, parallel build (failures) and ld WARNINGS

[Michael Felt]

Michael Felt  added the comment:

If #19521 had been merged I would be all for closing this as a duplicate. 
However, if i have read all the comments correctly noone has tested the other 
pr. 

As the approaches are quite different I think both should be open until a 
decision is made on the better approach. 

Closing one (asap) is a good idea, especially if that leads to something being 
merged so this is finally repaired. 

Sent from my iPhone

> On 15 Aug 2020, at 23:07, Stefan Krah  wrote:
> 
> 
> Stefan Krah  added the comment:
> 
> I understand that both of you are in favor of #19521 (the patch of
> which I have not tried yet).
> 
> Can we close this as a duplicate? Please just reopen if you disagree.
> 
> --
> nosy: +skrah
> resolution:  -> duplicate
> stage: patch review -> resolved
> status: open -> closed
> superseder:  -> Parallel build race condition on AIX since python-2.7
> 
> ___
> Python tracker 
> 
> ___
>

--

___
Python tracker 

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

[issue38379] finalizer resurrection in gc

[Lewis Gaul]

Lewis Gaul  added the comment:

You're right that's how I had interpreted it, thanks for clarifying.

I was wondering if this could be related to an issue I've hit with gc.collect() 
getting slower and slower in a test suite, but that now seems unlikely, so I 
won't go into that here.

--

___
Python tracker 

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

[issue38379] finalizer resurrection in gc

[Tim Peters]

Tim Peters  added the comment:

I suspect you're reading some specific technical meaning into the word "block" 
that the PR and release note didn't intend by their informal use of the word. 
But I'm unclear on what technical meaning you have in mind.

Before the change, gc "just gave up" after seeing a resurrection, ending the 
then-current cyclic gc run. It that sense, yes, resurrection "blocked" gc from 
making progress. It did not, e.g., "block" the interpreter in the sense of 
deadlock, or of waiting for some lock to be released, or of waiting for a 
network request to respond, or ...

--

___
Python tracker 

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

[issue13322] The io module doesn't support non-blocking files

[Bar Harel]

Bar Harel  added the comment:

I have experienced both ״TypeError: can't concat NoneType to bytes״, and the 
fact BufferedIO returns None.

@pitrou @izbyshev contrary to your belief, I think there is at least some 
interest in this issue. Every few months another ticket is opened about a 
different aspect of the same underlying problem.

--
nosy: +bar.harel

___
Python tracker 

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

[issue38379] finalizer resurrection in gc

[Lewis Gaul]

Lewis Gaul  added the comment:

I noticed this bug is mentioned in the 3.9 release notes with a note similar to 
the title of the 4th PR: "garbage collection does not block on resurrected 
objects".

I can't see any mention of a blocking issue here on the issue:

> The bug:  the stats keep claiming gc is collecting an enormous number of 
> objects, but in fact it's not collecting any.  Objects in the unreachable set 
> shouldn't add to the "collected" count unless they _are_ collected.

Would someone be able to elaborate on the blocking issue that was fixed as part 
of this BPO?

--
nosy: +LewisGaul

___
Python tracker 

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

[issue38628] Issue with ctypes in AIX

[Vinay Sajip]

Vinay Sajip  added the comment:

> Implementing a work-around solely based on x64 ABI is not correct.

But AFAIK the test_array_in_struct test passes on AIX and exercises the 
workaround - why does it work if the workaround is faulty? If OTOH the test is 
faulty, could you update it with code that fails on AIX, as I suggested earlier?

--

___
Python tracker 

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

[issue41503] Race between setTarget and flush in logging.handlers.MemoryHandler

[Vinay Sajip]

Change by Vinay Sajip :


--
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

[issue41503] Race between setTarget and flush in logging.handlers.MemoryHandler

[miss-islington]

miss-islington  added the comment:


New changeset 08f0a2109297e8a64e8636d47dce737e5b7ccf2c by Miss Islington (bot) 
in branch '3.8':
[3.8] bpo-41503: Fix race between setTarget and flush in 
logging.handlers.MemoryHandler (GH-21765) (GH-21898)
https://github.com/python/cpython/commit/08f0a2109297e8a64e8636d47dce737e5b7ccf2c


--

___
Python tracker 

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

[issue35058] Unable to Install Python on Windows

[sahiba]

sahiba  added the comment:

Can you please find the log files and attach them or you could also provide the 
download link as without it there is nothing that can be done.

--
nosy: +sahiba007

___
Python tracker 

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

[issue41032] locale.setlocale example incorrect

[Barathwaja]

Barathwaja  added the comment:

Hi Marco,

Can I work on this?

--
nosy: +Barathwaja

___
Python tracker 

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

[issue41541] [PATCH] Make pty.spawn set window size

[Soumendra Ganguly]

Soumendra Ganguly  added the comment:

Further proposal: Rename my _login_tty to login_tty and make it available as a 
part of the pty library. Note that usually login_tty accompanies openpty and 
forkpty on a system; for example, see

https://www.man7.org/linux/man-pages/man3/login_tty.3.html
https://man.openbsd.org/login_tty
https://netbsd.gw.com/cgi-bin/man-cgi?login_tty++NetBSD-current

However, python's pty only offers openpty and forkpty in the form of 
pty.openpty and pty.fork respectively. While it is true that forkpty [ pty.fork 
] combines openpty, fork, and login_tty, it also closes the slave end of the 
pty, making it unsuitable for situations where the slave end needs to be kept 
open; for example, in my patch, the slave end is used to set the window size; 
or, in case someone wants to do even better and register a SIGWINCH handler for 
situations in which the window size can change.

--

___
Python tracker 

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

[issue41503] Race between setTarget and flush in logging.handlers.MemoryHandler

[miss-islington]

miss-islington  added the comment:


New changeset 2c050e52f1ccf5db03819e4ed70690521d67e9fa by Miss Islington (bot) 
in branch '3.9':
[3.9] bpo-41503: Fix race between setTarget and flush in 
logging.handlers.MemoryHandler (GH-21765) (GH-21897)
https://github.com/python/cpython/commit/2c050e52f1ccf5db03819e4ed70690521d67e9fa


--

___
Python tracker 

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

[issue38628] Issue with ctypes in AIX

[David Edelsohn]

David Edelsohn  added the comment:

Yes, it doesn't appear that it will be solved in libffi.  I don't fully 
understand the need for the work-around because it should gracefully overflow 
to the stack.  I can't tell if the issue is a problem with arguments passed by 
value that need to be passed partially in registers and partially in the stack.

But if the work-around is necessary, it is target- and ABI-dependent: the 
number of arguments passed in registers is target- and ABI-dependent.  
Implementing a work-around solely based on x64 ABI is not correct.  The ctypes 
stgdict.c code needs to define MAX_STRUCT_SIZE based on the target, at least 
for the targets that experience the problem.

--

___
Python tracker 

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

[issue41503] Race between setTarget and flush in logging.handlers.MemoryHandler

[miss-islington]

Change by miss-islington :


--
nosy: +miss-islington
nosy_count: 2.0 -> 3.0
pull_requests: +21016
pull_request: https://github.com/python/cpython/pull/21897

___
Python tracker 

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

[issue41503] Race between setTarget and flush in logging.handlers.MemoryHandler

[miss-islington]

Change by miss-islington :


--
pull_requests: +21017
pull_request: https://github.com/python/cpython/pull/21898

___
Python tracker 

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

[issue41503] Race between setTarget and flush in logging.handlers.MemoryHandler

[Vinay Sajip]

Vinay Sajip  added the comment:


New changeset 2353d77fad7ed9d11d8a4d66b5dd1306cdb94125 by Irit Katriel in 
branch 'master':
bpo-41503: Fix race between setTarget and flush in 
logging.handlers.MemoryHandler (GH-21765)
https://github.com/python/cpython/commit/2353d77fad7ed9d11d8a4d66b5dd1306cdb94125


--

___
Python tracker 

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

[issue38628] Issue with ctypes in AIX

[Vinay Sajip]

Vinay Sajip  added the comment:

> an array definition in a structure is always part of the struct itself and is 
> never a pointer

True, but a problem only arises in practice when passing by value in registers. 
It's still an open libffi issue that doesn't look like it's going to be solved 
any time soon, hence the attempted workaround in ctypes.

https://github.com/libffi/libffi/issues/33

--

___
Python tracker 

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

[issue33051] IDLE: Create new tab for editor options in configdialog

[E. Paine]

E. Paine  added the comment:

Thank you Cheryl for linking this issue on #40468 (I didn't find this when 
researching for existing issues). I have briefly tested the PR and it seems 
perfect, though seeing `init_validators` made me think we should possibly have 
an ABC for the tab pages. This would be a separate issue, but I think there 
would be three main advantages:
1. We could enforce a more standard naming of page methods (`create_page_*` 
would become `create_page` and be called by the parent, for example)
2. We could share methods like `init_validators` (which would preferably be 
part of the class but I appreciate the need to move it in this PR)
3. We can also potentially remove the example `TabPage` as the ABC would serve 
as its own example

Back to this issue, I didn't scrutinise it but the PR looks good and the 
"result" (user-facing) is exactly as I would propose based on #40468.

--
nosy: +epaine
versions: +Python 3.10, Python 3.9

___
Python tracker 

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

[issue37658] In some cases asyncio.wait_for can lead to socket leak.

[aaliddell]

Change by aaliddell :


--
nosy: +aaliddell

___
Python tracker 

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

[issue41503] Race between setTarget and flush in logging.handlers.MemoryHandler

[Irit Katriel]

Change by Irit Katriel :


--
versions: +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

[issue38628] Issue with ctypes in AIX

[Ronald Oussoren]

Ronald Oussoren  added the comment:

As mentioned before I haven't studied the ctypes code base, but I am a bit 
worried about the use of MAX_STRUCT_SIZE, an array definition in a structure is 
always part of the struct itself and is never a pointer.

I agree with Vinay that there needs to be a unittest that demonstrates the 
problem.

--
versions: +Python 3.10, Python 3.9

___
Python tracker 

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

[issue41563] .python_history file causes considerable slowdown

[bytecookie]

bytecookie  added the comment:

Using Python 3.8.3 on Windows 10 1803

--

___
Python tracker 

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

[issue41563] .python_history file causes considerable slowdown

[Denniver]

New submission from Denniver :

The seemingly unlimited growth of the ".python_history"-file seems to cause a 
massive slowdown when starting or exiting python, the same after running 
commands.
On one machine python took about 3 minutes to start and I found out that while 
it is seemingly doing nothing, it was constantly aceesing the 
".python_history"-file, which was 130 Mb large. After deleting the file, 
anything was back to normal.

--
components: Build
messages: 375505
nosy: bytecookie
priority: normal
severity: normal
status: open
title: .python_history file causes considerable slowdown
type: performance
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

[issue41551] test.support has way too many imports in libregrtest

[hai shi]

Change by hai shi :


--
nosy: +shihai1991

___
Python tracker 

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