#34167: Set a reasonable default for EMAIL_TIMEOUT
-------------------------------------+-------------------------------------
Reporter: Federico Capoano | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Core (Mail) | Version: 4.1
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => wontfix
Comment:
> Why there's no default for `EMAIL_TIMEOUT`?
If timeout is unspecified,
[https://docs.djangoproject.com/en/stable/topics/email/#smtp-backend SMTP
backend] will use `socket.getdefaulttimeout()`, so adding a default value
for `EMAIL_TIMEOUT` would 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
[https://docs.djangoproject.com/en/stable/internals/contributing/triaging-
tickets/#closing-tickets 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!
--
Ticket URL: <https://code.djangoproject.com/ticket/34167#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018483ec77be-2d7a9785-e05a-43ff-a0bd-09253399f266-000000%40eu-central-1.amazonses.com.
