do Obsolete chore filenames cause conflicts with newer chores?
I'm not sure whether the filenames used in a django File objects are the actual file names on disc or not...
Do we have to worry about collisions if I have two BuildPaperPDFChores that have the same filename, then what is the status of those bytes on disc?
E.g., after !2385 (merged) we can have:
┌────────────────┬────────────┬──────────┬───────────┬────────────────────────┐
│ paper_number │ obsolete │ status │ message │ pdf_filename │
├────────────────┼────────────┼──────────┼───────────┼────────────────────────┤
│ 1 │ False │ Complete │ │ exam_0001_10050380.pdf │
│ 1 │ True │ Complete │ │ exam_0001_10050380.pdf │
Do I need to worry about this or does django take care of it?
I'd probably sleep easier if we stored the md5sum in there as well as the file name...