Re: [Django] #29172: Using Window in Subquery causes AttributeError

[Django]

#29172: Using Window in Subquery causes AttributeError
-+-
 Reporter:  Tomáš Ehrlich|Owner:  nobody
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  subquery window  | Triage Stage:
  expression orm |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tomáš Ehrlich):

 * has_patch:  0 => 1


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

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

[Django] #29172: Using Window in Subquery causes AttributeError

[Django]

#29172: Using Window in Subquery causes AttributeError
-+-
   Reporter:  Tomáš  |  Owner:  nobody
  Ehrlich|
   Type:  Bug| Status:  assigned
  Component:  Database   |Version:  2.0
  layer (models, ORM)|   Keywords:  subquery window
   Severity:  Normal |  expression orm
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Using Window expression within Subquery causes an `AttributeError:
 'NoneType' object has no attribute ‘relabeled_clone'`

 Error is raised in `relabeled_clone` method,
 
https://github.com/django/django/blob/master/django/db/models/expressions.py#L319
 which calls `e.relabeled_clone` method on every expression returned from
 `get_source_expressions`.

 Window expression returns `source_expression`, `partition_by`, `order_by`
 and `frame` in `get_source_expression`:
 
https://github.com/django/django/blob/master/django/db/models/expressions.py#L1188
 but all parameters except `source_expression` are optional and might be
 `None`. This leads to AttributeError.

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

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

Re: [Django] #29171: PostgreSQL specific model fields - ArrayField: Type Mismatch

[Django]

#29171: PostgreSQL specific model fields - ArrayField: Type Mismatch
-+-
 Reporter:  Pal  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  Postgres Array   | Triage Stage:
  Query  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 Could you provide a traceback and more details about how ''it fails''?

 Does it happen when you define a model using `ArrayField(CharField())`,
 when performing a query annotation?

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

Re: [Django] #29171: PostgreSQL specific model fields - ArrayField: Type Mismatch

[Django]

#29171: PostgreSQL specific model fields - ArrayField: Type Mismatch
-+-
 Reporter:  Pal  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  Postgres Array   | Triage Stage:
  Query  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Pal):

 * type:  Uncategorized => 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/063.ada286db57595ebc220a5a54bb5fb80f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #29171: PostgreSQL specific model fields - ArrayField: Type Mismatch

[Django]

#29171: PostgreSQL specific model fields - ArrayField: Type Mismatch
-+-
   Reporter:  Pal|  Owner:  nobody
   Type: | Status:  new
  Uncategorized  |
  Component:  Database   |Version:  2.0
  layer (models, ORM)|   Keywords:  Postgres Array
   Severity:  Normal |  Query
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 When you define ArrayField as models.CharField, the query fails. But if
 you define ArrayField as models.TextField, the query succeeds.

 Not Working: ArrayField(models.CharField(max_length=200), blank=True)

 Working: ArrayField(models.TextField(blank=True))

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

Re: [Django] #18867: Restoring YAML fixtures with DateTimeField causes timezone warnings

[Django]

#18867: Restoring YAML fixtures with DateTimeField causes timezone warnings
-+-
 Reporter:  aigarius@…   |Owner:  Aymeric
 Type:   |  Augustin
  Cleanup/optimization   |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 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 tehfink):

 * cc: tehfink (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/076.bca398546362d75b834df26eea141ab3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29166: in lookup doesn't work with lists in a When clause

[Django]

#29166: in lookup doesn't work with lists in a When clause
-+-
 Reporter:  Matthew Pava |Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  lookup in| 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 Mariusz Felisiak ):

 In [changeset:"10a20e4b37da94fd55b4e9a13e634c2a379bd9e0" 10a20e4]:
 {{{
 #!CommitTicketReference repository=""
 revision="10a20e4b37da94fd55b4e9a13e634c2a379bd9e0"
 [2.0.x] Fixed #29166 -- Fixed crash in When() expression with a list
 argument.

 Thanks Matthew Pava for the report and Tim Graham and Carlton Gibson for
 reviews.
 Regression in 19b2dfd1bfe7fd716dd3d8bfa5f972070d83b42f.

 Backport of 54f80430be4a9adf1fc00b4ca17547415fafc69b from master
 }}}

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

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

Re: [Django] #29166: in lookup doesn't work with lists in a When clause

[Django]

#29166: in lookup doesn't work with lists in a When clause
-+-
 Reporter:  Matthew Pava |Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  lookup in| 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 GitHub ):

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


Comment:

 In [changeset:"54f80430be4a9adf1fc00b4ca17547415fafc69b" 54f8043]:
 {{{
 #!CommitTicketReference repository=""
 revision="54f80430be4a9adf1fc00b4ca17547415fafc69b"
 Fixed #29166 -- Fixed crash in When() expression with a list argument.

 Thanks Matthew Pava for the report and Tim Graham and Carlton Gibson for
 reviews.
 Regression in 19b2dfd1bfe7fd716dd3d8bfa5f972070d83b42f.
 }}}

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

