Changes between Initial Version and Version 1 of Ticket #27301, comment 6
- Timestamp:
- Oct 3, 2016, 5:17:53 AM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #27301, comment 6
initial v1 5 5 > we can try to fix thousands of unpickleable errors, but with a robust test runner it might not matter at all. 6 6 7 Thousands seems like an exaggeration to me. A dozen seems like a more reasonableupper bound.7 Thousands seems like an exaggeration to me. A dozen seems like a more likely upper bound. 8 8 9 9 In any case, if a particular exception isn't picklable, it seems like that should be reported as a bug each time we notice it -- regardless of the state of Django's test runner, and regardless of the number of instances we notice. Also, as long as Django relies on the picklability of exceptions for the nicest form of error messages, it seems we should want those exceptions to be picklable.