Re: [Django] #28621: Crash in QuerySet.annotate() with OuterRef

[Django]

#28621: Crash in QuerySet.annotate() with OuterRef
-+-
 Reporter:  Дилян Палаузов   |Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  QuerySet.extra   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by B Martsberger):

 Out of curiosity, why does this fix not qualify for a backport?

-- 
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/072.049183e94c7a68a1d0a439fef48e%40djangoproject.com.

Re: [Django] #30728: Django urls patterns resolver shadowing exceptions thrown everywhere else

[Django]

#30728: Django urls patterns resolver shadowing exceptions thrown everywhere 
else
-+
 Reporter:  Ariel Torti  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Utilities|  Version:  2.2
 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 Tom Forbes):

 Let’s keep it open for now, thank you for your detailed and very helpful
 diagnostics

 Likely the fix will be just “update Python”, but I want to do some digging
 around why exactly this happens and document it here.

-- 
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.87cf1506181b371faa4bdabc7bd31a34%40djangoproject.com.

Re: [Django] #30728: Django urls patterns resolver shadowing exceptions thrown everywhere else

[Django]

#30728: Django urls patterns resolver shadowing exceptions thrown everywhere 
else
-+
 Reporter:  Ariel Torti  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Utilities|  Version:  2.2
 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 Ariel Torti):

 Everything works just fine on Python 3.5.7, apparently it's a bug with
 python itself.
 So the solution would be to update python, do I set the ticket as fixed ?

-- 
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.92438d4c28cec79dc71c4cff0590daf9%40djangoproject.com.

Re: [Django] #30728: Django urls patterns resolver shadowing exceptions thrown everywhere else

[Django]

#30728: Django urls patterns resolver shadowing exceptions thrown everywhere 
else
-+
 Reporter:  Ariel Torti  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Utilities|  Version:  2.2
 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 Ariel Torti):

 * Attachment "output.log" added.

 System information and run output, you can see it appears the issue has
 something to do with race condition because it doesn't trigger everytime I
 run 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.1ac008b373d55093fd21acaf817edfda%40djangoproject.com.

Re: [Django] #30728: Django urls patterns resolver shadowing exceptions thrown everywhere else

[Django]

#30728: Django urls patterns resolver shadowing exceptions thrown everywhere 
else
-+
 Reporter:  Ariel Torti  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Utilities|  Version:  2.2
 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 Ariel Torti):

 * Attachment "bug.zip" added.

 Bundled PoC project

-- 
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.1a0d16228c4841b1c4d01a4635b22998%40djangoproject.com.

Re: [Django] #30728: Django urls patterns resolver shadowing exceptions thrown everywhere else

[Django]

#30728: Django urls patterns resolver shadowing exceptions thrown everywhere 
else
-+
 Reporter:  Ariel Torti  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Utilities|  Version:  2.2
 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 Ariel Torti):

 Replying to [comment:6 Tom Forbes]:
 > Also I cannot see how the given exception ("The included URLconf ...")
 could be caused by the autoreloader. It's triggered from this code:
 >
 > {{{
 > patterns = getattr(self.urlconf_module, "urlpatterns",
 self.urlconf_module)
 > try:
 > iter(patterns)
 > except TypeError:
 > msg = (
 > "The included URLconf '{name}' does not appear to have
 any "
 > "patterns in it. If you see valid patterns in the file
 then "
 > "the issue is probably caused by a circular import."
 > )
 > raise
 ImproperlyConfigured(msg.format(name=self.urlconf_name))
 > }}}
 >
 > If the urls.py code was evaluated at all then this code wouldn't be
 reached and the exception not thrown. So, if this is not something
 specific to the users environment then something very fishy is going on.

 Ok, so to make sure it was not my environment configuration getting on the
 way I tried to reproduce it on a docker container.
 With Python 3.7.0 and Django 2.2.4 (the latest version from pip) it worked
 just right.

 But then I tried running it with Python 3.5.2 (same version as my local
 machine where I have the issue) and I got the
 `django.core.exceptions.ImproperlyConfigured` instead of my exception.
 Apparently is a race condition (maybe?) because when I run it again it
 worked as expected, it failed only sometimes.

 I will attach a file of the system configuration and the output showing it
 doesn't fail every time I run it. There's also the bundled project, can
 you try and check if you can reproduce it using Python 3.5.2

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

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

Re: [Django] #30728: Django urls patterns resolver shadowing exceptions thrown everywhere else

[Django]

#30728: Django urls patterns resolver shadowing exceptions thrown everywhere 
else
-+
 Reporter:  Ariel Torti  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Utilities|  Version:  2.2
 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 Keryn Knight):

 This looks like it could ''possibly'' be the same problem described in
 #30500 (and #30674). As with those, knowing the version of Python being
 used would be useful.

-- 
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.0a471396f09bde7a00e06a236af5af02%40djangoproject.com.

