Mailman 3 May 2021 - python-committers

Call for resumes: Developer-in-Residence to support CPython
by Ewa Jodlowska 20 Jul '21

20 Jul '21

Hello! Through a collaboration, the PSF and SC scoped the role for a Developer-in-Residence. We are now accepting resumes -- see below for details. I am super happy to finally set this in motion! If you have any questions, don't hesitate to reach out. Ee and I are on apply@ so feel free to send questions there as well. A blog will be posted later today informing the community. ------------------------------------------------------------------ The Python Steering Council and the Python Software Foundation are looking to hire a Developer-in-Residence! Background CPython, the reference implementation of Python, is developed and primarily maintained by volunteers. Inspired by the Django Fellowship Program's success ( https://www.djangoproject.com/fundraising/), the PSF has strategically planned to support CPython in a similar way beginning this year. Thanks to the support from sponsors such as Google, this effort is moving forward. 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. Job Description This Developer-in-Residence will continually coordinate with PSF staff and the Steering Council on the following tasks (note: this is not an exhaustive list of all tasks, but an overview of desired outcomes): - Create metrics based on: - Surveying maintainers and community to capture: - a directory showing who maintains what standard library module - interest in maintaining standard library modules - which standard library modules are most important to users - Combine usage and surveyed metrics to determine which standard library modules need help and what the maintainer cost is for standard library modules - Determine additional intersections of data that could be useful - Address Pull Request and Issue backlogs based on the developed metrics and other metrics created by the Steering Council - Create a long-term plan for addressing the backlog - Review personally pull requests & triage issues - Help coordinate core developers/maintainers of specific modules to review pull requests and triage issues - Help maintaining, improving and stabilizing the CPython test suite, including the continuous integration infrastructure and buildbot fleet. - Attend Steering Council meetings quarterly and have regular communications with the PSF staff - Organize virtual sprints (i.e., at PyCon US) to collaborate with other Python core developers to grow the community of Python core developers and simultaneously close a large number of existing issues and pull requests - Provide transparency by proposing and fulfilling a public record as agreed to by the Steering Council and PSF Staff - Publish two blogs on pyfound.blogspot.com throughout the year informing the community on progress (halfway through and at the end of the residency) Necessary skills - Strong project management skills - Must be very organized and detail-oriented - Experience working with CPython volunteers - Excellent written and verbal communication - Experience working with software development teams remotely - Ability to balance demand and prioritize An active maintainer of CPython is preferred. Interested in this position? If you are interested, please send an email to apply(a)python.org with your resume (please include community contributions). The call for resumes will be open until May 16, 2021, AoE. Employment/vendor arrangement will depend on whether the person resides in or outside of the US.

9 11

Vote on core-dev chat choice
by Senthil Kumaran 03 Jun '21

03 Jun '21

Please vote on this topic of "Core-dev" chat choice. https://discuss.python.org/t/vote-on-core-dev-chat-choice/8870 Thank you, Senthil

2 3

Farewell, for now :)
by Kyle Stanley 31 May '21

31 May '21

Hi all, Last week, I started a new thread on discuss.python.org <https://discuss.python.org/t/farewell-for-now/8918?u=aeros> 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? <https://devguide.python.org/coredev/>) *Pronouns: they/them **(why is my pronoun here?* <http://feministing.com/2015/02/03/how-using-they-as-a-singular-pronoun-can-…> )

1 0

Commits are no longer noted in bro issues
by Guido van Rossum 29 May '21

29 May '21

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)

10 17

IMPORTANT: Python 3.10b2 release blockers
by Pablo Galindo Salgado 28 May '21

28 May '21

Hi, Tomorrow is the scheduled release of Python 3.10 beta 2 but unfortunately we have several release blockers: https://bugs.python.org/issue41282: Deprecate and remove distutils https://bugs.python.org/issue40222: "Zero cost" exception handling https://bugs.python.org/issue42972: [C API] Heap types (PyType_FromSpec) must fully implement the GC protocol https://bugs.python.org/issue44043: 3.10 b1 armhf Bus Error in hashlib test: test_gil We also have the address sanitizer buildbot failing : https://buildbot.python.org/all/#/builders/582/builds/165/steps/5/logs/stdio and some segmentation faults on the fedora stable buildbot: https://buildbot.python.org/all/#/builders/543/builds/190 Some of these issues have PRs but some of them have not. Please, if you are involved or you maintain one of the areas involved in these issues, take a look at them and act with one of the following: * Fix the issue making a PR * Review an existing PR and / or merge it * If you intend to mark it as a deferred blocker, please provide a rationale and contact me first by pinging me in the issue. Until these issues are fixed or deferred, the release team will not be able to make a new beta release. Thanks for your help, Regards from stormy London, Pablo Galindo Salgado

7 28

Re: core-dev chat
by Senthil Kumaran 23 May '21

23 May '21

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

3 7

core-dev chat
by Senthil Kumaran 18 May '21

18 May '21

Hello Core Dev, I find a need for a core-dev chat service, wherein I could engage in some quick effervescent conversations. It is like a team chat, that is popular with remote work these days. We even seem to have used Zoom Chat yesterday! * I know #python-dev in IRC exists, but it is mostly a channel for bots to send notifications, and there are plenty. I am not certain if any core dev is active there. There was a time when this was active. * We tried python discord last year, and were bit overwhelmed with the number of channels and inability to customize * There seems to be Slack called pyslackers too[1]. I am yet to try it. To have a proper team-chat, we need a service (a) as well as (b) team using that. Does anyone else feel the need? Should we explore any? My thoughts and options are a) Resurrect #python-dev - changing notifications to different group. b) Request for core-dev in pyslackers Slack c) Request for core-dev in Discord. Any other ideas are welcome. 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. If we feel a chat service will be a good idea for core-dev to hangaround, then we can go to stage 2 of choosing the service by votes in discourse (discuss.python.org). Thank you, Senthil

21 55

Welcome Irit Katriel to the team!
by Brett Cannon 11 May '21

11 May '21

EOM

7 6

Important: Python3.10 what's new
by Pablo Galindo Salgado 10 May '21

10 May '21

Hi everyone, Now that we are in the beta period for 3.10 is very important that we make sure that all improvements, new APIs and deprecations are reflected in the 3.10 what's New document. IMPORTANT!! If you have worked on: * Make a PEP that affects Python 3.10. * A new feature/class/function/argument/option... * Deprecating something. * Remove something. * Improve something important. Please, make sure is reflected on the What's new document for Python 3.10. Users normally don't read the changelog directly and learn about what's available from the What's New document so you *absolutely* want your work to be reflected there. *Small* tutorials and small code samples and descriptions are a fantastic thing to add as well. Specially for deprecations and removals, this is our public window to the world so that learn what's coming or how to port code to Python 3.10. Thanks for helping to make Python3.10 a great release. Regards from sunny London, Pablo Galindo Salgado

2 1

The importance of mental health
by Kyle Stanley 10 May '21

10 May '21

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? <https://devguide.python.org/coredev/>) *Pronouns: they/them **(why is my pronoun here?* <http://feministing.com/2015/02/03/how-using-they-as-a-singular-pronoun-can-…> )

1 0