python / python/python-docs-theme

Issue URL on translated Python docs site is always pointed to English version

Open
#235 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
CSS
Stars
90
Forks
78
Avg merge
2d 19h
Merged PRs (30d)
4

Description

BPO 38427
Nosy @JulienPalard, @zhsj, @tirkarthi

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 = None
created_at = <Date 2019-10-10.06:00:23.007>
labels = ['3.8', 'docs']
title = 'Issue URL on translated Python docs site is always pointed to English version'
updated_at = <Date 2019-10-10.07:18:07.283>
user = 'https://github.com/zhsj'

bugs.python.org fields:

activity = <Date 2019-10-10.07:18:07.283>
actor = 'zhsj'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2019-10-10.06:00:23.007>
creator = 'zhsj'
dependencies = []
files = []
hgrepos = []
issue_num = 38427
keywords = []
message_count = 3.0
messages = ['354314', '354316', '354317']
nosy_count = 4.0
nosy_names = ['docs@python', 'mdk', 'zhsj', 'xtreak']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue38427'
versions = ['Python 3.8']

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue on a translated Python documentation page and trace how the theme generates its issue URL. Verify that the resulting link preserves the translated site's language instead of pointing to the English site, then check the relevant documentation behavior before and after the change.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
documentation
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.