[python-committers] Re: Sad news from Zurich

[Kyle Stanley]

May he rest in peace, I can't even fathom the impact PIL has had on Python
over the years.

On Fri, Dec 10, 2021 at 3:20 PM Guido van Rossum  wrote:

> A former core dev who works at Google just passed the news that Fredrik
> Lundh (also known as Effbot) has died.
>
> Fredrik was an early Python contributor (e.g. Elementtree and the 're'
> module) and his enthusiasm for the language and community were inspiring
> for all who encountered him or his work. He spent countless hours on
> comp.lang.python answering questions from newbies and advanced users alike.
>
> He also co-founded an early Python startup, Secret Labs AB, which among
> other software released an IDE named PythonWorks. Fredrik also created the
> Python Imaging Library (PIL) which is still THE way to interact with images
> in Python, now most often through its Pillow fork. His effbot.org site
> was a valuable resource for generations of Python users, especially its
> Tkinter documentation.
>
> Fredrik's private Facebook page contains the following message from
> November 25 by Ylva Larensson (translated from Swedish):
>
> """
>
> It is with such sorrow and pain that I write this. Fredrik has left us
> suddenly.
>
> """
>
> A core dev wrote: "I felt privileged to be able to study Fredrik's code
> and to read his writing. He was a huge asset to our community in the early
> days. I enjoyed his sense of humor as well. I'm sad that he passed away."
>
> We will miss him.
>
>
>
> --
> --Guido van Rossum (python.org/~guido)
> *Pronouns: he/him **(why is my pronoun here?)*
> 
> ___
> 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.org/
> Message archived at
> https://mail.python.org/archives/list/python-committers@python.org/message/36Q5QBILL3QIFIA3KHNGFBNJQKXKN7SD/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
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.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/YAIZPWDPVWD74ZTA3Z7G25VFQ2URAU2Y/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Alex Waygood is now part of the Python Triage team

[Kyle Stanley]

Welcome Alex!

On Mon, Dec 6, 2021 at 10:40 AM Ken Jin  wrote:

> Hi python-committers,
>
> Alex Waygood (cc-ed) has been given triage permissions:
> https://github.com/python/core-workflow/issues/416. He's great at docs
> and he's branching out to trickier issues. I believe the triage permissions
> will allow him to contribute more to CPython. I'll be helping him with his
> new responsibilities.
>
> Congrats Alex! Welcome to the team.
>
> Regards,
> Ken Jin
>
> ___
> 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.org/
> Message archived at
> https://mail.python.org/archives/list/python-committers@python.org/message/ECDSL4HO7DWIXSDMDKZKKINBRFRZSWCI/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
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.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/K5DOX6SE4GIZITEDH63RFGCF3QVCCBNI/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: PSF hires first Developer-in-Residence (was: Re: Re: Call for resumes: Developer-in-Residence to support CPython)

[Kyle Stanley]

Congrats Łukasz! :)

On Mon, Jul 12, 2021, 11:44 AM Ewa Jodlowska  wrote:

> Hi folks -
>
> Just to circle back, we have officially contracted with Łukasz Langa to be
> the first CPython Developer-in-Residence!
>
> PSF announcement:
> https://pyfound.blogspot.com/2021/07/ukasz-langa-is-inaugural-cpython.html
>
> We look forward to seeing all the impact that Łukasz and this role will
> have!
>
> Best wishes,
>
> Ewa
>
> On Thu, May 13, 2021 at 3:41 PM Ewa Jodlowska  wrote:
>
>> Hi folks -
>>
>> Just a reminder that we are still accepting resumes for the
>> Developer-in-Residence role.
>>
>> The deadline to submit a resume is May 16th.
>>
>> If you would like to chat tomorrow, Saturday or Sunday, let me know. I am
>> happy to share how the employee will work with the PSF and expectations.
>>
>>
>> Ewa Jodlowska
>> Executive Director
>> Python Software Foundation
>> e...@python.org
>>
>>
>> On Mon, Apr 5, 2021 at 4:00 PM Brett Cannon  wrote:
>>
>>>
>>>
>>> On Mon, Apr 5, 2021 at 12:57 PM Ewa Jodlowska  wrote:
>>>



 On Mon, Apr 5, 2021 at 2:36 PM Victor Stinner 
 wrote:

> Hi Ewa,
>
> This is really awesome! It's great that the PSF can now hire someone
> for that!
>
> The job offer is great, but I would like some clarification :-) (While
> I was part of the previous Steering Council who helped to write the
> job offer, sadly I was not avaialble last months when it was
> discussed.)
>
>
> Who is going to "manage" the candidate?
>

 Great question! The technical direction will come from the SC and the
 people management will be Ee and myself.

>
>
> On Mon, Apr 5, 2021 at 7:30 PM Ewa Jodlowska  wrote:
> > The Developer-in-Residence will work full-time for one year to
> assist CPython maintainers and the Steering Council. Areas of
> responsibility will include analytical research to understand the 
> project's
> volunteer hours and funding, investigation of project priorities and their
> tasks going forward, and begin working on those priorities. We are looking
> to hire an existing core developer because of the type of work involved 
> and
> interaction with volunteer core developers and contributors. Need and
> available funding will determine any extension beyond the first year.
> >
> > Create metrics (...) Combine usage and surveyed metrics to determine
> which standard library modules need help and what the maintainer cost is
> for standard library modules
>
> What are the expected steps after the production of such report of the
> stdlib usage and maintenance? Hire more people to maintain most used
> stdlib modules, or deprecate least used modules?
>

> For example, asyncio and ctypes are popular but barely maintained. For
> the CI, the most unstable test is test_asyncio (I asked for help
> multiple times on python-dev). Do we need a more detailed reports on
> the 302 (len(sys.stdlib_module_names)) stdlib modules?
>

 One of the intentions is to document these cases to better prioritize
 funding we have and provide direction to potential future funders.

 I am sure someone from the Steering Council will want to chime in on
 additional, more technical intentions :)

>>>
>>> I think the results of the research is going to help inform what the
>>> next steps are (hence the need for the research ). Guessing what needs
>>> work and making a call without having at least *some* form of data
>>> seems premature. I also have stdlib data already for a language summit
>>> discussion (if it gets selected), and at worst I will just open source the
>>> Jupyter notebook with the charts of what I found so this won't be starting
>>> from scratch.
>>>
>>> Plus I suspect there will be some discussion here of what people want to
>>> see be worked on. While the SC is the final decider on the priorities
>>> simply because it would probably be a bit chaotic if the whole team tried
>>> to direct a single person's work, that doesn't mean things won't be
>>> discussed here to provide guidance and feedback to the SC.
>>>
>>>


>
> I understand that the first step is to put priorities in bug triage
> and PR reviews for the candidate.
>
>
> > Address Pull Request and Issue backlogs based on the developed
> metrics and other metrics created by the Steering Council
>
> What about the candidate skills? I don't expect the candidate to be
> able to fix any bug in any part of the Python. What if is the priority
> is a module that the candidate doesn't know? They should do their
> best, help debugging issues and propose a fix? I expect the existing
> module maintainers to remain the local autority to review pull
> requests written by the candidate, to avoid mistakes.
>

>>> What would *you* do in this situation? The expectation is the 

[python-committers] Farewell, for now :)

[Kyle Stanley]

Hi all,

Last week, I started a new thread on discuss.python.org
 about my
intention to take a further extended break from open source to continue my
mental health healing process. Just wanted to announce it in the other
channels as well since I know that not everyone has the bandwidth to keep
up with more than just the MLs.

In the thread, I discussed my intention to pursue the path of becoming a
Buddhist monk for some time, and recently detailed my adventures at a local
Thai temple. Check it out if you are interested. :)

With Loving Regards,
-- 
--Kyle R. Stanley, Python Core Developer (what is a core dev?
)
*Pronouns: they/them **(why is my pronoun here?*

)
___
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.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/5KN37I5PSMLSBEER3NWWVQCP7DBYPD3Y/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Commits are no longer noted in bro issues

[Kyle Stanley]

Not a solution, but I just wanted to point out the hilarity of the "bro
issues" instead of "bpo issues" typo. I've been having a difficult evening
and seeing the title in my inbox made me chuckle. Might as well stop and
love life's happy little accidents when one has the chance to. :)