Re: [Django] #30728: Django urls patterns resolver shadowing exceptions thrown everywhere else

[Django]

#30728: Django urls patterns resolver shadowing exceptions thrown everywhere 
else
-+
 Reporter:  Ariel Torti  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Utilities|  Version:  2.2
 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 Tom Forbes):

 Also I cannot see how the given exception ("The included URLconf ...")
 could be caused by the autoreloader. It's triggered from this code:

 {{{
 patterns = getattr(self.urlconf_module, "urlpatterns",
 self.urlconf_module)
 try:
 iter(patterns)
 except TypeError:
 msg = (
 "The included URLconf '{name}' does not appear to have any
 "
 "patterns in it. If you see valid patterns in the file
 then "
 "the issue is probably caused by a circular import."
 )
 raise ImproperlyConfigured(msg.format(name=self.urlconf_name))
 }}}

 If the urls.py code was evaluated at all then this code wouldn't be
 reached and the exception not thrown. So, if this is not something
 specific to the users environment then something very fishy is going on.

-- 
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.15cf56c19dcb0e0f89e843d00f930ca5%40djangoproject.com.

Re: [Django] #30728: Django urls patterns resolver shadowing exceptions thrown everywhere else

[Django]

#30728: Django urls patterns resolver shadowing exceptions thrown everywhere 
else
-+
 Reporter:  Ariel Torti  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Utilities|  Version:  2.2
 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 Tom Forbes):

 I cannot seem to reproduce this with the latest master
 (bb9e82f2748ace292a584841ab9af8696df27f53), even with the same code as the
 description:

 {{{
 Exception in thread django-main-thread:
 Traceback (most recent call last):
   ...
   File "", line 728, in exec_module
   File "", line 219, in
 _call_with_frames_removed
   File
 "/Users/tom/PycharmProjects/test_django_app/test_django_app/urls.py", line
 6, in 
 from test_app import views
   File "/Users/tom/PycharmProjects/test_django_app/test_app/views.py",
 line 6, in 
 raise MyCustomExceptionShadowed('I have a description of your error')
 test_app.views.MyCustomExceptionShadowed: I have a description of your
 error
 }}}

 There is this snippet of code in the autoreloader:

 {{{
 try:
 get_resolver().urlconf_module
 except Exception:
 # Loading the urlconf can result in errors during development.
 # If this occurs then swallow the error and continue.
 pass
 }}}

 which catches the exception (added to fix #30323), but the exception
 should always be re-thrown by the system checks code in `runserver()`, or
 if that's somehow disabled/silenced then when the view is requested.

-- 
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.c1ba90e0960b4d9d32d476713364917e%40djangoproject.com.

Re: [Django] #30686: Improve utils.text.Truncator to use a full HTML parser.

[Django]

#30686: Improve utils.text.Truncator  to use a full HTML parser.
---+
 Reporter:  Thomas Hooper  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Utilities  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Jon Dufresne):

 > To me, at this point, html5lib essentially looks unmaintained.

 I agree with this observation. The previous main maintainer looks to have
 stopped working on the project. Responses to issues and PRs have stopped.

 > Is html5lib in trouble? If so, as a user, what are your plans, if any?
 And from that, what do you think about Django adopting it? What's the
 alternative?

 For my own projects, I'll probably continue using html5lib until its
 staleness creates an observable bug for me. I haven't hit that point yet.

 Bleach, on the other hand, looks like maintenance has slowed, but not
 stopped. I believe they have vendored html5lib to allow them to make
 changes internally. FWIW, I also still use Bleach.

 ---

 I'm not familiar with all the details of this ticket, but would the stdlib
 HTML parser be sufficient?

 https://docs.python.org/3/library/html.parser.html

-- 
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.b93513dceae4c751e6d6dee3d345a209%40djangoproject.com.

Re: [Django] #30728: Django urls patterns resolver shadowing exceptions thrown everywhere else

[Django]

#30728: Django urls patterns resolver shadowing exceptions thrown everywhere 
else
-+
 Reporter:  Ariel Torti  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Utilities|  Version:  2.2
 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 felixxm):

 * cc: Tom Forbes (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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.88659a7ad7bcf5d4669ecaa0e785bd53%40djangoproject.com.

Re: [Django] #30728: Django urls patterns resolver shadowing exceptions thrown everywhere else

[Django]

#30728: Django urls patterns resolver shadowing exceptions thrown everywhere 
else
-+
 Reporter:  Ariel Torti  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Utilities|  Version:  2.2
 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 Claude Paroz):

 * severity:  Normal => Release blocker
 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.9268a1441144bef39734bbdc5926a85f%40djangoproject.com.

Re: [Django] #25499: Distance lookup not possible with a column value as distance

[Django]

#25499: Distance lookup not possible with a column value as distance
--+
 Reporter:  Bibhas C Debnath  |Owner:  Claude Paroz
 Type:  New feature   |   Status:  closed
Component:  GIS   |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  1.10  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Mariusz Felisiak ):

 In [changeset:"bb9e82f2748ace292a584841ab9af8696df27f53" bb9e82f2]:
 {{{
 #!CommitTicketReference repository=""
 revision="bb9e82f2748ace292a584841ab9af8696df27f53"
 Fixed #29955 -- Added support for distance expression to the dwithin
 lookup.

 This was missed when adding support to other distance lookups in
 refs #25499.

 Thanks Peter Bex for the report and Mariusz for testcases.
 }}}

-- 
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.2fb6e0142e8f593f751b985135a1bf80%40djangoproject.com.

Re: [Django] #29955: Support dwithin lookup on F expressions for distance stored in model

[Django]

#29955: Support dwithin lookup on F expressions for distance stored in model
-+-
 Reporter:  Peter Bex|Owner:  Simon
 |  Charette
 Type:  New feature  |   Status:  closed
Component:  GIS  |  Version:  2.1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  distance, query  | Triage Stage:  Accepted
  builder, F expressions |
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:"bb9e82f2748ace292a584841ab9af8696df27f53" bb9e82f2]:
 {{{
 #!CommitTicketReference repository=""
 revision="bb9e82f2748ace292a584841ab9af8696df27f53"
 Fixed #29955 -- Added support for distance expression to the dwithin
 lookup.

 This was missed when adding support to other distance lookups in
 refs #25499.

 Thanks Peter Bex for the report and Mariusz for testcases.
 }}}

-- 
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.854c6dbe3a7080e8bc9045902fac8067%40djangoproject.com.

Re: [Django] #30725: Textbox size of a DateTimeField becomes too small in admin.TabularInline when browser windows is made smaller

[Django]

#30725: Textbox size of a DateTimeField becomes too small in admin.TabularInline
when browser windows is made smaller
-+-
 Reporter:  Basil Eric Rabi  |Owner:  Lionel Bersee
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  2.2
 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:  1
-+-
Changes (by Lionel Bersee):

 * owner:  nobody => Lionel Bersee
 * 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/067.821b9bead1e66d84c9b40b7116333a3a%40djangoproject.com.

Re: [Django] #30725: Textbox size of a DateTimeField becomes too small in admin.TabularInline when browser windows is made smaller

[Django]

#30725: Textbox size of a DateTimeField becomes too small in admin.TabularInline
when browser windows is made smaller
-+
 Reporter:  Basil Eric Rabi  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  2.2
 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:  1
-+

Comment (by felixxm):

 Lionel, feel-free, patch is welcome.

-- 
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.39f0a2ff08ca7a51fb675a75da8e7e7f%40djangoproject.com.

Re: [Django] #30726: 'week' queryset returns no objects

[Django]

#30726: 'week' queryset returns no objects
-+-
 Reporter:  Andrew Williams  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 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 felixxm):

 * status:  new => closed
 * has_patch:  1 => 0
 * version:  2.2 => master
 * resolution:   => needsinfo
 * stage:  Accepted => Unreviewed


Comment:

 I cannot reproduce this issue on Django == 2.2.4 or master. Can you
 provide a sample project?

-- 
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.a652c9e666d8dc16c6a6cabb147d4f9d%40djangoproject.com.

Re: [Django] #30725: Textbox size of a DateTimeField becomes too small in admin.TabularInline when browser windows is made smaller

[Django]

#30725: Textbox size of a DateTimeField becomes too small in admin.TabularInline
when browser windows is made smaller
-+
 Reporter:  Basil Eric Rabi  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  2.2
 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:  1
-+
Changes (by Lionel Bersee):

 * cc: Lionel Bersee (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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.4408a6aa82038ebd95c52ec2643390a4%40djangoproject.com.

Re: [Django] #30725: Textbox size of a DateTimeField becomes too small in admin.TabularInline when browser windows is made smaller

[Django]

#30725: Textbox size of a DateTimeField becomes too small in admin.TabularInline
when browser windows is made smaller
-+
 Reporter:  Basil Eric Rabi  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  2.2
 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:  1
-+

Comment (by Lionel Bersee):

 I would like to pick up and work on this ticket, would this be okay? I am
 a first time contributor.

-- 
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.c17d84db1716753344dfb575155417fe%40djangoproject.com.

Re: [Django] #30200: Add support for using indexes in update() for ArrayFields.

[Django]

#30200: Add support for using indexes in update() for ArrayFields.
-+-
 Reporter:  felixxm  |Owner:  Nasir
 |  Hussain
 Type:  New feature  |   Status:  assigned
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  ArrayField   | Triage Stage:  Accepted
  PostreSQL index update |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Nasir Hussain):

 * status:  new => assigned
 * owner:  (none) => Nasir Hussain


-- 
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.d3af0749f62220993d86f41b3c1a3972%40djangoproject.com.