Skip to content

Restrict Google search to docs when in the docs subtree? #45559

Closed

Description

@smontanaro
BPO 1218
Nosy @loewis, @smontanaro

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:

assignee = None
closed_at = <Date 2008-01-06.15:31:34.692>
created_at = <Date 2007-09-27.19:27:17.151>
labels = ['type-bug', 'invalid', 'docs']
title = 'Restrict Google search to docs when in the docs subtree?'
updated_at = <Date 2008-01-06.15:31:34.692>
user = 'https://github.com/smontanaro'

bugs.python.org fields:

activity = <Date 2008-01-06.15:31:34.692>
actor = 'georg.brandl'
assignee = 'none'
closed = True
closed_date = <Date 2008-01-06.15:31:34.692>
closer = 'georg.brandl'
components = ['Documentation']
creation = <Date 2007-09-27.19:27:17.151>
creator = 'skip.montanaro'
dependencies = []
files = []
hgrepos = []
issue_num = 1218
keywords = []
message_count = 4.0
messages = ['56179', '56185', '56191', '56195']
nosy_count = 2.0
nosy_names = ['loewis', 'skip.montanaro']
pr_nums = []
priority = 'normal'
resolution = 'not a bug'
stage = None
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue1218'
versions = []

Activity

  1. smontanaro commented on Sep 27, 2007

    @smontanaro
    ContributorAuthor

    It was reported to webmaster@python.org today that Thomas Heller's
    pyhelp.cgi script is not available (yields 403 Forbidden). For the
    time being I removed that link from http://www.python.org/doc/.
    Still, there is the Google search box at the top of the page. Alas,
    that only restricts the search to www.python.org. It would be nice if
    on those pages under the /doc/... tree the relevant parameter
    (sitesearch?) restricted the search to the doc tree. Can this be done
    easily?

    (On a related note, shouldn't the website be listed as a separate
    component in the classification section?)

  2. added
    docsDocumentation in the Doc dir
    type-bugAn unexpected behavior, bug, or error
    on Sep 27, 2007
  3. loewis commented on Sep 28, 2007

    loewismannequin
    Mannequin

    Website issues are not tracked in this tracker. See

    http://wiki.python.org/moin/PythonWebsiteCreatingNewTickets

  4. smontanaro commented on Sep 28, 2007

    @smontanaro
    ContributorAuthor

    Martin> Website issues are not tracked in this tracker. See
    Martin> http://wiki.python.org/moin/PythonWebsiteCreatingNewTickets

    Is there some reason at this point that we need to maintain two separate
    trackers? A ton of work went into making our Roundup instance what the key
    players wanted. Why not use it to track website issues as well? With them
    separate you have two communities of maintainers and triage folks who are
    mostly disjoint.

    I assume there would be some trac-to-roundup conversion necessary. Perhaps
    something like that already exists.

    Skip

  5. loewis commented on Sep 28, 2007

    loewismannequin
    Mannequin

    Is there some reason at this point that we need to maintain two separate
    trackers?

    I don't know - I explained what is, not what should be. Whether or not
    pydotorg people want to use the tracker, I can't tell.

    Regards,
    Martin

  6. transferred this issue fromon Apr 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    docsDocumentation in the Doc dirtype-bugAn unexpected behavior, bug, or error

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions