Re: [python-committers] My cavalier and aggressive manner, API change and bugs introduced for basically zero benefit

On 21 January 2017 at 23:32, Antoine Pitrou <anto...@python.org> wrote: > > Le 21/01/2017 à 12:27, Nick Coghlan a écrit : >> >> The Red Hat python-maint folks (Peter Viktorin et al) similarly tried >> to time things so there was a window to provide feedback from Fedor

Re: [python-committers] My cavalier and aggressive manner, API change and bugs introduced for basically zero benefit

focus was on string hashing, the secrets module, and direct use of the os.urandom() and os.getrandom() APIs. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing list python-committers@python.org

Re: [python-committers] My cavalier and aggressive manner, API change and bugs introduced for basically zero benefit

reamline the patch review process for simple fixes, but it's far from clear at this point whether or not that will be enough to get the issue metrics moving in a healthier direction. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ py

[python-committers] 3.6 release blocker review request

needed, but now we need them again for error detection purposes). Regards, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo

Re: [python-committers] 3.6 branch now open only for 3.6.0 release critical fixes and doc updates!

a. > > I'm not sure that a trailing '-' is the right way to mark this. Maybe > "rc1+dev" or similar? The "3.6.0rc0+" notation would reflect that it's not a beta any more, but still comes before rc1. (While Donald's right that PEP 440 recommends a ".dev0" suffix

Re: [python-committers] Promote Xiang Zhang as a core developer

s (i.e. the "to work on X, Y, Z" comments in the developer log), rather than saying "feel free to approve changes anywhere in the code base". Branching out from that initial base (if they choose to do so) can then happen over time as they gain familiarity and confidence in more are

Re: [python-committers] Promote Xiang Zhang as a core developer

and fixed an obscure problem in the new multi-phase extension module import system [1] was a genuinely enjoyable experience for me as a patch reviewer (and the patch itself was complete and correct, so the only thing I needed to add was a NEWS entry). Cheers, Nick. [1] http://bugs.python.org/

Re: [python-committers] Greeting from INADA Naoki

On 28 September 2016 at 03:35, INADA Naoki <songofaca...@gmail.com> wrote: > Hi, all. > > Thank you, Yury and all for approve me. Welcome, and thank you for your previous work and patience! :) Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Bris

Re: [python-committers] commit privileges for INADA Naoki

t that I gained my own commit privileges back in the CVS days specifically to work on updates to PEP 346 rather than due to my work on the activity of general patch wrangling (which I still generally don't do outside my particular areas of interest, and even then, hitting a bug or API limitation mysel

Re: [python-committers] commit privileges for INADA Naoki

many asyncio related > discussions/PRs, on python-ideas and bug tracker. +1 from me. I've always found him receptive to feedback, and he's illustrated he definitely has the patience needed for the role ;) Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com

Re: [python-committers] Xavier de Gaye

ue: support of the android platform" > https://bugs.python.org/issue26865 Thanks for the update, and welcome again Xavier! Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing list

Re: [python-committers] PEP process with github

n-dev (or the appropriate corresponding venue), Guido or the BDFL-Delegate may direct discussion of the finer details to a GitHub PR if the mailing list consensus is that the overall PEP is a good idea, but there are some specifics to work out before the PEP can be accepted. Cheers, Nick. -- Nick Coghlan

Re: [python-committers] The peps repo is now on GitHub!

org around, just as we kept svn.python.org. We may want to add banners to point people at the GitHub repos for the latest versions, though. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers maili

Re: [python-committers] bugs.python.org, job status, and contributors (aka not core devs)

list of current triagers? (even if we don't have precise dates) Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinf

Re: [python-committers] Promote Xavier de Gaye as a core developer

rather than increasing the number of fixes and improvements actually applied :) Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/

[python-committers] Tweaks to the Motivations & Affiliations page

ould (at least in theory) be obtained by mining publicly available information, and instead ask contributors if they're willing to explicitly volunteer that data in a central location. Regards, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia __

Re: [python-committers] Please add your GitHub username to your bugs.python.org account

the GitHub username field. The GitHub API doesn't strip that automatically, so we may need to clean it either in Roundup directly or by stripping it in the bots when they retrieve the username information from Roundup. Cheers, Nick. -- Nick Coghlan

Re: [python-committers] Making the PSF CoC apply to core developers

r patches (rather than needing to suggest changes), so I can be confident they've worked out for themselves what "good" looks like. (Such a bot would be useful even without that though, as the folks actually reviewing and merging the commits would still be the ones to propose new c

Re: [python-committers] Call For Participants For The 2016 Python Language Summit

to actually work through the details of getting it added via the PEP process. I'm also not aware of any explicit documentation of the underlying FFI from a C API/ABI perspective, which is what would be needed for tools like SWIG and Cython to support it as an alternative to the ful

Re: [python-committers] Call For Participants For The 2016 Python Language Summit

at do we know about network security management now that we didn't know back when the ssl module was added to Python 2.6?") Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing list py

Re: [python-committers] Making the PSF CoC apply to core developers

that community members actually strive to conduct themselves, than it helps newcomers better assess "Am I likely to feel comfortable here?". Regards, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committer

Re: [python-committers] Making the PSF CoC apply to core developers

ns in writing since we *can't* assume a shared understanding of phrases like "don't be a jerk" and "don't harass people" when attendees are flying in from all over the world. Regards, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia __

Re: [python-committers] Deprecation Policy PEP

ve to contend with. Although if anyone has both the C/POSIX skills and the necessary roundtuits to help move Geoffrey Thomas's "pythonmux" [1] idea forward, we may be able to settle the preferred behaviour of the "/usr/bin/python" path once and for all. Cheers, Nick. [1] https://github.co

Re: [python-committers] Deprecation Policy PEP

cationWarning by default, but still hide PendingDeprecationWarning globally. That idea actually seemed to garner general approval, so I suspect the main reason the discussion died out was the fact that it's a bit fiddly to implement. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com

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

my own activities. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Would anyone STOP contributing to Python if we used GitHub?

eing given a free choice between them and their more familiar proprietary competitors. By the same taken, nobody would consider a community event that refused to cater to special dietary needs to be a particularly welcoming event, which is why I consider it important to offer a free-softw

Re: [python-committers] PSA: replace your DSA keys for SSH

to Windows: http://blogs.msdn.com/b/powershell/archive/2015/10/19/openssh-for-windows-update.aspx As that stabilises, it may be worth offering common OpenSSH based instructions for Windows as well. Regards, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers

[python-committers] Initial Motivations & Affiliations page has been merged

eir own entries. However, I figured it would be better to put the page live and have that discussion here as people start filling it out, rather than speculating further on the issue tracker. Regards, Nick. -- Nick Coghlan | ncogh...@gmail.com

Re: [python-committers] Initial Motivations & Affiliations page has been merged

On 12 October 2015 at 13:08, Nick Coghlan <ncogh...@gmail.com> wrote: > On 11 October 2015 at 22:33, Nick Coghlan <ncogh...@gmail.com> wrote: >> Based on the thread a few weeks ago and the subsequent issue tracker >> discussion at http://bugs.python.org/issue25194, I j

Re: [python-committers] Initial Motivations & Affiliations page has been merged

On 11 October 2015 at 22:33, Nick Coghlan <ncogh...@gmail.com> wrote: > Based on the thread a few weeks ago and the subsequent issue tracker > discussion at http://bugs.python.org/issue25194, I just committed an > initial version of a "Motivations & Affiliations"

Re: [python-committers] PSA: replace your DSA keys for SSH

org >> >> ___ >> python-committers mailing list >> python-committers@python.org >> https://mail.python.org/mailman/listinfo/python-committers > _______ > python-committers mailing list >

Re: [python-committers] Python 3.6 Release Schedule Details

allers to be tested (for example). Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Python 3.6 Release Schedule Details

ick. [1] https://fedoraproject.org/wiki/Changes/Python_3_as_Default#Owner [2] https://badges.fedoraproject.org/badge/parselmouth -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing list python-committers@python.org

Re: [python-committers] SSH problems attempting to access hg.python.org

ht be a problem with OpenSSH 7.1p1 and ssh-ed25519 host keys (it's the only remote SSH host I using with an ed25519 key - all the others are still ssh-rsa). Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-com

Re: [python-committers] SSH problems attempting to access hg.python.org

d the RSA key for use on hg.python.org. Ah well, good motivation to finally generate some ed25519 keys of my own :) Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing list python-committers@

[python-committers] SSH problems attempting to access hg.python.org

048 SHA256:kz2qX96utlWroXvMf75x2WFiL0o2SEeHnX7eJStd3wc ncoghlan@llamedos (RSA) -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Idea: listing commercial prioritisation options as a new section in the developer guide?

On 20 September 2015 at 03:04, Antoine Pitrou <anto...@python.org> wrote: > > Le 19/09/2015 18:45, Nick Coghlan a écrit : >> >> That's part of it, but I also think we (as in those of us with commit >> privileges that are also professional developers) bear the >

Re: [python-committers] Idea: listing commercial prioritisation options as a new section in the developer guide?

On 20 Sep 2015 00:02, "Antoine Pitrou" wrote: > > > It doesn't sound like the devguide is ideally the right place for it. > > Actually, for a guide devoted to attract new contributors, saying "hey, > we'd really like you to contribute on a volunteer basis, but here is a > list

Re: [python-committers] Idea: listing commercial prioritisation options as a new section in the developer guide?

On 20 Sep 2015 02:40, "Barry Warsaw" <ba...@python.org> wrote: > > On Sep 19, 2015, at 03:43 PM, Nick Coghlan wrote: > > >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 &g

Re: [python-committers] getting help with the hgaccounts alias

On 24 Jul 2015 01:38, Jesus Cea j...@jcea.es wrote: I wonder about the new PSF infraestructure/programming volunteers. Never heard of them and I am more than willing to help out. The infra team handles the back end servers for PyPI, PyCon, python.org, et al. Folks with the keys to the kingdom

Re: [python-committers] Speaking of noticing tracker activity

, helpful reviews and patches from Martin Panter. +1 from me as well. I was actually thinking of Martin when I wrote the comment David referenced, but hadn't done the research to look into his wider involvement in tracker discussions. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com

Re: [python-committers] More explicit Code of Conduct for the issue tracker core mailing lists?

On 17 July 2015 at 01:49, Meador Inge mead...@gmail.com wrote: On Thu, Jul 16, 2015 at 10:08 AM, Nick Coghlan ncogh...@gmail.com wrote: Given the global nature of the lists, I think we should be giving folks *at least* 24 hours to reply to a question before assuming they're not going

Re: [python-committers] More explicit Code of Conduct for the issue tracker core mailing lists?

On 16 July 2015 at 14:16, Steven D'Aprano st...@pearwood.info wrote: On Wed, Jul 15, 2015 at 12:29:52PM +1000, Nick Coghlan wrote: [...] 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

[python-committers] More explicit Code of Conduct for the issue tracker core mailing lists?

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

Re: [python-committers] Co-maintainer(s) for contextlib, dis and/or runpy?

On 28 Jun 2015 8:57 pm, Tal Einat talei...@gmail.com wrote: On Sat, Jun 27, 2015 at 2:29 PM, Nick Coghlan ncogh...@gmail.com wrote: On 27 June 2015 at 15:08, Robert Collins robe...@robertcollins.net wrote: I'm happy to provide on demand reviews. I an take on the backporting easily enough

Re: [python-committers] Co-maintainer(s) for contextlib, dis and/or runpy?

On 28 June 2015 at 00:47, Serhiy Storchaka storch...@gmail.com wrote: On 27.06.15 14:35, Nick Coghlan wrote: I also added you to the nosy list for the contextlib issue that Serhiy originally pinged me about :) The patch already was approved by you. I reviewed the patch and it LGTM too. I

Re: [python-committers] Co-maintainer(s) for contextlib, dis and/or runpy?

/ncoghlan/contextlib2/, but the main problem with it is that it's old CI service went away, and I never got around to finding a replacement. Regards, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing

Re: [python-committers] Co-maintainer(s) for contextlib, dis and/or runpy?

On 27 June 2015 at 20:42, Yury Selivanov yselivanov...@gmail.com wrote: Hi Nick, I've added myself to dis contextlib modules on the experts list. Thanks! I also added you to the nosy list for the contextlib issue that Serhiy originally pinged me about :) Cheers, Nick. -- Nick Coghlan

[python-committers] Co-maintainer(s) for contextlib, dis and/or runpy?

work that I struggle to find the time for :( The affected modules: * contextlib * dis * runpy Regards, Nick. P.S. In the specific case of contextlib, I'm also interested in finding someone willing to take up maintenance of the contextlib2 backport: https://pypi.python.org/pypi/contextlib2 -- Nick

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

, there's no need for a pure Python implementation - Guido rejected the idea of a pure Python fallback for the math module a while back (http://bugs.python.org/issue23595) Regards, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia

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

On 13 May 2015 03:47, Brett Cannon br...@python.org wrote: On Tue, May 12, 2015 at 1:05 PM Larry Hastings la...@hastings.org wrote: [SNIP] What do you think? My votes are as follows: Workflow 0: -0.5 Workflow 1: +1 Workflow 2: +0.5 Please cast your votes, Workflow 0: -0

Re: [python-committers] changing the python version on the 2.7 branch

string, rather than 2.7.10-. Regards, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Do people prefer pushing feature repos or one massive patch?

combine posting a patch series with the rebase if needed setting for submitting approved changes. It's not a model Kallithea currently supports, but it's one I'd like to see it handle at some point in the future) Regards, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia

Re: [python-committers] Proposed core developer for contributing to multiprocessing

, and that's something which varies on a case by case basis. Regards, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python

Re: [python-committers] MSDN Subscriptions/Renewals

On 14 November 2014 12:08, Nick Coghlan ncogh...@gmail.com wrote: On 14 November 2014 09:04, Brian Curtin br...@python.org wrote: Hey all, Since I've gotten a couple of requests now for MSDN renewals, I may as well try to do them in a big batch. If you have an MSDN subscription

Re: [python-committers] Commit rights for Robert Collins

On 9 Oct 2014 02:34, Antoine Pitrou anto...@python.org wrote: Le 04/10/2014 07:47, Michael Foord a écrit : On 4 Oct 2014, at 11:15, Benjamin Peterson benja...@python.org wrote: hgaccou...@python.org Thanks. I've forwarded this to Robert. For the record, he hasn't contacted us

Re: [python-committers] cherry picking after rc

(*cough*totally*cough*) biased, but attempting to accommodate redistributors when it doesn't place any excessive demands on the upstream release cycle sounds like a fine approach to me :) Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia

[python-committers] Anatoly (again)

Why is Anatoly posting to python-dev? I thought he was banned when he was banned from the tracker. I refuse to waste my time trying to reason with him, and I consider the just ignore him approach to be unacceptable, as it leaves him free to waste everyone *else's* time trying to break through his

Re: [python-committers] Mark Lawrence

for a status update. Regards, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Commit rights for Robert Collins

, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers

[python-committers] Contact info for possible workflow tool security issue

, and their maintenance arrangements would be a nice thing to have... -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python

Re: [python-committers] New mailing list for workflow/workflow infrastructure discussion/tasks

On 16 Apr 2014 21:07, R. David Murray rdmur...@bitdance.com wrote: On Wed, 16 Apr 2014 18:02:31 -0400, Terry Reedy tjre...@udel.edu wrote: On 4/16/2014 4:49 PM, R. David Murray wrote: Apologies for the cross post, but I want to make sure committers who aren't reading python-dev for one

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

On 18 Mar 2014 07:37, Victor Stinner victor.stin...@gmail.com 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 6ba468d4fa96) * I removed 3.4.1 section: changes of 3.4 after

Re: [python-committers] Brian Kearns for commit

On 11 Mar 2014 09:10, Antoine Pitrou anto...@python.org wrote: On lun., 2014-03-10 at 16:02 -0700, Alex Gaynor wrote: Hi all, I'd like to propose Brian Kearns for commit. He's been a committer on PyPy for about a year and a half now, and in particular he's done a bunch of Python

[python-committers] PEP 450: Commit access for Steven D'Aprano?

always the option of pinging core-mentors...@python.org with any specific questions). Steven: http://docs.python.org/devguide/coredev.html Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing

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

On 26 January 2014 02:14, Antoine Pitrou solip...@pitrou.net wrote: On dim., 2014-01-26 at 01:40 +1000, Nick Coghlan wrote: I think an extra beta is still a good idea, though - I'd like to get at least the builtins that are already supported converted, since that clearly demonstrates

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

integration (http://bugs.python.org/issue20264) 4. Adding a commit hook that ensures clinic files have been regenerated prior to commit/push Regards, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing list

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

to Argument Clinic for 3.4 after all. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] PEP 462: Workflow automation for CPython

steps :) Cheers, Nick. P.S. https://www.youtube.com/watch?v=xGLMe2dyx6k goes into more detail on how Elastic recheck works -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing list python-committers@python.org

Re: [python-committers] LCA2014 presentation on Zuul, OpenStack's merge gating system

On 19 January 2014 20:59, Antoine Pitrou solip...@pitrou.net wrote: On dim., 2014-01-19 at 15:34 +1000, Nick Coghlan wrote: Rather than suggesting wholesale changes to our own infrastructure, what I am suggesting we consider is devoting time (and potentially PSF funding) to getting Zuul

Re: [python-committers] Commit access for Yury Selivanov?

trying to figure out how his profile is different from Vajrasky's profile. By the way, I also proposed to mentor Vajrasky. Victor Le 19 janv. 2014 21:34, Terry Reedy tjre...@udel.edu a écrit : On 1/19/2014 1:30 AM, Nick Coghlan wrote: Hi, I'd like to suggest granting commit access to Yury

[python-committers] LCA2014 presentation on Zuul, OpenStack's merge gating system

of things. Regards, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers

[python-committers] Commit access for Yury Selivanov?

to merge them on his behalf. Regards, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Updated schedule for Python 3.4

the infrastructure and community in place to maintain a CPython 2 fork, so backporting a few additional changes from CPython 3 really doesn't make a big difference to that workload. Cheers, Nick. K From: Nick Coghlan [mailto:ncogh...@gmail.com] Sent: Friday, January 17, 2014 7:51

Re: [python-committers] Updated schedule for Python 3.4

On 16 Jan 2014 21:54, Kristján Valur Jónsson krist...@ccpgames.com wrote: I suppose different projects have different ways, but I'm actually talking about commercial projects with which I am somewhat familiar. Once a project goes into feature freeze, it is branched off so that continued feature

Re: [python-committers] Updated schedule for Python 3.4

On 17 Jan 2014 01:02, Kristján Valur Jónsson krist...@ccpgames.com wrote: The hope is that by not adding features to 2.x, people will flock around 3.x en masse :) Very few of us think that way - it's that we think Python 3 is a better language in most ways, and it is certainly much easier and

Re: [python-committers] Updated schedule for Python 3.4

On 17 Jan 2014 03:25, Serhiy Storchaka storch...@gmail.com wrote: четвер, 16-січ-2014 15:03:28 Georg Brandl написано: Am 16.01.2014 14:47, schrieb Antoine Pitrou: The question is less for us than for occasional contributors who see their patches or feature requests languish on the

Re: [python-committers] Some topics I have suggested for the language summit

ways we can better combine efforts, and that we can definitely accommodate 5 people, but to check with you regarding numbers if more OREC folks will be in Montreal for the summit day and would like to attend. Which day is the summit again? April 6th? Cheers, Nick. -- Nick Coghlan | ncogh

Re: [python-committers] clinic churn after beta2

On 8 Jan 2014 17:06, Georg Brandl g.bra...@gmx.net wrote: Am 08.01.2014 03:23, schrieb Benjamin Peterson: On Tue, Jan 7, 2014, at 06:06 PM, Nick Coghlan wrote: On 8 Jan 2014 08:44, Eric V. Smith e...@trueblade.com wrote: On 1/7/2014 7:33 PM, Benjamin Peterson wrote: A PyPI module

Re: [python-committers] clinic churn after beta2

On 9 Jan 2014 02:34, Georg Brandl g.bra...@gmx.net wrote: Am 08.01.2014 11:08, schrieb Nick Coghlan: On 8 Jan 2014 17:06, Georg Brandl g.bra...@gmx.net mailto: g.bra...@gmx.net wrote: Am 08.01.2014 03:23, schrieb Benjamin Peterson: On Tue, Jan 7, 2014, at 06:06 PM, Nick Coghlan

Re: [python-committers] clinic churn after beta2

On 8 Jan 2014 07:11, A.M. Kuchling a...@amk.ca 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

Re: [python-committers] clinic churn after beta2

On 8 Jan 2014 08:44, Eric V. Smith e...@trueblade.com wrote: On 1/7/2014 7:33 PM, Benjamin Peterson wrote: A PyPI module is not so great because you'll have to change every formatting operation to use a function from a module rather than the % operator or the format method. I think this

Re: [python-committers] clinic churn after beta2

On 8 Jan 2014 10:36, Larry Hastings la...@hastings.org wrote: 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

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

On 7 Jan 2014 07:34, Ethan Furman et...@stoneleaf.us wrote: On 01/06/2014 02:21 PM, Barry Warsaw wrote: On Jan 06, 2014, at 01:34 PM, Larry Hastings wrote: The thing is, I feel like this is borderline between bug fix and new feature. But without adding this, we would make a lot of the

Re: [python-committers] Anatoly has been warned about his behaviour potentially leading to his loss of tracker privileges

we're falling into the Ostracizers are Evil trap in refusing to ban Anatoly despite on ongoing pattern of detrimental behaviour that has persisted over years: http://www.plausiblydeniable.com/opinion/gsf.html Regards, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia

Re: [python-committers] Anatoly has been warned about his behaviour potentially leading to his loss of tracker privileges

and at least get him out of everyone's hair. We tried to get him to be a productive contributor, it's time to admit we failed, and stop him being a drag on everyone else. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia

Re: [python-committers] Anatoly has been warned about his behaviour potentially leading to his loss of tracker privileges

on his behalf. I'm willing to be the bearer of bad news, and let Anatoly know this is being done, and cc' Guido and Ezio (as I'll also pass along their offers of assistance). Regards, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia

Re: [python-committers] Anatoly has been warned about his behaviour potentially leading to his loss of tracker privileges

of ignoring Anatoly. (And FTR I don't think I'm wasting my time -- if anything I'm sharpening my already nearly-limitless patience ;). It took about three years of actively trying to help him for Anatoly to exhaust mine :P Regards, Nick. -- Nick Coghlan | ncogh...@gmail.com

Re: [python-committers] Thank you

to come! Welcome and thanks for finally resolving that long standing test suite limitation where the embedding tests couldn't be run on Windows :) Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers

Re: [python-committers] Zachary Ware for commit access?

On 1 Nov 2013 13:50, Brian Curtin br...@python.org wrote: Hi all, What do you think about giving commit access to Zachary Ware? He's been active on the tracker for a while and has contributed a good bit of Windows code. I'm not doing much Windows stuff these days, and unfortunately I

Re: [python-committers] Closing the 2.6 branch?

On 31 Oct 2013 00:31, Martin v. Löwis mar...@v.loewis.de wrote: Am 30.10.13 15:13, schrieb Barry Warsaw: Now that 2.6.9 is out, I wonder if there's anything we can or should do to the Mercurial repository to explicitly prevent commits to the 2.6 branch? We have we done to older branches?

Re: [python-committers] Closing the 2.6 branch?

On 31 Oct 2013 01:54, Barry Warsaw ba...@python.org wrote: On Oct 31, 2013, at 01:28 AM, Nick Coghlan wrote: There's a trick to get the PEP 0 generator to move the release PEP to the historical section, too. I'd have to look at the source code to remember what it is, though. elif

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

be fixed now given my last push. On a second review, I actually understood the rationale behind Jeremy's proposed test patch in http://bugs.python.org/issue18396 and accepted it. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia

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

, but this early in the cycle erring on the side of just ship it is a good way to go. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman

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

On 3 Aug 2013 10:25, Larry Hastings la...@hastings.org wrote: 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

[python-committers] Changes column on filtered BuildBot waterfall views?

I don't see any entries in the Changes column when I look at a filtered BuildBot waterfall like http://buildbot.python.org/all/waterfall?category=3.x.stable Is that expected? A bug in our BuildBot setup? A bug in BuildBot itself? (This is in Firefox 22 on Fedora 18) Cheers, Nick. -- Nick

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

that arise due to changes in the underlying platforms seem to be the two main reasons we do it :) Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing list python-committers@python.org http

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

). Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] what's going on with Misc/NEWS?

the tooling to merge the NEWS entries and clear NEWS.next before we can next do a release for 3.3 and 3.4, and Georg and Larry are happy with that notion. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers

Re: [python-committers] what's going on with Misc/NEWS?

On Sun, May 26, 2013 at 1:10 AM, Brett Cannon br...@python.org wrote: On Sat, May 25, 2013 at 4:40 AM, Nick Coghlan ncogh...@gmail.com wrote: The 3.3 branch layout would look like this: NEWS.next/ 3.3.txt # Categorised changes Categorized how? E.g. Core,Lib,Docs, etc.? Or 3.3

<    1   2   3   >