This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author amaury.forgeotdarc
Recipients amaury.forgeotdarc, farcat, glchapman, lorph, mwh
Date 2009-05-29.14:07:49
SpamBayes Score 0.00081927335
Marked as misclassified No
Message-id <1243606073.52.0.315275831496.issue672115@psf.upfronthosting.co.za>
In-reply-to
Content
Lars, I think that your question has a simple explanation, and is not
related to the original issue:
- On 4th line, the variable named "A" is bound to a new type object.
This type has no attribute by itself.
- The first dir(A) displays the attributes of the bases class, which are
the previous A and B: you see ['one', 'two']
- The second dir(A) displays the attributes of the bases class, which
are B and C: you see ['two', 'three']

The instruction "A = type(...)" causes A to refer to another object; it
does not change the object previously contained in A.
History
Date User Action Args
2009-05-29 14:07:53amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, mwh, glchapman, lorph, farcat
2009-05-29 14:07:53amaury.forgeotdarcsetmessageid: <1243606073.52.0.315275831496.issue672115@psf.upfronthosting.co.za>
2009-05-29 14:07:51amaury.forgeotdarclinkissue672115 messages
2009-05-29 14:07:50amaury.forgeotdarccreate