-
Notifications
You must be signed in to change notification settings - Fork 291
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
tensorflow-io 0.32.0 release #1789
Comments
We are seeing an issue in aarch64 build: https://ci.linaro.org/job/ldcg-python-manylinux-tensorflow-io/61/ |
`tensorflow` 2.12.0 needs a new release of `tensorflow-io` 0.32.0: tensorflow/io#1789 PiperOrigin-RevId: 519659112
`tensorflow` 2.12.0 needs a new release of `tensorflow-io` 0.32.0: tensorflow/io#1789 PiperOrigin-RevId: 519659112
Sorry, now resolved. https://snapshots.linaro.org/ldcg/python/tensorflow-io-manylinux/62/ |
`tensorflow` 2.12.0 needs a new release of `tensorflow-io` 0.32.0: tensorflow/io#1789 PiperOrigin-RevId: 519659112
`tensorflow` 2.12.0 needs a new release of `tensorflow-io` 0.32.0: tensorflow/io#1789 PiperOrigin-RevId: 519965653
Release binaries:
|
`tensorflow` 2.12.0 needs a new release of `tensorflow-io` 0.32.0: tensorflow/io#1789 PiperOrigin-RevId: 520311151
There is yet no wheel for Windows on PyPI, while they are present for v0.31.0. This makes it harder for multiplatform projects to depend on TensorFlow itself. https://pypi.org/project/tensorflow-io-gcs-filesystem/0.32.0/#files |
Is there a plan to provide wheels for tensorflow-io on windows? |
Any updates regarding windows wheels for 0.32.0? They were working fine until this latest release. |
Not having Windows wheels for 0.32.0 prevents from using TensorFlow 2.12.0, and in turn Python 3.11. |
still, to this date windows stage is failing so there for no wheels |
Hello,
When I use
tensorflow-io
0.31.0 withtensorflow
2.12.0 there's a problem with missing symbols inlibtensorflow_io.so
. I noticed that you updatedtensorflow-io
to 0.32.0, but there was no new release on PyPI.Are there any issues with the new release?
The text was updated successfully, but these errors were encountered: