On Wed, Jan 5, 2022 at 7:04 AM Petr Viktorin wrote:
> IMO, there should be a PEP for wide-reaching changes like bpo-40521, and
> the PEP should be actually *approved* before such changes are made.
FWIW, I plan on posting a PEP by the end of the week regarding
per-interpreter GIL and the related w
On Wed, Apr 15, 2020 at 6:38 PM Eric V. Smith wrote:
> Here are the slides from my talk:
> https://github.com/ericvsmith/f-strings-by-default/raw/master/F-strings%20everywhere!.pdf
Here are slides for my lightning talk ("A Retrospective on My
“Multi-core Python” Project"):
https://docs.google.c
I have a growing concern I have about the impact of our current
promotion process on aspiring core developers. I've opened a
discussion thread about:
https://discuss.python.org/t/concerns-about-how-we-vote-on-new-core-developers/2351
-eric
___
python-c
On Mon, Jun 3, 2019 at 12:05 PM Pablo Galindo Salgado
wrote:
> After we have received all responses, Ewa will reach out to you individually
> with additional information for booking rooms and getting travel reimbursed
> if you requested it.
What nights are accommodated for the hotel room? I'd
On Fri, Nov 2, 2018, 21:44 Victor Stinner Le sam. 3 nov. 2018 à 04:40, Eric Snow a
> écrit :
> > Would it help if we only published who voted, and kept their votes
> private? Publishing the actual votes probably doesn't make a big
> difference here, relative to the broader P
On Fri, Nov 2, 2018, 21:24 Tim Peters Nevertheless, I probably won't vote - I object to public ballots on
> principle. That's been raised by others, so I won't repeat the
> arguments, and I appear to be very much in a minority here.
>
Would it help if we only published who voted, and kept their
On Sat, Sep 29, 2018, 09:31 Yury Selivanov wrote:
> Given all the above, Łukasz *volunteered* his own time to help setup
> Discourse and help everyone to migrate to it so that we can all try
> it.
Yes. Thank-you Łukasz! :)
When he announced that we want to try Discourse at the sprints,
> out
On Tue, Sep 25, 2018 at 1:30 PM Yury Selivanov wrote:
> What's the current plan for what version of Python we release after 3.9?
One idea I've heard is to switch to calendar versioning after 3.9. So
we'd start with something like "2021" (year) or "2021.06" (year +
month). sys.version_info would
iously
> attended two Language Summits and three core development sprints at PyCon.
> Since July, Emily has worked with Guido's guidance to implement PEP 572,
> Assignment Expressions. She has also worked with Eric Snow to dive into
> CPython's runtime as well as subinterpreters.
On Wed, Aug 1, 2018 at 3:44 PM M.-A. Lemburg wrote:
> On 01.08.2018 23:28, Mariatta Wijaya wrote:
> > See also an open issue to revamp the Developer log:
> > https://github.com/python/devguide/issues/390
> >
> > Someone has also said that they're working on tracking down the dormant
> > core devs,
On Wed, Jul 18, 2018 at 10:44 AM Steve Dower wrote:
> Your contributions to this part of the discussion are also very useful -
> we need to know what concerns people have, and often those concerns may
> not have occurred to those of us who approach it with a more idealistic
> idea of how everythin
On Wed, Jul 18, 2018 at 10:36 AM Łukasz Langa wrote:
> A simple majority vote is wildly insufficient for this case. Python is a
> large project with many contributors and alienating maybe tens of them is not
> acceptable, especially if we are talking about a "for life" choice.
+1
-eric
___
On Wed, Jul 18, 2018 at 2:43 AM Antoine Pitrou wrote:
> Le 18/07/2018 à 04:02, Barry Warsaw a écrit :
> > A singular BDFL provides clear leadership. With a council of elders, it
> > will be more difficult to communicate both to the Python community, and to
> > the larger, more peripheral user b
On Tue, Jul 17, 2018 at 8:15 PM Eric V. Smith wrote:
> On 7/17/2018 10:02 PM, Barry Warsaw wrote:
> > I’d like to propose an alternative model, and with it a succession plan,
> > that IMHO hasn’t gotten enough discussion. It’s fairly radical in that it
> > proposes to not actually change that m
On Thu, Jul 12, 2018 at 1:29 PM Brett Cannon wrote:
> On Thu, 12 Jul 2018 at 10:42 Eric Snow wrote:
>> In the short term we could appoint a *temporary* triumvirate to fill
>> in as BDFL (with the intent to re-assess the situation in September if
>> we haven't resolved
On Thu, Jul 12, 2018 at 11:55 AM Brett Cannon wrote:
> One other idea if we go the BDFL or triumvirate route is we could ask Guido
> to choose (if he's willing). I think Guido's key point is he wants us to
> choose how we want to keep this team going, but that may not preclude us to
> essential
On Thu, Jul 12, 2018 at 10:55 AM Yury Selivanov wrote:
>
> Thank you, Guido. This is a sad day for me personally; I really hoped
> you'd lead Python for a few more years. On the other hand, Python is
> in good hands, you've built a large enough and diverse community
> around it!
+1
Thank you f
On Thu, Jun 14, 2018 at 8:06 PM Nathaniel Smith wrote:
> On Thu, Jun 14, 2018 at 4:40 AM, Berker Peksağ
> wrote:
> > This isn't about my or someone else's high standards. We keep saying
> > we need more triagers and reviewers, and we keep promoting people who
> > didn't do any issue triaging and
On Wed, Jun 13, 2018 at 10:16 AM 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.
>
> [snip]
>
> I am mentoring
+1
-eric
On Mon, May 14, 2018 at 4:41 PM, Larry Hastings wrote:
>
>
> 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
>
On Wed, May 2, 2018 at 3:49 AM, Victor Stinner wrote:
> I propose a poll because I'm unable to track the opinion of each core
> dev, too many emails have been sent to python-dev, and maybe some
> people changed their mind during the long discussion (which started in
> February) :-)
Victor said "P
On Wed, May 2, 2018 at 3:49 AM, Victor Stinner wrote:
> I propose a poll because I'm unable to track the opinion of each core
> dev, too many emails have been sent to python-dev, and maybe some
> people changed their mind during the long discussion (which started in
> February) :-)
FWIW, contrary
On Wed, May 2, 2018 at 3:49 AM, Victor Stinner wrote:
> 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 w
Welcome, Petr!
-eric
On Mon, Apr 23, 2018, 08:39 Nick Coghlan wrote:
> Hi folks,
>
> With my recent proposal to accept Petr Viktorin as a specialist core
> developer focusing on extension module imports receiving several +1's
> and no concerns being raised, I'm happy to report that Brett has no
+1
-eric
On Fri, Apr 13, 2018 at 4:56 PM, Raymond Hettinger
wrote:
>
>
>> On Apr 13, 2018, at 5:13 AM, Nick Coghlan wrote:
>>
>> I'd like to propose Petr Viktorin as a specialist core developer,
>> focusing on extension module imports.
>
> +1 This is an area that could use more attention from s
On Mon, Jan 29, 2018 at 4:32 PM, Mariatta Wijaya
wrote:
> I suggest we start adding this where it makes sense, to give proper credit
> to PR authors.
+1
Thanks for noticing this. I've bumped into this several times and
look forward to (more clearly) giving credit where credit is due.
-eric
___
On Sat, Jan 27, 2018 at 2:02 PM, Barry Warsaw wrote:
> please welcome your next release manager…
>
> Łukasz Langa!
Congrats, Łukasz! (or condolences? )
-eric
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailm
On Wed, Dec 6, 2017 at 10:43 AM, Victor Stinner
wrote:
> To recognize the good contributions of Cheryl Sabella, I gave her the
> bug triage permission on bugs.python.org. (In practice, Ezio gave her
> the permission.)
>
> In the past, such "promotion" wasn't always advertized on
> python-committer
On Thu, May 25, 2017 at 4:16 AM, Victor Stinner
wrote:
> Welcome Carol!
A giant +1 from me! And a huge thank-you for how much you've already
been doing! You are an excellent example of what makes this community
great.
-eric
___
python-committers mail
+1
On Tue, May 23, 2017 at 11:15 AM, Brett Cannon wrote:
> While at the PyCon US sprints the idea came up of offering Carol Willing
> developer privileges. Everyone at the table -- about 6 of us -- liked the
> idea and Carol also said she would happy to become a core dev, so I'm
> officially putt
On Mon, Feb 13, 2017 at 11:16 AM, Brett Cannon wrote:
> if the webhook event for your merge
> got rejected due to the bad cert then it would have been dropped.
A repo admin should be able to manually request that a failed webhook
be retried. The webhook's page on GH has a list of all associated
On Fri, Feb 10, 2017 at 9:00 AM, Tim Golden wrote:
> Good luck, and thanks to you and the team for all the hard work
A big +1!
-eric
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committ
On Sun, Mar 6, 2016 at 9:54 PM, Brett Cannon wrote:
> I just finished doing what was necessary to make Davin a core dev, so let's
> welcome our first new core dev of 2016!
You've certainly earned this, Davin. Well done and thanks for sticking with it.
-eric
_
On Fri, Mar 4, 2016 at 5:07 PM, Brett Cannon wrote:
> When I thought about this the other week after a
> cranky email to python-dev appeared I realized that the CoC isn't exactly
> advertised so that people know they shouldn't act mean here like they might
> in other corners of the internet where
On Thu, Mar 3, 2016 at 10:39 AM, Brett Cannon wrote:
> But I do think the spirit of Victor's idea is worth considering.
+1
> ...what would we need to do to our C API to make
> it so that anyone following a new API wouldn't be broken if we dropped the
> GIL?
If I recall correctly, this was one k
On Tue, Mar 1, 2016 at 6:01 PM, Larry Hastings wrote:
> It's that time once again: time to start planning for the 2016 Python
> Language Summit! This year the summit will be at the Oregon Convention
> Center in Portland, Oregon, USA, on May 28th.
Thanks for chairing this again!
> Sadly, again
On Jul 29, 2015 11:08 AM, "Robert Collins"
wrote:
>
> On 30 July 2015 at 04:50, Guido van Rossum wrote:
> > The more recent Python 2.7 bugfix releases have
> > specific exemptions from the backwards compatibility requirements for
> > security fixes -- because their lifespan will still be many yea
On Fri, May 24, 2013 at 9:46 PM, Raymond Hettinger
wrote:
> and it recognizes that users don't really need to look across merge
> boundaries.
This is tricky though for any patch that is forward-ported to a
release branch (a la 3.2->3.3). How can you tell from MISC/News in
which release (e.g. 3.3
Welcome!
-eric
On Mar 21, 2013 9:39 PM, "serwy" wrote:
> Hi Everyone,
>
> My name is Roger Serwy and I would like to introduce myself. I am a
> graduate student at the University of Illinois in electrical and computer
> engineering. Python has been a primary language for my research in signal
>
On Mon, Feb 25, 2013 at 12:46 PM, R. David Murray wrote:
> I'll be there the whole time (summit through the end of the sprints).
Same here.
-eric
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/py
40 matches
Mail list logo
