Invalid escape sequence DeprecationWarnings don't trigger by default
Open
Nobody has claimed this yet.
3.10
3.11
3.9 (EOL)
interpreter-core
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 40199 |
|---|---|
| Nosy | @terryjreedy, @ncoghlan, @vstinner, @serhiy-storchaka, @Numerlor, @snoopjedi |
| Files |
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 2020-04-05.20:29:24.208>
labels = ['interpreter-core', 'type-bug', '3.9', '3.10', '3.11']
title = "Invalid escape sequence DeprecationWarnings don't trigger by default"
updated_at = <Date 2021-06-03.18:25:46.751>
user = 'https://github.com/Numerlor'
bugs.python.org fields:
activity = <Date 2021-06-03.18:25:46.751>
actor = 'SnoopJeDi'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2020-04-05.20:29:24.208>
creator = 'Numerlor'
dependencies = []
files = ['50091']
hgrepos = []
issue_num = 40199
keywords = []
message_count = 9.0
messages = ['365825', '365826', '365832', '366150', '366151', '366191', '394913', '394933', '395030']
nosy_count = 7.0
nosy_names = ['terry.reedy', 'ncoghlan', 'vstinner', 'habnabit', 'serhiy.storchaka', 'Numerlor', 'SnoopJeDi']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue40199'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']
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 with the issue title and the attached gdb_deprecationwarning_session.txt session to understand the reported interpreter behavior. Then locate the relevant Python interpreter warning path and existing tests; done means reproducing the invalid-escape case and confirming the intended default DeprecationWarning behavior with regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100