By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
464,358 Members | 1,238 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 464,358 IT Pros & Developers. It's quick & easy.

Re: Problem found in tutorial

P: n/a


John W. Hamill wrote:
C:\__jh\ftp\python\2_5_2\doc\tutorial\node11.html
When reporting doc bugs, it is a good idea to check the most recent
version. The 3.0 version has the same problems (no changes have been
made -- page and graduates are still undefined), so report that too.

Jun 27 '08 #1
Share this Question
Share on Google+
2 Replies

P: n/a
On Jun 25, 2:09*pm, Terry Reedy <tjre...@udel.eduwrote:
John W. Hamill wrote:
C:\__jh\ftp\python\2_5_2\doc\tutorial\node11.html

When reporting doc bugs, it is a good idea to check the most recent
version. *The 3.0 version has the same problems (no changes have been
made -- page and graduates are still undefined), so report that too.
Changes to the 2.6 docs will be propagated to 3.0, so it's usually not
an issue.
Jun 27 '08 #2

P: n/a


Benjamin wrote:
On Jun 25, 2:09 pm, Terry Reedy <tjre...@udel.eduwrote:
>John W. Hamill wrote:
>>C:\__jh\ftp\python\2_5_2\doc\tutorial\node11.htm l
When reporting doc bugs, it is a good idea to check the most recent
version. The 3.0 version has the same problems (no changes have been
made -- page and graduates are still undefined), so report that too.

Changes to the 2.6 docs will be propagated to 3.0, so it's usually not
an issue.
Let me rephrase my comment. Because charges are so propagated, the
absence of change in 3.0 implies the absence of change in 2.6 (and
probably in the development version of 2.5.3.) Therefore, the bug has
not been fixed and it would be appropriate to report it.

When people report but based on older versions, it is not uncommon for
that they have already been fixed.

Jun 27 '08 #3

This discussion thread is closed

Replies have been disabled for this discussion.