[Python-Dev] Summary of Python tracker Issues
ACTIVITY SUMMARY (2019-10-25 - 2019-11-01) 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: open7091 (+25) closed 43325 (+51) total 50416 (+76) Open issues with patches: 2799 Issues opened (60) == #34975: start_tls() difficult when using asyncio.start_server() https://bugs.python.org/issue34975 reopened by icgood #38233: datetime.datetime.fromtimestamp have different behaviour on wi https://bugs.python.org/issue38233 reopened by p-ganssle #38590: argparse unexpected behavior with argument group inside mutual https://bugs.python.org/issue38590 opened by Tim Sanders #38591: Deprecate Process Child Watchers https://bugs.python.org/issue38591 opened by aeros #38592: Add pt-br to the language switcher at the Python docs website https://bugs.python.org/issue38592 opened by rougeth #38593: Python 3.7 does not catch infinite recursion for some values o https://bugs.python.org/issue38593 opened by Valentyn Tymofieiev #38594: importlib.metadata documentation deficiencies https://bugs.python.org/issue38594 opened by indygreg #38595: io.BufferedRWPair doc warning may need clarification https://bugs.python.org/issue38595 opened by rgov #38596: simple example give a Linux core dumped with atk-bridge https://bugs.python.org/issue38596 opened by catafest #38597: C Extension import limit https://bugs.python.org/issue38597 opened by Kevin Schlossser #38599: Deprecate creation of asyncio object when the loop is not runn https://bugs.python.org/issue38599 opened by asvetlov #38601: Couldn't able to install multiple python minor version in wind https://bugs.python.org/issue38601 opened by kkotari #38603: inspect.getdoc could examine the __class__ cell for dynamicall https://bugs.python.org/issue38603 opened by Antony.Lee #38605: [typing] PEP 563: Postponed evaluation of annotations: enable https://bugs.python.org/issue38605 opened by vstinner #38607: Document that cprofile/profile only profile the main thread https://bugs.python.org/issue38607 opened by benspiller #38608: Undocumented behavior that IsolatedAsyncioTestCase would enabl https://bugs.python.org/issue38608 opened by legnaleurc #38609: Trashcan mechanism segfault during interpreter finalization in https://bugs.python.org/issue38609 opened by ysnt27 #38610: use-after-free in list object function https://bugs.python.org/issue38610 opened by LCatro #38611: ElementTree.ParseError does not implement SyntaxError interfac https://bugs.python.org/issue38611 opened by jamercee #38613: Optimize some set operations in dictkeys object https://bugs.python.org/issue38613 opened by inada.naoki #38614: test_asyncio: test_communicate() failed on AMD64 FreeBSD Share https://bugs.python.org/issue38614 opened by vstinner #38615: imaplib has no timeout setting https://bugs.python.org/issue38615 opened by Jairo Llopis #38619: [Doc] UUID.hex is lowercase https://bugs.python.org/issue38619 opened by fov #38620: Shell python-config --includes returns the same path twice https://bugs.python.org/issue38620 opened by vstinner #38622: _ctypes.dlsym (py_dl_sym) does not trigger audit hooks https://bugs.python.org/issue38622 opened by tholl #38623: Python documentation should mention how to find site-packages https://bugs.python.org/issue38623 opened by bittner #38624: pathlib .suffix, .suffixes, .stem unexpected behavior for path https://bugs.python.org/issue38624 opened by inyeollee #38625: SpooledTemporaryFile does not seek correctly after being rolle https://bugs.python.org/issue38625 opened by graham.coster #38628: Issue with ctypes in AIX https://bugs.python.org/issue38628 opened by Ayappan #38629: float is missing __ceil__() and __floor__(), required by numbe https://bugs.python.org/issue38629 opened by bluetech #38630: subprocess.Popen.send_signal() should poll the process https://bugs.python.org/issue38630 opened by vstinner #38631: Replace Py_FatalError() with regular Python exceptions https://bugs.python.org/issue38631 opened by vstinner #38632: setup.py sdist should honor SOURCE_DATE_EPOCH https://bugs.python.org/issue38632 opened by zwol #38633: shutil.copystat fails with PermissionError in WSL https://bugs.python.org/issue38633 opened by pspeter #38634: Symbol resolution conflict when embeding python in an applicat https://bugs.python.org/issue38634 opened by serge-sans-paille #38635: Simplify decoding the ZIP64 extra field and make it tolerant t https://bugs.python.org/issue38635 opened by serhiy.storchaka #38636: IDLE regression: toggle tabs and change indent width functions https://bugs.python.org/issue38636 opened by Zero #38638: Backtrace of exit phase of context managers https://bugs.python.org/issue38638 opened by kuraga #38639: Optimize floor(), ceil() and trunc() for floats https://bugs.python.org/issue38639 opened by serhiy.storchaka #3
[Python-Dev] Re: Accepting PEP 602 -- Annual Release Cycle for Python
Did you weigh PEP 602 against PEP 605? Is there a summary of the strong points you found for each and how you decided for the former? Thank you Antoine. On Wed, 30 Oct 2019 19:26:35 - "Brett Cannon" wrote: > On behalf of the steering council I am happy to announce that as > BDFL-Delegate I am accepting PEP 602 to move us to an annual release schedule > (gated on a planned update; see below). > > The steering council thinks that having a consistent schedule every year when > we hit beta, RC, and final it will help the community: > > * Know when to start testing the beta to provide feedback > * Known when the expect the RC so the community can prepare their projects > for the final release > * Know when the final release will occur to coordinate their own releases (if > necessary) when the final release of Python occurs > * Allow core developers to more easily plan their work to make sure work > lands in the release they are targeting > * Make sure that core developers and the community have a shorter amount of > time to wait for new features to be released > > The acceptance is gated on Łukasz updating PEP 602 to reflect a planned shift > in scheduling (he's been busy with a release of Black): > > * 3 months for betas instead of 2 > * 2 months for RCs instead of 1 > > This was discussed on https://discuss.python.org in order to give the > community enough time to provide feedback in the betas while having enough > time to thoroughly test the RC and to prep for the final release so the delay > from Python's final release to any new project releases is minimal. It should > also fit into the release schedule of Linux distributions like Fedora better > than previously proposed so the distributions can test the RC when they start > preparing for their own October releases. If this turns out to be a mistake > after we try it out for Python 3.9 we can then discuss going back to longer > betas and shorter RCs for the release after that. This will not change when > feature development is cut off relative to PyCon US nor the core dev sprints > happening just before the final release or the alpha of the next version. > > To help people who cannot upgrade on an annual cycle, do note that: > > * PEP 602 now says that deprecations will last two releases which is two > years instead of the current 18 months > * Now that the stable ABI has been cleaned, extension modules should feel > more comfortable targeting the stable ABI which should make supporting newer > versions of Python much easier > > As part of the shift to a 2 year deprecation time frame I will be restarting > discussions around PEP 387 as BDFL-Delegate so we can have a more clear > deprecation and backwards-compatibility policy as well for those that find an > annual cycle too fast which will be updated to reflect this two year time > frame (head's up, Benjamin 😉). > > Thanks to Łukasz, Nick, and Steve for PEPs 602, 605, and 607 and everyone > else who provided feedback on those PEPs! > ___ > Python-Dev mailing list -- python-dev@python.org > To unsubscribe send an email to python-dev-le...@python.org > https://mail.python.org/mailman3/lists/python-dev.python.org/ > Message archived at > https://mail.python.org/archives/list/python-dev@python.org/message/KE7OS4PZASZMFTW2FP2MWZU5R4Q2QZKU/ > Code of Conduct: http://python.org/psf/codeofconduct/ ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/B2OZTVNI7HFQ5VIFVQWXHSFMR2WDDAK6/ Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] [RELEASED] Python 3.5.9 is released
On behalf of the Python development community, I'm slightly chagrined to announce the availability of Python 3.5.9. There were no new changes in version 3.5.9; 3.5.9 was released only because of a CDN caching problem, which resulted in some users downloading a prerelease version of the 3.5.8 .xz source tarball. Apart from the version number, 3.5.9 is identical to the proper 3.5.8 release. This new version is a source-only release. You can find Python 3.5.9 here: https://www.python.org/downloads/release/python-359/ Happy Halloween, /arry ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/5CXAJRF5SLODC5ETYWSWIT56IXHT7AIP/ Code of Conduct: http://python.org/psf/codeofconduct/
