Obsolete info in Tutorial 9.1

[kjohnson]

BPO	1067018
Nosy	@rhettinger, @terryjreedy

^{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 2004-11-18.06:22:10.000>
created_at = <Date 2004-11-15.22:50:42.000>
labels = ['docs']
title = 'Obsolete info in Tutorial 9.1'
updated_at = <Date 2004-11-18.06:22:10.000>
user = 'https://bugs.python.org/kjohnson'

bugs.python.org fields:

activity = <Date 2004-11-18.06:22:10.000>
actor = 'rhettinger'
assignee = 'none'
closed = True
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2004-11-15.22:50:42.000>
creator = 'kjohnson'
dependencies = []
files = []
hgrepos = []
issue_num = 1067018
keywords = []
message_count = 4.0
messages = ['23158', '23159', '23160', '23161']
nosy_count = 4.0
nosy_names = ['rhettinger', 'terry.reedy', 'jlgijsbers', 'kjohnson']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue1067018'
versions = ['Python 2.4']

[kjohnson]

In the Tutorial, section 9.1, the second paragraph
(starting with "I also have to warn you") is obsolete -
integers and list are now instances of <type 'int'> and
<type 'list'> if I understand correctly.

For a brief discussion on c.l.python see
http://groups.google.com/groups?hl=en&lr=&c2coff=1&threadm=ad052e5c.0411150401.2b215499%40posting.google.com&prev=/groups%3Fhl%3Den%26lr%3D%26ie%3DUTF-8%26c2coff%3D1%26group%3Dcomp.lang.python

Kent

[jlgijsbers]

Logged In: YES
user_id=469548

This isn't really obsolete, technically speaking. Types look
a lot more like classes since Python 2.2, but they're not
the same. I don't know whether we still want to introduction
in the tutorial, though, so I'm leaving this open for now.

[terryjreedy]

Logged In: YES
user_id=593130

Instances of builtin types were always just that.  So this is 
not new.  What is new in 2.2 (I think) is that they gained 
a .__class__ attribute pointing to the type.
>>> 1 .__class__
<type 'int'>

In addition, the builtin types, including type itself, are now
subclasses of object (via their __bases__ attribute), even
though their .__class__ attributes point to type instead.

>>> issubclass(int, object)
1
>>> int.__bases__
(<type 'object'>,)
>>> int.__class__
<type 'type'>

So I think the warning, as now written, is arguably untrue,
or at least confusing rather than helpful.

[rhettinger]

Logged In: YES
user_id=80475

Zapped the useless and confusing paragraph.