New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
python 2.6.5 documentation can't search #52663
Comments
http://docs.python.org/release/2.6.5/search.html?q=regular+expression fails. It fails because http://docs.python.org/release/2.6.5/searchindex.js returns 404 NOT FOUND There are really two bugs here:
IMO the second one is more important: the page stays forever with the Searching and the dots moving... I reported against build and Documentation as I'm not sure if the web site belongs here and where is the issue originating. |
With FireFox, searching from http://docs.python.org/release/2.6.5/ Georg, I do not see a 2.6.6 page. Can you verify that it will work when released? |
I got this trying to reply: This is the mail system at host psf.upfronthosting.co.za. I'm sorry to have to inform you that your message could not For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can
<roundup+tracker@psf.upfronthosting.co.za> (expanded from Final-Recipient: rfc822; roundup+tracker@psf.upfronthosting.co.za ---------- Forwarded message ---------- Regards On Thu, Aug 5, 2010 at 9:41 PM, Terry J. Reedy <report@bugs.python.org> wrote:
|
The best way to reply to tracker messages is to click the link at the bottom and enter in the box. Pasting all that junk is useless. The noise hides the message, which seems to be a non-helpful repeat of the original message. I already did what was needed, which was to verify the problem and try to alert GB. Let him respond. |
Hi Georg, I've verified doc search works with 2.6.[467], so if the fix is so easy to just add that js, could you please give it a look? TIA |
Santiago, if you are still running 2.6.5 code, use the most recent 2.6 docs at George, since the continuously updated x.y docs released with x.y.z really document x.y and not each x.y.z bugfix release, I am a bit surprised that they are labelled x.y.z docs with the claim "This is the documentation for Python x.y.z", especially since they are updated after the x.y.z code release. The current '2.7.2' docs, last updated today, would more truthfully be called either '2.7' docs or '2.7.3a0' docs, as they are are a preview of what will be released with 2.7.3 and are not what was released with 2.7.2. If there *were* (unusally) any new features in 2.7.3a0, they would already be listed in the so-called '2.7.2' docs. (There *was* such a bugfix addition for difflib.SequenceMatcher in 2.7.1, and I presume it did appear in the updated '2.7.0' online docs.) I am not sure we should have obsolete snapshot versions online. They only serve to be an attractive nuisance as illustrated by this issue. With the initial 3.3 release being called 3.3.0, there would be no ambiguity in calling the 3.3 docs just that. |
Sorry, /George/Georg/ |
Still http://docs.python.org/release/2.6.6/search.html?q=regular+expression Regards On Wed, Jan 4, 2012 at 12:55 AM, Ezio Melotti <report@bugs.python.org> wrote:
|
The continually updated docs are built from the stable branches, whose version remains at (e.g.) 2.7.2 until 2.7.3a1 is released, at which point the continuous updating stops until 2.7.3 is final. I don't think presenting docs with an alpha version on the http://docs.python.org/ frontpage is useful. On the other hand, I do think it is important to have doc fixed reflected (more or less) instantly somewhere, so that e.g. people reporting typos can see the fixes. The status quo is a compromise between these two needs. When we do make backwards incompatible changes or additions during a stable cycle, they need to be marked with "new/changed in version 2.7.X+1" anyway. So the SequenceMatcher change would alert users itself. If not, that's a bug. About the "obsolete" snapshots: I don't know what you're referring to there: if it's the released docs for specific versions, then I think that's standard practice to have a doc version released for a specific Python version; and I wouldn't change that. |
searchindex.js is now present in 2.6.5 too. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: