➜

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 jaraco
Recipients KayEss, Rhamphoryncus, benjamin.peterson, blakeross, georg.brandl, gregory.p.smith, gvanrossum, jaraco, jcea, jonash, rhettinger, terry.reedy
Date 2013-01-14.21:08:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1358197719.48.0.82059947908.issue1683368@psf.upfronthosting.co.za>
In-reply-to
Content 
For reference, I encountered an issue due to this change and didn't quite understand what was going on. I distilled the problem down and posted a question on stack overflow:

http://stackoverflow.com/questions/14300153/why-does-this-datetime-subclass-fail-on-python-3/14324503#14324503

The answer led me here, so now I understand. I wanted to share this use-case for posterity.

I didn't find anything in the "what's new" documents for Python 3.3 or 3.0. Was this fundamental signature change to all objects documented anywhere? Any objection if I draft a change to the docs?
History
Date User Action Args
2013-01-14 21:08:39jaracosetrecipients: + jaraco, gvanrossum, georg.brandl, rhettinger, terry.reedy, gregory.p.smith, jcea, Rhamphoryncus, blakeross, benjamin.peterson, KayEss, jonash
2013-01-14 21:08:39jaracosetmessageid: <1358197719.48.0.82059947908.issue1683368@psf.upfronthosting.co.za>
2013-01-14 21:08:39jaracolinkissue1683368 messages
2013-01-14 21:08:39jaracocreate