Re: [Django] #28668: Add ON CONFLICT support to QuerySet.bulk_create()

[Django]

#28668: Add ON CONFLICT support to QuerySet.bulk_create()
-+-
 Reporter:  Tom Forbes   |Owner:  Tom
 |  Forbes
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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
-+-

Comment (by Tom Forbes):

 Hey, I recommend consolidating your patches into a single PR on Github and
 linking it here, that's the development process Django now follows.

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

Re: [Django] #28668: Add ON CONFLICT support to QuerySet.bulk_create()

[Django]

#28668: Add ON CONFLICT support to QuerySet.bulk_create()
-+-
 Reporter:  Tom Forbes   |Owner:  Tom
 |  Forbes
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 Дилян Палаузов):

 * Attachment "on_conflict_postgresql_signals_ids.patch" added.

 In addition to the other file, this one add support for sending post_save
 for the newly created objects and retrieving the ids of the objects
 provided as parameters to bulk_create, that already existed in the
 database.

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

Re: [Django] #28514: Clarify docs regarding idempotence of RelatedManager.add()

[Django]

#28514: Clarify docs regarding idempotence of RelatedManager.add()
-+-
 Reporter:  Дилян Палаузов   |Owner:  Jezeniel
 Type:   |  Zapanta
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.11
 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 Дилян Палаузов):

 This approach is nice, but status quo is misleading the ones who try to
 use {{{.add()}}}.

 If currently nobody has the time to fix the bug, then it is more likely
 that somebody will have the time to document the behaviour, as this
 requires less time.

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

[Django] #29170: Oracle - Unable to add triggers in migrations, semicolon removed.

[Django]

#29170: Oracle - Unable to add triggers in migrations, semicolon removed.
-+-
   Reporter:  Danny  |  Owner:  nobody
  Willems|
   Type:  Bug| Status:  new
  Component:  Database   |Version:  1.11
  layer (models, ORM)|   Keywords:  oracle trigger
   Severity:  Normal |  database
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 We have several database triggers we need to insert into our Oracle
 database using a custom migration. The migration runs without raising an
 error and the triggers are created in the database, however, when they are
 invoked as a result of various operations in the Django admin we see an
 error that says that the trigger cannot be compiled. After investigation
 we realised that a required semicolon was being removed from the SQL
 defined in the migration. Ordinarily this is removed from standard SQL
 statements such as SELECT, INSERT etc but in the case of triggers it is
 required as a way to delimit multiple BEGIN...END statements.

 After debugging the issue we found the cause in this line of code:

 
https://github.com/django/django/blob/master/django/db/backends/oracle/base.py#L481

 It appears that the blanket assumption that cx_Oracle does not require
 semicolons does not hold for triggers.

 Here is a simplified migration that shows the issue:


 {{{
 from django.db import migrations

 class Migration(migrations.Migration):
 dependencies = []

 create_trigger_insert_entry = """
 CREATE OR REPLACE TRIGGER UPDATE_BALANCE
 AFTER DELETE OR INSERT OR UPDATE OF AMOUNT ON ENTRY
 BEGIN
   UPDATE ACCOUNT_BALANCE B
   SET (B.BALANCE, B.ACCOUNT) = (SELECT SUM(AMOUNT) sum_amount, account
   FROM ENTRY e WHERE e.ACCOUNT = B.ACCOUNT
 GROUP BY ACCOUNT)
   WHERE EXISTS (SELECT 1 FROM ENTRY e WHERE e.ACCOUNT = B.ACCOUNT);
 END;
 """

 delete_trigger_insert_entry = "DROP TRIGGER UPDATE_BALANCE"

 operations = [
 migrations.CreateModel(
 name='Account',
 fields=[
 ('name', models.CharField(max_length=32, primary_key=True,
 serialize=False)),
 ],
 options={
 'db_table': 'account',
 'managed': True,
 },
 ),

 migrations.CreateModel(
 name='Entry',
 fields=[
 ('value_date', models.DateTimeField()),
 ('amount', models.DecimalField(decimal_places=8,
 max_digits=23)),
 ],
 options={
 'db_table': 'entry',
 'managed': True,
 },
 ),
 migrations.CreateModel(
 name='AccountBalance',
 fields=[
 ('account', models.OneToOneField(db_column='account',
 on_delete=django.db.models.deletion.DO_NOTHING, primary_key=True,
 serialize=False, to='app.Account')),
 ('balance', models.DecimalField(decimal_places=14,
 max_digits=38)),
 ],
 options={
 'db_table': 'account_balance',
 'managed': True,
 },
 ),
 migrations.AddField(
 model_name='entry',
 name='account',
 field=models.ForeignKey(db_column='account',
 on_delete=django.db.models.deletion.CASCADE, to='app.Account'),
 ),
 migrations.RunSQL(sql=create_trigger_insert_entry,
 reverse_sql=delete_trigger_insert_entry),
 ]
 }}}

 As a workaround, we « fixed » this issue by overriding the method
 `_fix_for_params` with the following code:
 {{{
 def _fix_for_params(self, query, params, unify_by_values=False):
 # cx_Oracle wants no trailing ';' for SQL statements.  For PL/SQL, it
 # it does want a trailing ';' but not a trailing '/'.  However, these
 # characters must be included in the original query in case the query
 # is being passed to SQL*Plus.
 # ---> Fix this issue
 if query.endswith(" END;"):
 pass
 elif query.endswith(';') or query.endswith('/'):
 query = query[:-1]
 if params is None:
 params = []
 query = query
 [...]
 }}}
 and we used
 {{{
 django.db.backends.oracle.base.FormatStylePlaceholderCursor._fix_for_params
 = _fix_for_params
 }}}
 in the migration file as it doesn't impact all the Django project. We
 would be happy to raise a pull request to get this fixed and obviously if
 anyone has a better way of doing this, we'd gladly oblige.

-- 
Ticket URL: 

Re: [Django] #28514: Clarify docs regarding idempotence of RelatedManager.add()

[Django]

#28514: Clarify docs regarding idempotence of RelatedManager.add()
-+-
 Reporter:  Дилян Палаузов   |Owner:  Jezeniel
 Type:   |  Zapanta
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.11
 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 Tim Graham):

 If `RelatedManager.add()` isn't idempotent, then that sounds like a bug.
 We prefer to spend time fixing bugs rather than documenting them, so
 that's the approach I'd suggest.

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

Re: [Django] #28715: Prevent a migration changing DateTimeField(auto_now_add=True) to default=timezone.now from generating SQL

[Django]

#28715: Prevent a migration changing DateTimeField(auto_now_add=True) to
default=timezone.now from generating SQL
--+
 Reporter:  Дилян Палаузов|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  1.11
 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 Tim Graham):

 The patch must apply cleanly to Django's master branch and it must have a
 test. Ideally, you could provide the patch as a pull request and then
 check "Has patch" on the ticket so that it appears in the review queue.

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

Re: [Django] #28514: Clarify docs regarding idempotence of RelatedManager.add()

[Django]

#28514: Clarify docs regarding idempotence of RelatedManager.add()
-+-
 Reporter:  Дилян Палаузов   |Owner:  Jezeniel
 Type:   |  Zapanta
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.11
 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 Дилян Палаузов):

 Any progress here?

 I think only the concurrent aspect of .add() is missing:
 * if two .add() are called in parallel with overlapping set of related
 objects, one of them can fail with IntegrityError and has to be repeated.
 This is caused by the fact that Django inserts the objects within a
 transaction and only after the transaction is closed it can be determined
 if the changes are permament.  Django does not retry in this case
 * When IntegrityError is thrown, m2m_changed is still sent for the
 objects, that were supposed to be matched.

 The latter is valid if I recall correctly the circumstances from five
 months ago.  The code can certainly be changed so that m2m_changed is not
 sent, but it is better to document the current behaviour than doing
 noting.

 Jack, I would like to encourage you to use the opportunity and check the
 implementation, while you describe it.

 Apart from this my plan is to work with Django for one more month and I
 will be glad if by then all concerns related to this ticket can be
 clarified.

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

Re: [Django] #28715: Prevent a migration changing DateTimeField(auto_now_add=True) to default=timezone.now from generating SQL

[Django]

#28715: Prevent a migration changing DateTimeField(auto_now_add=True) to
default=timezone.now from generating SQL
--+
 Reporter:  Дилян Палаузов|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  1.11
 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 Дилян Палаузов):

 My plan is to work one more month with Django, so if there are concerns on
 this patch, please raise them by then.

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

Re: [Django] #29157: Allow querying for distinct values in JSONField lists

[Django]

#29157: Allow querying for distinct values in JSONField lists
---+
 Reporter:  Hrishikesh Barman  |Owner:  (none)
 Type:  New feature|   Status:  new
Component:  contrib.postgres   |  Version:  2.0
 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 Hrishikesh Barman):

 Replying to [comment:2 Tim Graham]:
 > Accepting for investigation if someone is interested, although I'm not
 sure what change or if a change should be made here.

 I'll try working on this, but I won't tag myself on owned for now. But
 will be checking what can be done.

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

Re: [Django] #29169: Upgrade django 1.8 to 1.9

[Django]

#29169: Upgrade django 1.8 to 1.9
-+-
 Reporter:  Olivetree|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:   |  Version:  1.9
  contrib.contenttypes   |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  upgrade, error,  | Triage Stage:
  contenttypes, app_label,   |  Unreviewed
  INSTALLED_APPS |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by Olivetree:

Old description:

> I am upgrading from django 1.8.4 to 1.9.13. I installed django 1.9.3 and
> added to my settings
>
> {{
> import django
> django.setup()
> }}}
>
> My application no longer works, it displays the following error:
> {{{
> Unhandled exception in thread started by  check_errors..wrapper at 0x7f9c9655b158>
> Traceback (most recent call last):
>   File "/usr/local/lib/python3.4/dist-
> packages/django/utils/autoreload.py", line 226, in wrapper
> fn(*args, **kwargs)
>   File "/usr/local/lib/python3.4/dist-
> packages/django/core/management/commands/runserver.py", line 116, in
> inner_run
> self.check(display_num_errors=True)
>   File "/usr/local/lib/python3.4/dist-
> packages/django/core/management/base.py", line 426, in check
> include_deployment_checks=include_deployment_checks,
>   File "/usr/local/lib/python3.4/dist-
> packages/django/core/checks/registry.py", line 75, in run_checks
> new_errors = check(app_configs=app_configs)
>   File "/usr/local/lib/python3.4/dist-
> packages/django/core/checks/urls.py", line 13, in check_url_config
> return check_resolver(resolver)
>   File "/usr/local/lib/python3.4/dist-
> packages/django/core/checks/urls.py", line 23, in check_resolver
> for pattern in resolver.url_patterns:
>   File "/usr/local/lib/python3.4/dist-
> packages/django/utils/functional.py", line 33, in __get__
> res = instance.__dict__[self.name] = self.func(instance)
>   File "/usr/local/lib/python3.4/dist-
> packages/django/core/urlresolvers.py", line 417, in url_patterns
> patterns = getattr(self.urlconf_module, "urlpatterns",
> self.urlconf_module)
>   File "/usr/local/lib/python3.4/dist-
> packages/django/utils/functional.py", line 33, in __get__
> res = instance.__dict__[self.name] = self.func(instance)
>   File "/usr/local/lib/python3.4/dist-
> packages/django/core/urlresolvers.py", line 410, in urlconf_module
> return import_module(self.urlconf_name)
>   File "/usr/lib/python3.4/importlib/__init__.py", line 109, in
> import_module
> return _bootstrap._gcd_import(name[level:], package, level)
>   File "", line 2254, in _gcd_import
>   File "", line 2237, in _find_and_load
>   File "", line 2226, in
> _find_and_load_unlocked
>   File "", line 1200, in _load_unlocked
>   File "", line 1129, in _exec
>   File "", line 1471, in exec_module
>   File "", line 321, in
> _call_with_frames_removed
>   File
> "/home/eva/work/test_upgrade_django_to_1_11/be/centroproduto/urls.py",
> line 7, in 
> from django.contrib.auth.views import login, logout
>   File "/usr/local/lib/python3.4/dist-
> packages/django/contrib/auth/views.py", line 11, in 
> from django.contrib.auth.forms import (
>   File "/usr/local/lib/python3.4/dist-
> packages/django/contrib/auth/forms.py", line 10, in 
> from django.contrib.auth.models import User
>   File "/usr/local/lib/python3.4/dist-
> packages/django/contrib/auth/models.py", line 6, in 
> from django.contrib.contenttypes.models import ContentType
>   File "/usr/local/lib/python3.4/dist-
> packages/django/contrib/contenttypes/models.py", line 161, in 
> class ContentType(models.Model):
>   File "/usr/local/lib/python3.4/dist-packages/django/db/models/base.py",
> line 102, in __new__
> "INSTALLED_APPS." % (module, name)
> RuntimeError: Model class django.contrib.contenttypes.models.ContentType
> doesn't declare an explicit app_label and isn't in an application in
> INSTALLED_APPS.
> }}}
> 
>
> I can not even run migrations ...
> In my settings I have:
> {{{
> (...)
>
> import django
> django.setup()
>
> (...)
>
> INSTALLED_APPS = (
> 'django.contrib.auth',
> 'django.contrib.contenttypes',
> 'django.contrib.sessions',
> 'django.contrib.sites',
> 'django.contrib.messages',
> 'django.contrib.staticfiles',
> 'django.contrib.admin',
> 'myapp',
> #'debug_toolbar',
> 'django_extensions',
> 'corsheaders',
> 'watson',
> 'raven.contrib.django.raven_compat',
> #'django.contrib.admindocs',
> 'django_mailbox',
> 'django.contrib.postgres',
> )
>
> (...)

Re: [Django] #29169: Upgrade django 1.8 to 1.9

[Django]

#29169: Upgrade django 1.8 to 1.9
-+-
 Reporter:  Olivetree|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:   |  Version:  1.9
  contrib.contenttypes   |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  upgrade, error,  | Triage Stage:
  contenttypes, app_label,   |  Unreviewed
  INSTALLED_APPS |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Olivetree):

 If I don't call django.setup() I have a diferente error:


 {{{
 Unhandled exception in thread started by .wrapper at 0x7effd13cbbf8>
 Traceback (most recent call last):
   File "/usr/local/lib/python3.4/dist-
 packages/django/utils/autoreload.py", line 226, in wrapper
 fn(*args, **kwargs)
   File "/usr/local/lib/python3.4/dist-
 packages/django/core/management/commands/runserver.py", line 109, in
 inner_run
 autoreload.raise_last_exception()
   File "/usr/local/lib/python3.4/dist-
 packages/django/utils/autoreload.py", line 249, in raise_last_exception
 six.reraise(*_exception)
   File "/usr/local/lib/python3.4/dist-packages/django/utils/six.py", line
 685, in reraise
 raise value.with_traceback(tb)
   File "/usr/local/lib/python3.4/dist-
 packages/django/utils/autoreload.py", line 226, in wrapper
 fn(*args, **kwargs)
   File "/usr/local/lib/python3.4/dist-packages/django/__init__.py", line
 18, in setup
 apps.populate(settings.INSTALLED_APPS)
   File "/usr/local/lib/python3.4/dist-packages/django/apps/registry.py",
 line 85, in populate
 app_config = AppConfig.create(entry)
   File "/usr/local/lib/python3.4/dist-packages/django/apps/config.py",
 line 90, in create
 module = import_module(entry)
   File "/usr/lib/python3.4/importlib/__init__.py", line 109, in
 import_module
 return _bootstrap._gcd_import(name[level:], package, level)
   File "", line 2254, in _gcd_import
   File "", line 2237, in _find_and_load
   File "", line 2226, in
 _find_and_load_unlocked
   File "", line 1200, in _load_unlocked
   File "", line 1129, in _exec
   File "", line 1471, in exec_module
   File "", line 321, in
 _call_with_frames_removed
   File
 "/home/eva/work/test_upgrade_django_to_1_11/be/centroprodutoapp/__init__.py",
 line 1, in 
 import centroprodutoapp.signals
   File
 "/home/eva/work/test_upgrade_django_to_1_11/be/centroprodutoapp/signals.py",
 line 6, in 
 from django.contrib.auth.models import User
   File "/usr/local/lib/python3.4/dist-
 packages/django/contrib/auth/models.py", line 4, in 
 from django.contrib.auth.base_user import AbstractBaseUser,
 BaseUserManager
   File "/usr/local/lib/python3.4/dist-
 packages/django/contrib/auth/base_user.py", line 49, in 
 class AbstractBaseUser(models.Model):
   File "/usr/local/lib/python3.4/dist-packages/django/db/models/base.py",
 line 94, in __new__
 app_config = apps.get_containing_app_config(module)
   File "/usr/local/lib/python3.4/dist-packages/django/apps/registry.py",
 line 239, in get_containing_app_config
 self.check_apps_ready()
   File "/usr/local/lib/python3.4/dist-packages/django/apps/registry.py",
 line 124, in check_apps_ready
 raise AppRegistryNotReady("Apps aren't loaded yet.")
 django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.
 }}}



 Replying to [comment:1 Tim Graham]:
 > Please see TicketClosingReasons/UseSupportChannels for ways to get help.
 If you confirm a bug in Django, then please open a ticket with details.
 >
 > I will say that there's no need to call `django.setup()` in your
 settings.

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

Re: [Django] #29168: Document how to write a custom lookup where the rhs comes before the lhs (was: Custom lookup documentation is incomplete)

[Django]

#29168: Document how to write a custom lookup where the rhs comes before the lhs
-+-
 Reporter:  JJ Gutierrez |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  lookup   | 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):

 * type:  Bug => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 Maybe looking at
 [https://github.com/django/django/blob/master/django/db/models/lookups.py
 the built in lookups] would offer a hint.

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

Re: [Django] #29157: Allow querying for distinct values in JSONField lists

[Django]

#29157: Allow querying for distinct values in JSONField lists
---+
 Reporter:  Hrishikesh Barman  |Owner:  (none)
 Type:  New feature|   Status:  new
Component:  contrib.postgres   |  Version:  2.0
 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 Tim Graham):

 * stage:  Unreviewed => Accepted


Comment:

 Accepting for investigation if someone is interested, although I'm not
 sure what change or if a change should be made 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 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.f9f12d288566d09ab25fd72f38dc6a86%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29167: HashedFilesMixin doesn't work with data URIs that include a closing parenthesis (was: collectstatic breaks Bootstrap 4 styles)

[Django]

#29167: HashedFilesMixin doesn't work with data URIs that include a closing
parenthesis
-+
 Reporter:  Clem Flory   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  Version:  2.0
 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 Tim Graham):

 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #29169: Upgrade django 1.8 to 1.9

[Django]

#29169: Upgrade django 1.8 to 1.9
-+-
 Reporter:  Olivetree|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:   |  Version:  1.9
  contrib.contenttypes   |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  upgrade, error,  | Triage Stage:
  contenttypes, app_label,   |  Unreviewed
  INSTALLED_APPS |
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:   => invalid


Old description:

> I am upgrading from django 1.8.4 to 1.9.13. I installed django 1.9.3 and
> added to my settings
>
> **import django
> django.setup ()**
>
> My application no longer works, it displays the following error:
>
> Unhandled exception in thread started by  check_errors..wrapper at 0x7f9c9655b158>
> Traceback (most recent call last):
>   File "/usr/local/lib/python3.4/dist-
> packages/django/utils/autoreload.py", line 226, in wrapper
> fn(*args, **kwargs)
>   File "/usr/local/lib/python3.4/dist-
> packages/django/core/management/commands/runserver.py", line 116, in
> inner_run
> self.check(display_num_errors=True)
>   File "/usr/local/lib/python3.4/dist-
> packages/django/core/management/base.py", line 426, in check
> include_deployment_checks=include_deployment_checks,
>   File "/usr/local/lib/python3.4/dist-
> packages/django/core/checks/registry.py", line 75, in run_checks
> new_errors = check(app_configs=app_configs)
>   File "/usr/local/lib/python3.4/dist-
> packages/django/core/checks/urls.py", line 13, in check_url_config
> return check_resolver(resolver)
>   File "/usr/local/lib/python3.4/dist-
> packages/django/core/checks/urls.py", line 23, in check_resolver
> for pattern in resolver.url_patterns:
>   File "/usr/local/lib/python3.4/dist-
> packages/django/utils/functional.py", line 33, in __get__
> res = instance.__dict__[self.name] = self.func(instance)
>   File "/usr/local/lib/python3.4/dist-
> packages/django/core/urlresolvers.py", line 417, in url_patterns
> patterns = getattr(self.urlconf_module, "urlpatterns",
> self.urlconf_module)
>   File "/usr/local/lib/python3.4/dist-
> packages/django/utils/functional.py", line 33, in __get__
> res = instance.__dict__[self.name] = self.func(instance)
>   File "/usr/local/lib/python3.4/dist-
> packages/django/core/urlresolvers.py", line 410, in urlconf_module
> return import_module(self.urlconf_name)
>   File "/usr/lib/python3.4/importlib/__init__.py", line 109, in
> import_module
> return _bootstrap._gcd_import(name[level:], package, level)
>   File "", line 2254, in _gcd_import
>   File "", line 2237, in _find_and_load
>   File "", line 2226, in
> _find_and_load_unlocked
>   File "", line 1200, in _load_unlocked
>   File "", line 1129, in _exec
>   File "", line 1471, in exec_module
>   File "", line 321, in
> _call_with_frames_removed
>   File
> "/home/eva/work/test_upgrade_django_to_1_11/be/centroproduto/urls.py",
> line 7, in 
> from django.contrib.auth.views import login, logout
>   File "/usr/local/lib/python3.4/dist-
> packages/django/contrib/auth/views.py", line 11, in 
> from django.contrib.auth.forms import (
>   File "/usr/local/lib/python3.4/dist-
> packages/django/contrib/auth/forms.py", line 10, in 
> from django.contrib.auth.models import User
>   File "/usr/local/lib/python3.4/dist-
> packages/django/contrib/auth/models.py", line 6, in 
> from django.contrib.contenttypes.models import ContentType
>   File "/usr/local/lib/python3.4/dist-
> packages/django/contrib/contenttypes/models.py", line 161, in 
> class ContentType(models.Model):
>   File "/usr/local/lib/python3.4/dist-packages/django/db/models/base.py",
> line 102, in __new__
> "INSTALLED_APPS." % (module, name)
> RuntimeError: Model class django.contrib.contenttypes.models.ContentType
> doesn't declare an explicit app_label and isn't in an application in
> INSTALLED_APPS.
>
> 
>
> I can not even run migrations ...
> In my settings I have:
>
> (...)
>
> import django
> django.setup()
>
> (...)
>
> INSTALLED_APPS = (
> 'django.contrib.auth',
> 'django.contrib.contenttypes',
> 'django.contrib.sessions',
> 'django.contrib.sites',
> 'django.contrib.messages',
> 'django.contrib.staticfiles',
> 'django.contrib.admin',
> 'myapp',
> #'debug_toolbar',
> 'django_extensions',
> 'corsheaders',
> 'watson',
> 'raven.contrib.django.raven_compat',
> #'django.contrib.admindocs',
> 'django_mailbox',
> 

Re: [Django] #20601: intcomma and floatformat internationalization error

[Django]

#20601: intcomma and floatformat internationalization error
-+-
 Reporter:  c.schmitt@…  |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Template system  |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  internationalization, humanize,|
  contrib, float, floatcomma |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Alexey):

 Should we try to parse value to float?

 Something like try to find float separator with regex, and convert it
 before `isinstance` check

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

[Django] #29169: Upgrade django 1.8 to 1.9

[Django]

#29169: Upgrade django 1.8 to 1.9
-+-
   Reporter:  Olivetree  |  Owner:  nobody
   Type: | Status:  new
  Uncategorized  |
  Component: |Version:  1.9
  contrib.contenttypes   |   Keywords:  upgrade, error,
   Severity:  Normal |  contenttypes, app_label,
   Triage Stage: |  INSTALLED_APPS
  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I am upgrading from django 1.8.4 to 1.9.13. I installed django 1.9.3 and
 added to my settings

 **import django
 django.setup ()**

 My application no longer works, it displays the following error:

 Unhandled exception in thread started by .wrapper at 0x7f9c9655b158>
 Traceback (most recent call last):
   File "/usr/local/lib/python3.4/dist-
 packages/django/utils/autoreload.py", line 226, in wrapper
 fn(*args, **kwargs)
   File "/usr/local/lib/python3.4/dist-
 packages/django/core/management/commands/runserver.py", line 116, in
 inner_run
 self.check(display_num_errors=True)
   File "/usr/local/lib/python3.4/dist-
 packages/django/core/management/base.py", line 426, in check
 include_deployment_checks=include_deployment_checks,
   File "/usr/local/lib/python3.4/dist-
 packages/django/core/checks/registry.py", line 75, in run_checks
 new_errors = check(app_configs=app_configs)
   File "/usr/local/lib/python3.4/dist-
 packages/django/core/checks/urls.py", line 13, in check_url_config
 return check_resolver(resolver)
   File "/usr/local/lib/python3.4/dist-
 packages/django/core/checks/urls.py", line 23, in check_resolver
 for pattern in resolver.url_patterns:
   File "/usr/local/lib/python3.4/dist-
 packages/django/utils/functional.py", line 33, in __get__
 res = instance.__dict__[self.name] = self.func(instance)
   File "/usr/local/lib/python3.4/dist-
 packages/django/core/urlresolvers.py", line 417, in url_patterns
 patterns = getattr(self.urlconf_module, "urlpatterns",
 self.urlconf_module)
   File "/usr/local/lib/python3.4/dist-
 packages/django/utils/functional.py", line 33, in __get__
 res = instance.__dict__[self.name] = self.func(instance)
   File "/usr/local/lib/python3.4/dist-
 packages/django/core/urlresolvers.py", line 410, in urlconf_module
 return import_module(self.urlconf_name)
   File "/usr/lib/python3.4/importlib/__init__.py", line 109, in
 import_module
 return _bootstrap._gcd_import(name[level:], package, level)
   File "", line 2254, in _gcd_import
   File "", line 2237, in _find_and_load
   File "", line 2226, in
 _find_and_load_unlocked
   File "", line 1200, in _load_unlocked
   File "", line 1129, in _exec
   File "", line 1471, in exec_module
   File "", line 321, in
 _call_with_frames_removed
   File
 "/home/eva/work/test_upgrade_django_to_1_11/be/centroproduto/urls.py",
 line 7, in 
 from django.contrib.auth.views import login, logout
   File "/usr/local/lib/python3.4/dist-
 packages/django/contrib/auth/views.py", line 11, in 
 from django.contrib.auth.forms import (
   File "/usr/local/lib/python3.4/dist-
 packages/django/contrib/auth/forms.py", line 10, in 
 from django.contrib.auth.models import User
   File "/usr/local/lib/python3.4/dist-
 packages/django/contrib/auth/models.py", line 6, in 
 from django.contrib.contenttypes.models import ContentType
   File "/usr/local/lib/python3.4/dist-
 packages/django/contrib/contenttypes/models.py", line 161, in 
 class ContentType(models.Model):
   File "/usr/local/lib/python3.4/dist-packages/django/db/models/base.py",
 line 102, in __new__
 "INSTALLED_APPS." % (module, name)
 RuntimeError: Model class django.contrib.contenttypes.models.ContentType
 doesn't declare an explicit app_label and isn't in an application in
 INSTALLED_APPS.

 

 I can not even run migrations ...
 In my settings I have:

 (...)

 import django
 django.setup()

 (...)

 INSTALLED_APPS = (
 'django.contrib.auth',
 'django.contrib.contenttypes',
 'django.contrib.sessions',
 'django.contrib.sites',
 'django.contrib.messages',
 'django.contrib.staticfiles',
 'django.contrib.admin',
 'myapp',
 #'debug_toolbar',
 'django_extensions',
 'corsheaders',
 'watson',
 'raven.contrib.django.raven_compat',
 #'django.contrib.admindocs',
 'django_mailbox',
 'django.contrib.postgres',
 )

 (...)


 

 I'm using python3.4 and postgresql9.3

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

-- 
You received this message because you are 

Re: [Django] #20601: intcomma and floatformat internationalization error

[Django]

#20601: intcomma and floatformat internationalization error
-+-
 Reporter:  c.schmitt@…  |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Template system  |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  internationalization, humanize,|
  contrib, float, floatcomma |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Alexey):

 * cc: Alexey (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/078.97c1e1948486533d8aeab0cf6e32664a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29166: in lookup doesn't work with lists in a When clause

[Django]

#29166: in lookup doesn't work with lists in a When clause
-+-
 Reporter:  Matthew Pava |Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  lookup in| 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 Carlton Gibson):

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

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

[Django]

#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Rajesh
 Type:   |  Veeranki
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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
-+-
Changes (by Carlton Gibson):

 * needs_better_patch:  0 => 1


Comment:

 Comments on
 [https://github.com/django/django/pull/8570#pullrequestreview-10437
 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/066.1aafcdf045374351cfc88a32d1c09de6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28184: FileField storage param should allow a callable

[Django]

#28184: FileField storage param should allow a callable
-+-
 Reporter:  miigotu  |Owner:  miigotu
 Type:  New feature  |   Status:  assigned
Component:  File |  Version:  1.11
  uploads/storage|
 Severity:  Normal   |   Resolution:
 Keywords:  callable storage | Triage Stage:  Accepted
  filefield  |
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Carlton Gibson):

 Left some comments on 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/065.3cf1fbdf95065533dc49dd4efdc975d5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28184: FileField storage param should allow a callable

[Django]

#28184: FileField storage param should allow a callable
-+-
 Reporter:  miigotu  |Owner:  miigotu
 Type:  New feature  |   Status:  assigned
Component:  File |  Version:  1.11
  uploads/storage|
 Severity:  Normal   |   Resolution:
 Keywords:  callable storage | Triage Stage:  Accepted
  filefield  |
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

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

Re: [Django] #26763: Control rendering of add/change/delete_related admin buttons

[Django]

#26763: Control rendering of add/change/delete_related admin buttons
---+---
 Reporter:  Chris Clark|Owner:  Chris Clark
 Type:  New feature|   Status:  closed
Component:  contrib.admin  |  Version:  1.9
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  1
---+---
Changes (by Carlton Gibson):

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


Comment:

 This was resolved by #27728, which allowed overriding admin templatetag's
 templates.

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

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

Re: [Django] #18957: Add next/previous buttons when editing a model in the admin site

[Django]

#18957: Add next/previous buttons when editing a model in the admin site
---+
 Reporter:  palkeo |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  contrib.admin  |  Version:  1.4
 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 Carlton Gibson):

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


Comment:

 This was resolved by #27728, which allowed overriding admin templatetag's
 templates.

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

Re: [Django] #19235: Admin actions displayed as buttons instead of drop-down list

[Django]

#19235: Admin actions displayed as buttons instead of drop-down list
+-
 Reporter:  Marijonas   |Owner:  Marijonas
 Type:  New feature |   Status:  closed
Component:  contrib.admin   |  Version:  master
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  admin, actions  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  1
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  1
+-
Changes (by Carlton Gibson):

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


Comment:

 This was resolved by #27728, which allowed overriding admin templatetag's
 templates.

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

Re: [Django] #12566: admin action templates cannot be overriden on a per-app basis

[Django]

#12566: admin action templates cannot be overriden on a per-app basis
---+-
 Reporter:  Ben Jackson|Owner:  Tay Ray Chuan
 Type:  New feature|   Status:  closed
Component:  contrib.admin  |  Version:  1.1
 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 Carlton Gibson):

 * status:  assigned => closed
 * resolution:   => 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 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/061.f9f1239e616917edb8ff22adc50e6d30%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #12566: admin action templates cannot be overriden on a per-app basis

[Django]

#12566: admin action templates cannot be overriden on a per-app basis
---+-
 Reporter:  Ben Jackson|Owner:  Tay Ray Chuan
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  1.1
 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 Carlton Gibson):

 This was resolved by #27728, which allowed overriding admin templatetag's
 templates.

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