[issue14678] Update zipimport to support importlib.invalidate_caches()

Nick Coghlan added the comment: Moving zipimporter to Python code is harder than it sounds: we don't want to break the ability to ship the standard library itself inside a zipfile. If you try to move zipimporter to pure Python, you could easily end up with a *very* ugly bootstrapping problem,

[issue14726] Lib/email/*.py use an EMPTYSTRING global instead of ''

Barry A. Warsaw added the comment: On May 05, 2012, at 01:25 AM, R. David Murray wrote: >I've always wondered why the code did that. If Barry doesn't have a good >reason for it, I'll refactor it at some point. A long time ago, Tim (IIRC) expressed an opinion that using the variable makes the

[issue14702] os.makedirs breaks under autofs directories

R. David Murray added the comment: Hynek: it doesn't seem like that would work, since legitimate EPERM errors are much more likely. -- nosy: +r.david.murray ___ Python tracker

[issue14695] Tools/parser/unparse.py is out of date.

R. David Murray added the comment: There is a test_tools file now. test_unparse could be called from it. -- nosy: +r.david.murray ___ Python tracker ___ ___

[issue14726] Lib/email/*.py use an EMPTYSTRING global instead of ''

R. David Murray added the comment: I've always wondered why the code did that. If Barry doesn't have a good reason for it, I'll refactor it at some point. -- assignee: -> r.david.murray nosy: +barry, r.david.murray type: -> performance ___ Python

[issue14726] Lib/email/*.py use an EMPTYSTRING global instead of ''

New submission from Gregory P. Smith : Lib/email/*.py are fond of using EMPTYSTRING = '' and within the code: EMPTYSTRING.join(...) instead of just writing: ''.join(...) They should just do the latter. It'll avoid a name lookup and look less silly to people reading the code. ;)

[issue14725] test_multiprocessing failure under Windows

New submission from Antoine Pitrou : There was this failure on one of the XP buildbots: Process Process-269: Traceback (most recent call last): File "D:\cygwin\home\db3l\buildarea\3.x.bolen-windows\build\lib\multiprocessing\process.py", line 258, in _bootstrap self.run() File "D:\cyg

[issue14724] kill imp.load_dynamic's third argument

New submission from Antoine Pitrou : imp.load_dynamic's third optional argument doesn't seem used in the wild, and I don't think it's correctly implemented by the current code. It would seem reasonable to kill it. -- components: Interpreter Core, Library (Lib) messages: 159971 nosy: bre

[issue14724] kill imp.load_dynamic's third argument

Brett Cannon added the comment: +1 -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/m

[issue14662] shutil.move doesn't handle ENOTSUP raised by chflags on OS X

Ned Deily added the comment: I will test and check it in next week if still open. -- ___ Python tracker ___ ___ Python-bugs-list mail

[issue13959] Re-implement parts of imp in pure Python

Roundup Robot added the comment: New changeset 22b0689346f9 by Brett Cannon in branch 'default': Issue #13959: Move module type constants to Lib/imp.py. http://hg.python.org/cpython/rev/22b0689346f9 -- ___ Python tracker

[issue14578] importlib doesn't check Windows registry for paths

Brett Cannon added the comment: FYI, I just deleted PC/import_nt.c as it stopped compiling after my removal of _imp.get_suffixes(). Obviously hg has the history of the file so if someone needs to resurrect it there shouldn't be much issue. -- ___ P

[issue14093] Mercurial version information not appearing in Windows builds

Roundup Robot added the comment: New changeset 4459d82ff127 by Vinay Sajip in branch 'default': Closes #14093: Added Mercurial version information to Windows builds. http://hg.python.org/cpython/rev/4459d82ff127 -- nosy: +python-dev resolution: -> fixed stage: patch review -> committed

[issue14722] Overflow in parsing 'float' parameters in PyArg_ParseTuple*

Mark Dickinson added the comment: > But values that rounded to DBL_MAX can raise > OverflowError. In any case it's too difficult to achieve strict behavior > in this corner case. Well, PyLong_AsDouble *does* achieve strict behaviour in this corner case :-). Integers less than 0.5 * (sys.float

[issue14721] httplib doesn't specify content-length header for POST requests without data

Arve Knudsen added the comment: Yes, I agree it doesn't make much sense for HEAD AFAICT, but Chrome does it. Maybe there's a reason? -- ___ Python tracker ___ _

[issue14721] httplib doesn't specify content-length header for POST requests without data

Arve Knudsen added the comment: Here's my initial proposal for a patch against httplib, based on the 2.7 branch of cpython repository. I've included a couple of tests, which check that when content is empty, content-length is set to 0 for certain methods (POST/PUT etc) and not specified for o

[issue14722] Overflow in parsing 'float' parameters in PyArg_ParseTuple*

Changes by Serhiy Storchaka : -- type: -> enhancement versions: -Python 2.7, Python 3.2 ___ Python tracker ___ ___ Python-bugs-list

[issue14722] Overflow in parsing 'float' parameters in PyArg_ParseTuple*

Serhiy Storchaka added the comment: Here is a patch with tests. > Nope. Values just larger than DBL_MAX won't raise OverflowError here. Isn't that a little bit. But values that rounded to DBL_MAX can raise OverflowError. In any case it's too difficult to achieve strict behavior in this corner

[issue13959] Re-implement parts of imp in pure Python

Brett Cannon added the comment: OK, I'm waiting on issue #14657 (avoiding the _frozen_importlib/importlib dichotomy) is resolved before I document the new imp.extension_suffixes() as it would be good to know where I should pull in the source and bytecode suffixes. I think this only leaves get

[issue13959] Re-implement parts of imp in pure Python

Roundup Robot added the comment: New changeset 257cbd2fac38 by Brett Cannon in branch 'default': Issue #13959: Re-implement imp.get_suffixes() in Lib/imp.py. http://hg.python.org/cpython/rev/257cbd2fac38 -- ___ Python tracker

[issue14657] Avoid two importlib copies

Roundup Robot added the comment: New changeset 257cbd2fac38 by Brett Cannon in branch 'default': Issue #13959: Re-implement imp.get_suffixes() in Lib/imp.py. http://hg.python.org/cpython/rev/257cbd2fac38 -- nosy: +python-dev ___ Python tracker

[issue14721] httplib doesn't specify content-length header for POST requests without data

Jesús Cea Avión added the comment: HEAD?. It doesn't make sense in HEAD if it doesn't make sense in GET. Looking around, I found this, to mud the water a little bit more: . Not being explicit about th

[issue13790] In str.format an incorrect error message for list, tuple, dict, set

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue14723] Misleading error message for str.format()

Eric V. Smith added the comment: This is a duplicate of issue 13790. See the comments there for why it works this way. -- nosy: +eric.smith resolution: -> duplicate status: open -> closed superseder: -> In str.format an incorrect error message for list, tuple, dict, set ___

[issue14701] parser module doesn't support 'raise ... from'

Mark Dickinson added the comment: Hmm. Possibly, yes. At least, it should be clear somehow from the docs that the parser, symbol, token and ast modules are CPython specific. (And possibly tokenize, too.) -- ___ Python tracker

[issue14723] Misleading error message for str.format()

New submission from Mark Theisen : When I run this code: '{0:i}'.format(None) I get this error: ValueError: Unknown format code 'i' for object of type 'str' This seems misleading because None is of Type 'NoneType'. I was expecting the error to say something to the effect of: Unknown format cod

[issue14701] parser module doesn't support 'raise ... from'

Terry J. Reedy added the comment: Just curious, should "The parser module provides an interface to Python’s internal parser and byte-code compiler." say "CPython's"? -- nosy: +terry.reedy ___ Python tracker _

[issue14721] httplib doesn't specify content-length header for POST requests without data

Arve Knudsen added the comment: Actually, when inspecting the HTTP requests sent by Chrome for the different methods (a great little Chrome app called Postman let me fire requests manually), I found that content-length would be set for most methods. I could confirm that 'content-length: 0' wo

[issue14722] Overflow in parsing 'float' parameters in PyArg_ParseTuple*

Mark Dickinson added the comment: > And it checks strictly out of ±DBL_MAX. Nope. Values just larger than DBL_MAX won't raise OverflowError here. > Because float(10**1000) returns no float('inf'), but raises an > exception, I think that returning ±∞ will be wrong. Possibly. But there's also

[issue14692] json.loads parse_constant callback not working anymore

Changes by Terry J. Reedy : -- title: json.joads parse_constant callback not working anymore -> json.loads parse_constant callback not working anymore ___ Python tracker ___ ___

[issue14722] Overflow in parsing 'float' parameters in PyArg_ParseTuple*

Serhiy Storchaka added the comment: I also thought about ±∞. But PyLong_AsDouble() raises OverflowError for out-of-range value. And it checks strictly out of ±DBL_MAX. Because float(10**1000) returns no float('inf'), but raises an exception, I think that returning ±∞ will be wrong. --

[issue11943] Add TLS-SRP (RFC 5054) support to ssl, _ssl, http, and urllib

Antoine Pitrou added the comment: Quinn, are you planning to work on an updated patch? -- ___ Python tracker ___ ___ Python-bugs-list

[issue2377] Replace __import__ w/ importlib.__import__

Changes by Brett Cannon : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue14711] Remove os.stat_float_times

Antoine Pitrou added the comment: +1 for deprecating. -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsub

[issue11618] Locks broken wrt timeouts on Windows

Antoine Pitrou added the comment: I agree that Martin that it's not a good idea to add "dead" code. Furthermore, you patch has: +#ifndef _PY_EMULATED_WIN_CV +#define _PY_EMULATED_WIN_CV 0 /* use emulated condition variables */ +#endif + +#if !defined NTDDI_VISTA || NTDDI_VERSION < NTDDI_VISTA

