[python-committers] 3.4a2 now being tagged and built

The last revision that made it in is 98f82b124c7d from Victor. The buildbots are all green, it's been a quiet day... you folks are making this easy! Hope to get the release out tomorrow, //arry/ ___ python-committers mailing list python-committe

[python-committers] [RELEASED] Python 3.4.0a2

isit: http://www.python.org/download/releases/3.4.0/ Please consider trying Python 3.4.0a2 with your code and reporting any issues you notice to: http://bugs.python.org/ Enjoy! -- Larry Hastings, Release Manager larry at hastings.org (on behalf of the entire python-dev team and 3.4

[python-committers] [RELEASED] Python 3.4.0a3

s you notice to: http://bugs.python.org/ Enjoy! -- Larry Hastings, Release Manager larry at hastings.org (on behalf of the entire python-dev team and 3.4's contributors) ___ python-committers mailing list [email protected] htt

[python-committers] I *might* push Python 3.4.0 alpha 4 back a week

A lot has landed in trunk in the last day or two: Tulip, Argument Clinic, and statistics just landed too. The buildbots are upset at us humans--there's a lot of red. See for yourself: http://buildbot.python.org/all/waterfall?category=3.x.stable I'd like to tag Alpha 4 late tonight, but

[python-committers] Python 3.4.0a4: Coming In For A Bumpy Landing

3.4.0a4 is tagged and I'm in the process of releasing it. But it's going to be, let's say, more "alpha-quality" than the previous alphas. Known problems: * There's a reference count leak in the compiler. * asyncio test suite sometimes times out, which takes... an hour. * asyncio test sui

[python-committers] [RELEASED] Python 3.4.0a4

ule test suite fails on some platforms. * I/O conducted by the "asyncio" module may, rarely, erroneously time out. The timeout takes one hour. Please consider trying Python 3.4.0a4 with your code and reporting any new issues you notice to: http://bugs.python.org/ Enjoy! -- La

[python-committers] Reminder: Python 3.4 feature freeze in a week

We're on schedule to tag Python 3.4 Beta 1 next Saturday. And when that happens we go into "feature freeze" on Python trunk; no new features will be accepted in trunk until we branch the 3.4 release branch next February. Time to get those checkins in folks. Last call, everyone, //arry/

[python-committers] Reminder: Less than 24 hours until 3.4 feature freeze

I hope to tag 3.4 in less than 24 hours from now. Last call, folks. Here's hoping the buildbots all get green soon, //arry/ ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers

[python-committers] Python 3.4.0b1 is now tagged, feature-freeze is now in effect

Please refrain from checking in any new features to Python trunk until after the 3.4 release branch is created (which will be a few months). Instead, let's concentrate our efforts on polishing Python 3.4 until it's the best and most-defect-free release yet! Thanks, //arry/ __

[python-committers] [RELEASED] Python 3.4.0b1

e", meaning that no new features will be added. The final release is projected for late February 2014. To download Python 3.4.0b1 visit: http://www.python.org/download/releases/3.4.0/ Please consider trying Python 3.4.0b1 with your code and reporting any new issues you notice to:

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

On 11/24/2013 02:00 PM, Larry Hastings wrote: Python 3.4 includes a range of improvements of the 3.x series, including hundreds of small improvements and bug fixes. Major new features and changes in the 3.4 release series include: Whoops, sorry, I missed a couple of PEPs there: * PEP 428, a

[python-committers] [RELEASED] Python 3.4.0b2

inal release is projected for late February 2014. To download Python 3.4.0b2 visit: http://www.python.org/download/releases/3.4.0/ Please consider trying Python 3.4.0b2 with your code and reporting any new issues you notice to: http://bugs.python.org/ Enjoy! -- Larry Hastings, Rel

[python-committers] 3.4.0b2 release commits merged back into trunk, trunk is open for business again EOM

//arry/ ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers

[python-committers] Adding a (small) feature to 3.4 for Argument Clinic: inspect.Signature supporting simple named constants for default values

Serhiy Storchaka ran into a ticklish problem with Argument Clinic and inspect.Signature information for builtins. Consider pattern_match() in Modules/_sre.c. This implements the match method on a pattern object; in other words, re.compile().match(). The third parameter, endpos, defaults to

Re: [python-committers] Adding a (small) feature to 3.4 for Argument Clinic: inspect.Signature supporting simple named constants for default values

On 01/06/2014 02:10 PM, M.-A. Lemburg wrote: Looks like a documentation bug to me. Several functions were changed to be keyword aware some years ago and the docs you quoted still list the old positional format. Your intuition was spot on. Revision 0a97f5dde3a7, by the effbot, Tue Oct 03 200

Re: [python-committers] clinic churn after beta2

On 01/07/2014 03:10 PM, A.M. Kuchling wrote: On Tue, Jan 07, 2014 at 02:37:22PM -0800, Eli Bendersky wrote: Just to be clear, this is exactly what I mean. I'm not saying AC is not worth it; I'm questioning the timing. Agreed; let's try to avoid far-ranging sets of changes so late in the beta cy

Re: [python-committers] clinic churn after beta2

On 01/07/2014 06:06 PM, Nick Coghlan wrote: Addressing the key remaining barriers to migration for existing Python 2 users would be an excellent objective to attain before we end upstream support for Python 2.7, but it's one that would be better addressed by a slightly shorter dev cycle than

Re: [python-committers] clinic churn after beta2

On 01/08/2014 02:16 AM, Antoine Pitrou wrote: Agreed with Nick here. Let's just add a third beta for the clinic churn. Just to be clear: I plan to add a third beta, and have a proposed schedule. I haven't posted it yet because I'm waiting to hear back from the rest of the crew that the sche

[python-committers] Updated schedule for Python 3.4

We've added a third beta and pushed the whole schedule out by three weeks. Assuming we stick to this schedule, beta 3 will be released Jan 26th, rc1 Feb 9, rc2 Feb 23, and final March 16th. That's all the details, but here's the release schedule PEP anyway: http://www.python.org/dev/pe

[python-committers] Status of the Derby, and request for another slip

The Great Argument Clinic Conversion Derby has been underway for about 2.5 weeks. Here's a status update. I'll try to keep this short. It's taking a lot longer than I expected it to. This has been due to * bugs and flaws in Argument Clinic itself (a "flaw" is an "I didn't foresee that" de

Re: [python-committers] Status of the Derby, and request for another slip

On 01/25/2014 05:35 AM, Antoine Pitrou wrote: Stop the Derby. We needn't convert everything for 3.4 (I didn't even know that was your goal). Converting everything was my goal at one point. At this point it is nowhere near viable, not the least because there simply isn't enough time. As disc

Re: [python-committers] Status of the Derby, and request for another slip

On 01/26/2014 02:18 PM, Guido van Rossum wrote: On Sun, Jan 26, 2014 at 2:16 PM, Barry Warsaw > wrote: The closer Python 3.4 can stick to the March 16th release, the better. Yes. That's the whole point of time-based releases. Please stick to the plan. We've alrea

[python-committers] [RELEASED] Python 3.4.0b3

he final release is projected for mid-March 2014. To download Python 3.4.0b3 visit: http://www.python.org/download/releases/3.4.0/ Please consider trying Python 3.4.0b3 with your code and reporting any new issues you notice to: http://bugs.python.org/ Enjoy! -- Larry Hastings, Rel

Re: [python-committers] Code review tool (rietveld) bug

On 01/27/2014 12:24 PM, Antoine Pitrou wrote: As a sidenote, why is Larry green on this page? Motion sickness. //arry/ ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers

[python-committers] [RELEASED] Python 3.4.0 release candidate 1

he final release is projected for mid-March 2014. To download Python 3.4.0rc1 visit: http://www.python.org/download/releases/3.4.0/ Please consider trying Python 3.4.0rc1 with your code and reporting any new issues you notice to: http://bugs.python.org/ Enjoy! -- Larry Hastings,

[python-committers] [RELEASED] Python 3.4.0 release candidate 2 is now available

rg/download/releases/3.4.0/ Once I can update the new web site, Python 3.4.0rc2 will be available here: http://python.org/download/releases/ (I'm not sure what the final URL will be, but you'll see it listed on that page.) Please consider trying Python 3.4.0rc2 with your code an

[python-committers] [RELEASED] Python 3.4.0 release candidate 3

ill be added. The final release is projected for March 16, 2014. To download Python 3.4.0rc3 visit: http://www.python.org/download/releases/3.4.0/ Please consider trying Python 3.4.0rc3 with your code and reporting any new issues you notice to: http://bugs.python.org/ Enjoy! **

[python-committers] default hg.python.org/cpython is now 3.5

The "3.4" branch is now checked in. It contains all the 3.4 releases since 3.4.0rc1. Its current state is effectively 3.4.1. The "default" branch is now 3.5. Cry havoc, and let slip the dogs of war, //arry/ ___ python-committers mailing list py

[python-committers] [RELEASED] Python 3.4.0

ved protocol for pickled objects * PEP 3156, a new "asyncio" module, a new framework for asynchronous I/O To download Python 3.4.0 visit: http://www.python.org/download/releases/3.4.0/ This is a production release. Please report any issues you notice to: http://bugs.python

Re: [python-committers] default hg.python.org/cpython is now 3.5

On 03/17/2014 04:23 PM, Nick Coghlan wrote: On 18 Mar 2014 07:37, "Victor Stinner" > wrote: > > Hi, > > I modified the Misc/NEWS file: > > * I moved 3.3 sections to Misc/HISTORY: items were already present, > but the format in Misc/NEWS was improved (changeset

[python-committers] [RELEASED] Python 3.4.1rc1

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.1rc1. Python 3.4.1rc1 has over three hundred bugfixes and other improvements over 3.4.0. One notable change: the version of OpenSSL bundled with the Windows

[python-committers] [RELEASED] Python 3.4.1

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.1. Python 3.4.1 has over three hundred bugfixes and other improvements over 3.4.0. One notable change: the version of OpenSSL bundled with the Windows instal

[python-committers] [RELEASE] Python 3.4.2rc1 is now available

On behalf of the Python development community and the Python 3.4 release team, I'm chuffed to announce the availability of Python 3.4.2rc1. Python 3.4.2 has many bugfixes and other small improvements over 3.4.1. One new feature for Mac OS X users: the OS X installers are now distributed as

Re: [python-committers] [RELEASE] Python 3.4.2rc1 is now available

/issue21431 We'll get it right for 3.4.2 final. I don't think we need to respin 3.4.2rc1 / add a 3.4.2rc2 for this. On 09/22/2014 06:02 PM, Terry Reedy wrote: On 9/22/2014 10:15 AM, Larry Hastings wrote: You can download it here: https://www.python.org/download/rele

Re: [python-committers] cherry picking after rc

On 10/05/2014 07:11 AM, R. David Murray wrote: Larry, saw your discussion on IRC with Georg about what to cherry pick into the release clone before issuing final. IMO you shouldn't cherry pick anything, since I believe there have been *zero* issues opened that said that the RC was broken. 3.4.

[python-committers] [RELEASE] Python 3.4.2 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.2. Python 3.4.2 has many bugfixes and other small improvements over 3.4.1. One new feature for Mac OS X users: the OS X installers are now distributed as sig

[python-committers] Time for a 3.4.3?

3.4.2 rc1 was two months ago. Time to start thinking about another point release? I was thinking about 3.4.3 rc1 on Dec 13, then 3.4.3 final on Dec 27. //arry/ ___ python-committers mailing list [email protected] https://mail.python.o

Re: [python-committers] Time for a 3.4.3?

On 11/24/2014 06:48 AM, "Martin v. Löwis" wrote: Am 24.11.14 04:48, schrieb Larry Hastings: 3.4.2 rc1 was two months ago. Time to start thinking about another point release? I was thinking about 3.4.3 rc1 on Dec 13, then 3.4.3 final on Dec 27. I'm travelling between Christm

[python-committers] Schedule for 3.4.3, revised schedule for 3.5.0a1

Python 3.5.0a1 is currently scheduled to be released February 1. Since I'll be on the road that day, the 3.5 team has agreed to push the release back a week. 3.5.0a1 will be tagged Saturday February 7 and released Sunday February 8. This doesn't change any of the other release dates for 3.

[python-committers] [RELEASE] Python 3.5.0a1 is now available

On behalf of the Python development community and the Python 3.5 release team, I'm also pleased to announce the availability of Python 3.5.0a1. Python 3.5.0a1 is the first alpha release of Python 3.5, which will be the next major release of Python. Python 3.5 is still under heavy developm

[python-committers] [RELEASE] Python 3.4.3rc1 is now available

On behalf of the Python development community and the Python 3.4 release team, I'm happy to announce the availability of Python 3.4.3rc1. Python 3.4.3rc1 has many bugfixes and other small improvements over 3.4.2. You can download it here: https://www.python.org/download/releases/3.4.3

[python-committers] [RELEASED] Python 3.4.3 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.3. Python 3.4.3 has many bugfixes and other small improvements over 3.4.2. You can find it here: https://www.python.org/downloads/release/python-343/

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

On behalf of the Python development community and the Python 3.5 release team, I'm thrilled to announce the availability of Python 3.5.0a2. Python 3.5.0a2 is the second alpha release of Python 3.5, which will be the next major release of Python. Python 3.5 is still under heavy development

[python-committers] Minor update to Python 3.5 release schedule

I always intended all my releases to be on Sundays--that all the release engineering work is done on weekends, which is generally easier for everybody. But I goofed up the 3.5 release schedule and had proposed 3.5.0a3 to be released Saturday March 28th. With the assent of the team I bumped

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

On behalf of the Python development community and the Python 3.5 release team, I'm thrilled to announce the availability of Python 3.5.0a3. Python 3.5.0a3 is the third alpha release of Python 3.5, which will be the next major release of Python. Python 3.5 is still under heavy development,

[python-committers] Do we need to sign Windows files with GnuPG?

As of Python 3.5 Steve Dower has taken over the Windows builds of Python from Martin van Loewis. He's also taken over for 2.7--though Martin's still doing builds for 3.4. For both versions, Steve is using all-new tooling for the build process. The output is different, too; he's producing

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

On behalf of the Python development community and the Python 3.5 release team, I'm thrilled to announce the availability of Python 3.5.0a4. Python 3.5.0a4 is the fourth and alpha release of Python 3.5, which will be the next major release of Python. Python 3.5 is still under development, a

[python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)

Python 3.5 beta 1 is coming up soon. After beta is rc; after rc is 3.5.0 final. During the beta and rc periods the Python developer workflow changes a little--what sorts of checkins are permissible, and how to get something accepted and merged generally becomes more complicated. I was the

Re: [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)

On 05/12/2015 10:23 AM, Ned Deily wrote: One possible issue with Workflow 1 is that there would need to be an additional set of buildbots (for 3.5, in addition to the existing 3.x (AKA "trunk"), 3.4, and 2.7 ones) for the period from beta 1 until at least 3.5.0 is released and, ideally, until 3

Re: [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)

On 05/12/2015 11:21 AM, Ned Deily wrote: I like the idea of experimentally trying the push workflow but, if we are all doing our jobs right, there should be very few changes going in after rc1 so most committers won't need to push anything to the 3.5.0rc repo and, if for some reason they aren'

Re: [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)

On 05/12/2015 05:11 PM, Dirkjan Ochtman wrote: Couldn't you just keep this as a branch that you then keep rebasing (without unlinking the original branch)? It doesn't seem like something that needs a one-off script, to me. Probably. It's water under the bridge now--that all happened last Febr

Re: [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)

On 05/12/2015 11:18 AM, Jesus Cea wrote: Larry, could you comment about the impact in the buildbots?. I suppose option #1 could allows us to test both 3.5 and 3.6 changes. Would you confirm this? Workflow #1 gets us automatic buildbot testing for the 3.5 branch (betas and 3.5.1) and trunk (3.6

Re: [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)

On 05/12/2015 05:19 PM, Nick Coghlan wrote: Workflow 0: -0 Workflow 1: +1 Workflow 2: +0 That's taking into account the clarification that the buildbots will be set up to track the 3.5.x branch after the beta is forked, and that Larry will also push the 3.5rcX repo to hg.python.org

Re: [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)

On 05/12/2015 10:04 AM, Larry Hastings wrote: What do you think? [...] Please cast your votes workflow 012 Larry Hastings-0.5 10.5 Brett Cannon 010 Nick Coghlan 010 Chris Angelico 000“in favor of [Workflow 1]” Ned Deily

Re: [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)

On 05/14/2015 08:14 AM, R. David Murray wrote: On Thu, 14 May 2015 07:15:34 -0700, Larry Hastings wrote: I'll start experimenting with the workflow(s) and will add documentation to the Dev Guide. The fun starts next weekend, By "next weekend" you mean "the weekend after

[python-committers] Reminder: Python 3.5 beta 1 will be tagged tomorrow

Howdy howdy. It's-a me, Larry, your friendly neighborhood Python 3.5 Release Manager. Somewhere around 2 or 3pm tomorrow I expect to tag Python 3.5 beta 1. We'll actually release beta 1 on Sunday, once the binary installers are all built. Beta 1 is also feature-freeze, meaning no new fe

Re: [python-committers] [Python-Dev] Reminder: Python 3.5 beta 1 will be tagged tomorrow

On 05/22/2015 02:29 PM, Chris Barker wrote: Is it too late to get the isclose() code (PEP 485) into 3.5? I posted the code here, and got a tiny bit of review, but have not yet merged it into the source tree -- and don't know the process for getting it committed to the official source. So --

[python-committers] Can we clean up the buildbots please?

Right now we have eight online buildbots for Python trunk. Of those, currently *six* are reporting errors in either the compile or test phases. http://buildbot.python.org/all/waterfall?category=3.x.stable There's one platform ("AMD64 Snow Leop") where the failures are sporadic "stack ov

Re: [python-committers] Can we clean up the buildbots please?

On 05/22/2015 03:06 PM, Steve Dower wrote: The Windows 7 buildbots are failing on test_asdl_parser, but I have no idea why – the test works for me just fine. Yury and Benjamin made the most recent changes to Python.asdl, but I have no idea what effect they would have here, or why it’s Windows

Re: [python-committers] Can we clean up the buildbots please?

*From:*Larry Hastings [mailto:[email protected]] *On Behalf Of *Larry Hastings *Sent:* Friday, May 22, 2015 1530 *To:* Steve Dower; Python Dev; python-committers *Cc:* Yury Selivanov; Benjamin Peterson *Subject:* Re: [python-committers] Can we clean up the buildbots please? Is MSVS 2015 the

Re: [python-committers] Can we clean up the buildbots please?

On 05/22/2015 05:11 PM, Trent Nelson wrote: Do we still support WS2K3? (Can I even install VS 2015 on that? I would have thought not.) According to PCbuild/readme.txt, no. It says: This directory is used to build CPython for Microsoft Windows NT version 6.0 or higher (Windows Vista, Wi

Re: [python-committers] Can we clean up the buildbots please?

On 05/22/2015 06:35 PM, Terry Reedy wrote: Not supporting 2010 should be contingent on the availability of just the 2015 compiler -- as is possible for the 2010 compiler -- without several gigabytes of extra fluff. This is still in the future. Perhaps, but that's not what it says in the sourc

Re: [python-committers] [Python-Dev] Reminder: Python 3.5 beta 1 will be tagged tomorrow

On 05/23/2015 06:25 AM, Nick Coghlan wrote: I filed http://bugs.python.org/issue24270 to track this, but there's a fair bit of work to be done to integrate the changes into the existing math module's code, tests and documentation. I'm willing to consider a feature freeze exception for this, as

[python-committers] [RELEASED] Python 3.5.0b1 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.0b1. Python 3.5 has now entered "feature freeze". By default new features may no longer be added to Python 3.5. (However, there are a handful of features tha

[python-committers] Reminder: 3.5 now has its own branch! "default" branch is now 3.6!

I've now pushed the 3.5.0 beta 1 release-engineering checkins to hg.python.org. At the same time I did this, I also created the 3.5 branch. Quick FAQ: Q: Where should I check in bugfixes for 3.5? A: In the "3.5" branch. You should also merge them forward into "default". Q: Where should I

Re: [python-committers] [Python-Dev] Reminder: 3.5 now has its own branch! "default" branch is now 3.6!

On 05/24/2015 06:01 PM, Chris Angelico wrote: Additional Q. What does this mean for buildbots? Will they immediately pick up the new branch? I don't know about "immediately", but yes the buildbots should get configured to point at the 3.5 branch, preferably soon. //arry/ _

Re: [python-committers] Reminder: 3.5 now has its own branch! "default" branch is now 3.6!

On 05/25/2015 02:03 AM, Serhiy Storchaka wrote: Perhaps needed version bump in the default branch? I think now Misc/NEWS will have two modifiable sections - for 3.5 (bugfixes) and for 3.6 (new features). That's a good point! I've added a "3.6.0 alpha 1" section as you suggest. That suggests

Re: [python-committers] [Python-Dev] Preserving the definition order of class namespaces.

On 05/25/2015 03:22 PM, Eric Snow wrote: On Mon, May 25, 2015 at 2:40 PM, Terry Reedy wrote: On 5/25/2015 3:40 PM, Eric Snow wrote: Since Larry already gave an exception, Conditional on 'general approval of the community'. Unless I misunderstood him, Larry gave me an unconditional exceptio

Re: [python-committers] Reminder: 3.5 now has its own branch! "default" branch is now 3.6!

On 05/25/2015 01:37 PM, Zachary Ware wrote: Should probably also actually bump the version (default still says it's 3.5.0b1: "Python 3.5.0b1+ (default:cf7e905ef5dd+, May 25 2015, 15:34:05)"). -- Zach Another good point! I checked with Benjamin and set it to the proper value ("Python 3.6.0a0

[python-committers] Python 3.5 schedule addendum adding a new Python 3.5.0 beta, this weekend

On behalf of the Python 3.5 release team: Due to a particularly bad bug ( http://bugs.python.org/issue24285 ), we're going to issue a new beta of Python 3.5 this weekend. This will not change the rest of the schedule; it'll just bump the remaining beta numbers up by 1. Thus the schedule is

[python-committers] [RELEASED] Python 3.5.0b2 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.0b2. Python 3.5.0b1 had a major regression (see http://bugs.python.org/issue24285 for more information) and as such was not suitable for testing Python 3.5.

Re: [python-committers] Ned Deily is release manager for Python 3.6

On 06/01/2015 11:09 AM, Barry Warsaw wrote: Please welcome Ned Deily as RM for Python 3.6. https://www.python.org/dev/peps/pep-0494/ We're in good hands. For two versions now Benjamin and Ned have been quietly cleaning up my mistakes after (nearly) every release. My guess is, Ned won't both

[python-committers] [RELEASED] Python 3.5.0b3 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.0b3. Python 3.5 has now entered "feature freeze". By default new features may no longer be added to Python 3.5. This is a preview release, and its use is

[python-committers] Reminder: Python 3.5 beta 4 is tagged in one week

Approximately a week from when I post this, I'll be tagging Python 3.5 beta 4, which is the last beta before we go to release candidates. Please wind up all your bug fixes soon, I'd really like checkins to 3.5 to stop soon. And a minor reminder: when we hit Release Candidate 1, I'll be swi

Re: [python-committers] [Python-Dev] Reminder: Python 3.5 beta 4 is tagged in one week

On 07/21/2015 06:35 PM, Robert Collins wrote: Cool. http://bugs.python.org/issue21750 is in a bad state right now. I landed a patch to fix it, which when exposed to users had some defects. I'm working on a better patch now, but need to either roll the prior patch completely back, or get the ne

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

On behalf of the Python development community and the Python 3.5 release team, I'm delighted to announce the availability of Python 3.5.0b4. Python 3.5.0b4 is scheduled to be the last beta release; the next release will be Python 3.5.0rc1, or Release Candidate 1. Python 3.5 has now entered "featu

[python-committers] Reminder: the "3.5" branch in CPython trunk is now 3.5.1

As I write this email I'm tagging Python 3.5.0 release candidate 1. This is the moment that we switch over to our new experimental workflow, where we use Bitbucket and pull requests for all future changesets that will get applied to 3.5.0. The Bitbucket repository isn't ready yet, and I'm s

[python-committers] Python 3.5.0rc1 is delayed by a day

We retagged Python 3.5.0rc1 today to fix two bugs that popped up late in the process. Release candidates are supposed to be software you genuinely would release, and I couldn't release Python with both those bugs. This delay rippled through the whole process, so it just isn't going out ton

[python-committers] Instructions on the new "push request" workflow for 3.5.0rc1+ through 3.5.0 final

As of Python 3.5.0rc1, the canonical repository for Python 3.5.0 is *no longer* on hg.python.org. Instead, it's hosted on Bitbucket on my personal account, here: https://bitbucket.org/larry/cpython350 Since 3.5.0rc1 isn't out yet I'm keeping the repository private for now. Once 3.5.0 rc1 i

[python-committers] [RELEASED] Python 3.5.0rc1 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.0rc1, also known as Python 3.5.0 Release Candidate 1. Python 3.5 has now entered "feature freeze". By default new features may no longer be added to Python

Re: [python-committers] Instructions on the new "push request" workflow for 3.5.0rc1+ through 3.5.0 final

On 08/10/2015 01:27 AM, Larry Hastings wrote: As of Python 3.5.0rc1, the canonical repository for Python 3.5.0 is *no longer* on hg.python.org. Instead, it's hosted on Bitbucket on my personal account, here: https://bitbucket.org/larry/cpython350 Since 3.5.0rc1 isn't out yet I

[python-committers] Sorry folks, minor hiccup for Python 3.5.0rc1

I built the source tarballs with a slightly-out-of-date tree. We slipped the release by a day to get two fixes in, but the tree I built from didn't have those two fixes. I yanked the tarballs off the release page as soon as I suspected something. I'm rebuilding the tarballs and the docs n

Re: [python-committers] Sorry folks, minor hiccup for Python 3.5.0rc1

On 08/10/2015 05:55 PM, Larry Hastings wrote: I yanked the tarballs off the release page as soon as I suspected something. I'm rebuilding the tarballs and the docs now. If you grabbed the tarball as soon as it appeared, it's slightly out of date, please re-grab. p.s. I s

Re: [python-committers] [Python-Dev] Sorry folks, minor hiccup for Python 3.5.0rc1

On 08/11/2015 05:29 PM, Matthias Klose wrote: On 08/11/2015 02:56 AM, Larry Hastings wrote: On 08/10/2015 05:55 PM, Larry Hastings wrote: I yanked the tarballs off the release page as soon as I suspected something. I'm rebuilding the tarballs and the docs now. If you grabbed the tarba

[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 hg.python.org/cpyth

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 you'd

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 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 basically what we d

[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

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

[python-committers] [RELEASED] Python 3.5.0rc3 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.0rc3, also known as Python 3.5.0 Release Candidate 3. The next release of Python 3.5 will be Python 3.5.0 final. There should be few (or no) changes to Pyt

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

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

[python-committers] Python 3.5.1 release schedule

At the request of the platform experts, 3.5.1 is now scheduled to happen simultaneously with 2.7.11. That means: Saturday November 21, 2015 tag 3.5.1rc1 Sunday November 22, 2015 release 3.5.1rc1 Saturday December 5, 2015 tag 3.5.1 final Sunday December 6, 2015 release 3.5.1

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

[python-committers] [RELEASED] Python 3.5.1rc1 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.1rc1. Python 3.5.1 will be the first update for Python 3.5. Python 3.5 is the newest version of the Python language, and it contains many exciting new featur

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

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

[python-committers] [RELEASED] Python 3.4.4 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.4. Python 3.4.4 is the last version of Python 3.4.4 with binary installers, and the end of "bugfix" support. After this release, Python 3.4.4 moves into "sec

Re: [python-committers] We will be moving to GitHub (hopefully) in 2016

On 01/04/2016 10:59 PM, Serhiy Storchaka wrote: Is it possible to keep the same hashes in both Mercurial and Git? Or at least the same short hashes? tl;dr: it's impossible. The hash is a SHA1 of the revision's "manifest", which contains all the metadata about the revision. To preserve the

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

<    1   2   3   >