pyRight configuration and its fixes #30
Open
Conversation
This file contains 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
…red files and provides necessary warnings
sbimochan
changed the title
kabirbaidhya
requested review from
amritghimire,
Basanta78,
sanjevShakya,
shakyapranin and
shradayshakya
kabirbaidhya
reviewed
Mar 4, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix pyRight configuration so that it checks for required files and provides necessary warnings.
This PR will surely not pass test in Travis. So I'd like to request everyone to checkout from this branch fix their import issues, type issues... and push on this PR.
Screenshots:
Before:
After the changes:
Next iteration after configuring venvPaths. Less and relevant warnings 💃
closes #29