Release new version that's compatible with `tfx[kfp]==1.10.0`
See original GitHub issueCurrently master branch has Depends on tensorflow>=1.15.5,<2 or tensorflow>=2.10,<2.11
from this commit. But this isn’t released yet.
Here’s a minimal repro of the dependency conflicts with tfx[kfp]==1.10.0
.
❯ cat requirements.in
tfx[kfp]==1.10.0
tensorflow-ranking
❯ pip-compile requirements.in
Could not find a version that matches tensorflow!=2.0.*,!=2.1.*,!=2.2.*,!=2.3.*,!=2.4.*,!=2.5.*,!=2.6.*,!=2.7.*,!=2.8.*,<2.10,<3,>=1.15.5,>=2.10.0 (from tfx[kfp]==1.10.0->-r requirements.in (line 1))
Tried: 2.2.0, 2.2.1, 2.2.2, 2.2.3, 2.3.0, 2.3.1, 2.3.2, 2.3.3, 2.3.4, 2.4.0, 2.4.1, 2.4.2, 2.4.3, 2.4.4, 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.6.0, 2.6.1, 2.6.2, 2.6.3, 2.6.4, 2.6.5, 2.7.0, 2.7.1, 2.7.2, 2.7.3, 2.7.4, 2.8.0, 2.8.1, 2.8.2, 2.8.3, 2.9.0, 2.9.1, 2.9.2, 2.10.0
Skipped pre-versions: 2.6.0rc0, 2.6.0rc1, 2.6.0rc2, 2.7.0rc0, 2.7.0rc1, 2.8.0rc0, 2.8.0rc1, 2.9.0rc0, 2.9.0rc1, 2.9.0rc2, 2.10.0rc0, 2.10.0rc1, 2.10.0rc2, 2.10.0rc3, 2.11.0rc0, 2.11.0rc1
There are incompatible versions in the resolved dependencies:
tensorflow!=2.0.*,!=2.1.*,!=2.2.*,!=2.3.*,!=2.4.*,!=2.5.*,!=2.6.*,!=2.7.*,!=2.8.*,<3,>=1.15.5 (from tfx-bsl==1.10.1->tfx[kfp]==1.10.0->-r requirements.in (line 1))
tensorflow!=2.0.*,!=2.1.*,!=2.2.*,!=2.3.*,!=2.4.*,!=2.5.*,!=2.6.*,!=2.7.*,!=2.8.*,<3,>=1.15.5 (from tensorflow-model-analysis==0.41.1->tfx[kfp]==1.10.0->-r requirements.in (line 1))
tensorflow!=2.0.*,!=2.1.*,!=2.2.*,!=2.3.*,!=2.4.*,!=2.5.*,!=2.6.*,!=2.7.*,!=2.8.*,<2.10,>=1.15.5 (from tfx[kfp]==1.10.0->-r requirements.in (line 1))
tensorflow!=2.0.*,!=2.1.*,!=2.2.*,!=2.3.*,!=2.4.*,!=2.5.*,!=2.6.*,!=2.7.*,!=2.8.*,<2.10,>=1.15.5 (from tensorflow-transform==1.10.1->tfx[kfp]==1.10.0->-r requirements.in (line 1))
tensorflow!=2.0.*,!=2.1.*,!=2.2.*,!=2.3.*,!=2.4.*,!=2.5.*,!=2.6.*,!=2.7.*,!=2.8.*,<3,>=1.15.5 (from tensorflow-data-validation==1.10.0->tfx[kfp]==1.10.0->-r requirements.in (line 1))
tensorflow<3,>=2.10.0 (from tensorflow-serving-api==2.10.0->tfx[kfp]==1.10.0->-r requirements.in (line 1))
Any rough timeline of when this will be released? Thanks!
Issue Analytics
- State:
- Created a year ago
- Comments:7
Top Results From Across the Web
Releases · tensorflow/tfx - GitHub
This is the last version that supports TensorFlow 1.15.x. TF 1.15.x support · Artifact/Channel properties now support the new MLMD PROTO property type....
Read more >tfx - PyPI
tfx apache‑beam ml‑metadata pyarrow tensorflow tensorflow‑data‑validat...
GitHub master 2.40.0 1.11.0 6.0.0 nightly (1.x/2.x) 1.11.0
1.11.0 2.40.0 1.11.0 6.0.0 1.15.5 / 2.10.0 1.11.0
1.10.0 2.40.0 1.10.0 6.0.0...
Read more >tfx Changelog - pyup.io
We will rollback this change once `kfp` releases a new version. * Fixed a compatibility issue with apache-airflow 2.3.0 that is failing with...
Read more >TensorFlow Transform | TFX
Compatible versions. The following table is the tf.Transform package versions that are compatible with each other. This is determined by our testing ...
Read more >TFX 0.25.0 is Out - Google Groups
We are pleased to announce that TFX 0.25.0 is released. ... Added CloudTuner KFP e2e example running on Google Cloud Platform with ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks, I should clarify that I’m able to repro dep conflicts with just the following.
The conflict is specifically from
pip-compile
thinking tensorflow has to be both<2.10
and>=2.10.0
. The<2.10
restriction is fromtensorflow-transform==1.10.1->tfx[kfp]==1.10.0
(hence this issue) and interestingly also fromtfx[kfp]==1.10.0
itself (corresponding issue).More curious is that despite
pip-compile
failing,pip install -r requirements.in
works with resulting packages.The pip-compile error I had above was actually incorrect behavior from legacy pip-compile resolver logic.
pip-compile
≥ 6.10.0 with--resolver backtracking
successfully resolves the dependencies.— https://pypi.org/project/pip-tools/