On Wed, May 12, 2021 at 10:23 AM Guido van Rossum  wrote:

> Recently it seems that when a PR linked to a bpo issue is merged, no note
> of this event is made in the bpo issue. Look at
> https://bugs.python.org/issue43933 for example. There are notes for the
> first two merged PRs (25717 and 25719), at
> https://bugs.python.org/issue43933#msg392343 and the next message. But I
> cannot find a similar note for the third PR, 26054, which is also merged.
>
> I recall seeing this for other recent issues as well. Did some piece of
> automation recently break? (Could it have to do with the master->main move?)
> --
> --Guido (mobile)
> ___
> 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.org/
> Message archived at
> https://mail.python.org/archives/list/python-committers@python.org/message/M2Z3WSJ4SGGH2GQ7D5NELAZSD3PECG7Q/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
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.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/GDLHBLNRZ3HWSTXVMSUROHSCNHOFUYJM/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: core-dev chat

[Kyle Stanley]

On Sat, May 22, 2021 at 4:54 PM Guido van Rossum  wrote:

> 2. I can handle Discord just fine nowadays but *please* don't combine this
> with the Python Discord server. That server is super active with learners
> and teachers, and has hundreds of channels and it's just really hard to
> ignore that activity if all you're interested in is a single channel. At
> this point I'm sure Kyle will pop in with instructions for how to
> permanently hide all the other channels, but I still say it'd be way easier
> if we had our own small server so nobody would have to hide anything. (And
> "server" is purely a virtual thing IIUC, we don't need hardware or even a
> dedicated VM. If there's a fee I'd be happy to pay for it personally, if
> that's what would stop us considering this option.)
>

I actually 100% agree with using our own smaller server instead of Python
Discord solely for core dev purposes. I think the 2020 sprint demonstrated
well that the traffic on Python Discord can be overwhelming for those who
aren't there for the other channels (as much as I love PyDis). Muting every
channel manually can be quite tedious to completely suppress notifications,
especially when there are as many as PyDis has.

As far as paid options go, there's nitro which IIRC helps to improve voice
quality and adds some other neat features, but shouldn't be strictly needed
for our purposes.

Gitter would work fine as well, I just like that Discord provides easy
voice/video chat in the same location and seems to be where more people are
already at these days (reducing the number of separate open channels one
has to keep track of).


Best Regards,
-- 
--Kyle R. Stanley
*Pronouns: they/them **(why is my pronoun here?*

)
___
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.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/H5TTQEMUJWUZNLN6Q3ZAIBRSJ67E3ECD/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: core-dev chat

[Kyle Stanley]

Thanks, Senthil. This poll format well summarizes the options presented in
the discussion. :)

On Tue, May 18, 2021 at 1:55 PM Senthil Kumaran  wrote:

> Senthil Kumaran wrote:
> > Hello Core Dev,
> > I find a need for a core-dev chat service, wherein I could engage in
> > some quick effervescent conversations.
> ...
> > Does anyone else feel the need? Should we explore any? My thoughts and
> > options are
> ...
>
> > If you think that chatting is not a good idea, and a mailing list, and
> > discourse(discuss.python.org) are the best option, please share your
> > thoughts as well.
>
> This was my original email. Based on the discussion here it looks like
> an informal chat medium will be desirable to many. Some don't see a
> need.
>
> To bring a closure to this topic, I plan to create a poll in
> discuss.python.org to bring get votes on the decision.
>
> So, the first decision will be.
>
> Q: Do we need a core-dev only chat? An informal, private mechanism to
> hang around and chat.
>
> A) No. Let's not do anything new. The status quo we have seems fine.
> B) Yes, let's experiment with Discord / Slack / Teams / Gitter / IRC.
>
>
> If B, is your answer choice, and if we decide to experiment with a new
> solution, what could it be? (1-Many choices)
>
> A) Let's try with Discord for core-dev
> B) Let's try with Gitter for core-dev
> C) Let's try with private IRC group other than #python-dev
> D) Let's try with Slack for core-dev
> E) Let's try with Teams for core-dev
> F) I don't have a strong preference. I will use whatever core-dev community
> uses as long as I can use it on my platform or web.
>
> My aim is not disrupt existing systems that are used like #python-dev in
> IRC. So, it will continue to be chat mechanism open to public.
>
> There will privacy focus with this solution, details on where to host to
> be determined.
>
> I hope, I have represented the initial choices well. If not, please let
> me know.
>
> If we end up with coming to a consensus, I will make a formal proposal
> to the steering council to make a pronuncement on this topic.
>
>
> Thank you,
> Senthil
> ___
> 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.org/
> Message archived at
> https://mail.python.org/archives/list/python-committers@python.org/message/J7XSINSNWKNMYUVOXNJVGZWBECHVDHSB/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
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.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/W5DSDDSHLHTHKM55CA635ZEN5ZYRB3QR/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: core-dev chat

[Kyle Stanley]

> FWIW, I would love to add a core dev Discord server to my long-ish list of
> Discord servers. It's a chat platform I find convenient (much more so than
> Zulip and Slack, and slightly more so than IRC), very organised, with good
> moderation tools (better than Slack and IRC), and widely adopted. If people
> prefer other platforms I will endeavour to participate, but it won't be as
> convenient to me as Discord.
>

Huge +1. I'd love to have a place to hang out and voice chat (or text) with
others on the core team in real time. I think it would double as a great
social outlet, and we could keep it very simple to the point where its
basically just IRC with some extra features. Using existing servers like
PySlackers or Python Discord aren't ideal options (as much as I love Python
Discord), just because there's too much noise to filter out if one is only
interested in the core dev aspect. Whatever we do, I think it needs to be
just for the core development community with as little noise as possible.
___
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.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/5YSJEIPT7HPUFDUI7SUVBXTNTBTXBBC5/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Welcome Irit Katriel to the team!

[Kyle Stanley]

 Welcome to the team, Irit! :-)

On Tue, May 11, 2021 at 1:18 AM Brett Cannon  wrote:

> EOM
> ___
> 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.org/
> Message archived at
> https://mail.python.org/archives/list/python-committers@python.org/message/RJLSGQW233DBYJWKXGHCXVZUKLMOTYJR/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
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.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/AJHRZNNA7IFZGVIN3N3AAWUK47T7FZPV/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] The importance of mental health

[Kyle Stanley]

Hey all,

In these last few months, I have been in the process of healing from some
pretty heavy past trauma. And now that I am on the road to recovery, I want
to share my journey with the Python community in hopes that it may reach
those that are struggling with their own mental health battles, as many of
us are during these dark and difficult times.

Trigger warning that it includes a decent amount of highly personal
content, so only check it out if you are okay with that:
https://discuss.python.org/t/break-from-open-source/6372/7?u=aeros.

To anyone that would limit my employment opportunities as a result of
having had these struggles, *that's perfectly okay*. I kept the post in the
private section because I was originally in fear of discriminate. However,
I have reached an important conclusion: *I would not want to work for your
company if you discriminate against people who have overcome past struggles*
.

-- 
--Kyle R. Stanley, Python Core Developer (what is a core dev?
)
*Pronouns: they/them **(why is my pronoun here?*

)
___
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.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/3H6JIULWOTFYMJLWOBFO7PM4RAOEL74U/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Welcome Batuhan Taskaya to the team!

[Kyle Stanley]

Welcome to the core dev team, Batuhan!

On Mon, Nov 9, 2020 at 5:02 PM Brett Cannon  wrote:

> 
> ___
> 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.org/
> Message archived at
> https://mail.python.org/archives/list/python-committers@python.org/message/23C4CKSESDVFUVJCSZ4X3U7CUPUJKWUP/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
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.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/Y3BHAIMHWQSPWTNSWFH5YNNKNWDG5Q3V/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Core Dev Sprint: Collecting Discord usernames

[Kyle Stanley]

On Fri, Oct 2, 2020 at 2:07 AM Kyle Stanley  wrote:

