Contributing to Python: Difference between revisions

m
Protected "Contributing to Python" (‎[edit=sysop] (indefinite) ‎[move=sysop] (indefinite))
imported>Jesstess
No edit summary
imported>Jesstess
m (Protected "Contributing to Python" (‎[edit=sysop] (indefinite) ‎[move=sysop] (indefinite)))
 
(3 intermediate revisions by the same user not shown)
Line 1:
Welcome! This page contains instructions for getting started with contributing to Python. They cover practicing some of the common tools of open source development, as well as steps for contributing specifically to Python.
 
These instructions were written for prospective [http://wiki.python.org/moin/OPW/2014| GNOME Outreach Program for Women] and [http://wiki.python.org/moin/SummerOfCode/2014| Google Summer of Code] interns, but are relevant for anyone interested in contributing to CPython and the standard library.
 
[[File:Python_logo.png|200px]] [[File:Opw.png|200px]] [[File:Pyladies_logo.png|200px]]
Line 50:
Mercurial is the distributed version control system Python uses to manages changes to its code.
 
Please [http://mercurial.selenic.com/downloads/| download and install Mercurial now].
 
If you have not used Mercurial before, please go through [this tutorial| http://hgbook.red-bean.com/read/a-tour-of-mercurial-the-basics.html this tutorial].
 
 
Line 74:
The Python community has a lot of mailing lists. The 2 big ones for new contributors are:
 
# [http://mail.python.org/mailman/listinfo/core-mentorship| core-mentorship]: This is a great place to ask questions about contributing, ask for reviews, and get suggestions for bugs to work on.
# [http://mail.python.org/mailman/listinfo/python-dev| python-dev]: The main mailing list for developing and releasing Python. Please do not ask general Python questions on this list.
 
The core-mentorship mailing list will be our focus as we get settled in, so please [http://mail.python.org/mailman/listinfo/core-mentorship| join the list] now.
 
 
Line 88:
Please read through the following sections of the developer guide:
 
# [http://docs.python.org/devguide/#quick-start| Quick start]
# [http://docs.python.org/devguide/setup.html| Setup]
# [http://docs.python.org/devguide/help.html| Where to get help]
# [http://docs.python.org/devguide/patch.html| The lifecycle of a patch]
# [http://docs.python.org/devguide/runtests.html| Writing and running tests]
# [http://docs.python.org/devguide/tracker.html#tracker| Using the issue tracker]
# [http://docs.python.org/devguide/devcycle.html| The CPython development cycle]
 
By the end, you'll:
Line 116:
First, the developer guide suggests 2 good areas for first-time contributors:
 
# [http://docs.python.org/devguide/docquality.html| Documentation]
# [http://docs.python.org/devguide/coverage.html| Test coverage]
 
If those sound interesting to you, look for issues in those areas.
Anonymous user