Re: [Django] #29232: Add title option for admin filter when providing a field name

[Django]

#29232: Add title option for admin filter when providing a field name
---+
 Reporter:  David Sanders  |Owner:  pdecol
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  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 pdecol):

 * owner:  nobody => pdecol
 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.751339e7410206dc2541bf22116aa5a7%40djangoproject.com.

Re: [Django] #31032: Document the minimal supported version of browsers for the admin

[Django]

#31032: Document the minimal supported version of browsers for the admin
-+-
 Reporter:  Claude Paroz |Owner:  Carlton
 Type:   |  Gibson
  Cleanup/optimization   |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by GitHub ):

 In [changeset:"29e35b9a3e405afe747b9ea8ada31d0448881a40" 29e35b9]:
 {{{
 #!CommitTicketReference repository=""
 revision="29e35b9a3e405afe747b9ea8ada31d0448881a40"
 Refs #31032 -- Removed unnecessary vendor prefixes from admin CSS.

 The CSS properties have been standardized and are available in all
 supported browsers.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.1f01b9a8ff7fc479fc0d37f4ee9cc71c%40djangoproject.com.

Re: [Django] #8408: Add a new meta option: don't do count(*) in admin

[Django]

#8408: Add a new meta option: don't do count(*) in admin
---+---
 Reporter:  LI Daobing |Owner:  Thomas Chaumeny
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+---

Comment (by TapanGujjar):

 Is it possible to have a separate table that keeps the count of all the
 rows in other tables? I am new here and don't know how much 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.72e3e49ed60fcb725fcc193077b769ae%40djangoproject.com.

Re: [Django] #27778: Update unicode documentation for Python 3

[Django]

#27778: Update unicode documentation for Python 3
-+-
 Reporter:  Aymeric Augustin |Owner:
 Type:   |  ChillarAnand
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  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
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"fc0e0876da8b18ac70fc0e90e9fcc4d06682b8cb" fc0e087]:
 {{{
 #!CommitTicketReference repository=""
 revision="fc0e0876da8b18ac70fc0e90e9fcc4d06682b8cb"
 [3.0.x] Refs #27778 -- Removed reference to ASCII usernames in
 django.contrib.auth.models.User docs.

 Backport of 505b7b616320b8d5bbc83d0dbbb3aec3a58ba0c9 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.87ee9ba12613d12e79ad101e29c82afa%40djangoproject.com.

Re: [Django] #27778: Update unicode documentation for Python 3

[Django]

#27778: Update unicode documentation for Python 3
-+-
 Reporter:  Aymeric Augustin |Owner:
 Type:   |  ChillarAnand
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  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
-+-

Comment (by GitHub ):

 In [changeset:"505b7b616320b8d5bbc83d0dbbb3aec3a58ba0c9" 505b7b6]:
 {{{
 #!CommitTicketReference repository=""
 revision="505b7b616320b8d5bbc83d0dbbb3aec3a58ba0c9"
 Refs #27778 -- Removed reference to ASCII usernames in
 django.contrib.auth.models.User docs.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.2a5eec4f66b0a4b4d3047a7e454597a6%40djangoproject.com.

Re: [Django] #20347: Add an absolute_max parameter to formset_factory

[Django]

#20347: Add an absolute_max parameter to  formset_factory
---+---
 Reporter:  Carsten Fuchs  |Owner:  David Smith
 Type:  New feature|   Status:  assigned
Component:  Forms  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+---
Changes (by felixxm):

 * version:  1.5 => master


Comment:

 [https://github.com/django/django/pull/12830 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.16882b8a40338787dd00cb952ef14eb5%40djangoproject.com.

Re: [Django] #9107: URL arguments to set values of fields in admin don't work for inlines

[Django]

#9107: URL arguments to set values of fields in admin don't work for inlines
---+---
 Reporter:  josh@… |Owner:  TapanGujjar
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  admin inline   | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+---
Changes (by TapanGujjar):

 * owner:  nobody => TapanGujjar
 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/075.c178e8baae6801eb5c76ea35a494f177%40djangoproject.com.

Re: [Django] #31522: FilteredSelectMultiple widget jumps to top when an option is added.

[Django]

#31522: FilteredSelectMultiple widget jumps to top when an option is added.
-+-
 Reporter:  Shai Berger  |Owner:
 Type:   |  TapanGujjar
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  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:  1
-+-
Changes (by TapanGujjar):

 * has_patch:  0 => 1


Comment:

 https://github.com/django/django/pull/12833

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.f9851daa5857a43e52731ba3ff3d436f%40djangoproject.com.

Re: [Django] #20347: Add an absolute_max parameter to formset_factory

[Django]

#20347: Add an absolute_max parameter to  formset_factory
---+---
 Reporter:  Carsten Fuchs  |Owner:  David Smith
 Type:  New feature|   Status:  assigned
Component:  Forms  |  Version:  1.5
 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 David Smith):

 * owner:  ethurgood => David Smith
 * needs_better_patch:  1 => 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.66bc1368f489195255e7eddf9f9238b3%40djangoproject.com.

Re: [Django] #31504: Allow makemigrations to skip database consistency checks

[Django]

#31504: Allow makemigrations to skip database consistency checks
-+
 Reporter:  Tom Forbes   |Owner:  wtkm11
 Type:  New feature  |   Status:  assigned
Component:  Migrations   |  Version:  3.0
 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 wtkm11):

 * needs_better_patch:  1 => 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/061.71d17fbdfbebb76d0bc831dfb6895d85%40djangoproject.com.

Re: [Django] #31504: Allow makemigrations to skip database consistency checks

[Django]

#31504: Allow makemigrations to skip database consistency checks
-+
 Reporter:  Tom Forbes   |Owner:  wtkm11
 Type:  New feature  |   Status:  assigned
Component:  Migrations   |  Version:  3.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+

Comment (by wtkm11):

 I updated the PR so that a CommandError describing the error that was
 encountered in check_consistent_history will be raised.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/061.c9c4e459cec74241f14c58e33294b699%40djangoproject.com.

Re: [Django] #31527: Admindocs' View index assumes settings.ROOT_URLCONF is an import string

[Django]

#31527: Admindocs' View index assumes settings.ROOT_URLCONF is an import string
--+
 Reporter:  Keryn Knight  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admindocs |  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 Carlton Gibson):

 * type:  Uncategorized => Cleanup/optimization


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.eab56197393bb8ae3b9f5af63cfb844b%40djangoproject.com.

Re: [Django] #31527: Admindocs' View index assumes settings.ROOT_URLCONF is an import string

[Django]

#31527: Admindocs' View index assumes settings.ROOT_URLCONF is an import string
---+
 Reporter:  Keryn Knight   |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  contrib.admindocs  |  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 Carlton Gibson):

 * stage:  Unreviewed => Accepted


Comment:

 Thanks for the update Keryn. Let's accept this, since it seems we could
 investigate bullet proofing the admindoc view there.

 Nice example.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.5035e9e4b3d3bf991316fbc4cceec32b%40djangoproject.com.

Re: [Django] #31358: Increase default password salt size in BasePasswordHasher.

[Django]

#31358: Increase default password salt size in BasePasswordHasher.
--+
 Reporter:  Jon Moroney   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Utilities |  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
--+

Comment (by Jon Moroney):

 Checking in again just to make sure this doesn't get lost.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.b38f0bf16c5b84ee9f950cae8389091b%40djangoproject.com.

Re: [Django] #31527: Admindocs' View index assumes settings.ROOT_URLCONF is an import string

[Django]

#31527: Admindocs' View index assumes settings.ROOT_URLCONF is an import string
---+--
 Reporter:  Keryn Knight   |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  contrib.admindocs  |  Version:  master
 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 Keryn Knight):

 > Docs have it thus [...]
 > So I'm kind of inclined towards `wontfix`. `ViewIndexView` is making a
 reasonable assumption.

 It is making a generally reasonable assumption, but it's an ''assumption''
 which is ''sort of'' wrong.
 The documentation is also misleading anyway, because it says **Not
 defined** is the default which is ... true (being that it's not in
 `global_settings`), but at least on 2.2, not having a `ROOT_URLCONF` is
 your project settings is an `AttributeError`:
 {{{
 /path/to/python3.7/site-packages/django/core/handlers/base.py", line 74,
 in get_response
 set_urlconf(settings.ROOT_URLCONF)
 AttributeError: 'Settings' object has no attribute 'ROOT_URLCONF'
 }}}
 So `ROOT_URLCONF` must be set, fine. It is on any given `startproject`
 driven package anyway. Let's set it to something which might be
 ''considered'' "not defined" and do  `ROOT_URLCONF = None` because we know
 [https://docs.djangoproject.com/en/3.0/topics/http/urls/#how-django-
 processes-a-request how Django processes a request must allow for some
 variation upon it...] and use a middleware instead:
 {{{
 class URLPatternsMW(MiddlewareMixin):
 def process_request(self, request):
 request.urlconf = urlpatterns()
 }}}

 That works fine, and lo we can navigate to the admin and all around it as
 you might expect (and also most of admindocs, because in my original
 ticket I stupidly omitted that route from the `urlpatterns()` definition).
 But if we try to go to the same URL as before (`/admin/doc/views/`), we
 get the same principle error, but on a different type:
 {{{
 'NoneType' object has no attribute 'startswith'
 }}}

 Perhaps we should've set `ROOT_URLCONF = ""` and tried that instead:
 {{{
 Exception Type: ValueError at /admin/doc/views/
 Exception Value: Empty module name
 }}}

 It also cannot be a `"myproject.urls"` where there's no `urlpatterns`
 attribute, but it **can** if `urlpatterns = []` is within that module -
 that's at least dealt with by the checks framework. So I guess that's the
 ''actual intended'' way of having no root urlconf to speak of... Ten years
 in, and I didn't actually know that :)
 `ROOT_URLCONF` can be `()` and it's also seemingly fine (because
 `set_urlconf` does the weaker ''falsy'' test), again except for this
 import expectation. Mostly because these things are hashable.

 > Can I ask what the use-case here is? (Also: How does it go with tests
 and override_settings and such? Is this literally the only place it blows
 up?)

 It's actually specifically within tests where I found it (or remembered
 it, I do think I encountered it before but just moved on with life), by
 doing:
 {{{
 if __name__ == "__main__":
 def urlpatterns(...):
 return ()
 settings.configure(ROOT_URLCONF=SimpleLazyObject(urlpatterns), ...)
 django.setup()
 run the tests etc.
 }}}
 I happen to "know" (hah!) using the deferred object mostly seems to work
 from other weird hacks and things I've played around with over the years
 (I think for example I may've been doing something similar in #26287), but
 I cannot say with certainty that it's the **only** place it poses an error
 (and certainly a bunch of downstream packages would make the same
 assumption).
 I can say that it's the only place in Django where I **know** the error
 can happen, being that it's the only place which directly tries to
 **import** the value of `ROOT_URLCONF`, where most everything else handles
 it further down the resolver stack.

 A cursory glancing guess (as is always my way, I'm afraid) at a fix is
 something more like:
 {{{
 urlconf = get_resolver(settings.ROOT_URLCONF)
 try:
 view_functions =
 extract_views_from_urlpatterns(urlconf.url_patterns)
 except ImproperlyConfigured:
 view_functions = []
 }}}
 which is more like what everything else looks to do (using the threadlocal
 resolver). I don't offer that up as the full solution, but a possible
 direction in which a correction might be found.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You re

Re: [Django] #31527: Admindocs' View index assumes settings.ROOT_URLCONF is an import string

[Django]

#31527: Admindocs' View index assumes settings.ROOT_URLCONF is an import string
---+--
 Reporter:  Keryn Knight   |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  contrib.admindocs  |  Version:  master
 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 Carlton Gibson):

 Hi.

 Docs have it thus:

 > `ROOT_URLCONF`: A string representing the full Python import path to
 your root URLconf, for example "mydjangoapps.urls". ...

 So I'm kind of inclined towards `wontfix`. `ViewIndexView` is making a
 reasonable assumption.

 > Bt, it's possible to get Django to otherwise run with, for
 example, something like...

 Can I ask what the use-case here is? (Also: How does it go with tests and
 override_settings and such? Is this literally the only place it blows up?)

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.4dbf5ae611b1eee19c187a07c51d7979%40djangoproject.com.

Re: [Django] #20581: Support DEFERRABLE INITIALLY DEFERRED for UNIQUE constraints

[Django]

#20581: Support DEFERRABLE INITIALLY DEFERRED for UNIQUE constraints
-+-
 Reporter:  dmadeley@…   |Owner:  Ian Foote
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  db-indexes   | 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 Mariusz Felisiak ):

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


Comment:

 In [changeset:"c226c6cb3209122b6732fd501e2994c408dc258e" c226c6cb]:
 {{{
 #!CommitTicketReference repository=""
 revision="c226c6cb3209122b6732fd501e2994c408dc258e"
 Fixed #20581 -- Added support for deferrable unique constraints.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/085.2dcdda87d81eff9c27e3cb6fe2bb4a98%40djangoproject.com.

[Django] #31527: Admindocs' View index assumes settings.ROOT_URLCONF is an import string

[Django]

#31527: Admindocs' View index assumes settings.ROOT_URLCONF is an import string
-+
   Reporter:  Keryn Knight   |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  contrib.admindocs  |Version:  master
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 Currently, the code looks like:
 {{{
 urlconf = import_module(settings.ROOT_URLCONF)
 view_functions = extract_views_from_urlpatterns(urlconf.urlpatterns)
 }}}

 Bt, it's possible to get Django to otherwise run with, for
 example, something like:
 {{{
 def urlpatterns():
 from django.urls import path
 from django.contrib import admin
 return (
 path("admin/", admin.site.urls),
 )

 ROOT_URLCONF = SimpleLazyObject(urlpatterns)
 }}}

 which will happily pass through the checks framework, and runserver (and
 gunicorn), and let you use Django as you otherwise would... except for
 navigating to `django.contrib.admindocs.views.ViewIndexView` (for example,
 routed at `/admin/doc/views/`) where you'll instead encounter an exception
 like:
 {{{
 File "/path/to/python3.7/site-packages/django/contrib/admindocs/views.py"
 in dispatch
   46. return super().dispatch(request, *args, **kwargs)

 File "/path/to/python3.7/site-packages/django/views/generic/base.py" in
 dispatch
   97. return handler(request, *args, **kwargs)

 File "/path/to/python3.7/site-packages/django/views/generic/base.py" in
 get
   158. context = self.get_context_data(**kwargs)

 File "/path/to/python3.7/site-packages/django/contrib/admindocs/views.py"
 in get_context_data
   139. urlconf = import_module(settings.ROOT_URLCONF)

 File "/path/to/python3.7/importlib/__init__.py" in import_module
   118. if name.startswith('.'):

 File "/path/to/python3.7/site-packages/django/utils/functional.py" in
 inner
   257. return func(self._wrapped, *args)


 Exception Type: AttributeError at /admin/doc/views/
 Exception Value: 'tuple' object has no attribute 'startswith'
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.4d4eb678d194ac48b497375bc50d6575%40djangoproject.com.

Re: [Django] #20581: Support DEFERRABLE INITIALLY DEFERRED for UNIQUE constraints

[Django]

#20581: Support DEFERRABLE INITIALLY DEFERRED for UNIQUE constraints
-+-
 Reporter:  dmadeley@…   |Owner:  Ian Foote
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  db-indexes   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * stage:  Accepted => Ready for checkin


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/085.a73b65a75f28e9d01c135e8259dbda90%40djangoproject.com.