Mailman 3 July 2019 - Python-Dev

Removing dead bytecode vs reporting syntax errors
by Pablo Galindo Salgado 08 Jul '19

08 Jul '19

Hi, Recently, we moved the optimization for the removal of dead code of the form if 0: .... to the ast so we use JUMP bytecodes instead (being completed in PR14116). The reason is that currently, any syntax error in the block will never be reported. For example: if 0: return if 1: pass else: return while 0: return at module level do not raise any syntax error (just some examples), In https://bugs.python.org/issue37500 it was reported that after that, code coverage will decrease as coverage.py sees these new bytecodes (even if they are not executed). In general, the code object is a bit bigger and the optimization now it requires an JUMP instruction to be executed, but syntax errors are reported. The discussion on issue 37500 is about if we should prioritize the optimization or the correctness of reporting syntax errors. In my opinion, SyntaxErrors should be reported with independence of the value of variables (__debug__) or constant as is a property of the code being written not of the code being executed. Also, as CPython is the reference implementation of Python, the danger here is that it could be interpreted that this optimization is part of the language and its behavior should be mirrored in every other Python implementation. Elsewhere we have always prioritize correctness over speed or optimizations. I am writing this email to know what other people think. Should we revert the change and not report Syntax Errors on optimized blocks? Someone sees a viable way of reporting the errors and not emitting the bytecode for these block? Regards, Pablo

12 17

Steering Council Update for July 2019
by Carol Willing 08 Jul '19

08 Jul '19

I've posted an update from the Steering Council to our repo: https://github.com/python/steering-council/blob/master/updates/2019-07-08_s… I will also link to this on python-dev and on Discourse (discuss.python.org ). For completeness, below is the full text. # Steering Council Update ## Date: 2019-07-08 Steering Council updates will be posted irregularly and as needed. We provide these updates to foster open and transparent communication about Steering Council activity. We strive to post at least once every month. # Message from the Steering Council Sorry we've been silent for a while! With PyCon in Cleveland, the Language Summit, Sprints, PEP activity, and a Python 3.8 beta release, it's been a busy and productive May and June. Thank you all for your contributions. Below are some of the outcomes of our weekly Steering Council conversations. --- ## Mandate This section organizes Steering Council (SC) activity and projects using the mandates listed in PEP 13. ### Language > Maintain the quality and stability of the Python language and CPython interpreter - Inspired by Russell Keith-Magee's PyCon keynote about Black Swan events, the Steering Council is looking at what may impact Python for the next decade. We have been discussing this within the Steering Council and writing up some thoughts on major challenges facing Python. We'll continue to edit and polish this vision document and share it when we are ready for wider comment. ### Contributors > Make contributing as accessible, inclusive, and sustainable as possible - **Communications channels:** We are very pleased with the move of python-dev, etc. to Mailman 3. We now have a modern UI and easy search across mailing lists. Just a reminder to recap where announcements and conversations are taking place: - To reach core committers specifically, we will use python-committers(a)python.org. - To reach the entire Python developer community, we will use python-dev(a)python.org. - For specific requests to the SC (e.g., PEP reviews), please use our public GitHub tracker at https://github.com/python/steering-council/issues. - To reach just the SC, you can email us at steering-council(a)python.org. - We will also occasionally use Discourse, at https://discuss.python.org (for example, Discourse is useful for polls and votes). ### PEPs > Establish appropriate decision-making processes for PEPs - To request a PEP review, please file an issue on the [SC issue tracker](https://github.com/python/steering-council/issues). PEP highlights include: - PEP 570, "Python Positional-Only Parameters", by Larry Hastings, Pablo Galindo and others. *Appointed Guido van Rossum as BD.* "Completed." - PEP 574, "Pickle protocol 5 with out-of-band data", Antoine Pitrou. *Appointed Nick Coghlan as BD.* "Marked Final." - PEPs 576, 579, 580, 590 (competing PEPs on C function call optimizations by Mark Shannon and Jeroen Demeyer; note that PEP 576 is withdrawn in favor of PEP 590). *Appointed Petr Viktorin as BD.* "Accepted 590." - PEP 578, "Python Runtime Audit Hooks", Steve Dower. *Appointed Christian Heimes as BD.* "Landed, about to be marked Final." ### Interaction with PSF > Formalize and maintain the relationship between the core team and the PSF - We began discussions about fundraising ideas for CPython projects and administrative support. - A [donation page]([https://www.python.org/psf/donations/python-dev/](https://www.python… was created by the PSF and was linked from the [CPython repo]([https://github.com/python/cpython](https://github.com/python/cpython…. Any funds that are donated will be used for Core Developers to attend the core development sprints (to start; future possibilities are dependent on the amount of funds gathered). - At the Steering Council's recommendation, the PSF also is looking at hiring a Project Manager to manage communication and some logistics for the 2020 Python 2.7 End of Life. - The PSF Code of Conduct Workgroup is working on a revision of the CoC and its approval by the PSF board. Brett and Carol serve on the Workgroup. ### Governance > Seek consensus among contributors and the core team before acting in a formal capacity, > Act as a "court of final appeal" for decisions where all other methods have failed. - The weekly SC meeting cadence (Tuesdays 3-4pm US West Coast time) has been working out well. --- ## Reference This reference section summarizes the Steering Council's mandate and powers. ### Mandate (PEP 13) The steering council shall work to: - Maintain the quality and stability of the Python language and CPython interpreter, - Make contributing as accessible, inclusive, and sustainable as possible, - Formalize and maintain the relationship between the core team and the PSF, - Establish appropriate decision-making processes for PEPs, - Seek consensus among contributors and the core team before acting in a formal capacity, - Act as a "court of final appeal" for decisions where all other methods have failed. ### Powers (PEP 13) The council has broad authority to make decisions about the project. For example, they can: - Accept or reject PEPs - Enforce or update the project's code of conduct - Work with the PSF to manage any project assets - Delegate parts of their authority to other subcommittees or processes

2 3

Summary of Python tracker Issues
by Python tracker 05 Jul '19

05 Jul '19

ACTIVITY SUMMARY (2019-06-28 - 2019-07-05) 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 7068 (+14) closed 42192 (+53) total 49260 (+67) Open issues with patches: 2838 Issues opened (49) ================== #29312: Use FASTCALL in dict.update() https://bugs.python.org/issue29312 reopened by inada.naoki #34602: python3 resource.setrlimit strange behaviour under macOS https://bugs.python.org/issue34602 reopened by ned.deily #35605: backported patch requires new sphinx, minimum sphinx version w https://bugs.python.org/issue35605 reopened by steve.dower #37390: Generate table of audit events for docs https://bugs.python.org/issue37390 reopened by steve.dower #37424: subprocess.run timeout does not function if shell=True and cap https://bugs.python.org/issue37424 reopened by gregory.p.smith #37444: Differing exception between builtins and importlib when import https://bugs.python.org/issue37444 opened by brett.cannon #37445: Some FormatMessageW() calls use FORMAT_MESSAGE_FROM_SYSTEM wit https://bugs.python.org/issue37445 opened by ZackerySpytz #37446: Undefined behavior in Python/hamt.c https://bugs.python.org/issue37446 opened by ZackerySpytz #37448: obmalloc: radix tree for tracking arena address ranges https://bugs.python.org/issue37448 opened by nascheme #37449: Move ensurepip off of pkgutil and to importlib.resources https://bugs.python.org/issue37449 opened by brett.cannon #37451: Remove redudant test code in _testcapimodule.c https://bugs.python.org/issue37451 opened by shihai1991 #37452: Microsoft store package has an invalid ExecutablePath registry https://bugs.python.org/issue37452 opened by Fredrik Mellbin #37454: Clarify docs for math.log1p() https://bugs.python.org/issue37454 opened by rhettinger #37455: asyncio.run() error related to finalizing async generators https://bugs.python.org/issue37455 opened by samfrances #37456: FAQ says positional arguments aren't a thing https://bugs.python.org/issue37456 opened by SoniEx2 #37458: ast: Different FormattedValue expressions have same col_offset https://bugs.python.org/issue37458 opened by Weijar Z #37461: email.parser.Parser hang https://bugs.python.org/issue37461 opened by Guido #37465: Incorrect documentation for `s#` arguments in C API argument p https://bugs.python.org/issue37465 opened by enrico #37468: Don't install wininst*.exe on non-Windows platforms https://bugs.python.org/issue37468 opened by vstinner #37471: mmap module: add MAP_ALIGNED_SUPER FreeBSD constant https://bugs.python.org/issue37471 opened by devnexen #37473: importlib: Remove libregrtest hack: "We import importlib *ASAP https://bugs.python.org/issue37473 opened by vstinner #37474: Should Py_Initialize() control the floating point mode? https://bugs.python.org/issue37474 opened by vstinner #37475: What is urllib.request.urlcleanup() function? https://bugs.python.org/issue37475 opened by vstinner #37476: Adding a unit test of unicode in test_unicode.py https://bugs.python.org/issue37476 opened by shihai1991 #37478: Docs: Method os.chdir() does not mention errors that can be ra https://bugs.python.org/issue37478 opened by aeros167 #37479: IntEnum __format__ behavior can't be overridden through __str_ https://bugs.python.org/issue37479 opened by jason.curtis #37480: add ptpython to list of alternate interpreters https://bugs.python.org/issue37480 opened by zjayv #37482: Email address display name fails with both encoded words and s https://bugs.python.org/issue37482 opened by bsiem #37483: Add PyObject_CallOneArg() https://bugs.python.org/issue37483 opened by jdemeyer #37484: Use PY_VECTORCALL_ARGUMENTS_OFFSET for __exit__ https://bugs.python.org/issue37484 opened by jdemeyer #37487: PyList_GetItem() document regarding index https://bugs.python.org/issue37487 opened by 杨昆仑 #37488: Document the "gotcha" behaviors in utcnow() and utcfromtimesta https://bugs.python.org/issue37488 opened by p-ganssle #37489: pickling instance which inherited from Exception with keyword https://bugs.python.org/issue37489 opened by liugang93 #37490: poor documentation for .startswith, .endswith https://bugs.python.org/issue37490 opened by v+python #37491: IndexError in get_bare_quoted_string https://bugs.python.org/issue37491 opened by maxking #37495: socket.inet_aton parsing issue on some libc versions https://bugs.python.org/issue37495 opened by Dominik Czarnota #37496: Support annotations in signature strings. https://bugs.python.org/issue37496 opened by eric.snow #37497: Add inspect.Signature.from_text(). https://bugs.python.org/issue37497 opened by eric.snow #37498: request.urlopen(), memory leak? https://bugs.python.org/issue37498 opened by neonene #37499: test_gdb.test_pycfunction should use dedicated test functions https://bugs.python.org/issue37499 opened by p-ganssle #37500: 3.8.0b2 no longer optimizes away "if 0:" ? https://bugs.python.org/issue37500 opened by nedbat #37501: Test failures when CPython is built without docstrings https://bugs.python.org/issue37501 opened by ZackerySpytz #37502: Fix default argument handling for buffers argument in pickle.l https://bugs.python.org/issue37502 opened by Markus Mohrhard #37504: 3.8 b2 now requires sphinx2, but only has documented 1.8 https://bugs.python.org/issue37504 opened by doko #37505: Early auditing broken https://bugs.python.org/issue37505 opened by christian.heimes #37506: os.mkdir creates invalid folder when path string has trailing https://bugs.python.org/issue37506 opened by hollyroberts #37507: multiprocessing: Add a stop() method to ForkServer https://bugs.python.org/issue37507 opened by vstinner #37508: A wrong return type in memory.rst https://bugs.python.org/issue37508 opened by shihai1991 #37509: OSError preadv() https://bugs.python.org/issue37509 opened by YoSTEALTH Most recent 15 issues with no replies (15) ========================================== #37509: OSError preadv() https://bugs.python.org/issue37509 #37508: A wrong return type in memory.rst https://bugs.python.org/issue37508 #37507: multiprocessing: Add a stop() method to ForkServer https://bugs.python.org/issue37507 #37498: request.urlopen(), memory leak? https://bugs.python.org/issue37498 #37496: Support annotations in signature strings. https://bugs.python.org/issue37496 #37491: IndexError in get_bare_quoted_string https://bugs.python.org/issue37491 #37489: pickling instance which inherited from Exception with keyword https://bugs.python.org/issue37489 #37488: Document the "gotcha" behaviors in utcnow() and utcfromtimesta https://bugs.python.org/issue37488 #37487: PyList_GetItem() document regarding index https://bugs.python.org/issue37487 #37482: Email address display name fails with both encoded words and s https://bugs.python.org/issue37482 #37480: add ptpython to list of alternate interpreters https://bugs.python.org/issue37480 #37476: Adding a unit test of unicode in test_unicode.py https://bugs.python.org/issue37476 #37473: importlib: Remove libregrtest hack: "We import importlib *ASAP https://bugs.python.org/issue37473 #37451: Remove redudant test code in _testcapimodule.c https://bugs.python.org/issue37451 #37449: Move ensurepip off of pkgutil and to importlib.resources https://bugs.python.org/issue37449 Most recent 15 issues waiting for review (15) ============================================= #37508: A wrong return type in memory.rst https://bugs.python.org/issue37508 #37502: Fix default argument handling for buffers argument in pickle.l https://bugs.python.org/issue37502 #37501: Test failures when CPython is built without docstrings https://bugs.python.org/issue37501 #37484: Use PY_VECTORCALL_ARGUMENTS_OFFSET for __exit__ https://bugs.python.org/issue37484 #37483: Add PyObject_CallOneArg() https://bugs.python.org/issue37483 #37482: Email address display name fails with both encoded words and s https://bugs.python.org/issue37482 #37480: add ptpython to list of alternate interpreters https://bugs.python.org/issue37480 #37479: IntEnum __format__ behavior can't be overridden through __str_ https://bugs.python.org/issue37479 #37476: Adding a unit test of unicode in test_unicode.py https://bugs.python.org/issue37476 #37468: Don't install wininst*.exe on non-Windows platforms https://bugs.python.org/issue37468 #37461: email.parser.Parser hang https://bugs.python.org/issue37461 #37451: Remove redudant test code in _testcapimodule.c https://bugs.python.org/issue37451 #37448: obmalloc: radix tree for tracking arena address ranges https://bugs.python.org/issue37448 #37445: Some FormatMessageW() calls use FORMAT_MESSAGE_FROM_SYSTEM wit https://bugs.python.org/issue37445 #37440: httplib should enable post-handshake authentication for TLS 1. https://bugs.python.org/issue37440 Top 10 most discussed issues (10) ================================= #37483: Add PyObject_CallOneArg() https://bugs.python.org/issue37483 28 msgs #37421: Some tests leak temporary files https://bugs.python.org/issue37421 17 msgs #29312: Use FASTCALL in dict.update() https://bugs.python.org/issue29312 10 msgs #10945: bdist_wininst depends on MBCS codec, unavailable on non-Window https://bugs.python.org/issue10945 8 msgs #19696: Merge all (non-syntactic) import-related tests into test_impor https://bugs.python.org/issue19696 8 msgs #37380: subprocess.Popen._cleanup() "The handle is invalid" error when https://bugs.python.org/issue37380 8 msgs #37490: poor documentation for .startswith, .endswith https://bugs.python.org/issue37490 8 msgs #37495: socket.inet_aton parsing issue on some libc versions https://bugs.python.org/issue37495 8 msgs #18374: ast.parse gives wrong position (col_offset) for some BinOp-s https://bugs.python.org/issue18374 7 msgs #37500: 3.8.0b2 no longer optimizes away "if 0:" ? https://bugs.python.org/issue37500 7 msgs Issues closed (54) ================== #5115: Extend subprocess.kill to be able to kill process groups https://bugs.python.org/issue5115 closed by gregory.p.smith #19960: zlib skipped when building 2.7 on macOS without /usr/include i https://bugs.python.org/issue19960 closed by ned.deily #26534: subprocess.check_output with shell=True ignores the timeout https://bugs.python.org/issue26534 closed by gregory.p.smith #30154: subprocess.run with stderr connected to a pipe won't timeout w https://bugs.python.org/issue30154 closed by gregory.p.smith #30754: textwrap.dedent mishandles empty lines https://bugs.python.org/issue30754 closed by gregory.p.smith #31783: Race condition in ThreadPoolExecutor when scheduling new jobs https://bugs.python.org/issue31783 closed by bquinlan #32178: Some invalid email address groups cause an IndexError instead https://bugs.python.org/issue32178 closed by cheryl.sabella #32179: Empty email address in headers triggers an IndexError https://bugs.python.org/issue32179 closed by cheryl.sabella #32934: logging.handlers.BufferingHandler capacity is unclearly specif https://bugs.python.org/issue32934 closed by vinay.sajip #36168: DOC: Fix capitalization in string.rst https://bugs.python.org/issue36168 closed by CuriousLearner #36422: tempfile.TemporaryDirectory() removes entire directory tree ev https://bugs.python.org/issue36422 closed by giampaolo.rodola #36689: docs: os.path.commonpath raises ValueError for different drive https://bugs.python.org/issue36689 closed by asvetlov #36904: Implement _PyStack_UnpackDict() with a single allocation https://bugs.python.org/issue36904 closed by jdemeyer #36924: Simplify implementation of classmethod_descriptor.__call__ https://bugs.python.org/issue36924 closed by jdemeyer #36926: Implement methoddescr_call without _PyMethodDef_RawFastCallDic https://bugs.python.org/issue36926 closed by jdemeyer #36974: Implement PEP 590 https://bugs.python.org/issue36974 closed by petr.viktorin #37199: Test suite fails when Ipv6 is unavailable https://bugs.python.org/issue37199 closed by asvetlov #37208: Weird exception behaviour in ProcessPoolExecutor https://bugs.python.org/issue37208 closed by bquinlan #37221: PyCode_New API change breaks backwards compatibility policy https://bugs.python.org/issue37221 closed by petr.viktorin #37231: Optimize calling special methods https://bugs.python.org/issue37231 closed by jdemeyer #37250: C files generated by Cython set tp_print to 0: PyTypeObject.tp https://bugs.python.org/issue37250 closed by ncoghlan #37294: concurrent.futures.ProcessPoolExecutor and multiprocessing.poo https://bugs.python.org/issue37294 closed by bquinlan #37335: Improve encoding alias handling in locale coercion tests https://bugs.python.org/issue37335 closed by kulikjak #37346: Documentation of os not using OSError subclasses https://bugs.python.org/issue37346 closed by asvetlov #37357: mbox From line wrongly detected https://bugs.python.org/issue37357 closed by eric.smith #37366: Add an "onitem" callback parameter to shutil.rmtree() https://bugs.python.org/issue37366 closed by giampaolo.rodola #37369: Issue with pip in venv on Powershell in Windows https://bugs.python.org/issue37369 closed by steve.dower #37403: Recommend .venv for virtual environment names https://bugs.python.org/issue37403 closed by brett.cannon #37416: If threading is not imported from the main thread it sees the https://bugs.python.org/issue37416 closed by pitrou #37427: sorted, list.sort reject non-boolean objects with __bool__() a https://bugs.python.org/issue37427 closed by terry.reedy #37441: Fix a param error in exceptions.rst https://bugs.python.org/issue37441 closed by xiang.zhang #37443: Python Returns NoneType when convert a string to a list and us https://bugs.python.org/issue37443 closed by SilentGhost #37447: Nested For Loop in Python not working as Expected after cnt=21 https://bugs.python.org/issue37447 closed by xtreak #37450: Generalize Euclidean distance function in the math module to M https://bugs.python.org/issue37450 closed by rhettinger #37453: Symlink creation on Windows should work without privilege esca https://bugs.python.org/issue37453 closed by jaraco #37457: python3.7 re.split() module bug https://bugs.python.org/issue37457 closed by SilentGhost #37459: importlib docs improperly reference get_resource_loader() https://bugs.python.org/issue37459 closed by barry #37460: importlib.import_module("test.test_curses") could not import b https://bugs.python.org/issue37460 closed by yoonghm #37462: Default starting directory for os.walk() https://bugs.python.org/issue37462 closed by aeros167 #37463: ssl.match_hostname() ignores extra string after whitespace in https://bugs.python.org/issue37463 closed by christian.heimes #37464: multiple comparison https://bugs.python.org/issue37464 closed by SilentGhost #37466: Move casting prompt after its validation in _raw_input() https://bugs.python.org/issue37466 closed by myungsekyo #37467: sys.excepthook (PyErr_Display) does crash with SyntaxError whi https://bugs.python.org/issue37467 closed by vstinner #37469: Make it explicit that logging QueueHandler / QueueListener acc https://bugs.python.org/issue37469 closed by vinay.sajip #37470: Make it explicit what happens when using a bounded queue with https://bugs.python.org/issue37470 closed by vinay.sajip #37472: Remove Lib/test/outstanding_bugs.py https://bugs.python.org/issue37472 closed by vstinner #37477: NamedTemporaryFile can hang on windows https://bugs.python.org/issue37477 closed by earonesty #37481: Deprecate bdist_wininst: use bdist_wheel instead https://bugs.python.org/issue37481 closed by vstinner #37485: dataclass __foo__ methods inheritance is not working https://bugs.python.org/issue37485 closed by eric.smith #37486: pathlib.Path('.').parent is itself rather than parent https://bugs.python.org/issue37486 closed by pitrou #37492: should email.utils.parseaddr treat a@b. as invalid email ? https://bugs.python.org/issue37492 closed by jpic #37493: Use _PyObject_CallNoArg() in a few more places https://bugs.python.org/issue37493 closed by jdemeyer #37494: Call asyncio Future in scope https://bugs.python.org/issue37494 closed by asvetlov #37503: Queue.join(): Broken example in documentation https://bugs.python.org/issue37503 closed by misterunknown

1 0

Change SystemError to NOT inherit from Exception
by Jeroen Demeyer 04 Jul '19

04 Jul '19

A SystemError is typically raised from C to indicate serious bugs in the application which shouldn't normally be caught and handled. It's used for example for NULL arguments where a Python object is expected. So in some sense, SystemError is the Python equivalent of a segmentation fault. Since these exceptions should typically not be handled in a try/except Exeption block, I suggest to make SystemError inherit directly from BaseException instead of Exception.

3 4

strip behavior provides inconsistent results with certain strings
by dan＠bauman.space 03 Jul '19

03 Jul '19

Anyone experienced anything like this? The behavior seems consistent but unexpected. python 3.6 on both windows (10) and linux (ubuntu 18.04) seem to exhibit the same odd behavior. something about a docker-image looking string seems to trigger this behavior. The behavior seems as expected for other strings. Python 3.6.5 |Anaconda, Inc.| (default, Mar 29 2018, 13:32:41) [MSC v.1900 64 bit (AMD64)] on win32 Type "help", "copyright", "credits" or "license" for more information. sample_string_1 = "namespace/something-plugin-extra:dev" print(sample_string_1.lstrip("namespace/something-plugin")) xtra:dev print(sample_string_1.lstrip("namespace/something-plug")) xtra:dev print(sample_string_1.lstrip("namespace/something-plu")) xtra:dev print(sample_string_1.lstrip("namespace/something-pl")) ugin-extra:dev sample_string_1 = "namespace/something-plugxx-extra:dev" print(sample_string_1.lstrip("namespace/something-plugin")) xx-extra:dev print(sample_string_1.lstrip("namespace/something-plug")) xx-extra:dev print(sample_string_1.lstrip("namespace/something-plu")) xx-extra:dev print(sample_string_1.lstrip("namespace/something-pl")) ugxx-extra:dev Python 3.6.5 (default, Apr 1 2018, 05:46:30) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. sample_string_1 = "namespace/something-plugin-extra:dev" print(sample_string_1.lstrip("namespace/something-plugin")) xtra:dev print(sample_string_1.lstrip("namespace/something-plug")) xtra:dev print(sample_string_1.lstrip("namespace/something-plu")) xtra:dev print(sample_string_1.lstrip("namespace/something-pl")) ugin-extra:dev sample_string_1 = "namespace/something-plugxx-extra:dev" print(sample_string_1.lstrip("namespace/something-plugin")) xx-extra:dev print(sample_string_1.lstrip("namespace/something-plug")) xx-extra:dev print(sample_string_1.lstrip("namespace/something-plu")) xx-extra:dev print(sample_string_1.lstrip("namespace/something-pl")) ugxx-extra:dev

15 21

[RELEASE] Python 3.7.4rc2 is now available for testing
by Ned Deily 02 Jul '19

02 Jul '19

Python 3.7.4rc2 is now available. 3.7.4rc2 is the second release preview of the next maintenance release of Python 3.7, the latest feature release of Python. Assuming no further critical problems are found prior to 2019-07-08, no code changes are planned between this release candidate and the final release. The release candidate is intended to give you the opportunity to test the new security and bug fixes in 3.7.4. Because of the small number of changes between rc1, the original release preview, and rc2, we are planning on an abbreviated exposure cycle so we can get the final release to you as soon as possible. We strongly encourage you to test your projects and report issues found to https://bugs.python.org/ as soon as possible. Please keep in mind that this is a preview release and, thus, is not recommended for production environments. You can find the release files, a link to the changelog, and more information here: https://www.python.org/downloads/release/python-374rc2/ -- Ned Deily nad(a)python.org -- []

1 0

[RELEASE] Python 3.6.9 security-fix release is now available
by Ned Deily 02 Jul '19

02 Jul '19

Python 3.6.9 is now available. 3.6.9 is the first security-only-fix release of Python 3.6. Python 3.6 has now entered the security fix phase of its life cycle. Only security-related issues are accepted and addressed during this phase. We plan to provide security fixes for Python 3.6 as needed through 2021, five years following its initial release. Security fix releases are produced periodically as needed and only provided in source code form; binary installers are not provided. We urge you to consider upgrading to the latest release of Python 3.7, the current fully-supported version. You can find the release files, a link to the changelog, and more information here: https://www.python.org/downloads/release/python-369/ https://www.python.org/downloads/ -- Ned Deily nad(a)python.org -- []

1 0

Annoying user on GitHub
by Guido van Rossum 02 Jul '19

02 Jul '19

There's a user on GitHub ('experimentalles') who has created random PRs on several projects (e.g. https://github.com/python/peps/pull/1116). Can we ban them? The PRs look the work of a vandal or a bot, not of a clueless human. -- --Guido van Rossum (python.org/~guido) *Pronouns: he/him/his **(why is my pronoun here?)* <http://feministing.com/2015/02/03/how-using-they-as-a-singular-pronoun-can-…>

9 9

PEP 581 has been updated with "Downsides of GitHub" section
by Mariatta 02 Jul '19

02 Jul '19

Hi, I've updated PEP 581 yesterday, adding the "Downsides of GitHub" section. https://www.python.org/dev/peps/pep-0581/#downsides-of-github Other parts of the PEP has also been updated to reflect recent changes to roundup/bpo that happened after PEP 581's acceptance, for example: - ability to automatically close issues when a PR has been merged. This was added to bpo after PEP 581's acceptance. I've also created an issue in devguide so that this can be documented: https://github.com/python/devguide/issues/502 - Availability of REST API in Roundup/bpo. REST API has been requested in Roundup for several years, and there was no activity on it since 2016. REST API has been incorporated to Roundup in February 2019, but it is not yet incorporated to bpo. - Availability of CI for Roundup/bpo. There is CI running on Roundup's unofficial GitHub mirror. But pull requests aren't happening there. Mercurial patches are still how you would contribute to it. Please re-read PEP 581 in its entirety. I plan to update PEP 588 sometime this weekend or next, to incorporate the discussions and suggestions brought up in Python Language Summit 2019:( http://pyfound.blogspot.com/2019/05/mariatta-wijaya-lets-use-github-issues.… ) Some of the items brought up during the language summit: - we're talking with The PSF to get a professional PM to handle the migration (mentioned by steering council members). - we should create a playground GitHub issue tracker and copy 100s of tickets from bpo to there (suggested by Barry Warsaw) - we should be updating devguide ahead of the actual migration, so core developers and release managers have time to review and learn the new workflow. (suggested by Ned Deily) - Devguide should have a section for "how to triage issues on GitHub" (sorry I forgot who said this, but it is in my note) - Some people liked having screencast of "how to do X on GitHub" (similar to miss-islington's Youtube demo https://www.youtube.com/watch?v=p85YtKKLNno). It would be good if we can do more of them. (suggested by Davin Potts) Thanks. ᐧ

13 14

Re: strip behavior provides inconsistent results with certain strings
by Brian Skinn 02 Jul '19

02 Jul '19

It seems to me that the desired behavior is closest to 'str.replace()' out of all the options, just with the constraint of being limited to either the start or the end of the string. (Thus the .lreplace() and .rreplace() option suggested by Glenn earlier in the thread.) The minimal change (which actually also seems pretty general) seems to me to be adding *only_start* and *only_end* keyword arguments to str.replace(), both defaulting to False. If, e.g., *only_start* is passed True, each repetition of *old* at the start of *str* is replaced by a copy of *new*, with the number of replacements limited by the existing optional *count*. Similar behavior for *only_end*=True. Probably best to raise a ValueError(?) if both *only_start*=True and *only_end*=True? Taking swapping a file extension as an example of a particular transformation of interest, it would be achieved with something like s.replace(".htm", ".html", only_end=True). -Brian ---------------------------------------------------------------------- > > Date: Tue, 2 Jul 2019 14:33:57 +1000 > From: Chris Angelico <rosuav(a)gmail.com> > Subject: [Python-Dev] Re: strip behavior provides inconsistent results > with certain strings > To: python-dev <python-dev(a)python.org> > Message-ID: > <CAPTjJmqFsWof= > x64_vDYm9jaJ0z9N19Te7DK+naVvoXOih7SJQ(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > On Tue, Jul 2, 2019 at 2:28 PM Glenn Linderman <v+python(a)g.nevcal.com> > wrote: > > > >> A method could raise instead of returning the string as-is if the > prefix is not really a prefix. How often is this needed? The most common > end deletions are whitespace, which the current .strip handles correctly. > > > > raising wouldn't be helpful in most of the situations where I use this > logic... it would require a more complex flow control than the if > startswith path in the current situation. > > > > Yes, I use strip more frequently, but if startswith: chop_prefix > operation (and the other end too) happens an awful lot. > > If the method accepts a tuple of prefixes and will remove the first > one found (or the longest, or whatever) and raises if none found, you > could get the "chop only if present" behaviour by including an empty > string as one of the possible prefixes. > > ChrisA > > >

1 0