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
Add Support for torch==1.5.x #104
Comments
I don't think it's possible, because support of custom RNGs was added in PT 1.6.0. The only possible workaround for 1.5.0 is to have something like |
@pbelevich Good idea, lets see if thats sufficient for our use case and then we can just wait out the deprecation of 1.5.x. |
@madhavajay you closed this because you don't need it anymore? |
@pbelevich Oh sorry, I thought you were suggesting that this only required changing the use of t.x to torchcsprng.x(t) but I guess to prevent torch version conflicts there might still need to be a change on torchcsprng? |
@madhavajay how long do you think you will need to support 1.5.x? Or in other words when are you going to stop supporting 1.5.x? |
@pbelevich good question. I would imagine we would probably deprecate it when 1.8.x rolls around but we currently had to re-add 1.4.0 for another use case the other day so its hard to say exactly when. Is there a technical reason the random number generator won't work or is it just that there is a lot of related work to support the older code base and different platforms / targets? |
Yes, we have stopped testing |
Is there any chance torch 1.5.x can be supported?
Then we can achieve our current support matrix in Syft / Duet: https://github.com/OpenMined/pysyft of torch 1.5.x+ as we need csprng in SyMPC: https://github.com/OpenMined/SyMPC/
The text was updated successfully, but these errors were encountered: