-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Danb27/sar literal fix #1663
Danb27/sar literal fix #1663
Conversation
More information on the problem with using 'is': https://lerner.co.il/2015/06/16/why-you-should-almost-never-use-is-in-python/ |
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.
good catch!
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.
Great work!
hey @danb27 I have just realized that you haven't signed your commits, so your name won't appear on GitHub. If you want to keep contributing to the repo and that your name appears on it, you can sign your commits following: https://github.com/microsoft/recommenders/wiki/How-to-add-your-name-as-a-contributor-to-the-repo#make-sure-that-your-github-user-is-setup-correctly
|
Description
Change how the package checks for similarity type from 'is' to ==
This is more correct python code - check for the same value in the string using ==, avoids problems when unpacking parameters from other files using json package.
Related Issues
Checklist:
staging branch
and not tomain branch
.