vulture: Adapt for internal API in versions 0.9+#182
Closed
smspillaz wants to merge 1 commit into
Closed
Conversation
Contributor
Author
|
Bump? This bug is pretty annoying - it means it is not possible to use vulture with prospector. |
|
Changes Unknown when pulling 95c506a on smspillaz:fix-180 into ** on landscapeio:develop**. |
Member
|
Finally dealt with this apologies but did so by merging #194 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Vulture now only sets self.unused_funcs etc to be the name
of the unused thing and does not specify a file or line. Not ideal
for us, but at least wrap it in something so that we get useful
error messages instead of "exception raised"
Fixes #180