iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
python-peps/pep0/constants.py

38 lines
973 B
Python
Raw Normal View History

add the supporting library for generating PEP 0
2008-12-30 12:44:55 -05:00
# -*- coding: utf-8 -*-
title_length = 55
column_format = (u' %(type)1s%(status)1s %(number)4s %(title)-' +
unicode(title_length) + u's %(authors)-s')
header = u"""PEP: 0
Title: Index of Python Enhancement Proposals (PEPs)
Add in a dummy Version value for PEP 0 to make pep0 code happy.
2010-09-27 15:36:11 -04:00
Version: N/A
Put Version before Last-Modified in PEP 0.
2010-09-27 16:54:00 -04:00
Last-Modified: %s
add the supporting library for generating PEP 0
2008-12-30 12:44:55 -05:00
Author: David Goodger <goodger@python.org>,
normalize Barry's name
2009-01-07 22:44:48 -05:00
Barry Warsaw <barry@python.org>
add the supporting library for generating PEP 0
2008-12-30 12:44:55 -05:00
Status: Active
Type: Informational
Created: 13-Jul-2000
"""
intro = u"""
Further updates to PEP 1 to better reflect current practice - identify the current PEP editors and clarify their role - separate out PEP administrative email from design discussion - reference implementations typically co-evolve with their PEP - it's OK to get a PEP number before a PEP is ready for python-dev - eliminate most of the ambiguous 'we' references (Initial patch by Chris Jerdonek)
2012-12-22 06:30:14 -05:00
This PEP contains the index of all Python Enhancement Proposals,
known as PEPs. PEP numbers are assigned by the PEP editors, and
once assigned are never changed[1]. The Mercurial history[2] of
Fix mentions of svn.python.org and remove unneeded files.
2011-03-24 04:10:55 -04:00
the PEP texts represent their historical record.
add the supporting library for generating PEP 0
2008-12-30 12:44:55 -05:00
"""
references = u"""
Further updates to PEP 1 to better reflect current practice - identify the current PEP editors and clarify their role - separate out PEP administrative email from design discussion - reference implementations typically co-evolve with their PEP - it's OK to get a PEP number before a PEP is ready for python-dev - eliminate most of the ambiguous 'we' references (Initial patch by Chris Jerdonek)
2012-12-22 06:30:14 -05:00
[1] PEP 1: PEP Purpose and Guidelines
[2] View PEP history online
use https url to hg.python.org
2014-11-14 12:17:47 -05:00
https://hg.python.org/peps/
add the supporting library for generating PEP 0
2008-12-30 12:44:55 -05:00
"""
footer = u"""
Local Variables:
mode: indented-text
indent-tabs-mode: nil
sentence-end-double-space: t
fill-column: 70
coding: utf-8
End:"""