Your message dated Fri, 11 Jul 2014 19:24:11 -0400
with message-id <27569011.YbDX5QnXVc@scott-latitude-e6320>
and subject line The information requested is now included in the documentation
has caused the Debian Bug report #163703,
regarding [SF #621526] Docs do not include accepted PEPs
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
163703: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=163703
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python-doc
Version: 2.1.3-4
Severity: important
A large part of the python docs regarding new features (and this especially
true for 2.2) are only in PEPs (and for 2.2). The "What's New" pages just say
"see PEP 123" or something. However, python-doc doesn't include the PEPs. I
think it should include all accepted PEPs for the respective Python version.
-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux topato 2.4.18 #1 Sat Jul 20 11:28:52 EDT 2002 i586
Locale: LANG=C, LC_CTYPE=
Versions of packages python-doc depends on:
ii python2.1-doc 2.1.3-4 Documentation for the scripting la
--- End Message ---
--- Begin Message ---
Upstream rejected the idea of putting PEP's directly into the docs, but in
this case the information in question is now added.
--- End Message ---
