Extending int class

[jbvsmo]

BPO	12538
Nosy	@bitdancer, @jbvsmo

^{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 2011-07-11.21:07:53.043>
created_at = <Date 2011-07-11.20:26:03.135>
labels = ['interpreter-core', 'type-bug', 'invalid']
title = 'Extending int class'
updated_at = <Date 2011-07-11.21:07:53.032>
user = 'https://github.com/jbvsmo'

bugs.python.org fields:

activity = <Date 2011-07-11.21:07:53.032>
actor = 'r.david.murray'
assignee = 'none'
closed = True
closed_date = <Date 2011-07-11.21:07:53.043>
closer = 'r.david.murray'
components = ['Interpreter Core']
creation = <Date 2011-07-11.20:26:03.135>
creator = 'JBernardo'
dependencies = []
files = []
hgrepos = []
issue_num = 12538
keywords = []
message_count = 2.0
messages = ['140161', '140162']
nosy_count = 2.0
nosy_names = ['r.david.murray', 'JBernardo']
pr_nums = []
priority = 'normal'
resolution = 'not a bug'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue12538'
versions = ['Python 2.7', 'Python 3.2']

[jbvsmo]

I'm having trouble subclassing the int type and I think this behavior is a bug... (Python 3.2)

>>> class One(int):
	def __init__(self):
		super().__init__(1)

>>> one = One()
>>> one + 2
2
>>> one == 0
True

I know int objects are immutable but my One class should be mutable... and why it doesn't raise an error?

That gives the same result on Python 2.7 using super properly.

Also, if that's not a bug, how it should be done to achieve "one + 2 == 3" without creating another attribute.

Things I also tried:
self.real = 1 #readonly attribute error
int.__init__(self, 1) #same behavior

I Couldn't find any related issues... sorry if it's repeated.

[bitdancer]

To set the value of an immutable type you must use the __new__ method. By the time __init__ is called the value has already be established, and in the case of int it defaults to 0.