Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!nntp.club.cc.cmu.edu!micro-heart-of-gold.mit.edu!bloom-beacon.mit.edu!bloom-beacon.mit.edu!panix!gordon
From: John Gordon <gordon@panix.com>
Newsgroups: comp.lang.python
Subject: Re: hashlib suddenly broken
Date: Thu, 18 Sep 2014 16:47:59 +0000 (UTC)
Organization: PANIX Public Access Internet and UNIX, NYC
Lines: 17
Message-ID: <lvf2bv$j9q$1@reader1.panix.com>
References: <mailman.14109.1411057681.18130.python-list@python.org>
NNTP-Posting-Host: panix3.panix.com
X-Trace: reader1.panix.com 1411058879 19770 166.84.1.3 (18 Sep 2014 16:47:59 GMT)
X-Complaints-To: abuse@panix.com
NNTP-Posting-Date: Thu, 18 Sep 2014 16:47:59 +0000 (UTC)
User-Agent: nn/6.7.3
Xref: csiph.com comp.lang.python:78025

In <mailman.14109.1411057681.18130.python-list@python.org> Larry Martell <larry.martell@gmail.com> writes:

> Googling this showed that it's an issue with hashlib with a common
> cause being a file called hashlib.py that gets in the way of the
> interpreter finding the standard hashlib module, but that doesn't seem
> to be the case:

Perhaps hashlib imports some other module which has a local module of the
same name?

SHA1 has been deprecated for some time.  Maybe a recent OS update finally
got rid of it altogether?

-- 
John Gordon         Imagine what it must be like for a real medical doctor to
gordon@panix.com    watch 'House', or a real serial killer to watch 'Dexter'.