Skip to content

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

Closed
@IanTayler

Description

@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.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions