[Python-Dev] Python 3.7.4rc1 (and 3.6.9rc1) cutoffs ahead, now set for 2019-06-17
https://discuss.python.org/t/python-3-7-4rc1-and-3-6-9rc1-cutoffs-ahead-now-set-for-2019-06-17/1824 A reminder: it is time for the next quarterly maintenance release of Python 3.7. The cutoff for **3.7.4rc1** had been scheduled for this coming Monday (2019-06-10) but many of us have been focused on feature code off for 3.8.0, which just took place a few days ago (yay!). So, to give us all a bit more time to attend to 3.7.x matters, I have moved the code cutoff a week, to **Monday 2019-06-17** by the end of day AOE. Please review open issues and ensure that any that you believe need to be addressed in 3.7.4 are either resolved or marked as a **release blocker**. Any assistance you can provide in helping resolve issues will be greatly appreciated! Following the rc1 cutoff, changes merged to the 3.7 branch will be released in 3.7.5 three months from now unless you mark the issue as a release blocker prior to **3.7.4 final**, planned for release on **2019-06-28**, and explain why the change should be cherry-picked into the final release. I am also scheduling for the same dates the rc1 and final releases of Python **3.6.9**, which is the first 3.6 security-fix-only source release since its final bugfix release, 3.6.8, six months ago. If there are any open security issues that you feel should be backported to 3.6, please get them in before its cutoff on **2019-06-17** AoE. Thanks to everyone who has been helping to ensure the continued success of Python 3.6 and 3.7! Our users truly appreciate it and are showing their confidence in us by the rapid adoption of these latest releases. Onward! P.S. I have recently updated the 3.7.x release schedule in PEP 537 to show tentative release dates for the rest of 3.7's bugfix phase. Like with 3.6, we plan to continue having 3.7.x bugfix releases every three months until 2020-06-27, two years after the initial release of 3.7.0. At that point, 3.7.x will enter its security-fix-only phase for an additional three years. https://www.python.org/dev/peps/pep-0537/ -- Ned Deily n...@python.org -- [] Python-Dev mailing list -- python-dev(a)python.org To unsubscribe send an email to python-dev-leave(a)python.org https://mail.python.org/mailman3/lists/python-dev.python.org/
[Python-Dev] Re: PEP 594: update 1
Perhaps if PEP 594 is seen to be moving ahead towards a slimmer Python (4?) stdlib, it might encourage the development of a PEP to take over maintenance of dead parrots. They might be recruited by the offer of some way to at least publish a supported bundle via the same (python.org) site that Python itself comes from. It would seem unfair to burden the PEP with promising an afterlife. That would raise quality assurance issues, though. If no such PEP emerges then the dead parrots will be buried and forgotten. I see little reason why we (Python users) shouldn't trust the collective python-dev wisdom on what ultimately belongs in stdlib, and heaven knows these aren't simple discussions. On Wed, Jun 5, 2019 at 6:56 PM Brett Cannon wrote: > > > On Tue, Jun 4, 2019 at 5:22 PM Victor Stinner wrote: > >> So what is happening for this PEP since Python 3.8 beta1 has been >> released? Is it too late for Python 3.8 or not? >> >> It seems like most people are confused by the intent of the PEP. IMHO >> it would be better to rewrite "Remove packages from the stdlib" as >> "Move some stdlib modules to PyPI". But that would require to rewrite >> some parts of the PEP to explain how modules are moved, who become the >> new maintainers, how to support modules both in stdlib (old Python >> versions) and in PyPI (new Python), etc. >> > > Correct, that is more than a title change but a shift in what the PEP's > final result is. And the title as it currently stands as the modules would > still be removed from the stdlib regardless of whether they end up on PyPI > or not. > Python-Dev mailing list -- python-dev(a)python.org > To unsubscribe send an email to python-dev-leave(a)python.org > Unsubscribe: > https://mail.python.org/mailman3/lists/python-dev.python.org/ Python-Dev mailing list -- python-dev(a)python.org To unsubscribe send an email to python-dev-leave(a)python.org https://mail.python.org/mailman3/lists/python-dev.python.org/
[Python-Dev] Re: python-ideas and python-dev migrated to Mailman 3/HyperKitty
Barry Warsaw wrote on 6/5/19 10:56 AM: On Jun 5, 2019, at 02:08, Victor Stinner wrote: Our kind postmasters Mark Sapiro and Abhilash Raj migrated python-ideas and python-dev mailing lists from Mailman 2 to Mailman 3 (running on Python 3 ;-))! Gosh, it warms my heart. :) Thank you Mark, Abhilash! -Barry Bravo! Mark and Abhilash, thank you so much. I'm so happy to be able to use Mailman 3 for all my searches :D Python-Dev mailing list -- python-dev(a)python.org To unsubscribe send an email to python-dev-leave(a)python.org https://mail.python.org/mailman3/lists/python-dev.python.org/
[Python-Dev] Re: python-ideas and python-dev migrated to Mailman 3/HyperKitty
On Jun 5, 2019, at 02:08, Victor Stinner wrote: > > Our kind postmasters Mark Sapiro and Abhilash Raj migrated > python-ideas and python-dev mailing lists from Mailman 2 to Mailman 3 > (running on Python 3 ;-))! Gosh, it warms my heart. :) Thank you Mark, Abhilash! -Barry signature.asc Description: Message signed with OpenPGP Python-Dev mailing list -- python-dev(a)python.org To unsubscribe send an email to python-dev-leave(a)python.org Unsubscribe: https://mail.python.org/mailman3/lists/python-dev.python.org/
[Python-Dev] Re: PEP 594: update 1
On Tue, Jun 4, 2019 at 5:22 PM Victor Stinner wrote: > So what is happening for this PEP since Python 3.8 beta1 has been > released? Is it too late for Python 3.8 or not? > > It seems like most people are confused by the intent of the PEP. IMHO > it would be better to rewrite "Remove packages from the stdlib" as > "Move some stdlib modules to PyPI". But that would require to rewrite > some parts of the PEP to explain how modules are moved, who become the > new maintainers, how to support modules both in stdlib (old Python > versions) and in PyPI (new Python), etc. > Correct, that is more than a title change but a shift in what the PEP's final result is. And the title as it currently stands as the modules would still be removed from the stdlib regardless of whether they end up on PyPI or not. Python-Dev mailing list -- python-dev(a)python.org To unsubscribe send an email to python-dev-leave(a)python.org Unsubscribe: https://mail.python.org/mailman3/lists/python-dev.python.org/
[Python-Dev] Re: python-ideas and python-dev migrated to Mailman 3/HyperKitty
On Wed, Jun 05, 2019 at 11:08:13AM +0200, Victor Stinner wrote: > Hi, > > Our kind postmasters Mark Sapiro and Abhilash Raj migrated > python-ideas and python-dev mailing lists from Mailman 2 to Mailman 3 > (running on Python 3 ;-))! Great! But email footers are currently broken: > Python-Dev mailing list -- python-dev@python.org > To unsubscribe send an email to python-dev-le...@python.org > %(web_page_url)slistinfo/%(_internal_name)s > Unsubscribe: %(user_optionsurl)s -- Steven ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org %(web_page_url)slistinfo/%(_internal_name)s Unsubscribe: %(user_optionsurl)s
[Python-Dev] Re: python-ideas and python-dev migrated to Mailman 3/HyperKitty
05.06.19 13:52, Serhiy Storchaka пише: 05.06.19 12:08, Victor Stinner пише: Our kind postmasters Mark Sapiro and Abhilash Raj migrated python-ideas and python-dev mailing lists from Mailman 2 to Mailman 3 (running on Python 3 ;-))! You can now enjoy HyperKitty, the new web UI to access the mailing lists: https://mail.python.org/archives/list/python-dev@python.org/ and https://mail.python.org/archives/list/python-id...@python.org/ Hurray! Tested the Gmane gateway: worked in both directions. ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org %(web_page_url)slistinfo/%(_internal_name)s Unsubscribe: %(user_optionsurl)s
[Python-Dev] Re: python-ideas and python-dev migrated to Mailman 3/HyperKitty
05.06.19 12:08, Victor Stinner пише: Our kind postmasters Mark Sapiro and Abhilash Raj migrated python-ideas and python-dev mailing lists from Mailman 2 to Mailman 3 (running on Python 3 ;-))! You can now enjoy HyperKitty, the new web UI to access the mailing lists: https://mail.python.org/archives/list/python-dev@python.org/ and https://mail.python.org/archives/list/python-id...@python.org/ Hurray! ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org %(web_page_url)slistinfo/%(_internal_name)s Unsubscribe: %(user_optionsurl)s
[Python-Dev] python-ideas and python-dev migrated to Mailman 3/HyperKitty
Hi, Our kind postmasters Mark Sapiro and Abhilash Raj migrated python-ideas and python-dev mailing lists from Mailman 2 to Mailman 3 (running on Python 3 ;-))! You can now enjoy HyperKitty, the new web UI to access the mailing lists: https://mail.python.org/archives/list/python-dev@python.org/ and https://mail.python.org/archives/list/python-id...@python.org/ Enhancements: * Ability to post an email directly on the web UI (open a new topic or reply to an existing topic) * Nicer "archives": profile photo (gravatar), thread view * New "Most Active" and "Most Popular" views of mailing lists * Statistics (note: it seems like stats on python-dev are not computed yet) * Single login/password to subscribe to multiple Python mailing lists * Simpler UI to subscribe/unsubscribe * More reliable "permalink" URLs to emails * And more! Many lists already migrated: speed, capi-sig, python-committers, etc. All lists hosted by Mailman3: https://mail.python.org/archives/ -- There are also http://discuss.python.org/ and https://python.zulipchat.com/ to discuss Python ;-) Victor -- Night gathers, and now my watch begins. It shall not end until my death. ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org %(web_page_url)slistinfo/%(_internal_name)s Unsubscribe: %(user_optionsurl)s
