From the Steering Council, we would like to get some idea of everyone’s
availability for a potential core dev sprint this year. Given the current
world limitations on travelling and the time frame, it will have to be an
online core dev sprint like past year’s. Before any further work on this or
preparation, we need to determine a time frame for when it will happen so I
am opening this poll to find out about your availability so we can
determine the best time for everyone.
You can find the poll here:
Regards from cloudy London,
Pablo Galindo Salgado
I recently found a really nice tool to do code analysis and exploration:
Sourcetrail supports C, C++, Java and Python. It also integrates
well into many standard editors (in both directions).
It's great for analyzing dependencies in code and navigating the code
base. Indexing takes a bit long, but then you only do this once in
I suppose this could be of great help for new core devs, as well
as seasoned one exploring new parts of the code base.
Professional Python Services directly from the Experts (#1, Aug 27 2021)
>>> Python Projects, Coaching and Support ... https://www.egenix.com/
>>> Python Product Development ... https://consulting.egenix.com/
::: We implement business ideas - efficiently in both time and costs :::
eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
Registered at Amtsgericht Duesseldorf: HRB 46611
Just a quick note to mention that Dennis Sweeney (CC'd) has been added
to the Python Triage team:
https://github.com/python/core-workflow/issues/412. Dennis has
already been responding to new issues, and the newly added permissions
will enable better responses and corrections to issue/PR metadata.
As you might know, PEP 581 (Using GitHub Issues for CPython) has been
approved. I've been working with Ewa, Ee, the Working Group, the
Steering Council, and the GitHub folks to make this happen, and the SC
encouraged me to give you all a quick update.
This effort is being tracked at
<https://github.com/psf/gh-migration/projects/1>: this board reflects
the current status of the project. The PEPs (including PEP 588 --
GitHub Issues Migration Plan) haven't been updated yet and might
contain outdated information, so please refer to the psf/gh-migration
repo for the latest updates.
During the next phase I will work with the WG to sort out all the
major issues that we might encounter, and then I will once again reach
out to you to gather feedback from the wider audience that follows
these mailing lists.