python / python/cpython

Ambiguous datetime comparisons should use == rather than 'is' for tzinfo comparison

Open
#72,787 2 comments 0 reactions 1 assignee View on GitHub

@abalkin is already working on this.

Since Nov 3, 2016.

3.7 (EOL) stdlib type-bug
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 28601
Nosy @tim-one, @abalkin, @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 = 'https://github.com/abalkin'
closed_at = None
created_at = <Date 2016-11-03.18:37:19.485>
labels = ['3.7', 'type-bug', 'library']
title = "Ambiguous datetime comparisons should use == rather than 'is' for tzinfo comparison"
updated_at = <Date 2016-11-03.18:46:38.618>
user = 'https://github.com/pganssle'

bugs.python.org fields:

activity = <Date 2016-11-03.18:46:38.618>
actor = 'belopolsky'
assignee = 'belopolsky'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2016-11-03.18:37:19.485>
creator = 'p-ganssle'
dependencies = []
files = []
hgrepos = []
issue_num = 28601
keywords = []
message_count = 2.0
messages = ['280003', '280005']
nosy_count = 3.0
nosy_names = ['tim.peters', 'belopolsky', 'p-ganssle']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue28601'
versions = ['Python 3.6', 'Python 3.7']

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.