| msg69462 - (view) |
Author: (ThomasH) |
Date: 2008-07-09 11:32 |
| The page http://docs.python.org/inst/search-path.html contains a broken link to site module documentation. Is: http://www.python.org/doc/devel/lib/module-site.html Should be: http://docs.python.org/lib/module-site.html |
|
|
| msg69593 - (view) |
Author: Benjamin Peterson (benjamin.peterson) *  |
Date: 2008-07-12 18:49 |
| This has been fixed in the development docs: http://docs.python.org/dev/install/index.html |
|
|
| msg69718 - (view) |
Author: (ThomasH) |
Date: 2008-07-15 21:06 |
| What? You have fixed it in some development version, and left the current online version broken? How much can it take to fix a broken link on a web page? If that's the net effect, I shouldn't have gone through all the efforts of filing this issue! Rather than closing the bug somebody should have asked the question how broken links can creep into the Python web site at all, and how to prevent this situation from re-occurring. |
|
|
| msg69726 - (view) |
Author: Benjamin Peterson (benjamin.peterson) * |
Date: 2008-07-15 23:05 |
| For Python 2.6 and 3.0, we have transitioned over from LaTex to a new document format, reST. For this reason, we are not backporting fixes to the docs. However, when 2.7 and 3.1 become the development focus, we will again backport fixes. I'm sorry for the misunderstanding and thank you for your time. |
|
|
| msg69745 - (view) |
Author: Georg Brandl (georg.brandl) * |
Date: 2008-07-16 01:44 |
| In addition to what Benjamin said, the Python docs are released together with the source, so even if the issue was corrected in the 2.5 docs now, the correction would not show up until 2.5.3 is released, which is not even planned before 2.6. |
|
|
| msg69768 - (view) |
Author: (ThomasH) |
Date: 2008-07-16 08:29 |
| Thank you for both of your feedback. I was sure that there is a release and deployment process in place for the docs. But if the process doesn't allow links to be fixed on a web page, there is probably something wrong with it. It's hard to believe you would leave such a trivial thing unfixed, accepting hundreds or thousands of people running into a dead end. Don't you run a link checker on the online version? Does anybody check the web server logs for misses? It's also hard to understand why you would treat a (flexible) online presentation like (inflexible) released software. At the very least, could you fix the existing link (http://www.python.org/doc/devel/lib/module-site.html), which is seemingly a development URL, to redirect to the correct page?! Or does this also interfer with policies and procedures?! "Essence over ceremony" (after Neil Ford) On Wed, Jul 16, 2008 at 3:44 AM, Georg Brandl <report@bugs.python.org> wrote: > > Georg Brandl <georg@python.org> added the comment: > > In addition to what Benjamin said, the Python docs are released together > with the source, so even if the issue was corrected in the 2.5 docs now, > the correction would not show up until 2.5.3 is released, which is not > even planned before 2.6. > > _______________________________________ > Python tracker <report@bugs.python.org> > <http://bugs.python.org/issue3324> > _______________________________________ > |
|
|
| msg69902 - (view) |
Author: Georg Brandl (georg.brandl) * |
Date: 2008-07-17 20:03 |
| I've backported the fix to the 2.5 branch. This will go live with the release of 2.5.3. For those who do not want to use the released documentation we do offer the 2.6 documentation under development under http://docs.python.org/dev -- it is very usable for 2.5 too, since anything new in 2.6 will be clearly marked as such. When 2.6 is released, handling of the docs will be different in any case, since comments and change suggestions will be possible and handled in a timely manner, I hope. |
|
|