fix winbot/py 2.4.4 bug

[bb-migration]

Originally reported by: agroszer (Bitbucket: agroszer, GitHub: agroszer)

---

http://winbot.zope.org/builders/setuptools_master%20py_244_win32/builds/2/steps/test/logs/stdio

ERROR: test_md5 (setuptools.tests.test_packageindex.TestContentCheckers)

Traceback (most recent call last):
File "c:\buildslave\setuptools_master_py_244_win32\build\setuptools\tests\test_packageindex.py", line 150, in test_md5
self.assertEqual(checker.hash.name, 'md5')
AttributeError: name

---

• Bitbucket: https://bitbucket.org/pypa/setuptools/issue/44

[bb-migration]

Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco):

---

It appears the hashlib backport doesn't implement the full API of the canonical hashlib module (not supplying the .name attribute). Thanks so much for running these tests on Python 2.4.

[bb-migration]

Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco):

---

Add compatibility for Python 2.4 when querying the hash name. Fixes #44

[bb-migration]

Original comment by agroszer (Bitbucket: agroszer, GitHub: agroszer):

---

welcome, FYI tests are run as "nightly" did not have the time yet to figure the change poller for hg

[bb-migration]

Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco):

---

Bitbucket also provides a 'POST' service, which can POST details about commits (and possibly other activity) to the service to trigger a build. If there's an endpoint at winbot.zope.org to consume that API, I'd be happy to have the BB repo trigger a build.

[bb-migration]

Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco):

---

I see the test is now passing. I'll release 0.9.6 shortly.

[bb-migration]

Original comment by dholth (Bitbucket: dholth, GitHub: dholth):

---

Set self.hash_name in init rather than using this function or relying on self.hash.name. Needed for pypy 1.9 as well as python 2.4.

[bb-migration]

Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco):

---

Python 2.4 issue was previously resolved. The PyPy issue was reported in #49.