Skip to content

Use public DateFrame names in processing logs - #16

Merged
fyulita merged 1 commit into
mainfrom
fix-public-log-names
May 27, 2026
Merged

Use public DateFrame names in processing logs#16
fyulita merged 1 commit into
mainfrom
fix-public-log-names

Conversation

@fyulita

@fyulita fyulita commented May 27, 2026

Copy link
Copy Markdown
Owner

Summary

Changed the names of the functions on the logs.

Related Issue

Validation

Describe how this change was tested. Include automated tests and any small sample workflow used.

  • python -m pytest -q passes locally
  • I tested changed behavior on disposable or copied sample media, if applicable
  • I updated documentation when user-visible behavior changed

Processing Impact

Check every area affected by this change:

  • Filename or destination-path behavior
  • Metadata reading or writing
  • Sidecars or Apple Live Photo pairing
  • CSV/TXT logs, checkpointing, or --resume-csv
  • Windows-only behavior or cross-platform compatibility
  • Packaging or command-line interface
  • None of the above

Privacy And Safety

  • This pull request does not include personal media files, generated logs, private paths, or unredacted sensitive metadata.

@fyulita
fyulita merged commit 4e62af7 into main May 27, 2026
4 checks passed
@fyulita
fyulita deleted the fix-public-log-names branch May 27, 2026 02:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant