Re: [Django] #26090: Changing a ForeignKey to a OneToOne field leaves an extraneous index behind

2016-06-29 Thread Django 
#26090: Changing a ForeignKey to a OneToOne field leaves an extraneous index 
behind
+
 Reporter:  aaugustin   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  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 jdufresne):

 * cc: jon.dufresne@… (added)
 * has_patch:  0 => 1


Comment:

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

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

Re: [Django] #25317: Altering a 1to1 field to FK on Postgres drops uniqueness but does not create index

2016-06-29 Thread Django 
#25317: Altering a 1to1 field to FK on Postgres drops uniqueness but does not
create index
+
 Reporter:  synotna |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  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 jdufresne):

 * has_patch:  0 => 1


Comment:

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

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

Re: [Django] #21523: Models DateField to_python method no longer supports mock dates.

2016-06-29 Thread Django 
#21523: Models DateField to_python method no longer supports mock dates.
-+-
 Reporter:  hugo@…   |Owner:
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |
 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 akki):

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

Re: [Django] #26001: Make ModelAdmin.search_fields do an integer lookup for IntegerFields

2016-06-29 Thread Django 
#26001: Make ModelAdmin.search_fields do an integer lookup for IntegerFields
--+
 Reporter:  timgraham |Owner:
 Type:  Cleanup/optimization  |   Status:  new
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 akki):

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

Re: [Django] #26605: Abstract model inheriting concrete model crashes migrations

2016-06-29 Thread Django 
#26605: Abstract model inheriting concrete model crashes migrations
+
 Reporter:  sebdiem |Owner:
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.8
 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 akki):

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

[Django] #26820: Reverse join in `exclude` fails when GenericRelation is defined on an abstract model

