-
Notifications
You must be signed in to change notification settings - Fork 174
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
Support more kinds of mypy messages #343
Conversation
The Some options:
@chocoelho Do you have any preference on how to move forward here? |
Can you point the PR to develop? We might still have chance to ship it in 1.1.7 and before that have a 1.1.7.dev1. |
That's done. Any opinion on how to pass tests? |
@rik can you try updating .travis.yml install option to add mypy? Prob worth moving line 17 into 13 in this file and install only once. |
8ca9e4c
to
387b025
Compare
1 similar comment
The 2.7 failure seems to be https://sourceforge.net/p/docutils/bugs/365/. |
@carlio as Python 2 support is being handled in https://github.com/landscapeio/prospector2 and discussed in here #265, do you think it makes sense dropping it from TravisCI? |
So docutils has been fixed but the 2.7 build is still failing because |
@chocoelho ahem "handled" I had largely ignored it :-) but yes the idea was that prospector is py3 only as of that point and prospector2 will deal with anyone stuck using 2. |
@rik there are two approaches we can take here:
|
Extracts a `format_message` to help unit testing fix prospector-dev#339
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
Thanks for the contribution, will add you to the contributors list in develop branch.
Thanks for maintaining this very useful tool! |
You're welcome! We just published |
Extracts a
format_message
to help unit testingfix #339