Fixed. The TypeError in this nonsense never gonna work use case is now consistent in 2.7, 3.2 and 3.3.
On Sun, 22 Jul 2012 01:05:35 -0000, =?iso-8859-1?Q?Kristj=E1n_Valur_J=F3nsson?= <kristjan@ccpgames.com> wrote:It is indeed, and we have been moving the unit tests to do exactly
> Indeed, shame on me for not mentioning this.
> I rarely have the full complement of externals available when I'm doing python work, and it struck me that this unitest was failing.
> I suppose it should be possible to write unittests that test more than one particular implementation.
that for the cases where there is a Python implementation as well as
a C implementation. It seems like it would be appropriate to open an
issue for doing that for hashlib, in addition to one for fixing this
particular issue with the Python version.
--David
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/greg%40krypto.org