2016-06-29 Thread Django 
#26820: Reverse join in `exclude` fails when GenericRelation is defined on an
abstract model
--+
 Reporter:  sbussetti |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.9
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Exact same use case and setup as #20378.  passing the reverse for a
 GenericRelation to QuerySet.filter works just fine, but for
 QuerySet.exclude it fails with AttributeError: 'GenericRelation' object
 has no attribute 'field'

 {{{
 AttributeErrorTraceback (most recent call
 last)
  in ()
 > 1 Comment.objects.exclude(list_set__comments_enabled=False)

 ./lib/python2.7/site-packages/django/db/models/manager.pyc in
 manager_method(self, *args, **kwargs)
 120 def create_method(name, method):
 121 def manager_method(self, *args, **kwargs):
 --> 122 return getattr(self.get_queryset(), name)(*args,
 **kwargs)
 123 manager_method.__name__ = method.__name__
 124 manager_method.__doc__ = method.__doc__

 ./lib/python2.7/site-packages/django/db/models/query.pyc in exclude(self,
 *args, **kwargs)
 795 set.
 796 """
 --> 797 return self._filter_or_exclude(True, *args, **kwargs)
 798
 799 def _filter_or_exclude(self, negate, *args, **kwargs):
 ./lib/python2.7/site-packages/django/db/models/query.pyc in
 _filter_or_exclude(self, negate, *args, **kwargs)
 804 clone = self._clone()
 805 if negate:
 --> 806 clone.query.add_q(~Q(*args, **kwargs))
 807 else:
 808 clone.query.add_q(Q(*args, **kwargs))

 ./lib/python2.7/site-packages/django/db/models/sql/query.pyc in
 add_q(self, q_object)
1241 existing_inner = set(
1242 (a for a in self.alias_map if
 self.alias_map[a].join_type == INNER))
 -> 1243 clause, _ = self._add_q(q_object, self.used_aliases)
1244 if clause:
1245 self.where.add(clause, AND)

 ./lib/python2.7/site-packages/django/db/models/sql/query.pyc in
 _add_q(self, q_object, used_aliases, branch_negated, current_negated,
 allow_joins, split_subq)
1267 child, can_reuse=used_aliases,
 branch_negated=branch_negated,
1268 current_negated=current_negated,
 connector=connector,
 -> 1269 allow_joins=allow_joins,
 split_subq=split_subq,
1270 )
1271 joinpromoter.add_votes(needed_inner)

 ./lib/python2.7/site-packages/django/db/models/sql/query.pyc in
 build_filter(self, filter_expr, branch_negated, current_negated,
 can_reuse, connector, allow_joins, split_subq)
1179 except MultiJoin as e:
1180 return self.split_exclude(filter_expr,
 LOOKUP_SEP.join(parts[:e.level]),
 -> 1181   can_reuse,
 e.names_with_path)
1182
1183 if can_reuse is not None:

 ./lib/python2.7/site-packages/django/db/models/sql/query.pyc in
 split_exclude(self, filter_expr, prefix, can_reuse, names_with_path)
1497 # Try to have as simple as possible subquery -> trim
 leading joins from
1498 # the subquery.
 -> 1499 trimmed_prefix, contains_louter =
 query.trim_start(names_with_path)
1500
1501 # Add extra check to make sure the selected field will not
 be null

 ./lib/python2.7/site-packages/django/db/models/sql/query.pyc in
 trim_start(self, names_with_path)
1932 self.unref_alias(alias)
1933 # The path.join_field is a Rel, lets get the other side's
 field
 -> 1934 join_field = path.join_field.field
1935 # Build the filter prefix.
1936 paths_in_prefix = trimmed_paths

 AttributeError: 'GenericRelation' object has no attribute 'field'
 }}}

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

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

Re: [Django] #21548: Add the ability to limit file extensions for ImageField and FileField

2016-06-29 Thread Django 
#21548: Add the ability to limit file extensions for ImageField and FileField
-+-
 Reporter:  timo |Owner:  berkerpeksag
 Type:  New feature  |   Status:  assigned
Component:  Forms|  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:  0|UI/UX:  0
-+-
Changes (by timgraham):

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

Re: [Django] #26819: Using a ArrayField on Meta.unique_together throws "unhashable type: 'list'" on validate_unique method

2016-06-29 Thread Django 
#26819: Using a ArrayField on Meta.unique_together throws "unhashable type: 
'list'"
on validate_unique method
--+
 Reporter:  gleber-diniz  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.postgres  |  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 timgraham):

 * needs_better_patch:   => 0
 * component:  Uncategorized => contrib.postgres
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Bug
 * 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.dfb701ce39c92fadd520a73a4d4bdf2f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25694: Migrate command creates a default index for a CharField with a wrong '_uniq' suffix in the name

2016-06-29 Thread Django 
#25694: Migrate command creates a default index for a CharField with a wrong
'_uniq' suffix in the name
+
 Reporter:  synasius|Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  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:"16614dcd5cad50648ef75021b919fc90dd449312" 16614dc]:
 {{{
 #!CommitTicketReference repository=""
 revision="16614dcd5cad50648ef75021b919fc90dd449312"
 Fixed #25694 -- Removed incorrect _uniq suffix on index names during
 migrations.
 }}}

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

Re: [Django] #19513: update() after annotate(val=Sum(...)) crashes on PostgreSQL & Oracle

2016-06-29 Thread Django 
#19513: update() after annotate(val=Sum(...)) crashes on PostgreSQL & Oracle
-+-
 Reporter:  mengzhuo1203@…   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"a84344bc539c66589c8d4fe30c6ceaecf8ba1af3" a84344bc]:
 {{{
 #!CommitTicketReference repository=""
 revision="a84344bc539c66589c8d4fe30c6ceaecf8ba1af3"
 Fixed #19513, #18580 -- Fixed crash on QuerySet.update() after annotate().
 }}}

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

Re: [Django] #18580: Avoiding SQLite update+annotations "only a single result allowed for a SELECT that is part of an expression"

2016-06-29 Thread Django 
#18580: Avoiding SQLite update+annotations "only a single result allowed for a
SELECT that is part of an expression"
-+-
 Reporter:  jonash   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |
 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:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"a84344bc539c66589c8d4fe30c6ceaecf8ba1af3" a84344bc]:
 {{{
 #!CommitTicketReference repository=""
 revision="a84344bc539c66589c8d4fe30c6ceaecf8ba1af3"
 Fixed #19513, #18580 -- Fixed crash on QuerySet.update() after annotate().
 }}}

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

Re: [Django] #26818: Django Admin Responsive

2016-06-29 Thread Django 
#26818: Django Admin Responsive
---+--
 Reporter:  henriquechehad |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  contrib.admin  |  Version:  1.9
 Severity:  Normal |   Resolution:  needsinfo
 Keywords:  admin, responsive  | Triage Stage:  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
 * resolution:   => needsinfo
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 The last I heard of the idea was [https://groups.google.com/d/msg/django-
 developers/HJAikaEBqJ4/GrtyELWDOtYJ during the 1.9 release cycle] when
 Elky worked on the redesign:

  I don't plan to make admin responsive yet (to make it perfectly
 accessible on mobile) - just because we can't control third-party apps.
 Ideally django should have its own css framework for that but not in near
 future I think.

 Someone interested in working on this will need to write a proposal to the
 DevelopersMailingList. Until that happens, I think the idea isn't concrete
 enough to keep a ticket open about 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/072.58d5ad27aa0622f0b9eafb1d8be6c995%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26819: Using a ArrayField on Meta.unique_together throws "unhashable type: 'list'" on validate_unique method

2016-06-29 Thread Django 
#26819: Using a ArrayField on Meta.unique_together throws "unhashable type: 
'list'"
on validate_unique method
---+
 Reporter:  gleber-diniz   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.9
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 It happens on a second save (when there is already data to be validated)

 On this line: "if row_data in seen_data:", because row_data contains a
 list and seen_data is a set (row_data: (1, [1, 1]) / seen_data: set())

 Example to reproduce:

 models:
 {{{#!python
 class Map(models.Model):
 name = models.CharField(_('name'), max_length=128)


 class MapSpot(models.Model):
 map = models.ForeignKey('body.Map', related_name='spots')
 position = ArrayField(models.IntegerField(), size=2)

 class Meta:
 unique_together = [('map', 'position')]
 }}}

 admin:
 {{{#!python
 class MapSpotInline(admin.TabularInline):
 model = MapSpot
 extra = 0


 @admin.register(Map)
 class MapAdmin(admin.ModelAdmin):
 inlines = [MapSpotInline]
 }}}

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

[Django] #26818: Django Admin Responsive

2016-06-29 Thread Django 
#26818: Django Admin Responsive
+---
 Reporter:  henriquechehad  |  Owner:  nobody
 Type:  New feature | Status:  new
Component:  contrib.admin   |Version:  1.9
 Severity:  Normal  |   Keywords:  admin, responsive
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  1
+---
 There is expectancy about responsive admin layouts?

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

Re: [Django] #26817: Document downsides and alternatives of Jinja2 context processors

2016-06-29 Thread Django 
#26817: Document downsides and alternatives of Jinja2 context processors
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  1.11  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by berkerpeksag):

 * cc: berker.peksag@… (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/067.22cb30ca3434f73fbd62ec71223bd3af%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26816: BaseModelAdminChecks._check_inlines_item may raise AttributeError

2016-06-29 Thread Django 
#26816: BaseModelAdminChecks._check_inlines_item may raise AttributeError
--+
 Reporter:  kezabelle |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (System checks)  |  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
--+

Comment (by kezabelle):

 Additional addendum:
 {{{
 class MyInline(BaseModelAdmin):
 model = MyModel
 }}}
 will also fail it seems, because `BaseModelAdmin` doesn't have the same
 `__init__` argspec as `InlineModelAdmin`:
 {{{
 TypeError: __init__() takes 1 positional argument but 3 were given
 }}}

 I suppose the simplest fix is to check the inline is a subclass of
 `InlineModelAdmin`.

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

Re: [Django] #26816: BaseModelAdminChecks._check_inlines_item may raise AttributeError

2016-06-29 Thread Django 
#26816: BaseModelAdminChecks._check_inlines_item may raise AttributeError
--+
 Reporter:  kezabelle |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (System checks)  |  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 timgraham):

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

[Django] #26816: BaseModelAdminChecks._check_inlines_item may raise AttributeError

2016-06-29 Thread Django 
#26816: BaseModelAdminChecks._check_inlines_item may raise AttributeError
--+
 Reporter:  kezabelle |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Core (System checks)  |Version:  1.9
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 given something like:
 {{{
 class MyInline(object): pass

 class MyModelAdmin(admin.ModelAdmin):
 inlines = [MyInline]
 }}}
 '''admin.E104''' will be added to the error stack because its not a
 subclass (ugh) of BaseModelAdmin.

 changing to:
 {{{
 class MyInline(BaseModelAdmin): pass
 }}}
 will throw:
 {{{
 AttributeError: type object 'MyInline'  has no attribute 'model'
 }}}
 because its not until `ModelAdmin` or `InlineModelAdmin` that the
 attribute is set (in `__init__` for `ModelAdmin`, as a class attribute for
 `InlineModelAdmin`)

 Encountered on 1.9, but looks to be the same in 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/052.a154879d9500221b5e0b46ca509e199b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24694: Add support for OPTIONS['context_processors'] to Jinja2 template backend

2016-06-29 Thread Django 
#24694: Add support for OPTIONS['context_processors'] to Jinja2 template backend
-+
 Reporter:  carljm   |Owner:  berkerpeksag
 Type:  New feature  |   Status:  closed
Component:  Template system  |  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
-+

Comment (by timgraham):

 Sorry, I didn't read that entire discussion. I created #26817 for that
 documentation.

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

[Django] #26817: Document downsides and alternatives of Jinja2 context processors

2016-06-29 Thread Django 
#26817: Document downsides and alternatives of Jinja2 context processors
+
   Reporter:  timgraham |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Documentation |Version:  master
   Severity:  Normal|   Keywords:  1.11
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 See the IRC discussion in the description of #24694 and
 ticket:24694#comment: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/052.5a84d161487ab2052b6911afef1dde88%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25694: Migrate command creates a default index for a CharField with a wrong '_uniq' suffix in the name

2016-06-29 Thread Django 
#25694: Migrate command creates a default index for a CharField with a wrong
'_uniq' suffix in the name
+
 Reporter:  synasius|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  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 jdufresne):

 * needs_better_patch:  1 => 0


Comment:

 > Good. That makes the proposal redundant.

 Ok thanks. Then I will proceed.

 I have updated the test to work with Oracle.

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

Re: [Django] #26693: RenameModel causes state.apps rendering leading to massive time increase in makemigrations

2016-06-29 Thread Django 
#26693: RenameModel causes state.apps rendering leading to massive time 
increase in
makemigrations
--+
 Reporter:  simonpercivall|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  1.9
 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
--+
Changes (by vinayinvicible):

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

Re: [Django] #26693: RenameModel causes state.apps rendering leading to massive time increase in makemigrations

2016-06-29 Thread Django 
#26693: RenameModel causes state.apps rendering leading to massive time 
increase in
makemigrations
--+
 Reporter:  simonpercivall|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  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
--+

Comment (by vinayinvicible):

 I recently came across this issue and the above patch fixed 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/072.ffd8689fa9828a81b7d2e526158836b0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26693: RenameModel causes state.apps rendering leading to massive time increase in makemigrations

2016-06-29 Thread Django 
#26693: RenameModel causes state.apps rendering leading to massive time 
increase in
makemigrations
--+
 Reporter:  simonpercivall|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  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 vinayinvicible):

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

Re: [Django] #26815: Addition of Trunc may have altered the ordering of dates() queries

2016-06-29 Thread Django 
#26815: Addition of Trunc may have altered the ordering of dates() queries
-+-
 Reporter:  Kazade   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  dates, queryset  | 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):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Could you provide example queries to demonstrate the bug?

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

Re: [Django] #26803: Add a statistics option to makemessages (was: Allow makemessages to be used for validation of gettext files)

2016-06-29 Thread Django 
#26803: Add a statistics option to makemessages
--+
 Reporter:  vzima |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Internationalization  |  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 claudep):

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

Re: [Django] #26803: Allow makemessages to be used for validation of gettext files

2016-06-29 Thread Django 
#26803: Allow makemessages to be used for validation of gettext files
-+-
 Reporter:  vzima|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:   |  Version:  master
  Internationalization   |
 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 vzima):

 If it also returns appropriate exit code, similar to `makemigrations
 --exit`, then yes.

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

[Django] #26815: Addition of Trunc may have altered the ordering of dates() queries

2016-06-29 Thread Django 
#26815: Addition of Trunc may have altered the ordering of dates() queries
--+
 Reporter:  Kazade|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.10
 Severity:  Normal|   Keywords:  dates,
  |  queryset
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 We're looking into supporting Django 1.10 in Djangae, and while fixing up
 some breakages I noticed a change in the way that dates() queries are
 ordered. I'm not 100% sure this is a real bug as I'm looking at the code
 in a fairly abnormal situation, but it definitely seems like a bug...

 This line was recently added as part of the datetime expression changes:

 
https://github.com/django/django/commit/2a4af0ea43512370764303d35bc5309f8abce666
 #diff-5b0dda5eb9a242c15879dc9cd2121379R743

 It seems to me that now, instead of ordering by the full date, this change
 will make dates queries order by just the component that they are
 selecting (e.g. year, month, day etc.) - although I might be wrong about
 this!

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

Re: [Django] #24096: GROUP BY on oracle fails with TextField and BinaryField

2016-06-29 Thread Django 
#24096: GROUP BY on oracle fails with TextField and BinaryField
-+-
 Reporter:  jarshwah |Owner:  nobody
 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
-+-
Changes (by robin):

 * cc: robinchew@… (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/066.6b2742c9a770f9b54538816457b7f14e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24694: Add support for OPTIONS['context_processors'] to Jinja2 template backend

2016-06-29 Thread Django 
#24694: Add support for OPTIONS['context_processors'] to Jinja2 template backend
-+
 Reporter:  carljm   |Owner:  berkerpeksag
 Type:  New feature  |   Status:  closed
Component:  Template system  |  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
-+

Comment (by aaugustin):

 Unfortunately, the discussion of the drawbacks of this API didn't make it
 into the documentation, so we're ending up with exactly what PEP 182 was
 designed to avoid :-(

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