chore: get rid of warnings#1
Open
0xricksanchez wants to merge 1 commit into
Open
Conversation
chore: get rid of warnings
0xricksanchez
force-pushed
the
fix_warnings
branch
from
2d12f4c to
bf17b40
Compare
|
this needs to be merged in lol |
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
2 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.
Just cleaned up the warnings with the
invalid escape-sequences and ranblackas a code-formatter on it, which cleans up some small things. Changes of interest are those at the end of the main__init__.py.Warnings that will be removed: