[issue35283] "threading._DummyThread" redefines "is_alive" but forgets "isAlive"

Dong-hee Na added the comment: Hi, Can I work with this issue if no one works on it? -- nosy: +corona10 ___ Python tracker ___ ___

[issue35293] make doctest (Sphinx) emits a lot of warnings

Dong-hee Na added the comment: Looks like they already fixed it. - jinja2: https://github.com/pallets/jinja/commit/31bf9b7e71c3fee3b7866ffdc0f70f4525a490d9 - babel: https://github.com/python-babel/babel/commit/65d6bf39f2a2b4c02cd1e00c44ce9d7c1c5b We should wait their release :)

[issue9566] Compilation warnings under x64 Windows

Change by STINNER Victor : -- pull_requests: +9905 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35059] Convert Py_INCREF() and PyObject_INIT() to inlined functions

Change by STINNER Victor : -- pull_requests: +9904 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35290] [FreeBSD] test_c_locale_coercion: fsencoding is ASCII instead of UTF-8 on FreeBSD CURRENT buildbot

STINNER Victor added the comment: Result of the additional debug info, on the FreeBSD CURRENT buildbot: AVAILABLE_TARGETS = ['C.UTF-8'] EXPECTED_C_LOCALE_EQUIVALENTS = ['C', 'invalid.ascii'] EXPECTED_C_LOCALE_STREAM_ENCODING = 'ascii' EXPECTED_C_LOCALE_FS_ENCODING = 'ascii'

[issue35059] Convert Py_INCREF() and PyObject_INIT() to inlined functions

STINNER Victor added the comment: New changeset a42de742e7c20eeb64699b5785543fea65b2e8d3 by Victor Stinner in branch 'master': bpo-35059: Cast void* to PyObject* (GH-10650) https://github.com/python/cpython/commit/a42de742e7c20eeb64699b5785543fea65b2e8d3 --

[issue24746] doctest 'fancy diff' formats incorrectly strip trailing whitespace

Sanyam Khurana added the comment: Thanks for your suggestion, Tim. I've fixed the patch and it is ready for review at https://github.com/python/cpython/pull/10639 -- ___ Python tracker

[issue35293] make doctest (Sphinx) emits a lot of warnings

STINNER Victor added the comment: > They are warnings related to third party packages used for doctest and some > of them might become incompatible with > https://github.com/python/cpython/pull/10596. Related discussion : issue35109 We should help these packages to be fixed :-) --

[issue35283] "threading._DummyThread" redefines "is_alive" but forgets "isAlive"

Andrew Svetlov added the comment: The only _DummyThread usage is `threading.current_thread()`: > If the caller's thread of control was not created through the threading > module, a dummy thread object with limited functionality is returned. -- nosy: +asvetlov

[issue18407] Fix compiler warnings in pythoncore for Win64

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue18407] Fix compiler warnings in pythoncore for Win64

Change by STINNER Victor : -- pull_requests: +9908 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue17490] Improve ast.literal_eval test suite coverage

Change by Nick Coghlan : -- assignee: -> ncoghlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue18407] Fix compiler warnings in pythoncore for Win64

STINNER Victor added the comment: New changeset c48ff73dd60bec5dcbe64bedeff91e6db26d98bc by Victor Stinner in branch 'master': bpo-18407: win32_urandom() uses PY_DWORD_MAX (GH-10656) https://github.com/python/cpython/commit/c48ff73dd60bec5dcbe64bedeff91e6db26d98bc --

[issue35290] [FreeBSD] test_c_locale_coercion doesn't support new C.UTF-8 locale of FreeBSD CURRENT

STINNER Victor added the comment: > I'm wondering if we may need to make test_c_locale_coercion less opinionated, > where for most platforms it's just a "don't segfault" test, and it's only for > ones where we're certain about how we expect it to behave (i.e. Linux, Mac OS > X, AIX, maybe

[issue24658] open().write() fails on 2 GB+ data (OS X)

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

[issue35283] "threading._DummyThread" redefines "is_alive" but forgets "isAlive"

Serhiy Storchaka added the comment: isAlive() is the part of the old API. It is not even documented in Python 3, and can be removed in future. It is better to remove it from docstrings. -- nosy: +serhiy.storchaka ___ Python tracker

[issue9566] Compilation warnings under x64 Windows

Change by STINNER Victor : -- pull_requests: +9907 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35295] Please clarify whether PyUnicode_AsUTF8AndSize() or PyUnicode_AsUTF8String() is preferred

New submission from Marcin Kowalczyk : The documentation is silent whether PyUnicode_AsUTF8AndSize() or PyUnicode_AsUTF8String() is preferred. We are under the assumption that both are acceptable for the given caller, i.e. the caller wants to access just the sequence of UTF-8 code units

[issue9566] Compilation warnings under x64 Windows

STINNER Victor added the comment: New changeset 28f468cb19e3097079b7ce7850e6048de99022fa by Victor Stinner in branch 'master': bpo-9566: Fix compiler warnings in pyexpat.c (GH-10654) https://github.com/python/cpython/commit/28f468cb19e3097079b7ce7850e6048de99022fa --

[issue9566] Compilation warnings under x64 Windows

STINNER Victor added the comment: There is also: commit cdbcb773f5db24e23fa90e644ec620d54bd08127 Author: Victor Stinner Date: Thu Nov 22 10:25:46 2018 +0100 cjkcodecs: Fix compiler warning (GH-10651) Fixed the following compiler warning in multibytecodec.c:

[issue24746] doctest 'fancy diff' formats incorrectly strip trailing whitespace

Change by Sanyam Khurana : -- assignee: -> CuriousLearner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue24658] open().write() fails on 2 GB+ data (OS X)

Change by STINNER Victor : -- pull_requests: +9910 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue24658] open().write() fails on 2 GB+ data (OS X)

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

[issue35284] Incomplete error handling in Python/compile.c:compiler_call()

Change by Serhiy Storchaka : -- nosy: +serhiy.storchaka, yselivanov ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue18407] Fix compiler warnings in pythoncore for Win64

Change by STINNER Victor : -- pull_requests: +9909 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue24925] Allow doctest to find line number of __test__ strings if formatted as a triple quoted string.

Sanyam Khurana added the comment: Hey R. David Murray, Where do you think the unit test for `doctest` should be placed? Should it be in `test_doctest.py`? -- assignee: -> CuriousLearner versions: +Python 3.7, Python 3.8 ___ Python tracker

[issue18407] Fix compiler warnings in pythoncore for Win64

STINNER Victor added the comment: New changeset 4d73ae776140a583fdfe8f016d88cc767791e481 by Victor Stinner in branch 'master': bpo-18407: ast.c uses Py_ssize_t for asdl_seq_LEN() iterator (GH-10655) https://github.com/python/cpython/commit/4d73ae776140a583fdfe8f016d88cc767791e481

[issue35290] [FreeBSD] test_c_locale_coercion: fsencoding is ASCII instead of UTF-8 on FreeBSD CURRENT buildbot

STINNER Victor added the comment: > AVAILABLE_TARGETS = ['C.UTF-8'] Aha, that's something new in FreeBSD. In FreeBSD 11.2, this locale is invalid. The locale has been added to FreeBSD CURRENT (future FreeBSD 12) at November 4: https://reviews.freebsd.org/D17833 See discussion on

[issue35134] Add a new Include/unstable/ subdirectory for the "unstable" API

Nick Coghlan added the comment: I think the rules for C includes are that `"path/header.h"` looks next to the current file first, whereas `` looks only in include directories. However, given your technique of mostly hiding the new directory name from API consumers, what do you think of

[issue35290] [FreeBSD] test_c_locale_coercion doesn't support new C.UTF-8 locale of FreeBSD CURRENT

Nick Coghlan added the comment: Ah, interesting. https://bugs.python.org/issue30672 covered the fact that this test was already weird on FreeBSD, but the current status is that it was expecting BSD variants to act somewhat like Mac OS X, not like Linux. I'm wondering if we may need to make

[issue35283] "threading._DummyThread" redefines "is_alive" but forgets "isAlive"

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

[issue35290] [FreeBSD] test_c_locale_coercion doesn't support new C.UTF-8 locale of FreeBSD CURRENT

STINNER Victor added the comment: More FreeBSD commits, "Teach man(1) about C.UTF-8": https://svnweb.freebsd.org/base?view=revision=340128 --- EXPECTED_C_LOCALE_STREAM_ENCODING = 'ascii' EXPECTED_C_LOCALE_FS_ENCODING = 'ascii' I guess that the problem comes from that. But I'm not sure of

[issue35283] "threading._DummyThread" redefines "is_alive" but forgets "isAlive"

Serhiy Storchaka added the comment: And since threads support no longer optional, are there reasons to keep _DummyThread? -- nosy: +pitrou ___ Python tracker ___

[issue35283] "threading._DummyThread" redefines "is_alive" but forgets "isAlive"

Change by Dong-hee Na : -- pull_requests: -9906 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35290] [FreeBSD] test_c_locale_coercion doesn't support new C.UTF-8 locale of FreeBSD CURRENT

Change by Kubilay Kocak : -- nosy: +koobs ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue18407] Fix compiler warnings in pythoncore for Win64

STINNER Victor added the comment: Almost all compiler warnings on 64-bit Windows have been fixed: bpo-9566 tracked most of them. I extract the CryptGenRandom() fix from issue18407-2.diff. I rewrote the ast.c fix differently (use larger type, don't downcast). The patch may still contains

[issue35283] "threading._DummyThread" redefines "is_alive" but forgets "isAlive"

Antoine Pitrou added the comment: If it's not already deprecated, I'd say deprecate it first. -- ___ Python tracker ___ ___

[issue35283] "threading._DummyThread" redefines "is_alive" but forgets "isAlive"

Dong-hee Na added the comment: @serhiy.storchaka @pitrou Then should we add the deprecated message for isAlive of class "Thread" first? -- ___ Python tracker ___

[issue35266] Add _PyPreConfig and rework _PyCoreConfig and _PyMainInterpreterConfig

Nick Coghlan added the comment: I didn't know what was possible when I wrote PEP 432 either - instead, I wrote down an initial concept for what I *wanted*, and then started exploring the code to find out the barriers to achieving that. We know enough now to know that original design concept

[issue24658] open().write() fails on 2 GB+ data (OS X)

STINNER Victor added the comment: New changeset 9a0d7a7648547ffb77144bf2480155f6d7940dea by Victor Stinner in branch 'master': bpo-24658: os.read() reuses _PY_READ_MAX (GH-10657) https://github.com/python/cpython/commit/9a0d7a7648547ffb77144bf2480155f6d7940dea --

[issue9263] Try to print repr() when an C-level assert fails (in the garbage collector, beyond?)

Change by STINNER Victor : -- pull_requests: +9915 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue9263] Try to print repr() when an C-level assert fails (in the garbage collector, beyond?)

Change by STINNER Victor : -- pull_requests: +9916 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35265] Internal C API: pass the memory allocator in a context

STINNER Victor added the comment: Honestly, I'm not convinced that the change is worth it. It looks like a giant complication for a very specific use case, whereas the current _PyMem_SetDefaultAllocator() solution "works". I close the issue. Moreover, bpo-35266 conflicts with issue, and

[issue35265] Internal C API: pass the memory allocator in a context

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

[issue35239] _PySys_EndInit() doesn't copy main interpreter configuration

STINNER Victor added the comment: New changeset a5194115733f6ca8fc1ddbee43eabbde536900e6 by Victor Stinner in branch '3.7': Revert "bpo-35239: _PySys_EndInit() copies module_search_path (GH-10532)" (GH-10660) https://github.com/python/cpython/commit/a5194115733f6ca8fc1ddbee43eabbde536900e6

[issue35239] _PySys_EndInit() doesn't copy main interpreter configuration

STINNER Victor added the comment: I has been decided to not backport the change to Python 3.7: see PR 10532 discusssion. -- ___ Python tracker ___

[issue35206] [WIP] Add a new experimental _Py_CAPI2 API

STINNER Victor added the comment: According to discussions on python-dev, a PEP will be needed first. Moreover, I prefer to make some progress on https://bugs.python.org/issue35134 before. I close the issue. -- resolution: -> rejected stage: patch review -> resolved status: open ->

[issue35239] _PySys_EndInit() doesn't copy main interpreter configuration

Change by STINNER Victor : -- pull_requests: +9913 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue9263] Try to print repr() when an C-level assert fails (in the garbage collector, beyond?)

Change by STINNER Victor : -- pull_requests: +9914 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35266] Add _PyPreConfig and rework _PyCoreConfig and _PyMainInterpreterConfig

STINNER Victor added the comment: Hum, my split is incomplete. From a high level point of view, the initialization should be done in these steps: 1) select memory allocator, config made of C char* (bytes) and int types 2) select encodings, add wchar_t* (Unicode) strings to the config 3)

[issue9263] Try to print repr() when an C-level assert fails (in the garbage collector, beyond?)

STINNER Victor added the comment: New changeset 2cf5d32fd9e61488e8b0be55a2e92a752ba8b06b by Victor Stinner in branch 'master': bpo-9263: Fix _PyObject_Dump() for freed object (#10661) https://github.com/python/cpython/commit/2cf5d32fd9e61488e8b0be55a2e92a752ba8b06b --

[issue9263] Try to print repr() when an C-level assert fails (in the garbage collector, beyond?)

STINNER Victor added the comment: New changeset c9b3fc6b59b625c36c31ad437253e7140938af1a by Victor Stinner in branch '3.6': bpo-9263: _PyObject_Dump() detects freed memory (GH-10061) (GH-10662) (GH-10663) https://github.com/python/cpython/commit/c9b3fc6b59b625c36c31ad437253e7140938af1a

[issue24658] open().write() fails on 2 GB+ data (OS X)

miss-islington added the comment: New changeset 18f3327d9a99163a658697465eb00c31f86535eb by Miss Islington (bot) in branch '3.7': bpo-24658: os.read() reuses _PY_READ_MAX (GH-10657) https://github.com/python/cpython/commit/18f3327d9a99163a658697465eb00c31f86535eb --

[issue35134] Add a new Include/unstable/ subdirectory for the "unstable" API

STINNER Victor added the comment: > I think the rules for C includes are that `"path/header.h"` looks next to the > current file first, whereas `` looks only in include > directories. Oh ok, thanks. > However, given your technique of mostly hiding the new directory name from > API

[issue24658] open().write() fails on 2 GB+ data (OS X)

miss-islington added the comment: New changeset 0c15e508baec7e542933db2b31ea950a646cd968 by Miss Islington (bot) in branch '3.6': bpo-24658: os.read() reuses _PY_READ_MAX (GH-10657) https://github.com/python/cpython/commit/0c15e508baec7e542933db2b31ea950a646cd968 --

[issue9263] Try to print repr() when an C-level assert fails (in the garbage collector, beyond?)

STINNER Victor added the comment: New changeset 95036ea25d47f0081bda2ba96ea327f3375cb6a4 by Victor Stinner in branch '3.7': [3.7] bpo-9263: _PyObject_Dump() detects freed memory (GH-10061) (GH-10662) https://github.com/python/cpython/commit/95036ea25d47f0081bda2ba96ea327f3375cb6a4

[issue35177] Add missing dependencies between AST/parser header files

STINNER Victor added the comment: Ok, I fixed the "Yield warning" again. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue35283] "threading._DummyThread" redefines "is_alive" but forgets "isAlive"

pmpp added the comment: about micropython, only unix port have thread basic implementation and garbage collector messes with EINTR actually so it is not very useable. unix port is only one on many, and is the less interesting port apart from running quick simulations. --

[issue35283] "threading._DummyThread" redefines "is_alive" but forgets "isAlive"

Andrew Svetlov added the comment: Well, to satisfy everybody we need to: 1. Implement `isAlive` for dummy thread 2. Add a deprecation warning for both Thread.isAlive and _DummyThread.isAlive 3. Remove isAlive in future Python release (3.8 for the deprecation, 3.8+2 for removal). 4.

[issue35296] Install Include/internal/ header files

STINNER Victor added the comment: Example of debuggers: vmprof or faulthandler (now part of the stdlib). -- ___ Python tracker ___

[issue35296] Install Include/internal/ header files

STINNER Victor added the comment: TODO: Update the Windows installer: https://github.com/python/cpython/pull/10624#issuecomment-441090519 -- ___ Python tracker ___

[issue35134] Add a new Include/unstable/ subdirectory for the "unstable" API

Brett Cannon added the comment: The "unstable" name bugs me as it suggests we might change it without notice which isn't true at all. It's more a limited versus broad API. So maybe rename the directory "broad"? -- nosy: +brett.cannon ___ Python

[issue35283] "threading._DummyThread" redefines "is_alive" but forgets "isAlive"

Brett Cannon added the comment: I guess the question is whether any other Python implementation is threadless? E.g. is MicroPython? If it even has threads then I agree about deprecating the module. But if MicroPython does support threads we should keep the module. That would mean updating

[issue35296] Install Include/internal/ header files

New submission from STINNER Victor : For some very specific use cases (ex: debuggers), it can be interesting to access the internal API of CPython. I propose to install the internal API: Include/internal/*.h header files. Attached PR implements this idea. -- components: Interpreter

[issue35296] Install Include/internal/ header files

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

[issue35177] Add missing dependencies between AST/parser header files

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

[issue35177] Add missing dependencies between AST/parser header files

STINNER Victor added the comment: New changeset 3bb183d7fb83ad6a84ec13dea90f95d67be35c69 by Victor Stinner in branch 'master': bpo-35177, Python-ast.h: Fix "Yield" compiler warning (GH-10664) https://github.com/python/cpython/commit/3bb183d7fb83ad6a84ec13dea90f95d67be35c69 --

[issue35081] Move internal headers to Include/internal/

Change by STINNER Victor : -- pull_requests: +9919 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35283] "threading._DummyThread" redefines "is_alive" but forgets "isAlive"

pmpp added the comment: > I guess the question is whether any other Python implementation is threadless? emscripten python ( cpython on asm.js or webassembly ) is threadless -- nosy: +pmpp ___ Python tracker

[issue35292] Make SimpleHTTPRequestHandler load mimetypes lazily

Danish Prakash added the comment: I would like to work on this if you have not already started, Steve. > We should check whether people read from > SimpleHTTPRequestHandler.extensions_map directly before calling guess_type(), > and decide how quickly we can make the change. Are you

[issue35283] "threading._DummyThread" redefines "is_alive" but forgets "isAlive"

Dong-hee Na added the comment: @asvetlov I agree with asvetlov :) -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue20582] socket.getnameinfo() does not document flags

Danish Prakash added the comment: I would like to work on this if nobody else has. -- nosy: +danishprakash ___ Python tracker ___

[issue34812] [EASY] support.args_from_interpreter_flags() doesn't inherit -I (isolated) flag

Danish Prakash added the comment: Sorry for bumping this thread but Victor, could you please share your inputs on this if you have the time for it, thanks. -- ___ Python tracker

[issue35134] Add a new Include/unstable/ subdirectory for the "unstable" API

Jeremy Kloth added the comment: As a heavy user of the non-limited Python C API, I would like to offer my suggestions for consideration. (I'm not allowed to post in discourse) First off, to me, 'unstable' comes off quite negative, i.e. risky or erratic. Brett's suggestion of 'broad' is,

[issue31823] Opaque default value for close_fds argument in Popen.__init__

Danish Prakash added the comment: I'd like to work on this. I get that the 3.7+ doc still has the irrelevant change from 3.6 which needs to be removed but I'm not sure what's wrong with the 3.6 doc. > The signature is indeed awkward for 3.6, -- nosy: +danishprakash

[issue31823] Opaque default value for close_fds argument in Popen.__init__

Tal Einat added the comment: Danish, see Martin's previous comment (msg314413): "... the signature at [the 3.6 docs] should not show close_fds=True, because that is not necessarily the default on Windows." -- ___ Python tracker

[issue35134] Add a new Include/unstable/ subdirectory for the "unstable" API

STINNER Victor added the comment: Another proposal: Include\impl\ as in "implementation details". -- ___ Python tracker ___ ___

[issue35134] Add a new Include/unstable/ subdirectory for the "unstable" API

STINNER Victor added the comment: I created a poll on discuss.python.org for the name of the new subdirectory :-) https://discuss.python.org/t/poll-what-is-your-favorite-name-for-the-new-include-subdirectory/477 -- ___ Python tracker

[issue30951] Documentation error in inspect module

Change by Utkarsh Gupta : -- nosy: +utkarsh2102 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35297] untokenize documentation is not correct

Change by Zsolt Cserna : -- versions: +Python 3.6 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35297] untokenize documentation is not correct

New submission from Zsolt Cserna : untokenize documentation (https://docs.python.org/3/library/tokenize.html#tokenize.untokenize) states the following: """ Converts tokens back into Python source code. The iterable must return sequences with at least two elements, the token type and the

[issue35134] Add a new Include/unstable/ subdirectory for the "unstable" API

STINNER Victor added the comment: Brett: > The "unstable" name bugs me as it suggests we might change it without notice > which isn't true at all. It's more a limited versus broad API. So maybe > rename the directory "broad"? Brett: Nick proposed "Include\cpython", do you prefer this name?

[issue35035] Documentation for email.utils is named email.util.rst

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

[issue35083] Fix documentation for __instancecheck__

Julien Palard added the comment: Currently [1] there's no concensus about: - Is this a documentation issue and we should document the optimisation? - Is the optimisation over-zealeous? [1]: https://mail.python.org/pipermail/python-ideas/2018-October/054342.html -- nosy: +mdk

[issue35035] Documentation for email.utils is named email.util.rst

Change by Julien Palard : -- pull_requests: +9920 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue30951] Documentation error in inspect module

Change by Utkarsh Gupta : -- keywords: +patch pull_requests: +9921 stage: -> patch review ___ Python tracker ___ ___

[issue35035] Documentation for email.utils is named email.util.rst

miss-islington added the comment: New changeset daa34b84e9f6680a4012d5138068236ccdd2d1bd by Miss Islington (bot) (Julien Palard) in branch '2.7': [2.7] bpo-35035: Rename email.utils documentation to email.utils.rst (GH-10023) (GH-10667)

[issue33416] Add endline and endcolumn to every AST node

Ivan Levkivskyi added the comment: issue22616 is a bit different (proposing line/column ranges instead of just endline/endcolumn). I am happy to close this one in favor of issue22616 if we agree that we will go with endline/endcolumn. I can't guarantee, but likely I will work on this during

[issue35181] Doc: Namespace Packages: Inconsistent documentation of __loader__ being None

Change by Géry : -- nosy: +eric.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue32305] Namespace packages have inconsistent __file__ and __spec__.origin

Géry added the comment: @barry You gave 2 reasons for changing __spec__.origin and __file__ for namespace packages. Your 1st reason: > I don't particularly like that its origin is "namespace". That's an odd > special case that's unhelpful to test against (what if you import a >

[issue35298] Segfault in _PyObject_GenericGetAttrWithDict

New submission from gilado : Running pulseeffects, it crashes occasionally. I have yet to find a cause, it just happens. I decided to run it under gdb to catch the crash. It worked for a few days before crashing. $ GDK_DPI_SCALE=0.6 gdb -args /usr/bin/python3 /usr/bin/pulseeffects gdb:

[issue33211] lineno and col_offset are wrong on function definitions with decorators

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

[issue35059] Convert Py_INCREF() and PyObject_INIT() to inlined functions

Change by STINNER Victor : -- pull_requests: +9922 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue29877] compileall hangs when accessing urandom even if number of workers is 1

INADA Naoki added the comment: I am not sure PR 4856 is enhancement or bugfix. But I think it's worth enough to backport to 3.6 and 3.7. It caused a real UX problem. -- nosy: +inada.naoki ___ Python tracker

[issue33211] lineno and col_offset are wrong on function definitions with decorators

Ethan Smith added the comment: This has been fixed, so the issue can be closed I believe. FWIW I didn't see anything useful to salvage from my PR that wasn't already tested by your tests Serhiy. -- pull_requests: +9923 ___ Python tracker

[issue35299] LGHT0091: Duplicate symbol 'File:include_pyconfig.h' found

New submission from Jorge Ramos : Build of Python 3.6.7 fails with error "LGHT0091: Duplicate symbol 'File:include_pyconfig.h' found" I am using Windows 10 64bit. Steps to reproduce this error: 1) Install Visual Studio 2017 (With the python development and native dev tools) (I have also

[issue35286] wrong result for difflib.SequenceMatcher

Change by Raymond Hettinger : -- assignee: -> tim.peters ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: