Re: [python-committers] Can we delete https://hg.python.org/coding/cpython/?
Seems that way. It doesn’t have any change sets not in the canonical repo. $ hg incoming https://hg.python.org/coding/cpython comparing with https://hg.python.org/coding/cpython searching for changes no changes found > On 19 Dec, 2016, at 17:23, Brett Cannon wrote: > > It's erroneously labeled as the "official python repo" and created by some > stranger. > ___ > python-committers mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Should I delay 3.5.3 and 3.4.6 by two weeks?
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 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 seemed sensible. > > 3.6 just slipped by two weeks. So now there's less than two weeks between > 3.6.0 > final shipping and tagging the release canddiates for 3.5.3 and 3.4.6. This > isn't as much time as I'd like. > > If I had total freedom to do as I liked, I'd slip my releases by two weeks to > match 3.6. But there might be people planning around 3.5.3 and 3.4.6--like > Guido was waiting for 3.5.3 for something iirc. > > So, if you have an opinion, please vote for one of these three options: > > * Don't slip 3.5.3. and 3.4.6. > * Slip 3.5.3 and 3.4.6 by two weeks to match 3.6.0. > * Slip 3.5.3 and 3.4.6 by a whole month, to give 3.6.0 the ability to >slip again without us having to change the release. I would appreciate a 3.5.3 release which doesn't slip, or which only slips by a week, to be available before the Debian freeze. Neither Debian nor Ubuntu ship the 3.4 branch anymore, so for 3.4 I'm fine with any solution. Matthias ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] MSDN Subscriptions - first timers and renewals
Hey all, I heard some of you wanted MSDN subscription renewals from Santa Claus, so I can take care of that and put in a good word for you. If you're an existing subscriber I just need the email and subscriber ID for your account, which you can get out of some of the emails they send you, or via https://msdn.microsoft.com/en-us/subscriptions/manage/. If you don't have a subscription and would like access to various Microsoft tools to help you make Python better, e.g., Visual Studio, Windows images, etc., they give us complimentary access to the Microsoft Developer Network to enable that. Each subscription gets you one year of access to download those tools (plus some amount of Azure credit), and they give us continued renewals as long as we're using them and making Python better. If you'd like a subscription for the first time, I need the following info: First Name: Last Name: Email Address: Project/Company: Python Software Foundation Complete Mailing Address: Phone Number: I'd like to batch these up so it makes things easier on the folks at Microsoft who help us out with this, so get me your details and I'll send a batch next week on the 28th, and any batches after that I'll just gauge by how many are coming in. Thanks, Brian ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
