Add more fields to sys.float_info

Open
#85,989 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start with the sys.float_info entry point named in the issue and review linked PRs gh-146400 and gh-150219 to determine the current state of the work. The issue does not specify which fields to add or name implementation files or tests, so completion criteria must be clarified before starting.

Written by the indexing model from the issue text.

Description

extension-modules tests type-feature
BPO 41823
Nosy @tim-one, @rhettinger, @mdickinson, @corona10

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-09-21.01:01:54.389>
labels = ['extension-modules', '3.10']
title = 'Add more fields to sys.float_info'
updated_at = <Date 2020-09-23.01:40:17.721>
user = 'https://github.com/rhettinger'

bugs.python.org fields:

activity = <Date 2020-09-23.01:40:17.721>
actor = 'rhettinger'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Extension Modules']
creation = <Date 2020-09-21.01:01:54.389>
creator = 'rhettinger'
dependencies = []
files = []
hgrepos = []
issue_num = 41823
keywords = []
message_count = 5.0
messages = ['377237', '377256', '377284', '377341', '377353']
nosy_count = 4.0
nosy_names = ['tim.peters', 'rhettinger', 'mark.dickinson', 'corona10']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue41823'
versions = ['Python 3.10']

Linked PRs
  • gh-146400
  • gh-150219
Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.