[python-committers] Proposed release schedule for Python 3.5.4

It's time to start planning the next 3.5 release, 3.5.4. Note that this will be the last 3.5 "bugfix" release; after 3.5.4, the 3.5 branch will only be open for security fixes. 3.5.4 will also be the last release of 3.5 with binary installers. I propose to tag and release 3.5.4 on these d

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

On 06/22/2017 01:04 AM, Victor Stinner wrote: About the cipher list in ssl, the change itself is simple but it's to blacklist DES and 3DES since it has been proved that these ciphers are really too weak nowadays: http://python-security.readthedocs.io/vuln/cve-2016-2183_sweet32_attack_des_3des

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 the

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 th

[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 between

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 s

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] New workflow change: Welcome to blurb

On 06/24/2017 09:40 AM, Terry Reedy wrote: On 6/23/2017 11:24 PM, Larry Hastings wrote: > You can install blurb from pip: > > % pip3.6 install blurb This does not seem to work right. On Windows: C:\Users\Terry>py -3 -m pip install blurb Collecting blurb Downloading blurb-

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 th

[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.

[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 i

[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 - r

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 it's

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. https://gi

[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] 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, Brett

[python-committers] RELEASED] Python 3.4.7rc1 and Python 3.5.4rc1 are now available

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

[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 i

[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.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

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] 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

[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] 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 sc

[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:

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] [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.

[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

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 Ha

[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 big

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 (

[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 big

[python-committers] Reminder: 2018 Python Language Summit signups close next week

The deadline is a week from today, April 18th 2018.  Original announcement below. -- 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,

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] 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 interes

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 > moving Python issues

[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 Gui

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

hlan, <mailto:ncogh...@gmail.com>> wrote: 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

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!)

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”

[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: Prev

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 incorrectly

Re: [python-committers] Transfer of power

On 07/12/2018 07:57 AM, Guido van Rossum wrote: I'll still be here, but I'm trying to let you all figure something out for yourselves. I'm tired, and need a very long break. Let me add my voice to the choir saying: * I'm sorry you had such a miserable experience. * I'm sad that you're reti

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 dictatorsh

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 a

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 b

Re: [python-committers] Transfer of power

On 07/13/2018 06:54 PM, Tim Peters wrote: So:  term limits!  Say, 12 years.  If there are 3 Elders, replace one every 12/3 = 4 years.  At the start we can use the `secrets` module to pick which Elders get the first 4, 8, and 12-year terms ;-) Fresh blood is a good thing in all areas. Can I

[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 python-committers@pyt

[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 source-only.

[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] 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 m

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 set

Re: [python-committers] New core developers: Lisa Roach and Emily Morehouse-Valcarcel

On 09/14/2018 12:28 PM, Raymond Hettinger wrote: At the developer sprints this week, we collectively decided to grant core committer status to Emily and Lisa. Please join me in welcoming them to the team. Congratulations Emily and Lisa!  I look forward to many years of arguing working with

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

[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] 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 Chri

[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] Last-minute request: please backport bpo-33329 fix to 3.4 and 3.5

n 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

[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 source-only

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] 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: https

[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 i

[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, en

[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 slow

[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 3.5.8rc1

[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

[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] [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 here

[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 .tgz

[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 3.5.8

[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: T

[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 re

[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 P

[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 doe

[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 d

[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 Wo

[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 that

[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 the

[python-committers] When do we stop automerging from trunk to py3k?

Pardon my general n00bishness, but I crave knowledge. IIUC currently if you have a checkin in trunk that you *don't* want merged into py3k, you must svnmerge block it in py3k. Otherwise it will be automatically merged at some point. My question is: when will we stop doing that? I assume

[python-committers] Call For Topics for Python Language Summit at EuroPython 2011

Howdy howdy. Michael Foord can't make it to EuroPython this year--and congratulations to him on his new baby!--so he's asked me to chair the Python Language Summit in his stead. Although I have some suggested topics from Michael, I don't have any burning issues of my own to add to the dock

[python-committers] Python Language Summit, Florence, July 2012

Like Python? Like Italy? Like meetings? Then I've got a treat for you! I'll be chairing a Python Language Summit this July in historic Florence, Italy. It'll be on July 1st (the day before EuroPython starts) at the Grand Hotel Mediterraneo conference center. Language Summits are when th

Re: [python-committers] Python Language Summit, Florence, July 2012

On 05/30/2012 05:06 AM, Larry Hastings wrote: Like Python? Like Italy? Like meetings? Then I've got a treat for you! I'll be chairing a Python Language Summit this July in historic Florence, Italy. It'll be on July 1st (the day before EuroPython starts) at the Grand Hot

[python-committers] EuroPython 2012 Language Summit Is In JEOPARDY *gasp*

So far I've had exactly four reservations for the Language Summit at EuroPython 2012. One of them is Guido--but he's threatening to skip it if we don't get more people and just go to the sprints. Also, honestly I have next-to-nothing on the docket. At this point we've just hit feature fre

[python-committers] EuroPython 2012 Language Summit is Canceled.

I only got one more RSVP and zero topics for the docket. So let's sprint instead. See you at the PyCon 2013 Language Summit, //arry/ ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-co

Re: [python-committers] WANTED: leader for the core sprint at PyCon US (was: I will NOT be leading the core sprint at PyCon US this year)

On 02/26/2013 10:13 AM, R. David Murray wrote: Given a little support from Brett on how best to go about it, I'm willing to volunteer for this. I'm happy to do it too, and I'll be there for the full sprint fwiw. //arry/ ___ python-committers mailing

Re: [python-committers] Language Summit at EuroPython

On 06/18/2013 09:09 AM, Michael Foord wrote: Hey Ezio, There are no plans that I'm aware of to have a language summit at EuroPython, sorry. We didn't have one last year because nobody had anything to say. If you're (gentle reader) going to be at EuroPython and think you have something that

Re: [python-committers] Policy for committing to 2.7

Everything I read in this thread says that 2.7 only gets bug fixes, and even at that it has to be a pretty bad bug. (Benjamin: "If it's been broken for all of the 2.x series, it probably doesn't need to be fixed now.") I don't see even mild dissent; the replies have been strongly unanimous

[python-committers] Reminder: Python 3.4 alpha 1 release is Saturday August 3

It's about nine days from now. I expect to tag the release late next week. So if you're doing any major brain surgery, please finish it up in the next week or so. Your mildly anxious release manager, //arry/ p.s. Anybody have contact information for Jim Hugunin? He left Google back in

Re: [python-committers] Reminder: Python 3.4 alpha 1 release is Saturday August 3

On 07/30/2013 01:01 PM, Ethan Furman wrote: Do modifications to _json to support Enum count as major? If they don't make it in to the first alpha, can I put them in the second? You can put them in either. //arry/ ___ python-committers mailing list

Re: [python-committers] Reminder: Python 3.4 alpha 1 release is Saturday August 3

On 08/01/2013 04:14 PM, Victor Stinner wrote: Is it ok to do such changes between the alpha4 and beta1? Yes. We don't hit feature-freeze until beta 1. But it's best to get your changes in earlier, so they can be in one (or more) alphas. And in case you discover something wrong with your a

Re: [python-committers] Reminder: Python 3.4 alpha 1 release is Saturday August 3

On 08/02/2013 01:00 PM, Ned Deily wrote: Hmm. I understand this is an alpha but I was hoping to get a few more fixes in today. Perhaps, in the future, we can be more clear about exactly when the code freeze time (tag time) is vs a release time. From a developer point of view, the former is im

Re: [python-committers] Reminder: Python 3.4 alpha 1 release is Saturday August 3

On 08/02/2013 02:00 PM, Antoine Pitrou wrote: "Forward" means what? Earlier or later? (intuitively, I'd say "earlier", but that doesn't seem very consistent with your explanations) Your intuition is the opposite of mine. When I move dates "forward", I increase the date / number / etc. So I w

[python-committers] Tagging 3.4a1 with an unhappy AMD64 Win7 SP1 buildbot?

I'm considering for Python 3.4.0a1. The buildbots are all happy, except for AMD64 Win7 SP1: http://buildbot.python.org/all/waterfall?category=3.x.stable The two failures are zipimport and signal. zipimport is sporadic, and looks like some sort of heisenissue. signal is much more cons

Re: [python-committers] Tagging 3.4a1 with an unhappy AMD64 Win7 SP1 buildbot?

On 08/03/2013 02:08 AM, Larry Hastings wrote: Can we, uh, live with that, for alpha 1? Ned pointed out, signal and zipimport worked on the retry. So it's sporadic, whatever it is. I think we can live with that. I've got some documentation warnings I can't quash, so I&#x

[python-committers] Can I get the keys to the website please?

PEP 101 tells me that in order to release Python 3.4.0a1 I must massage the website. I foolishly left this to the last minute. Can anybody give me access to the repo and shove me towards the README? Pretty please? I already have access to dinsdale and am in the "webmaster" group on there.

[python-committers] [RELEASED] Python 3.4.0a1

or implementing custom memory allocators To download Python 3.4.0a1 visit: http://www.python.org/download/releases/3.4.0/ Please consider trying Python 3.4.0a1 with your code and reporting any issues you notice to: http://bugs.python.org/ Enjoy! -- Larry Hastings, Release M

[python-committers] Trunk is ready for 3.4.0a2 work

All the release engineering work for 3.4.0a1 has been merged. Cry havoc, and let slip the checkins of war! //arry/ ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] [RELEASED] Python 3.4.0a1

On 08/03/2013 11:22 PM, Larry Hastings wrote: * PEP 435, a standardized "enum" module * PEP 442, improved semantics for object finalization * PEP 443, adding single-dispatch generic functions to the standard library * PEP 445, a new C API for implementing custom memory allocator

Re: [python-committers] [Python-Dev] [RELEASED] Python 3.4.0a1

On 08/04/2013 07:01 AM, Eli Bendersky wrote: Larry, if there are other things you're going to add, update the web page http://www.python.org/download/releases/3.4.0/ as well - it's the one being linked in the inter-webs now. Good thinking! I'll do that today. //arry/

[python-committers] Reminder: 3.4a2 to be tagged soon

It's been pretty quiet, and there aren't any genuine release blockers (everything marked release blocker and 3.4 is actually for 2.6.9). I expect to tag Saturday evening, New Zealand time. Cheers, //arry/ ___ python-committers mailing list python

  1   2   3   >