Re: [Django] #28667: Documentation for extending UserCreationForm doesn't work with UserAdmin

[Django]

#28667: Documentation for extending UserCreationForm doesn't work with UserAdmin
-+-
 Reporter:  Nathanael Gordon |Owner:  Swatantra
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  contrib.auth |  Version:  2.2
 Severity:  Normal   |   Resolution:
 Keywords:  add_fieldsets| Triage Stage:  Accepted
  UserAdmin UserCreationForm Custom  |
  Auth User Model|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by felixxm):

 * has_patch:  0 => 1
 * version:  1.11 => 2.2


Comment:

 [https://github.com/django/django/pull/11515 PR]

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.5cf19c9bbce732831db11a66fc14ae0c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26780: Prefetch objects don't work with slices

[Django]

#26780: Prefetch objects don't work with slices
-+-
 Reporter:  Ludwik Trammer   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  prefetch, slicing| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Dan LaManna):

 * cc: Dan LaManna (added)


-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.2dc12baf4db45aeb08422a4f0d10bf04%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26565: Allow Prefetch query to use .values()

[Django]

#26565: Allow Prefetch query to use .values()
-+-
 Reporter:  Maxime Lorant|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  prefetch, values | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Dan LaManna):

 * cc: Dan LaManna (added)


-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.bf0774a6e163e40338bc078982977e2d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25253: MySQL migrations drop & recreate constraints unnecessarily when changing attributes that don't affect the schema

[Django]

#25253: MySQL migrations drop & recreate constraints unnecessarily when changing
attributes that don't affect the schema
--+
 Reporter:  Thomas Recouvreux |Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  2.1
 Severity:  Normal|   Resolution:
 Keywords:  migrations m2m mysql  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by JR Heard):

 * version:  1.8 => 2.1


-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.4c992814eec0de6756b7a9477758b04d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25253: MySQL migrations drop & recreate constraints unnecessarily when changing attributes that don't affect the schema

[Django]

#25253: MySQL migrations drop & recreate constraints unnecessarily when changing
attributes that don't affect the schema
--+
 Reporter:  Thomas Recouvreux |Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:  migrations m2m mysql  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by JR Heard):

 * status:  assigned => new
 * owner:  Shun Yu => (none)


Comment:

 The issue in this ticket is still happening for me on Django 2.1.9 on
 Postgres. Adding `blank=True` to a `ManyToManyField` drops the FK
 constraints on the join table and creates them back, exactly as described.

 This ticket hasn't been touched in a couple of years so I'm going to
 deassign it. I hope this is the right thing to do here, I'm new to the
 Django community :)

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.958f03765d1ab6189e6b1aa483b43f97%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30608: Email messages crash on non-ASCII domain when email encoding is non-unicode. (was: Email messages crash on non-unicode hostname when email encoding is non-UTF-8.)

[Django]

#30608: Email messages crash on non-ASCII domain when email encoding is non-
unicode.
-+-
 Reporter:  Chason Chaffin   |Owner:  Chason
 |  Chaffin
 Type:  Bug  |   Status:  assigned
Component:  Core (Mail)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * stage:  Accepted => Ready for checkin


-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.3a41ee76b4c01076070b09f9f93195b3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27801: Make createsuperuser inspect environment variables for username and password

[Django]

#27801: Make createsuperuser inspect environment variables for username and
password
-+-
 Reporter:  Markus Holtermann|Owner:  Hasan
 |  Ramezani
 Type:  New feature  |   Status:  closed
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by James Pic):

 FTR, I fixed my issue among others in an external package:
 https://pypi.org/project/djcli/

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.3f9f9cc112a11fc18ed895e862722347%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27801: Make createsuperuser inspect environment variables for username and password

[Django]

#27801: Make createsuperuser inspect environment variables for username and
password
-+-
 Reporter:  Markus Holtermann|Owner:  Hasan
 |  Ramezani
 Type:  New feature  |   Status:  closed
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"a5308514fb4bc5086c9a16a8a24a945eeebb073c" a530851]:
 {{{
 #!CommitTicketReference repository=""
 revision="a5308514fb4bc5086c9a16a8a24a945eeebb073c"
 Fixed #27801 -- Made createsuperuser fall back to environment variables
 for password and required fields.
 }}}

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.54275ef829af864725e9958ea1c15e59%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30608: Email messages crash on non-unicode hostname when email encoding is non-UTF-8. (was: Email messages crash on non-unicode hostnames.)

[Django]

#30608: Email messages crash on non-unicode hostname when email encoding is non-
UTF-8.
+--
 Reporter:  Chason Chaffin  |Owner:  Chason Chaffin
 Type:  Bug |   Status:  assigned
Component:  Core (Mail) |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.4a54b7b4def72377573fe6038e6a6723%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30608: Email messages crash on non-unicode hostnames.

[Django]

#30608: Email messages crash on non-unicode hostnames.
+--
 Reporter:  Chason Chaffin  |Owner:  Chason Chaffin
 Type:  Bug |   Status:  assigned
Component:  Core (Mail) |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by felixxm):

 * owner:  nobody => Chason Chaffin
 * status:  new => assigned


-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.97496a9aa0d92f3400b2244082db4fc6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30608: Email messages crash on non-unicode hostnames.

[Django]

#30608: Email messages crash on non-unicode hostnames.
+
 Reporter:  Chason Chaffin  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Core (Mail) |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by Chason Chaffin):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/11532 PR]

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.0126fa6a80ffe20fd9928a3273fc01f8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30608: Email messages crash on non-unicode hostnames.

[Django]

#30608: Email messages crash on non-unicode hostnames.
+
 Reporter:  Chason Chaffin  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Core (Mail) |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by felixxm):

 Sure, feel free. Test is also required.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.f664c78d72bc473da3eb77debe77ef12%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30608: Email messages crash on non-unicode hostnames.

[Django]

#30608: Email messages crash on non-unicode hostnames.
+
 Reporter:  Chason Chaffin  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Core (Mail) |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by Chason Chaffin):

 Agreed. The patch you pasted in is essentially the same as I was about to
 submit as a pull request. Is it alright if I go ahead and submit that and
 add your name to the commit message?

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.438131e337bcb63a3fdbdda7d98d9674%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30608: Email messages crash on non-unicode hostnames. (was: Test failure in mail component when computer hostname is in unicode)

[Django]

#30608: Email messages crash on non-unicode hostnames.
+
 Reporter:  Chason Chaffin  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Core (Mail) |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by felixxm):

 * version:  2.2 => master
 * stage:  Unreviewed => Accepted


Comment:

 Thanks for the report. Simple encoding should fix this issue, e.g.
 {{{
 diff --git a/django/core/mail/utils.py b/django/core/mail/utils.py
 index d18dfe4667..68f9e464d6 100644
 --- a/django/core/mail/utils.py
 +++ b/django/core/mail/utils.py
 @@ -14,6 +14,10 @@ class CachedDnsName:
  def get_fqdn(self):
  if not hasattr(self, '_fqdn'):
  self._fqdn = socket.getfqdn()
 +try:
 +self._fqdn.encode('ascii')
 +except UnicodeEncodeError:
 +self._fqdn = self._fqdn.encode('idna').decode('ascii')
  return self._fqdn
 }}}

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.a7b1322659c34cc662fd74752636d020%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28588: Document User.has_perm() behavior for active superusers.

[Django]

#28588: Document User.has_perm() behavior for active superusers.
-+-
 Reporter:  Paul Hallett |Owner:  Carlton
 Type:   |  Gibson
  Cleanup/optimization   |   Status:  closed
Component:  contrib.auth |  Version:  2.2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"b6d8957356fd7f23e806c65657a72f7316d66b61" b6d8957]:
 {{{
 #!CommitTicketReference repository=""
 revision="b6d8957356fd7f23e806c65657a72f7316d66b61"
 [2.2.x] Fixed #28588 -- Doc'd User.has_perm() & co. behavior for active
 superusers.

 Equivalent note for PermissionsMixin was added in
 d33864ed138f65070049a3ac20ee98e03a1442b9.
 Backport of 4b32d039dbb59b3c3e76587df5c58150e752d9ac from master
 }}}

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.67a9486a2b8c8bb51c7c6c3e48b6bf4e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28588: Document User.has_perm() behavior for active superusers.

[Django]

#28588: Document User.has_perm() behavior for active superusers.
-+-
 Reporter:  Paul Hallett |Owner:  Carlton
 Type:   |  Gibson
  Cleanup/optimization   |   Status:  closed
Component:  contrib.auth |  Version:  2.2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"4b32d039dbb59b3c3e76587df5c58150e752d9ac" 4b32d039]:
 {{{
 #!CommitTicketReference repository=""
 revision="4b32d039dbb59b3c3e76587df5c58150e752d9ac"
 Fixed #28588 -- Doc'd User.has_perm() & co. behavior for active
 superusers.

 Equivalent note for PermissionsMixin was added in
 d33864ed138f65070049a3ac20ee98e03a1442b9.
 }}}

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.7bdd21633fe1806b941af07872020eb3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #30608: Test failure in mail component when computer hostname is in unicode

[Django]

#30608: Test failure in mail component when computer hostname is in unicode
--+
   Reporter:  Chason Chaffin  |  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  Core (Mail) |Version:  2.2
   Severity:  Normal  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+
 When the computer hostname is set in unicode (in my case "正宗"), the
 following test fails:
 https://github.com/django/django/blob/master/tests/mail/tests.py#L368

 Specifically, since the encoding is set to iso-8859-1, Python attempts to
 convert all of the headers to that encoding, including the Message-ID
 header which has been set here:
 https://github.com/django/django/blob/master/django/core/mail/message.py#L260

 This is not just a problem in the tests, Django should be handling the
 encoding of the message properly

 Steps to recreate:
 1. Set hostname to non iso-8859-1 value (i.e. `hostname 正宗`)
 2. run the mail tests

 Fix:
 have `django.core.mail.utils` or `django.core.mail.message` convert domain
 name to punycode before using

 Test:
 {{{
 #!python
 from unittest.mock import patch
 from django.core.mail import EmailMessage

 with patch("django.core.mailmessage.DNS_NAME", "漢字"):
 email = EmailMessage('subject', '', 'f...@example.com',
 ['t...@example.com'])
 email.encoding = 'iso-8859-1'
 message = email.message()
 self.assertIn('xn--p8s937b', message['Message-ID'])
 }}}

 Traceback:
 {{{
 Traceback (most recent call last):
   File "/Users/chason/projects/django/django/core/mail/message.py", line
 62, in forbid_multi_line_headers
 val.encode('ascii')
 UnicodeEncodeError: 'ascii' codec can't encode characters in position
 39-40: ordinal not in range(128)

 During handling of the above exception, another exception occurred:

 Traceback (most recent call last):
   File
 
"/usr/local/Cellar/python/3.7.3/Frameworks/Python.framework/Versions/3.7/lib/python3.7/unittest/mock.py",
 line 1204, in patched
 return func(*args, **keywargs)
   File "/Users/chason/projects/django/tests/mail/tests.py", line 373, in
 test_unicode_dns
 message = email.message()
   File "/Users/chason/projects/django/django/core/mail/message.py", line
 260, in message
 msg['Message-ID'] = make_msgid(domain=DNS_NAME)
   File "/Users/chason/projects/django/django/core/mail/message.py", line
 157, in __setitem__
 name, val = forbid_multi_line_headers(name, val, self.encoding)
   File "/Users/chason/projects/django/django/core/mail/message.py", line
 67, in forbid_multi_line_headers
 val = Header(val, encoding).encode()
   File
 
"/usr/local/Cellar/python/3.7.3/Frameworks/Python.framework/Versions/3.7/lib/python3.7/email/header.py",
 line 217, in __init__
 self.append(s, charset, errors)
   File
 
"/usr/local/Cellar/python/3.7.3/Frameworks/Python.framework/Versions/3.7/lib/python3.7/email/header.py",
 line 301, in append
 s.encode(output_charset, errors)
 UnicodeEncodeError: 'latin-1' codec can't encode characters in position
 39-40: ordinal not in range(256)
 }}}

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/049.a8762a08f45751b8fb46015e274e962e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28588: Document User.has_perm() behavior for active superusers. (was: User.has_perm() with superusers hides nonexistent permissions)

[Django]

#28588: Document User.has_perm() behavior for active superusers.
-+-
 Reporter:  Paul Hallett |Owner:  Carlton
 Type:   |  Gibson
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.auth |  Version:  2.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * version:  1.11 => 2.2


-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.80eb5a3da519182491eccc39e4292596%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.