Re: [python-committers] Commit privs for Serhiy Storchaka?

середа 26 грудень 2012 19:44:34 Eli Bendersky ви написали: On Wed, Dec 26, 2012 at 9:38 AM, Georg Brandl g.bra...@gmx.net wrote: The SSH key is added; tracker privileges were already given. Welcome Serhiy! Yes, welcome! Serhiy, if you haven't already done so, please subscribe to

Re: [python-committers] Commit privs for Serhiy Storchaka?

On 26.12.12 19:53, Antoine Pitrou wrote: Le mercredi 26 décembre 2012 à 18:38 +0100, Georg Brandl a écrit : The SSH key is added; tracker privileges were already given. Welcome Serhiy! Welcome indeed (und fröhlich Weihnachten)! Thank you. But you have something mixed up, Antoine. ;) Je

[python-committers] Pending contributor agreement

Several contributor agreement were send last months and wait for accepting. Ben Morgan (Ben.Morgan) http://bugs.python.org/issue12004 Zack Weinberg (zwol) http://bugs.python.org/issue16624 Robert Xiao (nneonneo) http://bugs.python.org/issue17051 Ramchandra Apte (ramchandra.apte) /I'm not sure

Re: [python-committers] Pending contributor agreement

Did you receive a form from Amir Szekely (kichik) [http://bugs.python.org/issue16800]? ___ 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?

24.05.13 15:24, Brett Cannon написав(ла): I was trying to do a simple merge of a doc change between 3.3 and default and the usual Misc/NEWS conflict came up. But when I looked at the diff it was massive! Turns out that Misc/NEWS in default goes from 3.3.1rc1 to 3.4.0a1

Re: [python-committers] clinic churn after beta2

вівторок, 07-січ-2014 13:42:29 Łukasz Langa написано: Let me play the devil’s advocate here: how much do we risk in future maintainability costs if we move to Argument Clinic in Python 3.5 and leave large parts of Python 3.4 uncovered by it? I mean that we can get some ugly diffs between

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

четвер, 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 tracker, and lose interest. To be honest, most patches and feature

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

25.01.14 18:14, Antoine Pitrou написав(ла): I don't think this is a killer feature that would deserve an extension of the release cycle. The feature freeze period is meant for bug fixing, not to shoehorn the latest bangs and whistles. Normally the whole Derby thing should already have waited for

Re: [python-committers] [RELEASED] Python 3.3.4 release candidate 1

29.01.14 18:55, Andrew Svetlov написав(ла): Would you to accept fixes for http://bugs.python.org/issue20434 and http://bugs.python.org/issue20437 before 3.3.4 final? And http://bugs.python.org/issue20440. ___ python-committers mailing list

Re: [python-committers] Proposing Berker Peksag for push privileges

неділя, 15-чер-2014 20:21:15 R. David Murray написано: I'd like to propose that we give Berker Peksag push privileges. He's provided a number of good quality patches and done good review work on other issues, and has been an active contributor for quite some time. IMO we've reached the point

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

понеділок, 25-тра-2015 17:30:02 Larry Hastings написано: For the record I've granted three exceptions to the beta 1 feature freeze (so far): * Serhiy asked for one very-last-minute for a C reimplementation of lru_cache. He checked it in about a half-hour before feature freeze and

Re: [python-committers] [Python-Dev] Make stacklevel=2 by default in warnings.warn()

субота, 19-вер-2015 23:55:44 Nathaniel Smith написано: > OTOH I guess if there is anyone out there who's intentionally using > stacklevel=1 they might be reasonably surprised at this change. That is why I ask on Python-Dev instead of just open an issue. But I doubt that there is such case.

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

понеділок, 04-січ-2016 09:49:57 Eli Bendersky написано: > I suppose you'll want to use https://github.com/python/cpython, which I'm > currently maintaining as a read-only mirror. Let me know when you want to > take control of that repo - I think since it belongs to the "python" Github > org

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

понеділок, 04-січ-2016 21:18:39 Brett Cannon написано: > On Mon, 4 Jan 2016 at 13:14 Donald Stufft wrote: > > On Jan 4, 2016, at 4:11 PM, Brett Cannon wrote: > > It’s pretty easy to migrate the entire history (at least what’s in Hg) > > including all branches

Re: [python-committers] Deprecation Policy PEP

On 29.01.16 19:11, Ezio Melotti wrote: Deprecation Warnings Python offers two kinds of deprecation warnings: * ``PendingDeprecationWarning`` * ``DeprecationWarning`` Initially, only ``PendingDeprecationWarning``\ s were silenced by default. Starting from Python 2.7,

Re: [python-committers] Deprecation Policy PEP

On 29.01.16 21:56, Ezio Melotti wrote: On Fri, Jan 29, 2016 at 8:00 PM, Serhiy Storchaka <storch...@gmail.com> wrote: What about adding deprecations in bugfix releases? If current behavior is obviously incorrect and should be fixed in development branch, but this can break existin

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

On 05.03.16 10:18, Ned Deily wrote: In article <20160305043104.60898b14...@webabinitio.net>, "R. David Murray" wrote: I the past few years I've monitored the bug tracker fairly closely, and watched for good prospects, and recommended or inspired the recommendation of

Re: [python-committers] Davin Potts as a new committer

On 05.03.16 09:21, Berker Peksağ wrote: On Sat, Mar 5, 2016 at 8:44 AM, Gregory P. Smith wrote: On Fri, Mar 4, 2016 at 10:07 PM Raymond Hettinger wrote: On Mar 4, 2016, at 4:07 PM, Brett Cannon wrote: I guess I'm just worried

Re: [python-committers] Guidance on merging(?)

2016-05-08 16:18 GMT+03:00 Steven D'Aprano : > My hg skills are still fairly basic, and I'm looking for somebody who > can mentor me (or at least point me in the right direction) with respect > to making the same change across multiple versions of Python. > > I have just made

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

On 24.05.16 13:16, Victor Stinner wrote: > 2016-05-24 6:22 GMT+02:00 Ned Deily : >> Is it time to discuss your shortlist? > > It would be nice to have a script parsing commit messages to find all > "patch written by ..." and compute statistics on this. I use one-liners like the

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

On 24.05.16 16:42, R. David Murray wrote: My current shortlist is eryksun and paul.j3. I've finally got time to monitor the bugs a bit more now, so I hope I'll notice some others in a while. Ah, argparse is out of my active interests, that is why paul.j3 is not well known by me. This module

Re: [python-committers] PVS-Studio licences

неділя, 14 серпня 2016 р. 13:28:10 EEST Stefan Krah написано: > I've notified viva64.com, and they were nice enough to do a second analysis, > this time done with the Linux version of PVS-Studio: > > http://www.viva64.com/en/b/0418/ > > > They found another issue. :) What is this issue? I see

Re: [python-committers] Proposed new core developer -- Mariatta Wijaya

2017-01-26 10:04 GMT+02:00 Raymond Hettinger : > Mariatta Wijaya has been working hard to become a Python core developer. At > this point she has worked with several of us and I think she has had two > dozen or more accepted patches. > > She is still green but is

[python-committers] The new github PR messages

неділя, 12 лютого 2017 р. 11:46:08 EET Paul Moore написано: > ... and just a further note that I'm finding the new github PR > messages much easier to follow than the old python-checkins traffic. > That's probably nothing more than personal familiarity with github, > but nevertheless, even after

Re: [python-committers] New Roundup notifications on Git commits?

2017-02-16 11:42 GMT+02:00 Victor Stinner : > What and where is the meta-tracker? Is it > http://github.com/python/core-workflow/? http://psf.upfronthosting.co.za/roundup/meta/ I suppose. ___ python-committers mailing list

Re: [python-committers] [RELEASE] Python 3.6.0b1 is now available

On 13.09.16 02:35, Ned Deily wrote: On behalf of the Python development community and the Python 3.6 release team, I'm happy to announce the availability of Python 3.6.0b1. 3.6.0b1 is the first of four planned beta releases of Python 3.6, the next major release of Python, and marks the end of

Re: [python-committers] [RELEASE] Python 3.6.0b1 is now available

On 14.09.16 17:36, Guido van Rossum wrote: Fortunately that page isn't linked from anywhere on the home page AFAIK. If it is, could someone file an issue in the pydotorg tracker? The url is at the bottom of every page. This is on of the first results (actually the first besides manually

Re: [python-committers] autoconf 2.70

abd928 - author Serhiy Storchaka > > If it is not too difficult to build autoconf 2.69 from source, then the > solution could be that they switch to autoconf 2.69. I don't know how this was happen. For now autoconf 2.69 is installed on all my computers. __

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

2016-11-18 18:16 GMT+02:00 Victor Stinner : > Berker, Serhiy: Do you prefer that I mentor Xiang first during one > month, then give him the commit bit, but continue to mentor him? Or > are you ok to give him the commit bit right now, and as I wrote, > request him to ask

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

On 07.12.16 09:26, Ned Deily wrote: Code for 3.6.0 is now frozen. Assuming no release critical problems are found prior to the 3.6.0 final release date, currently 2016-12-16, the 3.6.0 final release will be the same code base as this 3.6.0rc1. Maintenance releases for the 3.6 series will follow

[python-committers] Broken Travis blocks merging

For now all Travis CI builds failed. This blocks merging new PRs, backports and old PRs that need resolving Misc/NEWS conflicts. For details see https://github.com/python/core-workflow/issues/54 . ___ python-committers mailing list

Re: [python-committers] Regarding reviewing test cases written for tabnanny module

On 14.04.17 17:02, Nick Coghlan wrote: On 12 April 2017 at 01:57, Guido van Rossum wrote: On Tue, Apr 11, 2017 at 7:42 AM, Nick Coghlan wrote: Since we do the squash & merge to get an atomic commit at the end, it doesn't make sense to do any force

Re: [python-committers] Please edit the commit message when merge a PR

11.07.17 19:39, Brett Cannon пише: There's isn't a way to block a merge at that stage. But one thing I've been thinking about is adding a check to Bedevere post-merge that sees if the commit message was left unchanged (not quite sure if I can come up with a reliable heuristic, though). In

Re: [python-committers] My (positive) feedback on the new CPython workflow

18.07.17 13:24, Victor Stinner пише: == More contributors, more contributions, faster reviewed/merged == In term of contributions, I looked at statistics yesterday and it became clear the number of different authors is significantely much higher, around 25 contributors / month before, now

Re: [python-committers] My (positive) feedback on the new CPython workflow

18.07.17 14:40, Antoine Pitrou пише: Assuming you meant Martin von Löwis, I think Martin stopped contributing long before we migrated to git (unfortunately, I might add). I hope he's doing ok. I meant Martin Panter. His was the third of most active committers recent two years, but didn't

[python-committers] Please edit the commit message when merge a PR

When a PR is consistent on several commits, the final commit message composed by GitHub contains messages of all these commits: "fix typo", "address yyy comments", "revert zzz". If the initial commit message contained errors (e.g. absent issue number), it is easy to edit the title and text of

Re: [python-committers] Travis-CI compiles twice

23.07.17 19:04, Brett Cannon пише: If you look at the exact commands it's configure, make, and then make regen-all clinic. My guess is that last command is touching files in such a way that the make bulidbottest is causing make to rebuild some files. `make regen-all` touches header files

Re: [python-committers] Proposed release schedule for Python 3.5.4

2017-06-22 5:58 GMT+03:00 Larry Hastings : > There have only been two (2) checkins into the 3.4 branch since 3.4.6 was > released back in January: > > f37b0cb230069481609b0bb06891b5dd26320504 > bpo-25008: Deprecate smtpd and point to aiosmtpd > >

Re: [python-committers] New workflow change: Welcome to blurb

2017-06-24 6:24 GMT+03:00 Larry Hastings : > One minor but ongoing problem we've had in CPython core development has been > the mess of updating Misc/NEWS. Day-to-day developers may have a conflict > if they lose a push race, which means a little editing. You'll have a >

Re: [python-committers] What is a CPython core developer?

22.09.17 20:26, Brett Cannon пише: +1 for the list Victor and Antoine have here! +1 from me too! ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct:

Re: [python-committers] Merging when assignee does not respond.

пʼятниця, 22 вересня 2017 р. 14:43:40 EEST Terry Reedy написано: > https://bugs.python.org/issue30085 > https://github.com/python/cpython/pull/1171 > were submitted last April. > > Raymond assigned PR to himself, reviewed it in May. > > Contributor Sanket revised according to reviews, in my

Re: [python-committers] Should I merge a PR that I approved if it was written by a different core developer?

середа, 20 вересня 2017 р. 23:27:49 EEST Victor Stinner написано: > My question is: is someone opposed that a core developer clicks on the > [Merge] button for a PR proposed by a different core developer? I'm opposed. The author can be more acquainted with the writing code than reviewers. The

Re: [python-committers] Proposing Mark Shannon to be a core developer

14.05.18 23:41, Larry Hastings пише: Dr. Mark Shannon contributed the "key sharing dictionary" to Python, writing both the PEP and the implementation.  This shipped in Python 3.3 and was listed as one of the top features of that release as according to the "What's New?" document. We've

Re: [python-committers] A different way to focus discussions

19.05.18 01:25, Guido van Rossum пише: I wonder if it would make sense to require that for each PEP a new GitHub *repo* be created whose contents would just be a draft PEP and whose issue tracker and PR manager would be used to debate the PEP and propose specific changes. This way the

Re: [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!

15.05.18 14:51, Ned Deily пише: This is it! We are down to THE FINAL WEEK for 3.7.0! Please get your feature fixes, bug fixes, and documentation updates in before 2018-05-21 ~23:59 Anywhere on Earth (UTC-12:00). That's about 7 days from now. We will then tag and produce the 3.7.0 release

Re: [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!

15.05.18 14:51, Ned Deily пише: This is it! We are down to THE FINAL WEEK for 3.7.0! Please get your feature fixes, bug fixes, and documentation updates in before 2018-05-21 ~23:59 Anywhere on Earth (UTC-12:00). That's about 7 days from now. We will then tag and produce the 3.7.0 release

Re: [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!

24.05.18 19:02, Ned Deily пише: On May 24, 2018, at 11:35, Serhiy Storchaka <storch...@gmail.com> wrote: I have doubts about two issues. I feel the responsibility for them because I had the opportunity to solve them before, but I lost it. [...] Serhiy, what are the bugs.python.org

Re: [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!

24.05.18 10:23, Ned Deily пише: So this *is* really your last chance: if you know of any true releasing blocking issues for 3.7.0, you have about 12 more hours to log it in the bug tracker as a "release blocker". I'll send out an email once we start the release manufacturing. Any merges to the

Re: [python-committers] [Python-Dev] FINAL WEEK FOR 3.7.0 CHANGES!

17.05.18 21:43, Elvis Pranskevichus пише: I'm working on the What's New document. Will start putting PRs in the next few days. Great! ___ python-committers mailing list python-committers@python.org

Re: [python-committers] Missing In Action

16.06.18 03:03, Victor Stinner пише: Oh. After I sent my email, I checked the translation of "Missing In Action". It means more or less "lost", but it seems to be commonly associated to war: Good illustration of the loss in translation. :-) ___

Re: [python-committers] Missing In Action

16.06.18 02:59, Victor Stinner пише: The problem is that there are 3 lists and each has different numbers of core developers: 90 according to GitHub, 170 according to bugs.python.org. * https://github.com/orgs/python/teams/python-core/members *

Re: [python-committers] Vote to promote Pablo Salingo Salgado as core developer

13.06.18 19:43, Terry Reedy пише: On 6/13/2018 12:16 PM, Victor Stinner wrote: I propose to promote Pablo Salingo Salgado as a core developer and so open a vote during one week. If there is no strong opposition, I will promote him but also continue to mentor him for a least one month. Pablo is

Re: [python-committers] Vote to promote Pablo Salingo Salgado as core developer

13.06.18 23:46, Victor Stinner пише: It's not like Pablo proposed the idea himself and force to get this feature merged. Pablo just implemented an idea proposed by two other core developers. It looks like Pablo implements ideas for which he does not fully understand the consequences and the

Re: [python-committers] Poll: Do you like the PEP 572 Assignment Expressions?

02.05.18 12:49, Victor Stinner пише: The poll is on the *current* PEP. I propose 4 choices: * +1: you like the PEP * -1: you dislike the PEP * 0: you are not sure if you like it or not, or you have no opinon * don't reply to this poll :-) Just reply to this email with "+1", "0", "-1". Please

Re: [python-committers] Poll: Do you like the PEP 572 Assignment Expressions?

02.05.18 23:27, Serhiy Storchaka пише: I will not use it if it's accepted, and likely will not make reviews of patches that use it. I meant that this feature looks so bad to me, that it will be painful to me even to read a Python code that uses

Re: [python-committers] Time for 3.4.9 and 3.5.6

08.07.18 13:02, Larry Hastings пише: On 07/08/2018 01:31 AM, Serhiy Storchaka wrote: I suggest to merge a 3.5 specific documentation fix for CALL_FUNCTION_VAR and CALL_FUNCTION_VAR_KW opcodes. There were undocumented changes in 3.5, and third-party projects which implement interpreting

Re: [python-committers] Time for 3.4.9 and 3.5.6

08.07.18 10:45, Larry Hastings пише: My six-month cadence means it's time for the next releases of 3.4 and 3.5.  There haven't been many changes since the last releases--two, to be exact.  These two security fixes were backported to both 3.4 and 3.5: * bpo-32981: Fix catastrophic

[python-committers] Orphaned backports

miss-islington is an awesome bot! It makes fixing bugs in multiple versions much simpler. You need just accept automatically created backporting PRs. But there is a downside. miss-islington makes the life so easier, that sometimes you forgot about not finished backports. miss-islington can

Re: [python-committers] Orphaned backports

22.04.18 21:27, Terry Reedy пише: Replacing 'closed' with 'merged' excludes rejected PRs. Thank you, this gives cleaner result. The 2.7 backport of https://github.com/python/cpython/pull/3639 is yours. I thought you taken it. ___

Re: [python-committers] Orphaned backports

23.04.18 19:47, Brett Cannon пише: On Sun, 22 Apr 2018 at 11:27 Terry Reedy > wrote: Does github allow repository owners to send email directly to people who have submitted PRs or at least, people with commit privileges (in this

Re: [python-committers] python-committers is dead, long live discuss.python.org

29.09.18 03:45, Łukasz Langa пише: On 28 Sep 2018, at 23:04, Serhiy Storchaka wrote: Do you use NNTP? Like with IRC, you won't find the next generation of core developers on it. And no, there is no support for it in Discourse. Yes, I do. I read all Python-related mailing list via the Gmane

Re: [python-committers] python-committers is dead, long live discuss.python.org

29.09.18 00:45, Łukasz Langa пише: Hello committers, since this got pretty long, here's the tl;dr: - we're at the point where it is hard to make mailing lists work for us; - we're switching to Discourse; it's better in many ways; - go to https://discuss.python.org/ and create your account

Re: [python-committers] Python 4.0 or Python 3.10?

25.09.18 22:40, Barry Warsaw пише: On Sep 25, 2018, at 15:31, Antoine Pitrou wrote: So my preference would be on 3.10. 3.9 + 0.1 :) Renaming it to Python 4 is fraught with knock-on effects, so I think we do reserve that for major changes. I doubt we’ll ever need for a disruptive backward

Re: [python-committers] [Python-Dev] 3.7.2rc1 and 3.6.8rc1 cutoffs ahead, last 3.6.x bugfix release!

19.12.18 16:01, Victor Stinner пише: RHEL 7 is based on Python 2.7.5 which has been released in 2013 (5 years ago) and there are 150 patches on top of it: it means that around 30 patches are added per year. Unlikely the patch rate was constant. I suppose that more patches were created at

Re: [python-committers] Promote Stefan Behnel as a core developer

I asked Stefan some questions and here is he answer. 27.03.19 10:25, Stefan Behnel пише: Hi Serhiy! It's actually good that you asked. Please forward this to the committers list for me. Serhiy Storchaka schrieb am 27.03.19 um 07:40: Maybe it's my fault that I did not introduce you well

Re: [python-committers] Promote Stefan Behnel as a core developer

Opened an anonymous vote on https://discuss.python.org/t/vote-to-promote-stefan-behnel-as-a-core-developer/1054 . But if you have concerns or objections, it is better to express them publicly or in private to me. ___ python-committers mailing list

[python-committers] Promote Stefan Behnel as a core developer

I propose to promote Stefan Behnel (aka scoder on the tracker and GitHub) as a core developer. Perhaps not one from us is surprised that he is not yet a core developer. Stefan is a core developer of Cython and lxml, two important projects in Python ecosystem. He is a coauthor of PEP 489. His

Re: [python-committers] Promote Stefan Behnel as a core developer

24.03.19 18:40, Antoine Pitrou пише: I don't know. If he's not very active in writing or reviewing PRs, then perhaps he doesn't _need_ core developer rights. I understand you. He does not _need_ core developer rights just for this. But I have a grounded hope that Stefan can be the next

Re: [python-committers] Promote Stefan Behnel as a core developer

24.03.19 23:23, Victor Stinner пише: Cython became a major project in the Python community (see the PSF award). I noticed that sometimes Cython is slow to be updated to support new Python changes (like the new way to store exceptions in PyThreadState of Python 3.7). It is not slow. But it took

Re: [python-committers] Promote Stefan Behnel as a core developer

24.03.19 20:27, Terry Reedy пише: Have you asked Stefan if he would like the privilege, accept it, and would at least occasionally use it? Actually it is Stefan who asked me to promote him. So he is definitely would like. ___ python-committers