Incoherent type conversion in configparser
Open
Nobody has claimed this yet.
pending
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 35954 |
|---|---|
| Nosy | @taleinat, @ambv, @serhiy-storchaka, @remilapeyre |
| PRs |
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-02-10.12:28:34.481>
labels = ['type-bug', 'library', '3.9']
title = 'Incoherent type conversion in configparser'
updated_at = <Date 2019-06-09.15:54:16.996>
user = 'https://bugs.python.org/Adeokkuw'
bugs.python.org fields:
activity = <Date 2019-06-09.15:54:16.996>
actor = 'remi.lapeyre'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-02-10.12:28:34.481>
creator = 'Adeokkuw'
dependencies = []
files = []
hgrepos = []
issue_num = 35954
keywords = ['patch']
message_count = 7.0
messages = ['335150', '335151', '335830', '335852', '335900', '344904', '345085']
nosy_count = 5.0
nosy_names = ['taleinat', 'lukasz.langa', 'serhiy.storchaka', 'remi.lapeyre', 'Adeokkuw']
pr_nums = ['11918']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue35954'
versions = ['Python 3.9']
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
Start by reading the configparser implementation and its conversion-related tests, then review the historical discussion and PR python/cpython#11918. Done means the conversion behavior is made coherent and covered by tests, but the existing pull request and old activity indicate that this work may already be underway.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100