Closed 6r1d closed 2 years ago
Please use the Python version. e.g. 3.8.2
which supports the PyTorch version from requirements.txt when testing or running a project.
Currently python >= 3.10
is not supported. This version of python requires the latest dependencies which break the cuda docker image build.
You can submit a Pull Request with updated dependencies, but make sure all versions of the docker image (CUDA and CPU) correctly install dependencies and pass tests. If necessary, update the versions of the base images on which the project's docker images are built. I will update the project code to fix the warnings for the new version of pytorch if there is a Pull Request
I'm sorry, but I've got no CUDA machine to test the version change on and Colab's Python is locked on Python 3.7.13. I'll just test if updated versions work on 3.7.3 and leave it for the CUDA test stage. Hope that'll help a bit.
I had to set the exact Pillow version because of this small error while attempting to test how deps work with Colab's Python.
Current test seems to be working well (and interestingly, there's small difference on image 4 between CPU and GPU version.):
Cat | gpu | cpu |
---|---|---|
1 | gpu | cpu |
2 | gpu | cpu |
3 | gpu | cpu |
4 | gpu | cpu |
So, the resulting requirements.txt
is:
requests~=2.26.0
torch~=1.11.0
Pillow==9.0.0
typing~=3.7.4.3
gdown~=3.12.2
torchvision~=0.12.0
opencv-python~=4.5.5.62
numpy~=1.21.2
loguru~=0.5.3
uvicorn~=0.11.7
fastapi~=0.68.1
starlette~=0.14.2
pydantic~=1.7.4
click~=7.1.2
tqdm~=4.62.3
setuptools
aiofiles~=0.6.0
python-multipart~=0.0.5
I created a Pull Request #79 with updated dependencies and support for the latest version of Python. I will merge it after June 24th.
I've posted #75 and to help with tests, I am running CarveKit in
venv
with Python 3.10.4 to do a clean installation and I see this when trying to install the packages:Should I update Torch to
1.11.0
, I'd see:Let us try
torchvision~=0.12.0
andtorch~=1.11.0
:Let's fix NumPy now:
numpy~=1.21.2
. Things seem to work. I am not sure if warnings matter here:Since this version of Torch seems to have
ceil_mode
andreturn_indices
configured that way, it seems safe to update the package. Should I PR the change?If not yet, I can test if there are defects on several test images. Thanks.