[issue28865] [MinGW32-x64]-PyList_Check PyDict_Check does not work

Mikhail added the comment: SOLVED: I found a solution. It turned out that on the Windows x64 need to use '-DMS_WIN64' compiler option. Three days wasted. And although no one helped me, I felt that mentally you were with me, guys. Thank you! ;) -- resolution: -> not a bug status: op

[issue13886] readline-related test_builtin failure

Martin Panter added the comment: Since people keep coming upon this bug, perhaps we should inhibit push my fix without fixing that other prompt bug (now a feature change I think). Probably have to capture stderr to avoid it coming out in the test output. -- versions: +Python 3.7 _

[issue28875] test fails and freezes

Changes by Whitequill Riclo : -- hgrepos: -365 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue28875] test fails and freezes

Changes by Whitequill Riclo : -- status: closed -> open ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue28875] test fails and freezes

Changes by Whitequill Riclo : -- hgrepos: +366 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyt

[issue27870] Left shift of zero allocates memory

Mark Dickinson added the comment: Gah. Sorry about that. Thanks for the refleak fix, Benjamin. -- ___ Python tracker ___ ___ Python-bu

[issue24329] __qualname__ and __slots__

Xiang Zhang added the comment: > However, consistency is a good thing, so allowing it seems reasonable. The inconsistency also appears when "__classcell__" in slots with or without super(). v4 catches up with HEAD. -- Added file: http://bugs.python.org/file45762/slots_special-v4.patch

[issue28876] bool of large range raises OverflowError

New submission from Mark Dickinson: The bool of a large range raises OverflowError: >>> bool(range(2**63)) Traceback (most recent call last): File "", line 1, in OverflowError: Python int too large to convert to C ssize_t This is a side-effect of len raising OverflowError, wh

[issue22107] tempfile module misinterprets access denied error on Windows

Paul Doom added the comment: Can the _mkstemp_inner portion of Billy McCulloch's patch be applied? Due to a large default os.TMP_MAX value (2147483647 - seems to be the current value on Win 7/8.1/10 I have access to), the following will push the CPU to 100% for a very long time when run under

[issue25658] PyThread assumes pthread_key_t is an integer, which is against POSIX

Masayuki Yamamoto added the comment: I wrote a patch based on msg281227's idea. I confirmed to pass related tests (test_capi, test_threading and test_tracemalloc) on Cygwin x86 and Ubuntu 16.04 x86. This patch adds to change CPython about: 1. Avoid compile error on Currently TLS API. With

[issue28876] bool of large range raises OverflowError

Raymond Hettinger added the comment: +1 for implementing nb_bool for range objects. -- nosy: +rhettinger ___ Python tracker ___ ___ Py

[issue28427] WeakValueDictionary next bug (with multithreading)

Armin Rigo added the comment: issue28427-atomic.patch: is it still necessary to modify weakref.py so much, then? What I had in mind was a C function with Python signature "del_if_equal(dict, key, value)"; the C function doesn't need to know about weakrefs and checking if they are dead. The C

[issue28864] Add devnull file-like object

Raymond Hettinger added the comment: I had in mind a pre-opened file like sys.stderr or sys.stdout. -- ___ Python tracker ___ ___ Pyth

[issue28877] Cannot compile _ssl.o on HP-UX

New submission from James Matthews: Cannot build Python 2.7.12 on HP-UX due to the following error: /opt/hp-gcc64-4.7.1/bin/gcc -pthread -shared build/temp.hp-ux-B.11.31-9000-800-2.7/root/build/Python-2.7.12/Modules/_ssl.o -L/usr/local/lib -lssl -lcrypto -o build/lib.hp-ux-B.11.31-9000-800-2.7

[issue28427] WeakValueDictionary next bug (with multithreading)

Antoine Pitrou added the comment: Hi Armin, > is it still necessary to modify weakref.py so much, then? Not sure. I'll take a look again. Modifying __len__() at least is necessary, as the previous version took into account the length of _pending_removals (and could therefore return wrong resu

[issue25658] PyThread assumes pthread_key_t is an integer, which is against POSIX

Erik Bray added the comment: I'm still pretty happy with the previous patch, personally, since I don't need the tracemalloc module. But it seems like that should be fixed (or if nothing else that code in _tracemalloc.c should check Py_HAVE_NATIVE_TLS too). I like the idea of the new PyThread_

[issue25591] refactor imaplib tests

Maciej Szulik added the comment: Thank you David, of course I'll remind you :) -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue28876] bool of large range raises OverflowError

Changes by Serhiy Storchaka : -- nosy: +serhiy.storchaka stage: -> needs patch ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue28638] Creating namedtuple is too slow to be used in common stdlib (e.g. functools)

INADA Naoki added the comment: I think external cache system introduces more complexity and startup overhead than AC. I think functools is the only "very common" module using namedtuple, because `functools.wraps()` is used to create decorator functions. But if general solution for all namedtup

[issue28707] add 'directory' option to the http.server module

Changes by Julien Palard : Added file: http://bugs.python.org/file45764/issue28707.diff ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue28873] test_unittest failures when refleak hunting

Changes by Berker Peksag : -- stage: needs patch -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailin

[issue28875] test fails and freezes

Berker Peksag added the comment: Please do not reopen this one. You already opened issue 28874. -- nosy: +berker.peksag stage: -> resolved status: open -> closed ___ Python tracker

[issue28876] bool of large range raises OverflowError

Akira Li added the comment: Here's a patch with range_bool() implementation, tests and the docs update. I'm not sure how it should be documented. I've specified it as versionchanged:: 3.6 -- keywords: +patch nosy: +akira Added file: http://bugs.python.org/file45765/range_bool.patch __

[issue28724] Add method send_io, recv_io to the socket module.

Christian Heimes added the comment: Good idea! Initially I planned to add the functions and some other helpers around AF_UNIX to Python 3.6. You can directly copy the example functions from the documentation. https://docs.python.org/3/library/socket.html#socket.socket.sendmsg https://docs.pyth

[issue28878] datetime should not be a subclass of date

New submission from sergem: I have Python 3.5.2. datetime is implemented as a subclass of date (isinstance(datetime.datetime(2015,1,1), datetime.date) == True) I suppose that violates Liskov substitution principle: 1. datetime and date cannot be compared via "<". 2. both of these classes have

[issue28878] datetime should not be a subclass of date

R. David Murray added the comment: Right or wrong, this was a concious design choice. If you wish to argue that it should be changed, you need to address it on the python-ideas mailing list (but look for previous threads about it there and on python-dev first). -- nosy: +r.david.murra

[issue28876] bool of large range raises OverflowError

Mark Dickinson added the comment: > I'm not sure how it should be documented. I think a change at this level probably isn't worth documenting in the official docs; it's enough that there's a Misc/NEWS entry for it. -- ___ Python tracker

[issue28878] datetime should not be a subclass of date

sergem added the comment: Would you be so kind to point to me to the discussion/arguments for that choice? Also http://www.gossamer-threads.com/lists/python/python/1114426 -- resolution: not a bug -> ___ Python tracker

[issue28866] Unexpected behavior resulting from mro() and __setattr__ in interactive mode

Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue28845] Clean up known issues for AIX

Eric N. Vander Weele added the comment: I have been able to test the example without a segmentation fault. $ python3.5 Python 3.5.2 (default, Nov 17 2016, 10:45:58) [C] on aix7 Type "help", "copyright", "credits" or "license" for more information. >>> import curses >>> from curses import panel >

[issue28878] datetime should not be a subclass of date

R. David Murray added the comment: Hmm. I thought there was a PEP, but maybe datetime was from before PEPs because I did find a PEP when I searched. I don't have specific pointers to discussion, that's why I suggested you search first. I'm pretty sure I remember a discussion of this some ti

[issue28864] Add devnull file-like object

Josh Rosenberg added the comment: Didn't pre-opened (or lazily opened) file descriptors cause headaches with os.urandom? I'm not sure I'd want my programming environment eating file descriptors "just in case", even if it might make certain tasks trivially faster after startup. -- nosy

[issue28864] Add devnull file-like object

Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue28864] Add devnull file-like object

Christian Heimes added the comment: It can be done with some extra effort. We have to get the st_dev and st_inode from os.fstat(fd), cache them together with the fd, and verify them every time we create a new DevNull object. That way we catch both closed fd and modified fd. We might have to ad

[issue28864] Add devnull file-like object

Antoine Pitrou added the comment: Which begs the question: what's the point? As David said, `open(os.devnull)` is a reasonably obvious way to do it. Is there a use case that it doesn't satisfy? -- ___ Python tracker

[issue28879] smtplib RFC 5322 date header missing

New submission from Henning von Bargen: I'm using CPython 2.7 with the smtplib and email modules to send emails with SMTP. Today, one of our clients complained that the email sent is not RFC 5322 compliant because the required Date header is missing. The RFC states in section 3.6.: "The only

[issue28858] Fastcall uses more C stack

Roundup Robot added the comment: New changeset 4171cc26272c by Victor Stinner in branch 'default': Issue #28858: Remove _PyObject_CallArg1() macro https://hg.python.org/cpython/rev/4171cc26272c -- ___ Python tracker

[issue15812] inspect.getframeinfo() cannot show first line

Peter Waller added the comment: I have just hit this bug and independently invented the exact fix of changing the zero for a one. Any chance of getting this merged? -- nosy: +Peter.Waller ___ Python tracker __

[issue28427] WeakValueDictionary next bug (with multithreading)

Armin Rigo added the comment: I think the issue of __len__() is a different matter. More below. >> The C function would simply call PyObject_GetItem() and >> PyObject_DelItem()---without releasing the GIL in the middle. > > If you implement it like that, and the dictionary has non-trivial > key

[issue28879] smtplib RFC 5322 date header missing

R. David Murray added the comment: That is correct. Most SMTP gateways add the header on submission if it is missing. At least a few other MUA programs do not automatically add the Date header, they let the SMTP server do it. I have one person who sends me email that saw this same problem (

[issue28866] Unexpected behavior resulting from mro() and __setattr__ in interactive mode

STINNER Victor added the comment: If you call sys._clear_type_cache() after the setattr(), weird_without_interactive.py doesn't crash anymore. -- ___ Python tracker ___

[issue28852] sorted(range(1000)) is slower in Python 3.7 than in 3.5

Changes by STINNER Victor : -- resolution: -> not a bug status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue28838] Uniformize argument names of "call" functions (C API)

STINNER Victor added the comment: So, what do you think of renaming argument like: * Replace "callable_object" and "func" with "callable" * Replace "method" with "name" * Rename "o" to "obj" (ex: in "PyCallable_Check(PyObject *o)") I prefer "callable_object" over "callable" because it's shorter

[issue28427] WeakValueDictionary next bug (with multithreading)

Antoine Pitrou added the comment: > Now about __len__() returning a wrong result: it is a more complicated issue, > I fear. I already patched weakref.py inside PyPy in order to pass a unit > test inside CPython's test suite. This patch is to change __len__ to look > like this: [...] Thanks

[issue28765] _sre.compile(): be more strict on types of indexgroup and groupindex

STINNER Victor added the comment: sre-concrete-2.patch LGTM, so do you want to push it Serhiy? -- ___ Python tracker ___ ___ Python-bu

[issue28427] WeakValueDictionary next bug (with multithreading)

Armin Rigo added the comment: Agreed about fixing the other issues. I'm still unclear that we need anything more than just the _remove_dead_weakref function to do that, but also, I don't see a particular problem with adding self._commit_removals() a bit everywhere. About the O(1) expectation

[issue28765] _sre.compile(): be more strict on types of indexgroup and groupindex

Changes by Serhiy Storchaka : -- superseder: -> _sre.compile(): be more strict on types of indexgroup and groupindex ___ Python tracker ___

[issue28765] _sre.compile(): be more strict on types of indexgroup and groupindex

Changes by Serhiy Storchaka : -- superseder: _sre.compile(): be more strict on types of indexgroup and groupindex -> ___ Python tracker ___

[issue28152] Clang warnings: code will never be executed

Roundup Robot added the comment: New changeset b3f1210d098d by Victor Stinner in branch 'default': Issue #28152: Fix -Wunreachable-code warnings on Clang https://hg.python.org/cpython/rev/b3f1210d098d New changeset 390fbb9c5e59 by Victor Stinner in branch 'default': Issue #28152: Fix -Wunreachab

[issue28152] Clang warnings: code will never be executed

Roundup Robot added the comment: New changeset 7c7055305f69 by Victor Stinner in branch 'default': Issue #28152: Fix -Wunreachable-code warning on clang https://hg.python.org/cpython/rev/7c7055305f69 -- ___ Python tracker

[issue28152] Clang warnings: code will never be executed

STINNER Victor added the comment: My commits fixed all warnings using clang 3.8.0 on Fedora 25. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___

[issue28050] test_traceback is broken by new CALL_FUNCTION* opcodes

STINNER Victor added the comment: Oh, this issue was already fixed, thanks Serhiy :-) changeset: 103659:51b635e81958 user:Serhiy Storchaka date:Mon Sep 12 00:52:40 2016 +0300 files: Include/abstract.h Lib/dis.py Lib/test/test_extcall.py Lib/test/test_traceback.py Object

[issue28152] Clang warnings: code will never be executed

Serhiy Storchaka added the comment: Thanks Victor. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

[issue28050] test_traceback is broken by new CALL_FUNCTION* opcodes

Serhiy Storchaka added the comment: It is rather worked around. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue28050] test_traceback is broken by new CALL_FUNCTION* opcodes

STINNER Victor added the comment: Serhiy Storchaka added the comment: > It is rather worked around. The test pass, the change looks good to me. I don't think that it's still worth it to keep the issue open ;-) -- ___ Python tracker

[issue27829] test.regrtest: changed environment variables are not logged

Changes by STINNER Victor : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue27864] test_socket: unknown thread blocks forever on "AMD64 FreeBSD 9.x 3.x"

STINNER Victor added the comment: Sadly, such bug is hard to reproduce. I didn't look at buildbots recently, and I don't have access to FreeBSD 9, so I just close the issue :-/ -- resolution: -> out of date status: open -> closed ___ Python tracker

[issue27791] test_threading: test_threads_join_2() failed with "Fatal Python error: Py_EndInterpreter: not the last thread"

STINNER Victor added the comment: Sadly, such bug is hard to reproduce. I didn't look at buildbots recently, and I don't have access to FreeBSD, so I just close the issue :-/ -- resolution: -> out of date status: open -> closed ___ Python tracker <

[issue27367] Windows buildbot: random timeout failure on test_threading

STINNER Victor added the comment: Such bug is random. It's hard to reproduce. I don't have access to Windows right now, so I just close the issue. -- resolution: -> out of date status: open -> closed ___ Python tracker

[issue27784] Random failure of test_TCPServer() of test.test_socketserver.SocketServerTest and test_handle_accept() of test.test_asyncore.TestAPI_UseIPv6Select on FreeBSD buildbots

STINNER Victor added the comment: I didn't look at buildbots recently, and I don't have access to FreeBSD, so I just close the issue :-/ -- resolution: -> out of date status: open -> closed ___ Python tracker ___

[issue26769] Python 2.7: make private file descriptors non inheritable

STINNER Victor added the comment: Sorry, I loose interest on this backport. The patch is large, the risk of regression is high, the goal is non-obvious. I'm not sure that such bugfix is still useful since Python 2.7 is old and developers know how to workaround Python 2.7 limitations. The prob

[issue28858] Fastcall uses more C stack

STINNER Victor added the comment: The changeset 4171cc26272c "Remove _PyObject_CallArg1() macro" fixed the initial bug report, so I now close the issue. Serhiy: If you see further enhancements, please open a new issue. Your second stack_overflow.py script is interesting, but I don't see any ob

[issue26566] Failures on FreeBSD CURRENT buildbot

STINNER Victor added the comment: This random failure is just too old, I close the issue. -- resolution: -> out of date status: open -> closed ___ Python tracker ___ ___

[issue28880] range(i, j) doesn't work

New submission from John Henning: When attempting to use range(I, j) command in Windows 10 command prompt, the latest version of Python would simply echo what was typed. See below: >>> range(7) range(0, 7) >>> range(0, 9) range(0, 9) >>> range(1, 10, 3) range(1, 10, 3) >>> -- componen

[issue28880] range(i, j) doesn't work

Matthew Barnett added the comment: Not a bug. Python 2 had 'range', which returned a list, and 'xrange', which returned an xrange object which was iterable: >>> range(7) [0, 1, 2, 3, 4, 5, 6] >>> xrange(7) xrange(7) >>> list(xrange(7)) [0, 1, 2, 3, 4, 5, 6] In Python 3, 'range' was dropped an

[issue28880] range(i, j) doesn't work

John Henning added the comment: Right about the command prompt! My bad. However, the new language you provided gives me the following: >>> list(range(9)) Traceback (most recent call last): File "", line 1, in TypeError: 'list' object is not callable >>> list(range(0, 10)) Traceback (most r

[issue28880] range(i, j) doesn't work

R. David Murray added the comment: Presumably you use 'list' as a variable name earlier in your interactive session. Try restarting your python shell. -- nosy: +r.david.murray resolution: -> not a bug stage: -> resolved status: open -> closed ___

[issue28880] range(i, j) doesn't work

John Henning added the comment: Ha! Thanks! Restarted python and now that works. Sorry for the trouble! Trying to teach myself python working through the python tutorial and hit this problem. -- ___ Python tracker

[issue28881] int no attribute 'lower'

New submission from Vitold S: I have MIME message and parse content. Later I walk on message headers by call for and receive follow traceback: Traceback (most recent call last): ... for m in msg: (msg is email.message.Message instance) File "C:\Python27\lib\email\message.py", line 294, i

[issue28881] int no attribute 'lower'

R. David Murray added the comment: Oh, I think I misread your traceback. Can you provide the actual code you are running, please? And probably the message you are parsing, as well. -- ___ Python tracker

[issue28881] int no attribute 'lower'

R. David Murray added the comment: It looks like your 'name' variable holds an integer, not a string giving a header name. -- ___ Python tracker ___

[issue28873] test_unittest failures when refleak hunting

Changes by Ned Deily : -- assignee: ned.deily -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue23722] During metaclass.__init__, super() of the constructed class does not work

Changes by Ned Deily : -- assignee: ned.deily -> priority: release blocker -> ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue28872] test_builtin failures when refleak hunting

Changes by Ned Deily : -- assignee: ned.deily -> stage: needs patch -> resolved status: open -> closed ___ Python tracker ___ ___ Pyt

[issue28797] Modifying class __dict__ inside __set_name__

Changes by Ned Deily : -- priority: release blocker -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue28808] Make PyUnicode_CompareWithASCIIString() never failing

Ned Deily added the comment: This is currently blocking 360rc1. Victor, Serhiy, we either need to get this in now or wait until 3.6.1. I am leaning towards pushing the latest patch for 3.6 without having a decision about 3.5 yet. -- ___ Python tra

[issue28835] Change in behavior when overriding warnings.showwarning and with catch_warnings(record=True)

Ned Deily added the comment: What's the status of this issue? It's currently blocking 360rc1. We either need a resolution now or defer it to 3.6.1. -- ___ Python tracker ___ _

[issue28089] Document TCP_NODELAY by default

New submission from Ned Deily: This is marked as a release blocker but, since it's just a doc change, I'm not going to hold 3.6.0 for it. It would be nice to get it in, though. -- priority: release blocker -> deferred blocker ___ Python tracker

[issue28091] Document PEP 525

New submission from Ned Deily: Yuri, are you planning to do more for this for 3.6.0? This is marked as a release blocker but, since it's just a doc change, I'm not going to hold 3.6.0 for it. -- priority: release blocker -> deferred blocker ___ Pyt

[issue28091] Document PEP 525

Ned Deily added the comment: Yury, are you planning to do more for this for 3.6.0? This is marked as a release blocker but, since it's just a doc change, I'm not going to hold 3.6.0 for it. -- ___ Python tracker

[issue28091] Document PEP 525

Changes by Ned Deily : -- Removed message: http://bugs.python.org/msg282460 ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue28090] Document PEP 530

New submission from Ned Deily: Yury, are you planning to do more for this for 3.6.0? This is marked as a release blocker but, since it's just a doc change, I'm not going to hold 3.6.0 for it. -- priority: release blocker -> deferred blocker versions: +Python 3.7 _

[issue28091] Document PEP 525

Changes by Ned Deily : -- versions: +Python 3.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue28518] execute("begin immediate") throwing OperationalError

Ned Deily added the comment: Thanks everyone for investigating this, in particular Big Stone for the reference to the SQLite project and especially Richard Hipp for once again responding quickly to issues we've brought up. While it would be good to get this resolved soon one way or another (d

[issue28880] range(i, j) doesn't work

Steven D'Aprano added the comment: Hi John, and thanks for the bug report. If only they were all as easily resolved as this one :-) With respect, if you're just getting started with Python, you shouldn't get into the habit of hitting the bug tracker every time you find something that surprise

[issue28881] int no attribute 'lower' iterating email.Messasge

Martin Panter added the comment: You just need a messsage object with one or more header fields: >>> msg = message_from_string("Name: value\r\n\r\n") >>> for m in msg: ... pass ... AttributeError: 'int' object has no attribute 'lower' Python 2 does not implement __iter__(), so it is the de

[issue28881] int no attribute 'lower' iterating email.Message

Changes by Martin Panter : -- title: int no attribute 'lower' iterating email.Messasge -> int no attribute 'lower' iterating email.Message ___ Python tracker ___ ___

[issue28089] Document TCP_NODELAY by default

STINNER Victor added the comment: Yury: I don't understand your issue, can you please elaborate? Do you mean that the default value of the TCP_NODELAY changed in Python 3.6? Otherwise, why do you consider it as a release blocker? The Python 3.6 release must be blocked by a TCP flag? Really? -

[issue28866] Unexpected behavior resulting from mro() and __setattr__ in interactive mode

Julien Palard added the comment: I found a way to fix it, but as I'm just discovering cpython internals, I'm not sure it's the right way, review are very welcome. I fixed it this way because: The bytecode generated for "proxy.x = 0" (a STORE_ATTR) will call a PyObject_SetAttr with FooProxy whi

[issue28881] int no attribute 'lower' iterating email.Message

Martin Panter added the comment: The __iter__() method was added by Barry in : “Added an __iter__() to email.message.Message for iterating over the message’s headers.” On the other hand,

[issue28808] Make PyUnicode_CompareWithASCIIString() never failing

STINNER Victor added the comment: PyUnicode_CompareWithASCIIString-no-errors-2.patch LGTM. Go ahead Serhiy. -- ___ Python tracker ___

[issue28808] Make PyUnicode_CompareWithASCIIString() never failing

Changes by Serhiy Storchaka : -- assignee: -> serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue28089] Document TCP_NODELAY by default

Mariatta Wijaya added the comment: The change is that TCP_NODELAY option is set by default in 3.6. It was not the case in 3.5. -- ___ Python tracker ___

[issue28089] asyncio: Document that TCP_NODELAY is now used by default

Changes by STINNER Victor : -- title: Document TCP_NODELAY by default -> asyncio: Document that TCP_NODELAY is now used by default ___ Python tracker ___ ___

[issue28089] asyncio: Document that TCP_NODELAY is now used by default

STINNER Victor added the comment: > The change is that TCP_NODELAY option is set by default in 3.6. It was not > the case in 3.5. Ah, it's a change in _asyncio_, ok. I missed that from the issue title, so I changed the title. -- ___ Python tracker

[issue28617] Why isn't "in" called a comparison operation?

wim glenn added the comment: 1 month later.. is newpatch.diff OK to merge or any further improvements needed? thanks -- ___ Python tracker ___ _

[issue28808] Make PyUnicode_CompareWithASCIIString() never failing

Roundup Robot added the comment: New changeset b431d39da67f by Serhiy Storchaka in branch '3.5': Issue #28808: PyUnicode_CompareWithASCIIString() now never raises exceptions. https://hg.python.org/cpython/rev/b431d39da67f New changeset 5bdc8e1a50c8 by Serhiy Storchaka in branch '3.6': Issue #288

[issue23722] During metaclass.__init__, super() of the constructed class does not work

Roundup Robot added the comment: New changeset fa4d8276d0fb by Serhiy Storchaka in branch 'default': Fixed merge error in Misc/NEWS for issue #23722. https://hg.python.org/cpython/rev/fa4d8276d0fb -- ___ Python tracker

[issue28808] Make PyUnicode_CompareWithASCIIString() never failing

Serhiy Storchaka added the comment: Thanks Ned and Victor. -- priority: release blocker -> normal resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue28835] Change in behavior when overriding warnings.showwarning and with catch_warnings(record=True)

STINNER Victor added the comment: Ok, here is a fix. -- keywords: +patch Added file: http://bugs.python.org/file45767/warnings_fix.patch ___ Python tracker ___ __

  1   2   >