-
Notifications
You must be signed in to change notification settings - Fork 260
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
Dependency on both backends in requirements.txt switches off GPU support #332
Comments
Theano is the only backend for nolearn, whereas keras has several backends. This is why it makes sense to install the backend with nolearn but not with keras.
I don't see why that should be the case, I never had this problem. Regardless, you should consider using virtual environments (if you don't already do so) to prevent python libraries from overriding your global installs. |
Please note that the 0.8 version of Theano you are forcing us to use is not only CPU-only, but also extremely old (in fact more than 2 years old, see Theano release history).
Latest version (Theano is an abandoned project): It is also not true that there is only one dependency - see requirements.txt:
By your own admission - if it has several backends, it does not make sense to install these backends. |
I don't think you understand, Lasagne and Theano are not separate backends, Lasagne strictly depends on Theano.
This is the version required by Lasagne, a higher version would probably not work well with it.
Why should this be CPU only? Older Theano should still work on GPU. If you really want to, edit the setup.py yourself or try to upgrade Theano to 1.0 after installing nolearn.
nolearn has more than one dependency, yes, but that has nothing to do with your arguments. These requirements are all needed for nolearn to work.
Nowhere did I say this. |
Currently nolearn has a dependency on both Theano and Lasagne, which forces installation of CPU-only versions, overriding the GPU-enabled builds we might have already installed before. See how Keras setup does not force any of its backends as its requirements and please consider removing these dependencies from your requirements.txt.
The text was updated successfully, but these errors were encountered: