This repository was archived by the owner on Jun 2, 2025. It is now read-only.
add kwargs argument as a workaround to ignore boolean_number arguments#365
Open
adrian-forest wants to merge 1 commit intoWASasquatch:mainfrom
Open
add kwargs argument as a workaround to ignore boolean_number arguments#365adrian-forest wants to merge 1 commit intoWASasquatch:mainfrom
adrian-forest wants to merge 1 commit intoWASasquatch:mainfrom
Conversation
…ore boolean_number arguments passed to the function
Collaborator
|
This may not be needed now as per 7fb0766 |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
add kwargs argument as a workaround to ignore boolean_number arguments passed to the function
I encountered and reported #364 . This change seems to avoid this error on my local.
I know that this is BAD CODE! I'm a .NET developer by trade, but I could navigate python enough to identify this workaround, but I also know enough to assume it's VERY BAD and DOES NOT ACTUALLY SOLVE THE PROBLEM. However, this does avoid the error on my local, so far as I can tell, and I'm hoping maybe a PR might prompt somebody to make a proper fix?
Honestly, this is my first time making a PR to a public repo, so please be nice?