ThomasH <[EMAIL PROTECTED]> added the comment: 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 <[EMAIL PROTECTED]> wrote: > > Georg Brandl <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> > <http://bugs.python.org/issue3324> > _______________________________________ > _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3324> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
