< BACKMake Note | BookmarkCONTINUE >
152015024128143245168232148039196038240039088173205162105045222219252094020085215085111

New Development Process

Some business processes have changed after the main development team has left CNRI. Currently, SourceForge is hosting the Python project page at

http://sourceforge.net/projects/python/.

At that page, you can report bugs, visualize the Python CVS tree, submit patches, and use the patch manager and the bug tracking tools.

From now on, a new kind of document must be used in order to discuss new possible features and expose the Python community to information about features that have been implemented. This new document records all the discussion about the possibility to include a new idea in a future Python release. These documents are called Python Enhancement Proposals (PEPs), modeled on the Internet RFC process. It is said that they must provide a concise technical specification of the feature and a reason for the feature. They have to be used to collect input from the community and to document the design decisions that were approved. Each proposal has its own author as the sole responsible for managing it. Any kind of enhancement to the language must be documented by a PEP before it can be accepted as valid. For more information, check out

http://python.sourceforge.net/peps/


Last updated on 1/30/2002
Python Developer's Handbook, © 2002 Sams Publishing

< BACKMake Note | BookmarkCONTINUE >

Index terms contained in this section

migrating to Python 2.0
PEPs (Python Enhancement Proposals)
Python 2.0
      migrating to
      PEPs (Python Enhancement Proposals)
Python Enhancement Proposals (PEPs)
SourceForge
Web sites
      SourceForge

© 2002, O'Reilly & Associates, Inc.