[Django] #26089: The auth custom test model tables are not created anymore.

[Django]

#26089: The auth custom test model tables are not created anymore.
---+---
   Reporter:  charettes|  Owner:  charettes
   Type:  Bug  | Status:  new
  Component:  contrib.auth |Version:  1.8
   Severity:  Release blocker  |   Keywords:
   Triage Stage:  Accepted |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+---
 Since the introduction of contrib application migrations in 1.8 (#22170)
 the [https://docs.djangoproject.com/en/1.9/topics/auth/customizing
 /#custom-users-and-testing-fixtures documented custom user test models]
 table are not created anymore because they are registered to the `'auth'`
 labeled application but are not part of its shipped migrations.

 Based on the fact this was not reported before and that the only uses of
 `ExtensionUser` I can find is
 
[https://github.com/search?l=python=django+ExtensionUser=searchresults=Code=%E2%9C%93
 either from a vendored version of Django or a copy-pasta of the
 documentation suggested usage] I think we can safely assume it's not
 commonly used among third-party application who claim to support custom
 user models. I'll make sure to post the mailing list in order to gather
 feedback from the community about this point.

 Given the models are simply not usable on 1.8 and 1.9 now I'd like to
 start the deprecation in 1.8 in order order to be able to completely
 remove them on master but if it's not considered safe enough I came up
 with a with a workaround that could be backported since there's still no
 documented way to ship test only models (#7835).

 If these models are relied on by the community I would suggest we start
 deprecating them in 1.10 and adjust the documentation to suggest
 subclassing the provided abstract models instead.

--
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/052.5ab29215803bc275e193ab509af150d0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26085: contenttypes.views.shortcut fails if a FK to Site returns None

[Django]

#26085: contenttypes.views.shortcut fails if a FK to Site returns None
--+
 Reporter:  jaap3 |Owner:  jibaku
 Type:  Bug   |   Status:  assigned
Component:  contrib.contenttypes  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by jibaku):

 * owner:  nobody => jibaku
 * 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/063.a9dab61d1686c91a2711758a7f827729%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26085: contenttypes.views.shortcut fails if a FK to Site returns None

[Django]

#26085: contenttypes.views.shortcut fails if a FK to Site returns None
--+
 Reporter:  jaap3 |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.contenttypes  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by jibaku):

 Created a PR. Feedback needed, it's my first PR to Django.
 https://github.com/django/django/pull/5986

--
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.f90f5d73c2eb043b9a77ad6f30d77e4d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23422: Cannot add Permission to Group in data migration

[Django]

#23422: Cannot add Permission to Group in data migration
+--
 Reporter:  tjwalch |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.7
 Severity:  Normal  |   Resolution:  wontfix
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  1
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by acidjunk):

 I can confirm that it also works for me.

 0001.py added custom permissions
 0002.py assigned custom permissions to a group

 Without the workaround by guettli in 0002.py: the custom permissions
 weren't available.

 Thanks

 R

--
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.6fccc8c5c3121d8fbccc03032929ccd1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #18392: Use utf8mb4 encoding with MySQL 5.5

[Django]

#18392: Use utf8mb4 encoding with MySQL 5.5
-+-
 Reporter:  EmilStenstrom|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  utf8mb4 mysql| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by EmilStenstrom):

 Slightly off-topic but maybe interesting: The Wordpress team did convert
 all their users from utf8 to utf8mb4 according to [this blog
 post](https://make.wordpress.org/core/2015/04/02/the-utf8mb4-upgrade/).

 Looking at the code it seems they just dropped and recreated all the
 indexes: https://github.com/WordPress/WordPress/blob/master/wp-
 admin/includes/upgrade.php#L2687

 And then converted all the tables one by one:
 https://github.com/WordPress/WordPress/blob/master/wp-
 admin/includes/upgrade.php#L1951

--
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/071.81dcbc65db0419878a44db92ee696e19%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.