As of today, and the near future, Guild Python does not support Python 3. This ticket is to track progress and collect notes, ideas, rants, etc.
The challenge, as I see it, is that we're bringing in a lot of dependencies through Bazel, not the least of which is TensorBoard itself! It's not clear to me, short of exhaustive research and chasing issues, how easy it will be to finagle Python 3 support across the dependencies.
Frankly I think it will be far more sensible to just distribute Python with the Guild package and seal everything under an OS process.
As for Python level library use, Guild should support Python 3. If not, that is a bug that should be fixed as if it existed for Python 2.
Comments on this thread welcome!
As of today, and the near future, Guild Python does not support Python 3. This ticket is to track progress and collect notes, ideas, rants, etc.
The challenge, as I see it, is that we're bringing in a lot of dependencies through Bazel, not the least of which is TensorBoard itself! It's not clear to me, short of exhaustive research and chasing issues, how easy it will be to finagle Python 3 support across the dependencies.
Frankly I think it will be far more sensible to just distribute Python with the Guild package and seal everything under an OS process.
As for Python level library use, Guild should support Python 3. If not, that is a bug that should be fixed as if it existed for Python 2.
Comments on this thread welcome!