Tink installation on bazel and pip3 fail about tink

[morambro]

Hi @TanJinKiat

When building with bazel: ERROR: C:/users/User/tink-1.7.0/WORKSPACE:5:17: fetching local_repository rule //external:tink_cc: java.io.IOException: Could not create symlink to repository "/tmp/tink/python/../cc" (absolute path: "/tmp/tink/cc"): Cannot create junction (name=C:\users\User\_bazel_User\ure6mkuv\external\tink_cc, target=\tmp\tink\cc): ERROR: src/main/native/windows/file-jni.cc(122): nativeCreateJunction(\\?\C:\users\User\_bazel_marcus\ure6mkuv\external\tink_cc, \\?\\tmp\tink\cc): ERROR: src/main/native/windows/file.cc(231): CreateJunction(\\?\\tmp\tink\cc): expected an absolute Windows path for junction_target ERROR: Error computing the main repository mapping: no such package '@tink_cc//': Could not create symlink to repository "/tmp/tink/python/../cc" (absolute path: "/tmp/tink/cc"): Cannot create junction (name=C:\users\User\_bazel_User\ure6mkuv\external\tink_cc, target=\tmp\tink\cc): ERROR: src/main/native/windows/file-jni.cc(122): nativeCreateJunction(\\?\C:\users\User\_bazel_User\ure6mkuv\external\tink_cc, \\?\\tmp\tink\cc): ERROR: src/main/native/windows/file.cc(231): CreateJunction(\\?\\tmp\tink\cc): expected an absolute Windows path for junction_target Loading:

There is currently an issue with the sdist for v1.7.0, see #621 (comment).

Also note that Windows is not currently supported for Tink Python. We've recently added some support for Windows to Tink C++ (https://github.com/tink-crypto/tink-cc/releases/tag/v2.0.0), but not yet tested this with Tink Python.

[morambro]

Also, I understand that tink is only supported for Python versions 3.7 till 3.9. I have tried running the install within a Docker container set to Python 3.9, and that only resulted in multiple conflicts with protobuf. Downgrading to protobuf 3.20 seemed to help, but it does not seem like a long term, sustainable solution. Are there any workarounds for this issue? Thanks.

3.10 is also supported. The requirement on protobuf is indeed restrictive (see #695). We will probably fix this (alongside the sdist I mentioned in #700 (comment)) in a patch release.

Any idea when I can expect to be able to run Tink Python on Windows, or if there are any workarounds for this issue? This seems like a major issue for Windows OS users that isn't communicated across properly in documentation

Thanks for the feedback. I haven't looked at Windows support yet so unfortunately I don't have a timeline for it.

[TanJinKiat]

Thank you @morambro for the prompt reply.

Any idea when I can expect to be able to run Tink Python on Windows, or if there are any workarounds for this issue? This seems like a major issue for Windows OS users that isn't communicated across properly in documentation

[TanJinKiat]

Noted, thanks for the clarification.