[issue41043] Escape the literal part of the path for glob()

Serhiy Storchaka added the comment: New changeset ecfecc2d6ce88ae71c783f0465a508c6a1b2f2b6 by Serhiy Storchaka in branch '3.9': [3.9] bpo-41043: Escape literal part of the path for glob(). (GH-20994). (GH-21275) https://github.com/python/cpython/commit/ecfecc2d6ce88ae71c783f0465a508c6a1b2f2b

[issue41043] Escape the literal part of the path for glob()

Serhiy Storchaka added the comment: New changeset e73896241e55f452656fd8070eb79f344091bca0 by Serhiy Storchaka in branch '3.8': [3.8] bpo-41043: Escape literal part of the path for glob(). (GH-20994). (GH-21277) https://github.com/python/cpython/commit/e73896241e55f452656fd8070eb79f344091bca

[issue41043] Escape the literal part of the path for glob()

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

[issue41183] Workaround or fix for SSL "EE_KEY_TOO_SMALL" test failures

Larry Hastings added the comment: New changeset d565be84993a3d618add139cf21038e12c60a13e by Christian Heimes in branch '3.5': bpo-41183: Update test certs and keys (#21258) https://github.com/python/cpython/commit/d565be84993a3d618add139cf21038e12c60a13e --

[issue34542] [TLS] Update test certs to future proof settings

Larry Hastings added the comment: New changeset d565be84993a3d618add139cf21038e12c60a13e by Christian Heimes in branch '3.5': bpo-41183: Update test certs and keys (#21258) https://github.com/python/cpython/commit/d565be84993a3d618add139cf21038e12c60a13e -- nosy: +larry ___

[issue41183] Workaround or fix for SSL "EE_KEY_TOO_SMALL" test failures

Larry Hastings added the comment: Thanks for the backport! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ _

[issue34542] [TLS] Update test certs to future proof settings

Larry Hastings added the comment: I also needed a backport of this to 3.5. See #41183. Also, it looks like this issue should have been closed long ago, so I'll go ahead and do that. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.5

[issue41165] [Python 3.10] Remove APIs deprecated long enough

Christian Heimes added the comment: I'm all in favor to remove deprecated things, but please set a tangible deadline first. A lot of these functions have been deprecated for like a decade. Users tend to forget about deprecations or assume that removal was never going to happen. For example t

[issue41183] Workaround or fix for SSL ".._KEY_TOO_SMALL" test failures

Larry Hastings added the comment: Christian: Help! Again! I merged your PR, pulled a fresh copy, built it, and ran the test suite. I get seven failures in I think the same modules. Most of the failures are either "ssl.SSLError: [SSL] internal error (_ssl.c:728)", or some flavor of "OSErr

[issue41183] Workaround or fix for SSL ".._KEY_TOO_SMALL" test failures

Larry Hastings added the comment: Upgrading to release blocker. -- priority: high -> release blocker resolution: fixed -> stage: resolved -> needs patch status: closed -> open ___ Python tracker ___

[issue41183] Workaround or fix for SSL ".._KEY_TOO_SMALL" test failures

Christian Heimes added the comment: I'm testing with latest build of OpenSSL 1.1.1 and Fedora's DEFAULT crypto policy here. Your vendor may have configured OpenSSL with a more strict crypto policy. Could you please attach a full output of ./python -m test -v test_ssl? Does the 3.6 test sui

[issue41183] Workaround or fix for SSL ".._KEY_TOO_SMALL" test failures

Larry Hastings added the comment: test_ssl was one of the seven modules that failed. But attached here is just the output of % ./python -m test -v test_ssl >& test_ssl_failure -- Added file: https://bugs.python.org/file49287/test_ssl_failure ___

[issue41183] Workaround or fix for SSL ".._KEY_TOO_SMALL" test failures

Larry Hastings added the comment: The 3.6 branch of python/cpython fails as well on this machine. Output attached. -- Added file: https://bugs.python.org/file49288/test_ssl_36_branch ___ Python tracker ___

[issue41183] Workaround or fix for SSL ".._KEY_TOO_SMALL" test failures

Larry Hastings added the comment: I assume this is building against the system OpenSSL. On this machine, the "openssl", "libssl1.1", and "libssl-dev" packages are all version "1.1.1f-1ubuntu2". The OS is "Pop!_OS" version 20.04, which is a derivative of Ubuntu 20.04. It appears to be gett

[issue41165] [Python 3.10] Remove APIs deprecated long enough

Inada Naoki added the comment: I don't propose adding DeprecationWarning in 3.9 in this issue. I don't propose removing functions that don't emit DeprecationWarning. My first message is just a starting point. I don't propose to remove them all. --

[issue41165] [Python 3.10] Remove APIs deprecated long enough

Inada Naoki added the comment: For the record, I noticed DeprecationWarning is not shown by unittest.runner by default. For example, https://travis-ci.org/github/necaris/python3-openid/jobs/703119609 So deprecated aliases should be not removed in 3.10. -- __

[issue41183] Workaround or fix for SSL ".._KEY_TOO_SMALL" test failures

Christian Heimes added the comment: test_ssl_36_branch just contains "1 test failed: test_ssl". Could you please attach a verbose run? The problems are caused by security policy. We had similar issues in Fedora. - Set OPENSSL_TLS_SECURITY_LEVEL=2 as compiled-in minimum security lev

[issue41183] Workaround or fix for SSL ".._KEY_TOO_SMALL" test failures

Larry Hastings added the comment: ./python -m test -v test_ssl >& test_ssl_verbose_36_master -- Added file: https://bugs.python.org/file49290/test_ssl_verbose_36_master ___ Python tracker ___

[issue41183] Workaround or fix for SSL ".._KEY_TOO_SMALL" test failures

Larry Hastings added the comment: Do you need a temporary login on one of my Pop!_OS computers, in order to test? -- ___ Python tracker ___ ___

[issue41183] Workaround or fix for SSL ".._KEY_TOO_SMALL" test failures

Change by Christian Heimes : -- pull_requests: +20427 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/21278 ___ Python tracker ___ _

[issue41183] Workaround or fix for SSL ".._KEY_TOO_SMALL" test failures

Christian Heimes added the comment: GH-21278 takes care of test failures related to DH params. For the other test failures somebody has to backport df6ac7e2b82d921a6e9ff5571b40c6dbcf635581 to 3.6 and 3.5. I cannot promise that I'm able to find time to do the backport today. --

[issue41183] Workaround or fix for SSL ".._KEY_TOO_SMALL" test failures

Larry Hastings added the comment: Gotcha. Thanks for looking into it for me. I don't think the world is super anxious about getting 3.5.10rc1 so it's not a big huge deal. But I will wait to hear back from you. Thanks! -- ___ Python tracker

[issue41165] [Python 3.10] Remove APIs deprecated long enough

Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue41165] [Python 3.10] Remove APIs deprecated long enough

Inada Naoki added the comment: I found most of deprecated items in my first comment are aliving by difficult reasons. I grepped top 4000 packages and found some candidates to deprecate. ## turtle * settiltangle is not used anywhere. * tiltangle is also deprecated by docstring, but not in t

[issue18080] setting CC no longer overrides default linker for extension module builds on OS X

Jason R. Coombs added the comment: In [pypa/distutils#1](https://github.com/pypa/distutils/pull/1), I learned that the test doesn't have the intended effect. Patching `get_config_var()` has no effect because the function under test calls `get_config_vars()`. In some environments, such as PyP

[issue41165] [Python 3.10] Remove APIs deprecated long enough

Karthikeyan Singaravelan added the comment: > For the record, I noticed DeprecationWarning is not shown by unittest.runner > by default. There is an open issue for this but I think it's enabled by default https://bugs.python.org/issue39892 $ cat /tmp/test_bar.py import unittest import warni

[issue41192] Some audit events are undocumented

Change by Karthikeyan Singaravelan : -- nosy: +steve.dower ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue18080] setting CC no longer overrides default linker for extension module builds on OS X

Jason R. Coombs added the comment: For easy reference, the relevant commit is https://github.com/python/cpython/commit/97345680dc. -- ___ Python tracker ___ _

[issue41193] traceback when exiting on read-only file system

New submission from Zbyszek Jędrzejewski-Szmek : [Originally reported as https://bugzilla.redhat.com/show_bug.cgi?id=1852941.] $ touch ~/foo touch: cannot touch '/home/fedora/foo': Read-only file system $ python Python 3.9.0b3 (default, Jun 10 2020, 00:00:00) [GCC 10.1.1 20200507 (Red Hat 10.1.

[issue41193] traceback when exiting on read-only file system

Change by Zbyszek Jędrzejewski-Szmek : -- nosy: +asottile ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue41194] SIGSEGV in Python 3.9.0b3 in Python-ast.c:1412

New submission from Arcadiy Ivanov : Built with pyenv on Fedora 32. Discovered while testing PyBuilder for 3.9 compatibility. $ abrt gdb e6ad9db GNU gdb (GDB) Fedora 9.1-5.fc32 Copyright (C) 2020 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

[issue41194] SIGSEGV in Python 3.9.0b3 in Python-ast.c:1412

Arcadiy Ivanov added the comment: I can't seem to be able to attach a gziped coredump (7MB) -- ___ Python tracker ___ ___ Python-bu

[issue41194] SIGSEGV in Python 3.9.0b3 in Python-ast.c:1412

Change by Batuhan Taskaya : -- nosy: +BTaskaya ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue41194] SIGSEGV in Python 3.9.0b3 in Python-ast.c:1412

Batuhan Taskaya added the comment: @arcivanov what kind of input do you pass to the compile function which leads this crash? -- ___ Python tracker ___ ___

[issue41194] SIGSEGV in Python 3.9.0b3 in Python-ast.c:1412

STINNER Victor added the comment: Can you provide a script to reproduce the issue? -- nosy: +vstinner ___ Python tracker ___ ___ Py

[issue41194] SIGSEGV in Python 3.9.0b3 in Python-ast.c:1412

Arcadiy Ivanov added the comment: I'm right now rerunning the script with debug-level build of CPython and will report as soon as I have more data. Any word on limits for attaching core dump? -- ___ Python tracker

[issue41194] SIGSEGV in Python 3.9.0b3 in Python-ast.c:1412

Arcadiy Ivanov added the comment: I can say that it is always reproduced, both in Travis environment (Ubuntu) and in Fedora. -- ___ Python tracker ___ ___

[issue41193] traceback when exiting on read-only file system

Change by STINNER Victor : -- keywords: +patch nosy: +vstinner nosy_count: 2.0 -> 3.0 pull_requests: +20428 stage: -> patch review pull_request: https://github.com/python/cpython/pull/21279 ___ Python tracker __

[issue41162] Clear audit hooks after destructors

Change by Frank : -- nosy: +frankli ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/m

[issue41195] Interface to OpenSSL's security level

New submission from Matthew Hughes : While investigating Python's SSL I noticed there was no interface for interacting with OpenSSL's SSL_CTX_{get,set}_security_level (https://www.openssl.org/docs/manmaster/man3/SSL_CTX_get_security_level.html) so I thought I'd look into adding one (see attac

[issue41193] traceback when exiting on read-only file system

STINNER Victor added the comment: New changeset 0ab917e07ed64c6bfde6f6e791f9b28acc97b510 by Victor Stinner in branch 'master': bpo-41193: Ignore OSError in readline write_history() (GH-21279) https://github.com/python/cpython/commit/0ab917e07ed64c6bfde6f6e791f9b28acc97b510 -- _

[issue41193] traceback when exiting on read-only file system

Change by miss-islington : -- nosy: +miss-islington nosy_count: 3.0 -> 4.0 pull_requests: +20429 pull_request: https://github.com/python/cpython/pull/21280 ___ Python tracker _

[issue41193] traceback when exiting on read-only file system

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

[issue41195] Interface to OpenSSL's security level

Christian Heimes added the comment: I'm not sure it's a good idea to expose a setter for security level. In general the security level is a system-wide policy decision that should be controlled by administrators. Applications should not change this setting. Python libraries tend to follow ba

[issue41194] SIGSEGV in Python 3.9.0b3 in Python-ast.c:1412

Batuhan Taskaya added the comment: If you aren't able to share some reproducer snippets, would you try a bisect? An interesting commit would be this ac46eb4ad66 to try and check if this crash happens before and after it? -- ___ Python tracker

[issue18080] setting CC no longer overrides default linker for extension module builds on OS X

Ned Deily added the comment: Jason, what action(s) are you expecting with regard to this and by whom? This issue has been long closed. -- ___ Python tracker ___ _

[issue41195] Interface to OpenSSL's security level

Matthew Hughes added the comment: > Applications should not change this setting > A read-only getter for the policy sounds like a good idea, though. Thanks for the feedback, sounds reasonable to me. I'll happily work on getting a PR up for the read-only setter. -- __

[issue41193] traceback when exiting on read-only file system

miss-islington added the comment: New changeset 53d2b715d10e5c81cb9c86fd25e88ace4e41bc25 by Miss Islington (bot) in branch '3.8': bpo-41193: Ignore OSError in readline write_history() (GH-21279) https://github.com/python/cpython/commit/53d2b715d10e5c81cb9c86fd25e88ace4e41bc25 -- __

[issue41193] traceback when exiting on read-only file system

miss-islington added the comment: New changeset 0b4c87ef8f88a4c4c325e964fa4919cef3997605 by Miss Islington (bot) in branch '3.9': bpo-41193: Ignore OSError in readline write_history() (GH-21279) https://github.com/python/cpython/commit/0b4c87ef8f88a4c4c325e964fa4919cef3997605 -- __

[issue41193] traceback when exiting on read-only file system

STINNER Victor added the comment: Thanks Zbyszek for your bug report. It's now fixed in 3.8, 3.9 and master branches. -- components: +Library (Lib) resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue41193] traceback when exiting on read-only file system

Zbyszek Jędrzejewski-Szmek added the comment: Wow, that was quick. Thanks! -- ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue41175] Static analysis issues reported by GCC 10

Change by STINNER Victor : -- nosy: +vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue41193] traceback when exiting on read-only file system

STINNER Victor added the comment: Well, two errors were already ignored (bpo-19891). I just made the "except" more generic. I don't think that we can do anything more useless than ignoring the error if the filesystem is read-only. I don't think that a warning would be useful. -- __

[issue41183] Workaround or fix for SSL ".._KEY_TOO_SMALL" test failures

Larry Hastings added the comment: New changeset f52bf62fe12d46267e958f80dbe1f4425b55cd0f by Christian Heimes in branch '3.5': bpo-41183: Update finite DH params to 3072 bits (#21278) https://github.com/python/cpython/commit/f52bf62fe12d46267e958f80dbe1f4425b55cd0f -- __

[issue41195] Interface to OpenSSL's security level

Change by Matthew Hughes : -- pull_requests: +20431 stage: -> patch review pull_request: https://github.com/python/cpython/pull/21282 ___ Python tracker ___ __

[issue41194] SIGSEGV in Python 3.9.0b3 in Python-ast.c:1412

STINNER Victor added the comment: Can you please provide a reproducer? Does PyBuilder use C extensions? -- ___ Python tracker ___ _

[issue41194] SIGSEGV in Python 3.9.0b3 in Python-ast.c:1412

Arcadiy Ivanov added the comment: No C extensions, working on giving you a reproducer. -- ___ Python tracker ___ ___ Python-bugs-li

[issue41194] SIGSEGV in Python 3.9.0b3 in Python-ast.c:1412

Arcadiy Ivanov added the comment: How to reproduce: 1. Clone github.com/pybuilder/pybuilder 2. Checkout https://github.com/pybuilder/pybuilder/pull/724 3. Run `PYTHONWARNINGS=ignore python ./build.py -v -X` The failure occurs in the integration test smoke test in smoke_clean_tests.py ---

[issue41194] SIGSEGV in Python 3.9.0b3 in Python-ast.c:1412

Arcadiy Ivanov added the comment: Once any of the integration tests run, the integration test environment is created and the test can be run directly from the command line via: '.../pybuilder/target/venv/test/cpython-3.9.0.beta.3/bin/python' '.../pybuilder/src/integrationtest/python/smoke_cl

[issue41194] SIGSEGV in Python 3.9.0b3 in Python-ast.c:1412

Arcadiy Ivanov added the comment: My guess is that the issue is related to the sys.modules manipulation, i.e. these parts of the integration test harness: def smoke_test(self, *args): old_argv = list(sys.argv) del sys.argv[:] sys.argv.append(self.build_py)

[issue41194] SIGSEGV in Python 3.9.0b3 in Python-ast.c:1412

Arcadiy Ivanov added the comment: To complete this report, this is a regression. This exact code runs perfectly in 2.7, 3.5 - 3.8. This is the PR in Travis: https://travis-ci.org/github/pybuilder/pybuilder/builds/704312142 -- ___ Python tracker

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

STINNER Victor added the comment: Using https://github.com/sphinx-doc/sphinx/pull/7905 but without -W, I'm able to build the unmodified Python documentation with Sphinx 3! I tried c_allow_pre_v3=1. The PR was updated to add a second c_warn_on_allowed_pre_v3=0 option so we can keep -W.

[issue41194] SIGSEGV in Python 3.9.0b3 in Python-ast.c:1412

Arcadiy Ivanov added the comment: So as soon as I started using CPython 3.9.0b3 with debug, the stack trace changed and the corruption apparently occurs in the GC, probably because the assertion is triggered vs release-style build: Modules/gcmodule.c:114: gc_decref: Assertion "gc_get_ref

[issue41194] SIGSEGV in Python 3.9.0b3 in Python-ast.c:1412

Batuhan Taskaya added the comment: A shorter reproducer; >>> import sys >>> sys.modules.clear() Traceback (most recent call last): File "", line 1, in RuntimeError: lost builtins module >>> import _ast >>> import gc >>> gc.collect() Modules/gcmodule.c:114: gc_decref: Assertion "gc_get_refs(

[issue41194] SIGSEGV in Python 3.9.0b3 in Python-ast.c:1412

Arcadiy Ivanov added the comment: That's not an entirely accurate reproducer as the references to the modules are still held in the collection when the sys.modules.clear() is called. -- ___ Python tracker _

[issue41194] SIGSEGV in Python 3.9.0b3 in Python-ast.c:1412

Arcadiy Ivanov added the comment: > old_modules = dict(sys.modules) > sys.modules.clear() > sys.modules.update(old_modules) -- ___ Python tracker ___ _

[issue41194] SIGSEGV in Python 3.9.0b3 in Python-ast.c:1412

Change by Batuhan Taskaya : -- nosy: +pablogsal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue41194] SIGSEGV in Python 3.9.0b3 in Python-ast.c:1412

Change by Arcadiy Ivanov : -- components: +Interpreter Core type: -> crash ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue41194] SIGSEGV in Python 3.9.0b3 in Python-ast.c:1412

Batuhan Taskaya added the comment: If I'm not wrong, this is the commit that introduced the regression. commit ac46eb4ad6662cf6d771b20d8963658b2186c48c (HEAD -> bpo-x) Author: Dino Viehland Date: Wed Sep 11 10:16:34 2019 -0700 bpo-38113: Update the Python-ast.c generator to PEP384

[issue41194] SIGSEGV in Python 3.9.0b3 in Python-ast.c:1412

STINNER Victor added the comment: I can reproduce the crash using the following script.py: --- import gc; gc.set_threshold(5) import sys old_modules = dict(sys.modules) sys.modules.clear() sys.modules.update(old_modules) import _ast import gc gc.collect() --- And the command: --- ./python -i

[issue41073] [C API] PyType_GetSlot() should accept static types

hai shi added the comment: > You'll probably need some table like typeslots.inc to record which sub-slots > struct each slot belongs to. Looks like it's a good way to solve this probleam, Let me try it ;) -- ___ Python tracker

[issue32958] socket module calls with long host names can fail with idna codec error

Steve Bowman added the comment: When will this issue be fixed? Thanks! -- nosy: +sdbowman ___ Python tracker ___ ___ Python-bugs-l

[issue41194] SIGSEGV in Python 3.9.0b3 in Python-ast.c:1412

Change by STINNER Victor : -- keywords: +patch pull_requests: +20433 stage: -> patch review pull_request: https://github.com/python/cpython/pull/21284 ___ Python tracker ___ _

[issue41139] cgi uses the locale encoding for log files

Srinivas Reddy Thatiparthy(శ్రీనివాస్ రెడ్డి తాటిపర్తి) added the comment: I am for keeping this functionality. Unless others in this nosy list think otherwise. -- nosy: +thatiparthy ___ Python tracker ___

[issue41139] cgi uses the locale encoding for log files

Ethan Furman added the comment: Which functionality? - cgi.log() - opening with current locale I don't mind keeping the function, but if the file isn't already opened I think using UTF-8 is an appropriate choice. -- ___ Python tracker

[issue41196] APPDATA directory is different in store installed python

Change by aku911 : -- components: Windows nosy: aku911, paul.moore, steve.dower, tim.golden, zach.ware priority: normal severity: normal status: open title: APPDATA directory is different in store installed python type: behavior versions: Python 3.8

[issue41196] APPDATA directory is different in store installed python

New submission from aku911 : Install the windows store python then run this code: import os os.listdir(os.environ['APPDATA']) Install another version of python and run the same code. You'll get different results. This can cause issues when trying to share data in a user's APPDATA folder. --

[issue41196] APPDATA directory is different in store installed python

aku911 added the comment: This is causing this issue here: https://github.com/microsoft/vscode-python/issues/11412 -- ___ Python tracker ___ __

[issue41139] cgi uses the locale encoding for log files

Srinivas Reddy Thatiparthy(శ్రీనివాస్ రెడ్డి తాటిపర్తి) added the comment: My bad. I meant cgi.log(), I pressed submit changes in a hurry. +1 for utf-8. -- ___ Python tracker __

[issue41197] Async magic methods in contextlib.closing

New submission from Рамзан Б. : # Async magic methods in contextlib.closing I think `__aenter__` and `__aexit__` methods should be added to `contextlib.closing`, so that we can use `contextlib.closing` in async code too. For example: ```python3 class SomeAPI: ... async def request(se

[issue12029] Allow catching virtual subclasses in except clauses

Change by Simon Charette : -- nosy: +charettes ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue41197] Async magic methods in contextlib.closing

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

[issue41139] cgi uses the locale encoding for log files

Serhiy Storchaka added the comment: Available options: 1. Do nothing (keep cgi.log() and continue to use the default encoding for open()). 2. Remove cgi.log(). I think that the deprecation period is not needed because the function is not documented, is not imported by star-import, and is not

[issue41197] Async magic methods in contextlib.closing

Serhiy Storchaka added the comment: And what happen when you accidentally use synchronous "with" instead of "async with" with closing()? with closing(SomeAPI()) as api: ... I think it is intentionally that different functions/methods/classes are used for synchronous and asynchronous ope

[issue33665] tkinter.ttk.Scrollbar.fraction() under-estimates length

E. Paine added the comment: I agree that the `tkinter.ttk.Scrollbar.fraction` under-estimates the length of the trough and I have written a program to try to measure this precisely. When tested (only on Linux, granted), this deficit was measured to be 9 pixels (unless I got the maths wrong!)

[issue33665] tkinter.ttk.Scrollbar.fraction() under-estimates length

Change by E. Paine : Added file: https://bugs.python.org/file49293/ttkscrl.tcl ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue41197] Async magic methods in contextlib.closing

Ramzan Bekbulatov added the comment: In this case: ```python3 class A: async def close(self): pass with closing(A()): pass ``` Python will raise `RuntimeWarning: coroutine 'A.close' was never awaited`. In another case: ```python3 class B: def close(self): pa

[issue41180] marshal load bypass code.__new__ audit event

Steve Dower added the comment: Actually, a quick search of codeobject.c and a look at tkmk's PR makes it seem like the audit event should be being raised from inside PyCode_NewWithPosOnlyArgs anyway (which IIRC didn't exist when I first added the event, though it was probably there before it

[issue38980] Compile libpython with -fno-semantic-interposition

Gregory P. Smith added the comment: and to echo others: Do not worry about LD_PRELOAD users trying to override internals. That is not a supported use case. It is always a hack. anyone using it knows this. -- ___ Python tracker

[issue38980] Compile libpython with -fno-semantic-interposition

Gregory P. Smith added the comment: Yes this should become part of --with-optimizations when building on a platform using a compiler that (a) supports it and (b) where it matters. If this is only relevant on --enable-shared builds (not the default), i'd assume also make it conditional on tha

[issue41198] Round built-in function not shows zeros acording significant figures and calculates different numbers of odd and even

New submission from Carlos Neves : Hi, I am observing unexpected behavior with round built-in function about (1) significant figures in analytical methods and (2) number of odd and even numbers obtained by this function. https://docs.python.org/3/library/functions.html#round https://en.wiki

[issue41196] APPDATA directory is different in store installed python

Steve Dower added the comment: This is by (Windows's) design - separate apps are treated as separate by the Windows app model. In the latest and N-1 updates to Windows, the AppData redirection only applies to newly created files, not those that already exist. [1] Before then, it used copy-on

[issue41196] APPDATA directory is different in store installed python

Steve Dower added the comment: As an aside, virtual environments will have the same redirection as the base interpreter, so this is really only an issue between a 3.7 install and a 3.8 install, or a Store install and a traditional install. -- ___

[issue39960] Using typename.__setattr__ in extension type with Py_TPFLAGS_HEAPTYPE is broken (hackcheck too eager?)

Stefan Behnel added the comment: I think we missed the train for fixing 3.7 (which was questionable anyway), but I added a test, so it's ready for merging into 3.8+ (minus merge conflicts for the test in 3.8, probably). -- ___ Python tracker

[issue41177] ConvertingList and ConvertingTuple lack iterators and ConvertingDict lacks items()

Michael DePalatis added the comment: I think the other issue here is that the ConvertingX classes aren't documented apart from comments in the code where they are defined. -- nosy: +mivade ___ Python tracker __

[issue41198] Round built-in function not shows zeros acording significant figures and calculates different numbers of odd and even

Tim Peters added the comment: For the first, your hardware's binary floating-point has no concept of significant trailing zeroes. If you need such a thing, use Python's `decimal` module instead, which does support a "significant trailing zero" concept. You would need an entirely new data typ

[issue35105] Document that CPython accepts "invalid" identifiers

Roy Smith added the comment: Just as another edge case, type() can do the same thing: Foo = type("Foo", (object,), {"a b": 1}) f = Foo() for example, will create a class attribute named "a b". Maybe this actually calls setattr() under the covers, but if it's going to be documented, it shoul

[issue41198] Round built-in function not shows zeros acording significant figures and calculates different numbers of odd and even

Steven D'Aprano added the comment: Thank you for your long and detailed bug report, but please post one issue per bug report. Tim, we agree that the notion of significant figures is irrelevant; is Carlos' even/odd test sufficiently flawed that we should close this bug report, or keep it ope

[issue41198] Round built-in function not shows zeros acording significant figures and calculates different numbers of odd and even

Carlos Neves added the comment: Hi Peters, I will pay more attention to the Python docs :) Thank you for your direction. Carlos A. Neves Em qui., 2 de jul. de 2020 às 18:22, Tim Peters escreveu: > > > Tim Peters added the comment: > > For the first, your hardware's binary floating-point has

[issue41198] Round built-in function not shows zeros acording significant figures and calculates different numbers of odd and even

Tim Peters added the comment: I assumed Mark would tell us what's up with the arange() oddity, so let's see whether he does. There is no truly good way to generate "evenly spaced" binary floats using a non-representable conceptual decimal delta. The dumbass ;-) way doesn't show a discrepan

  1   2   >