On Thu, May 27, 2021 at 9:50 PM Guido van Rossum wrote:
>
> Did you check your junk or spam mail folders? The email address from which
> bpo is sending email is not super trusted by the spam filters used by large
> email providers like GMail and Outlook.
Unfortunately, this is not just the case
On Thu, May 27, 2021 at 8:46 PM Irit Katriel via python-committers
wrote:
>
>
> I'm not getting anything at all from bpo for about a week now. Maybe it had
> enough of me.
That has nothing to do with the BPO issue we have been talking about.
The infra team is the best place to report email deliv
On Sun, Oct 11, 2020 at 10:14 PM Gregory P. Smith wrote:
>
> We've got the automerge tag on GH, it+bot make it awesome. There's one more
> thing I'd like to see that could help with bug hygiene: A tag to close the
> associated bug as "fixed" after the merge happens.
You can already do that by a
On Mon, Aug 17, 2020 at 10:59 AM Victor Stinner wrote:
>
> FYI this MSDN subscription allowed me to debug tons of Windows
> specific issues and to enhance Windows support. It's really very
> helpful, at least to me :-) Thanks Microsoft!
Same here! I was able to fix many issues and implement some
On Wed, Jul 22, 2020 at 10:31 PM Python Steering Council
wrote:
>
> The following message was sent to a core developer. This message was
> thoughtfully and respectfully sent by the Steering Council as a serious
> reminder that the privilege to serve as a core developer comes with the
> responsi
On Sun, May 19, 2019 at 2:41 PM Stefan Behnel wrote:
>
> Paul Moore schrieb am 15.05.19 um 17:18:
>
> > multiple fragmented forums for discussion. It
> > feels a lot harder these days to keep track of all the
> > discussions/decisions going on.
>
> +1
True, two years ago I was able to follow ever
On Fri, Apr 26, 2019 at 9:50 PM Barry Warsaw wrote:
> It would be very helpful if you could add these comments to the PR.
Sure, I just left a comment there.
> And as a fan of Roundup and its critical importance to the Python development
> process, I want to personally thank you for all your —an
On Fri, Apr 26, 2019 at 11:37 PM Brett Cannon wrote:
> Because that repo is private I will say that the last comment on that issue
> was exactly a month ago from someone at GitHub saying that they are looking
> into this feature request.
Thank you, I forgot those links are private. I'll also no
On Fri, Apr 26, 2019 at 5:55 PM Guido van Rossum wrote:
> - **Issue tracker:** We've discussed PEP 581, "Using GitHub Issues for
> CPython" by Mariatta Wijaya. We're in favor of this move, and feel
> that the transition should be professionally planned and executed.
> In collaboration with
On Sun, Apr 7, 2019 at 6:19 PM Antoine Pitrou wrote:
> Perhaps some Chinese people have reasons to be
> afraid when they see those good-willed initiatives done in the name of
> basic human rights.
I'm very familiar with the "they keep talking about democracy and
human rights so let's stick to our
On Sun, Apr 7, 2019 at 3:19 PM Xiang Zhang wrote:
> https://discuss.python.org/t/can-we-do-something-for-996-programmers-in-china/1119/11
Hi Xiang,
Perhaps I'm missing some context here, but Guido's first post in the
thread you've linked isn't about politics (nor a discussion about
comparing ide
On Wed, Oct 3, 2018 at 1:06 PM Chris Jerdonek wrote:
> Hi Łukasz, I tried signing up three days ago, but it doesn't look like I've
> been approved yet (e.g. I'm not listed in the members list). I notice some
> other people have been approved during this time based on the group count. I
> tried
On Sat, Sep 29, 2018 at 1:03 AM Victor Stinner wrote:
> Oh, I just saw that Berker sent a message:
> "Membership Request for @committers"
> https://discuss.python.org/t/membership-request-for-committers/27/2
>
> I don't see this message in any category. Is it a private message?
If I understood it
On Sun, Aug 12, 2018 at 4:22 PM, Eric V. Smith wrote:
> https://github.com/python/cpython/pull/8745
>
> This failed (I think travis, but can't tell now). I thought I could close it
> and re-open it to get it to retry, but apparently not. When I closed it, the
> backport branch was deleted. At this
On Thu, Jul 12, 2018 at 8:41 PM, Eric Snow wrote:
> Thank you for putting so much time, effort, and care into both the
> language and its community! We cannot thank you enough.
+1
> In the short term we could appoint a *temporary* triumvirate to fill
> in as BDFL (with the intent to re-assess t
On Thu, Jun 14, 2018 at 11:46 AM, Victor Stinner wrote:
> 2018-06-14 0:26 GMT+02:00 Berker Peksağ :
>> I don't care about total number of commits to be honest. It's not so
>> hard to get 50 PRs merged into master in a month or so.
>
> Wait, what? No developer got m
On Wed, Jun 13, 2018 at 10:38 PM, Serhiy Storchaka wrote:
> I think Pablo will be good core developer and agree with the description
> given by Victor. But it seems that he still needs to learn something about
> what changes are good for Python.
I agree with Serhiy. Count me -1 for now.
I don't
On Sun, Jun 3, 2018 at 11:27 AM, Antoine Pitrou wrote:
> That said, it is true that core development activity continues to
> shrink, at least according to this particular metric:
> https://github.com/python/cpython/graphs/contributors
I think the pre-GitHub stats includes merge commits too:
On Wed, May 2, 2018 at 12:49 PM, Victor Stinner wrote:
> Hi,
>
> I would like to start a poll on Chris Angelico's PEP 572 "Assignment
> Expressions", restricted to Python core developers, to prepare the
> talk at the Language Summit:
>
>https://www.python.org/dev/peps/pep-0572/
>
> The poll is
On Thu, Dec 7, 2017 at 2:17 AM, Victor Stinner wrote:
> Hi,
>
> I wrote a quick & dirty parser to compute statistics on *new* CPython
> core developer per year using the following page as data:
> https://devguide.python.org/developers/
>
> 2007: 15
> 2008: 19
> 2009: 11
> 2010: 20
> 2011: 12
> 201
On Thu, Dec 7, 2017 at 1:06 AM, Victor Stinner wrote:
> A contributor without the triage priviledge cannot triage bugs...
I don't see this as a big problem. There are many ways to do issue
triaging (you need to follow python-checkins, know how to use tools
like 'git blame' etc.) so I don't think
On Thu, Sep 21, 2017 at 12:27 AM, Victor Stinner
wrote:
> Hi,
>
> Before the GitHub era, in the old "Mercurial era", the unwritten rule
> was to not merge a patch written by a developer who has the commit
> bit, to not "steal" his/her work. The old workflow (patches attached
> to the bug tracker)
On Sat, Sep 2, 2017 at 3:37 AM, Senthil Kumaran wrote:
> If you are going to use for CPython development, then reach out to Vinay
> Sajip.
I have four available licences for CPython development too.
--Berker
___
python-committers mailing list
python-co
On Mon, Jul 10, 2017 at 4:14 PM, Serhiy Storchaka wrote:
> 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. ab
On Fri, Jun 2, 2017 at 12:23 PM, Victor Stinner
wrote:
> *Many* people ask me regulary "how to find easy Python issues", and
> the last 3 years, I always failed to find such issues... Many "easy
> issues" are older than 3 years old, have more than 20 comments and no
> compromise has been found how
On Sat, Apr 1, 2017 at 12:40 AM, Brett Cannon wrote:
> In the (long) discussion of
> https://github.com/python/core-workflow/issues/6, Wes Turner began to do his
> usual posting of lists. People pointed out he was stepping out of line by
> being somewhat off-topic and seemingly lecturing folks. He
On Mon, Mar 13, 2017 at 12:11 AM, Brett Cannon wrote:
>
>
> On Sun, 12 Mar 2017 at 06:33 M.-A. Lemburg wrote:
>>
>> On 10.03.2017 23:13, Brett Cannon wrote:
>> > Fifth, anything I missed? :)
>>
>> My main nit after the move is that messages to the checkin list
>> no longer include the full patch.
On Mon, Feb 27, 2017 at 4:45 PM, Victor Stinner
wrote:
> Hi,
>
> My PR was merged, but I don't see any notification on bpo:
> https://github.com/python/cpython/pull/253
> http://bugs.python.org/issue27840
>
> A few weeks ago, we got two notifications per commit (hg, git), and
> now there is zero n
On Mon, Feb 13, 2017 at 6:25 PM, Victor Stinner
wrote:
> 2017-02-13 16:04 GMT+01:00 Donald Stufft :
>> I’ve also never see the random -0.01%
>> coverage of code in another project, and my guess is that there is some sort
>> of non-determinism in the CPython test suite that would be a good idea to
On Sun, Feb 12, 2017 at 3:25 PM, Serhiy Storchaka
wrote:
> неділя, 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 pers
On Thu, Jan 26, 2017 at 4:49 PM, Nick Coghlan wrote:
> That would be pretty similar to the way things worked when I
> recommended Yury for commit privileges - at the start, the only thing
> that changed was that the final step in the review process changed
> from "wait until I find time to commit
On Thu, Jan 26, 2017 at 11:04 AM, Raymond Hettinger
wrote:
> Hello all,
>
> 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 pers
On Tue, Nov 15, 2016 at 11:17 AM, Victor Stinner
wrote:
> Hi,
>
> 2016-11-15 1:10 GMT+01:00 Berker Peksağ :
>> Xiang tends to fix things that are not broken,
>
> This sentence sounds strange. What do you mean? :-)
>
>> (...) and when you point out that the thing th
On Mon, Nov 14, 2016 at 3:09 PM, Victor Stinner
wrote:
> Hi,
>
> Last months, I noticed that Xiang Zhang is very active on the bug
> tracker and propose many enhancements and bug fixes. He contributes to
> Python code, but also to the C code (a rare skill nowadays). Slowly,
> he understood how to
On Sun, Sep 25, 2016 at 8:52 PM, Raymond Hettinger
wrote:
>
>> On Sep 25, 2016, at 8:38 AM, Yury Selivanov wrote:
>>
>> I want to propose to give commit privileges to INADA Naoki. He's the guy
>> behind compact dict implementation for CPython 3.6, which was a super
>> complex patch.
>
> I woul
On Mon, Aug 8, 2016 at 9:45 AM, Steven D'Aprano wrote:
> I tried make distclean and building again, and I get:
>
>
> Could not find platform dependent libraries
> Consider setting $PYTHONHOME to [:]
> Could not find platform dependent libraries
> Consider setting $PYTHONHOME to [:]
> /home/steve
On Mon, Jun 6, 2016 at 10:00 PM, R. David Murray wrote:
> We've talked about having a 'triage capable' symbol to go with our
> core dev and contributer agreement symbols, but no one has implemented
> it yet.
I'm a complete Roundup newbie but I have attached a patch at
http://psf.upfronthosting.co
On Mon, Jun 6, 2016 at 7:41 PM, Ethan Furman wrote:
> Question: I noticed a couple issues on b.p.o that were being closed by
> contributors (not core-devs, not their own issues).
>
> Should non-core-devs be closing issues that do not belong to them?
Yes, but they should provide enough informatio
On Sun, May 8, 2016 at 4:18 PM, Steven D'Aprano wrote:
> Hi,
>
> 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 a o
On Thu, Mar 3, 2016 at 10:58 PM, Zachary Ware
wrote:
> We actually have four separate copies of libffi:
>
> Modules/_ctypes/libffi: This is a mostly-vanilla copy of libffi-3.1
> (released 19May2014), lightly patched according to
> Modules/_ctypes/libffi.diff. This one is used for any non-OSX posi
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 about the health of this project. I'm doing
>> > what I can through the migration t
On Tue, Jul 21, 2015 at 6:28 PM, Serhiy Storchaka wrote:
> On 21.07.15 17:06, R. David Murray wrote:
>>
>> 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 w
On Sat, May 23, 2015 at 12:53 AM, Chris Barker wrote:
> On Fri, May 22, 2015 at 2:33 PM, Larry Hastings wrote:
>>
>> On 05/22/2015 02:29 PM, Chris Barker wrote:
>>
>> Is it too late to get the isclose() code (PEP 485) into 3.5?
>
> ...
>>
>> Hopefully you can find a core dev familiar enough wit
On Tue, May 12, 2015 at 8:04 PM, Larry Hastings wrote:
> 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
Workflow 1: +1
Workflow 2: +0
--Berker
___
pytho
On Sat, Mar 14, 2015 at 10:23 PM, Brett Cannon wrote:
> Paul has been participating on python-dev for quite a while, he is a
> committer on pip, and (co-)author on 5 PEPs. At this point I think it would
> be prudent for Paul to have commit privileges if for any other reason than
> to help manage t
On Sat, Jan 10, 2015 at 12:33 PM, M.-A. Lemburg wrote:
> Hi Ezio,
>
> I think I'm not making myself clear enough :-)
>
> Technically, operations would stay the same (tickets, patches, reviews),
> but from a motivational point of view, you change things a lot for the
> better if you put trust into
46 matches
Mail list logo
