ConfigParser calls Interpolation.before_read after reading
Open
Nobody has claimed this yet.
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 29333 |
|---|---|
| Files | BasicInterpolation and a subclass of ConfigParser which in concert allow recursive interpolation. |
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 2017-01-20.11:50:36.038>
labels = ['type-bug', 'library']
title = 'ConfigParser calls Interpolation.before_read after reading'
updated_at = <Date 2017-01-25.13:32:16.094>
user = 'https://bugs.python.org/Anaphory'
bugs.python.org fields:
activity = <Date 2017-01-25.13:32:16.094>
actor = 'Anaphory'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-01-20.11:50:36.038>
creator = 'Anaphory'
dependencies = []
files = ['46355']
hgrepos = []
issue_num = 29333
keywords = []
message_count = 1.0
messages = ['285902']
nosy_count = 1.0
nosy_names = ['Anaphory']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue29333'
versions = ['Python 3.5', 'Python 3.6']
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 attached earlyinterpolation.py module and the ConfigParser and Interpolation.before_read behavior described in the issue. Trace when before_read is called relative to value reading, then identify the expected timing and add coverage demonstrating that behavior; no specific existing test file is named.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100