[issue14678] Update zipimport to support importlib.invalidate_caches()

Brett Cannon added the comment: I should mention I have a version from importers that is probably out-of-date: http://code.google.com/p/importers/source/browse/importers/zip.py -- ___ Python tracker _

[issue14662] shutil.move doesn't handle ENOTSUP raised by chflags on OS X

Antoine Pitrou added the comment: Looks ok to me, but I don't have a system with os.chflags to test on. -- ___ Python tracker ___ ___

[issue14721] httplib doesn't specify content-length header for POST requests without data

Arve Knudsen added the comment: Which HTTP methods should we auto-define content-length for? POST and PUT? I noticed that my first attempt at a patch would define content-length also for GET requests, which broke a unit test (test_ipv6host_header). -- ___

[issue14093] Mercurial version information not appearing in Windows builds

Martin v. Löwis added the comment: Please go ahead and apply it. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscr

[issue14693] hashlib fallback modules should be built even if openssl *is* available at build time

Changes by Éric Araujo : -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue14703] Update PEP metaprocesses to describe PEP czar role

Changes by Éric Araujo : -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue14654] Faster utf-8 decoding

Antoine Pitrou added the comment: 64-bit Linux, Intel Core i5-2500K CPU @ 3.30GHz: vanilla 3.3 patch 2 patch 3 utf-8 'A'*1 6931 (+3%)7115 (+0%) 7117 utf-8 'A'*+'\x80' 2347 (+1%)

[issue14093] Mercurial version information not appearing in Windows builds

Vinay Sajip added the comment: I'd like to commit this soon. Any chance of a review? It's a very small patch, so it shouldn't need much time. -- keywords: +needs review -patch ___ Python tracker _

[issue14710] pkgutil.get_loader is broken

Changes by Éric Araujo : -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue14721] httplib doesn't specify content-length header for POST requests without data

Changes by Éric Araujo : -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue14721] httplib doesn't specify content-length header for POST requests without data

Piotr Dobrogost added the comment: > Fiddler reports that it receives the following headers for the POST request Python 3.2.3 on Windows Vista 64bit gives the same output for import http.client conn = http.client.HTTPConnection('localhost',) conn.request("POST", "/post", "", {}) conn.close

[issue14720] sqlite3 microseconds

Antoine Pitrou added the comment: Can be reproduced with: >>> con = sqlite3.connect(":memory:", detect_types=sqlite3.PARSE_DECLTYPES) >>> cur = con.cursor() >>> cur.execute("CREATE TABLE t (x TIMESTAMP)") >>> cur.execute("INSERT INTO t (x) VALUES ('2012-04-04 15:06:00.456')") >>> cur.execute(

[issue14721] httplib doesn't specify content-length header for POST requests without data

Changes by Antoine Pitrou : -- nosy: +orsenthil stage: test needed -> needs patch versions: +Python 3.2, Python 3.3 ___ Python tracker ___ ___

[issue14722] Overflow in parsing 'float' parameters in PyArg_ParseTuple*

Changes by Mark Dickinson : -- assignee: -> mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue14722] Overflow in parsing 'float' parameters in PyArg_ParseTuple*

Mark Dickinson added the comment: I was just remembering that I was *sure* I'd seen the double->float avoiding undefined behaviour issue mentioned on a C mailing list not so long ago. Turns out that there was a good reason for me remembering that... https://groups.google.com/group/comp.lang

[issue14722] Overflow in parsing 'float' parameters in PyArg_ParseTuple*

Changes by Mark Dickinson : -- nosy: +skrah ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue14722] Overflow in parsing 'float' parameters in PyArg_ParseTuple*

Mark Dickinson added the comment: I don't think this change should be made for 2.7 or 3.2, since it has potential to break existing code. Though technically, conversion of an out-of-range double to a float gives undefined behaviour (C99 6.3.1.5p2), I'm willing to bet that most current compil

[issue14721] httplib doesn't specify content-length header for POST requests without data

Jesús Cea Avión added the comment: Patch with test, please :-). I know it is a pain in the ass, but the result is having a higher quality python. -- ___ Python tracker ___ ___

[issue14722] Overflow in parsing 'float' parameters in PyArg_ParseTuple*

New submission from Serhiy Storchaka : In function convertsimple() in Python/getargs.c possible converting out of float range value from double to float. Fortunately, 'f' format character is not used in CPython source code. But it can be used in the extensions. Tests will be later. -

[issue14721] httplib doesn't specify content-length header for POST requests without data

Arve Knudsen added the comment: I can look into patch and 3.x tonight I think. Should I provide a test with an eventual patch? -- ___ Python tracker ___ ___

[issue14721] httplib doesn't specify content-length header for POST requests without data

Changes by Ezio Melotti : -- nosy: +ezio.melotti stage: -> test needed type: -> behavior ___ Python tracker ___ ___ Python-bugs-list

[issue14721] httplib doesn't specify content-length header for POST requests without data

Jesús Cea Avión added the comment: Could you provide a patch? Does this affect 3.x too? -- nosy: +jcea ___ Python tracker ___ ___ P

[issue14705] Add 'bool' format character to PyArg_ParseTuple*

Mark Dickinson added the comment: In this line in the patch (Python/getargs.c): +if (val == -1 || PyErr_Occurred()) { Isn't that call to PyErr_Occurred() redundant? -- ___ Python tracker

[issue14705] Add 'bool' format character to PyArg_ParseTuple*

Eric V. Smith added the comment: If bool_new() is going to use 'p', then my suggestion shouldn't be the only test of 'p'. -- ___ Python tracker ___

[issue14705] Add 'bool' format character to PyArg_ParseTuple*

Serhiy Storchaka added the comment: > Since the salient point is that 'p' returns the same value as bool(), right? Yes, and bool_new() is a candidate number one for using new feature. -- ___ Python tracker __

[issue14720] sqlite3 microseconds

Changes by Antoine Pitrou : -- nosy: +ghaering versions: +Python 2.7, Python 3.3 ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue14705] Add 'bool' format character to PyArg_ParseTuple*

Serhiy Storchaka added the comment: > Serily: why would you unhesitatingly prefer 'P' to 'p'? My name is Serhiy. :) 'P' has the advantage that you can safely backward-compatibly remove the restriction by replacing 'P' on 'p'. :) > I also found some funny in-between cases. This is historical

[issue14705] Add 'bool' format character to PyArg_ParseTuple*

Eric V. Smith added the comment: Now that I think about this some more, I think I'd structure the 'p' tests as: for expr in [False, None, True, 1, 0]: # add the rest self.assertEqual(bool(expr), getargs_p(expr)) Since the salient point is that 'p' returns the same value as bool(), right?

[issue14705] Add 'bool' format character to PyArg_ParseTuple*

Larry Hastings added the comment: Added test forcing a failure for 'p' (and 'P'). This made me have to handle errors a little differently, so it was definitely good to test it. Thanks for the suggestion, Martin! Also changed wording in documentation ever-so-slightly. -- Added file:

[issue14705] Add 'bool' format character to PyArg_ParseTuple*

Martin v. Löwis added the comment: >> I think there should be a test case also where PyObject_IsTrue gives an >> exception (which I think can happen if __bool__ raises an exception). > > I'd be happy to add such a test, but I don't know of any types like > that. Can anyone suggest one? class

[issue14705] Add 'bool' format character to PyArg_ParseTuple*

Larry Hastings added the comment: > I think there should be a test case also where PyObject_IsTrue gives an > exception (which I think can happen if __bool__ raises an exception). I'd be happy to add such a test, but I don't know of any types like that. Can anyone suggest one? -- __

[issue14705] Add 'bool' format character to PyArg_ParseTuple*

Martin v. Löwis added the comment: I think there should be a test case also where PyObject_IsTrue gives an exception (which I think can happen if __bool__ raises an exception). -- nosy: +loewis ___ Python tracker

[issue14127] add st_*time_ns fields to os.stat(), add ns keyword to os.*utime*(), os.*utimens*() expects a number of nanoseconds

Martin v. Löwis added the comment: Revision 4deb7c1f49b9 -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue14127] add st_*time_ns fields to os.stat(), add ns keyword to os.*utime*(), os.*utimens*() expects a number of nanoseconds

Richard Oudkerk added the comment: > I'm developing on Linux (64-bit) in case that helps. I tested it on 32 bit Linux. I have committed it, but I forgot to put the issue number in the commit message. -- ___ Python tracker

[issue14705] Add 'bool' format character to PyArg_ParseTuple*

Larry Hastings added the comment: I looked through the Python sources and couldn't find any instances of a function or method with an argument that only allowed you to pass in either True or False. Serily already said he would use 'P' over 'p', although I too am unconvinced that's a good id

[issue14127] add st_*time_ns fields to os.stat(), add ns keyword to os.*utime*(), os.*utimens*() expects a number of nanoseconds

Larry Hastings added the comment: By "the unit tests" I meant I ran the whole suite: Lib/test/regrtest.py. I know that runs test_os, and I assume it runs test_posix too. I just ran test_posix by hand and it passed. I'm developing on Linux (64-bit) in case that helps. -- ___

[issue14127] add st_*time_ns fields to os.stat(), add ns keyword to os.*utime*(), os.*utimens*() expects a number of nanoseconds

Richard Oudkerk added the comment: > Looks good to me. You're a core contributor, yes? If not let me know and > I'll commit it. I will commit. > Though I must admit I'm baffled how I haven't seen that crash. I've run > the unit tests a zillion times on this patch. Were you running test_p

[issue14127] add st_*time_ns fields to os.stat(), add ns keyword to os.*utime*(), os.*utimens*() expects a number of nanoseconds

Larry Hastings added the comment: Looks good to me. You're a core contributor, yes? If not let me know and I'll commit it. Though I must admit I'm baffled how I haven't seen that crash. I've run the unit tests a zillion times on this patch. --

[issue14127] add st_*time_ns fields to os.stat(), add ns keyword to os.*utime*(), os.*utimens*() expects a number of nanoseconds

Richard Oudkerk added the comment: There is another problem causing a fatal error in test_posix on Unix. The attached patch fixes it: *ua->path should be decrefed not ua->path. -- Added file: http://bugs.python.org/file25452/utime_read_time_arguments.patch

[issue14705] Add 'bool' format character to PyArg_ParseTuple*

Mark Dickinson added the comment: I also think that 'P' looks too strict to be really useful. I can't think of too many cases where I'd really want to insist on a boolean argument (and reject values of 0 or 1). Maybe implement just 'p' for now and consider 'P' later? -- nosy: +mark.

[issue14572] 2.7.3: sqlite module does not build on centos 5 and Mac OS X 10.4

Marc-Andre Lemburg added the comment: Mac OS X 10.4 is also affected and for the same reason. SQLite builds fine for Python 2.5 and 2.6, but not for 2.7. -- nosy: +lemburg title: 2.7.3: sqlite module does not build on centos 5 -> 2.7.3: sqlite module does not build on centos 5 and Mac

[issue14705] Add 'bool' format character to PyArg_ParseTuple*

Eric V. Smith added the comment: The patch looks good to me. Are there any places in the current code base that would use "P"? "p" seems the more useful case. Are you planning on changing existing code to use P or p, or just use it going forward? -- nosy: +eric.smith __

[issue14721] httplib doesn't specify content-length header for POST requests without data

New submission from Arve Knudsen : httplib doesn't specify the HTTP header 'content-length' for POST requests without data. Conceptually this makes sense, considering the empty content. However, IIS (7.5) servers don't accept such requests and respond with a 411 status code. See this question

[issue14127] add st_*time_ns fields to os.stat(), add ns keyword to os.*utime*(), os.*utimens*() expects a number of nanoseconds

Roundup Robot added the comment: New changeset fc5d2f4291ac by Larry Hastings in branch 'default': Issue #14127: Fix two bugs with the Windows implementation. http://hg.python.org/cpython/rev/fc5d2f4291ac -- ___ Python tracker

[issue14127] add st_*time_ns fields to os.stat(), add ns keyword to os.*utime*(), os.*utimens*() expects a number of nanoseconds

Richard Oudkerk added the comment: > Let me recap, just to make sure I have it straight. There are two errors > on Windows: That's right. The patch looks good and passes for me on Windows. -- ___ Python tracker

[issue14127] add st_*time_ns fields to os.stat(), add ns keyword to os.*utime*(), os.*utimens*() expects a number of nanoseconds

Larry Hastings added the comment: Let me recap, just to make sure I have it straight. There are two errors on Windows: * The ! on (what is currently) line 3770 is wrong: if (!utime_read_time_arguments(&ua)) { * If you pass in a Unicode string but also pass in both times and ns, you get

[issue14127] add st_*time_ns fields to os.stat(), add ns keyword to os.*utime*(), os.*utimens*() expects a number of nanoseconds

Richard Oudkerk added the comment: Without the check for RuntimeError os.utime("foo", times=(5,5), ns=(5,5)) raises TypeError("TypeError: 'str' does not support the buffer interface") because we have fallen through to the narrow path. The correct error is RuntimeError("utime: y

[issue14654] Faster utf-8 decoding

Serhiy Storchaka added the comment: Thank you, Martin, this is what I had in mind. Lost in translation. ;) -- ___ Python tracker ___

[issue14127] add st_*time_ns fields to os.stat(), add ns keyword to os.*utime*(), os.*utimens*() expects a number of nanoseconds

Richard Oudkerk added the comment: > TBH I don't understand why it should crash, and therefore how your patch > helps. Trying again using narrow strings should always work; indeed, the > code did that before I touched it. Can you describe how it crashes? The important part of the patch is t

[issue14654] Faster utf-8 decoding

Martin v. Löwis added the comment: There is nothing wrong with two issues having the same title. Of course, it would be best if the title reflected the *actual* defect or change, such as "specialize UTF-8 decoding by character width", or some such. In any case, the title change is desirable s

[issue14654] Faster utf-8 decoding

Serhiy Storchaka added the comment: > title: More fast utf-8 decoding -> Faster utf-8 decoding Éric, there is already an issue (#4868) with this title. -- ___ Python tracker __