Hello everyone! After a delay to finalize the various logistics details, [@pradyunsg , @FFY00 , @CAM-Gerlach] and I are pleased to announce that registration and topic proposals for the Python Packaging Summit at PyCon US 2023 are officially open! As in previous years, the summit will be an opportunity to have a hands-on, in-person discussion of the key packaging issues facing the Python community, with the topics to be decided by all of you.

This year, instead of one monolithic four-hour block, it'll be split into two shorter two-hour sessions—one near the beginning and one near the end of the conference, to both minimize conflicts with other events and give participants a break to think about the initial topics discussed and reconvene with fresh minds and insight. The first session will be Friday, April 21 from 10:30 AM - 12:30 PM, and the second will

Iteration toward Transformation of the Python Documentation

With the tremendous growth of the Python ecosystem, attracting an ever-wider audience of users with a variety of backgrounds and experience levels, it is more critical than ever that its documentation better serve the needs of its diverse array of readers. We formally introduce the Python Docs Community—the self-organized, Python Steering Council-endorsed collective working toward this goal—and provide a look at the major user-facing improvements implemented, underway and coming soon for the core documentation, devguide, PEPs and more.

Here's a strategy and a bunch of tips and tricks for dealing with a full inbox of GitHub notifications, dealing with those that matter and getting rid of the rest, and keeping things clean, organized and easy to deal with for the future. This is based on my own experiance using both and moving from the former to the latter, but YMMV.

• Mark all your unread GH emails as read, and maybe move them to a special folder/label just in case
• Mark all "read" GH notifications as done since you've presumably already seen them via email, using Select by -> Read at the top, then click the Done button
• Mark notifications on all closed/merged issues/PRs as done using the same Select by menu/Done button.
• Similarly, for any repos you know you don't care about, select them with the lower part of the left sidebar or repo:<name> in the search bar, then Select all and Done

If Spyder crashes or you receive an error message, please read the following troubleshooting steps before opening a new ticket. There's a good chance that someone else has already experienced the same issue, so solving it yourself will likely get Spyder working again for you as quickly as possible.

Important Note: To make sure you're getting the most relevant help for your problem, please make sure the issue is actually related to Spyder:

    General:
    - Key words (must/not, should/not, may/can) follow IETF conventions

    Structure:
    - In general, follow the [OpenStack Heading Guidelines](https://docs.openstack.org/doc-contrib-guide/writing-style/general-writing-guidelines.html) with regard to sections and headings; in particular, section and subsection titles delineating overall categories of tasks/topics and be in gerund (i.e. with "ing", e.g. "Editing code", "Debugging files"), while those concerning a concept or reference topic should be a noun (e.g. "General considerations", "Requirements") and lowest level topic/task titles should generally be in imperative ("Create a code cell", "Get help", etc) where reasonable
    - 1 L1 Heading for title with component/topic name in Title Case, use ###### with overline, on first line, keep to a few words
    - All other headings: Two blank lines should preceede them; use sentence case, with a capital letter beginning a parenthetic Like this: Begin with caps 

If Spyder crashes or you receive an error message, please read the following troubleshooting steps before opening a new ticket. There's a good chance that someone else has already experienced the same issue, so solving it