DeprecationWarnings of implicitly truncations by __int__ appearing in the standard library
Open
Nobody has claimed this yet.
3.8 (EOL)
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 39015 |
|---|---|
| Nosy | @vstinner, @ambv, @serhiy-storchaka, @tirkarthi |
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-12-10.15:03:06.691>
labels = ['3.8', 'type-bug', 'library']
title = 'DeprecationWarnings of implicitly truncations by __int__ appearing in the standard library'
updated_at = <Date 2019-12-12.09:18:19.956>
user = 'https://github.com/ambv'
bugs.python.org fields:
activity = <Date 2019-12-12.09:18:19.956>
actor = 'serhiy.storchaka'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-12-10.15:03:06.691>
creator = 'lukasz.langa'
dependencies = []
files = []
hgrepos = []
issue_num = 39015
keywords = ['3.8regression']
message_count = 2.0
messages = ['358195', '358197']
nosy_count = 4.0
nosy_names = ['vstinner', 'lukasz.langa', 'serhiy.storchaka', 'xtreak']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'pending'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue39015'
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 files or tests are named. Start by locating standard-library code that implicitly truncates values through int and inspect the linked BPO issue for the intended behavior; done means the relevant deprecation warnings no longer appear without breaking Python 3.8 behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100