New type based on int() created with typing.NewType is not consistent

[avanov]

BPO	33170
Nosy	@avanov

^{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 = <Date 2018-03-28.15:21:36.743>
created_at = <Date 2018-03-28.14:51:28.263>
labels = ['library']
title = 'New type based on int() created with typing.NewType is not consistent'
updated_at = <Date 2018-03-28.15:21:36.742>
user = 'https://github.com/avanov'

bugs.python.org fields:

activity = <Date 2018-03-28.15:21:36.742>
actor = 'avanov'
assignee = 'none'
closed = True
closed_date = <Date 2018-03-28.15:21:36.743>
closer = 'avanov'
components = ['Library (Lib)']
creation = <Date 2018-03-28.14:51:28.263>
creator = 'avanov'
dependencies = []
files = []
hgrepos = []
issue_num = 33170
keywords = []
message_count = 3.0
messages = ['314598', '314604', '314607']
nosy_count = 1.0
nosy_names = ['avanov']
pr_nums = []
priority = 'normal'
resolution = 'rejected'
stage = 'resolved'
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue33170'
versions = ['Python 3.6']

[avanov]

From my understanding of the docs section on new types, https://docs.python.org/3/library/typing.html#newtype the new type based on
int() should just pass the value into the base constructor. However,

PercentDiscount = NewType('PercentDiscount', int)

>>> PercentDiscount(50) == int(50)
True

>>> int('50') == int(50)
True

>>> PercentDiscount('50') == PercentDiscount(50)
False

[avanov]

Logically, I would expect it to behave similarly to

>>> class PercentDiscount(int): pass

>>> PercentDiscount('50') == PercentDiscount(50)
True

[avanov]

Ok, after further reading, I see that NewType creates an identity stub.