Please follow semantic versioning 0.6.13 is not backward with 0.6.12
See original GitHub issueThe 0.6.13 version is not backward compatible to 0.6.12 while version increment only seems to be a patch.
File "/usr/local/lib/python3.8/dist-packages/torch_geometric/data/data.py", line 3, in <module>
from torch_geometric.typing import OptTensor, NodeType, EdgeType
File "/usr/local/lib/python3.8/dist-packages/torch_geometric/typing.py", line 4, in <module>
from torch_sparse import SparseTensor
File "/usr/local/lib/python3.8/dist-packages/torch_sparse/__init__.py", line 41, in <module>
from .tensor import SparseTensor # noqa
File "/usr/local/lib/python3.8/dist-packages/torch_sparse/tensor.py", line 13, in <module>
class SparseTensor(object):
File "/usr/local/lib/python3.8/dist-packages/torch/jit/_script.py", line 974, in script
_compile_and_register_class(obj, _rcb, qualified_name)
File "/usr/local/lib/python3.8/dist-packages/torch/jit/_script.py", line 67, in _compile_and_register_class
torch._C._jit_script_class_compile(qualified_name, ast, defaults, rcb)
RuntimeError:
Tried to access nonexistent attribute or method 'crow_indices' of type 'Tensor'.:
File "/usr/local/lib/python3.8/dist-packages/torch_sparse/tensor.py", line 109
def from_torch_sparse_csr_tensor(self, mat: torch.Tensor,
has_value: bool = True):
rowptr = mat.crow_indices()
~~~~~~~~~~~~~~~~ <--- HERE
col = mat.col_indices()
I have a model that was trained in 0.6.12. When reloading the model in a fresh environment with the new version, the previous error occurs.
Did you bump the minimum torch version in dependencies?
Regards,
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Semantic Versioning 2.0.0 | Semantic Versioning
PATCH version when you make backwards compatible bug fixes. Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR....
Read more >Semantic versioning in solidity - Ethereum Stack Exchange
I have found an answer to my question. Thanks to this question and its comments. Before the major versioning gets to 1 i.e...
Read more >Preventing Version Conflicts with versionScheme
A library that you pulled could depend on other libraries, and the transitive dependencies could cause version conflicts.
Read more >Error: Compiler version ^0.8.0 does not satisfy the r semver ...
It doesn't matter what version of compiler I specify, I keep on getting the same error. Can someone help me out? What does...
Read more >semversioner - PyPI
Manage properly semver in your repository. ... Alternatively, you can use the following command to filter changes by the last released version:
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
You can stay on 0.6.12 if you are using PyTorch 1.9.
I see. The minimum PyTorch version required is now indeed PyTorch 1.10.0. Everything else is fully backward compatible.