[doc] urllib.parse.parse_qsl different results after urllib.parse.unquote

Open
#66,808 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

Start by reading the documentation for urllib.parse.parse_qsl and urllib.parse.unquote, then review the migrated issue details and its four-message thread. The issue does not name a documentation file, example, or expected wording, so completion depends on clarifying the intended explanation of their differing results.

Written by the indexing model from the issue text.

Description

3.11 docs type-bug
BPO 22618
Nosy @orsenthil, @bitdancer

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 2014-10-12.13:56:21.327>
labels = ['3.11', 'type-bug', 'docs']
title = '[doc] urllib.parse.parse_qsl different results after urllib.parse.unquote'
updated_at = <Date 2021-11-28.13:08:56.784>
user = 'https://bugs.python.org/AlexVaystikh'

bugs.python.org fields:

activity = <Date 2021-11-28.13:08:56.784>
actor = 'iritkatriel'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2014-10-12.13:56:21.327>
creator = 'Alex.Vaystikh'
dependencies = []
files = []
hgrepos = []
issue_num = 22618
keywords = []
message_count = 4.0
messages = ['229144', '229156', '229157', '229169']
nosy_count = 4.0
nosy_names = ['orsenthil', 'r.david.murray', 'docs@python', 'Alex.Vaystikh']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue22618'
versions = ['Python 3.11']

Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

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.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.