Log file Viewer

[02:29:55] <Ivo__> dstufft: maybe you'd like to give an example for Guido? seems or a good thing to make sure python doesn't get wrong... https://groups.google.com/forum/m/#!msg/python-tulip/s1XIfj9-H1k/ZT3B8Sj57qAJ

[04:06:12] <meltingwax> /wc

[04:48:24] <voidpirate> hey lads and gents - I am interested in contributing to warehouse, could someone point me in the right direction?

[04:51:49] <tomprince> voidpirate: I suspect people who could are asleep. But if you hang around, you'll probably get an answer.

[04:52:42] <voidpirate> sure thing i'll stick around. Reviewing the docs and contributing guidelines atm.

[21:32:29] <jaraco> Arfrever, I'm just now reading your message from earlier.

[21:34:18] <jaraco> You ask why 'None' is allowed to be passed to unittest.main. I had looked at Python 2.7 and 3.4 and saw that None was interpreted to mean "not specified". I didn't look into Python 2.6/3.1 to see what interpretation None would have for testRunner.

[21:35:20] <jaraco> Your patch would solve that, but it probably goes too far - test_loader can never be None, so there's no need to check.

[21:36:02] <jaraco> I'm inclined instead to write a 'compat' wrapper to support Python 2.6/3.1 such that when those versions are no longer supported, the compatibilty wrapper can be removed.

[22:33:57] <pmxbot> jaraco pushed 1 commit to setuptools (https://bitbucket.org/pypa/setuptools/) :

[22:33:57] <pmxbot> Wrap unittest.main in a compatibility wrapper for Python 3.1 compatibility. Fixes #183

[22:36:46] <pmxbot> jaraco pushed 2 commits to setuptools (https://bitbucket.org/pypa/setuptools/) :

[22:36:46] <pmxbot> Added tag 3.4.2 for changeset 369f6f90f696

[22:36:46] <pmxbot> Bumped to 3.4.3 in preparation for next release.