This repository has been archived by the owner on Oct 31, 2023. It is now read-only.
Remove mentions to async
reserved keyword for usage with Python 3.7
#135
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In this PR, I've deleted all mentions to the
async
keyword in the master branch of ELF to resume compatibility of the repository with Python 3.7ELF uses
async
as a name for variables and function parameters. In Python 3.7,async
has become a reserved word. The word is only used as argument to thecopy_
andcuda
methods, which are methods from thepytorch.Tensor
object. But these methods don't use the value of theasync
argument for anything.By removing mentions to the now-reserved keyword, no change in the behavior of the package is expected. I've tested training a model using
./train_minirts.sh
on Python 3.7 with both CPU and GPU and everything worked. I believe this fixes #124 and #127.I created a new PR because I used my master branch as the head repository in #134, which was a bad idea on my side.