-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
the check to make sure not --looponfail isn't working #1
Comments
|
I'm not sure what this stack trace has to do with --looponfail, but I have never used python 3.x. I would be happy to accept a PR for changes to make it work on 3.4, presuming that it doesn't break backwards compatibility with 2.x (as defined by passing tox runs). |
@klrmn What exaclty is meant by this issue? The topic alone doesn't help. |
i wish i remembered. i suggest you close it and wait until you / someone On Wed, May 20, 2015 at 11:12 PM, Florian Pilz notifications@github.com
|
No description provided.
The text was updated successfully, but these errors were encountered: