[issue28876] bool of large range raises OverflowError

Akira Li added the comment: I've removed the documentation changes from the patch. -- Added file: http://bugs.python.org/file45773/range_bool-no_docs.patch ___ Python tracker ___

[issue28596] on Android _bootlocale on startup relies on too many library modules

Xavier de Gaye added the comment: This is a performance issue. I will look at it shortly. -- ___ Python tracker ___ ___ Python-bugs-li

[issue10496] Python startup should not require passwd entry

Suraj Deshmukh added the comment: @grahamd thanks this helps. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue10496] Python startup should not require passwd entry

Graham Dumpleton added the comment: @surajd Why aren't you using the Python S2I builders for OpenShift? When you run anything under OpenShift, it will assign your project a UID which any containers are forced to run under. The OpenShift containers include a mechanism using a package call nss_w

[issue10496] Python startup should not require passwd entry

Suraj Deshmukh added the comment: I did not encounter this issue in fedora24 based container on docker but when I run it in openshift I see errors as: That container has `Python 2.7.12` installed. While `flask` and `redis` python libs are installed via pip. ``` bash: /usr/local/bin/wait-for-i

[issue28882] RFC: Slice confusing with negative strides and the 0th element.

steven Michalske added the comment: Argh, I swear I proofread this... print([a[x] for x in [slice(y+3, y-1, -1) for y in range(0, len(a), 4)]]) [[], [7, 7, 6, 5]] Catching my explicit case, I changed my code to: print([a[x] for x in [slice(y+3, y-1 if y > 1 else None, -1) for y in range(0, len

[issue28882] RFC: Slice confusing with negative strides and the 0th element.

New submission from steven Michalske: The slicing and using inputed math is is necessary to provide a special case to make the code behave as expected. Unless I'm missing something. Like we can't do this, as we loose negative indexing from the end of the file? Let's take the following exampl

[issue28091] Document PEP 525

Yury Selivanov added the comment: Hi Eric, please feel free to go ahead and submit a patch, I'll review it! -- ___ Python tracker ___

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

Mariatta Wijaya added the comment: Thanks, Berker :) Updated. -- Added file: http://bugs.python.org/file45772/issue28089v2.patch ___ Python tracker ___ __

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

Berker Peksag added the comment: +.. versionchanged:: 3.6.0 3.6.0 -> 3.6 + The socket option TCP_NODELAY is now set by default. TCP_NODELAY -> ``TCP_NODELAY`` -- nosy: +berker.peksag stage: needs patch -> patch review ___ Python tracker

[issue13886] readline-related test_builtin failure

Martin Panter added the comment: input-readline.v2.patch sets stderr=DEVNULL so that the prompt does not come out in the test log. A disadvantage of this is that if there is a failure, any error messages, stack trace, etc is also lost. To fix this properly, we would probably have to capture s

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

Mariatta Wijaya added the comment: I added the following to Doc/library/asyncio-protocol.rst .. versionchanged:: 3.6.0 The socket option TCP_NODELAY is now set by default. Let me know if this patch works. -- keywords: +patch Added file: http://bugs.python.org/file45770/issue28089.pa

[issue28091] Document PEP 525

Eric Appelt added the comment: Hi, I'm a new contributor trying to get started with documentation and testing. I have been following and testing PEP525 and PEP530 and feel familiar enough to try to work on adding this to the Python Language Reference if it would not be redundant with work alre

[issue28878] datetime should not be a subclass of date

Changes by Berker Peksag : -- resolution: -> not a bug ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

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

Martin Panter added the comment: Actually, I found a regression. Looks like you also need to cancel any showwarning() function set by the user: >>> import warnings >>> warnings.showwarning = print >>> with warnings.catch_warnings(record=True) as recording: ... warnings.warn("hi") # Unpatch

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

Martin Panter added the comment: The patch looks sensible to me. The fix is basically an extension to the first fixup (9c92352324e8), where Victor split _showwarnmsg_impl() out of _showwarnmsg(). Now, _showwarnmsg() is a helper for the C module to choose between the backwards-compatible showwa

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

Nick Coghlan added the comment: +1 from me as well -- assignee: -> haypo nosy: +ncoghlan stage: -> commit review type: -> behavior ___ Python tracker ___ _

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

Nick Coghlan added the comment: As long as the C API docs also get updated, +1 for: * 'o' -> 'obj' * 'callable_object' -> 'callable' * 'func' -> 'callable' (when the function actually accepts an arbitrary callable) * 'method' -> 'name' (assuming 'Method' appears in the function name) Documenti

[issue3687] Popen() object stdout attribute reassignment behaviour

Changes by Martin Panter : -- stage: -> needs patch versions: +Python 3.5, Python 3.6, Python 3.7 -Python 2.6, Python 3.1, Python 3.2 ___ Python tracker ___

[issue27847] os.set_inheritable() looks to be broken on OpenIndiana, regression of Python 3.6

Changes by Ned Deily : -- nosy: +jcea ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/m

[issue27847] os.set_inheritable() looks to be broken on OpenIndiana, regression of Python 3.6

Ned Deily added the comment: Although Victor initiated some discussions on python-dev about support for OpenIndiana and other Solaris-related derivatives, I don't we ever reached a consensus, no one has proposed a solution, and currently the OpenIndiana 3.6 buildbot is not functioning well (I'

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

Shinya Okano added the comment: Thanks for reviews and comments. I will work on the weekend. -- ___ Python tracker ___ ___ Python-bugs

[issue26223] decimal.to_eng_string() does not implement engineering notation in all cases.

Serge Stroobandt added the comment: Dear Keith, that is exactly how it should be! (I cross-checked with a HP calculator to make sure.) -- ___ Python tracker ___

[issue28866] Type cache is not correctly invalidated on a class defining mro()

STINNER Victor added the comment: > * Somehow, notify Foo that Meta has a reference to its cache, so Foo is able > to invalidate Meta cache This was implemented when the type cache was implemented in Python 2.6, but only for explicit subclasses. PyType_Modified() iterates on tp_subclasses. Py

[issue28866] Type cache is not correctly invalidated on a class defining mro()

STINNER Victor added the comment: The issue is that the Meta class has a reference to the class Foo in its mro() method, but Foo is not aware of Meta. So when Foo is modified, the Foo cache is invalidated, but not Meta cache. issue28866.diff always invalidates the cache, so it works. But it is

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

STINNER Victor added the comment: Patch version 3: fix test_warnings when running the test with python3 -Werror. Reset filters in the new unit test. -- Added file: http://bugs.python.org/file45769/warnings_fix-3.patch ___ Python tracker

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

Julien Palard added the comment: Carefully reviewed, and tests are passing, issue is fixed: LGTM. -- nosy: +mdk ___ Python tracker ___ ___

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

Eric V. Smith added the comment: I withdraw my concern. I was thinking it would affect the caller, but of course it won't. Apologies. -- ___ Python tracker ___ _

[issue28596] on Android _bootlocale on startup relies on too many library modules

STINNER Victor added the comment: android-locale-utf8.patch LGTM, but I added minor comments on the review. I would prefer to let Xavier merges this one, since he can test it. -- ___ Python tracker ___

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

STINNER Victor added the comment: Serhiy: Would you mind to review warnings_fix-2.patch? I tagged this bug as a release blocker, since it's a regression introduced in 3.6. -- nosy: +serhiy.storchaka ___ Python tracker

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

R. David Murray added the comment: I had no memory that __iter__ wasn't implemented in python2, thanks Martin. So, this isn't really a bug, though one could argue it should be mentioned explicitly in the 2.7 docs, since it is definitely counter-intuitive to a python programmer. -- _

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

R. David Murray added the comment: In case anyone else wonders, the tutorial does cover this, although its example uses ">>> print(range(10))" instead of just ">>> range(10)". -- ___ Python tracker ___

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

STINNER Victor added the comment: Oops, I made a mistake just before producing the patch: here is the right patch, test_warnings pass. -- Added file: http://bugs.python.org/file45768/warnings_fix-2.patch ___ 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 ___ __

[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

[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

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

[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 ___ _

[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

[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] 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 ___

[issue28808] Make PyUnicode_CompareWithASCIIString() never failing

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

[issue28808] Make PyUnicode_CompareWithASCIIString() never failing

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

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

[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

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

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

[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

[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

[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

[issue28091] Document PEP 525

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

[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 : -- Removed message: http://bugs.python.org/msg282460 ___ Python tracker ___ ___ Python-bugs-list mailing list U

[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

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

[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

[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 ___ _

[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

[issue28797] Modifying class __dict__ inside __set_name__

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

[issue28872] test_builtin failures when refleak hunting

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

[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

[issue28873] test_unittest failures when refleak hunting

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

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

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

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

[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

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

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

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

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

[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

[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

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

[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

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

[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

[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

[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

[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

[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

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

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

[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

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

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

[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

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)

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

[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

[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

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

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

[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

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

[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

[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

[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

[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

  1   2   >