Skip to content
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

tensorflow 2.1 doesn't require separate pip installes for gpu and cpu #39

Closed
faroit opened this issue Jan 28, 2020 · 8 comments
Closed

Comments

@faroit
Copy link

faroit commented Jan 28, 2020

Thanks for this great package! We love to use it!

You state

Because Tensorflow comes in CPU-only and GPU variants, we leave it up to the user to install the version that best fits their usecase.

This is not the case anymore in 2.1 so you could (if 2.1 is supported) make tensorflow part of the standard requirements.

@auroracramer
Copy link
Collaborator

Thanks for your interest! :)

Currently, the most recent version supports Tensorflow 1.0 versions. We haven't explicitly looked at 2.0 (and 2.1) versions yet, but if or when we decide to drop support for 1.0 then we can explicitly add the requirement.

@faroit
Copy link
Author

faroit commented Feb 5, 2020

@jtcramer sure. feel free to close this then

@happypanda5
Copy link

@jtcramer and @faroit : I tried using it with tensorflow 2.1 on Colab and it gave me a compatibility error.

Note that pip install tensorflow installs tensorflow2.1 now, maybe force it to be pip install tensorflow==1.14.0

@justinsalamon
Copy link
Collaborator

@jtcramer we should update the instructions in the readme per^^

@happypanda5
Copy link

FYI: @justinsalamon @jtcramer pip install openl3 is now force installing tf2.0, even though I had first pip install tensorflow==1.14.0 before pip install openl3

My previous openl3 installation (based on pip install openl3) from 9 days ago still works fine.

@justinsalamon
Copy link
Collaborator

Thanks @happypanda5 for the heads up, we'll look into this as soon as we can.

@auroracramer
Copy link
Collaborator

Per offline discussion with @justinsalamon, we'll plan on updating the dependencies to ensure that keras < 2.3.0 (2.3.0 uses TF 2.0) and add a note to the README that TF 2.* is not yet supported and make a v0.3.1 release. We'll aim to move to TF 2.0 (and thus tf.keras) in a future release at some point.

@auroracramer auroracramer self-assigned this Feb 27, 2020
@auroracramer auroracramer added bug Something isn't working and removed bug Something isn't working labels Feb 27, 2020
@auroracramer auroracramer removed their assignment Feb 27, 2020
@auroracramer
Copy link
Collaborator

Closing this issue, follow #42 for more on the installation problems.

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

No branches or pull requests

4 participants