[issue36546] Add quantiles() to the statistics module

Raymond Hettinger added the comment: One other thought: The PR implements both methods 6 and 7 which means that that we can reproduce the results of every major stats tool except for Mathematica. The summary of properties chart of in Hyndman & Fan lists our default as satisfying 5 of 6

[issue36640] python ibm_db setup.py post install script does not seem to work from Anaconda

Saba Kauser added the comment: I have debugged this further. The problem seems be happening due to usage of get_python_lib(). e.g: if('darwin' in sys.platform): class PostInstall(install): """ Post installation - run install_name_tool on Darwin """ def run(self):

[issue36546] Add quantiles() to the statistics module

Raymond Hettinger added the comment: Steven, as requested I added a documentation note reserving the right to add other interpolation methods. We can make the note stronger if you like. Otherwise, I think we're good to go now. Mark, thanks for the link. I've read all the posts and agree

[issue36693] Reversing large ranges results in a minor type inconsistency

Raymond Hettinger added the comment: This all seems proper to me. In each case, an iterator is returned -- that is the documented behavior. The specific type of iterator is allowed to vary in ways that are convenient for the implementation. Specifically, reversed() will call

[issue36695] Change (regression?) in v3.8.0a3 doctest output after capturing the stderr output from a raised warning

New submission from Brian Skinn : In [this project](https://github.com/bskinn/stdio-mgr) of mine, I have a tox matrix set up with Pythons from 3.3. to 3.8. I have pytest set up to run doctest on my

[issue23078] unittest.mock patch autospec doesn't work on staticmethods

Berker Peksag added the comment: Thank you! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue23078] unittest.mock patch autospec doesn't work on staticmethods

Berker Peksag added the comment: New changeset 15a57a3cadb992bb1752302333ff593e7eab284c by Berker Peksag in branch '3.7': bpo-23078: Add support for {class,static}method to mock.create_autospec() (GH-11613) https://github.com/python/cpython/commit/15a57a3cadb992bb1752302333ff593e7eab284c

[issue35586] Open pyexpat compilation, Make shows error（missing separator）

Aaron Hurst added the comment: This is the same issue as https://bugs.python.org/issue35184 I can reproduce this issue by uncommenting the pyexpat line in Setup.dist and compiling. The issue is with -DXML_POOR_ENTROPY=1. The equals character causes the line to be incorrectly interpreted

[issue23078] unittest.mock patch autospec doesn't work on staticmethods

Change by Berker Peksag : -- pull_requests: +12829 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue23078] unittest.mock patch autospec doesn't work on staticmethods

Change by Berker Peksag : -- pull_requests: -11349 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue23078] unittest.mock patch autospec doesn't work on staticmethods

Berker Peksag added the comment: New changeset 9b21856b0fcda949de239edc7aa6cf3f2f4f77a3 by Berker Peksag (Xtreak) in branch 'master': bpo-23078: Add support for {class,static}method to mock.create_autospec() (GH-11613)

[issue36670] test suite broken due to cpu usage feature on win 10/ german

Steve Dower added the comment: If the code page is set to UTF-8 then mbcs will still be the right encoding :) -- ___ Python tracker ___

[issue36518] Avoid conflicts when pass arbitrary keyword arguments to Python function

Steve Dower added the comment: No, now there is syntax that anyone using built in functions will have already learned I see no reason to create another way to solve the problem. -- ___ Python tracker

[issue35184] Makefile is not correctly generated when compiling pyextat with DXML_POOR_ENTROPY=1

Aaron Hurst added the comment: I can reproduce this issue by uncommenting the pyexpat line in Setup.dist and compiling. The issue is with -DXML_POOR_ENTROPY=1. The equals character causes the line to be incorrectly interpreted as a macro definition by makesetup. This results in an

[issue35184] Makefile is not correctly generated when compiling pyextat with DXML_POOR_ENTROPY=1

Change by Aaron Hurst : -- keywords: +patch pull_requests: +12827 stage: -> patch review ___ Python tracker ___ ___

[issue24011] Add error checks to PyInit_signal()

Berker Peksag added the comment: New changeset 9541bd321a94f13dc41163a5d7a1a847816fac84 by Berker Peksag (Joannah Nanjekye) in branch 'master': bpo-24011: Use PyModule_Add{Object,IntMacro} in PyInit__signal() (GH-12765)

