Re: [Django] #29948: Single empty TransactionTestCase fails with IntegrityError

[Django]

#29948: Single empty TransactionTestCase fails with IntegrityError
---+
 Reporter:  Matt Westcott  |Owner:  (none)
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 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 oliver):

 * owner:  oliver => (none)
 * status:  assigned => new


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

Re: [Django] #28905: Overhaul extra_requires to include more optional dependencies

[Django]

#28905: Overhaul extra_requires to include more optional dependencies
-+-
 Reporter:  Jaap Roes|Owner:  Nick Pope
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Packaging|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  setup optional   | Triage Stage:  Accepted
  dependencies packages  |
  requirements   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Nick Pope):

 * owner:  Niranj Rajasekaran => Nick Pope
 * needs_docs:  1 => 0


Comment:

 New [https://github.com/django/django/pull/10663 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/063.9acf0ffb2927283c4beb3cd1d4760553%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27755: add ModelAdmin.get_inlines() hook to allow set inlines based on the request or model instance.

[Django]

#27755: add ModelAdmin.get_inlines() hook to allow set inlines based on the 
request
or model instance.
-+-
 Reporter:  WeizhongTu   |Owner:  Hidde
 |  Bultsma
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  django,admin,inlines   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Hidde Bultsma):

 * owner:  nobody => Hidde Bultsma
 * status:  new => assigned


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

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

Re: [Django] #27685: Allow autoreloader to use watchman

[Django]

#27685: Allow autoreloader to use watchman
-+-
 Reporter:  Aymeric Augustin |Owner:  Tom
 Type:   |  Forbes
  Cleanup/optimization   |   Status:  assigned
Component:  Utilities|  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 Tom Forbes):

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

Re: [Django] #29722: Add introspection of special table and view types.

[Django]

#29722: Add introspection of special table and view types.
-+-
 Reporter:  Nick Pope|Owner:  Nick Pope
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  postgresql,  | Triage Stage:  Accepted
  introspection, inspectdb, views,   |
  partitions |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Nick Pope):

 * needs_better_patch:  1 => 0


Comment:

 [https://github.com/django/django/pull/10385 PR] for partitions support
 for PostgreSQL updated.

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

Re: [Django] #27080: `as_manager` on QuerySet should pass down `use_in_migrations` to new Manager instance

[Django]

#27080: `as_manager` on QuerySet should pass down `use_in_migrations` to new
Manager instance
-+-
 Reporter:  Leif Denby   |Owner:  Oliver
 |  Newman
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Oliver Newman):

 * status:  new => assigned
 * owner:  nobody => Oliver Newman


Comment:

 I have a tested fix for this, about to submit a PR if such a change is
 still 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 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.51f68bff2e943963a4339fa2276c1e87%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29964: Remove unused template admin/related_widget_wrapper.html

[Django]

#29964: Remove unused template admin/related_widget_wrapper.html
-+-
 Reporter:  Hidde Bultsma|Owner:  Vishvajit
 Type:   |  Pathak
  Cleanup/optimization   |   Status:  closed
Component:  contrib.admin|  Version:  2.1
 Severity:  Normal   |   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"11bcb57ee2064d795f5f596eade244168ef5ed65" 11bcb57e]:
 {{{
 #!CommitTicketReference repository=""
 revision="11bcb57ee2064d795f5f596eade244168ef5ed65"
 Fixed #29964 -- Removed unused admin/related_widget_wrapper.html template.

 Unused since b52c73008a9d67e9ddbb841872dc15cdd3d6ee01.
 }}}

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

Re: [Django] #17: Metasystem optimization: Share select_related in memory

[Django]

#17: Metasystem optimization: Share select_related in memory
-+-
 Reporter:  Adrian Holovaty  |Owner:  Philippe
 |  Raoult
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  feature caching  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by James Pic):

 Thanks for the heads up Tim, will mandate a hacker to give it a try.

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

Re: [Django] #29964: Remove unused template admin/related_widget_wrapper.html

[Django]

#29964: Remove unused template admin/related_widget_wrapper.html
-+-
 Reporter:  Hidde Bultsma|Owner:  Vishvajit
 Type:   |  Pathak
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  2.1
 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 Vishvajit Pathak):

 * status:  new => assigned
 * owner:  nobody => Vishvajit Pathak
 * stage:  Unreviewed => Accepted


