FileField doesn't clean up directory after deletion

[Michiel_1981]

If a FileField file is being deleted it doesn't clean up a empty directory that might occur after deletion.
This is only a issue if you use a dynamic path based on date.

If this is the case then you could create a lot of empty directories and/or nested empty directories.
Example code:

class MetaFile(models.Model):
    file = models.FileField(_("File"), max_length=255,
                            upload_to='meta/%y/%m')

[MichaelBishop]

Why should an empty folder be delete after a file is deleted? I think that should be an individual design decision. However, a Django design decision is required.

[Marty Alchin]

For what it's worth, when I added fs-rf-docs to this, it meant that my work on #5361 will make this behavior possible, but it won't be inclued by default. Instead, its documentation will show what hooks are available to make this happen. I'd also rather not see this behavior, but at least #5361 will make it possible for those who would like it. Just in case that helps with the design decision.

[Michiel_1981]

for what it's worth, I override the FileField and add a dispather call to it for clean up if needed.
This ticket can be closed as you could override the delete method on the model or the above method.

I'll post on djangosnippets.org how this could be done if anybody is interested

[Michael Radziej]

Not considered a bug => not 1.0 beta.

[Marty Alchin]

Bugs aren't the only things planned for 1.0 beta. This is being addressed as part of #5361, which is planned to make it into 1.0 beta. Even though it won't be fixed directly, the behavior requested in this ticket will be quite possible once that goes in. ​Per Jacob, all such related tickets should be placed in the 1.0 beta milestone.

[Jacob]

File storage is in as of [8244], so I'm marking this as wontfix -- as Marty says, it's very easy to write a custom file storage backend that works exactly how you like it.

[Jacob]

Milestone 1.0 beta deleted