Mailman 3 March 2021 - Python-Dev

Re: Steering Council reply regarding conduct (was Re: Steering Council update for February)
by Brian Herman 25 Mar '21

25 Mar '21

Maybe we can change the discussion to something more productive like the python module system or anything else?

1 0

Steering Council reply regarding conduct (was Re: Steering Council update for February)
by Python Steering Council 24 Mar '21

24 Mar '21

From Thomas Wouters, on behalf of and with full support of the Python Steering Council: I’ll post a separate reply about the merits of the decision, but we have to talk about this post from Steven D’Aprano in particular. Steven, this reply -- its tone and its message -- are completely unacceptable. It is offensive, dismissive and insulting. It’s a bad faith argument ridiculing a good faith effort. It is particularly insulting that you take the time to draw false equivalences to arguments that weren’t made on this list, and that you’re assuming motivation and ridiculing it, without taking the time to engage in the actual arguments. There are plenty of sources online that you could’ve used to learn more, or you could have just asked in this thread. Instead, you posted this sarcastic, denigrating, mocking reply. Yours isn’t the only post that crosses the line in this thread, but it is the worst. It is an example of the kind of discourse that is too common and that reflects very badly on python-dev. It creates an atmosphere of disrespect and abuse, and actively scares away both experienced contributors and new ones. This is not conjecture; I and others on the SC have heard from more than a dozen people that this is exactly the case. This is not acceptable. It has to stop. The PSF Code of Conduct WG has sent the SC a recommendation on this issue. It recommended a temporary ban from python-dev for Steven, and a warning for someone else. While the SC believes a temporary ban would certainly be a reasonable action, we decided to instead make this public statement, as a warning to everyone. The SC wants to be clear that this statement applies to everyone who has made uncivil and inflammatory posts. This tone is not acceptable from anyone. The SC wants to make this very clear: this is a final warning to remind everyone that this behaviour will result in strong measures, including bans and ejections. If you want to argue something, do so on the merits, in good faith, and with empathy and consideration. If you can only ridicule someone, their motivation or their lived experience, please keep it to yourself. > On Tue, Mar 09, 2021 at 08:27:19PM +0000, Pablo Galindo Salgado wrote: > > > The Steering Council discussed renaming the master branch to main and > > the consensus was that we should do that. > > And about time too. Can we now tackle some of the equally pressing use > of offensive terms that are common in the Python community, starting > with the name of the language itself? > > Pythons are snakes, which is triggering to people with a phobia of > snakes. About one third of all people, or more than two *billion* > people, suffer from some level of phobia towards snakes. > > The popular "nose" testing framework is a blatant antisemetic and > neo-nazi dog whistle. > > "bool" is named after George Boole, a problematic white man who > appropriated the culture of both the Middle East and East Asia. > > "dict" is confusable with, and is often abbreviated to, an offensive > word. And don't even get me started with the obvious sexism of "tty". > > Unicode is racist because it has unified Chinese, Japanese and Korean > characters as if they were the same thing, and relegates non-Western > languages to second class status: > > https://modelviewculture.com/pieces/i-can-text-you-a-pile-of-poo-but-i-cant… > > It also includes a teddy bear symbol, which is named after notorious > racist and imperialist Theodore Roosevelt, and no less than *six* > swastika symbols. Also the Cross of Jerusalem, the symbol of such openly > fascist groups as the Federal State of Austria during the 1930s and the > Russian far-right extremist organisation the People's National Party. > > It even has a symbol for chains, which is associated even more closely > with slavery than "master". > > Speaking of slavery, in the standard library we have ChainMap and > itertools.chain. > > We have the ableist "runpy", and in the random module a function named > after Vilfredo Pareto, who supported the rule of fascist dictator Benito > Mussolini. There are the token and tokenize modules, which are offensive > for their association with both sexist and racist views. > > The tarfile module is associated with the racist Uncle Remus stories, > and a derogatory term for US Blacks. > > https://www.washingtonpost.com/blogs/compost/post/doug-lamborns-tar-baby-qu… > > The textwrap module uses a derogatory racist and fatphobic term dozens > of times. > > http://rsdb.org/slur/chunk > > Each of these issues are just as important as the "master" issue. > > > -- > Steve

3 2

Merge request reminder.
by Alfred Perlstein 23 Mar '21

23 Mar '21

Hello, a while back we hit a bug with doctest and mock.call that confused a few people on our team for a while. I dug into fixing it and made doctest more defensive around un-unwrappable calls. I submitted a PR (https://github.com/python/cpython/pull/22981) for an Issue (https://bugs.python.org/issue35753) back in October 25, 2020 which got some review, and then have not heard for several months. I am wondering if it can be reviewed and feedback given on a way forward. Thank you, -Alfred

1 0

typo in PEP 636
by codeofdusk＠gmail.com 23 Mar '21

23 Mar '21

Hello, The GUI section of PEP 636 reads: "It will also requires that the event has a position attribute that matches the (x, y) pattern". It should read "It will also require that the event has a position attribute that matches the (x, y) pattern". Thanks, Bill

3 4

Tests now start with only 131 imported modules, instead of 233
by Victor Stinner 23 Mar '21

23 Mar '21

Hi, tl;dr Tests of the Python Test Suite now start with 131 imported modules, instead of 233. For example, asyncio, logging, multiprocessing and warnings are no longer imported by default. -- The Python test suite is run by a custom test runner called "libregrtest" (test.libregrtest). It can detect reference leaks, write the output as JUnit XML, run tests in parallel with multiple processes, etc. Tests are written with test.support which is a collection of helper functions. Over the years, test.support got more and more functions, and libregrtest got more and more features. The problem is that they import more and more modules. For example, "import test.support" imports 173 modules in Python 3.8! $ python3.8 >>> import sys, sys >>> before=set(sys.modules); import test.support; after=set(sys.modules) >>> len(after - before) 173 In these imports, you can find some "heavy" modules like asyncio and multiprocessing. Moreover, some modules have "side effects" on import. For example, "import logging" registers an "at fork" callback. In April 2020, I worked with Hai Shi on Python 3.10 in bpo-40275 to reduce the number of test.support imports from 171 to 25! test.support was splitted into multiple sub-modules: - bytecode_helper - hashlib_helper - import_helper - logging_helper - os_helper - script_helper - socket_helper - threading_helper - warnings_helper I continued the work in bpo-41718 to reduce the number of libregrtest imports, since libregrtest also imported many modules. A dummy test which does nothing in the master branch now only has 131 modules in sys.modules, whereas in Python 3.9 it has 233 (+102) modules! For example, asyncio, logging, multiprocessing and warnings are no longer imported by default. "import test.support" is now faster. master branch compared to Python 3.8 using ./python -c 'import test.support' command and Python built in release mode: [py38] 85.7 ms +- 6.8 ms -> [master] 32.4 ms +- 1.3 ms: 2.64x faster More realistic command running a single test method: ./python -m test test_os -m test_access [py38] 136 ms +- 5 ms -> [master] 97.8 ms +- 2.4 ms: 1.39x faster The only annoying point is that splitting test.support into sub-modules was not backported to Python 3.8 and 3.9, and so it will make backports a little bit more annoying. Sorry about that! -- If you know that two modules should be tested together, please write a dedicated test for that ;-) Victor -- Night gathers, and now my watch begins. It shall not end until my death.

2 3

Merge Request Review Reminder
by Faisal Mahmood 22 Mar '21

22 Mar '21

Hello, I hope you are all well, I currently have an issue / merge request that has become stale and as per the guidelines I am sending this e-mail to request someone to review it for me please. Issue Number: 42861 (https://bugs.python.org/issue42861) Pull Request: 24180 (https://github.com/python/cpython/pull/24180) This is my first contribution to CPython and I am very keen to get this added as I think it is an almost essential enhancement missing from the ipaddress module. I would greatly appreciate if someone can take a look and give me feedback, I am more than happy to help explain things, as I appreciate this is not the most straightforward thing to do. Effectively, this method allows you to get the next closest network of any prefix size, it works by effectively adding 1 to the host portion of the network. There is actually a very nice guide someone made on stackexchange explaining how to do this calculation manually, I simply followed this logic and have tested it as much as possible and it seems to work great. See here: https://networkengineering.stackexchange.com/questions/7106/how-do-you-calc… Please let me know if there is anything else I can do to help get this merged. Kind regards, Faisal.

8 12

Python Language Summit 2021 Signups Are Now Open
by Łukasz Langa 22 Mar '21

22 Mar '21

I’m happy to announce that we’ve opened the sign-up forms for the 2021 Python Language Summit! TL;DR When: Tuesday, May 11, 2021 (4 hours) and Wednesday, May 12, 2021 (4 hours). Exact times TBD depending on attendee timezones. Where: Online via Zoom (link will be sent via email to attendees) Co-chairs: Mariatta Wijaya & Łukasz Langa Blogger: Joanna Jablonski Sign up to attend and actively participate: https://forms.gle/cgmGnmQMDhD2mhHY8 <https://forms.gle/cgmGnmQMDhD2mhHY8> (closes after March 22nd, 2021 AoE) Propose a topic: https://forms.gle/Jui9mxsHrB4fVvAB8 <https://forms.gle/Jui9mxsHrB4fVvAB8> (closes after March 22nd, 2021 AoE) To get an idea of past Python Language Summits, you can read these blog posts: 2020: Python Software Foundation News: The 2020 Python Language Summit <https://pyfound.blogspot.com/2020/04/the-2020-python-language-summit.html> 2019: http://pyfound.blogspot.com/2019/05/the-2019-python-language-summit.html <http://pyfound.blogspot.com/2019/05/the-2019-python-language-summit.html> 2018: The 2018 Python Language Summit [LWN.net] <https://lwn.net/Articles/754152/> 2017: The 2017 Python Language Summit [LWN.net] <https://lwn.net/Articles/723251/> Do I need to sign up if I’m a Python core developer? Yes please! While in the past we have limited attendance to 50 people, this time, due to virtual format, we will be a bit more flexible, but will still keep it small and manageable. We aren’t planning to go beyond 80 participants. Please register to reserve your space. Can I sign up if I’m not a Python core developer? Yes you can. In the past, we had quite a number of participants who were not Python core devs. Among them were maintainers and representatives from BeeWare, CircuitPython, PSF board member, PyCharm, PyPA, etc. Register if you want to participate. Note that until you hear back from us, your attendance is not confirmed. As explained in the question above, our “space” is more flexible than usual, but in the interest of maintaining a vigorous discussion space, we might still be unable to invite everyone who signs up. What kind of topics are covered? Python Language Summit is a special event with very specific audience: Python core developers. Ideally your topic is not an “announcement” or “project status” but rather something that will encourage further discussion and questions. The more controversial, the better. An open issue, group of issues, or a PEP that is awaiting decision are all good topics to propose. You can also further explain why this is better discussed in person instead of online. According to last year’s feedback, our audience prefer more discussions and shorter talks. Who can present a talk? Anyone, even if you’re not a Python core developer. However, please understand that we will have to be selective as space and time are limited. In particular, we are prioritizing active core contributors, as well as those who we believe will be able to improve the quality of the discussions at the event and bring a more diverse perspective to core Python developers. Note that your topic is not confirmed until you hear back from us. Code of Conduct PyCon’s Code of Conduct <https://us.pycon.org/2020/about/code-of-conduct/> applies and will be enforced. Thanks! @mariatta <https://discuss.python.org/u/mariatta> & @ambv <https://discuss.python.org/u/ambv>

2 3

Fwd: Re: aiter/anext review request
by Joshua Bronson 22 Mar '21

22 Mar '21

On Sat, Mar 20, 2021 at 8:03 PM Guido van Rossum <guido(a)python.org> wrote: > The operator module is also C. > (In my 2018 PR, I was able to add the Python implementations of `aiter` and `anext` to Lib/operator.py, right above where it does "from _operator import *" toward the bottom of the file. I interpreted this pattern there to mean "shadow Python implementations with C implementations where available, but otherwise it's okay to use the Python implementations above". Is that right?) Dan also suggested freezing the Python implementations into the binary as a way of keeping their implementations in Python, but in builtins rather than operator. > I am pleading to remove the 2nd arg to aiter, which should simplify the > code. > Done in the latest revision of https://github.com/python/cpython/pull/23847. That does indeed simplify the patch significantly, nice.[1] All checks are passing. Yury or any other core developers, would you like to merge this now? Thanks again, everyone. --Josh, Dan, and Justin [1] The latest revision adds the following to the `aiter` docs: Unlike the :func:`iter` builtin, :func:`aiter` has no 2-argument variant. Often, this variant can be replaced with assignment expressions:: while chunk := await sock.read(CHUNK_SIZE): ... I think when I originally worked on this in 2018, PEP 572 had only just been approved. :-)

1 0

Buildbot UI auto-refreshes
by Antoine Pitrou 21 Mar '21

21 Mar '21

Hello, It seems the buildbot Web UI has the bad habit of auto-refreshing itself (by doing a full page reload) every minute or two. I also couldn't find a setting to disable it (despite being logged in). Am I missing something? Regards Antoine.

2 2

aiter/anext review request
by Joshua Bronson 20 Mar '21

20 Mar '21

Dear python-dev, New here (but not to Python). 👋 Brett Cannon recommended I start a thread here (thanks, Brett!). In December, two colleagues and I submitted https://github.com/python/cpython/pull/23847, "Add aiter and anext to builtins", which would fix https://bugs.python.org/issue31861. Would any core developers who may be reading this be willing and able to provide a code review? We would love to try to address any review feedback before having to fix (another round of) merge conflicts. (And ideally maybe even get this landed in time for the 3.10 feature freeze in early May?) Thanks and hope this finds you well.

9 20

Re: aiter/anext review request
by Daniel Pope 20 Mar '21

20 Mar '21

As someone who was involved in implementing these, I think they should not be in builtins if that means they have to be in C. My argument is from a point of maintainability. Writing them was plenty of effort in the first place; Josh had written them in idiomatic async Python in the first place, my contribution was to unroll that to sync Python code, and then port that to (sync) C code. It was a lot of effort and a lot of code - several hundred lines and 4(?) new types. The Python code was a few lines - very readable and likely to be practically as fast. We weren't writing this in C to speed it up or to make the code better, but because we *had to*. Implementing async functionality in C is a pain because to implement an awaitable type you need not just that awaitable type, but a new type to represent the iterator that am_await returns. I could imagine having generic type objects and other helpers for implementing async PyObjects in C but I don't really envisage anyone doing that; if you want to write async helpers for Python the best framework is Python. As Josh can attest I was in two minds while implementing this change; I argued firstly that having them in the operator module is fine, and later, that if we want async builtins in general, maybe we could implement them in Python and freeze them into the binary. We pushed on with the C approach mostly because we were already 70% done, and this was what Yury asked for, so it seemed more likely that this would get merged. But, if we're still discussing whether this should be merged in builtins or operator, and that dictates whether it is in Python or C, I'm 100% behind having this code be Python.

3 2

pth file encoding
by Inada Naoki 20 Mar '21

20 Mar '21

Hi, all. I found .pth file is decoded by the default (i.e. locale-specific) encoding. https://github.com/python/cpython/blob/0269ce87c9347542c54a653dd78b9f60bb9f… pth files contain: * import statements * paths For import statement, UTF-8 is the default Python code encoding. For paths, fsencoding is the right encoding. It is UTF-8 on Windows (excpet PYTHONLEGACYWINDOWSFSENCODING is set), and locale-specific encoding in Linux. What encoding should we use? * UTF-8 * sys.getfilesystemencoding() * Keep status-quo. Regards, -- Inada Naoki <songofacandy(a)gmail.com>

9 15

Summary of Python tracker Issues
by Python tracker 19 Mar '21

19 Mar '21

ACTIVITY SUMMARY (2021-03-12 - 2021-03-19) Python tracker at https://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open 7481 ( +3) closed 47813 (+75) total 55294 (+78) Open issues with patches: 2980 Issues opened (66) ================== #35943: PyImport_GetModule() can return partially-initialized module https://bugs.python.org/issue35943 reopened by pitrou #37788: fix for bpo-36402 (threading._shutdown() race condition) cause https://bugs.python.org/issue37788 reopened by mark.dickinson #42161: Remove private _PyLong_Zero and _PyLong_One variables https://bugs.python.org/issue42161 reopened by rhettinger #43334: venv does not install libpython https://bugs.python.org/issue43334 reopened by anuppari #43439: [security] Add audit events on GC functions giving access to a https://bugs.python.org/issue43439 reopened by steve.dower #43481: PyEval_EvalCode() namespace issue not observed in Python 2.7. https://bugs.python.org/issue43481 opened by chrisgmorton #43482: Py_AddPendingCall Inserted Function Never Called in 3.8, works https://bugs.python.org/issue43482 opened by chrisgmorton #43484: we can create valid datetime objects that become invalid if th https://bugs.python.org/issue43484 opened by zzzeek #43486: Python 3.9 installer not updating ARP table https://bugs.python.org/issue43486 opened by codaamok #43487: Rename __unicode__ methods to __str__ in 2to3 conversion https://bugs.python.org/issue43487 opened by bartbroere #43490: IDLE freezes at random https://bugs.python.org/issue43490 opened by aledeaux #43492: Upgrade to SQLite 3.35.2 in macOS and Windows https://bugs.python.org/issue43492 opened by erlendaasland #43493: EmailMessage mis-folding headers of a certain length https://bugs.python.org/issue43493 opened by mglover #43494: Minor changes to Objects/lnotab_notes.txt https://bugs.python.org/issue43494 opened by skip.montanaro #43495: Missing frame block push in compiler_async_comprehension_gener https://bugs.python.org/issue43495 opened by tomkpz #43497: SyntaxWarning for "assertion is always true, perhaps remove pa https://bugs.python.org/issue43497 opened by darke #43498: "dictionary changed size during iteration" error in _ExecutorM https://bugs.python.org/issue43498 opened by kulikjak #43500: Add filtercase() into fnmatch https://bugs.python.org/issue43500 opened by wyz23x2 #43501: email._header_value_parse throws AttributeError on display nam https://bugs.python.org/issue43501 opened by elenril #43502: [C-API] Convert obvious unsafe macros to static inline functio https://bugs.python.org/issue43502 opened by erlendaasland #43503: [subinterpreters] PyObject statics exposed in the limited API https://bugs.python.org/issue43503 opened by eric.snow #43504: effbot.org down https://bugs.python.org/issue43504 opened by mdk #43505: [sqlite3] Explicitly initialise and shut down sqlite3 https://bugs.python.org/issue43505 opened by erlendaasland #43508: Miscompilation information for tarfile.open() when given too m https://bugs.python.org/issue43508 opened by xxm #43509: CFunctionType object should be hashable in Python https://bugs.python.org/issue43509 opened by xxm #43510: PEP 597: Implemente encoding="locale" option and EncodingWarni https://bugs.python.org/issue43510 opened by methane #43511: tkinter with Tk 8.6.11 is slow on macOS https://bugs.python.org/issue43511 opened by thomaswamm #43513: venv: recreate symlinks on --upgrade https://bugs.python.org/issue43513 opened by ThiefMaster #43514: Disallow fork in a subinterpreter affects multiprocessing plug https://bugs.python.org/issue43514 opened by franku #43517: Fix false positives in circular import detection with from-imp https://bugs.python.org/issue43517 opened by pitrou #43518: textwrap.shorten does not always respect word boundaries https://bugs.python.org/issue43518 opened by annesylvie #43520: Fraction only handles regular slashes ("/") and fails with oth https://bugs.python.org/issue43520 opened by weightwatchers-carlanderson #43522: SSLContext.hostname_checks_common_name appears to have no effe https://bugs.python.org/issue43522 opened by Quentin.Pradet #43523: Handling Ctrl+C while waiting on I/O in Windows https://bugs.python.org/issue43523 opened by sovetov #43524: Addition of peek and peekexactly methods to asyncio.StreamRead https://bugs.python.org/issue43524 opened by awalgarg #43525: pathlib: Highlight pathlib operator behavior with anchored pat https://bugs.python.org/issue43525 opened by diegoe #43526: Programmatic management of BytesWarning doesn't work for nativ https://bugs.python.org/issue43526 opened by xmorel #43527: Support full stack trace extraction in warnings. https://bugs.python.org/issue43527 opened by xmorel #43528: "connect_read_pipe" raises errors on Windows for STDIN https://bugs.python.org/issue43528 opened by ivankravets #43529: pathlib.Path.glob causes OSError encountering symlinks to long https://bugs.python.org/issue43529 opened by eric.frederich #43530: email.parser.BytesParser failed to parse mail when it is with https://bugs.python.org/issue43530 opened by tzing #43532: Add keyword-only fields to dataclasses https://bugs.python.org/issue43532 opened by eric.smith #43533: Exception and contextmanager in __getattr__ causes reference c https://bugs.python.org/issue43533 opened by crccw #43534: turtle.textinput window is not transient https://bugs.python.org/issue43534 opened by quid256 #43535: Make str.join auto-convert inputs to strings. https://bugs.python.org/issue43535 opened by rhettinger #43536: 3.9.2 --without-pymalloc --with-pydebug --with-valgrind: test https://bugs.python.org/issue43536 opened by Thermi #43537: interpreter crashes when handling long text in input() https://bugs.python.org/issue43537 opened by xxm #43538: [Windows] support args and cwd in os.startfile() https://bugs.python.org/issue43538 opened by eryksun #43539: test_asyncio: test_sendfile_close_peer_in_the_middle_of_receiv https://bugs.python.org/issue43539 opened by vstinner #43540: importlib: Document how to replace load_module() in What's New https://bugs.python.org/issue43540 opened by vstinner #43542: Add image/heif(heic) to list of media types in mimetypes.py https://bugs.python.org/issue43542 opened by martbln #43544: mimetype default list make a wrong guess for illustrator file https://bugs.python.org/issue43544 opened by Inkhey #43545: Use LOAD_GLOBAL to set __module__ in class def https://bugs.python.org/issue43545 opened by bup #43546: "Impossible" KeyError from importlib._bootstrap acquire line 1 https://bugs.python.org/issue43546 opened by anentropic #43547: support ZIP files with zeroed out fields (e.g. for reproducibl https://bugs.python.org/issue43547 opened by eighthave #43548: RecursionError depth exceptions break pdb's interactive tracin https://bugs.python.org/issue43548 opened by behindthebrain #43549: Outdated descriptions for configuring valgrind. https://bugs.python.org/issue43549 opened by xxm #43550: pip.exe is missing from the NuGet package https://bugs.python.org/issue43550 opened by gipetrou #43551: [Subinterpreters]: PyImport_Import use static silly_list under https://bugs.python.org/issue43551 opened by JunyiXie #43552: Add locale.get_locale_encoding() and locale.get_current_locale https://bugs.python.org/issue43552 opened by vstinner #43553: [sqlite3] Improve test coverage https://bugs.python.org/issue43553 opened by erlendaasland #43554: email: encoded headers lose their quoting when refolded https://bugs.python.org/issue43554 opened by Emil.Styrke #43555: Location of SyntaxError with new parser missing (after continu https://bugs.python.org/issue43555 opened by aroberge #43556: fix attr names for ast.expr and ast.stmt https://bugs.python.org/issue43556 opened by samwyse #43557: Deprecate getdefaultlocale(), getlocale() and normalize() func https://bugs.python.org/issue43557 opened by vstinner #43558: The dataclasses documentation should mention how to call super https://bugs.python.org/issue43558 opened by eric.smith Most recent 15 issues with no replies (15) ========================================== #43558: The dataclasses documentation should mention how to call super https://bugs.python.org/issue43558 #43556: fix attr names for ast.expr and ast.stmt https://bugs.python.org/issue43556 #43555: Location of SyntaxError with new parser missing (after continu https://bugs.python.org/issue43555 #43554: email: encoded headers lose their quoting when refolded https://bugs.python.org/issue43554 #43553: [sqlite3] Improve test coverage https://bugs.python.org/issue43553 #43551: [Subinterpreters]: PyImport_Import use static silly_list under https://bugs.python.org/issue43551 #43550: pip.exe is missing from the NuGet package https://bugs.python.org/issue43550 #43549: Outdated descriptions for configuring valgrind. https://bugs.python.org/issue43549 #43548: RecursionError depth exceptions break pdb's interactive tracin https://bugs.python.org/issue43548 #43545: Use LOAD_GLOBAL to set __module__ in class def https://bugs.python.org/issue43545 #43544: mimetype default list make a wrong guess for illustrator file https://bugs.python.org/issue43544 #43542: Add image/heif(heic) to list of media types in mimetypes.py https://bugs.python.org/issue43542 #43538: [Windows] support args and cwd in os.startfile() https://bugs.python.org/issue43538 #43533: Exception and contextmanager in __getattr__ causes reference c https://bugs.python.org/issue43533 #43530: email.parser.BytesParser failed to parse mail when it is with https://bugs.python.org/issue43530 Most recent 15 issues waiting for review (15) ============================================= #43553: [sqlite3] Improve test coverage https://bugs.python.org/issue43553 #43552: Add locale.get_locale_encoding() and locale.get_current_locale https://bugs.python.org/issue43552 #43551: [Subinterpreters]: PyImport_Import use static silly_list under https://bugs.python.org/issue43551 #43542: Add image/heif(heic) to list of media types in mimetypes.py https://bugs.python.org/issue43542 #43534: turtle.textinput window is not transient https://bugs.python.org/issue43534 #43532: Add keyword-only fields to dataclasses https://bugs.python.org/issue43532 #43525: pathlib: Highlight pathlib operator behavior with anchored pat https://bugs.python.org/issue43525 #43522: SSLContext.hostname_checks_common_name appears to have no effe https://bugs.python.org/issue43522 #43517: Fix false positives in circular import detection with from-imp https://bugs.python.org/issue43517 #43510: PEP 597: Implemente encoding="locale" option and EncodingWarni https://bugs.python.org/issue43510 #43503: [subinterpreters] PyObject statics exposed in the limited API https://bugs.python.org/issue43503 #43502: [C-API] Convert obvious unsafe macros to static inline functio https://bugs.python.org/issue43502 #43501: email._header_value_parse throws AttributeError on display nam https://bugs.python.org/issue43501 #43498: "dictionary changed size during iteration" error in _ExecutorM https://bugs.python.org/issue43498 #43497: SyntaxWarning for "assertion is always true, perhaps remove pa https://bugs.python.org/issue43497 Top 10 most discussed issues (10) ================================= #43552: Add locale.get_locale_encoding() and locale.get_current_locale https://bugs.python.org/issue43552 25 msgs #42128: Structural Pattern Matching (PEP 634) https://bugs.python.org/issue42128 13 msgs #43503: [subinterpreters] PyObject statics exposed in the limited API https://bugs.python.org/issue43503 13 msgs #43313: feature: support pymalloc for subinterpreters. each subinterpr https://bugs.python.org/issue43313 9 msgs #43502: [C-API] Convert obvious unsafe macros to static inline functio https://bugs.python.org/issue43502 9 msgs #43475: Worst-case behaviour of hash collision with float NaN https://bugs.python.org/issue43475 8 msgs #43244: Move PyArena C API to the internal C API https://bugs.python.org/issue43244 7 msgs #43466: ssl/hashlib: Add configure option to set or auto-detect rpath https://bugs.python.org/issue43466 7 msgs #43478: Disallow Mock spec arguments from being Mocks https://bugs.python.org/issue43478 7 msgs #35883: Python startup fails with a fatal error if a command line argu https://bugs.python.org/issue35883 6 msgs Issues closed (74) ================== #12777: Inconsistent use of VOLUME_NAME_* with GetFinalPathNameByHandl https://bugs.python.org/issue12777 closed by eryksun #15453: ctype with packed bitfields does not match native compiler https://bugs.python.org/issue15453 closed by eryksun #15698: PEP 3121, 384 Refactoring applied to pyexpat module https://bugs.python.org/issue15698 closed by vstinner #18017: ctypes.PyDLL documentation https://bugs.python.org/issue18017 closed by eryksun #22781: ctypes: Differing results between Python and C. https://bugs.python.org/issue22781 closed by eryksun #25012: pathlib should allow converting to absolute paths without reso https://bugs.python.org/issue25012 closed by eryksun #25117: Windows installer: precompiling stdlib fails with missing DLL https://bugs.python.org/issue25117 closed by steve.dower #26882: The Python process stops responding immediately after starting https://bugs.python.org/issue26882 closed by eryksun #27820: Possible bug in smtplib when initial_response_ok=False https://bugs.python.org/issue27820 closed by orsenthil #28344: Python 3.5.2 installer hangs when run in session 0 https://bugs.python.org/issue28344 closed by eryksun #29586: Cannot run pip in fresh install of py 3.5.3 https://bugs.python.org/issue29586 closed by steve.dower #29687: smtplib does not support proxy https://bugs.python.org/issue29687 closed by christian.heimes #29982: tempfile.TemporaryDirectory fails to delete itself https://bugs.python.org/issue29982 closed by gvanrossum #31103: Windows Installer Product does not include micro version in di https://bugs.python.org/issue31103 closed by steve.dower #32434: pathlib.WindowsPath.reslove(strict=False) returns absoulte pat https://bugs.python.org/issue32434 closed by eryksun #33129: Add kwarg-only option to dataclass https://bugs.python.org/issue33129 closed by eric.smith #33136: Harden ssl module against CVE-2018-8970 https://bugs.python.org/issue33136 closed by gregory.p.smith #33159: Implement PEP 473 https://bugs.python.org/issue33159 closed by skreft #33603: Subprocess Thread handles grow with each call and aren't relea https://bugs.python.org/issue33603 closed by eryksun #33780: [subprocess] Better Unicode support for shell=True on Windows https://bugs.python.org/issue33780 closed by eryksun #34187: Issues with lazy fd support in _WindowsConsoleIO fileno() and https://bugs.python.org/issue34187 closed by eryksun #34840: dlopen() error with no error message from dlerror() https://bugs.python.org/issue34840 closed by eryksun #35216: misleading error message from shutil.copy() https://bugs.python.org/issue35216 closed by eryksun #36646: os.listdir() got permission error in Python3.6 but it's fine i https://bugs.python.org/issue36646 closed by eryksun #37820: Unnecessary URL scheme exists to allow 'URL: reading file in u https://bugs.python.org/issue37820 closed by christian.heimes #39340: shutil.rmtree and write protected files https://bugs.python.org/issue39340 closed by eryksun #39342: Expose X509_V_FLAG_ALLOW_PROXY_CERTS in ssl https://bugs.python.org/issue39342 closed by christian.heimes #40540: inconstent stdin buffering/seeking behaviour https://bugs.python.org/issue40540 closed by eryksun #40763: zipfile.extractall is safe by now https://bugs.python.org/issue40763 closed by gregory.p.smith #41123: Remove Py_UNICODE APIs except PEP 623 https://bugs.python.org/issue41123 closed by methane #41200: Add pickle.loads fuzz test https://bugs.python.org/issue41200 closed by gregory.p.smith #41567: multiprocessing.Pool from concurrent threads failure on 3.9.0r https://bugs.python.org/issue41567 closed by pitrou #41883: ctypes pointee goes out of scope, then pointer in struct dangl https://bugs.python.org/issue41883 closed by eryksun #41933: Wording of s * n in Common Sequence Operations is not optimal https://bugs.python.org/issue41933 closed by mdk #42322: Spectre mitigations in CPython interpreter https://bugs.python.org/issue42322 closed by gregory.p.smith #42370: test_ttk_guionly: test_to() fails on the GitHub Ubuntu job https://bugs.python.org/issue42370 closed by vstinner #42730: TypeError/hang inside of Time.Sleep() when _thread.interrupt_m https://bugs.python.org/issue42730 closed by eryksun #43065: Delegating to thread and process deadlocks https://bugs.python.org/issue43065 closed by doublex #43068: test_subprocess: test_specific_shell() fails on AMD64 FreeBSD https://bugs.python.org/issue43068 closed by vstinner #43175: filecmp is not working for UTF-8 BOM file. https://bugs.python.org/issue43175 closed by eryksun #43199: FAQ about goto lacks answer https://bugs.python.org/issue43199 closed by terry.reedy #43214: site: Potential UnicodeDecodeError when handling pth file https://bugs.python.org/issue43214 closed by methane #43228: Regression in function builtins https://bugs.python.org/issue43228 closed by vstinner #43245: Add keyword argument support to ChainMap.new_child() https://bugs.python.org/issue43245 closed by rhettinger #43285: ftplib should not use the host from the PASV response https://bugs.python.org/issue43285 closed by gregory.p.smith #43353: Document that logging.getLevelName() can return a numeric valu https://bugs.python.org/issue43353 closed by felixxm #43357: Python memory cleaning https://bugs.python.org/issue43357 closed by gregory.p.smith #43382: github CI blocked by the Ubuntu CI with an SSL error https://bugs.python.org/issue43382 closed by christian.heimes #43410: Parser does not handle correctly some errors when parsin from https://bugs.python.org/issue43410 closed by pablogsal #43427: Possible error on the descriptor howto guide https://bugs.python.org/issue43427 closed by rhettinger #43428: Sync importlib_metadata enhancements through 3.7. https://bugs.python.org/issue43428 closed by jaraco #43437: venv activate bash script has wrong line endings on windows https://bugs.python.org/issue43437 closed by eryksun #43441: [Subinterpreters]: global variable next_version_tag cause meth https://bugs.python.org/issue43441 closed by vstinner #43444: [sqlite3] Move MODULE_NAME def from setup.py to module.h https://bugs.python.org/issue43444 closed by berker.peksag #43462: canvas.bbox returns None on 'hidden' items while coords doesn' https://bugs.python.org/issue43462 closed by Vincent #43477: from x import * behavior inconsistent between module types. https://bugs.python.org/issue43477 closed by brett.cannon #43479: Remove a duplicate comment and assignment in http.client https://bugs.python.org/issue43479 closed by orsenthil #43483: Loss of content in simple (but oversize) SAX parsing https://bugs.python.org/issue43483 closed by ridgerat1611 #43485: Spam https://bugs.python.org/issue43485 closed by zach.ware #43488: Added new methods to vector.py https://bugs.python.org/issue43488 closed by rhettinger #43489: Can't install, nothing to install https://bugs.python.org/issue43489 closed by ned.deily #43491: Windows filepath bug https://bugs.python.org/issue43491 closed by eryksun #43496: macOS tkinter Save As doesn't accept keyboard shortcuts https://bugs.python.org/issue43496 closed by terry.reedy #43499: Compiler warnings in building Python 3.9 on Windows https://bugs.python.org/issue43499 closed by serhiy.storchaka #43506: PEP 624: Update document for removal schedule https://bugs.python.org/issue43506 closed by methane #43507: Variables in locals scope fails to be printed. https://bugs.python.org/issue43507 closed by mark.dickinson #43512: Bug in isinstance(instance, cls) with cls being a protocol? (P https://bugs.python.org/issue43512 closed by gvanrossum #43515: Lazy import in concurrent.futures produces partial import erro https://bugs.python.org/issue43515 closed by pitrou #43516: python on raspberry pi https://bugs.python.org/issue43516 closed by eric.smith #43519: access python private variable https://bugs.python.org/issue43519 closed by steven.daprano #43521: Allow `ast.unparse` to handle NaNs and empty sets https://bugs.python.org/issue43521 closed by pablogsal #43531: Turtle module does not work https://bugs.python.org/issue43531 closed by mark.dickinson #43541: PyEval_EvalCodeEx() can no longer be called with code which ha https://bugs.python.org/issue43541 closed by vstinner #43543: Spam https://bugs.python.org/issue43543 closed by petr.viktorin

1 0

PEP 654 -- Exception Groups and except* : request for feedback for SC submission
by Irit Katriel 18 Mar '21

18 Mar '21

Hi all, We would like to request feedback on PEP 654 -- Exception Groups and except*. https://www.python.org/dev/peps/pep-0654/ It proposes language extensions that allow programs to raise and handle multiple unrelated exceptions simultaneously, motivated by the needs of asyncio and other concurrency libraries, but with other use cases as well. * A new standard exception type, ExceptionGroup, to represent multiple exceptions with shared traceback. * Updates to the traceback printing code to display (possibly nested) ExceptionGroups. * A new syntax except* for handling ExceptionGroups. A reference implementation (unreviewed) can be found at: https://github.com/iritkatriel/cpython/pull/10 Thank you for your help Kind regards Irit, Yury & Guido

22 117

Non-monotonically increasing line numbers in dis.findlinestarts() output
by Skip Montanaro 18 Mar '21

18 Mar '21

Consider this little session from the tip of the spear: >>> sys.version '3.10.0a6+ (heads/master:0ab152c6b5, Mar 15 2021, 17:24:38) [GCC 10.2.0]' >>> def while2(a): ... while a >= 0: ... a -= 1 ... return a ... >>> dis.dis(while2) 2 0 LOAD_FAST 0 (a) 2 LOAD_CONST 1 (0) 4 COMPARE_OP 5 (>=) 6 POP_JUMP_IF_FALSE 24 3 >> 8 LOAD_FAST 0 (a) 10 LOAD_CONST 2 (1) 12 INPLACE_SUBTRACT 14 STORE_FAST 0 (a) 2 16 LOAD_FAST 0 (a) 18 LOAD_CONST 1 (0) 20 COMPARE_OP 5 (>=) 22 POP_JUMP_IF_TRUE 8 4 >> 24 LOAD_FAST 0 (a) 26 RETURN_VALUE >>> list(dis.findlinestarts(while2.__code__)) [(0, 2), (8, 3), (16, 2), (24, 4)] I get that somewhere along the way the compiler has been optimized to duplicate the loop's test so as to eliminate some jumps (perhaps). It's not clear to me that the line number should be "2" in the duplicated test though. Shouldn't it be "3"? I stumbled on this while trying to generate a line number table in my side project register VM. As I understand it, the line number delta in the output table is supposed to always be >= 0. In my code I'm using dis.findlinestarts() to determine the line numbers for each block. Perhaps I should be modifying its results. OTOH, maybe it's a bug. (If that's the consensus, I will create an issue.) Skip

5 5

Reviving PEP 473
by Sebastian Kreft 16 Mar '21

16 Mar '21

Hi dev-team, I'm reopening the discussion of PEP 473, which was closed due to: *The steering council felt the PEP was too broad and not focused enough. Discussions about adding more attributes to built-in exceptions can continue on the issue tracker on a per-exception basis (and obviously here for any broader points, e.g. performance implications as I know that has come up before when the idea of storing relevant objects on exceptions).* Before the PEP was rejected by the SC, I had submitted https://github.com/python/cpython/pull/6271 and the last response said: *You may propose a newly revised PEP which overcomes the last SC feedback.But without the accepted PEP, this PR can not be merged.* Please clarify how can I proceed with adding some of the specified fields to the mentioned exceptions. Should I create a new PEP as suggested in the PR or should we create individual BPO issues for each exception modification. -- Sebastian Kreft

4 4

Rejecting PEP 637 (Support for indexing with keyword arguments)
by Thomas Wouters 16 Mar '21

16 Mar '21

Hi Stefano, Thank you for submitting PEP 637 (Support for indexing with keyword arguments). The Steering Council has reviewed the PEP and after careful consideration, we have decided to reject the PEP. There are a number of reasons for this, but fundamentally we do not believe the benefit is great enough to outweigh the cost of the new syntax. The benefits of the new syntax as outlined in the PEP are not particularly strong, and community support for the new syntax seems low. The new syntax doesn’t provide an obvious way to do something that is currently error-prone, and doesn’t open up new possibilities that were not possible before. While there are certainly cases that could use the new syntax, for many of them it’s not clear that it would be a win, or that third-party libraries would indeed use the syntax. The Steering Council isn’t really convinced by any of the suggested uses in the PEP. The strongest argument for the new syntax comes from the typing side of Python. The Steering Council is not particularly convinced it is of significant benefit to the static type checking language, but even if it were, at this point we’re reluctant to add general Python syntax that only (or mostly) benefits the static typing language. If the syntax would be of great benefit to static typing, it might be time to discuss letting go of the requirement that the typing language be a subset of Python -- but whether this feature is important enough to consider that is up to the typing community. The SC considers the cost of the new syntax significant. It’s not a natural fit, as shown by the corner cases discussed in the PEP. It’s difficult to teach, as indexing and function calls are not as interchangeable or equivalent as they may appear. Looking at more complex expressions with the new syntax, mentally parsing them is significantly harder than the equivalent without the new syntax, even if it requires more lines of code to do the same thing. In addition to all that, the SC is worried about the performance of indexing in CPython and in other Python implementations, considering it’s a very common operation, and about the suggested new __getitem__ protocol, particularly the confusing corner cases of indexing with keywords and zero or one positional items. These are not, however, the main reason we decided to reject the PEP. With our appreciation, For the whole Python Steering Council, Thomas. -- Thomas Wouters <thomas(a)python.org> Hi! I'm an email virus! Think twice before sending your email to help me spread!

5 5

Accepting PEP 624 (Remove Py_UNICODE encoder APIs)
by Thomas Wouters 15 Mar '21

15 Mar '21

Hi Inada, Thank you for submitting PEP 624 (Remove Py_UNICODE encoder APIs). The Steering Council is happy to accept it, but we do have two conditions. We want to make sure that the documentation is clear on what is deprecated, and when they are scheduled to be removed. For example, PyUnicode_TransformDecimalToASCII is itself not currently marked as deprecated (although the section header does mention the deprecation, that is easy to miss), PyUnicode_TranslateCharmap is scheduled for removal in 4.0, and PyUnicode_AsUnicode has two deprecation notices, one mentioning removal in 3.10 and one in 3.12. We would also like to make sure users who need to migrate off of these APIs have the information necessary to do so. The PEP currently lists alternatives with caveats, and it's not immediately obvious from the PEP or the API documentation what the right alternative is for those caveats. As a condition of this PEP’s acceptance, we request that you fully document the recommended workarounds for these caveats. We do recognise that PyUnicode_EncodeDecimal is currently entirely undocumented. Documenting at this stage is probably not worth the effort, but perhaps it could be mentioned in a brief ‘porting’ section in the PEP instead. With the Python Steering Council's gratitude, Thomas. -- Thomas Wouters <thomas(a)python.org> Hi! I'm an email virus! Think twice before sending your email to help me spread!

2 1

Accepting PEP 597 (Add optional EncodingWarning)
by Thomas Wouters 15 Mar '21

15 Mar '21

Hi Inada, Thank you for submitting PEP 597 (Add optional EncodingWarning). The Steering Council is happy with the PEP, and hereby accepts it. The SC is of the opinion that we should move towards making UTF-8 the default encoding, and this PEP will make it easier to do so, and mitigate some of the confusion around the default encoding in the meantime. That being said, the SC would like to invite you and others with interest to work on a PEP for a long term plan to, in fact, change the default encoding to UTF-8. We don't want to make irrevocable decisions until we have a clear, viable plan with a good upgrade path and with community support, but we do believe we need to make that decision sooner rather than later. With thanks from the whole Python Steering Council, Thomas. -- Thomas Wouters <thomas(a)python.org> Hi! I'm an email virus! Think twice before sending your email to help me spread!

4 3

PEP 647 (type guards) -- final call for comments
by Guido van Rossum 14 Mar '21

14 Mar '21

I think we have reached consensus on PEP 647 in typing-sig. We have implementations for mypy and pyright, not sure about the rest. This PEP does not affect CPython directly except for the addition of one special item (TypeGuard) to typing.py -- it would be nice to get that in the 3.10 stdlib. I'm CC'ing python-dev here to see if there are any further comments; if not, we can initiate the approval process by creating an issue at https://github.com/python/steering-council. -- --Guido van Rossum (python.org/~guido) *Pronouns: he/him **(why is my pronoun here?)* <http://feministing.com/2015/02/03/how-using-they-as-a-singular-pronoun-can-…>

17 36

Summary of Python tracker Issues
by Python tracker 12 Mar '21

12 Mar '21

ACTIVITY SUMMARY (2021-03-05 - 2021-03-12) Python tracker at https://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open 7478 (+34) closed 47738 (+36) total 55216 (+70) Open issues with patches: 2968 Issues opened (56) ================== #43198: Operations on sets more than hundred times less efficient with https://bugs.python.org/issue43198 reopened by rhettinger #43411: wm_manage fails with ttk.Frame https://bugs.python.org/issue43411 opened by mfncooper #43412: object.h -Wcast-qual warning https://bugs.python.org/issue43412 opened by petere #43413: tuple subclasses allow kwargs https://bugs.python.org/issue43413 opened by jaraco #43414: os.get_terminal_size() should use file descriptors in Windows https://bugs.python.org/issue43414 opened by eryksun #43416: Add README files in Include/cpython and Include/internal https://bugs.python.org/issue43416 opened by serhiy.storchaka #43417: ast.unparse: Simplify buffering logic https://bugs.python.org/issue43417 opened by BTaskaya #43418: FTPLib module crashes when server returns byte message instead https://bugs.python.org/issue43418 opened by hugochiaxyz8 #43419: contextvars does not work properly in asyncio REPL. https://bugs.python.org/issue43419 opened by lanfon72 #43420: Optimize rational arithmetics https://bugs.python.org/issue43420 opened by Sergey.Kirpichev #43421: os.device_encoding(fd) should support any console fd in Window https://bugs.python.org/issue43421 opened by eryksun #43422: Revert _decimal C API changes https://bugs.python.org/issue43422 opened by pitrou #43424: Document the `controller.name` field in `webbrowser` module https://bugs.python.org/issue43424 opened by ilyagr #43425: test_peg_generator.test_c_parser emits DeprecationWarning due https://bugs.python.org/issue43425 opened by xtreak #43426: test_importlib.test_windows emits deprecation warning over usa https://bugs.python.org/issue43426 opened by xtreak #43427: Possible error on the descriptor howto guide https://bugs.python.org/issue43427 opened by marcosmodenesi #43428: Sync importlib_metadata enhancements through 3.7. https://bugs.python.org/issue43428 opened by jaraco #43429: mmap.size() raises OSError on Unix for anonymous memory https://bugs.python.org/issue43429 opened by ZackerySpytz #43430: Exception raised when attempting to create Enum via functional https://bugs.python.org/issue43430 opened by suhailsingh247 #43431: Subprocess timeout causes output to be returned as bytes in te https://bugs.python.org/issue43431 opened by macdjord #43432: Add function `clear` to the `os` module https://bugs.python.org/issue43432 opened by parsampsh #43433: xmlrpc.client ignores query in URI ("?action=xmlrpc2") since p https://bugs.python.org/issue43433 opened by OndrejPtak #43434: sqlite3.Connection(...) bypasses 'sqlite3.connect' audit hooks https://bugs.python.org/issue43434 opened by erlendaasland #43437: venv activate bash script has wrong line endings on windows https://bugs.python.org/issue43437 opened by jmoguill2 #43438: [doc] sys.addaudithook() documentation should be more explicit https://bugs.python.org/issue43438 opened by vstinner #43441: [Subinterpreters]: global variable next_version_tag cause meth https://bugs.python.org/issue43441 opened by JunyiXie #43442: multicorevm: guarantee type multi sub interpreters safe https://bugs.python.org/issue43442 opened by JunyiXie #43443: Should shelve support dict union? https://bugs.python.org/issue43443 opened by Dominik V. #43444: [sqlite3] Move MODULE_NAME def from setup.py to module.h https://bugs.python.org/issue43444 opened by erlendaasland #43447: Generate vectorcall code to parse arguments using Argument Cli https://bugs.python.org/issue43447 opened by vstinner #43451: pydoc terminal suboptimal rendering of complex annotations https://bugs.python.org/issue43451 opened by dw #43452: Microoptimize PyType_Lookup for cache hits https://bugs.python.org/issue43452 opened by dino.viehland #43453: docs: runtime_checkable example refers to changed behavior in https://bugs.python.org/issue43453 opened by Henry Schreiner #43454: [sqlite3] Add support for R*Tree callbacks https://bugs.python.org/issue43454 opened by erlendaasland #43455: pathlib mistakenly assumes os.getcwd() is a resolved path in W https://bugs.python.org/issue43455 opened by eryksun #43457: Include simple file loading and saving functions in JSON stand https://bugs.python.org/issue43457 opened by nervecenter #43458: Tutorial should mention about variable scope in try/except/fin https://bugs.python.org/issue43458 opened by deekox #43459: Race conditions when the same source file used to build mutlip https://bugs.python.org/issue43459 opened by mgorny #43460: Exception copy error https://bugs.python.org/issue43460 opened by douglas-raillard-arm #43461: Tottime column for cprofile output does not add up https://bugs.python.org/issue43461 opened by jonathanfrawley #43462: canvas.bbox returns None on 'hidden' items while coords doesn' https://bugs.python.org/issue43462 opened by Vincent #43463: typing.get_type_hints with TYPE_CHECKING imports / getting hin https://bugs.python.org/issue43463 opened by The Compiler #43464: set intersections should short-circuit https://bugs.python.org/issue43464 opened by josh.r #43465: ./configure --help describes what --with-ensurepip does poorly https://bugs.python.org/issue43465 opened by ngie #43466: ssl/hashlib: Add configure option to set or auto-detect rpath https://bugs.python.org/issue43466 opened by christian.heimes #43468: functools.cached_property locking is plain wrong. https://bugs.python.org/issue43468 opened by ztane #43471: Fails to import bz2 on Ubuntu https://bugs.python.org/issue43471 opened by xxm #43472: [security][subinterpreters] Add auditing hooks to subinterpret https://bugs.python.org/issue43472 opened by christian.heimes #43473: Junks in difflib https://bugs.python.org/issue43473 opened by hubertbdlb #43474: http.server.BaseHTTPRequestHandler end_header() fails https://bugs.python.org/issue43474 opened by grumblor #43475: Worst-case behaviour of hash collision with float NaN https://bugs.python.org/issue43475 opened by congma #43476: Enabling access to showsyntaxerror for IDLE's shell https://bugs.python.org/issue43476 opened by aroberge #43477: from x import * behavior inconsistent between module types. https://bugs.python.org/issue43477 opened by kaorihinata #43478: Disallow Mock spec arguments from being Mocks https://bugs.python.org/issue43478 opened by msuozzo #43479: Remove a duplicate comment and assignment in http.client https://bugs.python.org/issue43479 opened by maggyero #43480: Add .path method/property to tempfile.* for a pathlib.Path https://bugs.python.org/issue43480 opened by pxeger Most recent 15 issues with no replies (15) ========================================== #43480: Add .path method/property to tempfile.* for a pathlib.Path https://bugs.python.org/issue43480 #43479: Remove a duplicate comment and assignment in http.client https://bugs.python.org/issue43479 #43478: Disallow Mock spec arguments from being Mocks https://bugs.python.org/issue43478 #43477: from x import * behavior inconsistent between module types. https://bugs.python.org/issue43477 #43476: Enabling access to showsyntaxerror for IDLE's shell https://bugs.python.org/issue43476 #43473: Junks in difflib https://bugs.python.org/issue43473 #43472: [security][subinterpreters] Add auditing hooks to subinterpret https://bugs.python.org/issue43472 #43465: ./configure --help describes what --with-ensurepip does poorly https://bugs.python.org/issue43465 #43464: set intersections should short-circuit https://bugs.python.org/issue43464 #43461: Tottime column for cprofile output does not add up https://bugs.python.org/issue43461 #43459: Race conditions when the same source file used to build mutlip https://bugs.python.org/issue43459 #43458: Tutorial should mention about variable scope in try/except/fin https://bugs.python.org/issue43458 #43455: pathlib mistakenly assumes os.getcwd() is a resolved path in W https://bugs.python.org/issue43455 #43453: docs: runtime_checkable example refers to changed behavior in https://bugs.python.org/issue43453 #43451: pydoc terminal suboptimal rendering of complex annotations https://bugs.python.org/issue43451 Most recent 15 issues waiting for review (15) ============================================= #43466: ssl/hashlib: Add configure option to set or auto-detect rpath https://bugs.python.org/issue43466 #43459: Race conditions when the same source file used to build mutlip https://bugs.python.org/issue43459 #43455: pathlib mistakenly assumes os.getcwd() is a resolved path in W https://bugs.python.org/issue43455 #43454: [sqlite3] Add support for R*Tree callbacks https://bugs.python.org/issue43454 #43452: Microoptimize PyType_Lookup for cache hits https://bugs.python.org/issue43452 #43451: pydoc terminal suboptimal rendering of complex annotations https://bugs.python.org/issue43451 #43444: [sqlite3] Move MODULE_NAME def from setup.py to module.h https://bugs.python.org/issue43444 #43441: [Subinterpreters]: global variable next_version_tag cause meth https://bugs.python.org/issue43441 #43434: sqlite3.Connection(...) bypasses 'sqlite3.connect' audit hooks https://bugs.python.org/issue43434 #43432: Add function `clear` to the `os` module https://bugs.python.org/issue43432 #43429: mmap.size() raises OSError on Unix for anonymous memory https://bugs.python.org/issue43429 #43428: Sync importlib_metadata enhancements through 3.7. https://bugs.python.org/issue43428 #43427: Possible error on the descriptor howto guide https://bugs.python.org/issue43427 #43422: Revert _decimal C API changes https://bugs.python.org/issue43422 #43420: Optimize rational arithmetics https://bugs.python.org/issue43420 Top 10 most discussed issues (10) ================================= #43420: Optimize rational arithmetics https://bugs.python.org/issue43420 15 msgs #43466: ssl/hashlib: Add configure option to set or auto-detect rpath https://bugs.python.org/issue43466 9 msgs #43438: [doc] sys.addaudithook() documentation should be more explicit https://bugs.python.org/issue43438 8 msgs #43353: Document that logging.getLevelName() can return a numeric valu https://bugs.python.org/issue43353 7 msgs #43366: Unclosed bracket bug in code.interact prevents identifying syn https://bugs.python.org/issue43366 7 msgs #43443: Should shelve support dict union? https://bugs.python.org/issue43443 6 msgs #43475: Worst-case behaviour of hash collision with float NaN https://bugs.python.org/issue43475 6 msgs #43413: tuple subclasses allow kwargs https://bugs.python.org/issue43413 5 msgs #43462: canvas.bbox returns None on 'hidden' items while coords doesn' https://bugs.python.org/issue43462 5 msgs #28356: [easy doc] Document os.rename() behavior on Windows when src a https://bugs.python.org/issue28356 4 msgs Issues closed (35) ================== #14678: Update zipimport to support importlib.invalidate_caches() https://bugs.python.org/issue14678 closed by brett.cannon #16322: time.tzname on Python 3.3.0 for Windows is decoded by wrong en https://bugs.python.org/issue16322 closed by eryksun #25741: Usual Installation Directory https://bugs.python.org/issue25741 closed by eryksun #28259: Ctypes bug windows https://bugs.python.org/issue28259 closed by eryksun #31466: No easy way to change float formatting when subclassing encode https://bugs.python.org/issue31466 closed by methane #38033: Use After Free: PyObject_Free (valgrind) https://bugs.python.org/issue38033 closed by vstinner #42382: No easy way to get the distribution which provided a importlib https://bugs.python.org/issue42382 closed by jaraco #43287: Use PEP 590 vectorcall to speed up calls to filter() https://bugs.python.org/issue43287 closed by corona10 #43332: Make http.client._tunnel send one byte string over the network https://bugs.python.org/issue43332 closed by gregory.p.smith #43338: Provide offical installers for security releases https://bugs.python.org/issue43338 closed by terry.reedy #43356: PyErr_SetInterrupt should have an equivalent that takes a sign https://bugs.python.org/issue43356 closed by pitrou #43365: Operation conflict between time package and file https://bugs.python.org/issue43365 closed by terry.reedy #43372: ctypes: test_frozentable fails when make regen-frozen https://bugs.python.org/issue43372 closed by nascheme #43374: Apple refuses apps written in Python https://bugs.python.org/issue43374 closed by ned.deily #43379: Pasting multiple lines in the REPL is broken since 3.9 https://bugs.python.org/issue43379 closed by terry.reedy #43391: The comments have invalid license information (broken Python 2 https://bugs.python.org/issue43391 closed by lemburg #43397: Incorrect conversion path case with german character https://bugs.python.org/issue43397 closed by eryksun #43405: DeprecationWarnings in test_unicode https://bugs.python.org/issue43405 closed by methane #43406: Possible race condition between signal catching and signal.sig https://bugs.python.org/issue43406 closed by pitrou #43407: time.monotonic(): Docs imply comparing call N and call N+M is https://bugs.python.org/issue43407 closed by terry.reedy #43415: Typo in dataclasses documentation https://bugs.python.org/issue43415 closed by eric.smith #43423: Subprocess IndexError possible in _communicate https://bugs.python.org/issue43423 closed by gregory.p.smith #43435: Py_BuildValue("y#".... returns incomplete result https://bugs.python.org/issue43435 closed by dwoodjunkmail #43436: bounded _lru_cache_wrapprer behaves as if typed=True when it w https://bugs.python.org/issue43436 closed by rhettinger #43439: [security] Add audit events on GC functions giving access to a https://bugs.python.org/issue43439 closed by christian.heimes #43440: Enable rtree support in SQLite https://bugs.python.org/issue43440 closed by steve.dower #43445: Add frozen modules to sys.stdlib_module_names https://bugs.python.org/issue43445 closed by vstinner #43446: Wrong character in footnote https://bugs.python.org/issue43446 closed by berker.peksag #43448: exec() ignores scope. https://bugs.python.org/issue43448 closed by mark.dickinson #43449: multiprocessing.Pool - crash in subprocess causes deadlock in https://bugs.python.org/issue43449 closed by jkp #43450: List amnesia https://bugs.python.org/issue43450 closed by christian.heimes #43456: Remove _xxsubinterpreters from sys.stdlib_module_names https://bugs.python.org/issue43456 closed by vstinner #43467: IDLE: horizontal scrollbar https://bugs.python.org/issue43467 closed by terry.reedy #43469: Python 3.6 fails to run on MacOS (Big Sur 11.2.3) https://bugs.python.org/issue43469 closed by ned.deily #43470: Installation of Python 3.6.13 fails on MacOS Big Sur 11.2.3 https://bugs.python.org/issue43470 closed by ned.deily

1 0

Acceptance of Pattern Matching PEPs 634, 635, 636, Rejection of PEPs 640 and 642
by Python Steering Council 12 Mar '21

12 Mar '21

After much deliberation, the Python Steering Council is happy to announce that we have chosen to accept PEP 634, and its companion PEPs 635 and 636, collectively known as the Pattern Matching PEPs. We acknowledge that Pattern Matching is an extensive change to Python and that reaching consensus across the entire community is close to impossible. Different people have reservations or concerns around different aspects of the semantics and the syntax (as does the Steering Council). In spite of this, after much deliberation, reviewing all conversations around these PEPs, as well as competing proposals and existing poll results, and after several in-person discussions with the PEP authors, we are confident that Pattern Matching as specified in PEP 634, et al, will be a great addition to the Python language. We also recognize that such a large new feature needs to be accompanied by comprehensive documentation and specification, both in the tutorial section of the documentation and in the language reference. We consider that the presence of such high-quality documentation must be present on the first release of Python 3.10, and therefore its absence should be considered a release blocker. We do not consider the PEPs or any possible external documentation to be sufficient. At the same time, we’re rejecting PEPs 640 and 642. Both PEPs have received little support from core developers. PEP 642’s proposed syntax does not seem like the right way to solve the jagged edges in PEP 634’s syntax, although the SC understands the desire to improve those aspects of the Pattern Matching proposal. Regarding that, we would also like to mention that changes building on top of PEP 634 (even PEPs 640 and 642 if they now gain support) can still be submitted via the PEP process for review using the regular channels (discussions in python-dev or the https://discuss.python.org/ server), followed by a formal submission to the Steering Council for consideration, taking into account that backwards-incompatible changes can only be made before the feature freeze point of Python 3.10. See PEP 619 (https://www.python.org/dev/peps/pep-0619/) for details on the release schedule for Python 3.10. We know that Pattern Matching has been a challenging feature that has sparked considerable discussions and design conversations, leading to several revisions from feedback stemming from the community, core devs, and the Steering Council. We are very happy to see that the Python developer community remains passionate and respectful, and we are sure that the result has benefited a lot because of it. Congratulations to the PEP(s) authors: Guido, Brandt, Tobias, Daniel, Talin, and everyone that participated in the discussion and implementation of this important new feature! -The Python Steering Council

5 4

Python history: origin of the arrow annotation
by Steven D'Aprano 11 Mar '21

11 Mar '21

I was curious how and why return annotations use the arrow `->` symbol, so I went spelunking into the depths of the Python-Ideas and Python-Dev mailing lists. Much to my surprise, I couldn't find any discussion or debate about it. Eventually I tracked the discussion back to a mailing list I didn't even know existed, Types-Sig, all the way back to 13th Dec 1999, where I found this email by Tim Hochberg: https://mail.python.org/pipermail/types-sig/1999-December/000281.html suggesting the arrow symbol for all type declarations. This appears to be the first suggestion of the arrow symbol for type annotations in Python. I am surprised that type checking was being discussed so long ago. Python was not even a decade old, and if my calculations are correct, the versions at the time would have been 1.5.2 and 1.6.0. But I am especially amazed that the choice of symbol seems to have been accepted with very little argument or debate about alternative colours for the bike-shed. I can't find any suggestions for alternative symbols such as `=>` `-->` `==>` `->>` etc, and very little for keywords such as `as`. The day after Tim posted, Tony Lownds suggested `as` and then immediately suggested using Tim's arrow symbol for the return type only: https://mail.python.org/pipermail/types-sig/1999-December/000335.html and then as far as I can tell, we've never looked back. If there is anyone whose memory reaches back that far, does that sound right? -- Steve

5 4

[Release management] schedule for renaming the default branch
by Pablo Galindo Salgado 11 Mar '21

11 Mar '21

Hi, I am writing on behalf of the Python Release Management team. The Steering Council has requested the RM team to schedule and perform the necessary changes to rename the default branch from master to main. # The changes What follows is the technical description of the changes and the timeline. In order to keep this thread focused on this particular aspect, if you wish to discuss anything related to the change itself, please, open a new email thread or reuse an existing one. - The change will be executed ***when beta 1 is released***, as the beta 1 release requires some branching engineering already to create the 3.10 branch and point 3.11 to the new one as well as changing CI, buildbots...etc ** *This is scheduled for Monday, 2021-05-03**.* - The CI will be adapted to work with the new "main" branch. - The buildbots will be adapted to work with the new "main" branch. - Branch protection rules will be adapted. - The different bots will be adapted by the respective bot maintainer teams. - All the URLs that point to master in the README and other places will be adapted to point to main instead (notice this is not strictly necessary because GitHub redirects automatically). Notice that the renaming will automatically: - Re-target any open pull requests - Update any draft releases based on the branch - Move any branch protection rules that explicitly reference the old name - Show a notice to repository contributors, maintainers, and admins on the repository homepage with instructions to update local copies of the repository - Show a notice to contributors who git push to the old branch - Redirect web requests for the old branch name to the new branch name - Return a "Moved Permanently" response in API requests for the old branch name Check this <https://github.com/github/renaming> for more information. # What you need to do? You just need to update your local clone after the branch name changes. From the local clone of the repository on a computer, run the following commands to update the name of the default branch. $ git branch -m master main $ git fetch origin $ git branch -u origin/main main Apart from that, you should update any local script or command that uses the name "master" to use the name "main". Regards from windy London, Pablo Galindo Salgado

4 6

Steering Council update for February
by Pablo Galindo Salgado 10 Mar '21

10 Mar '21

Hi everyone, The Steering Council just published the community update for February: https://github.com/python/steering-council/blob/main/updates/2021-02-steeri… As a reminder, we'll are trying to keep this up monthly. As you can see we are mainly focusing on clearing the PEP backlog and to address ongoing efforts and time-sensitive issues. Here you can find the text for the update: February 01 - After more deliberation and consideration of all available information, the Steering Council accepted the Pattern Matching PEPs. The Steering Council agreed that high-quality documentation is crucial in this feature and therefore its presence should be required before the release. A response in the name of the Steering Council will be sent to python-dev addressing the decision and the Steering Council view of the process. - The Steering Council discussed Debian's Python distro issues. The Steering Council will collect and communicate where the concerns are to the Debian maintainers. Thomas started a draft of the communication that the Steering Council will review, complete and sign-off. <https://github.com/python/steering-council/blob/main/updates/2021-02-steeri…>February 08 - The Steering Council started the discussion of PEP 651. It was decided that the group will leave this open for next week to better deliberate and consider more information. - The Steering Council discussed the ongoing work on porting types in the standard library to heap-types. It was decided that through Pablo, the Steering Council will ask the core developers driving those changes to create an informational PEP and not to make any more changes in this area after beta 1, as per our general policy. - The Steering Council discussed adding a TOML module to the standard library. It was decided that maintainers should write a PEP. On the topic of the standard library, it was agreed that the Steering Council should present at the PyCon US 2021 Language Summit on the future of the standard library and Brett is going to gather data on what PRs are tied to which module, which modules are imported and used the most, commit churn to help start the planning so we can make data-driven discussions and decisions. - The acceptance notice for PEP 634 will be sent from the Steering Council email, and Thomas will send rejection notices to other competing PEPs that are therefore rejected. <https://github.com/python/steering-council/blob/main/updates/2021-02-steeri…>February 15 [ The SC could not meet this week due to holidays in the US and Canada, and the impossibility to find a common replacement date in the week ] <https://github.com/python/steering-council/blob/main/updates/2021-02-steeri…>February 22 - The Steering Council discussed PEP 651 request and has decided to reject it. An email with the rationale will be sent to the author and python-dev. - Ezio joined the Steering Council meeting today to give an update on the GitHub Migration. GitHub was dormant during the holiday months. Ezio and GH had a productive meeting a couple of weeks ago. He is working on the tool that will convert bpo issues into a format that the GH tool will accept. He will also work on a community update once the test repo is ready. Another sync up has been scheduled between Ezio and the SC on March 29th. - The Steering Council discussed renaming the master branch to main and the consensus was that we should do that. The group is going to discuss the timeline and how to approach this with other repositories under the Python organization in some future meeting. - The Steering Council discussed the Debian situation. The group discussed ways to approach the situation and how to coordinate with Debian maintainers so it can benefit the Python community at large. It was decided that the steering council will email the Debian maintainers to try to reach some common ground and discuss how to proceed. Regards from cloudy London, Pablo Galindo Salgado

25 41