-
Notifications
You must be signed in to change notification settings - Fork 1k
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
AttributeError when calling fmin with trials. #234
Comments
in package init.py line 20 |
in package base.py line 624 and 625,I just modified it as follows: |
I tried both of these approaches, however the error is still the same. AttributeError: 'function' object has no attribute 'fmin' |
In package base.py line 625 write fmin_module() instead of fmin_module.fmin(). |
got the same error. ghost's solution works. thanks! |
@ghost solution works for me as well. |
Still unfixed in the master branch :S |
I think base.py is still not changed in the 0.03dev version. |
I've got the same bug and fixed it via the ghost solution |
Fix from ghost: hyperopt#234 (comment)
I think this may differ between python3 and python2, the fix that was committed broke it for one, then reverting it broke the other again. The problem is that the fmin function is imported into the hyperopt package namespace, but there's also an fmin module underneath that package. (The Under python3 this seems to fix it for me, and is less ambiguous:
Not able to check it easily under python2 right now but perhaps someone else could check? |
I used ghost's solution, now I get: According to the api, the module bson do have ab Attribute BSON, so I'm a little bit confused. |
@mancap314 did you resolve the issue? |
I've added the following code and it works, BUT I don't know the side effects of this. from hyperopt import base
base.have_bson = False |
I've fixed this issue by uninstall bson. |
I get the following error when calling fmin. It only occurs when I specify a trials object, otherwise it runs just fine. I'm on ubuntu 14.04 using python 3.4.
The text was updated successfully, but these errors were encountered: