[issue24665] CJK support for textwrap

Changes by Serhiy Storchaka : -- dependencies: +Add functions to get the width in columns of a character, textwrap.wrap: add control for fonts with different character widths ___ Python tracker

[issue29564] ResourceWarning tracking is attaching incorrect file:position to unclosed socket

Martin Panter added the comment: Without more information about what the relevant code is and why you think the line number is wrong, my best guess is you may not realize how the ResourceWarning is emitted. It happens when the garbage collector runs and destroys the socket object, which

[issue29561] Interactive mode gives sys.ps2 not sys.ps1 after comment-only line

Eryk Sun added the comment: For the tokenizer, a blank line is "[a] logical line that contains only spaces, tabs, formfeeds and possibly a comment" [1]. A blank line is normally ignored, except in the REPL an entirely blank line (i.e. no whitespace or comment) is used to end a multi-line

[issue24665] CJK support for textwrap

INADA Naoki added the comment: FYI, I had implemented textwrap respects EAW in Bazaar project. See here. http://bazaar.launchpad.net/~bzr-pqm/bzr/bzr.dev/revision/5874 -- ___ Python tracker

[issue24665] CJK support for textwrap

Chi Hsuan Yen added the comment: Some CJK character are marked as "ambiguous width". Seems in this patch ambiguous characters are assumed as narrow. Maybe it's better to document it? -- nosy: +Chi Hsuan Yen ___ Python tracker

[issue24665] CJK support for textwrap

INADA Naoki added the comment: Sorry, I'm not unicode expert. Important usage of textwrap is printing in terminal. So I think we should learn from software relating terminal. tmux uses utf8proc. utf8proc calculates display width by script at here.

[issue29557] binhex documentation claims unknown bug

Changes by Serhiy Storchaka : -- components: +macOS nosy: +ned.deily, ronaldoussoren ___ Python tracker ___

[issue29557] binhex documentation claims unknown bug

Serhiy Storchaka added the comment: I think this should be read in the context of previous lines: If you code or decode textfiles on non-Macintosh platforms they will still use the old Macintosh newline convention (carriage-return as end of line). And may be related to the in-code

[issue29481] 3.6.0 doc describes 3.6.1 feature - typing.Deque

Mariatta Wijaya added the comment: Thanks, Thomas :) I'll let you close your own PR on GitHub. -- ___ Python tracker ___

[issue29481] 3.6.0 doc describes 3.6.1 feature - typing.Deque

Thomas Caswell added the comment: I am not optimistic about the speed at which my employer will get this sorted out. better to just fix it and drop my commit! On Tue, Feb 14, 2017, 23:43 Mariatta Wijaya wrote: Mariatta Wijaya added the comment: Thanks, Raymond :) I

[issue28929] Provide a link from documentation back to its source file

Changes by Mariatta Wijaya : -- pull_requests: +75 ___ Python tracker ___ ___

[issue29521] Minor warning messages when compiling documentation

Changes by Mariatta Wijaya : -- pull_requests: +73 ___ Python tracker ___ ___

[issue29521] Minor warning messages when compiling documentation

Changes by Mariatta Wijaya : -- pull_requests: +74 ___ Python tracker ___ ___

[issue29481] 3.6.0 doc describes 3.6.1 feature - typing.Deque

Mariatta Wijaya added the comment: Thanks, Raymond :) I prepared the pull requests for 3.5, 3.6, and master branches. Thomas, you mentioned about needing to go over CLA with your employer in your PR. Not sure if you have any update on that? If your CLA is approved, I can merge and

[issue29481] 3.6.0 doc describes 3.6.1 feature - typing.Deque

Changes by Mariatta Wijaya : -- pull_requests: +72 ___ Python tracker ___ ___

[issue29481] 3.6.0 doc describes 3.6.1 feature - typing.Deque

Changes by Mariatta Wijaya : -- pull_requests: +71 ___ Python tracker ___ ___

[issue29481] 3.6.0 doc describes 3.6.1 feature - typing.Deque

Changes by Mariatta Wijaya : -- pull_requests: +70 ___ Python tracker ___ ___

[issue29536] test_hashlib failure on Ubuntu 16.04

Xiang Zhang added the comment: I am using 16.10 but I can't reproduce the failures. Sachin can you reliably reproduce the failures? And one thing interesting is that all the failed test cases need the network source to be enabled but your command doesn't do that, it's better to use ./python

[issue29521] Minor warning messages when compiling documentation

Changes by Mariatta Wijaya : -- pull_requests: +69 ___ Python tracker ___ ___

[issue29563] Update Devguide about building documentation.

Zachary Ware added the comment: I'd suggest replacing as much as possible in the devguide with a link to Doc/README.rst (or Doc/README.txt, if that's what it still is). Other improvements should be made in the README. -- nosy: +zach.ware ___

[issue29470] [python] Error in `/usr/bin/python': free(): invalid size: 0x00007f628400d0e0

David Ford (FirefighterBlu3) added the comment: Arch Linux (updated ~weekly but not often rebooted) on a Digital Ocean droplet. Kernel 4.5.1-1-ARCH, x86_64, OpenSSL 1.0.2j, Python 3.6.0 -- ___ Python tracker

[issue29470] [python] Error in `/usr/bin/python': free(): invalid size: 0x00007f628400d0e0

David Ford (FirefighterBlu3) added the comment: my SNI callback is a function that chooses which SSL certificate to load and summarized is: 6 def sni_callback(sock, servername, context): [...] 44 # load a specific crt/key 45 store = crtstore[servername] 46 47

[issue29470] [python] Error in `/usr/bin/python': free(): invalid size: 0x00007f628400d0e0

David Ford (FirefighterBlu3) added the comment: in process of creating a non-stripped python install. the default Arch Linux PKGBUILD uses xvfb-run at the end of the build process which is crashing. -- ___ Python tracker

[issue29529] Backport Travis configuration

Changes by INADA Naoki : -- pull_requests: +68 ___ Python tracker ___ ___

[issue29564] ResourceWarning tracking is attaching incorrect file:position to unclosed socket

New submission from David Ford (FirefighterBlu3): the following warning is incorrectly reported as initiated at psycopg2/extras.py:314, it actually occurs inside the Twilio python module. /usr/lib/python3.6/site-packages/psycopg2/extras.py:314: ResourceWarning: unclosed ts =

[issue29563] Update Devguide about building documentation.

New submission from Jim DeLaHunt: The Devguide section 7.5.1 "Building the documentation" / "Using make / make.bat" is out of date. The document lists 10 documentation targets for `make`. The Doc/Makefile lists 17. One important omission is `make check`, which looks for errors in

[issue18779] Misleading documentations and comments in regular expression HOWTO

A.M. Kuchling added the comment: Unfortunately making the sentences pedantically correct also makes them ungainly, and I think people generally assume that underscores are treated as a letter. -- nosy: +akuchling resolution: -> wont fix stage: patch review -> resolved status: open ->

[issue29562] test_getgroups of test_posix fails (on OS X 10.10)

Jim DeLaHunt added the comment: I have pushed a branch for this issue to my cpython fork: https://github.com/JDLH/cpython/tree/bpo-29562_failing_test_getgroups_on_os_x It modifies test_getgroups in test_posix.py to give better diagnostics in the event of a test failure. It says specifically

[issue29562] test_getgroups of test_posix fails (on OS X 10.10)

New submission from Jim DeLaHunt: When I run test.test_posix.PosixTester.test_getgroups on my Mac OS X system, it fails: % ./python.exe -m unittest -v test.test_posix.PosixTester.test_getgroups test_getgroups (test.test_posix.PosixTester) ... FAIL

[issue29531] Update Doc/README.txt to README.rst

Changes by Roger Sachan : -- pull_requests: +67 ___ Python tracker ___ ___

[issue29531] Update Doc/README.txt to README.rst

Changes by Roger Sachan : -- pull_requests: -31 ___ Python tracker ___ ___

[issue29546] A more helpful ImportError message

Matthias Bussonnier added the comment: See https://github.com/python/cpython/pull/103 that implements Barry's proposed format. -- ___ Python tracker ___

[issue29546] A more helpful ImportError message

Changes by Matthias Bussonnier : -- pull_requests: +66 ___ Python tracker ___

[issue29546] A more helpful ImportError message

Matthias Bussonnier added the comment: I'm unsure I understand changing only the default __str__() method. You will anyway have to format the message differently depending on whether you raise from a from-import or a from-import-* or any other locations. AFAIU you "just" need the following

[issue29546] A more helpful ImportError message

Brett Cannon added the comment: Thanks to Matthias' PR the information is all there in the exception, but the message has not been changed. One idea for this -- depending on how much C code you want to write -- is to provide a default message for __str__() that changes depending on whether

[issue29546] A more helpful ImportError message

Brett Cannon added the comment: New changeset bc4bed440504597cac47d0a215ee094bfa99ba7e by Brett Cannon in branch 'master': bpo-29546: Set 'path' on ImportError for ``from ... import ...`` (GH-91) https://github.com/python/cpython/commit/bc4bed440504597cac47d0a215ee094bfa99ba7e --

[issue29557] binhex documentation claims unknown bug

Changes by Berker Peksag : -- stage: -> patch review type: -> behavior versions: +Python 3.5, Python 3.6 ___ Python tracker

[issue29557] binhex documentation claims unknown bug

Berker Peksag added the comment: New changeset 6de2b7817fa9403e81dc38f13f3690f0bbf3d064 by Berker Peksag in branch 'master': bpo-29557: Remove ambiguous line in binhex docs (#90) https://github.com/python/cpython/commit/6de2b7817fa9403e81dc38f13f3690f0bbf3d064 -- nosy: +berker.peksag

[issue29546] A more helpful ImportError message

Changes by Matthias Bussonnier : -- pull_requests: +62 ___ Python tracker ___

[issue29546] A more helpful ImportError message

Changes by Matthias Bussonnier : -- pull_requests: +62, 63, 64 ___ Python tracker ___

[issue29546] A more helpful ImportError message

Changes by Matthias Bussonnier : -- pull_requests: +62, 63 ___ Python tracker ___

[issue29558] Provide run_until_complete inside loop

Martin Panter added the comment: Sounds related to Issue 22239 -- nosy: +martin.panter ___ Python tracker ___

[issue29561] Interactive mode gives sys.ps2 not sys.ps1 after comment-only line

New submission from Jim DeLaHunt: When you run the Python interpreter in interactive mode, get a sys.ps1 prompt (`...`), and type a comment-only or white-space-only line, the interpreter responds with a sys.ps2 prompt (`...`), instead of a sys.ps1 prompt. This seems wrong. For example: %

[issue28695] Add SSL_CTX_set_client_cert_engine

Gennady Kovalev added the comment: Ok, thank you. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue28695] Add SSL_CTX_set_client_cert_engine

Christian Heimes added the comment: I haven't started to design the new feature yet. Since it is going to be a new feature and feature freeze of 3.7 is 2018-01-29, I'm going to start working on new stuff around in April or May for PyCon. -- ___

[issue10746] ctypes c_long & c_bool have incorrect PEP-3118 type codes

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___

[issue28695] Add SSL_CTX_set_client_cert_engine

Gennady Kovalev added the comment: Is there any news? -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue11165] Document PyEval_Call* functions

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___

[issue10746] ctypes c_long & c_bool have incorrect PEP-3118 type codes

Pauli Virtanen added the comment: Converted patch to Github PR + some cleanup. -- pull_requests: +61 ___ Python tracker ___

[issue29560] Turtle graphics fill behavior differs between versions

New submission from John Simmons: When I run the demo program on the library 24.1 documentation page to draw the star, it colors the entire star yellow, not just the parts that are show yellow on the page. This appears to be a behavior change. This is running on a Windows 7 or 10 machine

[issue29534] _decimal difference with _pydecimal

Mark Dickinson added the comment: All done. Closing. (In theory, as a bugfix, this could be backported to 3.5 and 3.6. In practice, I doubt it's worth the effort.) -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python

[issue29534] _decimal difference with _pydecimal

Mark Dickinson added the comment: New changeset 996c3874fdbc91d29f0a06b37043f62cf4ead6cb by GitHub in branch 'master': Issue #29534: move Misc/NEWS entry to correct section; add Misc/ACS entry for Andrew Nester. (#99)

[issue6143] IDLE - an extension to clear the shell window

Terry J. Reedy added the comment: Alwx, please do not change the headers. IDLE menu commands cannot be invoked from a program. -- type: resource usage -> behavior versions: +Python 3.6, Python 3.7 -Python 2.7 ___ Python tracker

[issue29534] _decimal difference with _pydecimal

Mark Dickinson added the comment: PR to fix the Misc/NEWS entry: https://github.com/python/cpython/pull/99 -- ___ Python tracker ___

[issue29559] Detect mouse over lines on canvas while mouse button is down

New submission from Ted Shaneyfelt: There way mouse captures are done, mouse-over events seem to be disabled while dragging. This makes it difficult to provides hints as feedback, and more complicated than it should be to detect when dropping over a particular line object. Tk may not

[issue29534] _decimal difference with _pydecimal

Mark Dickinson added the comment: PR merged; thank you! Unfortunately, just after I merged it I noticed that the Misc/NEWS entry was in the wrong section. I'll make a new PR to fix that, and close this issue once it's done. -- ___ Python tracker

[issue29534] _decimal difference with _pydecimal

Mark Dickinson added the comment: New changeset 6d1dece06d13a7d40637e07b2c79f34aab368766 by Mark Dickinson in branch 'master': Fixed #29534 - _decimal difference with _pydecimal (#65) https://github.com/python/cpython/commit/6d1dece06d13a7d40637e07b2c79f34aab368766 --

[issue29540] Add compact=True flag to json.dump/dumps

Brett Cannon added the comment: I'm a little confused as the PR proposes a COMPACT constant for the module but the issue proposes a new compact argument. Which are we actively considering? -- ___ Python tracker

[issue19675] Pool dies with excessive workers, but does not cleanup

Dustin Oprea added the comment: I don't think this can be tested. Throwing exceptions in the remote process causes exceptions that can't be caught in the same way (when the initializer fails the pool just attempts to recreate the process over and over) and I don't think it'd be acceptable to

[issue29558] Provide run_until_complete inside loop

New submission from Javier Domingo: The current architecture of asyncio makes it really hard to combine both async and sync code. When porting a Thread based application to asyncio, the first step is usually to start merging threads to the main loop, by using `run_coroutine_threadsafe`. This

[issue29556] Remove unused #include

Changes by Chi Hsuan Yen : -- title: Remove an unused #include from bltinmodule.c -> Remove unused #include ___ Python tracker ___

[issue29387] Tabs vs spaces FAQ out of date

Mariatta Wijaya added the comment: New changeset 38c8354f3204441f6c6bd22213b449d2d8954fcc by GitHub in branch '3.5': bpo-29521 Fix two minor documentation build warnings (#41) (#84) https://github.com/python/cpython/commit/38c8354f3204441f6c6bd22213b449d2d8954fcc -- nosy: +Mariatta

[issue29553] Argparser does not display closing parentheses in nested mutex groups

Changes by Christoph Stahl : -- type: -> behavior ___ Python tracker ___

[issue29556] Remove an unused #include from bltinmodule.c

Chi Hsuan Yen added the comment: Hmmm, seems there are more redundant #include ; let me check one by one -- ___ Python tracker ___

[issue29557] binhex documentation claims unknown bug

New submission from David Wilemski: The binhex documentation has a line in it that says "As of this writing, hexbin() appears to not work in all cases." This is a bit ambiguous and there is no context for what the bug may be. It appears this line is from the first commit to the hexbin

[issue29556] Remove an unused #include from bltinmodule.c

Changes by Chi Hsuan Yen : -- pull_requests: +58 ___ Python tracker ___ ___

[issue29556] Remove an unused #include from bltinmodule.c

New submission from Chi Hsuan Yen: This #include is added in b744ba1d14c5487576c95d0311e357b707600b47 (issue8610) and later the use of CODESET is removed in d64e8a75e5138d5e5970f0c70995ae5cc377c421 (issue9642). Found this in investigating issue29436 Add haypo as both commit is written by you

[issue29555] Update Python Software Foundation Copyright Year

Changes by Senthil Kumaran : -- nosy: +lemburg ___ Python tracker ___ ___

[issue29555] Update Python Software Foundation Copyright Year

New submission from Senthil Kumaran: In the attached patch, I updated the copyright year to 2017 at places it was mentioned until 2016. There was a suggestion that we remove the copyright line of Python Software Foundation from module headers since the code is already covered 1) by top level

[issue29554] profile/pstat doc clariification

New submission from Matthias Bussonnier: profile .rst say: > Each restriction is either an integer (to select a count of lines), or a > decimal fraction between 0.0 and 1.0 inclusive (to select a percentage of > lines), **or a regular expression** Actually it accept a string that will be

[issue29548] deprecate PyEval_Call*() functions.

INADA Naoki added the comment: I stopped deprecating PyEval_Call APIs, and removing it's usage in PR 75. Summary of current pull requests: PR 87 contains fix regression of PyEval_CallObjectWithKeywords for Python 3.6. PR 75 is for master branch. It contains fix same to PR 87. Additionally,

[issue29553] Argparser does not display closing parentheses in nested mutex groups

New submission from Christoph Stahl: When creating nested mutually exclusive groups, all closing brackets except one are omitted. Example: parser = ArgumentParser() group = parser.add_mutually_exclusive_group() group.add_argument('-a') group.add_argument('-b') group2 =

[issue29548] deprecate PyEval_Call*() functions.

STINNER Victor added the comment: > So they are part of stable ABI. We can't remove them until Python 4. Please just stop right now using "Python 4" as the starting point to break -again- the Python world. If you plan to remove the function, plan it right now with versions like "in 2 cycles".

[issue29540] Add compact=True flag to json.dump/dumps

STINNER Victor added the comment: "Add compact=True flag to json.dump/dumps" Oh, fun, I implemented exactly this option in my perf project. Extract: def dump(data, fp, compact): kw = {} if compact: kw['separators'] = (',', ':') else:

[issue29540] Add compact=True flag to json.dump/dumps

Berker Peksag added the comment: I'm +1 on the idea. Currently, a user needs to find this information in a wall of text: "To get the most compact JSON representation, you should specify (',', ':') to eliminate whitespace." It's easy to miss the lack of trailing space in (',', ':'). Perhaps

[issue29552] Issue in Dictionary fromkeys

Prudvi Mangadu added the comment: Thanks Martin , I will close it. -- stage: -> resolved status: open -> closed ___ Python tracker ___

[issue29552] Issue in Dictionary fromkeys

Martin Panter added the comment: I suggest to close this as not a bug. -- resolution: -> not a bug ___ Python tracker ___

[issue29552] Issue in Dictionary fromkeys

Martin Panter added the comment: This is similar to the problem of building a list by repeating one item: . With dict.fromkeys(), the resulting dictionary maps each specified key object to the one and

[issue29548] deprecate PyEval_Call*() functions.

INADA Naoki added the comment: > I would suggest to deprecate PyEval_Call*() functions first only in the > documentation. In 3.8 or 3.9 add the Py_DEPRECATED attribute. doesn't excluded by PEP 384. And these 3 functions and 1 macro is outside of "#ifndef Py_LIMITED_API" check. So they are

[issue29548] deprecate PyEval_Call*() functions.

Serhiy Storchaka added the comment: > Any idea of the popularity of the undocumented PyEval_xxx() functions? You can just search code at GitHub. I would suggest to deprecate PyEval_Call*() functions first only in the documentation. In 3.8 or 3.9 add the Py_DEPRECATED attribute. --

[issue29548] deprecate PyEval_Call*() functions.

Serhiy Storchaka added the comment: PyEval_CallObject() was added at Jan 12 1995 (05360cd616ae). PyObject_CallObject(), PyObject_CallFunction() and PyObject_CallMethod() were added with Include/abstract.h at Jul 18 1995 (d5398acafa2c) and implemented in terms of PyEval_CallObject().

[issue29548] deprecate PyEval_Call*() functions.

Marc-Andre Lemburg added the comment: On 14.02.2017 11:16, STINNER Victor wrote: > >> Please note that the two sets of APIs are not identical, e.g. you cannot >> simply replace PyEval_CallObject() with PyObject_Call(), since the former >> applies a few extra checks and defaults, which the

[issue29470] [python] Error in `/usr/bin/python': free(): invalid size: 0x00007f628400d0e0

Christian Heimes added the comment: Please also provide more information about your system: platform, distro, architecture, OpenSSL version, exact Python version etc. -- ___ Python tracker

[issue29470] [python] Error in `/usr/bin/python': free(): invalid size: 0x00007f628400d0e0

Christian Heimes added the comment: Please install debug symbols and provide a proper C backtrace of the invalid free call. The backtrace in your first comment is missing both line numbers, file and function names. -- ___ Python tracker

[issue29548] deprecate PyEval_Call*() functions.

INADA Naoki added the comment: > I'm more in favor of modifying PyEval_xxx() to call PyObject_xxx() and > deprecate them. That's PR 75 :) -- ___ Python tracker

[issue29157] random.c: Prefer getrandom() over getentropy() to support glibc 2.24 on Linux

STINNER Victor added the comment: Python 2.7, see issue #29188: "Backport random.c from Python 3.5 to Python 2.7". Mercurial commit 13a39142c047, Git commit 01bdbad3e951014c58581635b94b22868537901c. https://github.com/python/cpython/commit/01bdbad3e951014c58581635b94b22868537901c --

[issue29470] [python] Error in `/usr/bin/python': free(): invalid size: 0x00007f628400d0e0

STINNER Victor added the comment: You now have to test "PYTHONMALLOC=malloc valgrind python3 ...". IMHO it's not a bug in Python, but in your code ussing OpenSSL: File "/var/bluelabs/python/_cams_threaded_server.py", line 49 in sni_callback --

[issue29548] deprecate PyEval_Call*() functions.

STINNER Victor added the comment: > Please note that the two sets of APIs are not identical, e.g. you cannot > simply replace PyEval_CallObject() with PyObject_Call(), since the former > applies a few extra checks and defaults, which the latter doesn't. IMHO these checks are too expensive at

[issue29548] deprecate PyEval_Call*() functions.

STINNER Victor added the comment: "you now add the extra support for args being NULL to PyObject_Call()" I dislike this idea. I don't want to change the API of this function. If it is likely that NULL is the result of a previous error: args = Py_BuildValue(...); res = PyObject_Call(func,

[issue29548] deprecate PyEval_Call*() functions.

Marc-Andre Lemburg added the comment: Looking through Python's history, it's interesting that PyObject_Call() did apply the args == NULL checks up until Python 2.1. In Python 2.2 this was replaced by a direct call to tp_call, without the checks. However, the tp_call slots don't do this check

[issue25720] Fix curses module compilation with ncurses6

Ismail Donmez added the comment: What's the status on this? Can you please create a pull request on Github so we can continue there? -- ___ Python tracker

[issue24665] CJK support for textwrap

STINNER Victor added the comment: See also the now old issue #12568: "Add functions to get the width in columns of a character". -- ___ Python tracker

[issue11165] Document PyEval_Call* functions

Marc-Andre Lemburg added the comment: The PyEval_Call*() APIs indeed predate the PyObject_Call*() ones. The PyObject_Call*() APIs came into existence when the abstract layer was added in Python 1.3. The PyObject_Call*() APIs lacked a way to call an object with keyword arguments for a long

[issue5667] Interpreter fails to initialize on build dir when IO encoding is one of CJK

STINNER Victor added the comment: I'm unable to reproduce the bug. It seems like it was fixed since 8 years ;-) haypo@selma$ LC_ALL=ko_KR.eucKR ./python Python 3.7.0a0 (default, Feb 14 2017, 10:48:09) [GCC 6.3.1 20161221 (Red Hat 6.3.1-1)] on linux Type "help", "copyright", "credits" or

[issue24665] CJK support for textwrap

STINNER Victor added the comment: Florent Gallaire: Since Python 3.0 was released in 2008, new features are no more accepted in Python 2 (Python 2.7, the last release of Python 2). It's a deliberate choice, mostly motivated by the lack of CPython developers. See also the PEP 404. I'm only

[issue29548] deprecate PyEval_Call*() functions.

INADA Naoki added the comment: > The argument tuple can be NULL for PyEval_CallObject() (it then gets replaced > with an empty tuple), but will raise a segfault for PyObject_Call(). PyObject_CallObject() accepts NULL as args. Macro vs function is only difference of them. On the other hand,

[issue29470] [python] Error in `/usr/bin/python': free(): invalid size: 0x00007f628400d0e0

David Ford (FirefighterBlu3) added the comment: 2017-02-14 06:58:29 INFO connected: mustang.blue-labs.org/107.170.82.162:37188 2017-02-14 06:58:29 INFO No cert required for this host *** Error in `/usr/bin/python': double free or corruption (out): 0x7fb0f8003400 *** 2017-02-14 06:58:29

[issue11173] Undocumented public APIs in Python 3.2

Marc-Andre Lemburg added the comment: PyEval_CallObject wasn't removed. It's a macro now. And it was documented for a long time in Extending Python... in fact, the documentation was removed, not the API :-) -- ___ Python tracker

[issue26467] Add async magic method support to unittest.mock.Mock

Changes by Berker Peksag : -- nosy: +berker.peksag versions: +Python 3.7 ___ Python tracker ___

[issue29552] Issue in Dictionary fromkeys

Prudvi Mangadu added the comment: Also observed that ID of the values are pointing same, its ok. But if some one later modified that values which causes the un-usual output. >>> id(result['1']) 38121184 >>> id(result['2']) 38121184 -- ___ Python

  1   2   >