10000 [MRG + 1] Fix 5663: string comparison on arrays in new Gaussian process by ziky90 · Pull Request #5701 · scikit-learn/scikit-learn · GitHub
[go: up one dir, main page]

Skip to content

[MRG + 1] Fix 5663: string comparison 8000 on arrays in new Gaussian process #5701

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

Merged
merged 2 commits into from
Feb 3, 2016

Conversation

ziky90
Copy link
Contributor
@ziky90 ziky90 commented Nov 3, 2015

This PR fixes the issue described in described in issue #5663

@ziky90 ziky90 changed the title Fixed string comparison on arrays in new Gaussian process Fix #5663: string comparison on arrays in new Gaussian process Nov 3, 2015
@ziky90 ziky90 changed the title Fix #5663: string comparison on arrays in new Gaussian process Fix 5663: string comparison on arrays in new Gaussian process Nov 3, 2015
fixed = (bounds == "fixed")
fixed = False
if isinstance(bounds, six.string_types) and bounds == "fixed":
fixed = True
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

or

fixed = isinstance(bounds, six.string_types) and bounds == "fixed"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're right I like one line more, so I'll change it your way, thanks.

@GaelVaroquaux
Copy link
Member

It would be really good to have a test, for instance derived from the original issue.

@ziky90
Copy link
Contributor Author
ziky90 commented Nov 3, 2015

@GaelVaroquaux
Ok that's a good idea, I'm working on that.

@amueller
Copy link
Member
amueller commented Nov 3, 2015

@GaelVaroquaux #5685 ;)

@ziky90
Copy link
Contributor Author
ziky90 commented Nov 4, 2015

@amueller Do I understand this correctly that I should not write tests for this? And instead warnings should be treated as errors?

@ziky90
Copy link
Contributor Author
ziky90 commented Nov 6, 2015

I'm just curious, should I add something before merge or is it ok like this?

@amueller
Copy link
Member

Yes, this is good to merge. This raises warnings, not errors, at the moment, so we can't really test. Well we could test that no warning is raised but that is a bit overkill, I think.

@amueller amueller changed the title Fix 5663: string comparison on arrays in new Gaussian process [MRG + 1] Fix 5663: string comparison on arrays in new Gaussian process Dec 11, 2015
ogrisel added a commit that referenced this pull request Feb 3, 2016
[MRG + 1] Fix 5663: string comparison on arrays in new Gaussian process
@ogrisel ogrisel merged commit 4ae03d1 into scikit-learn:master Feb 3, 2016
@ogrisel
Copy link
Member
ogrisel commented Feb 3, 2016

Thanks for the fix @ziky90!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants
0