-
Notifications
You must be signed in to change notification settings - Fork 78
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
Will be better if removing tensorflow prerequisite? #42
Comments
A very good question. Apart from the slow downloading due to the large size, TensorFlow as a requirement has other issues, too. Say in m1 mac, the package name is tensorflow-macos, which can lead to installation failure of tensorcircuit silently. However, there are several reasons that support the inclusion of tensorflow as a requirement,
Still, to remove or not to remove tf as a requirement, is an question to me. Not sure which side is better, and would love to listen to more feedbacks. |
For the second point, how about changing the installation guide to the following lines?
I suppose it will not be less friendly for new users. |
And I am also curious about whether it would be convenient for us to re-implement those utilities by uniform API of |
For now, my preference is to try something like below in furture releases |
It is more than welcome if anyone wants to make these utilities backend agnostic, which is a good first issue. These methods are in tensorcircuit/tensorcircuit/quantum.py Lines 1108 to 1388 in 41f0254
|
closed, as the remaining issue is separately open in #161 |
Since
tensorcircuit
does not rely on any specific backends, I wonder if it will be better to removetensorflow
from prerequisites, whose binaries are rather big (~500MB).The text was updated successfully, but these errors were encountered: