Mailman 3 November 2017 - Python-Dev

Remove typing from the stdlib
by Victor Stinner 07 Nov '17

07 Nov '17

Hi, 2017-11-03 15:36 GMT+01:00 Guido van Rossum <guido(a)python.org>: > Maybe we should remove typing from the stdlib? > https://github.com/python/typing/issues/495 I'm strongly in favor on such move. My experience with asyncio in the stdlib is that users expect changes faster than the very slow release process of the stdlib (a release every 18 months in average). I saw many PEPs and discussion on the typing design (meta-classes vs regular classes), as if the typing is not stable enough to be part of the stdlib. The typing module is not used yet in the stdlib, so there is no technically reason to keep typing part of the stdlib. IMHO it's perfectly fine to keep typing and annotations out of the stdlib, since the venv & pip tooling is now rock solid ;-) Victor

17 35

Re: [Python-Dev] Proposal: go back to enabling DeprecationWarning by default
by Toshio Kuratomi 07 Nov '17

07 Nov '17

On Nov 7, 2017 5:47 AM, "Paul Moore" <p.f.moore(a)gmail.com> wrote: On 7 November 2017 at 13:35, Philipp A. <flying-sheep(a)web.de> wrote: > Sorry, I still don’t understand how any of this is a problem. > > If you’re an application developer, google “python disable > DeprecationWarning” and paste the code you found, so your users don’t see > the warnings. > If you’re a library developer, and a library you depend on raises > DeprecationWarnings without it being your fault, file an issue/bug there. > > For super-increased convenience in case 2., we could also add a convenience > API that blocks deprecation warnings raised from certain module or its > submodules. > Best, Philipp If you're a user and your application developer didn't do (1) or a library developer developing one of the libraries your application developer chose to use didn't do (2), you're hosed. If you're a user who works in an environment where moving to a new version of the application is administratively complex, you're hosed. As I say, the proposal prioritises developer convenience over end user experience. I don't agree with this characterisation. Even if we assume a user isn't going to fix a DeprecationWarning they still benefit: (1) if they're a sysadmin it will warn them that they need to be careful when upgrading a dependency. (2) if the developer never hears about the DeprecationWarning then it is ultimately the user who suffers when the tool they depend on breaks without warning so seeing and reporting the DeprecationWarning helps the end user. (3) if DeprecationWarnings are allowed to linger through multiple releases, it may tell the user about the quality of the software they're using. More information is helpful to end users. Developers are actually the ones that it inconveniences as we'll be the ones grumbling when an end user who hasn't evaluated the deprecation cycles of upstream projects as we have demand immediate changes for deprecations that are still years away from causing problems. But unlike end users, we do have the ability to solve that by turning those deprecations off in our code if we've done our due diligence (or even if we haven't done our due diligence). -Toshio

1 0

Partial support of a platform
by Victor Stinner 06 Nov '17

06 Nov '17

Hi, I see more and more proposed changes to fix some parts of the code to "partially" support a platform. I remember that 5 years ago, the CPython code was "full" of #ifdef and other conditional code to support various platforms, and I was happy when we succeeded to remove support for all these old platforms like OS/2, DOS or VMS. The PEP 11 has a nice description to get a *full* support of a new platform: https://www.python.org/dev/peps/pep-0011/ But the question here is more about "partial" support. While changes are usually short, I dislike applying them to Python 2.7 and/or Python 3.6, until a platform is fully support. I prefer to first see a platform fully supported to see how much changes are required and to make sure that we get someone involved to maintain the code (handle new issues). Example of platforms: MinGW, Cygwin, OpenBSD, NetBSD, xWorks RTOS, etc. But the way, is there an exhaustive list of platforms "officially" supported by CPython? Victor

5 10

Allow annotations using basic types in the stdlib?
by Victor Stinner 06 Nov '17

06 Nov '17

Hi, While discussions on the typing module are still hot, what do you think of allowing annotations in the standard libraries, but limited to a few basic types: * None * bool, int, float, complex * bytes, bytearray * str I'm not sure about container types like tuple, list, dict, set, frozenset. If we allow them, some developers may want to describe the container content, like List[int] or Dict[int, str]. My intent is to enhance the builtin documentation of functions of the standard library including functions implemented in C. For example, it's well known that id(obj) returns an integer. So I expect a signature like: id(obj) -> int Context: Tal Einat proposed a change to convert the select module to Argument Clinic: https://bugs.python.org/issue31938 https://github.com/python/cpython/pull/4265 The docstring currently documents the return like: --- haypo@selma$ pydoc3 select.epoll.fileno|cat Help on method_descriptor in select.epoll: select.epoll.fileno = fileno(...) fileno() -> int Return the epoll control file descriptor. --- I'm talking about "-> int", nice way to document that the function returns an integer. Problem: even if Argument Clinic supports "return converters" like "int", it doesn't generate a docstring with the return type. So I created the issue: "Support return annotation in signature for Argument Clinic" https://bugs.python.org/issue31939 But now I am confused between docstrings, Argument Clinic, "return converters", "signature" and "annotations"... R. David Murray reminded me the current policy: "the python standard library will not include type annotations, that those are provided by typeshed." While we are discussing removing (or not) typing from the stdlib (!), I propose to allow annotations in the stdlib, *but* only limited to the most basic types. Such annotations *shouldn't* have a significant impact on performances (startup time) or memory footprint. The expected drawback is that users can be surprised that some functions get annotations, while others don't. For example, os.fspath() requires a complex annotation which needs the typing module and is currently done in typeshed, whereas id(obj) can get its return type documented ("-> int"). What do you think? Victor

7 7

3.5.4 doesn't appear in changelog
by Antoine Pitrou 06 Nov '17

06 Nov '17

Hello, Is there a known reason why 3.5.4 doesn't appear in the changelogs at the bottom of https://docs.python.org/3.7/whatsnew/index.html ? (all releases until 3.5.3 do) Regards Antoine.

2 1

Re: [Python-Dev] Guarantee ordered dict literals in v3.7?
by Nathaniel Smith 05 Nov '17

05 Nov '17

On Nov 5, 2017 2:41 PM, "Paul Ganssle" <pganssle(a)gmail.com> wrote: I think the question of whether any specific implementation of dict could be made faster for a given architecture or even that the trade-offs made by CPython are generally the right ones is kinda beside the point. It's certainly feasible that an implementation that does not preserve ordering could be better for some implementation of Python, and the question is really how much is gained by changing the language semantics in such a way as to cut off that possibility. The language definition is not nothing, but I think it's easy to overestimate its importance. CPython does in practice provide ordering guarantees for dicts, and this solves a whole bunch of pain points: it makes json roundtripping work better, it gives ordered kwargs, it makes it possible for metaclasses to see the order class items were defined, etc. And we got all these goodies for better-than-free: the new dict is faster and uses less memory. So it seems very unlikely that CPython is going to revert this change in the foreseeable future, and that means people will write code that depends on this, and that means in practice reverting it will become impossible due to backcompat and it will be important for other interpreters to implement, regardless of what the language definition says. That said, there are real benefits to putting this in the spec. Given that we're not going to get rid of it, we might as well reward the minority of programmers who are conscientious about following the spec by letting them use it too. And there were multiple PEPs that went away when this was merged; no one wants to resurrect them just for hypothetical future implementations that may never exist. And putting it in the spec will mean that we can stop having this argument over and over with the same points rehashed for those who missed the last one. (This isn't aimed at you or anything; it's not your fault you don't know all these arguments off the top of your head, because how would you? But it is a reality of mailing list dynamics that rehashing this kind of thing sucks up energy without producing much.) MicroPython deviates from the language spec in lots of ways. Hopefully this won't need to be another one, but it won't be the end of the world if it is. -n

2 1

Official port of Python on EDK2
by Thiebaud Weksteen 03 Nov '17

03 Nov '17

Hi, UEFI has become the standard for firmware (BIOS) interface. Intel has provided an open source implementation under the name EDK2 (part of the TianoCore initiative) [1] for some time. This implementation has evolved significantly and now provides the functionalities of a small OS with a standard library similar to POSIX. In 2011, a port of Python 2.7.1 was added to the EDK2 repository [2]. This port then evolved to 2.7.2 which is still defined as the reference port [3]. In 2015, another port was added of Python 2.7.10 in parallel of 2.7.2 [4]. Since then, both implementations have diverged from upstream and know vulnerabilities have not been fixed. I would like to bring support for edk2 in the official Python repository to remediate this situation, that is officially support edk2 as a platform. Technically, there would be three main aspects for the on-boarding work: 1) Fix headers and source to resolve definition conflicts, similarly to ABS definition in [5]; 2) Add the edk2module.c [6] to handle platform-specific functionalities, similarly to the posixmodule.c; 3) Add the build configuration file [7] and necessary modifications within Python to handle the edk2 toolchain; This work would target the master branch (that is Python 3). I would be interested in hearing your thoughts on this idea. Thanks, Thiebaud [1] https://github.com/tianocore/edk2 [2] https://github.com/tianocore/edk2/commit/006fecd5a177b4b7b6b36fab6690bf2b2f… [3] https://github.com/tianocore/edk2/blob/master/AppPkg/Applications/Python/Py… [4] https://github.com/tianocore/edk2/commit/c8042e10763bca064df257547d04ae3dfc… [5] https://gist.github.com/tweksteen/ed516ca7ab7dfa8d18428f59d9c22a3e [6] https://github.com/tianocore/edk2/blob/master/AppPkg/Applications/Python/Ef… [7] https://github.com/tianocore/edk2/blob/master/AppPkg/Applications/Python/Py…

8 9

Summary of Python tracker Issues
by Python tracker 03 Nov '17

03 Nov '17

ACTIVITY SUMMARY (2017-10-27 - 2017-11-03) 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 6255 ( -5) closed 37431 (+54) total 43686 (+49) Open issues with patches: 2416 Issues opened (36) ================== #27456: asyncio: set TCP_NODELAY flag by default https://bugs.python.org/issue27456 reopened by yselivanov #31887: docs for email.generator are missing a comment on special mult https://bugs.python.org/issue31887 opened by dhke #31889: difflib SequenceMatcher ratio() still have unpredictable behav https://bugs.python.org/issue31889 opened by Siltaar #31892: ssl.get_server_certificate should allow specifying certificate https://bugs.python.org/issue31892 opened by hanno #31894: test_timestamp_naive failed on NetBSD https://bugs.python.org/issue31894 opened by serhiy.storchaka #31895: Native hijri calendar support https://bugs.python.org/issue31895 opened by haneef95 #31896: In function define class inherit ctypes.structure, and using c https://bugs.python.org/issue31896 opened by Yang Big #31897: Unexpected exceptions in plistlib.loads https://bugs.python.org/issue31897 opened by Ned Williamson #31898: Add a `recommended-packages.txt` file https://bugs.python.org/issue31898 opened by ncoghlan #31899: Ensure backwards compatibility with recommended packages https://bugs.python.org/issue31899 opened by ncoghlan #31900: localeconv() should decode numeric fields from LC_NUMERIC enco https://bugs.python.org/issue31900 opened by cstratak #31901: atexit callbacks only called for current subinterpreter https://bugs.python.org/issue31901 opened by Dormouse759 #31902: Fix col_offset for ast nodes: AsyncFor, AsyncFunctionDef, Asyn https://bugs.python.org/issue31902 opened by guoci #31903: `_scproxy` calls SystemConfiguration functions in a way that c https://bugs.python.org/issue31903 opened by Maxime Belanger #31904: Python should support VxWorks RTOS https://bugs.python.org/issue31904 opened by Brian Kuhl #31907: Clarify error message when attempting to call function via str https://bugs.python.org/issue31907 opened by mickey695 #31908: trace module cli does not write cover files https://bugs.python.org/issue31908 opened by Michael Selik #31910: test_socket.test_create_connection() failed with EADDRNOTAVAIL https://bugs.python.org/issue31910 opened by haypo #31911: Use malloc_usable_size() in pymalloc for realloc https://bugs.python.org/issue31911 opened by haypo #31912: PyMem_Malloc() should guarantee alignof(max_align_t) https://bugs.python.org/issue31912 opened by skrah #31913: forkserver could warn if several threads are running https://bugs.python.org/issue31913 opened by pitrou #31914: Document Pool.(star)map return type https://bugs.python.org/issue31914 opened by dilyan.palauzov #31916: ensurepip not honoring value of $(DESTDIR) - pip not installed https://bugs.python.org/issue31916 opened by multimiler #31920: pygettext ignores directories as inputfile argument https://bugs.python.org/issue31920 opened by Oleg Krasnikov #31921: Bring together logic for entering/leaving a frame in frameobje https://bugs.python.org/issue31921 opened by pdox #31922: Can't receive replies from multicast UDP with asyncio https://bugs.python.org/issue31922 opened by vxgmichel #31923: Misspelled "loading" in Doc/includes/sqlite3/load_extension.py https://bugs.python.org/issue31923 opened by davywtf #31924: Fix test_curses on NetBSD 8 https://bugs.python.org/issue31924 opened by serhiy.storchaka #31925: test_socket creates too many locks https://bugs.python.org/issue31925 opened by serhiy.storchaka #31927: Fix compiling the socket module on NetBSD 8 and other issues https://bugs.python.org/issue31927 opened by serhiy.storchaka #31930: IDLE: Pressing "Home" on Windows places cursor before ">>>" https://bugs.python.org/issue31930 opened by terry.reedy #31931: test_concurrent_futures: ProcessPoolSpawnExecutorTest.test_shu https://bugs.python.org/issue31931 opened by haypo #31932: setup.py cannot find vcversall.bat on MSWin 8.1 if installed i https://bugs.python.org/issue31932 opened by laranzu #31933: some Blake2 parameters are encoded backwards on big-endian pla https://bugs.python.org/issue31933 opened by oconnor663 #31934: Failure to build out of source from a not clean source https://bugs.python.org/issue31934 opened by xdegaye #31935: subprocess.run() timeout not working with grandchildren and st https://bugs.python.org/issue31935 opened by Martin Ritter Most recent 15 issues with no replies (15) ========================================== #31935: subprocess.run() timeout not working with grandchildren and st https://bugs.python.org/issue31935 #31934: Failure to build out of source from a not clean source https://bugs.python.org/issue31934 #31932: setup.py cannot find vcversall.bat on MSWin 8.1 if installed i https://bugs.python.org/issue31932 #31927: Fix compiling the socket module on NetBSD 8 and other issues https://bugs.python.org/issue31927 #31925: test_socket creates too many locks https://bugs.python.org/issue31925 #31924: Fix test_curses on NetBSD 8 https://bugs.python.org/issue31924 #31923: Misspelled "loading" in Doc/includes/sqlite3/load_extension.py https://bugs.python.org/issue31923 #31922: Can't receive replies from multicast UDP with asyncio https://bugs.python.org/issue31922 #31911: Use malloc_usable_size() in pymalloc for realloc https://bugs.python.org/issue31911 #31904: Python should support VxWorks RTOS https://bugs.python.org/issue31904 #31903: `_scproxy` calls SystemConfiguration functions in a way that c https://bugs.python.org/issue31903 #31902: Fix col_offset for ast nodes: AsyncFor, AsyncFunctionDef, Asyn https://bugs.python.org/issue31902 #31899: Ensure backwards compatibility with recommended packages https://bugs.python.org/issue31899 #31896: In function define class inherit ctypes.structure, and using c https://bugs.python.org/issue31896 #31889: difflib SequenceMatcher ratio() still have unpredictable behav https://bugs.python.org/issue31889 Most recent 15 issues waiting for review (15) ============================================= #31934: Failure to build out of source from a not clean source https://bugs.python.org/issue31934 #31933: some Blake2 parameters are encoded backwards on big-endian pla https://bugs.python.org/issue31933 #31927: Fix compiling the socket module on NetBSD 8 and other issues https://bugs.python.org/issue31927 #31924: Fix test_curses on NetBSD 8 https://bugs.python.org/issue31924 #31923: Misspelled "loading" in Doc/includes/sqlite3/load_extension.py https://bugs.python.org/issue31923 #31921: Bring together logic for entering/leaving a frame in frameobje https://bugs.python.org/issue31921 #31920: pygettext ignores directories as inputfile argument https://bugs.python.org/issue31920 #31910: test_socket.test_create_connection() failed with EADDRNOTAVAIL https://bugs.python.org/issue31910 #31908: trace module cli does not write cover files https://bugs.python.org/issue31908 #31904: Python should support VxWorks RTOS https://bugs.python.org/issue31904 #31903: `_scproxy` calls SystemConfiguration functions in a way that c https://bugs.python.org/issue31903 #31902: Fix col_offset for ast nodes: AsyncFor, AsyncFunctionDef, Asyn https://bugs.python.org/issue31902 #31900: localeconv() should decode numeric fields from LC_NUMERIC enco https://bugs.python.org/issue31900 #31897: Unexpected exceptions in plistlib.loads https://bugs.python.org/issue31897 #31887: docs for email.generator are missing a comment on special mult https://bugs.python.org/issue31887 Top 10 most discussed issues (10) ================================= #18835: Add PyMem_AlignedAlloc() https://bugs.python.org/issue18835 19 msgs #31630: math.tan has poor accuracy near pi/2 on OpenBSD and NetBSD https://bugs.python.org/issue31630 13 msgs #31897: Unexpected exceptions in plistlib.loads https://bugs.python.org/issue31897 9 msgs #31894: test_timestamp_naive failed on NetBSD https://bugs.python.org/issue31894 8 msgs #31626: Writing in freed memory in _PyMem_DebugRawRealloc() after shri https://bugs.python.org/issue31626 7 msgs #31895: Native hijri calendar support https://bugs.python.org/issue31895 7 msgs #31900: localeconv() should decode numeric fields from LC_NUMERIC enco https://bugs.python.org/issue31900 6 msgs #20182: Derby #13: Convert 50 sites to Argument Clinic across 5 files https://bugs.python.org/issue20182 5 msgs #31901: atexit callbacks only called for current subinterpreter https://bugs.python.org/issue31901 5 msgs #31908: trace module cli does not write cover files https://bugs.python.org/issue31908 5 msgs Issues closed (54) ================== #8070: Infinite loop in PyRun_InteractiveLoopFlags() if PyRun_Interac https://bugs.python.org/issue8070 closed by xdegaye #8548: Building on CygWin 1.7: PATH_MAX redefined https://bugs.python.org/issue8548 closed by berker.peksag #9667: NetBSD curses KEY_* constants https://bugs.python.org/issue9667 closed by serhiy.storchaka #9674: make install DESTDIR=/home/blah fails when the prefix specifie https://bugs.python.org/issue9674 closed by xdegaye #11383: compilation seg faults on insanely large expressions https://bugs.python.org/issue11383 closed by serhiy.storchaka #15037: curses.unget_wch and test_curses fail when linked with ncurses https://bugs.python.org/issue15037 closed by serhiy.storchaka #16994: collections.Counter.least_common https://bugs.python.org/issue16994 closed by serhiy.storchaka #20047: bytearray partition bug https://bugs.python.org/issue20047 closed by serhiy.storchaka #20064: PyObject_Malloc is not documented https://bugs.python.org/issue20064 closed by haypo #23699: Add a macro to ease writing rich comparisons https://bugs.python.org/issue23699 closed by ncoghlan #24291: Many servers (wsgiref, http.server, etc) can truncate large ou https://bugs.python.org/issue24291 closed by martin.panter #25293: Hooking Thread/Process instantiation in concurrent.futures. https://bugs.python.org/issue25293 closed by pitrou #25720: Fix curses module compilation with ncurses6 https://bugs.python.org/issue25720 closed by serhiy.storchaka #26618: _overlapped extension module of asyncio uses deprecated WSAStr https://bugs.python.org/issue26618 closed by berker.peksag #27666: "stack smashing detected" in PyCursesWindow_Box https://bugs.python.org/issue27666 closed by serhiy.storchaka #30333: test_multiprocessing_forkserver: poll() failed on AMD64 FreeBS https://bugs.python.org/issue30333 closed by haypo #30442: Skip test_xml_etree under coverage https://bugs.python.org/issue30442 closed by berker.peksag #30806: netrc.__repr__() is broken for writing to file https://bugs.python.org/issue30806 closed by inada.naoki #30824: Add mimetype for extension .json https://bugs.python.org/issue30824 closed by berker.peksag #31065: Documentation for Popen.poll is unclear https://bugs.python.org/issue31065 closed by berker.peksag #31095: Checking all tp_dealloc with Py_TPFLAGS_HAVE_GC https://bugs.python.org/issue31095 closed by berker.peksag #31245: Asyncio UNIX socket and SOCK_DGRAM https://bugs.python.org/issue31245 closed by yselivanov #31273: [2.7] unittest: Unicode support in TestCase.skip https://bugs.python.org/issue31273 closed by serhiy.storchaka #31298: Error when calling numpy.astype https://bugs.python.org/issue31298 closed by berker.peksag #31304: Update doc for starmap_async error_back kwarg https://bugs.python.org/issue31304 closed by Mariatta #31307: ConfigParser.read silently fails if filenames argument is a by https://bugs.python.org/issue31307 closed by berker.peksag #31308: forkserver process isn't re-launched if it died https://bugs.python.org/issue31308 closed by pitrou #31310: semaphore tracker isn't protected against crashes https://bugs.python.org/issue31310 closed by pitrou #31390: pydoc.Helper.keywords missing async and await https://bugs.python.org/issue31390 closed by berker.peksag #31629: Running test_curses on FreeBSD changes signal handlers https://bugs.python.org/issue31629 closed by haypo #31700: one-argument version for Generator.typing https://bugs.python.org/issue31700 closed by levkivskyi #31784: Implementation of the PEP 564: Add time.time_ns() https://bugs.python.org/issue31784 closed by haypo #31836: test_code_module fails after test_idle https://bugs.python.org/issue31836 closed by terry.reedy #31852: Crashes with lines of the form "async \" https://bugs.python.org/issue31852 closed by haypo #31858: IDLE: cleanup use of sys.ps1 and never set it. https://bugs.python.org/issue31858 closed by terry.reedy #31860: IDLE: Make font sample editable https://bugs.python.org/issue31860 closed by terry.reedy #31872: SSL BIO is broken for internationalized domains https://bugs.python.org/issue31872 closed by asvetlov #31881: subprocess.returncode not set depending on arguments to subpro https://bugs.python.org/issue31881 closed by nthompson #31883: Cygwin: heap corruption bug in wcsxfrm https://bugs.python.org/issue31883 closed by serhiy.storchaka #31888: Creating a UUID with a list throws bad exception https://bugs.python.org/issue31888 closed by serhiy.storchaka #31890: Please define the flag METH_STACKLESS for Stackless Python https://bugs.python.org/issue31890 closed by haypo #31891: Make curses compiling on NetBSD 7.1 and tests passing https://bugs.python.org/issue31891 closed by serhiy.storchaka #31893: Issues with kqueue https://bugs.python.org/issue31893 closed by serhiy.storchaka #31905: IPv4Networkcontains raises exception on None https://bugs.python.org/issue31905 closed by serhiy.storchaka #31906: String literals next to each other does not cause error https://bugs.python.org/issue31906 closed by Mariatta #31909: Missing definition of HAVE_SYSCALL_GETRANDOM https://bugs.python.org/issue31909 closed by Ilya.Kulakov #31915: (list).insert() not working https://bugs.python.org/issue31915 closed by steven.daprano #31917: Add time.CLOCK_PROF constant https://bugs.python.org/issue31917 closed by haypo #31918: Don't let all python code modify modules https://bugs.python.org/issue31918 closed by serhiy.storchaka #31919: Make curses compiling on OpenIndiana and tests passing https://bugs.python.org/issue31919 closed by serhiy.storchaka #31926: compile error when converting selectmodule to AC due to missin https://bugs.python.org/issue31926 closed by haypo #31928: DOC: Show sys.version_info as a named tuple https://bugs.python.org/issue31928 closed by csabella #31929: Raw strings create syntax error when last character is a singl https://bugs.python.org/issue31929 closed by barry #1447222: tkinter Dialog fails when more than four buttons are used https://bugs.python.org/issue1447222 closed by berker.peksag

1 0

Reorganizing re and curses related code
by Serhiy Storchaka 03 Nov '17

03 Nov '17

Currently the implementation of re and curses related modules is sparsed over several files: re: Lib/re.py Lib/sre_compile.py Lib/sre_constants.py Lib/sre_parse.py _sre: Modules/_sre.c Modules/sre_constants.h Modules/sre.h Modules/sre_lib.h _curses: Include/py_curses.h Modules/_cursesmodule.c Modules/_curses_panel.c I want to make the re module a package, and move sre_*.py files into it. Maybe later I'll add the sre_optimize.py file for separating optimization from parsing and compiling to an internal code. The original sre_*.py files will be left for compatibility for long time, but they will just import their content from the re package. _sre implementation will be moved into the Modules/_sre/ directory. This will just make them to be in one place and will decrease the number of files in the Modules/ directory. The implementations of the _curses and _curses_panel modules together with the common header file will be moved into the Modules/_curses/ directory. Excluding py_curses.h from the set of global headers will increase the speed of rebuilding when modify just the _curses implementation (I did this too much recent times). In future the implementation of menu and forms extensions will be added (the patch for menu has beed provided years ago). Since _cursesmodule.c is one of the largest file (it defines hundreds of functions), it may be worth to extract the implementation of the _curses.window class into a separate file. And I want to implement the support of "soft function-key labels". All this will increase the number of _curses related files to 7. curses already is a package. Since virtually all changes in these files at recent years have been made by me, I don't think this will harm other core developers. Are there any objections?

3 3

PEP 511 (code transformers) rejected
by Victor Stinner 02 Nov '17

02 Nov '17

Hi, I rejected my own PEP 511 "API for code transformers" that I wrote in January 2016: https://github.com/python/peps/commit/9d8fd950014a80324791d7dae3c130b1b64fd… Rejection Notice: """ This PEP was rejected by its author. This PEP was seen as blessing new Python-like programming languages which are close but incompatible with the regular Python language. It was decided to not promote syntaxes incompatible with Python. This PEP was also seen as a nice tool to experiment new Python features, but it is already possible to experiment them without the PEP, only with importlib hooks. If a feature becomes useful, it should be directly part of Python, instead of depending on an third party Python module. Finally, this PEP was driven was the FAT Python optimization project which was abandonned in 2016, since it was not possible to show any significant speedup, but also because of the lack of time to implement the most advanced and complex optimizations. """ Victor

4 6