[Python-bugs-list] [ python-Bugs-621526 ] docs do not include spec info from PEPs

[noreply@sourceforge.net]

Bugs item #621526, was opened at 2002-10-10 19:49
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=621526&group_id=5470

Category: Documentation
Group: Python 2.2.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Matthias Klose (doko)
Assigned to: Fred L. Drake, Jr. (fdrake)
Summary: docs do not include spec info from PEPs

Initial Comment:
[please see http://bugs.debian.org/163703]

The bug submitter complains, that the information found
in accepted PEPs like 252 and 253 cannot be found in
the "standard documentation" and proposes, that
accepted PEPs are included in the standard documentation.


----------------------------------------------------------------------

>Comment By: Jeremy Hylton (jhylton)
Date: 2002-10-14 19:39

Message:
Logged In: YES 
user_id=31392

Well it's not a question of cutting and pasting the spec 
part of a PEP into the reference manual.  The documentation 
changes, particularly for PEPs 252 and 253, are fairly 
substantial and involve a lot more than moving some text 
around.  (I'd wager that what counts as standard features 
and what is experimental isn't entirely clear.)

To sum up, I don't think there's much point keeping a bug 
report open for this unless there are a specific set of 
PEPs with tractable documentation to move around.


----------------------------------------------------------------------

Comment By: Matthias Klose (doko)
Date: 2002-10-12 07:53

Message:
Logged In: YES 
user_id=60903

Ok, changed the summary line.


----------------------------------------------------------------------

Comment By: Jeremy Hylton (jhylton)
Date: 2002-10-11 14:48

Message:
Logged In: YES 
user_id=31392

I don't think PEPs themselves should be included in the
documentation, but the relevant spec info should go into the
docs in an appropriate location.  I think leaving the
rationale/discussion part in the PEP is good.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=621526&group_id=5470