[issue24011] Add error checks to PyInit_signal()

Berker Peksag added the comment: Thank you, Joannah. There's no need to backport PR 12765 to maintenance branches, so I'm closing this issue as 'fixed'. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: -Python 3.7

[issue36678] duplicate method definitions in Lib/test/test_dataclasses.py

Change by Windson Yang : -- keywords: +patch pull_requests: +12826 stage: needs patch -> patch review ___ Python tracker ___ ___

[issue36523] Add docstring to io.IOBase.writelines

Marcin Niemira added the comment: Hey, Is there something I can improve in this PR? -- ___ Python tracker ___ ___ Python-bugs-list

[issue36645] re.sub() library entry does not adequately document surprising change in behavior between versions

Berker Peksag added the comment: Thank you! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed type: -> behavior versions: +Python 3.8 ___ Python tracker

[issue36645] re.sub() library entry does not adequately document surprising change in behavior between versions

miss-islington added the comment: New changeset 71b88827f6ad368eafa17983bd979175d24da888 by Miss Islington (bot) in branch '3.7': bpo-36645: Fix ambiguous formatting in re.sub() documentation (GH-12879) https://github.com/python/cpython/commit/71b88827f6ad368eafa17983bd979175d24da888

[issue36645] re.sub() library entry does not adequately document surprising change in behavior between versions

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

[issue36645] re.sub() library entry does not adequately document surprising change in behavior between versions

Berker Peksag added the comment: New changeset 5ebfa840a1c9967da299356733da41b532688988 by Berker Peksag (mollison) in branch 'master': bpo-36645: Fix ambiguous formatting in re.sub() documentation (GH-12879) https://github.com/python/cpython/commit/5ebfa840a1c9967da299356733da41b532688988

[issue36685] C implementation of xml.etree.ElementTree does not make a copy of attrib argument when creating new Element

Change by Gordon P. Hemsley : -- keywords: +patch pull_requests: +12823 stage: needs patch -> patch review ___ Python tracker ___

[issue35149] pip3 show causing Error for ConfigParaser

Eryk Sun added the comment: In Windows, Python defaults to the system ANSI codepage (e.g. 1252 in the West) for non-console standard I/O. For the case of a `for /f` loop in CMD, stdout is a pipe, so Python defaults to writing ANSI encoded text to its end of the pipe. I recommend overriding

[issue36691] SystemExit & sys.exit : Allow both exit status and message

Change by Barry A. Warsaw : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36693] Reversing large ranges results in a minor type inconsistency

Paul Ganssle added the comment: I believe the relevant code is here: https://github.com/python/cpython/blob/bb86bf4c4eaa30b1f5192dab9f389ce0bb61114d/Objects/rangeobject.c#L1038 It looks like it's a performance enhancement and that for ranges where the beginning and end can fit in a C long,

[issue35149] pip3 show causing Error for ConfigParaser

Karthikeyan Singaravelan added the comment: I am able to reproduce this by explicitly setting PYTHONIOENCODING as ascii . But I am not sure about the defaults in Windows (related to your environment, os only?) and perhaps something has changed since 3.6 since it fails when executed under

[issue36693] Reversing large ranges results in a minor type inconsistency

Paul Ganssle added the comment: I have edited the title to be a bit more and give more context. Donald, if you feel I have misrepresented your issue, please feel free to tweak it further. -- nosy: +p-ganssle title: Minor inconsistancy with types. -> Reversing large ranges results in

[issue36694] Excessive memory use or memory fragmentation when unpickling many small objects

Change by Paul Ellenbogen : Removed file: https://bugs.python.org/file48278/dump.py ___ Python tracker ___ ___ Python-bugs-list mailing

[issue36694] Excessive memory use or memory fragmentation when unpickling many small objects

Change by Paul Ellenbogen : Removed file: https://bugs.python.org/file48281/dump.py ___ Python tracker ___ ___ Python-bugs-list mailing

[issue36694] Excessive memory use or memory fragmentation when unpickling many small objects

Change by Paul Ellenbogen : Added file: https://bugs.python.org/file48282/dump.py ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue36694] Excessive memory use or memory fragmentation when unpickling many small objects

Paul Ellenbogen added the comment: Good point. I have created a new version of dump that uses random() instead. float reuse explains the getsizeof difference, but there is still a significant memory usage difference. This makes sense to me because the original code I saw this issue in is

[issue36694] Excessive memory use or memory fragmentation when unpickling many small objects

Serhiy Storchaka added the comment: The difference is because in the first case all floats are the same float object 0.0, but in the second case they are different objects. For more reaĺistic comparison use different floats (for example random()). -- nosy: +serhiy.storchaka

[issue36693] Minor inconsistancy with types.

Change by SilentGhost : -- nosy: +christian.heimes versions: +Python 3.7, Python 3.8 -Python 3.5 ___ Python tracker ___ ___

[issue36694] Excessive memory use or memory fragmentation when unpickling many small objects

Change by Paul Ellenbogen : Added file: https://bugs.python.org/file48280/common.py ___ Python tracker ___ ___ Python-bugs-list mailing

[issue36694] Excessive memory use or memory fragmentation when unpickling many small objects

New submission from Paul Ellenbogen : Python encounters significant memory fragmentation when unpickling many small objects. I have attached two scripts that I believe demonstrate the issue. When you run "dumpy.py" it will generate a large list of namedtuples, then write that list to a file

[issue36694] Excessive memory use or memory fragmentation when unpickling many small objects

Change by Paul Ellenbogen : Added file: https://bugs.python.org/file48279/load.py ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue32424] Synchronize copy methods between Python and C implementations of xml.etree.ElementTree.Element

Change by Gordon P. Hemsley : -- pull_requests: +12822 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36693] Minor inconsistancy with types.

New submission from Donald Hobson : Almost all of python makes the abstraction that ints are a single type of thing, the fact that some ints are too big to store in 8 bytes of memory is abstracted away. This abstraction fails when you try to reverse large ranges. >>> reversed(range(1<<63))

[issue36684] codecov.io code coverage has not updated since 2019-04-13

Gordon P. Hemsley added the comment: I'm not sure when the gcc build started failing, but it looks like the commits at the boundary failed due to max build time. Something is apparently too slow to run. -- ___ Python tracker

[issue36684] codecov.io code coverage has not updated since 2019-04-13

Change by SilentGhost : -- components: +Build nosy: +zach.ware versions: +Python 3.8 ___ Python tracker ___ ___ Python-bugs-list

[issue36684] codecov.io code coverage has not updated since 2019-04-13

Gordon P. Hemsley added the comment: It looks like this may be the result of the code coverage being provided by the optional gcc build, which has been failing for quite a while. -- ___ Python tracker

[issue36684] codecov.io code coverage has not updated since 2019-04-13

Gordon P. Hemsley added the comment: In fact, it seems the last commit on master was 962b028b0c20abcf39594f08b1e5f8c36c4e5f6f 3 months ago, which doesn't even have valid report. The previous commit, 9932a22897ef9905161dac7476e6976370e13515, was the last to have a functioning report.

[issue36691] SystemExit & sys.exit : Allow both exit status and message

Serhiy Storchaka added the comment: The default handler writes the message of non-integer code to stderr, but in case of '--help', the message should be written to stdout. So this feature is not applicable for it. Are there other examples where this feature can be used? In such cases it is

[issue36690] A typing error in demo rpython.py

Change by SilentGhost : -- keywords: +easy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36690] A typing error in demo rpython.py

SilentGhost added the comment: Would you be interested in submitting a PR on github? Guidelines can be found on https://devguide.python.org/pullrequest/ if you're not sure how to proceed. -- nosy: +SilentGhost stage: -> needs patch type: crash -> behavior versions: +Python 3.7,

[issue36692] Unexpected stderr output from test_sys_settrace

New submission from Nick Coghlan : The test output from test_sys_settrace makes it look like a couple of the async tracing tests aren't cleaning up after themselves properly: ``` [ncoghlan@localhost cpython]$ ./python -m test test_sys_settrace Run tests sequentially 0:00:00 load avg: 1.27

[issue35998] test_asyncio: test_start_tls_server_1() TimeoutError on Fedora 29

Change by Nick Coghlan : -- nosy: +ncoghlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36691] SystemExit & sys.exit : Allow both exit status and message

New submission from Thomas Kluyver : The SystemExit exception, and consequently the sys.exit() function, take a single parameter which is either an integer exit status for the process, or a message to print to stderr before exiting - in which case the exit status is implicitly 1. In

[issue36690] A typing error in demo rpython.py

New submission from jiawei zhou : Hi. There is an error in file `Tools/demo/rpython.py` at line 22. The original statement is `port = int(port[i+1:])`, but it will crash if the port is specified as parameters. The correct code should be `port = int(host[i+1:])`. Then the program can read

[issue36518] Avoid conflicts when pass arbitrary keyword arguments to Python function

Serhiy Storchaka added the comment: Steve, do you mind to create a PEP? I can help with examples and comments, but it is too hard to me to write it myself. -- ___ Python tracker

[issue36689] docs: os.path.commonpath raises ValueError for different drives

Change by Serhiy Storchaka : -- keywords: +easy stage: -> needs patch versions: +Python 3.7 ___ Python tracker ___ ___

[issue36689] docs: os.path.commonpath raises ValueError for different drives

New submission from Christoph Reiter : Since I just got bit by this despite reading the docs: https://docs.python.org/3.8/library/os.path.html#os.path.commonpath It lists various error cases where ValueError is raised but is missing the case where absolute paths on Windows are on different

[issue32780] ctypes: memoryview gives incorrect PEP3118 format strings for both packed and unpacked structs

Stefan Krah added the comment: Since Terry added me: Yes, this is clearly a bug, but it is a ctypes issue and not a memoryview issue. ctypes issues unfortunately tend to take some time until someone reviews. -- ___ Python tracker

[issue26746] struct.pack(): trailing padding bytes on x64

Change by Stefan Krah : -- nosy: +Eric.Wieser ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue32424] Synchronize copy methods between Python and C implementations of xml.etree.ElementTree.Element

Serhiy Storchaka added the comment: Concur with Stefan. Adding the method deprecated from the born looks silly. We should either deprecate the copy() method in the Python implementation, or add an undeprecated method in the C implementation. The latter should be considered as a new feature.

[issue33777] dummy_threading: .is_alive method returns True after execution has completed

Nate Atkinson added the comment: To be clear-- is_alive() doesn't *always* return True. It returns True until .join() is called. Python 3.6.7 (default, Oct 22 2018, 11:32:17) [GCC 8.2.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> from dummy_threading

[issue22246] add strptime(s, '%s')

Change by Karthikeyan Singaravelan : -- nosy: +p-ganssle ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue32424] Synchronize copy methods between Python and C implementations of xml.etree.ElementTree.Element

Stefan Behnel added the comment: We should not add anything to the implementation that we consider legacy elsewhere. Py3 has "always" used the C accelerator module instead of the Python implementation, which suggests that its interface is probably the righter one. So: make sure that the

[issue36685] C implementation of xml.etree.ElementTree does not make a copy of attrib argument when creating new Element

Stefan Behnel added the comment: Given that this has probably been like this forever, and thus provably doesn't hurt very much, I would argue that it's not worth fixing this in Py3.7. Not sure about Py2.7, but I think the answer there should be a no, too. -- stage: -> needs patch

[issue36685] C implementation of xml.etree.ElementTree does not make a copy of attrib argument when creating new Element

Stefan Behnel added the comment: Instead of always copying the dict in create_new_element(), we should make sure that all code that calls that function (directly or indirectly) does so with a safely owned dict. If that means that we need to add dict copying in some other place, then that's

[issue36688] import dummy_threading causes ImportError

New submission from Karthikeyan Singaravelan : importing dummy_threading causes ImportError. It used to work on 3.6. There are tests at Lib/test/test_dummy_threading.py and rearranging the import so that "import dummy_threading as _threading" is the first line also causes error. This module

[issue33777] dummy_threading: .is_alive method returns True after execution has completed

Karthikeyan Singaravelan added the comment: https://bugs.python.org/issue29376#msg286873 . Is this an intentional behavior for dummy_threading to always return True for is_alive? -- nosy: +pitrou, xiang.zhang, xtreak ___ Python tracker