Differences between revisions 25 and 27 (spanning 2 versions)
Revision 25 as of 2005-02-09 01:35:54
Size: 3111
Revision 27 as of 2005-05-02 01:50:55
Size: 3111
No differences found!

This page will collect information about the Python Software Foundation, and its committees.


The PSF has started a grants program to fund Python-related development. For more information, see [http://www.python.org/psf/grants/ PSF Grants].

PSF License

Important: See PythonSoftwareFoundationLicenseFaq before using the following licenses.

Older wiki materials can be found here:

PSF Software Contribution Agreement

Committees and Board of Directors

Special Project: Python.org website redesign

In January 2005, the PSF board voted to fund a proposal from Tim Parkin and Matt Goodall to develop a new framework for the python.org website. The purpose of this is to update the look for the python.org site and move to a more accessible and modern design (based on CSS), while keeping maintenance of the site simple and avoiding reliance on heavy monolithic tools. The text of the proposal is available at WebsiteRedesignProposal.


How do Modules Become Part of the Python Distribution?

I've always wondered:

How do modules become part of the Python distribution? What kind of process do you follow, what groups do you participate in, to become a part of that?

I've looked around, but haven't found any web pages on the subject.

-- LionKimbro DateTime(2004-06-28T21:22:21Z)

Answer: The final decision is by BDFL pronouncement, but the usual process is that the module is first written as a stand-alone module, and released. After it's been in use for some time, the author makes the suggestion in comp.lang.python or python-dev (both are used, I'm not sure which is preferred) that it be adopted into the standard distribution. This gets discussed by the usual crowd and usually the answer is obvious long before it ever gets to Guido. Certain modules skip the stand-alone stage and are adopted directly into the standard library, but that is usually because the module was written in response to requests, and frequently by an experienced python core developer. If you are interested in getting your module adopted into the core, the #1 question you are sure to be asked is "are you willing to commit to supporting this module for at least the next 5 years?", because unless SOMEONE is willing to volunteer to provide that support the module can't be accepted.

-- MichaelChermside

PythonSoftwareFoundation (last edited 2021-10-14 21:17:03 by Srinivas Ramakrishna)

Unable to edit the page? See the FrontPage for instructions.