You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are a few unusual builds in the Anaconda repository for Tensorflow (TF) 2.3 that seem to make the tensorflow-gpu 2.3 installation unable to function properly (see here).
For TF 2.1, conda search tensorflow=2.1 yields the following results:
These TF 2.3 builds do not follow the naming conventions of previous tensorflow builds (i.e., mkl_ prefix is only used for mkl versions). Moreover, for some of these tensorflow builds, their dependent _tflow_select options and tensorflow-base builds do not seem to match. Details of selected suspicious builds are shown in the following.
Yes, tensorflow 2.3.0 was broken in some aspects. We might revisit it, but I did now the upgrade to 2.4.1 and fixed along this all the issues we had for older tensorflow versions.
I uploaded to my private channel the rc for linux-64 for testing. Getting some feedback here would be nice.
Yes, tensorflow 2.3.0 was broken in some aspects. We might revisit it, but I did now the upgrade to 2.4.1 and fixed along this all the issues we had for older tensorflow versions.
I uploaded to my private channel the rc for linux-64 for testing. Getting some feedback here would be nice.
@katietz Great ! Where is your private channel? Will there be builds available for Windows?
There are a few unusual builds in the Anaconda repository for Tensorflow (TF) 2.3 that seem to make the
tensorflow-gpu
2.3 installation unable to function properly (see here).For TF 2.1,
conda search tensorflow=2.1
yields the following results:In contrast,
conda search tensorflow=2.3
yields the following:These TF 2.3 builds do not follow the naming conventions of previous tensorflow builds (i.e.,
mkl_
prefix is only used for mkl versions). Moreover, for some of thesetensorflow
builds, their dependent_tflow_select
options andtensorflow-base
builds do not seem to match. Details of selected suspicious builds are shown in the following.The text was updated successfully, but these errors were encountered: