[issue38216] Fix for issue30458 prevents crafting invalid requests

Karthikeyan Singaravelan added the comment: For reference this is how urllib handled the same issue in their test suite : https://github.com/urllib3/urllib3/pull/1673. golang also received similar regression report as the change landed in 1.11.6 and discussion : https://github.com/golang/go/

[issue16684] Unicode property value abbreviated names and long names

Greg Price added the comment: I've gone and implemented a version of this that's integrated into Tools/unicode/makeunicodedata.py , and into the unicodedata module. Patch attached. Demo: >>> import unicodedata, pprint >>> pprint.pprint(unicodedata.property_value_aliases) {'bidirectional':

[issue38154] test__xxsubinterpreters: random failures on AMD64 FreeBSD CURRENT Shared 3.x

Change by Kyle Stanley : -- keywords: +patch pull_requests: +15879 stage: -> patch review pull_request: https://github.com/python/cpython/pull/16293 ___ Python tracker ___ ___

[issue38154] test__xxsubinterpreters: random failures on AMD64 FreeBSD CURRENT Shared 3.x

Kyle Stanley added the comment: For an updated explanation of the PR, see https://bugs.python.org/msg352835 or the comments in the PR itself. -- stage: patch review -> ___ Python tracker __

[issue37812] Make implicit returns explicit in longobject.c (in CHECK_SMALL_INT)

Greg Price added the comment: > labeling long-stable code as "evil". Let me apologize about this bit -- I was thinking of the term in quotes (referring to the earlier comment), but I didn't write it clearly that way. I don't think any of this code is evil, past or present, and I regret that

[issue38225] iscoroutinefunction broken with cython - allow tagging of functions as async?

Andrew Svetlov added the comment: I think `func.__awaitable__ = True` can serve all possible situations. We need it for async mocks (now the library use flawless `_is_coroutine` approach. `__awaitable__` can also cover cases where a regular function returns awaitable object or there is a c

[issue38216] Fix for issue30458 prevents crafting invalid requests

Change by Matej Cepl : -- nosy: +mcepl ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.or

[issue38230] A Path Traversal vulnerability in ssl_servers.py

New submission from longwenzhang : There is a Path Traversal vulnerability in https://github.com/python/cpython/blob/master/Lib/test/ssl_servers.py (on windows platform), Steps to reproduce: 1.Run the script https://github.com/python/cpython/blob/master/Lib/test/ssl_servers.py 2.If you visit

[issue38230] A Path Traversal vulnerability in ssl_servers.py

Karthikeyan Singaravelan added the comment: Is this only about the test/ssl_servers.py ? I am not sure they are meant to be used by users and might have path access for tests. -- nosy: +xtreak ___ Python tracker

[issue38230] A Path Traversal vulnerability in test/ssl_servers.py

Change by Karthikeyan Singaravelan : -- title: A Path Traversal vulnerability in ssl_servers.py -> A Path Traversal vulnerability in test/ssl_servers.py ___ Python tracker ___

[issue38225] iscoroutinefunction broken with cython - allow tagging of functions as async?

Change by Emmanuel Arias : -- nosy: +eamanu ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue38231] Documentation search results focus on tutorials and not language specifications

New submission from Matt : * Problem: Documentation search results favor tutorials and over language specifications * How to reproduce: I often forget simple syntax. For example, say I want to raise an exception. Clearly, I need to search for "raise". 1. Go to https://docs.python.org/3.6

[issue38216] Fix for issue30458 prevents crafting invalid requests

Gregory P. Smith added the comment: All bug fixes are behavior changes. Any broken behavior can be relied upon by someone. So far the only ones who have popped up with this change as being a problem is one project's test suite where the behavior was used by a test because it was a convenie

[issue37353] Source code has not always been forward-compatible

Zachary Ware added the comment: New changeset 062cfe3b11c61d03ccc2915e360f9b0d80e23642 by Zachary Ware (Prateek Nayak) in branch 'master': bpo-37353: Updated parser note about source code compatibility(GH-14277) https://github.com/python/cpython/commit/062cfe3b11c61d03ccc2915e360f9b0d80e23642

[issue37353] Source code has not always been forward-compatible

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

[issue37353] Source code has not always been forward-compatible

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

[issue37353] Source code has not always been forward-compatible

Change by Zachary Ware : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.7, Python 3.8, Python 3.9 ___ Python tracker ___ __

[issue37353] Source code has not always been forward-compatible

miss-islington added the comment: New changeset 2552e27b752f449b1d7046b384b14db0a69f46ad by Miss Islington (bot) in branch '3.7': bpo-37353: Updated parser note about source code compatibility(GH-14277) https://github.com/python/cpython/commit/2552e27b752f449b1d7046b384b14db0a69f46ad --

[issue38216] Fix for issue30458 prevents crafting invalid requests

Jason R. Coombs added the comment: Thanks for all the comments. I agree the current (secure by default) implementation is desirable. I also agree that such usage was never explicitly supported, so the "regression" here is perhaps over-stated. What I seek is to avoid the Go recommendation of

[issue37353] Source code has not always been forward-compatible

miss-islington added the comment: New changeset 0ab6b01820afef44beea8158ba08b6469bf264a0 by Miss Islington (bot) in branch '3.8': bpo-37353: Updated parser note about source code compatibility(GH-14277) https://github.com/python/cpython/commit/0ab6b01820afef44beea8158ba08b6469bf264a0 --

[issue38232] empty local-part in addr_spec displayed incorrectly

New submission from Andrei Troie : Given an (RFC-legal) email address with the local part consisting of a quoted empty string (e.g. 'Nobody <""@example.org>'), when I call the 'addr_spec' property, the result no longer includes the quoted empty string (so, in this case, addr_spec would return

[issue38233] datetime.datetime.fromtimestamp have different behaviour on windows and mac

New submission from Alexandre Ouellet : in a python console on a windows machine: import datetime d = datetime.datetime.fromtimestamp(0) d >datetime.datetime(1969, 12, 31, 19, 0) d.timestamp() >OSError: [Errno 22] Invalid argument on a macOS machine : d = datetime.datetime.fromtimestamp(-1)

[issue30129] functools.partialmethod should look more like what it's impersonating.

Sylvain Marie added the comment: For future reference if this topic re-opens, there is now an alternative here: https://smarie.github.io/python-makefun/#removing-parameters-easily Note: it relies on a dynamic `compile` statement so of course it is less optimal than the one in functools. But

[issue37937] Mention ``frame.f_trace`` in :func:`sys.settrace` docs.

Nick Coghlan added the comment: New changeset 9c2682efc69568e1b42a0c1759489d6f2e3b30ea by Nick Coghlan (Ram Rachum) in branch 'master': bpo-37937: Mention frame.f_trace in sys.settrace docs (GH-15439) https://github.com/python/cpython/commit/9c2682efc69568e1b42a0c1759489d6f2e3b30ea

[issue37937] Mention ``frame.f_trace`` in :func:`sys.settrace` docs.

Change by miss-islington : -- keywords: +patch pull_requests: +15882 stage: -> patch review pull_request: https://github.com/python/cpython/pull/16296 ___ Python tracker ___ _

[issue37937] Mention ``frame.f_trace`` in :func:`sys.settrace` docs.

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

[issue38234] The value of Py_SetPath is not used to populate the configuration

New submission from Pablo Galindo Salgado : When calling Py_SetPath(), the value that is passed in is ignored. -- components: Interpreter Core keywords: 3.8regression messages: 352856 nosy: pablogsal, vstinner priority: normal severity: normal status: open title: The value of Py_SetPath

[issue38234] The value of Py_SetPath is not used to populate the configuration

STINNER Victor added the comment: It's a 3.8 regression: I set the priority to release blocker. -- nosy: +lukasz.langa priority: normal -> release blocker ___ Python tracker _

[issue37937] Mention ``frame.f_trace`` in :func:`sys.settrace` docs.

Nick Coghlan added the comment: Thanks for the PR, Ram, and the initial review, Serhiy. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.7, Python 3.8 ___ Python tracker

[issue38234] The value of Py_SetPath is not used to populate the configuration

Pablo Galindo Salgado added the comment: A very simple way to reproduce the bug: Using pyInstaller, after applying these patches (to fix other Python3.8 issues) https://github.com/pyinstaller/pyinstaller/pull/4441 https://github.com/pyinstaller/pyinstaller/pull/4440 you will get Fatal Pytho

[issue37937] Mention ``frame.f_trace`` in :func:`sys.settrace` docs.

miss-islington added the comment: New changeset fd4f28d894ee55d7ee1625c726c1859fcd1e2249 by Miss Islington (bot) in branch '3.7': bpo-37937: Mention frame.f_trace in sys.settrace docs (GH-15439) https://github.com/python/cpython/commit/fd4f28d894ee55d7ee1625c726c1859fcd1e2249 -- nos

[issue37937] Mention ``frame.f_trace`` in :func:`sys.settrace` docs.

miss-islington added the comment: New changeset c410390e89071c4a4c2a437a227c14274add4116 by Miss Islington (bot) in branch '3.8': bpo-37937: Mention frame.f_trace in sys.settrace docs (GH-15439) https://github.com/python/cpython/commit/c410390e89071c4a4c2a437a227c14274add4116 -- __

[issue38234] The value of Py_SetPath is not used to populate the configuration

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

[issue38232] empty local-part in addr_spec displayed incorrectly

Change by Andrei Troie : -- versions: +Python 3.9 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue38234] The value of Py_SetPath is not used to populate the configuration

STINNER Victor added the comment: That's a regression that I introduced between Python 3.7 and 3.8 when refactoring _PyCoreConfig/_PyPathConfig code into PyConfig/_PyPathConfig. Previously, if Py_SetPath() was called, the specified string was used to fill config->module_search_paths. Now, t

[issue38233] datetime.datetime.fromtimestamp have different behaviour on windows and mac

Ammar Askar added the comment: Thanks for the report Alexandre, this has to do with issues with negative numbers in Window's time APIs. There's already a bug open for this, so I've marked it as a duplicate. -- nosy: +ammar2 resolution: -> duplicate stage: -> resolved status: open -

[issue38231] Documentation search results focus on tutorials and not language specifications

Ammar Askar added the comment: This is a great point Matt, the documentation search is a bit lacking and we're kind of using https://bugs.python.org/issue34398 and https://github.com/python/cpython/pull/8773 to track it. The current idea that Julien, the docs expert, had is to add some sort

[issue34398] Docs search should prominently show definitions and glossary items

Ammar Askar added the comment: Changing the title a little to represent that this is now a general improvement of the docs search. Julien is working to upstream a solution into Sphinx that will allow any items to be featured prominently on search. -- title: Docs search does not index

[issue38235] Docs of logging module says argument is named "lvl". TypeError.

New submission from Daniel Andersson : How to reproduce: >>> import logging >>> logging.disable(lvl=logging.ERROR) Traceback (most recent call last): File "", line 1, in TypeError: disable() got an unexpected keyword argument 'lvl' The correct keyword argument name is `level` as can be seen

[issue38231] Documentation search results focus on tutorials and not language specifications

Matt added the comment: I will close this issue and post in one of the two places you linked. Thank you for your prompt reply and affirmation of my observations. I feel my language was colored by frustration, yet you focused instead on my willingness to help. I appreciate that and find you

[issue38231] Documentation search results focus on tutorials and not language specifications

Ammar Askar added the comment: > Somewhat related, I am responding to this through the bugs.python.org > interface. If I reply directly to the email the tracker sent me, will my > reply be properly routed to this thread? Yes, it will :) The bug tracker allows replies by email. --

[issue38236] Dump the Python path configuration at the first import error

New submission from STINNER Victor : When Python path configuration is not properly configured, Python fails with an error looking like: --- Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding Python runtime state: core initialized ModuleNotFoundErro

[issue38093] Update MagicMock __aenter__ and __aexit__ to return AsyncMock's

Change by Lisa Roach : -- pull_requests: +15885 pull_request: https://github.com/python/cpython/pull/16299 ___ Python tracker ___ __

[issue38216] Fix for issue30458 prevents crafting invalid requests

Tim Burke added the comment: > Since at least one project is known to have been impacted, it's not > unreasonable to expect that more will be. I can confirm at least one other: OpenStack Swift's stable jobs have been broken by https://github.com/python/cpython/commit/bb8071a since 11 Sep; se

[issue38234] The value of Py_SetPath is not used to populate the configuration

STINNER Victor added the comment: > Fatal Python error: init_fs_encoding: failed to get the Python codec of the > filesystem encoding I created bpo-38236 "Dump the Python path configuration at the first import error" which should ease to debug such issues. -- __

[issue6559] add pass_fds paramter to subprocess.Popen()

miss-islington added the comment: New changeset 77abf23c67c1a465a8899666c69f6bcd6930e003 by Miss Islington (bot) (Orivej Desh) in branch 'master': bpo-6559: Update _posixsubprocess.fork_exec doc (GH-16283) https://github.com/python/cpython/commit/77abf23c67c1a465a8899666c69f6bcd6930e003 ---

[issue38236] Dump the Python path configuration at the first import error

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

[issue38236] Dump the Python path configuration at the first import error

STINNER Victor added the comment: Without my change: --- vstinner@apu$ PYTHONHOME=/xxx ./python Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding Python runtime state: core initialized ModuleNotFoundError: No module named 'encodings' Current thr

[issue38236] Dump the Python path configuration at the first import error

STINNER Victor added the comment: > user site = 1 > import site = 1 I'm not sure that dumping these configuration variables are useful to debug this very specific error: "Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding" They only have an

[issue35696] remove unnecessary operation in long_compare()

STINNER Victor added the comment: I reopen the issue. The win32 job of Azure Pipelines now logs a compiler warning: Objects\longobject.c(412,5): warning C4244: 'function': conversion from 'unsigned long' to 'sdigit', possible loss of data Objects\longobject.c(420,5): warning C4244: 'functi

[issue38237] Expose meaningful keyword arguments for pow()

New submission from Raymond Hettinger : Current signature: pow(x, y, z=None, /) Proposed signature: pow(base, exp, mod=None) Benefits: * Meaningful and self-explanatory parameters in tooltips * Optionally clearer calls for the three argument form: pow(2, 5, mod=4) * More u

[issue38235] Docs of logging module says argument is named "lvl". TypeError.

Change by Raymond Hettinger : -- assignee: docs@python -> rhettinger nosy: +rhettinger versions: -Python 3.5, Python 3.6 ___ Python tracker ___ ___

[issue38237] Expose meaningful keyword arguments for pow()

Ammar Askar added the comment: Looks like a solid proposal, I especially like the clarity for the 3-argument call. Often beginners ask about why there's a third argument in pow especially when teaching RSA and number-theoretic stuff. Do you mind if I take this on Raymond? -- nosy: +

[issue38237] Expose meaningful keyword arguments for pow()

Ammar Askar added the comment: Actually quick question, should a similar change be made for `math.pow` for consistency's sake? -- ___ Python tracker ___ _

[issue38237] Expose meaningful keyword arguments for pow()

Change by Ammar Askar : -- keywords: +patch pull_requests: +15887 stage: -> patch review pull_request: https://github.com/python/cpython/pull/16302 ___ Python tracker ___

[issue38237] Expose meaningful keyword arguments for pow()

Ammar Askar added the comment: I've made a PR, feel free to close it if you'd rather implement this yourself or this proposal won't be accepted :) -- ___ Python tracker ___ _

[issue38237] Expose meaningful keyword arguments for pow()

Serhiy Storchaka added the comment: You can use a lambda instead of partial: squared = lambda x: pow(x, 2) Proposed names look meaningful. But after adding support of keyword arguments please compare performance of the old and the new functions. I expect that the difference will be smal

[issue38237] Expose meaningful keyword arguments for pow()

Ammar Askar added the comment: Here's a little microbenchmark, let me know if there's anything specific you'd like to see: Before == > python -m pyperf timeit "from test.test_builtin import BuiltinTest; tst = > BuiltinTest()" -- "tst.test_pow()" Mean +- std dev: 3.80 us +- 0.23 us > p

[issue7897] Support parametrized tests in unittest

Andre Herbst added the comment: +1 for the feature Subtests make the test results of all asserts visible at test execution time but decrease the readability of a test: @parameterized([2,4,6]) def test_method_whenCalled_returnsNone(self, a): # 1) arrange something = Something() #

[issue35696] remove unnecessary operation in long_compare()

Sergey Fedoseev added the comment: These warnings are caused by https://github.com/python/cpython/commit/c6734ee7c55add5fdc2c821729ed5f67e237a096. I'd fix them, but I'm not sure if we are going to restore CHECK_SMALL_INT() ¯\_(ツ)_/¯ -- nosy: +sir-sigurd _

[issue38238] site.py reporting user site info even if ENABLE_USER_SITE=False

New submission from Barry Muldrey : site info is accessed externally via getusersitepackages() and getuserbase()... for example see "pip/_internal/locations.py" If ENABLE_USER_SITE is set to "False," or otherwise disabled, accesses to these methods should return '' or None (shouldn't they?).

[issue38238] site.py reporting user site info even if ENABLE_USER_SITE=False

Change by Barry Muldrey : -- keywords: +patch pull_requests: +15888 stage: -> patch review pull_request: https://github.com/python/cpython/pull/16303 ___ Python tracker ___ __

[issue38237] Expose meaningful keyword arguments for pow()

Mark Dickinson added the comment: The proposal sounds reasonable to me. > should a similar change be made for `math.pow` for consistency's sake? I'd leave math.pow alone here. -- ___ Python tracker ___

[issue38237] Expose meaningful keyword arguments for pow()

Serhiy Storchaka added the comment: Thank you. Could you please test simpler examples like pow(2, 3)? Please use the --duplicate option. -- ___ Python tracker ___ ___

[issue38237] Expose meaningful keyword arguments for pow()

Serhiy Storchaka added the comment: And pow(2.0, 3.0) please. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue25244] Idle: refine right-click behavior

Change by Terry J. Reedy : -- versions: +Python 3.9 -Python 2.7, Python 3.4, Python 3.5, Python 3.6 ___ Python tracker ___ ___ Pytho

[issue25488] IDLE: Remove '', user_dir, and idlelib from sys.path when added

Change by Terry J. Reedy : -- versions: +Python 3.9 -Python 2.7, Python 3.5, Python 3.6, Python 3.7 ___ Python tracker ___ ___ Pytho

[issue1207613] Idle Editor: Bottom Scroll Bar

Terry J. Reedy added the comment: A horizontal text bar is added to a text view as needed (recent patch) when one is used for the font sample. The latter fits or not according to the font size. The same could be used for editor, or better, editor windows could inherit from text views. ---

[issue26949] IDLE restarts when one debugs code raising SystemExit

Terry J. Reedy added the comment: >>> raise SystemExit does not normally cause a restart. -- nosy: -kbk, roger.serwy versions: +Python 3.9 -Python 2.7, Python 3.5, Python 3.6 ___ Python tracker

[issue38216] Fix for issue30458 (HTTP Header Injection) prevents crafting invalid requests

Change by STINNER Victor : -- title: Fix for issue30458 prevents crafting invalid requests -> Fix for issue30458 (HTTP Header Injection) prevents crafting invalid requests ___ Python tracker

[issue28840] IDLE: Document tk's long line display limitation

Terry J. Reedy added the comment: IDLE Help's newish section "User Output in Shell" makes some mention of this but a bit more is still needed. -- stage: test needed -> needs patch versions: +Python 3.9 -Python 2.7, Python 3.5, Python 3.6, Python 3.7 __

[issue38187] test.test_tools.test_c_analyzer fails in refleak mode

Change by Eric Snow : -- pull_requests: +15890 pull_request: https://github.com/python/cpython/pull/16304 ___ Python tracker ___ ___

[issue21973] IDLE: catch user cfg file error, better error message, continue

Change by Terry J. Reedy : -- nosy: -kbk, roger.serwy versions: +Python 3.9 -Python 2.7, Python 3.5, Python 3.6, Python 3.7 ___ Python tracker ___

[issue23218] Modernize the IDLE Find/Replace/Find in Files dialogs

Change by Terry J. Reedy : -- versions: +Python 3.9 -Python 2.7, Python 3.4, Python 3.5 ___ Python tracker ___ ___ Python-bugs-list

[issue3559] IDLE: Pasted newline doesn't trigger execution when typed newline would

Change by Terry J. Reedy : -- versions: +Python 3.9 -Python 2.7, Python 3.5, Python 3.6 ___ Python tracker ___ ___ Python-bugs-list m

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

STINNER Victor added the comment: New changeset bc2256ea177a653bcab15b06b5f5725b10c1fff3 by Victor Stinner in branch 'master': bpo-33694: Remove test_asyncio ProactorDatagramTransportTests (GH-16288) https://github.com/python/cpython/commit/bc2256ea177a653bcab15b06b5f5725b10c1fff3 -

[issue25733] Code and IDLE should catch all compile errors.

Change by Terry J. Reedy : -- versions: +Python 3.9 -Python 2.7, Python 3.5, Python 3.6 ___ Python tracker ___ ___ Python-bugs-list

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

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

[issue38205] Py_UNREACHABLE() no longer behaves as a function call

STINNER Victor added the comment: New changeset b1542583bee204130934c2b90684041e29378250 by Victor Stinner in branch 'master': bpo-38205: Py_UNREACHABLE() calls Py_FatalError() (GH-16290) https://github.com/python/cpython/commit/b1542583bee204130934c2b90684041e29378250 -- _

[issue37857] Setting logger.level directly has no effect due to caching in 3.7+

Zane Bitter added the comment: In turns out that setting the level directly is used in the standard library, so we definitely have a bug here that needs fixing in 3.7 & 3.8. Obviously the fix could be just to stop doing that in the standard library, but I'd argue that this is even stronger e

[issue38205] Py_UNREACHABLE() no longer behaves as a function call

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

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

Change by STINNER Victor : -- pull_requests: -12891 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

Change by STINNER Victor : -- pull_requests: -13220 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

Change by STINNER Victor : -- pull_requests: -13649 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

Change by STINNER Victor : -- pull_requests: -14111 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

Change by STINNER Victor : -- pull_requests: -13661 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

Change by STINNER Victor : -- pull_requests: -13643 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

Change by STINNER Victor : -- pull_requests: -13656 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

Change by STINNER Victor : -- pull_requests: -13642 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

Change by STINNER Victor : -- pull_requests: -13625 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

Change by STINNER Victor : -- pull_requests: -13676 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

Change by STINNER Victor : -- pull_requests: -10267 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

Change by STINNER Victor : -- pull_requests: -13627 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

Change by STINNER Victor : -- pull_requests: -13654 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

Change by STINNER Victor : -- pull_requests: -13663 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

miss-islington added the comment: New changeset b50edac42fd39d58ba51eb9cee2d3645a2e28ca4 by Miss Islington (bot) in branch '3.8': bpo-33694: Remove test_asyncio ProactorDatagramTransportTests (GH-16288) https://github.com/python/cpython/commit/b50edac42fd39d58ba51eb9cee2d3645a2e28ca4 --

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

Change by STINNER Victor : -- pull_requests: -13660 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

Change by STINNER Victor : -- pull_requests: -15156 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

Change by STINNER Victor : -- pull_requests: -14161 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue38237] Expose meaningful keyword arguments for pow()

Ammar Askar added the comment: Before == >python -m pyperf timeit "pow(2, 3)" --duplicate 10 Mean +- std dev: 242 ns +- 19 ns > python -m pyperf timeit "pow(2.0, 3.0)" --duplicate 10 Mean +- std dev: 197 ns +- 16 ns After = > python -m pyperf timeit "pow(2, 3)" --duplicate 1

  1   2   >