68 captures

25 Jun 2018 - 08 Jan 2026

Oct	NOV	Dec
	25
2019	2020	2021

success

fail

About this capture

COLLECTED BY

Collection: Common Crawl

Web crawl data from Common Crawl.

TIMESTAMPS

The Wayback Machine - http://web.archive.org/web/20201125082258/https://devguide.python.org/communication/

Navigation

● index ● next | ● previous |

●Python » Python Developer's Guide »

12. Following Python’s Development¶

Python’s development is communicated through a myriad of ways, mostly through mailing lists, but also other forms.

12.1. Mailing Lists¶

python-dev is the primary mailing list for discussions about Python’s development. The list is open to the public and is subscribed to by all core developers plus many people simply interested in following Python’s development. Discussion is focused on issues related to Python’s development, such as how to handle a specific issue, a PEP, etc. ●Ideas about new functionality should not start here and instead should be sent to python-ideas. ●Technical support questions should also not be asked here and instead should go to python-listorpython-help. Python-ideas is a mailing list open to the public to discuss ideas on changing Python. If a new idea does not start here (orpython-list, discussed below), it will get redirected here. Sometimes people post new ideas to python-list to gather community opinion before heading to python-ideas. The list is also sometimes known as comp.lang.python, the name of the newsgroup it mirrors (it is also known by the abbreviation c.l.py). The python-committers mailing list is a private mailing list for core developers (the archives are publicly available). If something only affects core developers (e.g., the tree is frozen for commits, etc.), it is discussed here instead of python-dev to keep traffic down on the latter. Python-checkins sends out an email for every commit to Python’s various repositories from https://github.com/python/cpython. All core developers subscribe to this list and are known to reply to these emails to make comments about various issues they catch in the commit. Replies get redirected to python-dev. There are two mailing lists related to issues on the issue tracker. If you only want an email for when a new issue is open, subscribe to new-bugs-announce. If you would rather receive an email for all changes made to any issue, subscribe to python-bugs-list. General Python questions should go to python-listortutor or similar resources, such as StackOverflow or the #python IRC channel on Freenode. Core-Workflow mailing list is the place to discuss and work on improvements to the CPython core development workflow. A complete list of Python mailing lists can be found at https://mail.python.org. Most lists are also mirrored at GMANE and can be read and posted to in various ways, including via web browsers, NNTP newsreaders, and RSS feed readers.

12.2. Zulip¶

We have our own zulipchat instance. This should be used to discuss the development of Python only.

12.3. IRC¶

Some core developers enjoy spending time on IRC discussing various issues regarding Python’s development in the #python-dev channel on irc.freenode.net. This is not a place to ask for help with Python, but to discuss issues related to Python’s own development. You can use Freenode’s Web interface if you don’t have an IRC client.

12.4. Blogs¶

Several core developers are active bloggers and discuss Python’s development that way. You can find their blogs (and various other developers who use Python) at http://planetpython.org/.

12.5. Standards of behaviour in these communication channels¶

We try to foster environments of mutual respect, tolerance and encouragement, as described in the PSF’s Diversity Statement. Abiding by the guidelines in this document and asking questions or posting suggestions in the appropriate channels are an excellent way to get started on the mutual respect part, greatly increasing the chances of receiving tolerance and encouragement in return.

12.6. Setting Expectations for Open Source Participation¶

Burn-out is common in open source due to a misunderstanding of what users, contributors, and maintainers should expect from each other. Brett Cannon gave a talk about this topic that sets out to help everyone set reasonable expectations of each other in order to make open source pleasant for everyone involved.

12.7. Additional Repositories¶

Python Core Workflow hosts the codebase for tools such as cherry_picker and blurb. Python Performance Benchmark project is intended to be an authoritative source of benchmarks for all Python implementations.

●12. Following Python’s Development ●12.1. Mailing Lists ●12.2. Zulip ●12.3. IRC ●12.4. Blogs ●12.5. Standards of behaviour in these communication channels ●12.6. Setting Expectations for Open Source Participation ●12.7. Additional Repositories

This Page

● Show Source

Navigation

● index ● next | ● previous |

●Python » Python Developer's Guide »

Navigation

12. Following Python’s Development¶

12.1. Mailing Lists¶

12.2. Zulip¶

12.3. IRC¶

12.4. Blogs¶

12.5. Standards of behaviour in these communication channels¶

12.6. Setting Expectations for Open Source Participation¶

12.7. Additional Repositories¶

Table of Contents

Sections

Previous topic

Next topic

This Page

Navigation