Re: [pydotorg-www] Steering search engines and users away from 3.0/3.1 docs?

2016-11-03 Thread Skip Montanaro
On Thu, Nov 3, 2016 at 9:32 AM, M.-A. Lemburg wrote: > It's probably best to file a bug on > https://github.com/python/pythondotorg/issues > > or directly file a PR again: > > https://github.com/python/psf-salt/blob/master/salt/docs/ > config/nginx.docs-backend.conf > Thanks for the pointers, MA

Re: [pydotorg-www] Steering search engines and users away from 3.0/3.1 docs?

2016-11-03 Thread M.-A. Lemburg
On 03.11.2016 15:22, Skip Montanaro wrote: > Should I open a ticket on some issue tracker so this doesn't get lost? > bugs.python.org seems wrong (language, not website), and mail to > d...@python.org seems to be related to the documentation itself, not the > mechanics of its presentation through t

Re: [pydotorg-www] Steering search engines and users away from 3.0/3.1 docs?

2016-11-03 Thread Skip Montanaro
Should I open a ticket on some issue tracker so this doesn't get lost? bugs.python.org seems wrong (language, not website), and mail to d...@python.org seems to be related to the documentation itself, not the mechanics of its presentation through the web. Skip _

Re: [pydotorg-www] Steering search engines and users away from 3.0/3.1 docs?

2016-11-01 Thread tritium-list
engines and users away from 3.0/3.1 docs? Tweaking robots.txt seems like the simplest route. It would be nice if /3.[01]/index.html where visible through search engines but not anything underneath. I don't recall if robots.txt is a sharp enough tool to make that distinction. Followi

Re: [pydotorg-www] Steering search engines and users away from 3.0/3.1 docs?

2016-11-01 Thread Skip Montanaro
Tweaking robots.txt seems like the simplest route. It would be nice if /3.[01]/index.html where visible through search engines but not anything underneath. I don't recall if robots.txt is a sharp enough tool to make that distinction. Following my original thought a bit further, I wondered how far

Re: [pydotorg-www] Steering search engines and users away from 3.0/3.1 docs?

2016-10-31 Thread M.-A. Lemburg
On 31.10.2016 19:42, Skip Montanaro wrote: > Not quite sure where this should go, so I'll start here. > > I needed to look up a bit more information about the timeit module than I > happened to be carrying around in my noggin just now, so I asked Google to > tell me about "Python timeit". The firs

Re: [pydotorg-www] Steering search engines and users away from 3.0/3.1 docs?

2016-10-31 Thread Steve Holden
Good place to start. So, not acceptable because 3.0 rather than 3, right, and therefore not the current version? I could imagine a system whereby any reference to older versions was redirected to current if the source is a search engine. This should only be implemented for pages that can be versio

[pydotorg-www] Steering search engines and users away from 3.0/3.1 docs?

2016-10-31 Thread Skip Montanaro
Not quite sure where this should go, so I'll start here. I needed to look up a bit more information about the timeit module than I happened to be carrying around in my noggin just now, so I asked Google to tell me about "Python timeit". The first three hits were: https://docs.python.org/2/library