Closed hugovk closed 9 years ago
@hugovk, any ideas how this can be fixed?
@skudriashev Looks like you've already done it :)
https://github.com/mahmoudimus/nose-timer/commit/d78b845c11343bf7c7d8e844a3e22607759fb1ad
@skudriashev Any chance of a new release of nose-timer to include these fixes?
Version 0.4.3 on PyPI still hangs: https://travis-ci.org/hugovk/Pillow/builds/61051050
But the git version passes: https://travis-ci.org/hugovk/Pillow/builds/61215260
Thank you!
@hugovk Could you, please, give me an example of how to reproduce the behavior? Without coverage, just nose command, so I can look into this.
@skudriashev No need to look into it, just release :)
The latest master passes with the fixes made on 8 Dec 2014, but the last (four) releases were on 2 Dec 2014.
To release, just git tag and push and we should automatically get a publish on pypi
On Tue, May 5, 2015 at 5:12 AM, Hugo notifications@github.com wrote:
@skudriashev https://github.com/skudriashev No need to look into it, just release :)
The latest master passes with the fixes made ion Dec 8, 2014, but the last (four) releases were on 2 Dec 2014.
— Reply to this email directly or view it on GitHub https://github.com/mahmoudimus/nose-timer/issues/51#issuecomment-99063223 .
@hugovk new version released, please check.
I've rebuilt https://travis-ci.org/hugovk/Pillow/builds/61051050 and PyPy3 and Python 3.2 now pass.
Thank you!
See https://travis-ci.org/hugovk/nose-timer/builds/42836302 and https://travis-ci.org/mahmoudimus/nose-timer/builds/42836459
This prevents nose-timer being used on projects which need to support PyPy3 and Python 3.2.