> Prior to joining Python Discord, I recommend checking out the Discord
> setup guide that I recently finished:
> https://python-core-sprint-2020.readthedocs.io/communication.html#discord-setup-guide.
> The part on the privacy settings is particularly important for anyone with
> a public following to avoid receiving mass DMs and friend requests.
>
> Alternatively, you can join directly at the following perma-link:
> https://discord.gg/Q87A9Y9.
>

Minor clarification: since there was mention that the "alternatively" part
was unclear, I was just referring to joining the server directly for those
that didn't have time available to read over the guide prior to joining
(the guide includes a section on joining the server via the link).

Also, since we will be granting the role to participants en masse via
script, it will be granted after the majority of participants have
responded. As of writing this, I've received ~10/41 responses.
___
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.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/ZCQMRVDVWOB36RKGTJMO4SRJYFMUC46B/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Core Dev Sprint: Collecting Discord usernames

[Kyle Stanley]

Hey all,

The upcoming 2020 Python Core Development Sprint is right around the
corner, and we're currently towards the end of finalizing platform setup.

For using Discord during the sprint on the public Python Discord server (as
voted on in
https://discuss.python.org/t/2020-core-dev-sprint-poll-discord-or-zulip/5016/6),
we are collecting Discord usernames ahead of time and requesting that all
participants join Python Discord well before the start of the sprint (Oct.
19th). This will allow us to grant all participants a role for joining the
sprint channels (in order to be given the role, participants must be on the
server first).

To send your Discord username, simply reply to this email (without CCing
the list to keep it private) with it included. It is in the format of
"name#0123", and can be seen in the lower left corner of the Discord client
after creating an account (or in "User Settings" > "My Account"). I'll
verify replies against the email address used in the signup form, so please
use the same one if possible.

Prior to joining Python Discord, I recommend checking out the Discord setup
guide that I recently finished:
https://python-core-sprint-2020.readthedocs.io/communication.html#discord-setup-guide.
The part on the privacy settings is particularly important for anyone with
a public following to avoid receiving mass DMs and friend requests.

Alternatively, you can join directly at the following perma-link:
https://discord.gg/Q87A9Y9.

As a reminder, potential participants include Python core developers,
triagers, and those in a core dev mentorship. If you haven't already signed
up and are interested in attending, please do so at
https://forms.gle/fhzJdpRHR4GtSRCk9.

Regards,
Kyle Stanley
___
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.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/H3BFBA2HH5SQ222DL27YFI3ABKAONAKI/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Welcome Brandt Bucher to the team!

[Kyle Stanley]

Welcome to the core development team, Brandt! Great to have you on board.
:-)

On Wed, Sep 16, 2020 at 2:31 PM Brett Cannon  wrote:

> 
> ___
> 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.org/
> Message archived at
> https://mail.python.org/archives/list/python-committers@python.org/message/VWLTZR5FDXFRCCRUATKBF2G4JTQCKVH7/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
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.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/HZJ5ELTW4TFR2OVEM7GIRPDTRTIEFAZT/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] RSVP: 2020 Python Core Dev Sprint

[Kyle Stanley]

Hey all,

We just recently finished working on the signup form for the upcoming 2020
Python Core Dev Sprint on Oct. 19th - 23rd. In addition to getting an
general idea of (virtual) attendance, this is being used to assess the
topics covered, optimal start/end times for each day, and preferred social
activities.

Anyone who is a CPython core developer, engaged in a core dev mentorship,
or a member of the Python triage team is welcome to attend!

Sign up to attend here: https://forms.gle/84NkyYt5g616fs1r5

We will be accepting late sign ups for this event since capacity is not a
significant limitation, but for the purposes of scheduling the best
possible times for everyone, it is requested that participants do so at
their earliest convenience.

Regards,
Kyle Stanley
___
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.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/C24BIJVTG53G4X25K5QLPP2WPKDCI2XA/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] 2020 Core Dev Sprint Poll: Discord or Zulip

[Kyle Stanley]

Hey all,

For the upcoming 2020 Core Dev Sprint, we (Mariatta, Ewa, and I) decided to
create a poll for determining the platform that participants would prefer
to use. With this year's sprint being entirely virtual, the platform of
choice will have a significant impact on the event.

Poll:
https://discuss.python.org/t/2020-core-dev-sprint-poll-discord-or-zulip/5016

Regards,
Kyle Stanley
___
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.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/DPQGH3U2WG4AFWWV3OVIISZCKPR7PTDK/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Please welcome Lysandros Nikolaou to the team!

[Kyle Stanley]

>From one new member of the core team to another, welcome Lysandros! I look
forward to potentially working with you in the future. With the technical
expertise displayed from your work on the PEG parser, I have no doubt that
you'll provide invaluable contributions going forward. :-)

On Tue, Jun 30, 2020 at 4:50 PM Lysandros Nikolaou 
wrote:

> [cross-posting on python-commiters and on
> https://discuss.python.org/t/vote-to-promote-lysandros-nikolaou/4445/11]
>
> Hey everybody,
>
> first of all a huge thanks goes out to all of you for showing trust in me
> and accepting me into this big Python family. It’s truly an honour to be
> part of it.
>
> I will try to put all the effort and care I can into improving Python, the
> language, which has time and again helped me in my career as a programmer.
> I sincerely hope that the PEG parser is only the first of many projects I
> work on.
>
> Let me say that I believe that the values we represent and uphold really
> make us what we are. Thus, I will try to live up to the high standards of
> the Python community and, like all of us, I’ll strive to make Python an
> even more inclusive, diverse and open community than it is now.
>
> It goes without saying but I want to say for the thousandth time
> that Guido’s and Pablo’s mentoring has been invaluable. Very special thanks
> to both of them for, first, accepting me to work alongside them and for all
> they’ve shown and taught me these last few months. It’s been an awesome
> journey and I’m sure it’ll continue to be just like this.
>
> I’m looking forward to getting to know you all better.
>
> Cheers.
>
> On Tue, Jun 30, 2020 at 10:21 PM Brett Cannon  wrote:
>
>> 
>> ___
>> 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.org/
>> Message archived at
>> https://mail.python.org/archives/list/python-committers@python.org/message/OQPA633CV5TA44BBYFBMU3CI4WRT4AVC/
>> Code of Conduct: https://www.python.org/psf/codeofconduct/
>>
> ___
> 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.org/
> Message archived at
> https://mail.python.org/archives/list/python-committers@python.org/message/DSOXUBKICA3MDFTPDFFRIUIEEUOFDX4G/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
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.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/GQPDW4AHWOQ7XNQHSDXIBJ3LKB2NYH5D/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Remove accidentally created branch on cpython repo

[Kyle Stanley]

Thanks for cleaning it up and for the info, Ned. :-)

On Thu, May 21, 2020 at 3:50 AM Ned Deily  wrote:

>
> On May 21, 2020, at 03:44, Kyle Stanley  wrote:
> > So by my own mistake in the GitHub UI, I was looking at a previous
> commit for one of my PRs (https://github.com/python/cpython/pull/19282)
> and misclicked the "revert commit" button instead of "view details".
> Fortunately, this only created a separate branch in the cpython repository
> instead of actually reverting anything (see
> https://github.com/python/cpython/tree/revert-19282-bpo40115-test_asyncio-run_in_executor_cancel),
> but I'm unsure of the best way to remove the branch or if I'm even able to.
>
> You can view the active branches here:
>
> https://github.com/python/cpython/branches/active
>
> If you have permission to delete it, there will be a trashcan icon to the
> right of the branch.
>
> I made it go away.
>
> > Sorry about the mixup, I'm rather new to the core developer role and
> this is my first time running into anything like this.
>
> No problem! We all have learning events along the way.  Keep hacking!
>
> --
>   Ned Deily
>   n...@python.org -- []
>
>
___
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.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/TMI7HP7EEEQ4TQZIU6VCRLQEAJLORGTW/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Remove accidentally created branch on cpython repo

[Kyle Stanley]

Hey all,

So by my own mistake in the GitHub UI, I was looking at a previous commit
for one of my PRs (https://github.com/python/cpython/pull/19282) and
misclicked the "revert commit" button instead of "view details".
Fortunately, this only created a separate branch in the cpython repository
instead of actually reverting anything (see
https://github.com/python/cpython/tree/revert-19282-bpo40115-test_asyncio-run_in_executor_cancel),
but I'm unsure of the best way to remove the branch or if I'm even able to.

Sorry about the mixup, I'm rather new to the core developer role and this
is my first time running into anything like this.

Regards,
Kyle Stanley
___
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.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/XVW5GXWJGBH2EITJ3RNFA4IPYLCPG4B2/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Please welcome our next Release Manager, Pablo!

[Kyle Stanley]

> In light of the release of Python 3.9b1, let’s take a moment to celebrate
all the great work that our Python 3.8 and 3.9 release manager Łukasz has
done.

Thank you so much to Łukasz for a fantastic 3.8 release, and for the smooth
transition into 3.9 beta. :-)

> Please join me in welcoming Pablo in his new role!

Congrats, Pablo! With all of your incredible work on CPython's continuous
integration, I think you'll be a great release manager!

On Tue, May 19, 2020 at 6:54 PM Barry Warsaw  wrote:

> In light of the release of Python 3.9b1, let’s take a moment to celebrate
> all the great work that our Python 3.8 and 3.9 release manager Łukasz has
> done.  The role of Python Release Manager is hugely important to each
> successful release, and it can be a lot of work, often unseen and thankless
> to shepherd a new Python version through its first alpha release to its
> last security release.  With all of your immeasurable help, the Release
> Manager ensures solid, feature-full releases that the entire Python
> community eagerly awaits.
>
> Łukasz carries on the fine tradition of all of our past release managers,
> and now that his second release has entered beta phase, I’m very happy to
> announce our next Release Manager, for Python 3.10 and 3.11: Pablo Galindo
> Salgado!
>
> Since becoming a core developer in 2018, Pablo has contributed
> significantly to Python.  With the change to an annual release cycle (PEP
> 602, authored by Łukasz), the time commitment for release managers has been
> reduced as well, and we will continue to look for ways to make the
> selection process for release managers more transparent and accessible.  I
> know that in addition to admirably managing the releases for 3.10 and 3.11,
> Pablo will also help to continually improve the process of selecting and
> serving as release manager.
>
> Please join me in welcoming Pablo in his new role!
>
> Cheers,
> -Barry
>
> ___
> 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.org/
> Message archived at
> https://mail.python.org/archives/list/python-committers@python.org/message/44TLJO5YX6XYM4ICWSHMBMCKPBBQQP5S/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
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.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/J3CGQNJ2UH3RPFJ2IEVGERTIRAMGXOLI/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Lysandros Nikolaou got the bug triage permission!

[Kyle Stanley]

Welcome and congrats Lysandros!

On Wed, Apr 22, 2020 at 6:04 PM Pablo Galindo Salgado
 wrote:
>
> Hi,
>
> I am giving triage privileges to Lysandros Nikolaou (lys.nikolaou on bpo, 
> lysnikolaou in GitHub) .
>
> Lysandros has been working with Guido and myself in PEP 617 for quite a long 
> time, being an indispensable
> member of the team. In all this time he has proven to have a great set of 
> technical skills both in C and Python
> while being a real pleasure to work with. Lysandros has also learned greatly 
> about the processes, workflow
> and values of the core team and always has great enthusiasm and will to 
> improve. I can say with confidence
> that Lysandros is an excellent developer, a compassionate person and someone 
> who has shown to care about
> Python and its community.
>
> As usual, I will ask him to ask me before closing bugs for the first weeks.
>
> Congrats, Lysandros!
> ___
> 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.org/
> Message archived at 
> https://mail.python.org/archives/list/python-committers@python.org/message/MOOCZENDBLSYEXD56YYSWGJU3C2KKOKJ/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
___
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.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/4W3RIYNPYG7KBW3575EJXDJ2VUAJ4ROJ/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Welcome Kyle Stanley to the team!

[Kyle Stanley]

Thank you for the support everyone and for adding my permissions, Brett! I 
wrote my "acceptance speech" over on discuss: 
https://discuss.python.org/t/vote-to-promote-kyle-stanley/3839/7.
___
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.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/SGXGL2YXL3EWXONMBJ4CZB37ZK6B5BPD/
Code of Conduct: https://www.python.org/psf/codeofconduct/