python-committers July 2015

python-committers@python.org

29 participants
10 discussions

by Brett Cannon

I think the only people on it are Antoine, Georg, and myself. Antoine has said he has left python-dev, Georg is often busy with school, and I'm on a temp machine for a few weeks so I can't add any SSH keys for a while (heck I'll probably need new ones installed on my behalf once I have a permanent machine). Is anyone up for helping with adding SSH keys for people? It's basically taking someone's key as an attachment in an email, making sure it's RSA and not DSA, and then either creating a new file in a specific repo for them or appending it to their existing key file. P.S.: And I don't even remember how to get people added to the group of people who can add keys, so I probably need to find that out as well if anyone steps forward. =)

5 years, 9 months

"Gratuitous"? incompatibilities in the "fix only" releases

by Jesus Cea

Yesterday I upgraded one of my computer to 2.7.10 and a program working for years failed. The problem is this: """ http=httplib.HTTPConnection("127.0.0.1",8081) http.request("GET","/XXXXX/%f" %last_t, "", \ {"Authorization":"Basic %s" %base64.encodestring("%s:%s" %(a,b))}) """ base64.encodestring() creates base64 encoding with a final '\n'. This used to work until 2.7.9 but 2.7.10 if failing now with an exception about an "illegal character" in a header. I know that that code is faulty and I should drop the final '\n' or just use "base64.b64encode()" (my current fix). The point, thought, it that this code used to work in previous 2.7 releases but it is failing under 2.7.10. This incompatible change will be released in 3.4.4 too. I agree that new code is better, no argument here. My program was incorrect, sure. But I was under the impression that backwards incompatible code was forbidden in minor releases, except for very critical reasons (like the HTTPS security default backported to 2.7). I think that breaking working code during minor updates is risky and breaks user/programmer expectations. The change was done in <https://bugs.python.org/issue22928>. I think the change is the way to go, I don't ask for a revert (since 2.7.10 is already in the wild I want to keep it too in future 3.4.4) but I am interested in knowing the official statement of committers about backwards incompatible changes in minor releases for my own future reference. Sorry if this email seems confrontational. Not my intention, but my English is getting worse by the day :-). This is an inquiry about policy, not an attack. Thanks! -- Jesús Cea Avión _/_/ _/_/_/ _/_/_/ jcea(a)jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz

5 years, 9 months

[RELEASED] Python 3.5.0b4 is now available

by Larry Hastings

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 "feature freeze". By default new features may no longer be added to Python 3.5. This is a preview release, and its use is not recommended for production settings. An important reminder for Windows users about Python 3.5.0b4: if installing Python 3.5.0b4 as a non-privileged user, you may need to escalate to administrator privileges to install an update to your C runtime libraries. You can find Python 3.5.0b4 here: https://www.python.org/downloads/release/python-350b4/ Happy hacking, */arry*

5 years, 9 months

Reminder: Python 3.5 beta 4 is tagged in one week

by Larry Hastings

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 switching the canonical repo for 3.5 to a public Bitbucket repo. Any bug fixes that go in between RC 1 and final will only be merged using Bitbucket "pull requests". The new workflow experiment continues, //arry/

5 years, 9 months

MSDN subscriptions, Intel ICC licenses

by Brian Curtin

It's that time again: a batch of MSDN subscriptions are expiring, and I've already heard from a few of you, so in order to make it easier on the Microsoft end, I'll put together another batch of us to be renewed all at once. If you would like a renewal, I need the email address associated with your account as well as your subscriber ID. You can find the ID in the top left of https://msdn.microsoft.com/en-us/subscriptions/manage If you would like a first time subscription, I need your postal address and the email address you'd like to use for the account. We also now have a contact at Intel who can provide our developers with licenses for Intel ICC compilers. I don't know exactly what information they're going to need from you, but let me know if this is something you'd like to make use of. Brian

5 years, 9 months

Speaking of noticing tracker activity

by R. David Murray

In the recent thread on python-dev Nick mentioned our dependence on people noticing active contributors on the tracker. In that regard I'd like to recommend people take a look at the work of Martin Panter (vadmium). --David

5 years, 9 months

2.7 compilation problem on Mac 10.10.4 - Failure with mac specific modules

by Senthil Kumaran

This failure happens only in 2.7 branch in the source tree. [localhost 2.7]$ hg branch 2.7 [localhost 2.7]$ hg head 2.7 changeset: 96916:ca78b9449e04 branch: 2.7 user: Zachary Ware <zachary.ware(a)gmail.com> date: Thu Jul 16 00:24:48 2015 -0500 $./configure is OK $ make /opt/twitter/bin/gcc-4.2 -c -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I. -IInclude -I./Include -DPy_BUILD_CORE -o Python/mactoolboxglue.o Python/mactoolboxglue.c In file included from /System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:55, from /System/Library/Frameworks/Carbon.framework/Headers/Carbon.h:20, from Include/pymactoolbox.h:10, from Python/mactoolboxglue.c:27: /System/Library/Frameworks/CoreServices.framework/Frameworks/FSEvents.framework/Headers/FSEvents.h:486: error: expected ‘,’ or ‘}’ before ‘__attribute__’ make: *** [Python/mactoolboxglue.o] Error 1 If I disable Mac specific modules $ ./configure --disable-toolbox-glue $ make is fine. Has any else observed this? I am trying to determine if this a bug or an incompatibility of Mac Command Line Tools I have with the 2.7 sources, most likely it is the later. -- Senthil

5 years, 9 months

More explicit Code of Conduct for the issue tracker & core mailing lists?

by Nick Coghlan

Hi folks, The FreeBSD community recently posted their Code of Conduct guidelines for technical discussions at https://www.freebsd.org/internal/code-of-conduct.html I think their guidelines align pretty well with the way we try to run the CPython issue tracker and the core mailing lists, but we don't currently spell out those expectations for newcomers (or potential newcomers) as clearly as they have. Would folks mind if I drafted a CPython Code of Conduct inspired by their example, and proposed it for inclusion in the Developer's Guide? Regards, Nick. -- Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia

5 years, 9 months

New buildbots active

by Zachary Ware

Hi folks, Just wanted to let you know in case you hadn't seen them that there are a couple of new buildbots in service: one that builds on Windows in Release configuration [1] and one that builds the documentation and runs a couple of style checks on it [2]. Both are currently in the 'unstable' set, but I expect both of them to graduate to 'stable' status soon after an audit of the stability of the whole fleet. [1] http://buildbot.python.org/all/buildslaves/ware-win81-release [2] http://buildbot.python.org/all/buildslaves/ware-gentoo If anyone has suggestions for improvements to the Docs bot, I'm all ears. Eventually, I'd like to add a doctest step, but there's a lot of work that needs to go into fixing the doctests before I do that. Regards, -- Zach P.S.: for those receiving this message on python-committers, you may notice that it is also cross-posted to python-buildbots, a list that was recently set up for discussion of our buildbot fleet, mostly between buildslave and buildmaster operators. If you're interested, subscription is open [3] and the list is mirrored on Gmane [4]. [3] https://mail.python.org/mailman/listinfo/python-buildbots [4] http://dir.gmane.org/gmane.comp.python.devel.buildbots

5 years, 10 months

[RELEASED] Python 3.5.0b3 is now available

by Larry Hastings

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 not recommended for production settings. An important reminder for Windows users about Python 3.5.0b3: if installing Python 3.5.0b2 as a non-privileged user, you may need to escalate to administrator privileges to install an update to your C runtime libraries. You can find Python 3.5.0b2 here: https://www.python.org/downloads/release/python-350b3/ Happy hacking, //arry/

5 years, 10 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

python-committers July 2015