python-committers March 2018

python-committers@python.org

11 participants
13 discussions

GitHub: remove the "needs backport to 3.5" label?

by Victor Stinner

Hi, Python 3.5 entered security fix only mode. Should we now remove the "needs backport to 3.5" label? Other security only branches don't have this label neither (3.3 and 3.4). Victor

1 year, 11 months

Licences for PyCharm and other JetBrains products

by Vinay Sajip

Recently I received 20 one-year licenses from JetBrains for the PyCharm IDE (Professional) and other JetBrains products (the licenses cover their "All Products Pack") for use in Python development. There are 11 licenses available - of the licenses I asked for last year, nine people took them up, so those are in use and come out of the allocation of 20. Those of you who took up the licences last time should find that the tools continue to work normally. The licences expire on 27 November 2018. If any others of you are interested in using these licenses, let me know off-list and I will forward the license access details to you. To access the licenses, you will need to have (or create) a JetBrains account. Regards, Vinay Sajip

2 years, 7 months

[RELEASE] Python 3.7.0b3 is now available for testing

by Ned Deily

On behalf of the Python development community and the Python 3.7 release team, I'm happy to announce the availability of Python 3.7.0b3. b3 is the third of four planned beta releases of Python 3.7, the next major release of Python, and marks the end of the feature development phase for 3.7. You can find Python 3.7.0b3 here: https://www.python.org/downloads/release/python-370b3/ Among the new major new features in Python 3.7 are: * PEP 538, Coercing the legacy C locale to a UTF-8 based locale * PEP 539, A New C-API for Thread-Local Storage in CPython * PEP 540, UTF-8 mode * PEP 552, Deterministic pyc * PEP 553, Built-in breakpoint() * PEP 557, Data Classes * PEP 560, Core support for typing module and generic types * PEP 562, Module __getattr__ and __dir__ * PEP 563, Postponed Evaluation of Annotations * PEP 564, Time functions with nanosecond resolution * PEP 565, Show DeprecationWarning in __main__ * PEP 567, Context Variables Please see "What’s New In Python 3.7" for more information. Additional documentation for these features and for other changes will be provided during the beta phase. https://docs.python.org/3.7/whatsnew/3.7.html Beta releases are intended to give you the opportunity to test new features and bug fixes and to prepare their projects to support the new feature release. We strongly encourage you to test your projects with 3.7 during the beta phase and report issues found to https://bugs.python.org as soon as possible. While the release is feature complete entering the beta phase, it is possible that features may be modified or, in rare cases, deleted up until the start of the release candidate phase (2018-05-21). Our goal is have no ABI changes after beta 3 and no code changes after rc1. To achieve that, it will be extremely important to get as much exposure for 3.7 as possible during the beta phase. Attention macOS users: there is a new installer variant for macOS 10.9+ that includes a built-in version of Tcl/Tk 8.6. This variant is expected to become the default version when 3.7.0 releases. Check it out! We welcome your feedback. As of 3.7.0b3, the legacy 10.6+ installer also includes a built-in Tcl/Tk 8.6. Please keep in mind that this is a preview release and its use is not recommended for production environments. The next planned release of Python 3.7 will be 3.7.0b4, currently scheduled for 2018-04-30. More information about the release schedule can be found here: https://www.python.org/dev/peps/pep-0537/ -- Ned Deily nad(a)python.org -- []

3 years, 4 months

[RELEASE] Python 3.6.5 is now available

by Ned Deily

Python 3.6.5 is now available. 3.6.5 is the fifth maintenance release of Python 3.6, which was initially released in 2016-12 to great interest. Detailed information about the changes made in 3.6.5 can be found in its change log. You can find Python 3.6.5 and more information here: https://www.python.org/downloads/release/python-365/ See the "What’s New In Python 3.6" document for more information about features included in the 3.6 series. Detailed information about the changes made in 3.6.5 can be found in the change log here: https://docs.python.org/3.6/whatsnew/changelog.html#python-3-6-5-final Attention macOS users: as of 3.6.5, there is a new additional installer variant for macOS 10.9+ that includes a built-in version of Tcl/Tk 8.6. This variant is expected to become the default variant in future releases. Check it out! The next maintenance release is expected to follow in about 3 months, around the end of 2018-06. Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation: https://www.python.org/psf/ -- Ned Deily nad(a)python.org -- []

3 years, 4 months

IMPORTANT - 3.7.0b3 cutoff / 3.7.0 ABI freeze

by Ned Deily

Just a reminder that 3.7.0b3 is almost upon us. Please get your feature fixes, bug fixes, and documentation updates in before 2018-03-26 ~23:59 Anywhere on Earth (UTC-12:00). That's a little over 3.5 days from now. IMPORTANT: We are now entering the final phases of 3.7.0. After the tagging for 3.7.0b3, the intention is that the ABI for 3.7.0 is frozen. After next week's 3.7.0b3, there will only be two more opportunities planned for changes prior to 3.7.0 final: - 2018-04-30 3.7.0 beta 4 - 2018-05-31 3.7.0 release candidate As I've noted in previous communications, we need to start locking down 3.7.0 so that our downstream users, that is, third-party package developers, Python distributors, and end users, can test their code with confidence that the actual release of 3.7.0 will hold no unpleasant surprises. So after 3.7.0b3, you should treat the 3.7 branch as if it is already released and in maintenance mode. That means you should only push the kinds of changes that are appropriate for a maintenance release: non-ABI-changing bug and feature fixes and documentation updates. If you find a problem that requires an ABI-altering or other significant user-facing change (for example, something likely to introduce an incompatibility with existing users' code or require rebuilding of user extension modules), please make sure to set the b.p.o issue to "release blocker" priority and describe there why you feel the change is necessary. If you are reviewing PRs for 3.7 (and please do!), be on the lookout for and flag potential incompatibilities (we've all made them). Thanks again for all of your hard work towards making 3.7.0 yet another great release! --Ned -- Ned Deily nad(a)python.org -- []

3 years, 4 months

Wanting to merge my first PR under github - a bit of advice

by Paul Moore

Hi, Cheryl Sabella kindly migrated a patch I'd put on bpo some time ago but forgotten about onto github. The PR (#6158) is ready to go (I think) but this is the first time since the migration to github that I've done a merge, and I'm not quite sure what the workflow is :-( I didn't see much in the devguide (which covers how to write a PR, how to test it etc, but not so much how to merge it, unless I missed something, or it's so simple that the little I did find is all that's needed!) Am I right that all I need to do is hit "Squash and Merge", tidy up the commit message, and that's it for master? This is a doc change which should probably go into 3.7 - so I presume I just add the "Needs backport" label and Miss Islington does the rest? (I assume doc fixes are still OK for 3.7 at this point?) Is there anything else I've missed? (Do I need another approver? I'm assuming not, for a doc fix). Sorry for the dumb questions - if I've missed a glaringly obvious explanation, feel free to let me know. I'm just a little nervous that it's *so* simple I feel I must have missed something! Paul PS Thanks to everyone who has worked on the new github workflow. What I've done so far has been really straightforward, and if I'm right in what I think I need to do above, then you've made the rest of the process beautifully simple, too!

3 years, 4 months

Re: [python-committers] Save the date: Core developer sprints

by M.-A. Lemburg

On 18.03.2018 17:44, Steve Dower wrote: > If PyCon UK was in the calendar, then it would be cheating, but since > September 2018 appears totally open... :) Hmm, looks like the UK folks forgot to submit this. I've added it now. > Larry – hopefully being close to home (#1) means you can join for the > first few days. You won’t force someone else to miss out completely, > we'll have room. > > > > Top-posted from my Windows phone > > > > *From: *M.-A. Lemburg <mailto:mal@egenix.com> > *Sent: *Sunday, March 18, 2018 5:50 > *To: *Larry Hastings <mailto:larry@hastings.org>; > python-committers(a)python.org <mailto:python-committers@python.org> > *Subject: *Re: [python-committers] Save the date: Core developer sprints > > > > On 18.03.2018 03:16, Larry Hastings wrote: > >> > >> > >> On 03/07/2018 09:25 PM, Steve Dower wrote: > >>> So far, I have locked in dates and a building. Assuming no disasters, > >>> we will have Microsoft Building 20 > >>> > <https://www.bing.com/maps/?pc=W8AP&FORM=MAPXSH&where1=47.643699,-122.131305…> > >>> for our (almost) exclusive use from *September 10^th until the 14^th > >>> *. This is a set aside building for guests, which should mean no NDAs > >>> are required, and we’ll have a large space to use with a small kitchen > >>> and a few conference rooms. > >> > >> FWIW this butts up against PyCon UK 2018, which starts Saturday > >> September 15th and runs for five days. I suppose it's getting harder > >> and harder to throw a dart at a wall calendar and land on a date which > >> *doesn't* have a PyCon running. But still, I can think of one person > >> who might have otherwise planned on attending both.* > > You can use the Python event calendar to improve your dart skills :-) > > > > https://wiki.python.org/moin/PythonEventsCalendar#Available_Calendars > > > > (or is this cheating ?) > > > > -- > > Marc-Andre Lemburg > > eGenix.com > > > > Professional Python Services directly from the Experts (#1, Mar 18 2018) > >>>> Python Projects, Coaching and Consulting ... http://www.egenix.com/ > >>>> Python Database Interfaces ... http://products.egenix.com/ > >>>> Plone/Zope Database Interfaces ... http://zope.egenix.com/ > > ________________________________________________________________________ > > > > ::: We implement business ideas - efficiently in both time and costs ::: > > > > eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 > > D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg > > Registered at Amtsgericht Duesseldorf: HRB 46611 > > http://www.egenix.com/company/contact/ > > http://www.malemburg.com/ > > > > _______________________________________________ > > python-committers mailing list > > python-committers(a)python.org > > https://mail.python.org/mailman/listinfo/python-committers > > Code of Conduct: https://www.python.org/psf/codeofconduct/ > > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Experts (#1, Mar 18 2018) >>> Python Projects, Coaching and Consulting ... http://www.egenix.com/ >>> Python Database Interfaces ... http://products.egenix.com/ >>> Plone/Zope Database Interfaces ... http://zope.egenix.com/ ________________________________________________________________________ ::: We implement business ideas - efficiently in both time and costs ::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ http://www.malemburg.com/

3 years, 4 months

Re: [python-committers] Save the date: Core developer sprints

by Larry Hastings

On 03/07/2018 09:25 PM, Steve Dower wrote: > So far, I have locked in dates and a building. Assuming no disasters, > we will have Microsoft Building 20 > <https://www.bing.com/maps/?pc=W8AP&FORM=MAPXSH&where1=47.643699,-122.131305…> > for our (almost) exclusive use from *September 10^th until the 14^th > *. This is a set aside building for guests, which should mean no NDAs > are required, and we’ll have a large space to use with a small kitchen > and a few conference rooms. FWIW this butts up against PyCon UK 2018, which starts Saturday September 15th and runs for five days. I suppose it's getting harder and harder to throw a dart at a wall calendar and land on a date which *doesn't* have a PyCon running. But still, I can think of one person who might have otherwise planned on attending both.* //arry * me /

3 years, 4 months

Announcing: signups are open for the 2018 Python Language Summit

by Larry Hastings

It’s that time again: time to start thinking about the Python Language Summit! The 2018 summit will be held on Wednesday, May 9, from 10am to 4pm, at the Huntington Convention Center in Cleveland, Ohio, USA. Your befezzled and befuddled hosts Barry and Larry will once more be behind the big desk in front. The summit’s purpose is to disseminate information and spark conversation among core Python developers. It’s our yearly opportunity to get together for an in-person discussion, to review interesting developments of the previous year and hash out where we’re going next. And we have lots to talk about! 3.7 is in beta, and we've all collectively started work on 3.8 too. As before, we’re using Google Forms to collect signups. Signups are open now; the deadline to sign up is Wednesday April 18th, 2018 (AoE). Please do us a favor and sign up sooner rather than later. The signup form is simpler this year--I bet most people can be done in less than two minutes! One difference from last year: there are now *two* forms. The first form is for signing up to attend (the "Request For Invitation" form), and the second form is for proposing a talk. Please note: if you want to present, you still need to fill out the Request For Invitation form too. (Yes, it's more complicated this way, sorry. But having both on the same form kind of enforced a one-to-one mapping, and it's really a many-to-many mapping: one person might propose multiple talks, and one talk might have multiple presenters. Overall this should be less complicated.) You can find links to *both* forms on the official Python Language Summit 2018 page: https://us.pycon.org/2018/events/language-summit/ A few notes: * There will be lightning talks! Signups will only be available during the Language Summit itself. * You don’t need to be registered for PyCon in order to attend the summit! * We’ll have badge ribbons for Language Summit participants, which we’ll hand out at the summit room in the morning. * We're inviting Jake Edge from Linux Weekly News to attend the summit and provide press coverage again. Jake’s done a phenomenal job of covering the last few summits, providing valuable information not just for summit attendees, but also for the Python community at large. Jake’s coverage goes a long way toward demystifying the summit, while remaining respectful of confidential information that’s deemed “off the record” ahead of time by participants. One big final note (please read this!): When using Google Forms, you /can/ edit your responses later! When you fill out the form and hit Submit, the submission complete page (the one that says "Thanks for playing!") will have a link on it labeled "Edit your response". BOOKMARK THIS LINK! You can use this link at /any time/ to edit your response, up to the point that signups close on April 18th. Keep in mind, you'll need to bookmark each response independently: once for signing up to attend ("Request For Invitation"), and once for each talk proposal you submit. Again, /please/ be sure to save this bookmark yourself--we don't know how to find the link for you later if you don't save it. We hope to see you at the summit! [BL]arry

3 years, 4 months

[RELEASE] Python 3.6.5rc1 is now available for testing

by Ned Deily

Announcing the immediate availability of Python 3.6.5 release candidate 1! Python 3.6.5rc1 is the first release candidate for Python 3.6.5, the next maintenance release of Python 3.6. While 3.6.5rc1 is a preview release and, thus, not intended for production environments, we encourage you to explore it and provide feedback via the Python bug tracker (https://bugs.python.org). 3.6.5 is planned for final release on 2018-03-26 with the next maintenance release expected to follow in about 3 months. You can find Python 3.6.5rc1 and more information here: https://www.python.org/downloads/release/python-365rc1/ Attention macOS users: as of 3.6.5rc1, there is a new additional installer variant for macOS 10.9+ that includes a built-in version of Tcl/Tk 8.6. This variant is expected to become the default variant in future releases. Check it out! -- Ned Deily nad(a)python.org -- []

3 years, 4 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

python-committers March 2018