How do ideas on this mailing list turn into features?
How do ideas on this mailing list turn into features? What is the typical roadmap? Can this process be documented somewhere?
https://devguide.python.org/#proposing-changes-to-python-itself
On Fri, Feb 1, 2019, 1:12 PM James Lu How do ideas on this mailing list turn into features? What is the typical
roadmap? Can this process be documented somewhere?
_______________________________________________
Python-ideas mailing list
Python-ideas@python.org
https://mail.python.org/mailman/listinfo/python-ideas
Code of Conduct: http://python.org/psf/codeofconduct/
Basically the process is described here. Of course, as in any Open Source
projects, any ideas have a lot more chance of being considered if they are
accompanied by a patch with at least an example, partial but working
implementation of proposed feature.
https://www.python.org/dev/peps/pep-0001/
Em sex, 1 de fev de 2019 às 16:12, James Lu
How do ideas on this mailing list turn into features? What is the typical roadmap? Can this process be documented somewhere? _______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
-- Marcos Eliziário Santos mobile/whatsapp/telegram: +55(21) 9-8027-0156 skype: marcos.eliziario@gmail.com linked-in : https://www.linkedin.com/in/eliziario/
On 2/1/2019 1:10 PM, James Lu wrote:
How do ideas on this mailing list turn into features? What is the typical roadmap? Can this process be documented somewhere?
Ultimately, one or more people write Pull Request, usually containing new tests, that passes all tests. Then a Core Developer with current commit privileges who approves (after considering opinions of others) merges the PR into the main repository. -- Terry Jan Reedy
participants (4)
-
Geoffrey Spear -
James Lu -
Marcos Eliziario -
Terry Reedy