[issue31500] IDLE: Tiny font on HiDPI display

Serhiy Storchaka added the comment: If just negate the size the menu and the dialog fonts look like on a display with 72 DPI. But currently monitors rarely have such DPI. Normal displays have about 100 DPI (scaling factor about 1.33). If we want to keep font sizes on such displays we should

[issue31351] ensurepip discards pip's return code which leads to broken venvs

Martin Vielsmaier added the comment: I guess this is also the root cause for the problem I reported on virtualenv: https://github.com/pypa/virtualenv/issues/1074 -- nosy: +Martin Vielsmaier ___ Python tracker

[issue31506] Improve the error message logic for object_new & object_init

Nick Coghlan added the comment: I filed issue 31527 as a follow-up issue to see whether or not it might be possible to amend the way these custom errors are generated to benefit from the work that has gone into improving the error responses from PyArg_ParseTupleAndKeywords. --

[issue31527] Report details of excess arguments in object_new & object_init

Nick Coghlan added the comment: Adding a dependency on issue 31506, as this shouldn't be tackled until those simpler amendments are resolved. -- dependencies: +Improve the error message logic for object_new & object_init ___ Python tracker

[issue31527] Report details of excess arguments in object_new & object_init

New submission from Nick Coghlan: object_new and object_init currently use their own argument checking logic, and hence haven't benefited from the error reporting enhancements in PyArg_ParseTupleAndKeywords Compare: >>> str(1, 2, 3, 4, 5, x=1) Traceback (most recent call last): File "",

[issue31526] Allow setting timestamp in gzip-compressed tarfiles

New submission from Jack Lloyd: Context: I have a script which checks out a software release (tagged git revision) and builds an archive to distribute to end users. One goal of this script is that the archive is reproducible, ie if the script is run twice (at different times, on different

[issue31517] MainThread association logic is fragile

Nick Coghlan added the comment: One place where this came up recently is in working out precisely how a Python-level subinterpreter API will interact with the threading API: https://mail.python.org/pipermail/python-dev/2017-September/149566.html That said, I do agree with Tim that the status

[issue31525] require sqlite3_prepare_v2

Changes by Benjamin Peterson : -- keywords: +patch pull_requests: +3655 stage: -> patch review ___ Python tracker ___

[issue31525] require sqlite3_prepare_v2

Benjamin Peterson added the comment: ermm, yes, I guess I was looking at an old version of the code. -- title: switch to sqlite3_prepare_v2 -> require sqlite3_prepare_v2 ___ Python tracker

[issue31506] Improve the error message logic for object_new & object_init

Nick Coghlan added the comment: Reopening, as I was a little hasty with the merge button: the merged PR *also* changed the `__init__` error message to drop the method name, but I don't think that's what we want. I'm also wondering if we should change the up-call case to *always* report the

[issue31506] Improve the error message logic for object_new & object_init

Changes by Nick Coghlan : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue31506] Improve the error message logic for object_new & object_init

Nick Coghlan added the comment: New changeset a6c0c0695614177c8b6e1840465375eefcfee586 by Nick Coghlan (Serhiy Storchaka) in branch 'master': bpo-31506: Improve the error message logic for object.__new__ and object.__init__. (GH-3650)

[issue31525] switch to sqlite3_prepare_v2

Berker Peksag added the comment: We already use sqlite3_prepare_v2 if it's available: https://github.com/python/cpython/blob/master/Modules/_sqlite/util.h#L43 Do you want to use sqlite3_prepare_v2() unconditionally and drop support for older SQLite versions? -- nosy: +berker.peksag

[issue31498] Default values for zero in time.strftime()

Denis Osipov added the comment: Thank you for your answers. It's what I want to know. It looks like I shouldn't try to fix (to break) something that works well enough. If nobody minds I'll close the issue with not a bug resolution. -- ___ Python

[issue31517] MainThread association logic is fragile

Tim Peters added the comment: Is there a problem here? I haven't heard of anyone even wondering about this before. threading.py worries about Threads created _by_ threading.py, plus the magical (from its point of view) thread that first imports threading.py. Users mix in `_thread` threads,

[issue31524] mailbox._mboxMMDF.get_message throws away From envelope

R. David Murray added the comment: It just needs to call set_unixfrom as well as set_from. I don't know why the MMDFMessage tracks it separately, but I'm sure the author had a reason that seemed good at the time :) -- ___ Python tracker

[issue31525] switch to sqlite3_prepare_v2

New submission from Benjamin Peterson: sqlite has had the sqlite3_prepare_v2 API for more than 10 years now. The sqlite module should switch to using it, which will let us delete some code for automatically recompiling statements. -- components: Extension Modules messages: 302581

[issue31500] IDLE: Tiny font on HiDPI display

Terry J. Reedy added the comment: I mean ' if scaling >= 1.2:' in run.fix_scaling. It would also be interesting to instead replace the last line, "font['size'] = -size" with "font['size'] = 9" (or 8 or 10) and see how close the dialog is to what is was before. --

[issue31500] IDLE: Tiny font on HiDPI display

Terry J. Reedy added the comment: It appears that the cutoff of 1.2 in the patch is too low. Try raising it to 1.4 and you should see the dialog normal. -- ___ Python tracker

[issue31524] mailbox._mboxMMDF.get_message throws away From envelope

bpoaugust added the comment: I believe that setting the file back to the start is probably the best solution. The message as provided by e.g. postfix will include the From header and the parser is able to deal with that successfully, so I'm not sure why the mbox reader removes it before

[issue31524] mailbox._mboxMMDF.get_message throws away From envelope

bpoaugust added the comment: It is not saving the unix from line. #!/usr/bin/env python3 with open("test.mbox",'w') as f: f.write("From sender@invalid Thu Nov 17 00:49:30 2016\n") f.write("Subject: Test\n") f.write("\n") f.write("\n") import mailbox messages =

[issue31508] Running test_ttk_guionly logs "test_widgets.py:1562: UserWarning: Deprecated API of Treeview.selection() should be removed" warnings

Cheryl Sabella added the comment: Serhiy, In tkinter __init__.py, there's messages on trace_variable and other trace functions about adding a deprecation warning. I didn't know if you intended to make those changes as well. -- nosy: +csabella ___

[issue31524] mailbox._mboxMMDF.get_message throws away From envelope

R. David Murray added the comment: It looks like it is saving it (the set_from line). Do you have a test that proves otherwise? -- ___ Python tracker

[issue31500] IDLE: Tiny font on HiDPI display

Cheryl Sabella added the comment: configdialog looks better now, but the fonts are still huge. The configdialog is almost bigger than the shell when it opens. -- Added file: https://bugs.python.org/file47155/configkey_2.png ___ Python tracker

[issue31500] IDLE: Tiny font on HiDPI display

Cheryl Sabella added the comment: >>> import tkinter as tk >>> root = tk.Tk() >>> print(float(root.tk.call('tk', 'scaling'))) 1. -- ___ Python tracker

[issue31500] IDLE: Tiny font on HiDPI display

Terry J. Reedy added the comment: New changeset 97be14996b247b853ead77fb255d7029e3cf3dc9 by Terry Jan Reedy (Miss Islington (bot)) in branch '3.6': [3.6] bpo-31500: Removed fixed size of IDLE config dialog. (GH-3664) (#3665)

[issue31522] _mboxMMDF.get_string() fails to pass param to get_bytes()

bpoaugust added the comment: Ignore msg302569 - that was supposed to be a new issue. -- ___ Python tracker ___

[issue31524] mailbox._mboxMMDF.get_message throws away From envelope

New submission from bpoaugust: https://github.com/python/cpython/blob/master/Lib/mailbox.py#L778 The code here reads the first line, but fails to save it as the unixfrom line. Alternatively perhaps it should reset the file back to the start so the message factory has sight of the envelope.

[issue31522] _mboxMMDF.get_string() fails to pass param to get_bytes()

Changes by bpoaugust : -- title: mailbox._mboxMMDF.get_message throws away From envelope -> _mboxMMDF.get_string() fails to pass param to get_bytes() ___ Python tracker

[issue31522] mailbox._mboxMMDF.get_message throws away From envelope

bpoaugust added the comment: https://github.com/python/cpython/blob/master/Lib/mailbox.py#L778 The code here reads the first line, but fails to save it as the unixfrom line. Alternatively perhaps it should reset the file back to the start so the message factory has sight of the envelope. The

[issue31523] Windows build file fixes

Steve Dower added the comment: Also: * build releases to versioned subdirectories of Py_IntDir when it is set -- ___ Python tracker ___

[issue31523] Windows build file fixes

New submission from Steve Dower: This is basically a note to myself to go and fix these things when I have time (before 3.7a2): * split upload steps so we can fail on real failures * fail immediately if gpg2 step fails * purge and retry if download fails -- assignee: steve.dower

[issue31500] IDLE: Tiny font on HiDPI display

Changes by Roundup Robot : -- pull_requests: +3654 ___ Python tracker ___

[issue31500] IDLE: Tiny font on HiDPI display

Terry J. Reedy added the comment: New changeset d6e2f26f3f7c62a4ddbf668027d3ba27cb0e1eca by Terry Jan Reedy in branch 'master': bpo-31500: Removed fixed size of IDLE config dialog. (#3664) https://github.com/python/cpython/commit/d6e2f26f3f7c62a4ddbf668027d3ba27cb0e1eca --

[issue31501] Operator precedence description for arithmetic operators

Mariatta Wijaya added the comment: New changeset e2593aa673c0347a74c4896a519e3b8cb7b55eb4 by Mariatta (Miss Islington (bot)) in branch '3.6': bpo-31501: Operator precedence description for arithmetic operators (GH-3633) (GH-3638)

[issue31522] _mboxMMDF.get_string() fails to pass param to get_bytes()

New submission from bpoaugust: See: https://github.com/python/cpython/blob/master/Lib/mailbox.py#L787 The code should be self.get_bytes(key, from_)).as_string(unixfrom=from_) -- components: email messages: 302564 nosy: barry, bpoaugust, r.david.murray priority: normal severity: normal

[issue31500] IDLE: Tiny font on HiDPI display

Changes by Terry J. Reedy : -- pull_requests: +3653 ___ Python tracker ___ ___

[issue31500] IDLE: Tiny font on HiDPI display

Terry J. Reedy added the comment: Cheryl, what do you get with import tkinter as tk root = tk.Tk() print(float(root.tk.call('tk', 'scaling'))) If it is less than 1.2, then Serhiy's revised patch should leave config dialog as it should be. -- ___

[issue26673] Tkinter error when opening IDLE configuration menu (Tcl/Tk 8.6)

Changes by Serhiy Storchaka : -- pull_requests: +3652 ___ Python tracker ___

[issue31516] current_thread() becomes "dummy" thread during shutdown

Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___

[issue31518] ftplib, urllib2, poplib, httplib, urllib2_localnet use ssl.PROTOCOL_TLSv1 unconditionally

Christian Heimes added the comment: PR 3660 and PR 3661 address most of the failing tests. The two failures in msg302531 are discussed in issue #31453. -- ___ Python tracker

[issue31453] Debian Sid/Buster: Cannot enable TLS 1.0/1.1 with PROTOCOL_TLS

Christian Heimes added the comment: PR 3662 undos Debian's patching of OpenSSL. I'm not keen to undo a security improvement. However Debian is breaking backwards compatibility. For Python 3.7 we could consider to disable TLS 1.0 and TLS 1.1 for PROTOCOL_TLS_SERVER and PROTOCOL_TLS_CLIENT.

[issue31507] email.utils.parseaddr has no docstring

R. David Murray added the comment: New changeset 9e7b9b21fe45f7d93eaf9382fedfa18247d0d2b2 by R. David Murray (Rohit Balasubramanian) in branch 'master': bpo-31507 Add docstring to parseaddr function in email.utils.parseaddr (gh-3647)

[issue31415] Add -X option to show import time

Serhiy Storchaka added the comment: If this proposition be accepted I would want to see not only cumulated times, but also pure times, without time of nested imports. I guess this feature doesn't work correctly with threading. -- nosy: +serhiy.storchaka

[issue31453] Debian Sid/Buster: Cannot enable TLS 1.0/1.1 with PROTOCOL_TLS

Changes by Christian Heimes : -- keywords: +patch pull_requests: +3651 stage: -> patch review ___ Python tracker ___

[issue31518] ftplib, urllib2, poplib, httplib, urllib2_localnet use ssl.PROTOCOL_TLSv1 unconditionally

Matthias Klose added the comment: Christian, I assume you'd like to see a test which can be done at *runtime*, not *buildtime*. Assuming you have that openssl upstream patch available in your build dependency, would that help with the detection? If yes, I'll talk to Debian's and Ubuntu's

[issue31518] ftplib, urllib2, poplib, httplib, urllib2_localnet use ssl.PROTOCOL_TLSv1 unconditionally

Changes by Christian Heimes : -- pull_requests: +3650 ___ Python tracker ___ ___

[issue31518] ftplib, urllib2, poplib, httplib, urllib2_localnet use ssl.PROTOCOL_TLSv1 unconditionally

Changes by Christian Heimes : -- keywords: +patch pull_requests: +3649 stage: -> patch review ___ Python tracker ___

[issue31415] Add -X option to show import time

INADA Naoki added the comment: It means μs (micro seconds), in ASCII. On 2017年9月20日(水) 3:35 Brett Cannon wrote: > > Brett Cannon added the comment: > > What does the "[us]" mean? > > -- > nosy: +brett.cannon > > ___ > Python

[issue31415] Add -X option to show import time

Brett Cannon added the comment: What does the "[us]" mean? -- nosy: +brett.cannon ___ Python tracker ___ ___

[issue31521] segfault in PyBytes_AsString

Tim Smith added the comment: I forgot to mention, this is Arch Linux python package: Version : 3.6.2-1 Packager: Felix Yan Build Date : Wed 19 Jul 2017 01:54:34 PM MDT I had the files on a vfat filesystem, but copied them to ext4 with the exact

[issue31498] Default values for zero in time.strftime()

R. David Murray added the comment: Yes, I think we can "fix" some things. I don't know if this falls into the class of things we should fix. I'll leave that decision to people with more experience with time stuff. -- ___ Python tracker

[issue31521] segfault in PyBytes_AsString

New submission from Tim Smith: $ python -V Python 3.6.2 This crash appears to be specific to having files with some ill-encoded filenames. After renaming the offending files to remove the non-ASCII characters, the process could complete without crashing. $ beet import /share/Music/Berliner\

[issue31482] random.seed() doesn't work with bytes and version=1

Mariatta Wijaya added the comment: New changeset c6ce8fba07ea6798eac46ab2808167afecd4d90b by Mariatta (Miss Islington (bot)) in branch '3.6': [3.6] bpo-31482: Missing bytes support for random.seed() version 1 (GH-3614) (GH-3659)

[issue31498] Default values for zero in time.strftime()

Denis Osipov added the comment: Actually now Python time.strftime not always returns the same value as C strftime with the same arguments, because timemodule make some refining of raw argument values to avoid errors. -- ___ Python tracker

[issue31355] Remove Travis CI macOS job: rely on buildbots

Brett Cannon added the comment: Should this be closed? -- nosy: +brett.cannon ___ Python tracker ___ ___

[issue31482] random.seed() doesn't work with bytes and version=1

Serhiy Storchaka added the comment: Ah, now I understand what happened. Thanks Mariatta. -- ___ Python tracker ___

[issue31498] Default values for zero in time.strftime()

Denis Osipov added the comment: Yes, C strftime returns the same. Inside of Python time.strftime() in Windows we give struct tm with inconsistent attributes (year, mon, mday and wday,yday) as argument for C strftime(). Before it timemodule does a lot of work to parse arguments of

[issue31482] random.seed() doesn't work with bytes and version=1

Mariatta Wijaya added the comment: Serhiy, it can't be re-opened since miss-islington deleted the branch already. -- ___ Python tracker ___

[issue31479] Always reset the signal alarm in tests

STINNER Victor added the comment: Serhiy: "Maybe add a context manager? Some pattern is repeated multiple times." As I wrote on the PR, I'm not sure because not all the code look the same. Please propose a PR if you want, I can review it! -- resolution: -> fixed stage: patch review

[issue31479] Always reset the signal alarm in tests

STINNER Victor added the comment: While the fix is nice to have to handle corner cases, I'm not sure that it's really useful to backport the change to Python 2.7 and 3.6. So I close the issue. -- ___ Python tracker

[issue31482] random.seed() doesn't work with bytes and version=1

Serhiy Storchaka added the comment: If PR 3629 was closed by mistake it could be just reopened, isn't? -- ___ Python tracker ___

[issue31479] Always reset the signal alarm in tests

STINNER Victor added the comment: New changeset 9abee722d448c1c00c7d4e11ce242ec7b13e5c49 by Victor Stinner in branch 'master': bpo-31479: Always reset the signal alarm in tests (#3588) https://github.com/python/cpython/commit/9abee722d448c1c00c7d4e11ce242ec7b13e5c49 --

[issue13224] Change str(x) to return only the qualname for some types

Guido van Rossum added the comment: And thanks for working it through! It was a valuable exercise. -- ___ Python tracker ___

[issue31482] random.seed() doesn't work with bytes and version=1

Mariatta Wijaya added the comment: Hi Raymond, Somehow the backport PR https://github.com/python/cpython/pull/3629 was closed before instead of merged. To retrigger the backport, we can re-apply the "needs backport to 3.6" label on the original PR (3614). I will do this now :) --

[issue31520] ResourceWarning: unclosed warning

Changes by STINNER Victor : -- nosy: +martin.panter ___ Python tracker ___ ___

[issue31482] random.seed() doesn't work with bytes and version=1

Mariatta Wijaya added the comment: Backport PR has been created. Once the CI checks are done, we can squash and merge it. -- ___ Python tracker ___

[issue31520] ResourceWarning: unclosed warning

New submission from STINNER Victor: _socket.socket object destructor emits a ResourceWarning if the socket is not closed. The problem is this warning: build/Lib/contextlib.py:60: ResourceWarning: unclosed self.gen = func(*args, **kwds) The message says "unclosed" and "closed" in the same

[issue31482] random.seed() doesn't work with bytes and version=1

Changes by Roundup Robot : -- pull_requests: +3648 stage: resolved -> patch review ___ Python tracker ___

[issue2504] Add gettext.pgettext() and variants support

Changes by Éric Araujo : -- keywords: +needs review versions: +Python 3.7 -Python 3.5 ___ Python tracker ___

[issue31482] random.seed() doesn't work with bytes and version=1

Serhiy Storchaka added the comment: What is wrong with PR 3629? -- ___ Python tracker ___ ___

[issue31510] test_many_processes() of test_multiprocessing_spawn failed on x86-64 Sierra 3.x

STINNER Victor added the comment: I failed to reproduce the bug on Linux. -- ___ Python tracker ___ ___

[issue13224] Change str(x) to return only the qualname for some types

Éric Araujo added the comment: Yeah, it was interesting to explore but there are significant drawbacks and not enough benefit. Thanks for the guidance all! -- resolution: -> rejected stage: patch review -> resolved status: open -> closed ___

[issue31482] random.seed() doesn't work with bytes and version=1

Raymond Hettinger added the comment: Mariatta, what is the procedure for completing the backport? I can see the miss-islington bot made a commit but it didn't take in the 3.6 branch. -- assignee: rhettinger -> Mariatta nosy: +Mariatta ___ Python

[issue13224] Change str(x) to return only the qualname for some types

Guido van Rossum added the comment: Given Nick's feedback (and imagining what this would do to some codebases I know) I think this idea is dead, sadly. A helper function just doesn't give enough value, so let's not pursue that (it's easy to write the helper you want, it's hard to agree on what

[issue31519] Negative number raised to even power is negative (-1 ** even = negative)

R. David Murray added the comment: It's a FAQ, but it was faster for me to just cut and paste than it was to look up the FAQ link :) -- ___ Python tracker

[issue31519] Negative number raised to even power is negative (-1 ** even = negative)

Bob Hunkins added the comment: Thanks. Stupid of me. Appreciate the correction. -- ___ Python tracker ___

[issue31518] ftplib, urllib2, poplib, httplib, urllib2_localnet use ssl.PROTOCOL_TLSv1 unconditionally

Christian Heimes added the comment: Two tests are failing in 3.7 branch: == ERROR: test_PROTOCOL_TLS (test.test_ssl.ThreadedTests) Connecting to an SSLv23 server with various client options

[issue31519] Negative number raised to even power is negative (-1 ** even = negative)

R. David Murray added the comment: You are being tripped up by operator precedence: >>> -1**2 -1 >>> (-1)**2 1 -- nosy: +r.david.murray resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker

[issue31519] Negative number raised to even power is negative (-1 ** even = negative)

New submission from Bob Hunkins: Hello, I'm only a novice with Python, so please take it easy on me if I have transgressed. I am using Python 3.6.2 on a win10 64 bit machine, and entered this: >>> a= [-1 ** x for x in range(1,10)] >>> print(a) [-1, -1, -1, -1, -1, -1, -1, -1, -1] which is not

[issue31293] crashes in multiply_float_timedelta() and in truedivide_timedelta_float()

Changes by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.6 ___ Python tracker

[issue31293] crashes in multiply_float_timedelta() and in truedivide_timedelta_float()

Serhiy Storchaka added the comment: New changeset f37dd11f0d4832c15d49c2ddc83d533ddaa36e74 by Serhiy Storchaka (Miss Islington (bot)) in branch '3.6': [3.6] bpo-31293: Fix crashes in truediv and mul of a timedelta by a float with a bad as_integer_ratio() method. (GH-3227) (#3654)

[issue31518] ftplib, urllib2, poplib, httplib, urllib2_localnet use ssl.PROTOCOL_TLSv1 unconditionally

Christian Heimes added the comment: 3.7 does no longer use PROTOCOL_TLSv1 except for test_ssl.py, see #31346 By the way Debian Sid/Buster broke support for SSL and TLS < 1.2. see #31453. There is no way to enable the protocols from Python. -- versions: -Python 3.7

[issue31518] ftplib, urllib2, poplib, httplib, urllib2_localnet use ssl.PROTOCOL_TLSv1 unconditionally

Matthias Klose added the comment: failing tests: https://ci.debian.net/data/packages/unstable/amd64/p/python3.6/latest-autopkgtest/log.gz -- ___ Python tracker

[issue31518] ftplib, urllib2, poplib, httplib, urllib2_localnet use ssl.PROTOCOL_TLSv1 unconditionally

New submission from Matthias Klose: Debian's OpenSSL now disables TLS 1.0 and 1.1, letting some of the python tests fail. Please make them use a newer protocol version, or make the use of the older versions conditional. -- assignee: christian.heimes components: SSL messages: 302524

[issue31498] Default values for zero in time.strftime()

R. David Murray added the comment: Well, the first question that needs to be answered is: if you call the C strftime with the same arguments, what result do you get? Because if it is the C strftime doing this, then it is not a bug in Python, whether it is correct behavior or not. --

[issue31492] assertion failures in case a module has a bad __name__ attribute

Changes by Serhiy Storchaka : -- stage: patch review -> backport needed versions: +Python 3.6 ___ Python tracker ___

[issue31517] MainThread association logic is fragile

Antoine Pitrou added the comment: Fixing this will require thinking out what the "main thread" of an interpreter really is. Is it the thread in which PyInterpreterState_New() is called? (note this is not the same thing as the "main thread" in the signal module, which is process-global)

[issue6986] _json crash on scanner/encoder initialization error

STINNER Victor added the comment: Oh wow, this issue was fixed 8 years ago and it's now closed! Please open a write issue, or maybe even propose directly a PR? (If you do, I will review it.) -- ___ Python tracker

[issue31517] MainThread association logic is fragile

Changes by Antoine Pitrou : -- nosy: +asvetlov, tim.peters ___ Python tracker ___ ___

[issue31517] MainThread association logic is fragile

New submission from Antoine Pitrou: The threading main_thread() instance is associated to the thread that first imports the threading module. In usual circumstances, this will indeed be the interpreter's main thread. However, it is not always the case. See attached reproducer. $ ./python

[issue31293] crashes in multiply_float_timedelta() and in truedivide_timedelta_float()

Serhiy Storchaka added the comment: New changeset 865e4b4f630e2ae91e61239258abb58b488f1d65 by Serhiy Storchaka (Oren Milman) in branch 'master': bpo-31293: Fix crashes in truediv and mul of a timedelta by a float with a bad as_integer_ratio() method. (#3227)

[issue31293] crashes in multiply_float_timedelta() and in truedivide_timedelta_float()

Changes by Roundup Robot : -- keywords: +patch pull_requests: +3647 stage: needs patch -> patch review ___ Python tracker

[issue31315] assertion failure in imp.create_dynamic(), when spec.name is not a string

Serhiy Storchaka added the comment: Thank you Oren! -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue31315] assertion failure in imp.create_dynamic(), when spec.name is not a string

Changes by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: -Python 2.7 ___ Python tracker

[issue31315] assertion failure in imp.create_dynamic(), when spec.name is not a string

Serhiy Storchaka added the comment: New changeset 99a51d4e5b154a7b8d971090fecc1e34769a3ca1 by Serhiy Storchaka (Miss Islington (bot)) in branch '3.6': [3.6] bpo-31315: Fix an assertion failure in imp.create_dynamic(), when spec.name is not a string. (GH-3257) (#3653)

[issue31516] current_thread() becomes "dummy" thread during shutdown

Antoine Pitrou added the comment: The main thread being marked "stopped" at shutdown might be an obscure feature (as hinted in the comments for threading._shutdown()). However, current_thread() should definitely not return a separate DummyThread instance. --

[issue31315] assertion failure in imp.create_dynamic(), when spec.name is not a string

Changes by Roundup Robot : -- keywords: +patch pull_requests: +3646 ___ Python tracker ___

[issue31315] assertion failure in imp.create_dynamic(), when spec.name is not a string

Serhiy Storchaka added the comment: New changeset 9974e1bcf3d0cec9b38b39b39b7ec8a1ebd9ef54 by Serhiy Storchaka (Oren Milman) in branch 'master': bpo-31315: Fix an assertion failure in imp.create_dynamic(), when spec.name is not a string. (#3257)

[issue31516] current_thread() becomes "dummy" thread during shutdown

New submission from Antoine Pitrou: Attaching reproducer. During interpreter shutdown, threading.main_thread() gets marked "stopped" (while it's obviously still running), while threading.current_thread() returns a DummyThread instance with the same ident as the main thread. $ ./python

  1   2   >