You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I run photog in a docker container (python:3 and then just pip install photog), mounting a directory from the host. The files are simply named CK-20230224-kubernetes_3.5-11715.jpg; after running photog I get:
root@04184f3b7387:/photos# photog .
Traceback (most recent call last):
File "/usr/local/bin/photog", line 10, in <module>
photog.create_website(root[0])
File "/usr/local/lib/python3.11/site-packages/photog/__init__.py", line 40, in create_website
photos = rename_images(dir)
^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/photog/__init__.py", line 56, in rename_images
im = Image.open(os.path.join(dir, image))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/PIL/Image.py", line 3227, in open
fp = builtins.open(filename, "rb")
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: './CK-20230223-kubernetes_3.5-11065.jpg'
and files renamed to _CK-20230223-kubernetes_3.5-11065.jpg. Not sure how to fix this..
The text was updated successfully, but these errors were encountered:
The files are simply named CK-20230224-kubernetes_3.5-11715.jpg
Photog! attempts to rename all images to 1.jpg, 2.jpg, 3.jpg, etc. The bug is that it detects the "basename" wrong; instead of CK-20230224-kubernetes_3.5-11715 + .jpg it thinks your images are named CK-20230224-kubernetes_3 + .5-11715.jpg.
After it crashed, you were left with a bunch of "half-renamed" images. My apologies. I do not plan on fixing this bug soon, but I would welcome a PR that fixes it 🤗
I run photog in a docker container (
python:3
and then justpip install photog
), mounting a directory from the host. The files are simply namedCK-20230224-kubernetes_3.5-11715.jpg
; after running photog I get:and files renamed to
_CK-20230223-kubernetes_3.5-11065.jpg
. Not sure how to fix this..The text was updated successfully, but these errors were encountered: