Mailman 3 December 2015 - python-committers

Idea: listing commercial prioritisation options as a new section in the developer guide?
by Nick Coghlan May 3, 2016

May 3, 2016

Hi folks, A question I occasionally get asked by organisations that use Python commercially but don't currently employ any core developers themselves is "How can we prioritise getting particular issues fixed/reviewed/merged?". A related problem we have in the PSF is knowing which core developers are available for freelance & consulting work when organisations approach us regarding larger projects. At the moment, those kinds of referrals are reliant on Board members' personal knowledge of who amongst the core development team is open to that style of employment and making direct introductions, which is neither transparent nor fair. As such, what do folks think of the idea of a new, *opt-in* section in the developer guide, similar to the current experts index, but allowing core developers to indicate the ways in which we're willing to provide paid support. I'd see four likely sections in such a document: * Freelance consultants: folks that are available for contract opportunities at the individual level * Consulting companies: folks that are available for contract opportunities, but work for larger consulting organisations rather than contracting directly * Commercial redistributors: folks that work for commercial Python redistributors and are willing and able to both help in getting customer issues resolved and in acting as a point of escalation for their colleagues * Direct employment: folks that work directly for organisations that use Python extensively, and hence are able to act as a point of escalation for their colleagues The latter three categories would be further broken out by employer, while the first would just be a list of names and professional contact details. Regards, Nick. P.S. Disclosure: I do have my own interests in mind here, both personally and professionally. At a personal level, I'm a strong believer in "If you want me to care about your opinion on how I spend my time, pay me", so it makes sense to me to make it easy for more commercially-minded core developers to say "Pay me or my employer if you'd like to influence my time allocation". Professionally, it's definitely in my interests for both Python core developers and commercial Python redistributors to be recognised as a group for their expertise and overall influence on the technology sector. -- Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia

5 8

[RELEASED] Python 3.4.4 is now available
by Larry Hastings Dec. 21, 2015

Dec. 21, 2015

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 "security fixes only" mode, and future releases will be source-code-only. You can see what's changed in Python 3.4.4 (as compared to previous versions of 3.4) here: https://docs.python.org/3.4/whatsnew/changelog.html#python-3-4-4 And you can download Python 3.4.4 here: https://www.python.org/downloads/release/python-344/ Windows and Mac users: please read the important platform-specific "Notes on this release" section near the end of that page. One final note. 3.4.4 final marks the end of an era: it contains the last Windows installers that will be built by Martin von Loewis. Martin has been the Windows release "Platform Expert" since the Python 2.4 release cycle started more than twelve years ago--in other words, for more than half of Python's entire existence! On behalf of the Python community, and particularly on behalf of the Python release managers, I'd like to thank Martin for his years of service to the community, and for the care and professionalism he brought to his role. It was a pleasure working with him, and we wish him the very best in his future projects. We hope you enjoy Python 3.4.4! Happy holidays, //arry/

1 0

JetBrains licenses for IDEs
by Vinay Sajip Dec. 19, 2015

Dec. 19, 2015

Several committers have used JetBrains' PyCharm IDE in the past, and I am the person who initially requested a license for Python committers. The last license we had expired a while ago, and a couple of people asked me about renewals. So I applied to JetBrains for a renewed license. They have now very kindly responded with licenses for Python committers - not just for PyCharm but for a number of their other development tools as well - including IntelliJ IDEA, AppCode, CLion, PyCharm and others. The terms of the license (which is valid for a year, but should be renewable) restricts usage to development of non-commercial, open source software. JetBrains' new licensing model means that (IIUC) each user needs to have a JetBrains account. Once you have set one up, let me know if you're interested in using the tools and I'll email you a link you can visit to get your license. Please note that we have a limited pool of licenses, and each click of the link will, I understand, take one license from the pool. Please don't share this link with anyone else, and if another committer asks you about it, please refer them to me (so that I can keep track of who has what). Regards, Vinay Sajip

1 0

Would anyone STOP contributing to Python if we used GitHub?
by Brett Cannon Dec. 15, 2015

Dec. 15, 2015

Over at core-workflow@ we are discussing details of the GitHub and GitLab proposals and one of the worries the GitLab supporters have brought up is that some core developers could flat-out stop contributing if we moved to GitHub. Now I have major doubts that's true as no one has told me that is the case yet after all the time that this workflow change has been discussed, but I would not be doing my due diligence if I didn't check to make sure I truly didn't need to consider this in my final decision. So, if you would actually *stop* contributing to Python's development if we switched to GitHub, please let me know (and this is obviously addressed to us core developers and not external contributors since they can always submit old-style patches through the issue tracker). This is not asking about preference or you would only begrudgingly use GitHub since some people will begrudgingly do whatever decision I reach, so please don't reply about begrudging use so I can keep the signal:noise ratio down; only reply with "I will quit Python over GitHub" emails. You can email me privately if you want, but let me know if you care if I share this with very select people like Guido. Also realize that anyone who says they will walk away will be held to their word; if we still choose to switch to GitHub I will expect you to no longer contribute to Python and will personally hold you to your word (which also makes private emails a little moot, but I can understand if you would rather fade away than make a public political statement). I'm saying this not to be threaten people into not giving me an answer but because I want to get the point across that this is a very serious question, so I don't want any wavering on the answer. Please let me know by Wednesday, Dec 16 if you would walk away. I know it's not a ton of time but I said I expect silence so I don't want to be sitting around to find out the results of this question.

9 16

I am nos selectable in the bugtracker
by Jesus Cea Dec. 11, 2015

Dec. 11, 2015

After sending my new SSH key I have recovered "push" abilities in the mercurial repository, but it looks like I am not present in the bug tracker "assigned to" field. Thanks for your time. -- 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

3 2

[RELEASED] Python 3.5.1 and 3.4.4rc1 are now available
by Larry Hastings Dec. 6, 2015

Dec. 6, 2015

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 3.5.1 here: https://www.python.org/downloads/release/python-351/ And you can find Python 3.4.4rc1 here: https://www.python.org/downloads/release/python-344rc1/ Python 2.7.11 shipped today too, so it's a Python release-day hat trick! Happy computing, //arry/

1 0

Committer missing :)
by Jesus Cea Dec. 6, 2015

Dec. 6, 2015

I was trying to push a patch but it seems I am not a committer anymore. My name vanished of <https://hg.python.org/committers.txt> and the tracker. I guess I had a DSA key in hg.python.org and those are not valid anymore, but looks like I am not a documented committer anymore in order to send a new 2048 bits RSA key. I don't know if this is a mistake or a decision. Just let me know. -- 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

4 3

MSDN Subscription Expired
by Ethan Furman Dec. 4, 2015

Dec. 4, 2015

Woops. Can I get it renewed? -- ~Ethan~

2 3