Open Kogia-sima opened 1 month ago
In my python 3.11.9 environment, this issue is not reproduced at all in both 1.1.1
and the main
branch.
Yeah, I'm also using Python 3.11, which works fine
@harimkang @samet-akcay Thank you for your reply.
Hmm... Maybe python added a new feature during patch updates (e.g. 3.11.0 → 3.11.1). I'll check the cPython sources.
I've confirmed that the filter
argument was introduced during cpython 3.11.4 release.
That's why anomalib does not work with CPython<=3.11.3.
CPython 3.11.3 https://github.com/python/cpython/blob/v3.11.3/Lib/tarfile.py#L2079
CPython 3.11.4 https://github.com/python/cpython/blob/v3.11.4/Lib/tarfile.py#L2273
Now I'll send a PR to fix this.
Describe the bug
Anomalib depends on the new feature introduced with Python 3.12, which causes an error on Python 3.11.
When I simply run the train command from tutorial, anomalib raise the following error.
This behaviour is due to the
filter
argument was introduced in the Python 3.12, but I'm using Python 3.11 (I can't upgrade to 3.12 because I'm using the python of Databricks).Dataset
MVTec
Model
PatchCore
Steps to reproduce the behavior
pip install anomalib==1.1.1
OS information
OS information:
Expected behavior
Screenshots
No response
Pip/GitHub
pip
What version/branch did you use?
1.1.1
Configuration YAML
Logs
Code of Conduct