[issue33455] test.test_posix.TestPosixSpawn::test_specify_environment fails with custom LD_LIBRARY_PATH

Serhiy Storchaka added the comment: New changeset 7ec8f28656ea9d84048e9b5655375c6a74a59f53 by Serhiy Storchaka (Miro Hrončok) in branch 'master': bpo-33455: Pass os.environ in test_posix::test_specify_environment. (GH-6753)

[issue33455] test.test_posix.TestPosixSpawn::test_specify_environment fails with custom LD_LIBRARY_PATH

Change by miss-islington : -- pull_requests: +6451 ___ Python tracker ___

[issue15443] datetime module has no support for nanoseconds

Change by Giampaolo Rodola' : -- nosy: +giampaolo.rodola ___ Python tracker ___ ___

[issue33463] Can namedtuple._asdict return a regular dict instead of OrderedDict?

Change by Serhiy Storchaka : -- assignee: -> rhettinger nosy: +rhettinger ___ Python tracker ___

[issue33462] reversible dict

Change by Raymond Hettinger : -- versions: +Python 3.8 ___ Python tracker ___

[issue33463] Can namedtuple._asdict return a regular dict instead of OrderedDict?

Change by Raymond Hettinger : -- versions: -Python 3.7 ___ Python tracker ___

[issue33463] Can namedtuple._asdict return a regular dict instead of OrderedDict?

New submission from Michael Selik : Since the basic dict is now keeping insertion order, can we switch namedtuple._asdict to return a basic dict? Other than OrderedDict.move_to_end and the repr, I believe there is no compatibility issue. -- messages: 316387 nosy: selik

[issue33462] reversible dict

New submission from Michael Selik : Now that dicts are tracking insertion order, they can be made reversible via the built-in reversed, just like OrderedDict. -- messages: 316386 nosy: selik priority: normal severity: normal status: open title: reversible dict type:

[issue31817] Compilation Error with Python 3.6.1/3.6.3 with Tkinter

dplusplus added the comment: I am trying to build Python 3.6.5 from source, with Tcl 8.6.8 and Tk 8.6.8, and I get the same issue (Building on Ubuntu 18.04, tried with GCC 7.3 and 8.1 with same results). Run 'readelf -d` on

[issue29204] Add code deprecations in ElementTree

Change by Matthias Bussonnier : -- pull_requests: +6450 ___ Python tracker ___

[issue33461] json.loads(encoding=) does not emit deprecation warning.

Change by Matthias Bussonnier : -- keywords: +patch pull_requests: +6449 stage: -> patch review ___ Python tracker ___

[issue33461] json.loads(encoding=) does not emit deprecation warning.

New submission from Matthias Bussonnier : The `encoding` keyword of json.loads is ignored and deprecated. AFAICT this is since Python 3.1. Passing a value for encoding does not emit a deprecation warning. -- messages: 316384 nosy: mbussonn priority:

[issue33351] Support compiling with clang-cl on Windows

Change by Ethan Smith : -- keywords: +patch pull_requests: +6448 stage: test needed -> patch review ___ Python tracker ___

[issue33459] Define "tuple display" in the docs

Cheryl Sabella added the comment: Actually, 'tuple display' is in the index under 'display' and links to the last paragraph in 6.2.3. However, except for the index name, that paragraph doesn't use the phrase 'tuple display'. So it gives the definition without saying what

[issue33459] Define "tuple display" in the docs

R. David Murray added the comment: Nope, a tuple display is not equal to a parenthesized list. For example, in: x = 1, 2, 3 1, 2, 3 is a tuple display. The parenthesis are optional in that case (in the general case it is the comma that makes the tuple, not the

[issue33460] ... used to indicate many different things in chapter 3, some are confusing

New submission from Lew Kurtz : https://docs.python.org/3/tutorial/introduction.html uses ... to mean 5 or 6 different things. Since ... is continuation prompt, some of these other uses on that page are confusing - at least they were to this newbie. The most confusing are

[issue33459] Fix "tuple display" mention in Expressions

Change by Andrés Delfino : -- keywords: +patch pull_requests: +6447 stage: -> patch review ___ Python tracker ___

[issue33459] Fix "tuple display" mention in Expressions

New submission from Andrés Delfino : Expressions mentions "tuple displays" in 6.16 (Operator precedence). AFAIK, there ano "tuple displays". Expressions mentions list, dict, and set displays, and then talks about generator expressions. I guess "parenthesized expressions"

[issue31670] Associate .wasm with application/wasm

Brad Nelson added the comment: We have a provisional registration for application/wasm now with IANA: https://www.iana.org/assignments/provisional-standard-media-types/provisional-standard-media-types.xhtml This is also shipping in Firefox and Chrome. Would it be

[issue33449] Documentation for email.charset confusing about the location of constants

R. David Murray added the comment: Ah, I see. Yes, those strings are actually hardcoded in the documentation source instead of being references. You are correct, they should be fixed. Note, however, that Charset is part of the legacy API and isn't actually used if

[issue13044] pdb throws AttributeError at end of debugging session

Xavier de Gaye added the comment: See also issue 33458 that deals with the same problem when pdb is run as 'python -m pdb some_main.py' instead of by inserting a breakpoint with 'pdb.set_trace()'. -- ___ Python tracker

[issue33458] pdb.run() does not trace destructors of __main__

Xavier de Gaye added the comment: The following patch fixes the problem when applied applied on top of PR 6730: diff --git a/Lib/bdb.py b/Lib/bdb.py index c6a10359ac..07231ec588 100644 --- a/Lib/bdb.py +++ b/Lib/bdb.py @@ -582,7 +582,7 @@ class Bdb: cmd =

[issue33458] pdb.run() does not trace destructors of __main__

New submission from Xavier de Gaye : This issue is a companion to issue 13044. Running with Python 3.6.5 the following code fails with NameError: 1 class C: 2 def __del__(self): 3 print('deleted') 4 5 c = C() 6 x = 1 $ python -m pdb bar.py > ./bar.py(1)() ->

[issue33449] Documentation for email.charset confusing about the location of constants

Francois Labelle added the comment: Original poster here (OpenID just wouldn't work anymore). For instance: https://docs.python.org/2/library/email.charset.html Under "class email.charset.Charset" Under "header_encoding" "If the character set must be encoded before

[issue13044] pdb throws AttributeError at end of debugging session

Xavier de Gaye added the comment: Actually the segfault can be avoided by running the garbage collection before _PyState_ClearModules() in PyImport_Cleanup() and one can trace the C destructor with the attached patch global_destructors.diff applied on top of PR 6730.

[issue28556] typing.py upgrades

Change by Ivan Levkivskyi : -- pull_requests: +6446 ___ Python tracker ___ ___

[issue28556] typing.py upgrades

Change by Ivan Levkivskyi : -- pull_requests: +6445 ___ Python tracker ___ ___

[issue33012] Invalid function cast warnings with gcc 8 for METH_NOARGS

Serhiy Storchaka added the comment: I think it safer to silence this kind of warnings in 3.7 and 3.6. PR 6757 does this. -- ___ Python tracker

[issue33012] Invalid function cast warnings with gcc 8 for METH_NOARGS

Change by Serhiy Storchaka : -- pull_requests: +6444 ___ Python tracker ___ ___

[issue33413] asyncio.gather should not use special Future

Change by Ned Deily : -- components: +asyncio nosy: +asvetlov, yselivanov ___ Python tracker ___

[issue33413] asyncio.gather should not use special Future

Martin Teichmann added the comment: I looked a bit into the details, and found that bpo-30048 created the described weird behavior. There they fixed the problem that a cancel is ignored if a coroutine manages to cancel its own task and return immediately. As shown

[issue33448] Output_Typo_Error

Mark Dickinson added the comment: Marking as pending; we can't take this forward without more input from the OP. As far as I can tell, the documentation is perfectly correct here: I suspect that there was a misunderstanding somewhere along the line. -- assignee:

[issue33419] Add functools.partialclass

Nick Coghlan added the comment: Marking as closed/later to indicate that we're not going to pursue this in the near term, but it's not out of the question that we might accept a future proposal along these lines. -- resolution: -> later stage: patch review ->

[issue33457] python-config ldflags, PEP 513 and explicit linking to libpython in python extensions

New submission from dimi : The python-config outputs ldflag for explicit linking to libpyhton, which is a good idea in many use cases. However, this is inconsistent with the PEP 513 recommendation for building manylinux1 python extensions

[issue33456] site.py: by default, a virtual environment is *not* isolated from the system-level site-packages directories

Change by Lukas Waymann : -- keywords: +patch pull_requests: +6442 stage: -> patch review ___ Python tracker ___

[issue32962] test_gdb fails in debug build with `-mcet -fcf-protection -O0`

Change by Marcel Plch : -- keywords: +patch pull_requests: +6441 stage: -> patch review ___ Python tracker ___

[issue33455] test.test_posix.TestPosixSpawn::test_specify_environment fails with custom LD_LIBRARY_PATH

Change by Miro Hrončok : -- keywords: +patch pull_requests: +6440 stage: -> patch review ___ Python tracker ___

[issue33456] site.py: by default, a virtual environment is *not* isolated from the system-level site-packages directories

New submission from Lukas Waymann : PEP 405 says this: > By default, a virtual environment is entirely isolated from the system-level > site-packages directories. > > If the pyvenv.cfg file also contains a key include-system-site-packages with > a value of true (not case

[issue26701] Documentation for int constructor mentions __int__ but not __trunc__

miss-islington added the comment: New changeset 22df4187c3882c6ec67180902e1151e65b03aee0 by Miss Islington (bot) in branch '3.7': bpo-26701: Tweak the documentation for special methods in int(). (GH-6741)

[issue26701] Documentation for int constructor mentions __int__ but not __trunc__

miss-islington added the comment: New changeset 7488c79b600cd173b0ccea13adb567d078e7b835 by Miss Islington (bot) in branch '3.6': bpo-26701: Tweak the documentation for special methods in int(). (GH-6741)

[issue33449] Documentation for email.charset confusing about the location of constants

R. David Murray added the comment: Can you provide an example of where this occurs in the docs? -- nosy: +r.david.murray ___ Python tracker

[issue33453] from __future__ import annotations breaks dataclasses ClassVar and InitVar handling

Rick Teachey added the comment: > Is there any scenario where the following code would be useful... Perhaps if someone, in search of a speedup, were sort of rolling their own lighter-weight equivalent to the typing module (in order to avoid importing the full typing

[issue33455] test.test_posix.TestPosixSpawn::test_specify_environment fails with custom LD_LIBRARY_PATH

New submission from Miro Hrončok : When we build Python in Fedora, we set LD_LIBRARY_PATH environment variable so the testsuite is run against the currently built Python. However a test added in ef347535f289baad22c0601e12a36b2dcd155c3a (test_specify_environment) spawns a

[issue26701] Documentation for int constructor mentions __int__ but not __trunc__

Change by miss-islington : -- pull_requests: +6439 ___ Python tracker ___

[issue26701] Documentation for int constructor mentions __int__ but not __trunc__

Change by miss-islington : -- pull_requests: +6438 ___ Python tracker ___

[issue26701] Documentation for int constructor mentions __int__ but not __trunc__

Nick Coghlan added the comment: New changeset df00f048250b9a07195b0e3b1c5c0161fdcc9db8 by Nick Coghlan (Serhiy Storchaka) in branch 'master': bpo-26701: Tweak the documentation for special methods in int(). (GH-6741)

[issue33012] Invalid function cast warnings with gcc 8 for METH_NOARGS

Change by pmpp : -- nosy: +pmpp ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue32216] Document PEP 557 Data Classes (dataclasses module)

Ned Deily added the comment: We really need to get this done prior to 370rc1 coming up on 05-21. -- priority: deferred blocker -> release blocker ___ Python tracker

[issue33444] Memory leak/high usage on copy in different thread

whitespacer added the comment: pitrou, thanks for great diagnosing program! You are right that there is no memory leak. We have investigated this issue a little bit more - it looks real reason for large memory consuming in the end is not fragmentation, just glibc doesn't

[issue32942] Regression: test_script_helper fails

Ethan Smith added the comment: For reference this is happening with a clean checkout and build of master for me, which seems like it shouldn't be the case... -- nosy: +Ethan Smith ___ Python tracker

[issue33012] Invalid function cast warnings with gcc 8 for METH_NOARGS

Serhiy Storchaka added the comment: See also issue33454 about a real bug found thanks to these warnings. -- ___ Python tracker

[issue33012] Invalid function cast warnings with gcc 8 for METH_NOARGS

Charalampos Stratakis added the comment: Is it possible/feasible to fix that for the 3.7 and 3.6 branches as well? -- ___ Python tracker

[issue33012] Invalid function cast warnings with gcc 8 for METH_NOARGS

Serhiy Storchaka added the comment: The following PRs fix warnings in casts to PyCFunction for method conventions different from METH_NOARGS, METH_O and METH_VARARGS. PR 6748 does this for Argument Clinic generated code (all files except Tools/clinic/clinic.py are

[issue33012] Invalid function cast warnings with gcc 8 for METH_NOARGS

Change by Serhiy Storchaka : -- pull_requests: +6437 ___ Python tracker ___ ___

[issue33012] Invalid function cast warnings with gcc 8 for METH_NOARGS

Change by Serhiy Storchaka : -- pull_requests: +6436 ___ Python tracker ___ ___

[issue33454] Mismatched C function signature in _xxsubinterpreters.channel_close()

Change by Serhiy Storchaka : -- keywords: +patch pull_requests: +6435 stage: -> patch review ___ Python tracker ___

[issue33454] Mismatched C function signature in _xxsubinterpreters.channel_close()

New submission from Serhiy Storchaka : The C function that implements _xxsubinterpreters.channel_close() is defined with the signature PyObject *channel_close(PyObject *self, PyObject *args, PyObject *kwds) which corresponds the method convention METH_VARARGS

[issue33450] unexpected EPROTOTYPE returned by sendto on MAC OSX

Ronald Oussoren added the comment: The second link contains an explanation of what's going on, and that this is unexpected behaviour of the macOS kernel. I'm not sure what we could do about this, the blog post explains that this error can happen when send(2) is called

[issue20171] Derby #2: Convert 115 sites to Argument Clinic in Modules/_cursesmodule.c

Serhiy Storchaka added the comment: New changeset b00854caa080cec613496d3a5e1b0891c9ff83e6 by Serhiy Storchaka in branch 'master': bpo-20171: Convert the _curses and _curses_panel modules to Argument Clinic. (GH-4251)

[issue33453] from __future__ import annotations breaks dataclasses ClassVar and InitVar handling

Eric V. Smith added the comment: I see that https://github.com/python/typing/issues/508 is also referenced in https://github.com/python-attrs/attrs/issues/361, where it contributed to attrs using string inspection. -- ___

[issue33453] from __future__ import annotations breaks dataclasses ClassVar and InitVar handling

Eric V. Smith added the comment: See also [2]_ for a brief discussion of forward references, which makes get_type_hints() undesirable in this case. > This is why attrs went with the fast way which covers most (but not all) > bases in this case. If the annotation is a

[issue32375] Compilation warnings in getpath.c with gcc on Ubuntu / -D_FORTIFY_SOURCE=2

Serhiy Storchaka added the comment: Warnings are emitted when compile with gcc-5, gcc-6 and gcc-7, but not when compile with gcc-4.8 or gcc-8. Versions: gcc-4.8 (Ubuntu 4.8.5-4ubuntu8) 4.8.5 gcc-5 (Ubuntu 5.5.0-12ubuntu1) 5.5.0 20171010 gcc-6 (Ubuntu

[issue33015] Fix function cast warning in thread_pthread.h

Siddhesh Poyarekar added the comment: gcc8.1 throws this warning irrespective of the cast since converting function pointers may result in undefined behaviour unless it is cast back to its original type. -- ___ Python