[Django] #25897: Managers defined on non-abstract base classes are in fact inherited by child classes.

[Django]

#25897: Managers defined on non-abstract base classes are in fact inherited by
child classes.
--+
 Reporter:  poleha|  Owner:  poleha
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:  manager,
  |  inheritance
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Although documentation says it shouldn't:
 https://docs.djangoproject.com/en/dev/topics/db/managers/#custom-managers-
 and-model-inheritance

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

Re: [Django] #25883: Admin Delete Page Incorrectly Counts Related Objects

[Django]

#25883: Admin Delete Page Incorrectly Counts Related Objects
---+--
 Reporter:  jpulec |Owner:  sir-sigurd
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  1.9
 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 sir-sigurd):

 * has_patch:  0 => 1


Comment:

 Minimal example to reproduce:
 {{{
 class Shrubbery(models.Model):
 pass

 class KnightWhoSayNi(models.Model):
 shrubbery = ForeignKey(Shrubbery, related_name='+')
 another_shrubbery = ForeignKey(Shrubbery, related_name='+')

 shrubbery = Shrubbery.objects.create()
 KnightWhoSayNi.objects.create(shrubbery=shrubbery,
 another_shrubbery=shrubbery)
 }}}

 PR -- https://github.com/django/django/pull/5796

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

Re: [Django] #25878: APPEND_SLASH doesn't work with DEBUG=False when template/404.html is erroneous

[Django]

#25878: APPEND_SLASH doesn't work with DEBUG=False when template/404.html is
erroneous
---+--
 Reporter:  kuna   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  HTTP handling  |  Version:  1.9
 Severity:  Normal |   Resolution:
 Keywords:  slash,debug| Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by kuna):

 It was caused by my projects buggy template, but behavior changed since
 django version was updated. So It's no use to do git bisect. I'm also
 confused it's bug or just a simple behavior change...

 [https://dl.dropboxusercontent.com/u/102712785/django19.zip Download] and
 unzip this project and check not working APPEND_SLASH when Debug=False
 with this project under django v1.9.

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

Re: [Django] #25888: migrate with "--fake" option modifies the database

[Django]

#25888: migrate with "--fake" option modifies the database
-+-
 Reporter:  mandm|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by shaib):

 You can use `--fake` also when migrating backwards, thus undoing your
 original `--fake` (but beware if you have other migrations depending on
 your migration). How you created the migration file is irrelevant.

 In the future, please use the designated support channels (IRC channel
 #django on freenode, or django-users mailing list) rather than the bug
 tracker for this kind of question.

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

Re: [Django] #25672: Clarify why related ManyToMany fields with a custom intermediary model disable the remove() method.

[Django]

#25672: Clarify why related ManyToMany fields with a custom intermediary model
disable the remove() method.
--+
 Reporter:  Antwan86  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:  fixed
 Keywords:  manytomany related| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"d508326e2f7d35973e2662109e34b425cb108b81" d508326]:
 {{{
 #!CommitTicketReference repository=""
 revision="d508326e2f7d35973e2662109e34b425cb108b81"
 Fixed #25672 -- Clarified why related ManyToManyFields with a custom
 intermediate model disable the remove() method.
 }}}

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

Re: [Django] #25884: migrate --run-syncdb doesn't work when specifying a database (was: migrate --run-syncdb doesn't [seem to] work for app without migrations)

[Django]

#25884: migrate --run-syncdb doesn't work when specifying a database
+
 Reporter:  gertjanol   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.9
 Severity:  Normal  |   Resolution:
 Keywords:  syncdb, migrations  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by timgraham):

 * stage:  Unreviewed => Accepted


Comment:

 This could very well be a bug as I didn't think or test the multiple
 database support when adding `run_syncdb`. Feel free to submit a patch and
 we can probably backport it to 1.9.

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

Re: [Django] #10060: Multiple table annotation failure

[Django]

#10060: Multiple table annotation failure
-+-
 Reporter:  svsharma@…   |Owner:
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 timgraham):

 If I understood Anssi correctly, the existing documentation warning
 [https://groups.google.com/d/msg/django-
 developers/qiYKd1YZY_E/Tgn0p1wHCQAJ isn't correct], so I submitted
 [https://github.com/django/django/pull/5795 a revision].

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

Re: [Django] #24622: Response "context" and "templates" not available in the Test Client when using Jinja2 - Django 1.8

[Django]

#24622: Response "context" and "templates" not available in the Test Client when
using Jinja2 - Django 1.8
-+
 Reporter:  rivantis |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  jinja2, test client  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by timgraham):

 As I see it, "populated" means set to something non-empty/non-none, but I
 recognize the wording could be not ideal for non-native speakers. Feel
 free to submit a rewording if you like.

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

Re: [Django] #24622: Response "context" and "templates" not available in the Test Client when using Jinja2 - Django 1.8

[Django]

#24622: Response "context" and "templates" not available in the Test Client when
using Jinja2 - Django 1.8
-+
 Reporter:  rivantis |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  jinja2, test client  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by phispi):

 "This attribute is only populated when using the
 `django.template.backends.django.DjangoTemplates backend`" might be a bit
 misleading:
 `templates` ''is'' populated with an empty list, `context` ''is'' set to
 `None` for non-Django templates.
 As I see it, there is currently no way for 3rd party template engines to
 be compatible with the `TestClient` in this respect.

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

Re: [Django] #25872: Title attribute for related widget links lacks escaping (and breaks html)

[Django]

#25872: Title attribute for related widget links lacks escaping (and breaks 
html)
-+
 Reporter:  a1tus|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.8
 Severity:  Release blocker  |   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 a1tus):

 I mean, in translation files we don't usually know where this string will
 be used. It can be used in python or printed as text/html as always or
 like in our case in some html attribute. So responsibility about escaping
 must be taken by the one who knows the context. In this particular case I
 think that's our template file.

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

Re: [Django] #25872: Title attribute for related widget links lacks escaping (and breaks html)

[Django]

#25872: Title attribute for related widget links lacks escaping (and breaks 
html)
-+
 Reporter:  a1tus|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.8
 Severity:  Release blocker  |   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 a1tus):

 Replying to [comment:3 claudep]:
 > This was discussed already AFAIR. We have currently no way to tell if
 the markup from a translated string should be escaped or not, as it is
 perfectly legal to mark for translation strings having HTML markup. Until
 now, we simply trust translations, as if they were code. I'm open to some
 strategy to change this behavior if anyone has good ideas.
 > Until then, the workaround is to update the translation with escaped
 content.
 I agree that in general there can be some choices but in this particular
 place of code (where translated string is in `title` attribute) there
 should not be any unescaped chars. So I don't see any drawbacks of
 escaping it in this template. In english and all locales that don't have
 quotes everything will remain as it is now while bug will be fixed in
 others.

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

Re: [Django] #25657: gevent-monkeypatching with GIS PointField causes intermittent traceback on shutdown

[Django]

#25657: gevent-monkeypatching with GIS PointField causes intermittent traceback 
on
shutdown
--+-
 Reporter:  jaddison  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  GIS   |  Version:  1.9
 Severity:  Normal|   Resolution:  fixed
 Keywords:  gevent| 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 Claude Paroz ):

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


Comment:

 In [changeset:"cd40d9e721eb4f5d05f57a74c6f1fd5d4aaef444" cd40d9e7]:
 {{{
 #!CommitTicketReference repository=""
 revision="cd40d9e721eb4f5d05f57a74c6f1fd5d4aaef444"
 Fixed #25657 -- Ignored exceptions when destroying geometry objects

 Due to randomness of garbage collection with geometry objects, it's
 easier to simply ignore AttributeError/TypeError generally raised when
 parts of objects are already garbage-collected.
 Thanks Sergey Fedoseev and Tim Graham for reviewing the patch.
 }}}

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

Re: [Django] #25872: Title attribute for related widget links lacks escaping (and breaks html)

[Django]

#25872: Title attribute for related widget links lacks escaping (and breaks 
html)
-+
 Reporter:  a1tus|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.8
 Severity:  Release blocker  |   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 claudep):

 Probably somewhere in
 https://docs.djangoproject.com/en/stable/topics/i18n/translation
 /#internationalization-in-template-code

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

Re: [Django] #25637: Add label and hostname length validation in URLValidator

[Django]

#25637: Add label and hostname length validation in URLValidator
--+
 Reporter:  DheerendraRathor  |Owner:  raphaelm
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Other)  |  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 Tim Graham ):

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


Comment:

 In [changeset:"82976e5c3f7abf20dfd4c3cc5aa586e57edef104" 82976e5c]:
 {{{
 #!CommitTicketReference repository=""
 revision="82976e5c3f7abf20dfd4c3cc5aa586e57edef104"
 Fixed #25637 -- Added URLValidator hostname length validation.

 URLValidator now validates the maximum length of a hostname and the
 maximum length of all labels inside the hostname.
 }}}

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

Re: [Django] #25884: migrate --run-syncdb doesn't [seem to] work for app without migrations

[Django]

#25884: migrate --run-syncdb doesn't [seem to] work for app without migrations
+--
 Reporter:  gertjanol   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.9
 Severity:  Normal  |   Resolution:
 Keywords:  syncdb, migrations  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by gertjanol):

 * status:  closed => new
 * resolution:  invalid =>


Comment:

 Hi Tim,

 Thanks, you're right of course, but that doesn't solve my problem. But I
 think I've figured it out. If I run `./manage.py migrate --run-syncdb` it
 indeed works as intended: the `polls` app is also synced to the database.
 However, in our software stack we use a different database for each app,
 with a router configured in `DATABASE_ROUTERS` that routes reads, writes,
 relations and migrations.
 In that case, we need to migrate each database to it's own database.
 Before 1.9, we needed to specify the app that was being synced or
 migrated. I just found out that with 1.9 that's no longer necessary. In my
 example, these two commands gave the expected result: `./manage.py migrate
 --run-syncdb` and `./manage.py migrate --run-syncdb --database polls`.

 I've updated [https://github.com/gertjanol/django-test my example] at
 github to demonstrate our router and settings.

 I think this behaviour deserves a mention in the docs. Also, the error I
 encountered is not very helpful. It should at least mention that `--run-
 syncdb` it not possible when specifying an app. Why is that? When I change
 
[https://github.com/django/django/blob/e403f2217e67301526a0df5ea5be42e190e00e10/django/core/management/commands/migrate.py#L131
 this line] to `if app_label not in executor.loader.migrated_apps and not
 run_syncdb` (and move the assignment to `run_syncdb` higher) everything
 works as I'd expect. I couldn't find any tests that documented this
 behaviour :(.

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

Re: [Django] #25803: npm test failure

[Django]

#25803: npm test failure
---+--
 Reporter:  nikolas|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:  worksforme
 Keywords:  javascript | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Tim Graham ):

 In [changeset:"abd870651c7de87b4b1340d966d0140cc802cac7" abd8706]:
 {{{
 #!CommitTicketReference repository=""
 revision="abd870651c7de87b4b1340d966d0140cc802cac7"
 [1.9.x] Refs #25803 -- Documented npm compatibility in package.json

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

Re: [Django] #25803: npm test failure

[Django]

#25803: npm test failure
---+--
 Reporter:  nikolas|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:  worksforme
 Keywords:  javascript | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Tim Graham ):

 In [changeset:"d7a58f285b4c0c1b4ec032f9a7bf8f31913d0f5f" d7a58f2]:
 {{{
 #!CommitTicketReference repository=""
 revision="d7a58f285b4c0c1b4ec032f9a7bf8f31913d0f5f"
 Refs #25803 -- Documented npm compatibility in package.json
 }}}

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

Re: [Django] #25617: Disallow usernames that differ only in case in UserCreationForm

[Django]

#25617: Disallow usernames that differ only in case in UserCreationForm
--+
 Reporter:  timgraham |Owner:  nmundar
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * needs_better_patch:  0 => 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/067.a5a912ce52ce718fa0dfd199b01d13c6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25657: gevent-monkeypatching with GIS PointField causes intermittent traceback on shutdown

[Django]

#25657: gevent-monkeypatching with GIS PointField causes intermittent traceback 
on
shutdown
--+-
 Reporter:  jaddison  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  GIS   |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  gevent| 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 timgraham):

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

Re: [Django] #25872: Title attribute for related widget links lacks escaping (and breaks html)

[Django]

#25872: Title attribute for related widget links lacks escaping (and breaks 
html)
-+
 Reporter:  a1tus|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.8
 Severity:  Release blocker  |   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 timgraham):

 So this is a case of incorrect translations (at least for now) and we
 should close the ticket as invalid and perhaps open a new one for ideas
 for improvements? Do you have a suggestion of where to document these
 translations rules if it's not done already?

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

Re: [Django] #25892: Optimize SeparateDatabaseAndState.database_backwards() by caching intermediate state (was: SeparateDatabaseAndState database_backwards is slow.)

[Django]

#25892: Optimize SeparateDatabaseAndState.database_backwards() by caching
intermediate state
--+
 Reporter:  amosonn   |Owner:  amosonn
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Migrations|  Version:  1.8
 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 timgraham):

 * stage:  Unreviewed => Accepted


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

Re: [Django] #21221: Widgets and Admin's Media should use the configured staticfiles storage to create the right path to a file

[Django]

#21221: Widgets and Admin's Media should use the configured staticfiles storage 
to
create the right path to a file
-+-
 Reporter:  Guilherme Gondim |Owner:  codingjoe
  |
 Type:  New feature  |   Status:  assigned
Component:  contrib.staticfiles  |  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  staticfiles, admin,  | Triage Stage:  Ready for
  CachedFilesMixin, media, widgets   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * type:  Bug => New feature
 * stage:  Accepted => Ready for checkin


Comment:

 Looks good pending incorporation of my edits.

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

Re: [Django] #25895: Customizing user admin docs shouldn't override name.

[Django]

#25895: Customizing user admin docs shouldn't override name.
-+-
 Reporter:  justinabrahms|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"cdc354eb39085bb03f90216509611c279bf368f5" cdc354e]:
 {{{
 #!CommitTicketReference repository=""
 revision="cdc354eb39085bb03f90216509611c279bf368f5"
 [1.8.x] Fixed #25895 -- Used a consistent style for UserAdmin overrides.

 Thanks Justin Abrahms for the report.

 Backport of 166e0490d39f619928ee9c5133cc5cab0ae5c1db 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/071.e2b8ed455ede2d009024e8752cda4815%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25895: Customizing user admin docs shouldn't override name.

[Django]

#25895: Customizing user admin docs shouldn't override name.
-+-
 Reporter:  justinabrahms|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"166e0490d39f619928ee9c5133cc5cab0ae5c1db" 166e0490]:
 {{{
 #!CommitTicketReference repository=""
 revision="166e0490d39f619928ee9c5133cc5cab0ae5c1db"
 Fixed #25895 -- Used a consistent style for UserAdmin overrides.

 Thanks Justin Abrahms for the report.
 }}}

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

Re: [Django] #25895: Customizing user admin docs shouldn't override name.

[Django]

#25895: Customizing user admin docs shouldn't override name.
-+-
 Reporter:  justinabrahms|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"abeb50db5dbc9e5b08c2974d39c1f92e0c051c1c" abeb50db]:
 {{{
 #!CommitTicketReference repository=""
 revision="abeb50db5dbc9e5b08c2974d39c1f92e0c051c1c"
 [1.9.x] Fixed #25895 -- Used a consistent style for UserAdmin overrides.

 Thanks Justin Abrahms for the report.

 Backport of 166e0490d39f619928ee9c5133cc5cab0ae5c1db 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/071.c7127a31646e1099dddb58932dd2ee07%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24162: "Method Flowchart" for all CB(G)V documentation pages

[Django]

#24162: "Method Flowchart" for all CB(G)V documentation pages
-+-
 Reporter:  ivanvenosdel |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  CBV CBGV method  | Triage Stage:  Accepted
  flowchart  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by ivanvenosdel:

Old description:

> First off, to whoever had the idea and put in the effort to add the
> "Method Flowchart" to the CBV and CBGV doc pages, thank you, thank you,
> thank you. So helpful.
>
> So naturally I would love to see the feature on all of the CB(G)V pages,
> particularly those with a form as they are more complicated.
>
> Why is this necessary?
>
> 1. To make the multiple branches of form view logic more explicit. What
> methods get called when there is a GET? What about a POST?
>
> 2. To gain all the advantages that the "Method Flow" chart has provided
> to the other views. For me it has been primarily helpful for
> understanding and figuring out how to avoid duplicate queries.
>
> Moved from comment on: ticket:20608

New description:

 First off, to whoever had the idea and put in the effort to add the
 "Method Flowchart" to some of the CBV and CBGV doc pages, thank you, thank
 you, thank you. So helpful.

 Example "Method Flowchart": ​https://docs.djangoproject.com/en/dev/ref
 /class-based-views/generic-display/#listview

 So naturally I would love to see the feature on all of the CB(G)V pages,
 particularly those with a form as they are more complicated.

 Why is this necessary?

 1. To make the multiple branches of form view logic more explicit. What
 methods get called when there is a GET? What about a POST?

 2. To gain all the advantages that the "Method Flow" chart has provided to
 the other views. For me it has been primarily helpful for understanding
 and figuring out how to avoid duplicate queries.

 Moved from comment on: ticket:20608

--

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

Re: [Django] #25886: Release notes confusion and Django 1.8.8/Python 3.2-3.3 import error

[Django]

#25886: Release notes confusion and Django 1.8.8/Python 3.2-3.3 import error
-+-
 Reporter:  ivanvenosdel |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Uncategorized|  Version:  1.8
 Severity:  Normal   |   Resolution:
 |  worksforme
 Keywords:  python3.2 python3.3  | Triage Stage:
  find_spec  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by ivanvenosdel):

 I am a bit late but, yes, the new version is great.

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

Re: [Django] #25895: Customizing user admin docs shouldn't override name.

[Django]

#25895: Customizing user admin docs shouldn't override name.
-+-
 Reporter:  justinabrahms|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  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:  1|UI/UX:  0
-+-
Changes (by claudep):

 * stage:  Accepted => Ready for checkin


Comment:

 In release notes, you can let one of MyUserAdmin / BaseUserAdmin as
 UserAdmin.

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

Re: [Django] #25894: Paginator fails with QuerySet returning no values

[Django]

#25894: Paginator fails with QuerySet returning no values
-+
 Reporter:  debnet   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  1.9
 Severity:  Release blocker  |   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 timgraham):

 * stage:  Unreviewed => Accepted


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

Re: [Django] #25895: Customizing user admin docs shouldn't override name.

[Django]

#25895: Customizing user admin docs shouldn't override name.
--+
 Reporter:  justinabrahms |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by justinabrahms):

 Sounds good to me. +1 on change. :)

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

Re: [Django] #25894: Paginator fails with QuerySet returning no values

[Django]

#25894: Paginator fails with QuerySet returning no values
-+--
 Reporter:  debnet   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  1.9
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by sir-sigurd):

 I can reproduce it on 1.9 and can't reproduce it on 1.8.7.

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

Re: [Django] #25893: Custom Lookups & Transform example lhs/rhs swap

[Django]

#25893: Custom Lookups & Transform example lhs/rhs swap
-+-
 Reporter:  browniebroke |Owner:
 Type:   |  browniebroke
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  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 browniebroke):

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

Re: [Django] #25896: SeparateDatabaseAndState.database_backwards() applies state incorrectly (was: SeparateDatabaseAndState database_backwards is broken.)

[Django]

#25896: SeparateDatabaseAndState.database_backwards() applies state incorrectly
+
 Reporter:  amosonn |Owner:  amosonn
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  1.8
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+
Changes (by timgraham):

 * needs_better_patch:  0 => 1
 * stage:  Unreviewed => Accepted


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

Re: [Django] #25895: Customizing user admin docs shouldn't override name.

[Django]

#25895: Customizing user admin docs shouldn't override name.
--+
 Reporter:  justinabrahms |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timgraham):

 * has_patch:  0 => 1


Comment:

 I think `import UserAdmin as BaseUserAdmin` is an okay way to go. Any
 preferences?

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

Re: [Django] #25895: Customizing user admin docs shouldn't override name.

[Django]

#25895: Customizing user admin docs shouldn't override name.
--+
 Reporter:  justinabrahms |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  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 timgraham):

 * Attachment "25895.diff" 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/071.93ba7a80c2faffcc8e144d5381bed28e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25886: Release notes confusion and Django 1.8.8/Python 3.2-3.3 import error

[Django]

#25886: Release notes confusion and Django 1.8.8/Python 3.2-3.3 import error
-+-
 Reporter:  ivanvenosdel |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Uncategorized|  Version:  1.8
 Severity:  Normal   |   Resolution:
 |  worksforme
 Keywords:  python3.2 python3.3  | Triage Stage:
  find_spec  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"e4354d8d7c4af81258132fdd4ff6f643dc301385" e4354d8]:
 {{{
 #!CommitTicketReference repository=""
 revision="e4354d8d7c4af81258132fdd4ff6f643dc301385"
 [1.9.x] Refs #25886 -- Improved language in Python compatibility section
 of the release notes.

 Backport of 26c26e83081d68035d6411b1acc17ba033e1876d 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/070.8b7ade67c5d62379f5d398396de9f91c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25886: Release notes confusion and Django 1.8.8/Python 3.2-3.3 import error

[Django]

#25886: Release notes confusion and Django 1.8.8/Python 3.2-3.3 import error
-+-
 Reporter:  ivanvenosdel |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Uncategorized|  Version:  1.8
 Severity:  Normal   |   Resolution:
 |  worksforme
 Keywords:  python3.2 python3.3  | Triage Stage:
  find_spec  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"975a451153d56561a84d5c2ca692bc10bd656b77" 975a451]:
 {{{
 #!CommitTicketReference repository=""
 revision="975a451153d56561a84d5c2ca692bc10bd656b77"
 [1.8.x] Refs #25886 -- Improved language in Python compatibility section
 of the release notes.

 Backport of 26c26e83081d68035d6411b1acc17ba033e1876d 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/070.047dd28d9edd6c42920971c29897f90b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25886: Release notes confusion and Django 1.8.8/Python 3.2-3.3 import error

[Django]

#25886: Release notes confusion and Django 1.8.8/Python 3.2-3.3 import error
-+-
 Reporter:  ivanvenosdel |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Uncategorized|  Version:  1.8
 Severity:  Normal   |   Resolution:
 |  worksforme
 Keywords:  python3.2 python3.3  | Triage Stage:
  find_spec  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"26c26e83081d68035d6411b1acc17ba033e1876d" 26c26e83]:
 {{{
 #!CommitTicketReference repository=""
 revision="26c26e83081d68035d6411b1acc17ba033e1876d"
 Refs #25886 -- Improved language in Python compatibility section of the
 release notes.
 }}}

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

Re: [Django] #15727: Add support for Content-Security-Policy (CSP) to core

[Django]

#15727: Add support for Content-Security-Policy (CSP) to core
---+
 Reporter:  db.pub.mail@…  |Owner:  Rudolph
 Type:  New feature|   Status:  assigned
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by timgraham):

 Consensus from [https://groups.google.com/d/topic/django-
 developers/OITfIvTOp0A/discussion django-developers] is to add this to
 `SecurityMiddleware`.

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

Re: [Django] #25881: Mark Python 3.2 in Django 1.8 as unsupported at the end of 2016

[Django]

#25881: Mark Python 3.2 in Django 1.8 as unsupported at the end of 2016
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.8
 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 Tim Graham ):

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


Comment:

 In [changeset:"e6bd688ef3b58ee522794dce77f64a81b53b3b9e" e6bd688e]:
 {{{
 #!CommitTicketReference repository=""
 revision="e6bd688ef3b58ee522794dce77f64a81b53b3b9e"
 Fixed #25881 -- Marked Python 3.2 in Django 1.8 as unsupported at the end
 of 2016.
 }}}

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

Re: [Django] #25886: Release notes confusion and Django 1.8.8/Python 3.2-3.3 import error

[Django]

#25886: Release notes confusion and Django 1.8.8/Python 3.2-3.3 import error
-+-
 Reporter:  ivanvenosdel |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Uncategorized|  Version:  1.8
 Severity:  Normal   |   Resolution:
 |  worksforme
 Keywords:  python3.2 python3.3  | Triage Stage:
  find_spec  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by claudep):

 +1 from a poor English speaker

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

Re: [Django] #25881: Mark Python 3.2 in Django 1.8 as unsupported at the end of 2016

[Django]

#25881: Mark Python 3.2 in Django 1.8 as unsupported at the end of 2016
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.8
 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 Tim Graham ):

 In [changeset:"5eeb8edfbbc90d58c76599943282003f3e5ad4fa" 5eeb8edf]:
 {{{
 #!CommitTicketReference repository=""
 revision="5eeb8edfbbc90d58c76599943282003f3e5ad4fa"
 [1.9.x] Fixed #25881 -- Marked Python 3.2 in Django 1.8 as unsupported at
 the end of 2016.

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

Re: [Django] #25881: Mark Python 3.2 in Django 1.8 as unsupported at the end of 2016

[Django]

#25881: Mark Python 3.2 in Django 1.8 as unsupported at the end of 2016
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.8
 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 Tim Graham ):

 In [changeset:"14e1e53a90c80e4d9e9b0f36218f25639a660957" 14e1e53a]:
 {{{
 #!CommitTicketReference repository=""
 revision="14e1e53a90c80e4d9e9b0f36218f25639a660957"
 [1.8.x] Fixed #25881 -- Marked Python 3.2 in Django 1.8 as unsupported at
 the end of 2016.

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

Re: [Django] #25895: Customizing user admin docs shouldn't override name.

[Django]

#25895: Customizing user admin docs shouldn't override name.
--+
 Reporter:  justinabrahms |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  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 claudep):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * version:  1.9 => master
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


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

Re: [Django] #25872: Title attribute for related widget links lacks escaping (and breaks html)

[Django]

#25872: Title attribute for related widget links lacks escaping (and breaks 
html)
-+
 Reporter:  a1tus|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.8
 Severity:  Release blocker  |   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 claudep):

 This was discussed already AFAIR. We have currently no way to tell if the
 markup from a translated string should be escaped or not, as it is
 perfectly legal to mark for translation strings having HTML markup. Until
 now, we simply trust translations, as if they were code. I'm open to some
 strategy to change this behavior if anyone has good ideas.
 Until then, the workaround is to update the translation with escaped
 content.

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

Re: [Django] #25886: Release notes confusion and Django 1.8.8/Python 3.2-3.3 import error

[Django]

#25886: Release notes confusion and Django 1.8.8/Python 3.2-3.3 import error
-+-
 Reporter:  ivanvenosdel |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Uncategorized|  Version:  1.8
 Severity:  Normal   |   Resolution:
 |  worksforme
 Keywords:  python3.2 python3.3  | Triage Stage:
  find_spec  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 Proposal: "The Django 1.8 series is the last to support Python 3.2 and
 3.3."

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

Re: [Django] #25717: Incorrect local language name for slovak language

[Django]

#25717: Incorrect local language name for slovak language
-+-
 Reporter:  azurit   |Owner:
 |  andersonresende
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  1.8
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by claudep):

 * needs_better_patch:  0 => 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/064.c1d54c9c83ea754b145210187e8c542d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25886: Release notes confusion and Django 1.8.8/Python 3.2-3.3 import error

[Django]

#25886: Release notes confusion and Django 1.8.8/Python 3.2-3.3 import error
-+-
 Reporter:  ivanvenosdel |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Uncategorized|  Version:  1.8
 Severity:  Normal   |   Resolution:
 |  worksforme
 Keywords:  python3.2 python3.3  | Triage Stage:
  find_spec  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by claudep):

 I admit that the current formulation is also ambiguous for me (as non-
 native speaker). If we can find something clearer, it would be nice.

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

Re: [Django] #25890: AUTH_USER_MODEL unfriendly to custom models with more than one level of encapsulation

[Django]

#25890: AUTH_USER_MODEL unfriendly to custom models with more than one level of
encapsulation
-+-
 Reporter:  junhua   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  contrib.auth |  Version:  1.9
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  AUTH_USER_MODEL  | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 I have no idea what `apps/authn/CustomUser` means. If your file doesn't
 have at least a `.py` extension nothing's going to work.

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

[Django] #25896: SeparateDatabaseAndState database_backwards is broken.

[Django]

#25896: SeparateDatabaseAndState database_backwards is broken.
+-
 Reporter:  amosonn |  Owner:  amosonn
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  1.8
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  1
Easy pickings:  0   |  UI/UX:  0
+-
 When there are various database ops in SeparateDatabaseAndState, and they
 depend on each other, database_backwards is broken because it applies
 states incorrectly.
 The code exists unchanged in 1.9 and master.
 Test coverage for SeparateDatabaseAndState was incomplete anyway, added a
 more thorough test which breaks, and the bug fix.

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

Re: [Django] #25896: SeparateDatabaseAndState database_backwards is broken.

[Django]

#25896: SeparateDatabaseAndState database_backwards is broken.
+--
 Reporter:  amosonn |Owner:  amosonn
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  1.8
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by amosonn):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 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/065.256924f8271127990b0e8dfc42589fda%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25895: Customizing user admin docs shouldn't override name.

[Django]

#25895: Customizing user admin docs shouldn't override name.
---+
 Reporter:  justinabrahms  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.9
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 
https://github.com/django/django/blob/master/docs/topics/auth/customizing.txt#L342

 In the above documentation, we're inheriting from `UserAdmin` while
 renaming our own class `UserAdmin`.  Instead, we should rename one of the
 two of those so it is more clear (and generally doesn't throw pylint
 errors).

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

Re: [Django] #25888: migrate with "--fake" option modifies the database

[Django]

#25888: migrate with "--fake" option modifies the database
-+-
 Reporter:  mandm|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by mandm):

 Is there a way to undo `--fake` for manually created migrations file (if
 `reverse_sql` isn't available) ?

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

Re: [Django] #25748: Glossary: Project vs App

[Django]

#25748: Glossary: Project vs App
--+
 Reporter:  guettli   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.8
 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 guettli):

 I created a pull request to improve the docs:
 https://github.com/django/django/pull/5788

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

Re: [Django] #25894: Paginator fails with QuerySet returning no values

[Django]

#25894: Paginator fails with QuerySet returning no values
-+--
 Reporter:  debnet   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  1.9
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by timgraham):

 Is this a regression in Django 1.9? Can you provide a test for
 `tests/pagination/tests.py`?

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

Re: [Django] #25876: Remove unused/untested OGRGeometry.transform_to() method (was: deprecate OGRGeometry.transform_to() method)

[Django]

#25876: Remove unused/untested OGRGeometry.transform_to() method
-+-
 Reporter:  sir-sigurd   |Owner:  sir-
 Type:   |  sigurd
  Cleanup/optimization   |   Status:  closed
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 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
-+-

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

Re: [Django] #25876: deprecate OGRGeometry.transform_to() method

[Django]

#25876: deprecate OGRGeometry.transform_to() method
-+-
 Reporter:  sir-sigurd   |Owner:  sir-
 Type:   |  sigurd
  Cleanup/optimization   |   Status:  closed
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 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 Sergey Fedoseev ):

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


Comment:

 In [changeset:"a8614fb438432551e52a818b5f76f48d4ac5b499" a8614fb]:
 {{{
 #!CommitTicketReference repository=""
 revision="a8614fb438432551e52a818b5f76f48d4ac5b499"
 Fixed #25876 -- Removed OGRGeometry.transform_to() backwards-compatibility
 method.
 }}}

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

Re: [Django] #25894: Paginator fails with QuerySet returning no values

[Django]

#25894: Paginator fails with QuerySet returning no values
-+--
 Reporter:  debnet   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  1.9
 Severity:  Release blocker  |   Resolution:
 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 debnet):

 * cc: marc@… (added)
 * needs_docs:   => 0
 * severity:  Normal => Release blocker
 * needs_tests:   => 0
 * needs_better_patch:   => 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.b979b33441d432ade1af152cff39ba7c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25894: Paginator fails with QuerySet returning no values

[Django]

#25894: Paginator fails with QuerySet returning no values
--+
 Reporter:  debnet|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Core (Other)  |Version:  1.9
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 When using a QuerySet returning no values without a whole model behind,
 the Paginator fails to display data from page.

 '''Example OK:'''

 {{{
 queryset = Model.objects.filter(my_filter_return_nothing=value)
 paginator = Paginator(queryset, 10)
 list(paginator.page(1))
 >>> []
 }}}

 '''Example KO:'''

 {{{
 queryset =
 Model.objects.values('whatever_field').filter(my_filter_return_nothing=value)
 paginator = Paginator(queryset, 10)
 list(paginator.page(1))
 >>>
 ---
 AttributeErrorTraceback (most recent call
 last)
  in ()
 > 1 list(paginator.page(1))

 \lib\site-packages\django\core\paginator.py in __len__(self)
 115
 116 def __len__(self):
 --> 117 return len(self.object_list)
 118
 119 def __getitem__(self, index):

 \lib\site-packages\django\db\models\query.py in __len__(self)
 238
 239 def __len__(self):
 --> 240 self._fetch_all()
 241 return len(self._result_cache)
 242

 \lib\site-packages\django\db\models\query.py in _fetch_all(self)
1072 def _fetch_all(self):
1073 if self._result_cache is None:
 -> 1074 self._result_cache = list(self.iterator())
1075 if self._prefetch_related_lookups and not
 self._prefetch_done:
1076 self._prefetch_related_objects()

 \lib\site-packages\django\db\models\query.py in __iter__(self)
 110 names = extra_names + field_names + annotation_names
 111
 --> 112 for row in compiler.results_iter():
 113 yield dict(zip(names, row))
 114

 \lib\site-packages\django\db\models\sql\compiler.py in results_iter(self,
 results)
 805 if results is None:
 806 results = self.execute_sql(MULTI)
 --> 807 fields = [s[0] for s in self.select[0:self.col_count]]
 808 converters = self.get_converters(fields)
 809 for rows in results:

 AttributeError: 'SQLCompiler' object has no attribute 'col_count'
 }}}

 Thanks.

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

Re: [Django] #25893: Custom Lookups & Transform example lhs/rhs swap

[Django]

#25893: Custom Lookups & Transform example lhs/rhs swap
--+
 Reporter:  browniebroke  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  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 MoritzS):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * version:  1.8 => master
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


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

Re: [Django] #25889: Organize tests in tests/queries (was: Organize tests in queries tests)

[Django]

#25889: Organize tests in tests/queries
--+
 Reporter:  claudep   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  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
--+

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

[Django] #25893: Custom Lookups & Transform example lhs/rhs swap

[Django]

#25893: Custom Lookups & Transform example lhs/rhs swap
--+
 Reporter:  browniebroke  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.8
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 In the doc for lookups and transform, in the example on optimizing
 lookups:
 https://docs.djangoproject.com/en/1.9/howto/custom-lookups/#writing-an-
 efficient-abs-lt-lookup

 The paragraph after the code snippets confused me:

   There are a couple of notable things going on. First,
 AbsoluteValueLessThan isn’t calling process_lhs(). Instead it skips the
 transformation of the lhs done by AbsoluteValue and uses the original lhs.
 That is, we want to get 27 not ABS(27)

 I initially though that lhs and rhs were swapped, but after asking on the
 #django IRC channel, I was advised that the confusion come from the last
 sentence, which should actually refer to the left of the SQL, rather than
 the right side:

   That is, we want to get "experiments"."change" not
 ABS("experiments"."change")

 Happy to submit a PR if suggested solution is accepted.

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

Re: [Django] #25892: SeparateDatabaseAndState database_backwards is slow.

[Django]

#25892: SeparateDatabaseAndState database_backwards is slow.
-+-
 Reporter:  amosonn  |Owner:  amosonn
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Migrations   |  Version:  1.8
 Severity:  Normal   |   Resolution:
 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 amosonn):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Old description:

> The database_backwards of SeparateDatabaseAndState runs at O(n^2) where n
> is the number of database_operations. For each operation, it regenerates
> the state up to it from the first operation. Instead, we could cache all
> the intermediate states, similar to the implementation of
> _migrate_all_backwards in the migration executor (or migrate in django
> 1.8.x).

New description:

 The database_backwards of SeparateDatabaseAndState runs at O(n^2^) where n
 is the number of database_operations. For each operation, it regenerates
 the state up to it from the first operation. Instead, we could cache all
 the intermediate states, similar to the implementation of
 _migrate_all_backwards in the migration executor (or migrate in django
 1.8.x).

--

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

[Django] #25892: SeparateDatabaseAndState database_backwards is slow.

[Django]

#25892: SeparateDatabaseAndState database_backwards is slow.
--+-
 Reporter:  amosonn   |  Owner:  amosonn
 Type:  Cleanup/optimization  | Status:  new
Component:  Migrations|Version:  1.8
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+-
 The database_backwards of SeparateDatabaseAndState runs at O(n^2) where n
 is the number of database_operations. For each operation, it regenerates
 the state up to it from the first operation. Instead, we could cache all
 the intermediate states, similar to the implementation of
 _migrate_all_backwards in the migration executor (or migrate in django
 1.8.x).

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

Re: [Django] #15578: loaddata and processing order of fixtures

[Django]

#15578: loaddata and processing order of fixtures
--+
 Reporter:  lsaffre   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.2
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by pakal):

 I'd like to highlight another imprecise point in this documentation
 paragraph : as described in (duplicate) ticket #15578, even if the order
 of fixture import gets precised, users may not always rely on the "in
 transaction" behaviour of loaddata, regarding relationships between
 records.

 Indeed DBs like MySQL do not have defered constraint checking, so
 referential integrity must be true for *each* SQL operation, not just as a
 whole. Others like PostgreSQL can have it on demand
 (http://www.postgresql.org/docs/9.1/static/sql-set-constraints.html), but
 I have alas no experience with these and the way Django uses them.

 Does anybody have experience with loading interdependent fixtures on
 several different engines ? Can we simply state "If your engine supports
 defered constraint checking etc. etc." ?

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

Re: [Django] #25888: migrate with "--fake" option modifies the database

[Django]

#25888: migrate with "--fake" option modifies the database
-+-
 Reporter:  mandm|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jarshwah):

 If you're looking to test the output of the migration perhaps you might
 want to use the sqlmigrate command
 https://docs.djangoproject.com/en/dev/ref/django-admin/#sqlmigrate-app-
 label-migrationname

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

Re: [Django] #25878: APPEND_SLASH doesn't work with DEBUG=False when template/404.html is erroneous

[Django]

#25878: APPEND_SLASH doesn't work with DEBUG=False when template/404.html is
erroneous
---+--
 Reporter:  kuna   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  HTTP handling  |  Version:  1.9
 Severity:  Normal |   Resolution:
 Keywords:  slash,debug| Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by timgraham):

 Can you [https://docs.djangoproject.com/en/dev/internals/contributing
 /triaging-tickets/#bisecting-a-regression bisect] to find the commit where
 the behavior changed? Could you put together a minimal project that
 reproduces the problem? I am not sure whether this is a bug in Django or a
 problem with your application.

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

Re: [Django] #25879: Uncertainty about constraint checks during fixture loading

[Django]

#25879: Uncertainty about constraint checks during fixture loading
---+--
 Reporter:  pakal  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.9
 Severity:  Normal |   Resolution:  duplicate
 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 timgraham):

 * status:  new => closed
 * resolution:   => duplicate


Comment:

 Yes, I think you can add your notes there (or even do some investigation
 about the actual ordering that's used and submit a patch if you have
 time). #15578 is a pure documentation ticket too, as far as I can tell (at
 least, it's component is "Documentation" so no behavior changes are
 expected to be made to resolve it).

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

Re: [Django] #25891: Add an admin widget to display user_permissions in tabular format (was: user_permissions in tabular format)

[Django]

#25891: Add an admin widget to display user_permissions in tabular format
-+-
 Reporter:  RamezIssac   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  admin,   | Triage Stage:
  user_permissions   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by timgraham):

 * status:  new => closed
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0
 * resolution:   => wontfix


Comment:

 Thanks for raising the idea. I think it would be better to implement this
 as a third-party widget, at least initially. If it becomes popular enough,
 we could consider moving it into the admin itself. Feel free to write to
 the DevelopersMailingList when you have something working.

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

Re: [Django] #25889: Organize tests in queries tests (was: Rename tests in queries tests)

[Django]

#25889: Organize tests in queries tests
--+
 Reporter:  claudep   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  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 timgraham):

 * cc: akaariai (added)
 * stage:  Unreviewed => Accepted


Comment:

 I think the issue is that for queries tests, they are not easily
 categorized or described. Many of the tickets are "here is query that
 regressed." If we can break up the single `tests.py` file into multiple
 tests files (perhaps based on the models they use) and `models.py` into a
 package similar to `tests/auth_tests/models`, I think that would be a
 useful task. If we can do some renaming along the way, that seems okay but
 it would be easiest to review in a separate commit from one that moves
 things around.

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

Re: [Django] #25883: Admin Delete Page Incorrectly Counts Related Objects

[Django]

#25883: Admin Delete Page Incorrectly Counts Related Objects
---+--
 Reporter:  jpulec |Owner:  sir-sigurd
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  1.9
 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 sir-sigurd):

 * status:  new => assigned
 * owner:  nobody => sir-sigurd


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

Re: [Django] #25888: migrate with "--fake" option modifies the database

[Django]

#25888: migrate with "--fake" option modifies the database
-+-
 Reporter:  mandm|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 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 sir-sigurd):

 * status:  new => closed
 * needs_better_patch:   => 0
 * resolution:   => invalid
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 This is intended behavior:
 {{{
 python manage.py help migrate
 ...
   --fakeMark migrations as run without actually running
 them.
 ...
 }}}

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

[Django] #25891: user_permissions in tabular format

[Django]

#25891: user_permissions in tabular format
---+-
 Reporter:  RamezIssac |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  contrib.admin  |Version:  master
 Severity:  Normal |   Keywords:  admin, user_permissions
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  1
---+-
 Basic permissions [add, change & delete] can be assigned via a custom
 widget that display them in a tabular format,

 || model verbose_name || add (check-box) || change (check box) || delete
 (check box)

 This proposal would leave other custom permissions to be assigned via the
 currently implemented SelectMultiple, as i think it is messy to try and
 implement them in the table.

 This way is easier when there are alot of models, and will also help with
 ticket #1688 (Permissions don't get translated in admin interface)  as the
 html table will get constructed initially via the models themselves.

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

Re: [Django] #25725: UpdateCacheMiddleware can't cache a generator response

[Django]

#25725: UpdateCacheMiddleware can't cache a generator response
-+-
 Reporter:  dracos   |Owner:  codingjoe
 Type:  Bug  |   Status:  assigned
Component:  Core (Cache system)  |  Version:  1.8
 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 codingjoe):

 * needs_better_patch:  1 => 0


Comment:

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

Re: [Django] #21221: Widgets and Admin's Media should use the configured staticfiles storage to create the right path to a file

[Django]

#21221: Widgets and Admin's Media should use the configured staticfiles storage 
to
create the right path to a file
-+-
 Reporter:  Guilherme Gondim |Owner:  codingjoe
  |
 Type:  Bug  |   Status:  assigned
Component:  contrib.staticfiles  |  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  staticfiles, admin,  | Triage Stage:  Accepted
  CachedFilesMixin, media, widgets   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by codingjoe):

 * needs_better_patch:  1 => 0


Comment:

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

Re: [Django] #25890: AUTH_USER_MODEL unfriendly to custom models with more than one level of encapsulation

[Django]

#25890: AUTH_USER_MODEL unfriendly to custom models with more than one level of
encapsulation
-+-
 Reporter:  junhua   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  contrib.auth |  Version:  1.9
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  AUTH_USER_MODEL  | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by junhua):

 How about a custom User Model that implement AbstractBaseUser, and is
 located at apps/authn/CustomUser?





 Replying to [comment:1 aaugustin]:
 > An application label cannot contain periods.
 >
 > For instance the `User` model of the `django.contrib.auth` app is
 located at `django.contrib.auth.models.User`. The application's name is
 `django.contrib.auth` and its label is `auth`. The default value of
 `AUTH_USER_MODEL` is `auth.User`.

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

Re: [Django] #25879: Uncertainty about constraint checks during fixture loading

[Django]

#25879: Uncertainty about constraint checks during fixture loading
---+--
 Reporter:  pakal  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.9
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by pakal):

 Hum to me these tickets are more complementary than duplicates, mine was
 just a doc update, the #15578 seems to deal with an engine that has no
 "deferred constraint checking" (although i'm not sure that this feature
 would suffice to solve the OP's problem) but proposes changes in the
 behaviour of loaddata instead.

 Should I bring my notes to the other ticket, so that both aspects (docs &
 behaviour) get matched whatever the choices made ?

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

Re: [Django] #25890: AUTH_USER_MODEL unfriendly to custom models with more than one level of encapsulation

[Django]

#25890: AUTH_USER_MODEL unfriendly to custom models with more than one level of
encapsulation
-+-
 Reporter:  junhua   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  contrib.auth |  Version:  1.9
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  AUTH_USER_MODEL  | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * status:  new => closed
 * needs_better_patch:   => 0
 * resolution:   => invalid
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 An application label cannot contain periods.

 For instance the `User` model of the `django.contrib.auth` app is located
 at `django.contrib.auth.models.User`. The application's name is
 `django.contrib.auth` and its label is `auth`. The default value of
 `AUTH_USER_MODEL` is `auth.User`.

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

[Django] #25890: AUTH_USER_MODEL unfriendly to custom models with more than one level of encapsulation

[Django]

#25890: AUTH_USER_MODEL unfriendly to custom models with more than one level of
encapsulation
--+-
 Reporter:  junhua|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  contrib.auth  |Version:  1.9
 Severity:  Normal|   Keywords:  AUTH_USER_MODEL
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+-
 In db/models/utils.py, when model is a string, it's handled by the
 following:

 `app_label, model_name = model.split(".")`

 In the event if AUTH_USER_MODEL has more than a level of encapsulation
 (e.g. "apps/authn/CustomUser"), it throws a ValueError: too many values to
 unpack.

  Suggested fix:

 {{{
 def make_model_tuple(model):
 """
 Takes a model or a string of the form "app_label.ModelName" and
 returns a
 corresponding ("app_label", "modelname") tuple. If a tuple is passed
 in,
 it's assumed to be a valid model tuple already and returned unchanged.
 """
 if isinstance(model, tuple):
 model_tuple = model
 elif isinstance(model, six.string_types):
 strings = model.split(".")
 app_label = ".".join(strings[:-1])
 model_name = strings[-1]
 # app_label, model_name = model.split(".")
 model_tuple = app_label, model_name.lower()
 else:
 model_tuple = model._meta.app_label, model._meta.model_name
 assert len(model_tuple) == 2, "Invalid model representation: %s" %
 model
 return model_tuple
 }}}

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