#34167 closed Cleanup/optimization (wontfix)
Set a reasonable default for EMAIL_TIMEOUT — at Version 2
| Reported by: | Federico Capoano | Owned by: | nobody |
|---|---|---|---|
| Component: | Core (Mail) | Version: | 4.1 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
For the record, I started a discussion here: https://groups.google.com/g/django-developers/c/XZbKeM8fVxU/m/jp0h8U4tBgAJ
Change History (2)
comment:1 by , 19 months ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
comment:2 by , 18 months ago
| Description: | modified (diff) |
|---|
For the record, I started a discussion in the Django Developers Mailing List: https://groups.google.com/g/django-developers/c/XZbKeM8fVxU/m/jp0h8U4tBgAJ .
Note:
See TracTickets
for help on using tickets.
If timeout is unspecified, SMTP backend will use
socket.getdefaulttimeout(), so adding a default value forEMAIL_TIMEOUTwould be backward incompatible for all projects that set a default timeout for sockets.Initially closing as "wontfix". Please first start a discussion on the DevelopersMailingList., where you'll reach a wider audience and see what other think, and follow triaging guidelines with regards to wontfix tickets. If you can get consensus on a proposal on the DevelopersMailingList, we can reopen the ticket. Thanks!