django.git/django/db/models/fields/files.py, branch main

Fixed #27150 -- Made base File objects truthy by default.

2026-04-14T11:32:08Z

Fixed 36622 -- Prevented LazyObject FileField storages from evaluating at boot time.

2025-10-15T21:25:08Z

Co-authored-by: Fabien MICHEL

Refs #36500 -- Rewrapped long docstrings and block comments via a script.

2025-07-23T23:17:55Z

Rewrapped long docstrings and block comments to 79 characters + newline using script from https://github.com/medmunds/autofix-w505.

Removed double spaces after periods and within phrases.

2025-07-23T13:09:43Z

Fixed #36005 -- Dropped support for Python 3.10 and 3.11.

2025-01-20T13:07:28Z

Fixed #35657 -- Made FileField handle db_default values.

2024-08-05T19:36:49Z

Fixed #35139 -- Prevented file read after ImageField is saved to storage.

2024-05-21T22:25:56Z

Fixed #35384 -- Raised FieldError when saving a file without a name to FileField.

2024-05-15T10:02:45Z

Refs #34517 -- Restored skipping ImageFileField.update_dimension_fields without width/height fields.

2023-06-19T03:24:42Z

This avoids reading the image size when the dimensions fields (image_width, image_height) do not exist, as that operation may be expensive. Partially reverts ea53e7c09f1b8864c20c65976bbeaeab77abdaec, that dropped the check for the dimension fields in update_dimension_fields(), because the post_init signal was no longer registered without dimension fields. However, another code path to that function exists: when the ImageFileField is save()d, the name from the storage is setattr()ed on the field, and ImageFileDescriptor calls update_dimension_fields() because the image size might have changed. Keep bailing out early when dimensions are unused. Besides, computing the image dimensions causes to close() the file, resulting in a backward-incompatible change. The test protects against that change.

Fixed #34517 -- Avoided connection post_init signal to ImageField without width/height fields.

2023-05-03T04:35:19Z