[issue31584] Documentation Language mixed up

INADA Naoki added the comment: Japanese HTML has this line: https://docs.python.org/2/faq/design.html; /> I suspect this line affects CDN's cache. But I can't find document about canonical link in fastly's document. -- nosy: +inada.naoki

[issue31728] crashes in _elementtree due to unsafe decrefs of Element.text and Element.tail

Oren Milman added the comment: As serhiy pointed out in a comment in PR 3924, setting self->text or self->tail to NULL might lead to an assertion failure, so we should also prevent the following assertion failure (and the similar one for tail): import xml.etree.ElementTree

[issue31736] PEP 485 tiny typo

Berker Peksag added the comment: Thank you for the report. Fixed in https://github.com/python/peps/commit/070dc7e037e5f66e4e17b661641503815a8bbe05 (By the way, you can report issues like this at https://github.com/python/peps/issues or send a PR directly.)

[issue31742] Default to emitting FutureWarning for provisional APIs

Amber Brown added the comment: Donald hits it on the head for me. As long as the code is not covered by the same API deprecation contract that the rest of the standard library is, it should make it obvious when attempting to use it. I can be relatively certain that

[issue31742] Default to emitting FutureWarning for provisional APIs

Donald Stufft added the comment: The fundamental problem is that unless you're closely following the development of python-dev, it's really really easy to use a provisional module without knowing that you are. Take asyncio for example, as far as I can tell the documentation

[issue31742] Default to emitting FutureWarning for provisional APIs

Guido van Rossum added the comment: While I understand the sentiment, having this warning pop up every time you import a provisional module while developing code feels like harassment of the very users we'd like to try out the provisional APIs. It's also too course-grained

[issue31742] Default to emitting FutureWarning for provisional APIs

Nick Coghlan added the comment: This is also fairly similar to Rust's approach of using feature flags to explicitly opt-in to unstable features: https://doc.rust-lang.org/unstable-book/ -- ___ Python tracker

[issue31742] Default to emitting FutureWarning for provisional APIs

Nick Coghlan added the comment: Another advantage of this approach: anyone running their tests in a "no warnings allowed" configuration would get a hard failure when dependencies on a provisional API were unexpectedly introduced (e.g. when updating a third party library),

[issue31742] Default to emitting FutureWarning for provisional APIs

New submission from Nick Coghlan : Chatting to Donald Stufft and Amber Brown about the way we currently handle provisional APIs, I think they have a legitimate concern that we may not be gathering adequately informed consent from users when they depend on APIs that we've

[issue31314] email throws exception with oversized header input

Dong-hee Na added the comment: I sent a patch if anyone have a time, please take a look :) -- nosy: +corona10 ___ Python tracker

[issue31741] backports import path can not be overridden in Windows (Linux works fine)

R. David Murray added the comment: What is "the backports module"? I still don't understand what a backports directory, that I don't think our installer creates, has to do with your MyLibraries directory. I'm sorry that I'm having trouble following your explanation.

[issue31741] backports import path can not be overridden in Windows (Linux works fine)

Chris Caron added the comment: Thank you for replying so quickly; the issue stems from a bug created here which explains it a bit better: https://github.com/caronc/nzb-notify/issues/27 (scroll to the bottom). In my case, I had a lib\site-packages\backports in C:\Python27

[issue31741] backports import path can not be overridden in Windows (Linux works fine)

R. David Murray added the comment: Where did you get your installer? I don't find any references to 'backports' in our repo, other than a couple of places in the docs where the word appears. I also don't understand the relationship between your MyPackages and a

[issue31741] backports import path can not be overridden in Windows (Linux works fine)

New submission from Chris Caron : The Windows install of Python 2.7.13 defaults it's install into **C:\Python27**. It creates several subdirectories within this; one of which is **C:\Python27\lib\site-packages\backports**. So just out of the box (without this script

[issue31608] crash in methods of a subclass of _collections.deque with a bad __new__()

Serhiy Storchaka added the comment: I meant that if make deque.copy(), deque.__add__() and deque.__mul__() returning an exact deque for subclasses, this would make the deque class more consistent with other collections and solve this issue. This could even make

[issue31740] refleaks when calling sqlite3.Connection.__init__() more than once

Oren Milman added the comment: Ah, here also there are crashes when calling methods of uninitialized connection objects. Should i fix this as part of this issue, or open another one? -- ___ Python tracker

[issue31738] Lib/site.py: method `abs_paths` is not documented

New submission from Julien Palard : Hi, thanks for reporting. This method has been renamed in https://github.com/python/cpython/commit/28a691b7fdde1b8abafa4c4a5025e6bfa44f48b9 and is only used in Lib/site.py (currently in main()). The function has a docstring, so:

[issue31740] refleaks when calling sqlite3.Connection.__init__() more than once

New submission from Oren Milman : The following code causes refleaks: import sqlite3 connection = sqlite3.Connection.__new__(sqlite3.Connection) connection.__init__('foo') connection.__init__('foo') This is because pysqlite_connection_init() (in Modules/_sqlite/connection.c)

[issue31734] crash or SystemError in sqlite3.Cache in case it is uninitialized or partially initialized

Change by Oren Milman : -- keywords: +patch pull_requests: +3912 stage: -> patch review ___ Python tracker ___

[issue31724] test_xmlrpc_net should use something other than buildbot.python.org

Change by Zachary Ware : -- stage: patch review -> needs patch ___ Python tracker ___

[issue31737] Documentation renders incorrectly

Julien Palard added the comment: Tested locally with different versions of sphinx-build: - 1.3.3 does not produce the issue - 1.6.2 (used on docs.python.org) produces the issue - 1.6.3 does not produce the issue - 1.6.4 does not produce the issue Reading the changelog

[issue31739] socket.close recommended but not demonstrated in same-page example code

R. David Murray added the comment: Which example? (It might be easiest to just generate a PR with your suggested improvement.) -- nosy: +r.david.murray ___ Python tracker

[issue31719] [2.7] test_regrtest.test_crashed() fails on s390x

Serhiy Storchaka added the comment: Why not use just abort() or Py_FatalError()? $ ./python -c 'import ctypes; ctypes.CDLL("libc.so.6").abort()' Aborted (core dumped) $ ./python -c 'import ctypes; ctypes.pythonapi.Py_FatalError(b"boom!")' Fatal Python error: boom!

[issue31739] socket.close recommended but not demonstrated in same-page example code

New submission from Nathaniel Manista : https://docs.python.org/3.7/library/socket.html#socket.socket.close says "it is recommended to close() [sockets] explicitly, or to use a with statement around them", but in the example code on the same page at

[issue26546] Provide translated french translation on docs.python.org

Julien Palard added the comment: → https://docs.python.org/fr/ -- stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue31584] Documentation Language mixed up

Julien Palard added the comment: FTR I'm still daily monitoring the presence of mixed-up pages server side and did not spotted a single one. I'm still using my very basic: $ grep -rl 'définition' /srv/docs.python.org/ja/; grep -rl か

[issue31737] Documentation renders incorrectly

Julien Palard added the comment: We spotted some quoting probleme in the french translation too, and I still didn't had time to look at it, typically here: https://docs.python.org/fr/3/library/itertools.html#itertool-functions where we're getting: 10.1.1.

[issue31314] email throws exception with oversized header input

Change by Dong-hee Na : -- keywords: +patch pull_requests: +3911 stage: -> patch review ___ Python tracker ___

[issue31705] test_sha256 from test_socket fails on ppc64le arch

Charalampos Stratakis added the comment: Attaching the strace output. -- Added file: https://bugs.python.org/file47202/trace ___ Python tracker

[issue31738] Lib/site.py: method `abs_paths` is not documented

Change by Liel Fridman : -- components: Tests nosy: lielfr priority: normal severity: normal status: open title: Lib/site.py: method `abs_paths` is not documented versions: Python 3.7 ___ Python tracker

[issue31737] Documentation renders incorrectly

Change by Ned Deily : -- nosy: +mdk ___ Python tracker ___ ___ Python-bugs-list mailing

[issue31737] Documentation renders incorrectly

New submission from Richard Gibson : The content at docs.python.org seems to be inserting language-dependent "smart quotes" in code blocks, which mangles backslashes and sequences like `'''`. Observed at

[issue31736] PEP 485 tiny typo

New submission from Ben Bolker : In two places in https://www.python.org/dev/peps/pep-0485/ floating point numbers are incorrectly formatted: 1-e8 and 1-e9 rather than 1e-8 and 1e-9 ("absolute tolerance default", para. 3 and "relative tolerance default", para. 1)

[issue31735] Documentation incorrectly states how descriptors are invoked

Paul Pinterits added the comment: If we take this class: class Obj: @property def d(self): print('called') And we access Obj.d: _ = Obj.d According to the docs, the following should happen: # obj.d looks up d in the dictionary of obj d = Obj.__dict__['d']

[issue31701] faulthandler dumps 'Windows fatal exception: code 0xe06d7363'

STINNER Victor added the comment: New changeset 6e3d6b5dc22cd06d8c4d44a38a8a3415e4bebb16 by Victor Stinner in branch 'master': bpo-31701: faulthandler: ignore MSC and COM Windows exception (#3929)

[issue31735] Documentation incorrectly states how descriptors are invoked

Paul Pinterits added the comment: I'm aware that descriptors have to exist on the class in order to work. The point is that the documentation states "If d defines the method __get__(), then d.__get__(obj) is invoked" (where d is obj.d), which is simply not true. --

[issue31415] Add -X option to show import time

Change by STINNER Victor : -- pull_requests: +3910 stage: resolved -> patch review ___ Python tracker ___

[issue27172] Undeprecate inspect.getfullargspec()

Tim Graham added the comment: Perhaps the reason for the undeprecation could use some clarification. In a Python 3 only world (where Django's master branch is), I believe there's still usefulness for inspect.getfullargspec() -- see

[issue31683] a stack overflow on windows in faulthandler._fatal_error()

STINNER Victor added the comment: IMHO this issue is theorical. I don't expect that anyone would call Py_FatalError() with a very long message, so I will not backport the fix to Python 2.7 and 3.6. Thanks for the bug report Oren Milman! -- resolution: ->

[issue24084] pstats: sub-millisecond display

Romuald Brunet added the comment: I figured we didn't want to change the size of the columns (+12 COL), but this could easily be done yes -- ___ Python tracker

[issue31178] [EASY] subprocess: TypeError: can't concat str to bytes, in _execute_child()

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

[issue31178] [EASY] subprocess: TypeError: can't concat str to bytes, in _execute_child()

STINNER Victor added the comment: commit fae0512e58619231a566bf77aa21148440b0ec8d Author: Miss Islington (bot) <31488909+miss-isling...@users.noreply.github.com> Date: Thu Oct 5 07:10:59 2017 -0700 [3.6] bpo-31178: Mock os.waitpid() in test_subprocess (GH-3896)

[issue31727] FTP_TLS errors when

Steve Dower added the comment: "OSError: [Errno 0] Error" typically means that OpenSSL failed due to a Windows error, but we assumed it failed due to a POSIX error and so read the wrong error number (errno instead of GetLastError()). It's worth testing with Python

[issue31735] Documentation incorrectly states how descriptors are invoked

Henk-Jaap Wagenaar added the comment: You get what you should get: when you print obj.d, Obj.d, you will get: which is exactly what you expect: - in the first case, you assigned a property object to the dictionary at obj.__dict__, so that's what you get back when

[issue31701] faulthandler dumps 'Windows fatal exception: code 0xe06d7363'

Steve Dower added the comment: > Is it possible to be asked to be called as the last handler ... Unfortunately not, since the stack-based handlers always come after the vector handlers, and C++ handlers written using try/catch will always be stack-based. It may be

[issue29324] test_aead_aes_gcm fails on Kernel 4.9

STINNER Victor added the comment: FYI the merged fix is: commit 9764c151c51480a7ca6042b1ccd69be2620ff360 Author: matejcik Date: Thu Feb 16 14:41:31 2017 +0100 update test_socket AEAD test for kernel 4.9 and up (#133) --

[issue31705] test_sha256 from test_socket fails on ppc64le arch

Charalampos Stratakis added the comment: Forgot the mention the kernel version which is 3.10.0-693.2.1.el7.ppc64le -- ___ Python tracker

[issue31705] test_sha256 from test_socket fails on ppc64le arch

STINNER Victor added the comment: > The issue is reproducible on a CentOS 7.4 on ppc64le architecture. What is the kernel version? It would be nice to have the strace output. Example: strace -o trace ./python -m test -v test_socket -m test_sha256 # then get the

[issue31681] pkgutil.get_data() leaks open files in Python 2.7

Change by Éric Araujo : -- assignee: -> merwok resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue31734] crash or SystemError in sqlite3.Cache in case it is uninitialized or partially initialized

Change by Eric N. Vander Weele : -- nosy: +ericvw ___ Python tracker ___ ___

[issue31723] refleaks in zipimport when calling zipimporter.__init__() more than once

Oren Milman added the comment: Yes, i am going manually over the code to find similar stuff to #31718, and i afraid i found quite a few, and still working on it.. -- ___ Python tracker

[issue31734] crash or SystemError in sqlite3.Cache in case it is uninitialized or partially initialized

Change by Serhiy Storchaka : -- nosy: +ghaering, serhiy.storchaka versions: +Python 2.7, Python 3.6 ___ Python tracker ___

[issue31723] refleaks in zipimport when calling zipimporter.__init__() more than once

STINNER Victor added the comment: > I'm curious, how did you find this code? Are you using a code generator > coupled with a tool to track for reference leaks? Oh, I think that the issue is related to bpo-31718. -- ___

[issue31723] refleaks in zipimport when calling zipimporter.__init__() more than once

STINNER Victor added the comment: I merged your PR, thanks! As I wrote on the PR: I don't think that a NEWS entry is needed, since you are not supposed to call __init__() multiple times. I don't think that it's worth it to backport the fix to Python 2.7 and 3.6. So

[issue31723] refleaks in zipimport when calling zipimporter.__init__() more than once

STINNER Victor added the comment: > The following code causes refleaks: I'm curious, how did you find this code? Are you using a code generator coupled with a tool to track for reference leaks? -- ___ Python tracker

[issue31723] refleaks in zipimport when calling zipimporter.__init__() more than once

STINNER Victor added the comment: New changeset c0cabc23bbe474d542ff8a4f1243f4ec3cce5549 by Victor Stinner (Oren Milman) in branch 'master': bpo-31723: Fix refleaks when zipimporter.__init__() is called more than once (GH-3919)

[issue31735] Documentation incorrectly states how descriptors are invoked

New submission from Paul Pinterits : The [descriptor howto](https://docs.python.org/3/howto/descriptor.html#invoking-descriptors) states: "For example, obj.d looks up d in the dictionary of obj. If d defines the method __get__(), then d.__get__(obj) is invoked [...]" This

[issue30008] OpenSSL 1.1.0 deprecated functions

Christian Heimes added the comment: Thanks for your patches, Mark. A few remarks: Python 3.5 is in security fix-only mode. The issue is not a security bug. Python has switched to a different workflow a while ago. Please provide a pull request on GitHub against master (3.7).

[issue30008] OpenSSL 1.1.0 deprecated functions

Change by Christian Heimes : -- pull_requests: +3908 stage: -> patch review ___ Python tracker ___

[issue24084] pstats: sub-millisecond display

STINNER Victor added the comment: Hum, "2447µs" makes the output more difficult to parse (by a program) and to read (by a human). Why not always displaying 6 digits (after the dot) for the two "percall" columns. -- nosy: +haypo

[issue31681] pkgutil.get_data() leaks open files in Python 2.7

Éric Araujo added the comment: New changeset cfe1aefcbd2534ddc1059a7332842644e6c8d1e4 by Éric Araujo (Elvis Pranskevichus) in branch '2.7': bpo-31681: Make sure pkgutil.get_data closes files properly (#3875)

[issue31092] delicate behaviour of shared (managed) multiprocessing Queues

Antoine Pitrou added the comment: > To a avoid race condition As Oren explained, the race condition is due to your use of the managed Queue. If you keep the object alive in the main process until the tasks have finished, there shouldn't be any problem. The question is: is

[issue31734] crash or SystemError in sqlite3.Cache in case it is uninitialized or partially initialized

Oren Milman added the comment: Also, the following code results in a memory leak: import sqlite3 cache = sqlite3.Cache.__new__(sqlite3.Cache) This is because pysqlite_cache_dealloc() just returns in case of an uninitialized Cache object. --

[issue31733] [2.7] Add PYTHONSHOWREFCOUNT environment variable to Python 2.7

STINNER Victor added the comment: Since this issue is on the thin border between "feature" and "bug fix", I would like to get the feedback of Benjamin on this change. @Benjamin: Are you ok to make such change late in the Python 2.7 cycle, in Python 2.7.15?

[issue31692] [2.7] Test `test_huntrleaks()` of test_regrtest fails in debug build with COUNT_ALLOCS

Serhiy Storchaka added the comment: All Victor's PRs LGTM is they look good to Benjamin. But on the next iteration we can get a report that tests don't work if set PYTHONSHOWREFCOUNT. -- ___ Python tracker

[issue27172] Undeprecate inspect.getfullargspec()

Larry Hastings added the comment: Wait, what is all this nonsense? inspect.getfullargspec is Python 3 only. It was added to support keyword-only parameters. Python 2 doesn't *have* keyword-only parameters, so it isn't needed there. Check for yourself: Python 2 doesn't

[issue31692] [2.7] Test `test_huntrleaks()` of test_regrtest fails in debug build with COUNT_ALLOCS

STINNER Victor added the comment: (I prefer to not split the discussion on this issue and my 2 PR, I prefer to only discuss the design in this issue.) https://github.com/python/cpython/pull/3927#pullrequestreview-67963845 Serhiy: > Using the requires_type_collecting

[issue31734] crash or SystemError in sqlite3.Cache in case it is uninitialized or partially initialized

New submission from Oren Milman : The following code causes a crash: import sqlite3 cache = sqlite3.Cache.__new__(sqlite3.Cache) cache.get(None) This is because pysqlite_cache_get() (in Modules/_sqlite/cache.c) assumes that the Cache object is initialized, and so it passes

[issue31692] [2.7] Test `test_huntrleaks()` of test_regrtest fails in debug build with COUNT_ALLOCS

STINNER Victor added the comment: > How many tests are still left broken if just change the COUNT_ALLOCS output > to stderr instead of stdout? That's my first PR: PR 3910. > COUNT_ALLOCS is not the only option that spoils Python output. Py_TRACE_REFS > adds even

[issue31692] [2.7] Test `test_huntrleaks()` of test_regrtest fails in debug build with COUNT_ALLOCS

STINNER Victor added the comment: Serhiy: "Do you going to backport also -X showrefcount?" I just created bpo-31733 "Add PYTHONSHOWREFCOUNT environment variable to Python 2.7". -- ___ Python tracker

[issue31733] [2.7] Add PYTHONSHOWREFCOUNT environment variable to Python 2.7

Change by STINNER Victor : -- nosy: +benjamin.peterson, ezio.melotti, serhiy.storchaka stage: patch review -> ___ Python tracker

[issue31733] [2.7] Add PYTHONSHOWREFCOUNT environment variable to Python 2.7

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

[issue30008] OpenSSL 1.1.0 deprecated functions

Mark Wright added the comment: My proposed patch based on python 3.6.3 to remove the use of the API that was deprecated in openssl 1.1. As RAND_pseudo_bytes was removed I call RAND_bytes instead. -- Added file:

[issue30008] OpenSSL 1.1.0 deprecated functions

Mark Wright added the comment: My proposed patch based on python 3.5.4 to remove the use of the API that was deprecated in openssl 1.1. As RAND_pseudo_bytes was removed I call RAND_bytes instead. -- Added file:

[issue30008] OpenSSL 1.1.0 deprecated functions

Mark Wright added the comment: This patch allows python 3.4.6 to compile with openssl 1.1 without using the deprecated API. It is hacky though as I had to backport changes that were already in 3.5.4 and 3.6.3. Also RAND_pseudo_bytes was removed, so I call RAND_bytes

[issue31733] [2.7] Add PYTHONSHOWREFCOUNT environment variable to Python 2.7

New submission from STINNER Victor : When Python 2.7 is built in debug mode, it displays the total number of references when the program finishes or after each statement in the interactive interpreter. Example: haypo@selma$ ./python Python 2.7.14+

[issue30008] OpenSSL 1.1.0 deprecated functions

Mark Wright added the comment: My proposed patch based on python 2.7.14 to remove the use of the API that was deprecated in openssl 1.1. -- keywords: +patch nosy: +gienah Added file: https://bugs.python.org/file47198/python-2.7.14-openssl-1.1.0.patch

[issue24084] pstats: sub-millisecond display

Change by Roundup Robot : -- pull_requests: +3906 ___ Python tracker ___

[issue31732] Add TRACE level to the logging module

STINNER Victor added the comment: More references to TRACE logging level: * "CUSTOM_TRACE = 5 # Mapping for zLOG.TRACE" in Zope zLOG https://github.com/zopefoundation/zLOG/blob/master/src/zLOG/EventLogger.py#L29 * Runlevel = stem.util.enum.UppercaseEnum('TRACE',

[issue31732] Add TRACE level to the logging module

STINNER Victor added the comment: Other references to a TRACE logging level: * SaltStack: trace = 5 https://docs.saltstack.com/en/latest/ref/configuration/logging/#log-levels * autologging.TRACE = 1: "A custom tracing log level, lower in severity than

[issue31445] Index out of range in get of message.EmailMessage.get()

Michala added the comment: I added 2 lines into the file "email/_header_value_parser.py" into the function "get_mailbox_list(value)" before return value: if not value: value = ';' return mailbox_list, value It is in attachments. -- resolution:

[issue31732] Add TRACE level to the logging module

STINNER Victor added the comment: Attached PR 3930 adds logging.TRACE, logging.trace() and logging.Logger.trace(). -- nosy: +vinay.sajip ___ Python tracker

[issue31732] Add TRACE level to the logging module

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

[issue31692] [2.7] Test `test_huntrleaks()` of test_regrtest fails in debug build with COUNT_ALLOCS

Serhiy Storchaka added the comment: Adding PYTHONSHOWALLOCCOUNT looks rather like a new feature to me. It is on to Bejaming to make a decision about this. The difference between an environment variable and a command line option is that the former is inherited by

[issue31732] Add TRACE level to the logging module

New submission from STINNER Victor : The logging module has already 5 log levels: CRITICAL, ERROR, WARNING, INFO, DEBUG. https://docs.python.org/dev/library/logging.html#logging-levels (I don't count NOTSET, I don't consider it to be "usable", at least not in an

[issue31692] [2.7] Test `test_huntrleaks()` of test_regrtest fails in debug build with COUNT_ALLOCS

Iryna Shcherbina added the comment: I have run a test build with the patch from PR 3927 applied, and all tests passed. Full build log can be viewed here: https://kojipkgs.fedoraproject.org//work/tasks/8392/22348392/build.log --

[issue10496] Python startup should not require passwd entry

Nicholas Brown added the comment: This is also a problem when using the DynamicUser=yes feature available in systemd 232 onward with a service that's implemented in python. See http://0pointer.net/blog/dynamic-users-with-systemd.html for details of the DynamicUser=

[issue31701] faulthandler dumps 'Windows fatal exception: code 0xe06d7363'

STINNER Victor added the comment: I abandon my intent to log all interesting errors: PR 3929 now always ignore all MSC and COM Windows exceptions. -- ___ Python tracker

[issue31701] faulthandler dumps 'Windows fatal exception: code 0xe06d7363'

Change by STINNER Victor : -- pull_requests: +3904 ___ Python tracker ___ ___

[issue31701] faulthandler dumps 'Windows fatal exception: code 0xe06d7363'

STINNER Victor added the comment: I failed to build https://github.com/FynnBe/faulthandler-spam with a Python built myself. But I succeeded to recompile a Python extension (_overlapped) in C++ (I removed two functions which caused compilation error) and then added

[issue31701] faulthandler dumps 'Windows fatal exception: code 0xe06d7363'

STINNER Victor added the comment: I misunderstood how Windows works. UNIX signals handlers and Windows exception handlers are unrelated. Exception handlers are not called to handle a SIGSEGV signal (raised manually by the process itself, not raised by the Windows

[issue31701] faulthandler dumps 'Windows fatal exception: code 0xe06d7363'

STINNER Victor added the comment: I wrote the PR 3928 to call AddVectoredExceptionHandler(0, ...) rather than AddVectoredExceptionHandler(1, ...), but it doesn't work as expected. I tested "faulthandler.enable(); faulthandler._sigsegv()": a traceback is logged. But

[issue31701] faulthandler dumps 'Windows fatal exception: code 0xe06d7363'

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

[issue31666] Pandas_datareader Error Message - ModuleNotFoundError: No module named 'pandas_datareader' with module in folder

Stéphane Wirtel added the comment: Hi, Your bug is related to Pandas and not to Python 3.6. Maybe you need to post your issue to the bug tracker of Pandas. You need to install pandas-datareader pip install pandas-datareader But it is not an issue with Python. Have a

[issue31692] [2.7] Test `test_huntrleaks()` of test_regrtest fails in debug build with COUNT_ALLOCS

STINNER Victor added the comment: I tested PR 3927. I run "./python -m test -j8 -r" with PYTHONSHOWALLOCCOUNT unset: the full Python test suite pass in release and debug modes: * ./configure CFLAGS="-D COUNT_ALLOCS=1" * ./configure --with-pydebug CFLAGS="-D

[issue27172] Undeprecate inspect.getfullargspec()

Nick Coghlan added the comment: Oops, we/I missed the window for also getting the deprecation removed from 3.5.x (as that branch is now in security-fix only mode). Marking as resolved for 3.6 accordingly. -- resolution: -> fixed stage: backport needed -> resolved

[issue31666] Pandas_datareader Error Message - ModuleNotFoundError: No module named 'pandas_datareader' with module in folder

Scott Tucholka added the comment: I am running Windows 10 Enterprise x64 and use Spyder (Python 3.6). This is my code: import pandas as pd import pandas_datareader as dr dr.get_data_yahoo('AAPL') I am expecting that the module will import and the get_data_yahoo will

[issue31267] threading.Timer object is affected by changes to system time: Python locks should use a monotonic clock if available

STINNER Victor added the comment: > it looks as if measures were implemented but never merged. The blocker issue is that sem_timedwait() doesn't support CLOCK_MONOTONIC. The glibc has to be enhanced to support this new feature. --

[issue31692] [2.7] Test `test_huntrleaks()` of test_regrtest fails in debug build with COUNT_ALLOCS

STINNER Victor added the comment: Ok, so. I wrote a different PR: PR 3927 adds a new PYTHONSHOWALLOCCOUNT environment variable and write allocations statistics into stderr (rather than stdout) when PYTHONSHOWALLOCCOUNT is set. The PR also fixes the test suite for

[issue19527] Test failures with COUNT_ALLOCS

Change by STINNER Victor : -- pull_requests: +3902 ___ Python tracker ___ ___

  1   2   >