[python-committers] Re: Please turn on 2FA/MFA support on your GitHub account

On 2/7/22 16:14, Victor Stinner wrote: On Tue, Feb 8, 2022 at 12:11 AM Brett Cannon wrote: And to be clear, you only need access to your 2FA solution when you log in; it's not a day-to-day action at all (I personally have not used my 2FA since the last time I logged into a new device for

[python-committers] Re: IMPORTANT: Python 3.10b2 release blockers

On 5/26/21 7:21 AM, Pablo Galindo Salgado wrote: Hi, Friendly reminder that the Python3.10 beta 2 is still blocked on: https://bugs.python.org/issue42972 Thanks for your help, Regards from stormy London, Pablo Galindo Salgado I took a quick look at

[python-committers] Re: PEP 563 and Python 3.10.

I commend the Steering Council for its wise decision.  I'm sure that once the Python community spends more time considering this issue, and innovating new solutions, we can come up with a path forward that'll be good news for everybody. Best wishes, //arry/ On 4/20/21 11:57 AM, Thomas

[python-committers] Re: Travis CI is no longer mandatory on Python pull requests

I don't know how the configuration on this stuff works.  But my dim understanding is: some automation from Github (that we own / configure / wrote) notices that we have a new checkin on a PR and kicks off the Travis CI build.  The problem is that sometimes the status of the Travis CI build

[python-committers] Re: Thank you Larry Hastings!

Thank you to the PSC and everybody else for your nice thoughts and kind words.  Glad to have helped out! Best wishes, //arry/ On 10/5/20 11:38 AM, Barry Warsaw wrote: They say being a Python Release Manager is a thankless job, so the Python Secret Underground (PSU), which emphatically

[python-committers] Farewell, Python 3.5

At last!  Python 3.5 has now officially reached its end-of-life. Since there have been no checkins or PRs since I tagged 3.5.10, 3.5.10 will stand as the final release in the 3.5 series. As with a similar announcement I wrote about eighteen months ago, I know we can all look back fondly on

[python-committers] [RELEASED] Python 3.5.10 is released

On behalf of the Python development community, I'm plesed to announce the availability of Python 3.5.10. Python 3.5 is in "security fixes only" mode.  This new version only contains security fixes, not conventional bug fixes, and it is a source-only release. Important Notice: The latest

[python-committers] [RELEASED] Python 3.5.10rc1 is released

On behalf of the Python development community, I'm pleased to finally announce the availability of Python 3.5.10rc1. Python 3.5 is in "security fixes only" mode.  This new version only contains security fixes, not conventional bug fixes, and it is a source-only release. Important Notice:

[python-committers] [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

[python-committers] [WARNING] Some users who downloaded the Python 3.5.8 .xz tarball got the wrong version

Due to awkward CDN caching, some users who downloaded the source code tarballs of Python 3.5.8 got a preliminary version instead of the final version.  As best as we can tell, this only affects the .xz release; there are no known instances of users downloading an incorrect version of the

[python-committers] [RELEASED] Python 3.5.8 is (finally) released

On behalf of the Python development community, I'm relieved to announce the availability of Python 3.5.8. Python 3.5 is in "security fixes only" mode.  This new version only contains security fixes, not conventional bug fixes, and it is a source-only release. You can find Python 3.5.8

[python-committers] [RELEASED] Python 3.5.8rc2 is released

On behalf of the Python development community, I'm relieved to announce the availability of Python 3.5.8rc2.  It's been a month after Python 3.5.8rc1, and since then we've added a small amount of new code to fix an API-level regression in http client, updated expat to 2.2.8, and upgraded the

[python-committers] Re: Timeline for 3.5.8

in a fix, or we need to downgrade the issue from Release Blocker. As I mention on the issue, depending on the complexity of the fix for this issue (if we go that route) I may do another rc before final. In a holding pattern, //arry/ On 9/1/19 11:53 AM, Larry Hastings wrote: Howdy howdy

[python-committers] [RELEASED] Python 3.5.8rc1 is released

On behalf of the Python development community, I'm chuffed to announce the availability of Python 3.5.8rc1. Python 3.5 is in "security fixes only" mode.  This new version only contains security fixes, not conventional bug fixes, and it is a source-only release. You can find Python

[python-committers] Timeline for 3.5.8

Howdy howdy.  Here's what I'm thinking for the next release of 3.5.  This week I'm going to merge / reject all the outstanding PRs for 3.5, then cut rc1 at the Python Core Dev sprints next week, either Monday (2019/9/9) or Tuesday (2019/9/10).  This isn't a lot of notice, but things have

[python-committers] Farewell, Python 3.4

It's with a note of sadness that I announce the final retirement of Python 3.4.  The final release was back in March, but I didn't get around to actually closing and deleting the 3.4 branch until this morning. Python 3.4 introduced many features we all enjoy in modern Python--the asyncio,

[python-committers] Python 3.4.10 is now available

On behalf of the Python development community, I'm proud--if slightly sad--to announce the availability of Python 3.4.10. Python 3.4.10 was released in "security fixes only" mode.  It only contains security fixes, not conventional bug fixes, and it is a source-only release. Python 3.4.10

[python-committers] Python 3.5.7 is now available

On behalf of the Python development community, I'm chuffed to announce the availability of Python 3.5.7. Python 3.5 is in "security fixes only" mode.  It only accepts security fixes, not conventional bug fixes, and the release is source-only. And you can find Python 3.5.7rc1 here:

Re: [python-committers] [Python-Dev] Last-minute request: please backport bpo-33329 fix to 3.4 and 3.5

On 3/4/19 2:29 AM, Joni Orponen wrote: On Sat, Mar 2, 2019 at 7:08 AM Larry Hastings <mailto:la...@hastings.org>> wrote: This bug in bpo-33329: https://bugs.python.org/issue33329 This is also potentially affecting PGO builds of 2.7 on Debian Buster with GCC. Somehow

[python-committers] [RELEASED] Python 3.4.10rc1 and Python 3.5.7rc1 are now available

On behalf of the Python development community, I'm chuffed to announce the availability of Python 3.4.10rc1 and Python 3.5.7rc1. Both Python 3.4 and 3.5 are in "security fixes only" mode.  Both versions only accept security fixes, not conventional bug fixes, and both releases are

Re: [python-committers] Last-minute request: please backport bpo-33329 fix to 3.4 and 3.5

on the tracker.  I hope to release my RCs later today.  (Right now I'm stuck due to an unrelated problem--permissions problem, resulting from recent server changes behind the scenes.) Enjoy your time off, //arry/ On 3/2/19 6:55 AM, Antoine Pitrou wrote: Hi Larry, Le 02/03/2019 à 07:05, Larry

[python-committers] Last-minute request: please backport bpo-33329 fix to 3.4 and 3.5

This bug in bpo-33329: https://bugs.python.org/issue33329 was fixed for 3.6+, but it also affects 3.4 and 3.5.  The bug is that with newer versions of glibc--which I'm pretty sure has shipped on all major Linux distros by now--the test suite may send signals that are invalid somehow.  As

Re: [python-committers] Proposed dates for Python 3.4.10 and Python 3.5.7

My thanks to Miro and (especially!) Victor for quickly putting together those lovely PRs.  I've now merged everything outstanding for 3.4 and 3.5 except this: https://github.com/python/cpython/pull/10994 It's a backport of LibreSSL 2.7.0 support for 3.5.  This is something I believe

[python-committers] Proposed dates for Python 3.4.10 and Python 3.5.7

Howdy howdy!  It's time to make the next bugfix release of 3.5--and the /final/ release /ever/ of Python 3.4. Here's the schedule I propose: 3.4.10rc1 and 3.5.7rc1 - Saturday March 2 2019 3.4.10 final and 3.5.7 final - Saturday March 16 2019 What's going in these releases?  Not much. 

Re: [python-committers] discuss.python.org participation

<http://discuss.python.org>.  For example Benjamin Peterson, Larry Hastings, Raymond Hettinger, Stefan Krah, Terry Reedy. I believe Larry is currently busy so he might simply have not taken the time (and will be occupied into I believe November). You kids!  Yeah, I was just on a two-week

Re: [python-committers] Winding down 3.4

If they're really all wontfix, maybe we should mark them as wontfix, thus giving 3.4 a sendoff worthy of its heroic stature. Godspeed, and may a flight of angels sing thee to thy rest, //arry/ On 08/20/2018 05:52 AM, Victor Stinner wrote: > "shutil copy* unsafe on POSIX - they preserve

[python-committers] Winding down 3.4

We of the core dev community commit to supporting Python releases for five years.  Releases get eighteen months of active bug fixes, followed by three and a half years of security fixes.  Python 3.4 turns 5 next March--at which point we'll stop supporting it, and I'll retire as 3.4 release

[python-committers] [RELEASED] Python 3.4.9 and Python 3.5.6 are now available

On behalf of the Python development community, I'm happy to announce the availability of Python 3.4.9 and Python 3.5.6. Both Python 3.4 and 3.5 are in "security fixes only" mode.  Both versions only accept security fixes, not conventional bug fixes, and both releases are source-only. You

[python-committers] [RELEASED] Python 3.4.9rc1 and Python 3.5.6rc1 are now available

On behalf of the Python development community, I'm pleased to announce the availability of Python 3.4.9rc1 and Python 3.5.6rc1. Both Python 3.4 and 3.5 are in "security fixes only" mode.  Both versions only accept security fixes, not conventional bug fixes, and both releases are

[python-committers] 3.4.9rc1 and 3.5.6rc1 slipping by one day to Thursday July 19 2018

I was working with Serhiy on fixing the documentation for some bytecodes in 3.5 (GH-8338) and time got away from me.  They'll both be out later today, Thursday July 19 2018. *yawn,* //arry/ ___ python-committers mailing list

Re: [python-committers] Transfer of power

On 07/13/2018 04:20 PM, Steve Dower wrote: On 13Jul2018 1600, Larry Hastings wrote: I disagree.  My proposal for Python's Council Of Elders is partially based on the Supreme Court Of The United States.  For example, SCOTUS judges are appointed for life, and I think PCOE members should be too

Re: [python-committers] Transfer of power

On 07/13/2018 03:30 PM, Barry Warsaw wrote: On Jul 13, 2018, at 15:11, Jack Jansen wrote: How about a triumvirate (or trium*ate if “vir” is seen as too male-centric, and actually the “3” isn’t important either) where unanimity is required for language changes (i.e. basically for accepting

Re: [python-committers] Transfer of power

(separate reply to discuss the "what do we do now" topic) On 07/12/2018 07:57 AM, Guido van Rossum wrote: I would like to remove myself entirely from the decision process. [...] I am not going to appoint a successor. So what are you all going to do? Create a democracy? Anarchy? A

Re: [python-committers] Time for 3.4.9 and 3.5.6

On 07/08/2018 01:31 AM, Serhiy Storchaka wrote: I suggest to merge a 3.5 specific documentation fix for CALL_FUNCTION_VAR and CALL_FUNCTION_VAR_KW opcodes. There were undocumented changes in 3.5, and third-party projects which implement interpreting or generating these opcodes do it

[python-committers] Time for 3.4.9 and 3.5.6

My six-month cadence means it's time for the next releases of 3.4 and 3.5.  There haven't been many changes since the last releases--two, to be exact.  These two security fixes were backported to both 3.4 and 3.5: * bpo-32981: Fix catastrophic backtracking vulns (GH-5955) * bpo-33001:

Re: [python-committers] Marking issues as "Release Blocker" priority (was Re: FINAL WEEK FOR 3.7.0 CHANGES!)

On 05/30/2018 11:59 AM, Brett Cannon wrote: On Wed, 30 May 2018 at 10:21 Donald Stufft > wrote: So I think for the system to work, you need to either allow anyone to flag an issue as a release blocker, and the RM is empowered to say “No this really isn’t”

Re: [python-committers] Marking issues as "Release Blocker" priority (was Re: FINAL WEEK FOR 3.7.0 CHANGES!)

On 05/30/2018 10:21 AM, Donald Stufft wrote: On May 30, 2018, at 1:15 PM, Larry Hastings <mailto:la...@hastings.org>> wrote: ISTM that opinions vary on what constitutes a "release blocker", and maybe empowering only the release managers to make that call would be a good

Re: [python-committers] Marking issues as "Release Blocker" priority (was Re: FINAL WEEK FOR 3.7.0 CHANGES!)

rote: On 25 May 2018 at 04:09, Ned Deily mailto:n...@python.org>> wrote: On May 24, 2018, at 13:46, Larry Hastings mailto:la...@hastings.org>> wrote: > On 05/24/2018 10:08 AM, Ned Deily wrote: >> If you (or anyone else) feels strongly enough about it,

[python-committers] Marking issues as "Release Blocker" priority (was Re: FINAL WEEK FOR 3.7.0 CHANGES!)

On 05/24/2018 10:08 AM, Ned Deily wrote: If you (or anyone else) feels strongly enough about it, you should re-open the issue now and make it as a "release blocker" and we should discuss the implications and possible plans of action in the issue. About that.  According to the Python Dev

Re: [python-committers] Comments on moving issues to GitHub

On 05/20/2018 10:19 AM, Nathaniel Smith wrote: On Sun, May 20, 2018, 03:18 Antoine Pitrou > wrote: Le 19/05/2018 à 02:10, Victor Stinner a écrit : > Hi, > > I failed to get the microphone after Mariatta's secret talk about >

[python-committers] Proposing Mark Shannon to be a core developer

Dr. Mark Shannon contributed the "key sharing dictionary" to Python, writing both the PEP and the implementation.  This shipped in Python 3.3 and was listed as one of the top features of that release as according to the "What's New?" document. We've asked Mark in the past if he'd be

Re: [python-committers] Poll: Do you like the PEP 572 Assignment Expressions?

-1 //arry/ ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [Crosspost from python-committers] Announcing: signups are open for the 2018 Python Language Summit

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

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

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 for our (almost) exclusive use from

[python-committers] Announcing: signups are open for the 2018 Python Language Summit

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

Re: [python-committers] [RELEASED] Python 3.4.8 and Python 3.5.5 are now available

Actually, it was updated on the server, but somehow the old version was sticking around in the CDN cache.  I "purged" it and it's fine now.  Weird that it would linger this long! Cheers, //arry/ On 02/10/2018 03:20 AM, Serhiy Storchaka wrote: 05.02.18 02:35, Larry Has

[python-committers] [RELEASED] Python 3.4.8 and Python 3.5.5 are now available

On behalf of the Python development community, I'm happy to announce the availability of Python 3.4.8 and Python 3.5.5. Both Python 3.4 and 3.5 are in "security fixes only" mode.  Both versions only accept security fixes, not conventional bug fixes, and both releases are source-only. You

[python-committers] [RELEASED] Python 3.4.8rc1 and Python 3.5.5rc1 are now available

On behalf of the Python development community, I'm pleased to announce the availability of Python 3.4.8rc1 and Python 3.5.5rc1. Both Python 3.4 and 3.5 are in "security fixes only" mode. Both versions only accept security fixes, not conventional bug fixes, and both releases are source-only.

Re: [python-committers] [Python-Dev] Slipping Python 3.5.5rc1 and 3.4.8rc1 because of a Travis CI issue--can someone make Travis CI happy?

On 01/22/2018 07:51 AM, Brett Cannon wrote: I can switch off the requirement that holds admins to having to pass the same status checks as everyone else (there's still a big warning when you exercise this power), that way you can override the merge if you want. Not sure if you want to ignore

[python-committers] Slipping Python 3.5.5rc1 and 3.4.8rc1 because of a Travis CI issue--can someone make Travis CI happy?

I have three PRs for Python 3.5.5rc1: https://github.com/python/cpython/pull/4656 https://github.com/python/cpython/pull/5197 https://github.com/python/cpython/pull/5201 I can't merge them because Travis CI is unhappy.  All three CI tests fail in the same way, reporting this error:

[python-committers] Proposed schedule for next 3.4 and 3.5 releases - end of January / early February

Howdy howdy.  I know nobody's excited by the prospect of 3.4 and 3.5 releases--I mean, fer gosh sakes, neither of those versions even has f-strings!   But we're about due.  I prefer to release roughly every six months, and the current releases came out in early August. Here's my proposed

[python-committers] PEP 549 v2: now titled Instance Descriptors

I've updated PEP 549 with a new title--"Instance Descriptors" is a better name than "Instance Properties"--and to clarify my rationale for the PEP. I've also updated the prototype with code cleanups and a new type: "collections.abc.InstanceDescriptor", a base class that allows user classes

[python-committers] Workflow change reminder: The Blurb Has Landed

Yesterday I "blurbified" the 2.7, 3.6, and master branches in CPython. It's finally official: all* branches have now been "blurbified". This means that Misc/NEWS is no longer present in any of CPython's active branches. Instead, Misc/NEWS has been broken up into a zillion little files in

Re: [python-committers] Taking the month of September off from Python volunteering

On 08/14/2017 03:22 PM, Brett Cannon wrote: The reason I'm making this announcement now is I know this coincides with the core sprint next month so if anyone has anything they want to ask me before that, now is the time. So, this means you're skipping the core dev sprint? //arry/

[python-committers] [RELEASED] Python 3.4.7 is now available

On behalf of the Python development community and the Python 3.4 release team, I'm pleased to announce the availability of Python 3.4.7. Python 3.4 is now in "security fixes only" mode. This is the final stage of support for Python 3.4. Python 3.4 now only receives security fixes, not bug

[python-committers] Python 3.5 has now transitioned to "security fixes only" mode

The Python 3.5 branch has now entered "security fixes only" mode. No more bugfixes will be accepted into the 3.5 branch. In keeping with our modern workflow, I have changed the permissions on the 3.5 branch on Github so that only release managers can accept PRs into the branch. Please add

[python-committers] [RELEASED] Python 3.5.4 is now available

On behalf of the Python development community and the Python 3.5 release team, I'm pleased to announce the availability of Python 3.5.4. Python 3.5.4 is the final 3.5 release in "bug fix" mode. The Python 3.5 branch has now transitioned into "security fixes mode"; all future improvements

Re: [python-committers] My (positive) feedback on the new CPython workflow

On 07/18/2017 02:36 AM, Antoine Pitrou wrote: Can I take the opportunity to say thank you again (both you and Larry) for the "blurb" tool? It really makes an important difference when contributing. On 07/18/2017 03:24 AM, Victor Stinner wrote: Thank you Larry Hastings, Br

[python-committers] Python 3.5.4rc1 and 3.4.7rc1 slipping by a day, to July 24 2017

Release engineering for 3.5.4rc1 and 3.4.7rc1 took a lot longer than expected, because this is the first release using "blurb", and it turned out there was a lot of work left to do and a couple dark corners yet to stumble over. 3.5.4rc1 and 3.4.7rc1 will be released Monday, July 24, 2017.

Re: [python-committers] "trivial" label replaced with "skip issue"

Getting rid of Misc/NEWS was the whole point. The benefit is that we get rid of Misc/NEWS collisions. The other questions, you can answer for yourself by looking at the PRs. They're all in a row, PR 2714 through PR 2719. 2719 is where most of the conversation is happening.

Re: [python-committers] "trivial" label replaced with "skip issue"

On 07/14/2017 08:33 PM, Brett Cannon wrote: In preparation of fully moving over to blurb and per-file news entries (I don't have an ETA from Larry on when he plans to do explode Misc/NEWS into individual files) Sorry for the lack of communication; I've been traveling for two weeks and

[python-committers] Announcing the schedule for 3.4.7

In reply to my proposal of a few days ago, I received two +1s and no other feedback. So I'm going to issue 3.4.7 with relatively-little notice.t Here's the schedule for 3.4.7; it mirrors the schedule for 3.5.4. Saturday, July 22, 2017 - tag 3.4.7 rc1 Sunday, July 23, 2017 -

[python-committers] Reminder: 3.5.4rc1 will be tagged next Saturday, July 22 2017

Just a quick reminder. I'll be tagging 3.5.4rc1 next Saturday, July 22. 3.5.4 final will be the last release of 3.5.4 that accepts bugfixes; after that, the 3.5 branch will transition to security-fixes-only mode. If you have bugfixes you want to ship with 3.5.4, please get them committed

[python-committers] Should I make a 3.4.7rc1 next weekend?

I'm scheduled to tag and release 3.5.4rc1 next weekend. I've been releasing 3.4 and 3.5 at the same time for the last year; this is convenient for me as it halves the frequency with which I have to put on the "release manager" hat. There are currently no scheduled dates to release 3.4.7.

Re: [python-committers] New workflow change: Welcome to blurb

On 06/24/2017 10:30 AM, Terry Reedy wrote: Solution: name the file blurb.py and put it in site-packages. This is standard and what is done by all other pip-installs that I have run. Put a copy in /Scripts if you want, but that is really optional and only sometimes effective. Brett redid

Re: [python-committers] New workflow change: Welcome to blurb

On 06/23/2017 11:25 PM, Serhiy Storchaka wrote: I have installed it, but how to use it? $ python3 -m pip install --user blurb Collecting blurb Using cached blurb-1.0-py3-none-any.whl Installing collected packages: blurb Successfully installed blurb-1.0 $ python3 -m blurb /usr/bin/python3: No

Re: [python-committers] [Python-Dev] New workflow change: Welcome to blurb

On 06/23/2017 10:55 PM, Nick Coghlan wrote: Aye, towncrier and OpenStack's reno were the two main alternatives we looked at in addition to Larry's offer of creating a tool specifically for CPython: https://github.com/python/core-workflow/issues/6 Fun fact: all three tools started at about the

[python-committers] New workflow change: Welcome to blurb

One minor but ongoing problem we've had in CPython core development has been the mess of updating Misc/NEWS. Day-to-day developers may have a conflict if they lose a push race, which means a little editing. You'll have a similar, if slightly worse, problem when cherry-picking a fix

Re: [python-committers] Proposed release schedule for Python 3.5.4

On 06/21/2017 07:58 PM, Larry Hastings wrote: If you have any feedback / concerns about this schedule, or if you think it's important that I release 3.4.7 with these minor changes, please reply here. If I don't hear anything back in a day or two I'll go ahead and make this the official

Re: [python-committers] [Python-Dev] Proposed release schedule for Python 3.5.4

On 06/23/2017 01:55 AM, Victor Stinner wrote: Larry: would you be ok to turn this protection off on the 3.4 branch? Or would you feel more confortable if only a few people would be allowed to push to the 3.4 branch, so add me a whitelist group or something like that? Actually I kind of like

[python-committers] Signups for 2017 Python Language Summit are now open

(reposting, cc'ing python-dev) It’s that time again: time to start thinking about the Python Language Summit! The 2017 summit will be held on Wednesday, May 17, from 10am to 4pm, at the Oregon Convention Center in Portland, Oregon, USA. Your befezzled hosts Larry and Barry will once again be

[python-committers] [RELEASED] Python 3.4.6 and Python 3.5.3 are now available

On behalf of the Python development community and the Python 3.4 and Python 3.5 release teams, I'm delighted to announce the availability of Python 3.4.6 and Python 3.5.3. Python 3.4 is now in "security fixes only" mode. This is the final stage of support for Python 3.4. Python 3.4 now

[python-committers] [RELEASED] Python 3.4.6rc1 and Python 3.5.3rc1 are now available

On behalf of the Python development community and the Python 3.4 and Python 3.5 release teams, I'm pleased to announce the availability of Python 3.4.6rc1 and Python 3.5.6rc1. Python 3.4 is now in "security fixes only" mode. This is the final stage of support for Python 3.4. Python 3.4

[python-committers] Reminder: 3.5.3 rc1 and 3.4.6 rc1 tagged tomorrow

Just a reminder: I'll be tagging 3.5.3 rc1 and 3.4.6 rc1 tomorrow, Jan 1 2017, sometime between 24 and 36 hours from now. Please work quickly if there's anything you need to get in to either of those releases. I'm hoping that, for once, there are literally no code changes between rc1 and

Re: [python-committers] Should I delay 3.5.3 and 3.4.6 by two weeks?

100% of votes cast were for "don't slip", so we won't slip. Retreat! Full steam behind! //arry/ On 12/20/2016 02:25 AM, Matthias Klose wrote: On 19.12.2016 06:26, Larry Hastings wrote: Python 3.6.0 final just slipped by two weeks. I scheduled 3.5.3 and 3.4.6 to ship about a m

[python-committers] Should I delay 3.5.3 and 3.4.6 by two weeks?

Python 3.6.0 final just slipped by two weeks. I scheduled 3.5.3 and 3.4.6 to ship about a month after 3.6.0 did, to "let the dust settle" around the release. I expect a flood of adoption of 3.6, and people switching will find bugs, and maybe those bugs are in 3.5 or 3.4. So it just

[python-committers] Release schedule for 3.5.3 and 3.4.6

Here's the release schedule for Python versions 3.5.3 and 3.4.6. Sun Jan 1st, 2017 - tag 3.5.3rc1and 3.4.6rc1 Mon Jan 2nd, 2017 - release 3.5.3rc1and 3.4.6rc1 Sun Jan 15th, 2017 - tag 3.5.3 finaland 3.4.6final Mon Jan 16th, 2017 - release 3.5.3 finaland 3.4.6final The 3.5

Re: [python-committers] [Python-Dev] [RELEASED] Python 3.4.5 and Python 3.5.2 are now available

On 06/27/2016 11:24 AM, R. David Murray wrote: On Mon, 27 Jun 2016 08:25:40 -0700, Steve Dower <steve.do...@python.org> wrote: On 26Jun2016 1932, Larry Hastings wrote: https://www.python.org/downloads/release/python-352/ ... /p.s. There appears to be a small oops with the Windows inst

[python-committers] [RELEASED] Python 3.4.5 and Python 3.5.2 are now available

On behalf of the Python development community and the Python 3.4 and Python 3.5 release teams, I'm thrilled to announce the availability of Python 3.4.5 and Python 3.5.2. Python 3.4 is now in "security fixes only" mode. This is the final stage of support for Python 3.4. All changes made

Re: [python-committers] Here's what's going into 3.5.2 final and 3.4.5 final

I did ask for a better fix on the bug tracker, about two weeks ago: http://bugs.python.org/issue26867 But no better fix seems forthcoming. So I'll ship that. */arry* On Fri, Jun 24, 2016 at 2:29 AM, Matthias Klose <d...@ubuntu.com> wrote: > On 24.06.2016 11:14, Larry Hasti

[python-committers] Here's what's going into 3.5.2 final and 3.4.5 final

Heads up! This is a courtesy reminder from your friendly 3.4 and 3.5 release manager. Here's a list of all the changes since 3.5.2rc1 that are currently going into 3.5.2 final: * 155e665428c6 - Zachary: OpenSSL 1.0.2h build changes for Windows * cae0b7ffeb9f - Benjamin: fix % in

[python-committers] [RELEASED] Python 3.4.5rc1 and Python 3.5.2rc1 are now available

On behalf of the Python development community and the Python 3.4 and Python 3.5 release teams, I'm pleased to announce the availability of Python 3.4.5rc1 and Python 3.5.2rc1. Python 3.4 is now in "security fixes only" mode. This is the final stage of support for Python 3.4. All changes

Re: [python-committers] bugs.python.org, job status, and contributors (aka not core devs)

On 06/06/2016 10:56 AM, Terry Reedy wrote: I have wondered whether triagers should have a symbol after their name -- perhaps &. I smell an assumption of ASCII, when presumably all of Unicode lay open at our feet. Let the bikeshedding begin!, //arry/

[python-committers] 2016 Python Language Smmit: All talk submitters have been notified!

We've sent out notices to all talk submitters telling them whether their talk was accepted or rejected. If you haven't gotten yours yet, check your spam folder. If you still can't find it, email us! See you there, [BL]arry ___

Re: [python-committers] 2016 Python Language Summit: Can we get volunteers to talk about pathlib?

On 04/29/2016 03:53 PM, Guido van Rossum wrote: The primary debate should be about fspath or not. Inheriting from str is off the table while I'm BDFL. Removing pathlib from the stdlib would only be on the table if we can't reach agreement on fspath. WFM. Are there competing proposals for

[python-committers] 2016 Python Language Summit: Can we get volunteers to talk about pathlib?

This month there were over 350 emails in python-dev with the word "pathlib" in the title. Yet, despite this massive online debate, nobody volunteered to present about pathlib at the language summit. Based on Jake Edge's summary of the conversation from LWN.net we've boiled down the debate

[python-committers] All Language Summit invites have been sent!

Barry and I have sent out notices to everyone who requested an invite--check the inbox for the email address you supplied us with! And boy are our fingers tired, [BL]arry ___ python-committers mailing list python-committers@python.org

[python-committers] Less than a week left! (was Re: Call For Participants For The 2016 Python Language Summit)

, please fill out the form in the next few days! I promise it's short, clear, and easy. It'll take you only a few minutes, honest. And remember: if you're a core developer, your invitation is guaranteed, [BL]arry On 03/01/2016 05:01 PM, Larry Hastings wrote: Signups are open as of now

Re: [python-committers] CFFI is slow

API, or even modify it in any meaningful way that would let us abstract away implementation details like reference counting. As I said in my original email, this magic wand simply doesn't exist. //arry/ On 03/05/2016 12:42 AM, Stefan Krah wrote: Larry Hastings hastings.org> writes: If we

[python-committers] Call For Participants For The 2016 Python Language Summit

It's that time once again: time to start planning for the 2016 Python Language Summit! This year the summit will be at the Oregon Convention Center in Portland, Oregon, USA, on May 28th. Sadly, again this year Michael Foord won't be in attendance. Barry Warsaw and I are running the

[python-committers] [RELEASED] Python 3.5.1 and 3.4.4rc1 are now available

On behalf of the Python development community and the Python 3.4 and 3.5 release teams, I'm pleased to announce the simultaneous availability of Python 3.5.1 and Python 3.4.4rc1. As point releases, both have many incremental improvements over their predecessor releases. You can find

[python-committers] Reminder: checkins into 3.5 after rc1 won't automatically go into final

3.5.1rc1 is tagged, merged, and pushed back into the central repo. At this point I don't plan to merge further changes from hg.python.org into 3.5.1 final. If you have an important bug fix that didn't make it into 3.5.1rc1 and *has* to go into 3.5.1 final, add me to the issue and we'll

[python-committers] Release schedule for 3.4.4

Sorry for the short notice of this schedule, but... here goes: Sat Dec 05 - tag 3.4.4rc1 Sun Dec 06 - release 3.4.4rc1 Sat Dec 19 - tag 3.4.4 final Sun Dec 20 - release 3.4.4 final The reason for the short notice: we may have to change personnel for this release, and we need to

[python-committers] [RELEASED] Python 3.5.0 is now available

On behalf of the Python development community and the Python 3.5 release team, I'm proud to announce the availability of Python 3.5.0. Python 3.5.0 is the newest version of the Python language, and it contains many exciting new features and optimizations. You can read all about what's

[python-committers] [RELEASED] Python 3.5.0rc4 is now available!

On behalf of the Python development community and the Python 3.5 release team, I'm surprised to announce the availability of Python 3.5.0rc4, also known as Python 3.5.0 Release Candidate 4. Python 3.5.0 Release Candidate 3 was only released about a day ago. However: during testing, a

[python-committers] How To Forward-Merge Your Change After Your Pull Request Is Accepted Into Python 3.5.0rcX

Now that we're in the release candidate phase of Python 3.5.0, the workflow has changed a little. We're trying an experiment using Bitbucket and pull requests. You can read about that workflow, here: https://mail.python.org/pipermail/python-dev/2015-August/141167.html But the instructions

[python-committers] [RELEASED] Python 3.5.0rc2 is now available

On behalf of the Python development community and the Python 3.5 release team, I'm relieved to announce the availability of Python 3.5.0rc2, also known as Python 3.5.0 Release Candidate 2. Python 3.5 has now entered feature freeze. By default new features may no longer be added to Python

Re: [python-committers] [Python-Dev] How are we merging forward from the Bitbucket 3.5 repo?

On 08/16/2015 08:24 AM, R. David Murray wrote: On Sun, 16 Aug 2015 00:13:10 -0700, Larry Hastings la...@hastings.org wrote: Can we pick one approach and stick with it? Pretty-please? Pick one Larry, you are the RM :) Okay. Unsurprisingly, I pick what I called option 3 before. It's

[python-committers] How are we merging forward from the Bitbucket 3.5 repo?

So far I've accepted two pull requests into bitbucket.com/larry/cpython350 in the 3.5 branch, what will become 3.5.0rc2. As usual, it's the contributor's responsibility to merge forward; if their checkin goes in to 3.5, it's their responsibility to also merge it into the

Re: [python-committers] How are we merging forward from the Bitbucket 3.5 repo?

On 08/16/2015 07:08 AM, Guido van Rossum wrote: I presume the issue here is that Hg is so complicated that everyone knows a different subset of the commands and semantics. I personally don't know what the commands for cherry-picking a revision would be. There are a couple. The command

  1   2   >