Fantastic, welcome Nikita!
On Sun, Jan 9, 2022 at 3:01 AM Dong-hee Na wrote:
> Hi
>
> I am very happy to share that Nikita Sobolev is now a member of the Python
> Triage team.
> https://github.com/python/core-workflow/issues/422
>
> Nikita contributes various parts of CPython and he is a passion
Congrats Irit, I'm excitied to have you with us!
- Tal
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.o
On Thu, Apr 29, 2021 at 7:58 AM Eric V. Smith wrote:
>
> At first blush it looks like a normal wheel file:
[...]
> Five seconds worth of looking at it doesn't raise any alarms, although
> I'm not going to install or execute anything!
>
> I think it was probably uploaded in error, and should just
On Tue, Nov 10, 2020 at 12:02 AM Brett Cannon wrote:
>
Welcome aboard Batuhan!
It's been a pleasure working with you so far, and I look forward to
further collaboration with you.
- Tal
___
python-committers mailing list -- python-committers@python.org
On Mon, Oct 12, 2020 at 11:50 AM Victor Stinner wrote:
>
> Closing automatically an issue is not incompatible with saying thanks
> to people who helped to get it fixed. You can still comment on a
> closed issue, and people who are subscribed to the bug will be
> notified by email.
That's true, bu
On Sun, Oct 11, 2020 at 10:13 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.
>
> This doesn't have to be t
2020-09-05. That’s 7 years of exemplary release
> managing!
>
> Larry, from all of us, and from me personally, thank you so much for your
> invaluable contributions to Python. Enjoy your retirement!
>
> Cheers,
> -Barry (on behalf of the P
important than TAB?
>
> Regards,
>
> On Tue, Nov 19, 2019 at 3:52 AM Tal Einat wrote:
> >
> > On Mon, Nov 18, 2019 at 8:50 PM Eric V. Smith
> wrote:
> >>
> >> Replying to python-committers for visibility, although maybe python-dev
> >> would be
is char before making that change, but
apparently my editor mishandled that search spectacularly.)
- Tal Einat
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://
gt;
> There are plenty of these in the code. Some people (who won't be named,
> but match the regex "Barry") like them. I don't think we should start
> removing them.
>
Oh wow, I completely missed that! :blush:
Terribly sorry, I'll revert the change.
- Tal Eina
"from the inside".
Congrats!
- Tal Einat
On Wed, Sep 25, 2019 at 3:46 AM Brett Cannon wrote:
> While we wait for the last step of the infrastructure team to add Joannah
> to the Python Core team on GitHub, I wanted to welcome to t
I've seen some great work from Paul Ganssle in the past year or so;
definitely well-deserved.
Congrats Paul!
On Thu, Feb 14, 2019 at 6:28 PM Victor Stinner wrote:
> Hi,
>
> Paul Ganssle just asked me to close a bug which he fixed. Instead, I
> just gave him the bug triage permission :-)
>
> Pau
Congrats Alexey!
I've seen some of Alexey's work over the past year and it has been of high
quality and generally showed good judgement. This is well deserved IMO.
On Fri, Feb 1, 2019, 18:04 Victor Stinner Hi,
>
> Alexey Izbyshev is working hard on CPython for 1 year and got a lot of
> non-trivi
I'll try to address some of the points brought up here without trying to
"sell" this too much.
To reiterate: I'm suggesting the "Mentorship Program" only because of an
apparent lack of regular contributors, many devs who would like to be
mentored, and a low availability of core devs for mentoring.
Hi Antoine,
On Fri, Nov 2, 2018 at 3:38 PM Antoine Pitrou wrote:
>
> Le 02/11/2018 à 14:19, Tal Einat a écrit :
> >
> > I would also like to work towards these goals. I have recently invested
> > more time on the core-mentorship mailing list and Zulip stream, as well
*tl;dr:* I’d like to apply for a PSF grant to mentor several developers
towards becoming active contributors and hopefully core-devs.
1. What do you think? Any +1/-1 would be very helpful.
2. I'm looking for info on how successful mentoring has been in getting
more contributors. Any such info or
buildbot appears to
be receiving more attention recently.
- Tal Einat
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/
Raymond Hettinger wrote:
>
> At the developer sprints this week, we collectively decided to grant core
> committer status to Emily and Lisa.
Welcome aboard! Glad to have you with us :)
___
python-committers mailing list
python-committers@python.org
http
ys of contributing to Python; KBK had to be
patient with me until I learned to review my patches once more before
submitting them, and reach a more consistently high quality.
- Tal Einat
___
python-committers mailing list
python-committers@python.org
http
On Sat, Jun 16, 2018 at 1:37 AM, Eric Snow wrote:
> The consequent question is how to get more people resolving open
> tracker issues and giving PR reviews? Off-hand, I'm not sure. :/
> We've discussed this before and it's probably time to discuss it
> again. Any ideas?
In 2012 point Martin Lö
ve a list.
We have at least one list on the developers' guide:
https://devguide.python.org/developers/
It's more of a log of permissions granted and dropped. It also has a
section titled "Permissions Dropped after Loss of Contact", c
x27;m very sure it
is appropriate.
Can the necessary permission bits be flipped?
- Tal Einat
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www
Dormant core dev here. Not contributing at all due to severe lack of
time in the past year and a half, not likely to have more time in the
near future. Also no longer working with Python at all except as a
hobby :(
I could pull off a review once a month if it would actually help!
On Sat, Jan 21,
On Sat, Jun 27, 2015 at 2:29 PM, Nick Coghlan wrote:
> On 27 June 2015 at 15:08, Robert Collins
> wrote:
> > I'm happy to provide on demand reviews. I an take on the backporting
> easily
> > enough.
>
> Thanks, I added you to the PyPI project as a co-owner. The source repo
> for the contextlib2
On Sat, May 23, 2015 at 4:25 PM, Nick Coghlan wrote:
> On 23 May 2015 at 19:29, Tal Einat wrote:
>> On Sat, May 23, 2015 at 1:34 AM, Berker Peksağ
>> wrote:
>>>
>>> * The C implementation should be in Modules/mathmodule.c
>>> * Tests should be in
I remember correctly, we don't need the Python implementation and its
> tests
I'll happily review the patch once it's on the bug tracker as Berker described.
- Tal Einat
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
On Sat, Jan 25, 2014 at 3:09 PM, Larry Hastings wrote:
> To be honest I have absolutely no idea what % of files have been converted
> so far. Figuring it out would use time that would be better spent catching
> up on my to-do list.
Of the 22 Derby issues:
* 2 have been closed: 20133 (audioop) an
27 matches
Mail list logo
