Consider quoting all values in Morsel objects
Open
Nobody has claimed this yet.
3.8 (EOL)
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 33535 |
|---|---|
| Nosy | @alex, @berkerpeksag, @serhiy-storchaka, @markrwilliams |
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 2018-05-16.08:15:36.847>
labels = ['3.8', 'type-feature', 'library']
title = 'Consider quoting all values in Morsel objects'
updated_at = <Date 2018-05-16.08:36:13.178>
user = 'https://github.com/berkerpeksag'
bugs.python.org fields:
activity = <Date 2018-05-16.08:36:13.178>
actor = 'serhiy.storchaka'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2018-05-16.08:15:36.847>
creator = 'berker.peksag'
dependencies = []
files = []
hgrepos = []
issue_num = 33535
keywords = []
message_count = 1.0
messages = ['316781']
nosy_count = 4.0
nosy_names = ['alex', 'berker.peksag', 'serhiy.storchaka', 'Mark.Williams']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'test needed'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue33535'
versions = ['Python 3.8']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No implementation files or tests are named in the issue. Start by locating the Python standard-library implementation and tests for Morsel objects, then inspect how values are currently rendered and quoted. Done means the intended quoting behavior is implemented consistently for all values and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100