Code

Opened 6 years ago

Closed 6 years ago

Last modified 3 years ago

#8004 closed (wontfix)

Make email functionality more consistent

Reported by: mikeblake Owned by: nobody
Component: Core (Mail) Version: master
Severity: Keywords:
Cc: Triage Stage: Design decision needed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

contrib.auth.models.User has a function email_user

contrib.core.mail has functions send_mail, mail_managers etc.

For the sake of consistency, could these all be renamed 'email' (ie: send_email).
Mail could refer to snail-mail - although obviously unlikely.

Attachments (0)

Change History (3)

comment:1 Changed 6 years ago by julianb

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Design decision needed

comment:2 Changed 6 years ago by mtredinnick

  • Resolution set to wontfix
  • Status changed from new to closed

Not worth it. These functions and methods are already used in a lot of code and this would just be churn for no really good reason. If it worries you in your code, then don't use the "mail" versions (since they're not as extensible as the real deal anyway): use the all-powerful EmailMessage class instead.

comment:3 Changed 3 years ago by jacob

  • milestone 1.0 deleted

Milestone 1.0 deleted

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.