Comment:

 [https://github.com/django/django/pull/10662]

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

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

[Django]

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

Comment (by James Pic):

 FTR there is an external solution for this that you can install with PyPi
 package djcli

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

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

[Django] #29964: Remove unused template admin/related_widget_wrapper.html

[Django]

#29964: Remove unused template admin/related_widget_wrapper.html
+
   Reporter:  Hidde Bultsma |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  contrib.admin |Version:  2.1
   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 |
+
 It looks like the ''admin/related_widget_wrapper.html'' template is not
 used anywhere. It was once used by `RelatedFieldWidgetWrapper` until
 commit
 
[https://github.com/django/django/commit/b52c73008a9d67e9ddbb841872dc15cdd3d6ee01
 b52c7300] changed the template to
 ''admin/widgets/related_widget_wrapper.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 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.c6e3a808c8d2068d204d977e8286f7d6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29961: Change-Add-Delete links are visible in tabular inline for foreignkey fields with a HiddenInput widget

[Django]

#29961: Change-Add-Delete links are visible in tabular inline for foreignkey 
fields
with a HiddenInput widget
-+-
 Reporter:  Hidde Bultsma|Owner:  Hidde
 |  Bultsma
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:  admin tabular| Triage Stage:  Accepted
  inline |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Hidde Bultsma):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/10661 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.a9af77a3c54272c4ea2e58a87bc45f94%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29961: Change-Add-Delete links are visible in tabular inline for foreignkey fields with a HiddenInput widget

[Django]

#29961: Change-Add-Delete links are visible in tabular inline for foreignkey 
fields
with a HiddenInput widget
-+-
 Reporter:  Hidde Bultsma|Owner:  Hidde
 |  Bultsma
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:  admin tabular| Triage Stage:  Accepted
  inline |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-

Comment (by Hidde Bultsma):

 Yeah, it looks like it has been there for at least since the admin was re-
 factored in 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 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.2c297239514ae4731b5085d0632fee06%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29963: JsonField should not allows top-level scalar values (was: JsonField validates number as a valid json format)

[Django]

#29963: JsonField should not allows top-level scalar values
--+--
 Reporter:  Khashayar |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  contrib.postgres  |  Version:  master
 Severity:  Normal|   Resolution:  wontfix
 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 Simon Charette):

 * status:  new => closed
 * resolution:   => wontfix
 * component:  Database layer (models, ORM) => contrib.postgres
 * version:  1.11 => master
 * type:  Bug => New feature


Comment:

 Python integers that are serialized to JSON numbers [https://json.org/ are
 valid JSON scalar values just like strings].

 I assume you requesting that only JSON objects should be allowed to be
 provided for top level values for `contrib.postgres.JsonField`. If that's
 your request I'm afraid that it would be backward incompatible. It
 shouldn't be too hard to subclass `JsonField` or provide
 [https://docs.djangoproject.com/en/2.1/ref/validators/#module-
 django.core.validators a validator] to prevent JSON scalar and array
 equivalent values from being provided.

 {{{#!python
 def validate_dict(value):
 if not isinstance(value, dict):
 raise ValidatorError('...')

 class Foo(models.Model):
 data = JsonField(validators=[validate_dict])
 }}}

 I'll close this ticket as ''wontfix'' because of the backward
 compatibility concerns and the small amount of code required to achieve it
 using standard APIs. Feel free to re-open the ticket if I misunderstood
 your request.

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

Re: [Django] #29962: Queryset.explain(verbose=True) doesn't work on non-PostgreSQL backend (was: queryset explain() doesn't work with verbose=True)

[Django]

#29962: Queryset.explain(verbose=True) doesn't work on non-PostgreSQL backend
-+-
 Reporter:  Mohd. Shafikur   |Owner:  nobody
  Rahman |
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.1
  (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 Simon Charette):

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


Comment:

 [https://docs.djangoproject.com/en/2.1/ref/models/querysets/#explain As
 documented] `explain()` accepts backend specific options and the the
 `verbose=True` option is PostgreSQL specific.

 > Some databases accept flags that can return more information about the
 query. Pass these flags as keyword arguments. **For example, when using
 PostgreSQL**:

 I managed to get the exact same error when trying to use `verbose=True`
 with SQLite, which I assume is what you tried doing there, and get a
 ''verbose'' output on PostgreSQL when using the same option.

 In the future please use TicketClosingReasons/UseSupportChannels to
 confirm your issue is a legitimate bug before filling a ticket.

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