`ModuleNotFoundError`: 1.4.0 (and below, possibly) missing an explicit `future` dependency

[IanTayler]

As of right now, new installations of tensorflow-transform==1.4.0 fail to import with a ModuleNotFoundError because the future library is not marked as a dependency in the setup.py.

This likely wasn't a problem before because some recursive dependency of tft depended on future, masking the issue. But future is a hard dependency of tft 1.4.0, as it is imported on import tensorflow_transform, so it should probably be added as a dep in a 1.4.1 release (assuming this team does back-releases of that kind).

For people looking for a hotfix in your own project, adding future as a dependency of your project should be enough.

This isn't a problem in 1.5.0 because the only usage of future was removed in this commit.

[davidxia]

My team's using tfx==1.3.4 and also hit this today. This tfx version pulls in tensorflow-transform==1.3.0 which explicitly depends on future here but doesn't declare it as a dependency.

We worked around by adding future==0.18.2 to our own requirements.txt.

The error messages will say Exception: The full "tfx" package must be installed to use this functionality. But if you look more closely, you'll see it's a future import failure.

[casassg]

@rcrowe-google any chance to get a patch release for this 1.4.1? Seeing also some issues here on CI - https://github.com/tensorflow/tfx-addons/runs/5031481438?check_suite_focus=true

[jeongukjae]

Same here. I'm using tensorflow-transform==1.4.0 and tfx==1.4.1, and ModuleNotFoundError: No module named 'future' raised.
After the pip install future, it works.

[jiyongjung0]

FYI, tensorflow-transform 1.4.1 was released with future as an additional dependency.

[davidxia]

This issue can probably be closed since #262 is merged. People can probably reopen if they really need for older versions.

[davidxia]

Actually I noticed the future requirement wasn't added to the 1.5 or 1.6 branches. Any chance they can be updated as well?

[zoyahav]

This shouldn't be needed as the dependency on future was removed in 1.5, did you run into an issue with 1.5 or 1.6?

See 1.4.1

transform/tensorflow_transform/analyzer_nodes.py

Line 31 in 8a63bc9

from future.utils import with_metaclass

v.s. 1.5

transform/tensorflow_transform/analyzer_nodes.py

Line 31 in fe97b4b

import numpy as np

[davidxia]

@zoyahav I see, thanks! This can probably be closed then.

[zoyahav]

Thanks for verifying!