[issue35369] List sorting makes duplicate comparisons

Tim Peters added the comment: Yup, it can do some redundant comparisons; more on that here: https://mail.python.org/pipermail/python-dev/2018-August/155020.html I'm not inclined to make this already-difficult code even harder to understand for something that's quite likely not to matter -

[issue33130] functools.reduce signature uses `iterable`, documentation should use the same term

Ben Finney added the comment: Hah, sorry to use a local-filesystem URL. (Hooray for locally-installed developer documentation!) The same section is online at https://docs.python.org/3/library/functools.html#functools.reduce . -- ___ Python

[issue33130] functools.reduce signature uses `iterable`, documentation should use the same term

Ben Finney added the comment: The library documentation (e.g. file:///usr/share/doc/python3/html/library/functools.html#functools.reduce ) also has this dissonance: > functools.reduce(`function`, `iterable` [, `initializer` ]) > >Apply function of two arguments cumulatively to the

[issue35354] Generator functions stack overflow

Karthikeyan Singaravelan added the comment: Brett, the user had an invalid email address in their profile thus adding comments to the issue caused a server error while sending notification to them. So they have been removed from the issue. Please see :

[issue35369] List sorting makes duplicate comparisons

Change by David Wyde : Added file: https://bugs.python.org/file47963/sort.py ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue35369] List sorting makes duplicate comparisons

New submission from David Wyde : Python's Timsort sometimes makes the same comparison twice. This leads to extra compares, which can hurt performance. Python sorts several length-3 permutations in 4 steps, and the problem accumulates with bigger data. There are ~9,800 duplicate less-than

[issue34850] Emit a syntax warning for "is" with a literal

Nathaniel Smith added the comment: > In my experience people are more likely to run code through a linter than > they are to ever run an interpreter with DeprecationWarning enabled. This used to be true, and it was a disaster. So there's been a lot of work to fix it, and it's not true

[issue34850] Emit a syntax warning for "is" with a literal

Barry A. Warsaw added the comment: I'm actually fine either way. Consider me a solid ±0 -- ___ Python tracker ___ ___

[issue34850] Emit a syntax warning for "is" with a literal

Steven D'Aprano added the comment: Looks like we have a stand-off between core devs, and no BDFL to make a ruling. There is support for the feature from at least Barry and Raymond (although I think Guido was cool on the idea, maybe?). Gregory, do you feel strongly enough about this that

[issue34850] Emit a syntax warning for "is" with a literal

Gregory P. Smith added the comment: Given that linters like pylint can already detect the common case of this issue when using `is` and `is not` to compare to a literal where == or != seems more appropriate, I don't think a warning is very useful. In my experience people are more likely to

[issue33015] Fix function cast warning in thread_pthread.h

STINNER Victor added the comment: > I don't think it is crazy for 2.7, but I'd move that to its own issue as you > already nicely addressed the problem related to this PR without needing that. Good idea. I created bpo-35368. I close this issue since it's now fixed. -- resolution:

[issue35368] [2.7] Make PyMem_Malloc() thread-safe in debug mode

Change by STINNER Victor : -- keywords: +patch pull_requests: +10076 stage: -> patch review ___ Python tracker ___ ___

[issue35368] [2.7] Make PyMem_Malloc() thread-safe in debug mode

New submission from STINNER Victor : While fixing bpo-33015, I discovered that PyMem_Malloc() isn't thread-safe when Python is compiled in debug mode: https://bugs.python.org/issue33015#msg330806 I wrote PR 10828 to make PyMem_Malloc() thread-safe when Python is compiled in debug mode.

[issue33015] Fix function cast warning in thread_pthread.h

Gregory P. Smith added the comment: I don't think it is crazy for 2.7, but I'd move that to its own issue as you already nicely addressed the problem related to this PR without needing that. -- ___ Python tracker

[issue34850] Emit a syntax warning for "is" with a literal

Nathaniel Smith added the comment: Would it be more acceptable to use a DeprecationWarning? It's not really the right thing because we're not planning to ever actually remove the functionality. But, we've already gone to a lot of trouble to try to show DeprecationWarnings specifically to

[issue33015] Fix function cast warning in thread_pthread.h

STINNER Victor added the comment: > why was that only an issue on 2.7? I added PyMem_RawMalloc() to Python 3.4 and this function must be thread-safe. https://docs.python.org/dev/c-api/memory.html#raw-memory-interface "These functions are thread-safe, the GIL does not need to be held." I

[issue33015] Fix function cast warning in thread_pthread.h

Gregory P. Smith added the comment: why was that only an issue on 2.7? -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue35352] test_asyncio fails on RHEL8, or on Fedora using NEXT security policy

STINNER Victor added the comment: I tested on Fedora 29 using: sudo update-crypto-policies --set NEXT With this config, I was able to reproduce the test_asyncio failure on 3.6, 3.7 and master branches. I confirm that the commits fixed test_asyncio in these 3 branches. Thanks

[issue34850] Emit a syntax warning for "is" with a literal

Change by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35365] Use wchar_t* buffer instead of Unicode object in code page decoder

Change by Serhiy Storchaka : -- keywords: +patch pull_requests: +10075 stage: -> patch review ___ Python tracker ___ ___

[issue29657] os.symlink: FileExistsError shows wrong message

Rich Jones added the comment: @Larry - that would be an acceptable solution! I'm here because I encountered this error independently. I explain why the arrow is a problem here: https://bugs.python.org/issue35367 The issue is that the '->' notation is already used by the standard operating

[issue31177] unittest mock's reset_mock throws an error when an attribute has been deleted

Change by Eli_B : -- pull_requests: +10074 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35367] FileExistsError During os.symlink() Displays Arrow in the Wrong Direction

Change by Eryk Sun : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> os.symlink: FileExistsError shows wrong message ___ Python tracker

[issue35367] FileExistsError During os.symlink() Displays Arrow in the Wrong Direction

New submission from Rich Jones : If I try to create a symlink which already exists, I get a FileExistsError. In this error message, the explanatory arrow is pointing in the wrong direction. This gave us a big scare in our logs! Example: ``` $ ls HELLO.txt $ python3 Python 3.7.0 (default,

[issue34850] Emit a syntax warning for "is" with a literal

Terry J. Reedy added the comment: I like this proposal better than a separate test mode. But users will see compiler warnings for main modules and for packages recompiled for a new version or for a maintenance releases with a byte code bump, and for unprecompiled packages on systems that

[issue35354] Generator functions stack overflow

Brett Cannon added the comment: How did you make a recursive generator? The 'yield' would have paused execution. Do you have code you can share to reproduce? Otherwise blowing your stack out is normal behaviour in a function which you can deal with by lowering your stack depth with

[issue34867] Add mode to disable small integer and interned string caches

Terry J. Reedy added the comment: Steven, thank you for splitting this off for proper discussion. To me, the base issue is that CPython is both the language reference implementation and, as yet, the main production implementation. As the latter, it has unintended and unwanted bugs and

[issue35366] Monkey Patching class derived from ctypes.Union doesn't work

Martijn Pieters added the comment: This is a repeat of old-tracker issue 1700288, see https://github.com/python/cpython/commit/08ccf202e606a08f4ef85df9a9c0d07e1ba1#diff-998bfefaefe2ab83d5f523e18f158fa4, which fixed this for StructType_setattro but failed to do the same for

[issue35358] Document that importlib.import_module accepts names that are not valid Python syntax

Brett Cannon added the comment: I agree that this shouldn't change and at best can be a documentation update to mention the fact that importlib.import_module() doesn't restrict itself to valid syntax names on purpose. -- assignee: -> docs@python components: +Documentation nosy:

[issue35352] test_asyncio fails on RHEL8

STINNER Victor added the comment: I leave the issue open until someone validates manually that the issue os fixed in all branches with stricter security (ex: RHEL8). -- ___ Python tracker

[issue35352] test_asyncio fails on RHEL8

STINNER Victor added the comment: New changeset 02250e57c37339ea6de08ab077a307e75eef02f5 by Victor Stinner in branch '3.6': bpo-35352: test_asyncio uses the certificate set from the test directory (GH-10826) (GH-10832)

[issue35352] test_asyncio fails on RHEL8

STINNER Victor added the comment: New changeset 38bed786a219c65d5a51c7ef4ffd97e12653a095 by Victor Stinner in branch '3.7': [3.7] bpo-35352: test_asyncio uses the certificate set from the test directory (GH-10826) (GH-10834)

[issue35366] Monkey Patching class derived from ctypes.Union doesn't work

New submission from Vijay : I am trying to "monkey patch" a class derived from Python ctypes "Union", but I am unable to do so - getting weird errors and sometimes seg-faults. The same thing works quite well when deriving from ctypes "Structure". I have narrowed this to down to the simplest

[issue35365] Use wchar_t* buffer instead of Unicode object in code page decoder

New submission from Serhiy Storchaka : Currently the code page decoder uses the legacy Unicode C API for creating an output buffer as a Unicode object with PyUnicode_WCHAR_KIND. Proposed PR makes it using a raw wchar_t* buffer. This is necessary for deprecating and removing the legacy

[issue35364] Datetime “fromtimestamp()” ignores inheritance if timezone is not None

Adrien added the comment: Actually, this also occurs while using "astimezone()" on a custom child class (I suppose this method is used by "fromtimestamp()"). -- ___ Python tracker

[issue35352] test_asyncio fails on RHEL8

Change by STINNER Victor : -- pull_requests: +10073 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35352] test_asyncio fails on RHEL8

STINNER Victor added the comment: New changeset 7212148c95947b0fdfcb0c8e37d4357287bdb4bd by Victor Stinner in branch 'master': bpo-35352: Cleanup test_asyncio/utils.py (GH-10831) https://github.com/python/cpython/commit/7212148c95947b0fdfcb0c8e37d4357287bdb4bd --

[issue35352] test_asyncio fails on RHEL8

STINNER Victor added the comment: > IIRC two copies exist from very early development times when asyncio was not > a part of Python stdlib. Yeah, that was my guess as well. Maybe data_file() could be simplified or replaced by support.findfile(), but I chose the easy solution (minimize

[issue35352] test_asyncio fails on RHEL8

Andrew Svetlov added the comment: IIRC two copies exist from very early development times when asyncio was not a part of Python stdlib. -- ___ Python tracker ___

[issue35352] test_asyncio fails on RHEL8

Change by STINNER Victor : -- pull_requests: +10072 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35364] Datetime “fromtimestamp()” ignores inheritance if timezone is not None

New submission from Adrien : Hello. I created a class inheriting from "datetime.datetime". While creating a new instance using the classmethod "fromtimestamp" it seems to work, except if I provide a timezone object. In such case, the returned object is of base type datetime. This looks like

[issue33015] Fix function cast warning in thread_pthread.h

STINNER Victor added the comment: New changeset bc9f53f69e8207027bf2b18e3d01b30401e76ace by Victor Stinner in branch '2.7': bpo-33015: Use malloc() in PyThread_start_new_thread() (GH-10829) https://github.com/python/cpython/commit/bc9f53f69e8207027bf2b18e3d01b30401e76ace --

[issue28608] Support creating hardlink using `pathlib`

Antoine Pitrou added the comment: Since Path already supports symlinking, it would be reasonable to add hardlinking (e.g. as `Path.link_to`). But as you said one may as well call `os.link(path1, path2)`. -- ___ Python tracker

[issue35352] test_asyncio fails on RHEL8

Change by STINNER Victor : -- pull_requests: +10071 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35352] test_asyncio fails on RHEL8

Change by miss-islington : -- pull_requests: +10070 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35352] test_asyncio fails on RHEL8

STINNER Victor added the comment: New changeset b062ba77b617b0f89b7ea25d14cc77c991462ad4 by Victor Stinner (stratakis) in branch 'master': bpo-35352: test_asyncio uses the certificate set from the test directory (GH-10826)

[issue33015] Fix function cast warning in thread_pthread.h

STINNER Victor added the comment: I wrote PR 10828 to make PyMem_Malloc() thread-safe in debug mode as well.. But I'm not sure that it's ok to push such change later in the 2.7 development cycle... So I wrote PR 10829 which only modified PyThread_start_new_thread(): use malloc/free instead

[issue33015] Fix function cast warning in thread_pthread.h

STINNER Victor added the comment: Oh... test_threaded_import started to crash on Python 2.7: $ ./python -m test -F -v test_threaded_import (...) 0:00:00 load avg: 1.06 [ 3] test_threaded_import Trying 20 threads ... OK. Trying 50 threads ... OK. Trying 20 threads ... OK. Segmentation fault

[issue33015] Fix function cast warning in thread_pthread.h

Change by STINNER Victor : -- pull_requests: +10069 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33015] Fix function cast warning in thread_pthread.h

Change by STINNER Victor : -- pull_requests: +10068 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue31046] ensurepip does not honour the value of $(prefix)

Matej Cepl added the comment: Per https://devguide.python.org/pullrequest/, can I ask you Xavier to prepare a proper pull request for this patch to the GitHub repo, please? -- nosy: +mcepl ___ Python tracker

[issue35352] test_asyncio fails on RHEL8

Charalampos Stratakis added the comment: Also on Fedora the same set of security policies can be set as RHEL8 by utilizing 'update-crypto-policies --set NEXT' -- ___ Python tracker

[issue35352] test_asyncio fails on RHEL8

STINNER Victor added the comment: > The strange thing is these tests are passed on our build bots. RHEL8 has a very strict security policy by default. I'm not sure if any OS run on buildbot has a security policy as strict as RHEL8? > Maybe bumping used protocol version will help to pass

[issue35352] test_asyncio fails on RHEL8

Change by Charalampos Stratakis : -- keywords: +patch pull_requests: +10067 stage: -> patch review ___ Python tracker ___ ___

[issue35338] set union/intersection/difference could accept zero arguments

Mark Dickinson added the comment: > set.union() without constructing the set you call union on only happens to > work for the set.union(a) case because `a` is already a set. Good point. I wasn't thinking clearly about the unbound-methodness of this. > I'm -1 on making any changes to

[issue35363] test_eintr: test_open() hangs randomly on x86-64 El Capitan 3.x buildbot

STINNER Victor added the comment: I stopped my manual test after 71 iterations. -- ___ Python tracker ___ ___ Python-bugs-list

[issue33015] Fix function cast warning in thread_pthread.h

STINNER Victor added the comment: Ok, the bug should now be fixed. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue33015] Fix function cast warning in thread_pthread.h

STINNER Victor added the comment: New changeset 03b1200dfd03061e9ad0bff8199967bd80b9b900 by Victor Stinner in branch '3.6': bpo-33015: Fix UB in pthread PyThread_start_new_thread (GH-6008) (GH-10822) https://github.com/python/cpython/commit/03b1200dfd03061e9ad0bff8199967bd80b9b900

[issue33015] Fix function cast warning in thread_pthread.h

STINNER Victor added the comment: New changeset 8f83c2fb19c45350c2161d9e75dab4cd2bcaee28 by Victor Stinner in branch '2.7': bpo-33015: Fix UB in pthread PyThread_start_new_thread (GH-6008) (GH-10823) https://github.com/python/cpython/commit/8f83c2fb19c45350c2161d9e75dab4cd2bcaee28

[issue35358] avoid '-' in importlib.import_module and builtins.__import__

Guido van Rossum added the comment: Do not change this. I'd rather see it documented that importlib can import any name as long as it doesn't contain a dot, slash or backslash. (Clearly the fact that Django loads it is an additional argument that this should be supported, not forbidden.)

[issue35363] test_eintr: test_open() hangs randomly on x86-64 El Capitan 3.x buildbot

Change by STINNER Victor : -- nosy: +pablogsal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35363] test_eintr: test_open() hangs randomly on x86-64 El Capitan 3.x buildbot

STINNER Victor added the comment: I'm unable to reproduce the bug on macOS 10.13.6 using: ./python.exe -m test -F test_eintr --timeout=60 I modified the test to display immediately result into stdout: diff --git a/Lib/test/test_eintr.py b/Lib/test/test_eintr.py index 25f86d3..47b89d3

[issue35363] test_eintr: test_open() hangs randomly on x86-64 El Capitan 3.x buildbot

New submission from STINNER Victor : test_open() of test_eintr hangs randomly on x86-64 El Capitan 3.x buildbot. test_eintr failed but then passed when run again. pythoninfo: platform.platform: Darwin-15.6.0-x86_64-i386-64bit # macOS 10.11 (El Capitan)

[issue35362] list inheritor with abstract content does not raise

Change by vassilis Lemonidis : -- title: list inheritor with abc method does not raise -> list inheritor with abstract content does not raise ___ Python tracker ___

[issue33015] Fix function cast warning in thread_pthread.h

miss-islington added the comment: New changeset b1355352d14a0a67107aba7ec6f26f17716a by Miss Islington (bot) in branch '3.7': bpo-33015: Fix UB in pthread PyThread_start_new_thread (GH-6008) https://github.com/python/cpython/commit/b1355352d14a0a67107aba7ec6f26f17716a --

[issue35362] list inheritor with abc method does not raise

Change by vassilis Lemonidis : -- type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35362] list inheritor with abc method does not raise

New submission from vassilis Lemonidis : The following does not raise: class Test(list, metaclass=ABCMeta): @abstractmethod def test(self): pass test = Test() There is not enough documentation to support this problem, so I believe this can be classified as a bug. Anyone

[issue33015] Fix function cast warning in thread_pthread.h

Change by STINNER Victor : -- pull_requests: +10066 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35338] set union/intersection/difference could accept zero arguments

Josh Rosenberg added the comment: set.union() without constructing the set you call union on only happens to work for the set.union(a) case because `a` is already a set. union takes arbitrary iterables, not just sets, and you're just cheating by explicitly passing `a` as the expected self

[issue33015] Fix function cast warning in thread_pthread.h

Change by STINNER Victor : -- pull_requests: +10065 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33015] Fix function cast warning in thread_pthread.h

Change by miss-islington : -- pull_requests: +10064 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33015] Fix function cast warning in thread_pthread.h

STINNER Victor added the comment: New changeset 9eea6eaf23067880f4af3a130e3f67c9812e2f30 by Victor Stinner (Siddhesh Poyarekar) in branch 'master': bpo-33015: Fix UB in pthread PyThread_start_new_thread (GH-6008)

[issue35352] test_asyncio fails on RHEL8

Charalampos Stratakis added the comment: I believe I figured out the issue, at least on the master branch. While checking the certificates used by asyncio tests within the test_asyncio folder I noticed they were quite outdated when compared to the more recent updated ones with the test/

[issue35358] avoid '-' in importlib.import_module and builtins.__import__

Eric V. Smith added the comment: I dynamically load a lot of modules whose names contain hyphens, or are otherwise non-identifiers (like 3rdparty.py). The suggested change would break a lot of working code. The only thing I can see being possible is to add a warning that no one would

[issue35352] test_asyncio fails on RHEL8

Andrew Svetlov added the comment: Maybe this is the reason. asycio test suite uses these ssl contexts: https://github.com/python/cpython/blob/master/Lib/test/test_asyncio/utils.py#L72-L92 Maybe bumping used protocol version will help to pass tests on your box. Would you try it? --

[issue35352] test_asyncio fails on RHEL8

Charalampos Stratakis added the comment: It seems I can reproduce it on Fedora as well by setting stronger crypto defaults through 'update-crypto-policies --set FUTURE'. Repo located here: https://gitlab.com/redhat-crypto/fedora-crypto-policies/tree/master The changes are many, but if I

[issue35350] importing "ctypes" immediately causes a segmentation fault

David added the comment: Another small update: After I recompiled Python with the commented out statement, I did a small test if loading a shared library works. I compiled the following test function to testib.so: #include void test_func(void); void test_func(void) {

[issue33930] Segfault with deep recursion into object().__dir__

INADA Naoki added the comment: $ ./python.patched -m perf timeit --compare-to ./python.master -s 'o="foo"' 'o.encode' --duplicate=1 python.master: . 23.1 ns +- 0.5 ns python.patched: . 24.6 ns +- 0.5 ns Mean +- std dev: [python.master] 23.1 ns +-

[issue35361] Update libffi dependency to 3.2.1?

New submission from STINNER Victor : Python 2.7 and 3.6 embed a copy of libffi 3.1, whereas libffi 3.2.1 was released on November 12, 2014. Should we update libffi? I'm talking about the directory Modules/_ctypes/libffi/. It seems like Fedora 29 still uses libffi 3.1: $ rpm -q libffi

[issue35360] [Windows] Update SQLite dependency

STINNER Victor added the comment: First the sqlite branch should be updated in: https://github.com/python/cpython-source-deps Then a new tag should be created in this repository. I tried to update cpython-source-deps, but "git push" never completed. I will retry next week ;-) --

[issue35347] test_socket: NonBlockingTCPTests.testRecv() uses a weak 100 ms sleep as synchronization

STINNER Victor added the comment: Ok, test_socket should depend a little bit less on time now ;-) -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue35347] test_socket: NonBlockingTCPTests.testRecv() uses a weak 100 ms sleep as synchronization

STINNER Victor added the comment: New changeset 304315d251dbb4e85dd86056ba1925f25e646ca1 by Victor Stinner in branch 'master': bpo-35347: Cleanup test_socket.NonBlockingTCPTests (GH-10818) https://github.com/python/cpython/commit/304315d251dbb4e85dd86056ba1925f25e646ca1 --

[issue33930] Segfault with deep recursion into object().__dir__

Serhiy Storchaka added the comment: Thank you Inada. There is a large overhead for iterating. Try to add --duplicate=1000. -- ___ Python tracker ___

[issue35360] [Windows] Update SQLite dependency

Change by STINNER Victor : -- components: +Windows nosy: +paul.moore, steve.dower, tim.golden, zach.ware ___ Python tracker ___ ___

[issue35360] [Windows] Update SQLite dependency

New submission from STINNER Victor : Windows and macOS installers require SQLite, but they require different versions! Windows uses 3.21 or 3.14, but macOS uses 3.22. I'm talking about the following line in PCbuild\get_externals.bat: set libraries=%libraries% sqlite-3.21.0.0 * 3.6, 3.7

[issue35347] test_socket: NonBlockingTCPTests.testRecv() uses a weak 100 ms sleep as synchronization

STINNER Victor added the comment: New changeset dab59fa56054d6c0f75ae7013337f7baaa248076 by Victor Stinner in branch '2.7': bpo-35347: Fix test_socket.NonBlockingTCPTests (GH-10791) (GH-10817) https://github.com/python/cpython/commit/dab59fa56054d6c0f75ae7013337f7baaa248076 --

[issue35359] [2.7][Windows] Define _CRT_SECURE_NO_WARNINGS to build Modules\zlib\

Change by STINNER Victor : -- keywords: +patch pull_requests: +10063 stage: -> patch review ___ Python tracker ___ ___

[issue35359] [2.7][Windows] Define _CRT_SECURE_NO_WARNINGS to build Modules\zlib\

New submission from STINNER Victor : The compilation of Modules\zlib\ on Python 2.7 emits a lot of warnings: see AppVeyor logs above. I propose to define _CRT_SECURE_NO_WARNINGS in the pythoncore project to make these warnings quiet, to spot more easily new warnings. Attached PR adds

[issue33930] Segfault with deep recursion into object().__dir__

INADA Naoki added the comment: microbench: $ ./python.patched -m perf timeit --compare-to ./python.master -s 'o="foo"' 'o.encode' python.master: . 29.3 ns +- 0.6 ns python.patched: . 30.9 ns +- 1.3 ns Mean +- std dev: [python.master] 29.3 ns +- 0.6

[issue35347] test_socket: NonBlockingTCPTests.testRecv() uses a weak 100 ms sleep as synchronization

miss-islington added the comment: New changeset af7e81f71858519de8d2bafcb38fce8cca86aa0a by Miss Islington (bot) in branch '3.6': bpo-35347: Fix test_socket.NonBlockingTCPTests (GH-10791) https://github.com/python/cpython/commit/af7e81f71858519de8d2bafcb38fce8cca86aa0a --

[issue35347] test_socket: NonBlockingTCPTests.testRecv() uses a weak 100 ms sleep as synchronization

Change by STINNER Victor : -- pull_requests: +10062 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35347] test_socket: NonBlockingTCPTests.testRecv() uses a weak 100 ms sleep as synchronization

miss-islington added the comment: New changeset 365f21c2d3756a6768c5b0d479aaf5c2a568b80b by Miss Islington (bot) in branch '3.7': bpo-35347: Fix test_socket.NonBlockingTCPTests (GH-10791) https://github.com/python/cpython/commit/365f21c2d3756a6768c5b0d479aaf5c2a568b80b -- nosy:

[issue35347] test_socket: NonBlockingTCPTests.testRecv() uses a weak 100 ms sleep as synchronization

Change by STINNER Victor : -- pull_requests: +10061 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue30167] site.main() does not work on Python 3.6 and superior if PYTHONSTARTUP is set

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

[issue35347] test_socket: NonBlockingTCPTests.testRecv() uses a weak 100 ms sleep as synchronization

Change by miss-islington : -- pull_requests: +10060 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35347] test_socket: NonBlockingTCPTests.testRecv() uses a weak 100 ms sleep as synchronization

STINNER Victor added the comment: New changeset ebd5d6d6e6e4e751ba9c7534004aadfc27ba9265 by Victor Stinner in branch 'master': bpo-35347: Fix test_socket.NonBlockingTCPTests (GH-10791) https://github.com/python/cpython/commit/ebd5d6d6e6e4e751ba9c7534004aadfc27ba9265 --

[issue35347] test_socket: NonBlockingTCPTests.testRecv() uses a weak 100 ms sleep as synchronization

Change by miss-islington : -- pull_requests: +10059 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35336] Bug in C locale coercion with PYTHONCOERCECLOCALE=1

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

[issue35336] Bug in C locale coercion with PYTHONCOERCECLOCALE=1

STINNER Victor added the comment: New changeset df738d56fe798b3586ed71775df25bf127789cf6 by Victor Stinner in branch '3.7': bpo-35336: Fix PYTHONCOERCECLOCALE=1 (GH-10806) (GH-10813) https://github.com/python/cpython/commit/df738d56fe798b3586ed71775df25bf127789cf6 --

[issue35336] Bug in C locale coercion with PYTHONCOERCECLOCALE=1

STINNER Victor added the comment: > PYTHONCOERCECLOCALE=1 should not force C locale coercion, Python should still > check if the LC_CTYPE locale is "C". Reference: https://docs.python.org/dev/using/cmdline.html#envvar-PYTHONCOERCECLOCALE "If (...) the current locale reported for the

  1   2   >