Add precision argument to datetime.now
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
The issue targets the datetime.now entry point in Python's standard library, but names no implementation files or tests. Start by locating datetime.now and reviewing the linked BPO issue discussion to establish the intended precision semantics; done means the argument's behavior and compatibility expectations are clearly defined and covered by appropriate tests.
Written by the indexing model from the issue text.
Description
| BPO | 32522 |
|---|---|
| Nosy | @tim-one, @warsaw, @abalkin, @vstinner, @pganssle |
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 2018-01-09.15:46:50.654>
labels = ['3.7', '3.8', 'type-feature', 'library']
title = 'Add precision argument to datetime.now'
updated_at = <Date 2018-01-09.21:44:13.815>
user = 'https://github.com/pganssle'
bugs.python.org fields:
activity = <Date 2018-01-09.21:44:13.815>
actor = 'p-ganssle'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2018-01-09.15:46:50.654>
creator = 'p-ganssle'
dependencies = []
files = []
hgrepos = []
issue_num = 32522
keywords = []
message_count = 20.0
messages = ['309703', '309704', '309706', '309707', '309710', '309714', '309715', '309717', '309718', '309719', '309722', '309723', '309724', '309726', '309730', '309732', '309734', '309735', '309737', '309738']
nosy_count = 5.0
nosy_names = ['tim.peters', 'barry', 'belopolsky', 'vstinner', 'p-ganssle']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue32522'
versions = ['Python 3.7', 'Python 3.8']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
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.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100