Opened 12 years ago
Closed 12 years ago
#18440 closed Cleanup/optimization (fixed)
Clarify that Reportlab is not thread-safe in pdf section
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Documentation | Version: | 1.4 |
| Severity: | Normal | Keywords: | pdf reportlab |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
In the doc section on 'Outputting PDFs with Django' there is a strong bias towards Reportlab and Reportlab is great - but it is not thread-safe. This should at least be mentioned and clarified that if if the intention is to offer pdf download from views that can be concurrently accessed - then Reportlab is not the right tool.
I have used Reportlab and now as the usage of my site grows I started to get really strange bugs in reportlab that has taken me now a week to figure out that this is due to threading issues in Reportlab. Had I known this from the start I should not have invested all the effort in using Reportlab, now I need to figure out how to replace it.
/ Jens
Change History (3)
comment:1 by , 12 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:2 by , 12 years ago
Have not yet decided on how to go about this, can update here with how I go about this. Would be at least good to mention characteristic of Reportlab in docs.
comment:3 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Good point. Do you know alternatives that we could point to? Or should we just mention the thread-(un)safety problem?