Re: [Django] #24607: Serialization (and deserialization) of MTI models doesn't work with natural keys

[Django]

#24607: Serialization (and deserialization) of MTI models doesn't work with 
natural
keys
-+-
 Reporter:  Denys Duchier|Owner:  Tim
 |  Graham 
 Type:  Bug  |   Status:  closed
Component:  Core |  Version:  master
  (Serialization)|
 Severity:  Normal   |   Resolution:  fixed
 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 Tim Graham ):

 * status:  new => closed
 * owner:  (none) => Tim Graham 
 * resolution:   => fixed


Comment:

 In [changeset:"cb7860ccedb199cb221c9e084b5104978b246356" cb7860cc]:
 {{{
 #!CommitTicketReference repository=""
 revision="cb7860ccedb199cb221c9e084b5104978b246356"
 Fixed #24607 -- Serialized natural keys in multi-table inheritance models.

 Thanks João Paulo Melo de Sampaio for the test.
 }}}

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

Re: [Django] #29128: makemigrations raises AppRegistryNotReady instead of ImproperlyConfigured in Django 2.0

[Django]

#29128: makemigrations raises AppRegistryNotReady instead of 
ImproperlyConfigured
in Django 2.0
-+-
 Reporter:  Jaye Doepke  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  2.0
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  migrations   | Triage Stage:  Accepted
  makemigrations |
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:

 Bisected to 13be45308045f522dfd1d0ff3da3cdc163bc521d.

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

Re: [Django] #29130: floatformat is rounding off incorrectly (was: Floatformat is rounding off incorrectly.)

[Django]

#29130: floatformat is rounding off incorrectly
-+-
 Reporter:  Akash Deshpande  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  template float   | Triage Stage:
  filter |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Old description:

> I think the below changes broke/caused issues in floatformat
>
> https://github.com/django/django/commit/12f7928f5a455e330c0a7f19bc86b37baca12811
>
> Easiest way to replicate the issue is
> 1. Create a simple view with a template
>
> views.py
> \\
>def test(request):
> return render('test.html')
>

> test.html
> \\
>  {{ 331.449|floatformat:-1 }}
>
> The above should return 331.5, but returns 331.4. This changed in django
> 1.11. (It returned 331.5 in django 1.8.X )

New description:

 I think 12f7928f5a455e330c0a7f19bc86b37baca12811 caused a regression in
 `floatformat`.

 `{{ 331.449|floatformat:-1 }}`

 The above should return 331.5, but returns 331.4. This changed in django
 1.11. (It returned 331.5 in django 1.8.X )

--

Comment (by Tim Graham):

 The current behavior looks correct to me. If rounding to one decimal
 place, look at the second decimal place (4). Since that's less than five,
 round down. Have I misunderstood the rules for rounding?

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

Re: [Django] #29125: Q.deconstruct() is nondeterministic if the Q has multiple kwargs

[Django]

#29125: Q.deconstruct() is nondeterministic if the Q has multiple kwargs
-+-
 Reporter:  Harro|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Release blocker  |   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 Tim Graham ):

 In [changeset:"fd18345e10b9e5c9713c606509feaf18e57178e2" fd18345e]:
 {{{
 #!CommitTicketReference repository=""
 revision="fd18345e10b9e5c9713c606509feaf18e57178e2"
 [2.0.x] Refs #29125 -- Made Q.deconstruct() omit 'query_utils' in the path
 and _connector='AND' since it's a default value.

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

Re: [Django] #29125: Q.deconstruct() is nondeterministic if the Q has multiple kwargs

[Django]

#29125: Q.deconstruct() is nondeterministic if the Q has multiple kwargs
-+-
 Reporter:  Harro|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Release blocker  |   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 Tim Graham ):

 In [changeset:"aeb35548dc3a669aebec45f8f51a9cd3fbfc8801" aeb35548]:
 {{{
 #!CommitTicketReference repository=""
 revision="aeb35548dc3a669aebec45f8f51a9cd3fbfc8801"
 [2.0.x] Fixed #29125 -- Made Q.deconstruct() deterministic with multiple
 keyword arguments.

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

Re: [Django] #29125: Q.deconstruct() is nondeterministic if the Q has multiple kwargs

[Django]

#29125: Q.deconstruct() is nondeterministic if the Q has multiple kwargs
-+-
 Reporter:  Harro|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Release blocker  |   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 Tim Graham ):

 In [changeset:"9ba3df82402e7e23b353da20aea6894935241ef9" 9ba3df8]:
 {{{
 #!CommitTicketReference repository=""
 revision="9ba3df82402e7e23b353da20aea6894935241ef9"
 Refs #29125 -- Made Q.deconstruct() omit 'query_utils' in the path and
 _connector='AND' since it's a default value.
 }}}

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

Re: [Django] #29125: Q.deconstruct() is nondeterministic if the Q has multiple kwargs

[Django]

#29125: Q.deconstruct() is nondeterministic if the Q has multiple kwargs
-+-
 Reporter:  Harro|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Release blocker  |   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:"b95c49c954e3b75678bb258e9fb2ec30d0d960bb" b95c49c9]:
 {{{
 #!CommitTicketReference repository=""
 revision="b95c49c954e3b75678bb258e9fb2ec30d0d960bb"
 Fixed #29125 -- Made Q.deconstruct() deterministic with multiple keyword
 arguments.
 }}}

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

Re: [Django] #29130: Floatformat is rounding off incorrectly.

[Django]

#29130: Floatformat is rounding off incorrectly.
-+-
 Reporter:  Akash Deshpande  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  template float   | Triage Stage:
  filter |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Akash Deshpande):

 * Attachment "Screen Shot 2018-02-12 at 1.49.17 PM.png" 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.0f25e6a566a032ecafaaf5955ba1acbd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #29130: Floatformat is rounding off incorrectly.

[Django]

#29130: Floatformat is rounding off incorrectly.
-+-
   Reporter:  Akash  |  Owner:  nobody
  Deshpande  |
   Type:  Bug| Status:  new
  Component:  Template   |Version:  1.11
  system |   Keywords:  template float
   Severity:  Normal |  filter
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I think the below changes broke/caused issues in floatformat

 
https://github.com/django/django/commit/12f7928f5a455e330c0a7f19bc86b37baca12811

 Easiest way to replicate the issue is
 1. Create a simple view with a template

 views.py
 \\
def test(request):
 return render('test.html')


 test.html
 \\
  {{ 331.449|floatformat:-1 }}

 The above should return 331.5, but returns 331.4. This changed in django
 1.11. (It returned 331.5 in django 1.8.X )

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

[Django] #29129: Child model updates parent model with empty fields making an extra query in multi-inheritance use case

[Django]

#29129: Child model updates parent model with empty fields making an extra 
query in
multi-inheritance use case
-+-
   Reporter:  user0007   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  2.0
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 While creating a new model object (using multi-inheritance model =>
 `Child(Parent)`), Django does an extra update query setting parent model
 fields to empty values. This situation occurs *only* if we define a custom
 primary key in a parent model (eg. as an UUID field).

 An example *without* custom primary key (correct behavior):

 {{{
 class Parent(models.Model):
 title = models.TextField()

 class Child(Parent):
 body = models.TextField()


 >> Child.objects.create()

 1. INSERT INTO "app_parent" ("title") VALUES ('') RETURNING
 "app_parent"."id"
 2. INSERT INTO "app_child" ("parent_ptr_id", "body") VALUES (1, '')
 }}}

 An example *with* custom primary key (incorrect behavior):

 {{{
 class Parent(models.Model):
 id = models.UUIDField(
 primary_key=True,
 default=uuid.uuid4,
 editable=False
 )
 title = models.TextField()

 class Child(Parent):
 body = models.TextField()


 >> Child.objects.create()

 1. UPDATE "app_parent" SET "title" = '' WHERE "app_parent"."id" =
 'd750cfdd-ae7b-48a6-a2e0-d49e70e28686'::uuid
 2. INSERT INTO "app_parent" ("id", "title") VALUES ('d750cfdd-ae7b-
 48a6-a2e0-d49e70e28686'::uuid, '')
 3. INSERT INTO "app_child" ("parent_ptr_id", "body") VALUES ('d750cfdd-
 ae7b-48a6-a2e0-d49e70e28686'::uuid, '')
 }}}


 Python 3.6, PostgreSQL 9.6

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

Re: [Django] #29103: sqlmigrate produces byte literal in SQL for one-off string default value in TextField, CharField on MySQL

[Django]

#29103: sqlmigrate produces byte literal in SQL for one-off string default 
value in
TextField, CharField on MySQL
-+-
 Reporter:  Qlimax   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  sqlmigrate, byte,| Triage Stage:  Accepted
  default value, one-off |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz):

 Ah sorry, in the current use case, the expected output is simply no binary
 marker, which is fixed in my patch.
 My question is about the SQL output in the hypothetic case the default
 would be a real binary bytestring.

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

Re: [Django] #29128: makemigrations raises AppRegistryNotReady instead of ImproperlyConfigured in Django 2.0

[Django]

#29128: makemigrations raises AppRegistryNotReady instead of 
ImproperlyConfigured
in Django 2.0
-+-
 Reporter:  Jaye Doepke  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  2.0
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  migrations   | Triage Stage:
  makemigrations |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 Could you [https://docs.djangoproject.com/en/dev/internals/contributing
 /triaging-tickets/#bisecting-a-regression bisect] to find the commit where
 the behavior changed?

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

Re: [Django] #29103: sqlmigrate produces byte literal in SQL for one-off string default value in TextField, CharField on MySQL

[Django]

#29103: sqlmigrate produces byte literal in SQL for one-off string default 
value in
TextField, CharField on MySQL
-+-
 Reporter:  Qlimax   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  sqlmigrate, byte,| Triage Stage:  Accepted
  default value, one-off |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz):

 It's still not entirely clear to me what is the correct expected output. I
 think that internally, mysqlclient is using the `'surrogateescape'`
 encoding which is apparently not usable for some outputs like the shell.
 Any suggestion welcome.

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

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

[Django] #29128: makemigrations raises AppRegistryNotReady instead of ImproperlyConfigured in Django 2.0

[Django]

#29128: makemigrations raises AppRegistryNotReady instead of 
ImproperlyConfigured
in Django 2.0
-+-
   Reporter:  Jaye   |  Owner:  nobody
  Doepke |
   Type:  Bug| Status:  new
  Component:  Core   |Version:  2.0
  (Management commands)  |   Keywords:  migrations
   Severity:  Normal |  makemigrations
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 In Django 2.0 with settings that should raise
 `django.exceptions.ImproperlyConfigured`, running `manage.py
 makemigrations` will raise `django.exceptions.AppRegistryNotReady`
 instead. This does not occur in Django 1.11.

 **Steps to Reproduce:**

 {{{
 $ django-admin startproject example_project .
 $ echo 'SECRET_KEY = None' >> example_project/settings.py
 $ ./manage.py makemigrations
 Traceback (most recent call last):
   File "./manage.py", line 15, in 
 execute_from_command_line(sys.argv)
   File "/home/jdoepke/Development/django_test/.venv/lib/python3.6/site-
 packages/django/core/management/__init__.py", line 371, in
 execute_from_command_line
 utility.execute()
   File "/home/jdoepke/Development/django_test/.venv/lib/python3.6/site-
 packages/django/core/management/__init__.py", line 365, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/jdoepke/Development/django_test/.venv/lib/python3.6/site-
 packages/django/core/management/__init__.py", line 216, in fetch_command
 klass = load_command_class(app_name, subcommand)
   File "/home/jdoepke/Development/django_test/.venv/lib/python3.6/site-
 packages/django/core/management/__init__.py", line 36, in
 load_command_class
 module = import_module('%s.management.commands.%s' % (app_name, name))
   File
 
"/home/jdoepke/Development/django_test/.venv/lib/python3.6/importlib/__init__.py",
 line 126, in import_module
 return _bootstrap._gcd_import(name[level:], package, level)
   File "", line 994, in _gcd_import
   File "", line 971, in _find_and_load
   File "", line 955, in
 _find_and_load_unlocked
   File "", line 665, in _load_unlocked
   File "", line 678, in exec_module
   File "", line 219, in
 _call_with_frames_removed
   File "/home/jdoepke/Development/django_test/.venv/lib/python3.6/site-
 packages/django/core/management/commands/makemigrations.py", line 10, in
 
 from django.db.migrations.autodetector import MigrationAutodetector
   File "/home/jdoepke/Development/django_test/.venv/lib/python3.6/site-
 packages/django/db/migrations/autodetector.py", line 11, in 
 from django.db.migrations.questioner import MigrationQuestioner
   File "/home/jdoepke/Development/django_test/.venv/lib/python3.6/site-
 packages/django/db/migrations/questioner.py", line 9, in 
 from .loader import MigrationLoader
   File "/home/jdoepke/Development/django_test/.venv/lib/python3.6/site-
 packages/django/db/migrations/loader.py", line 8, in 
 from django.db.migrations.recorder import MigrationRecorder
   File "/home/jdoepke/Development/django_test/.venv/lib/python3.6/site-
 packages/django/db/migrations/recorder.py", line 9, in 
 class MigrationRecorder:
   File "/home/jdoepke/Development/django_test/.venv/lib/python3.6/site-
 packages/django/db/migrations/recorder.py", line 22, in MigrationRecorder
 class Migration(models.Model):
   File "/home/jdoepke/Development/django_test/.venv/lib/python3.6/site-
 packages/django/db/models/base.py", line 100, in __new__
 app_config = apps.get_containing_app_config(module)
   File "/home/jdoepke/Development/django_test/.venv/lib/python3.6/site-
 packages/django/apps/registry.py", line 244, in get_containing_app_config
 self.check_apps_ready()
   File "/home/jdoepke/Development/django_test/.venv/lib/python3.6/site-
 packages/django/apps/registry.py", line 127, in check_apps_ready
 raise AppRegistryNotReady("Apps aren't loaded yet.")
 django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.
 }}}

-- 
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/051.b064a3352b72c25fc2eb07d8608231ab%40djangoproject.com.
For more 

Re: [Django] #29125: Q.deconstruct() is nondeterministic if the Q has multiple kwargs (was: BUG: Q object deconstruct is inconsistent when passing multiple kwargs.)

[Django]

#29125: Q.deconstruct() is nondeterministic if the Q has multiple kwargs
-+-
 Reporter:  Harro|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Release blocker  |   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 Tim Graham):

 * keywords:  has_test =>
 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/9694 PR]

 I don't understand why `{'_connector': 'AND'}` should be omitted but I
 implemented 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/066.914a2e683a6c1596d56bc99af3c39d00%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28972: `RelatedObjectDoesNotExist` during `loaddata` of models with multi-table inheritance

[Django]

#28972: `RelatedObjectDoesNotExist` during `loaddata` of models with multi-table
inheritance
-+-
 Reporter:  Kal Sze  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core |  Version:  2.0
  (Serialization)|
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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


Comment:

 I don't think the output you proposed could be deserialized properly. If
 `baselicense_ptr` isn't included in the `adobephotoshoplicense` object,
 there's no way to link `adobephotoshoplicense` to its `baselicense` object
 since `user` doens't uniquely identify a `baselicense`.

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

Re: [Django] #29127: Running tagged tests hides any with syntax errors (was: manage.py executing tagged tests with syntax error does not show them)

[Django]

#29127: Running tagged tests hides any with syntax errors
-+-
 Reporter:  Kryštof Řeháček  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  tests, tagged-   | Triage Stage:  Accepted
  tests, SyntaxError |
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:

 The problem may be in `django.test.runner.filter_tests_by_tags()`.

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

Re: [Django] #29024: `TestContextDecorator` never exits if `setUp` fails in tests

[Django]

#29024: `TestContextDecorator` never exits if `setUp` fails in tests
-+-
 Reporter:  Anthony King |Owner:  Shahbaj
 |  Sayyad
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Anthony King):

 Hi Shahbaj,

 I saw your post in the mailing list.


 So how we've done it internally is like this:

 {{{
 #!python

 class TestContextDecorator(DjangoTestContextDecorator):
 def decorate_class(self, cls):
 # https://code.djangoproject.com/ticket/29024

 if issubclass(cls, TestCase):
 decorated_setUp = cls.setUp

 @wraps(decorated_setUp)
 def setUp(inner_self):
 context = self.enable()
 if self.attr_name:
 setattr(inner_self, self.attr_name, context)
 inner_self.addCleanup(self.disable)
 decorated_setUp(inner_self)

 cls.setUp = setUp
 return cls
 raise TypeError('Can only decorate subclasses of
 unittest.TestCase')
 }}}

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

Re: [Django] #27795: Audit force_text invocations

[Django]

#27795: Audit force_text invocations
-+-
 Reporter:  Claude Paroz |Owner:  Claude
 Type:   |  Paroz
  Cleanup/optimization   |   Status:  assigned
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"b8a41a2872624a6d9e61308932dd81d001e31eb9" b8a41a28]:
 {{{
 #!CommitTicketReference repository=""
 revision="b8a41a2872624a6d9e61308932dd81d001e31eb9"
 Refs #27795 -- Removed force_bytes() in django.test.client where possible.
 }}}

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

Re: [Django] #29127: manage.py executing tagged tests with syntax error does not show them (was: manage.py executting tagged tests with syntax error does not show them)

[Django]

#29127: manage.py executing tagged tests with syntax error does not show them
-+-
 Reporter:  Kryštof Řeháček  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  tests, tagged-   | Triage Stage:
  tests, SyntaxError |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  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.b11d039d7338eb219ad92c988d2cfdcb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #29127: manage.py executting tagged tests with syntax error does not show them

[Django]

#29127: manage.py executting tagged tests with syntax error does not show them
-+-
   Reporter:  Kryštof|  Owner:  nobody
  Řeháček|
   Type:  Bug| Status:  new
  Component:  Testing|Version:  2.0
  framework  |   Keywords:  tests, tagged-
   Severity:  Normal |  tests, SyntaxError
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 When I execute tests with syntax error without any argument then it shows
 `SyntaxError: invalid syntax` as expected but when I execute tagged tests,
 then it shows that it ran 0 tests and it is OK and even error. So when
 tests with syntax executed with the --tag="some_tag" argument and they
 have syntax error then they complete with OK status.

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

Re: [Django] #20530: Incorrect QUERY_STRING handling on Python 3

[Django]

#20530: Incorrect QUERY_STRING handling on Python 3
-+-
 Reporter:  Armin Ronacher   |Owner:  Aymeric
 |  Augustin
 Type:  Bug  |   Status:  closed
Component:  Core (URLs)  |  Version:  1.5
 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
-+-

Comment (by Tim Graham ):

 In [changeset:"4206765a5b157bd6149d9e1aaf459fd4296e9b89" 4206765]:
 {{{
 #!CommitTicketReference repository=""
 revision="4206765a5b157bd6149d9e1aaf459fd4296e9b89"
 Refs #20530 -- Added a test for test client query string encoding.

 7bb627936034c1b9500a8d250cce75b30f980b23 is only tested in
 django-contrib-comments.
 }}}

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

Re: [Django] #29125: BUG: Q object deconstruct is inconsistent when passing multiple kwargs.

[Django]

#29125: BUG: Q object deconstruct is inconsistent when passing multiple kwargs.
-+-
 Reporter:  Harro|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  has_test | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * stage:  Unreviewed => Accepted


Comment:

 Apart from preserving the `kwargs` nature of some children I'd argue that
 `Q.deconstruct` should also use `django.utils.models.Q` as path instead of
 `django.db.models.query_utils.Q` like we do with
 `django.db.models.fields.*` and should avoid adding `_connector` if it's
 `'AND'` and `_negated` if it's `False` to `kwargs` because these are the
 default values.

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

Re: [Django] #24270: Wheel package does not contain 'extras' directory

[Django]

#24270: Wheel package does not contain 'extras' directory
-+
 Reporter:  Matt Layman  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Packaging|  Version:  1.7
 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 Tim Graham ):

 In [changeset:"0edcc723e728f57de0314e79b40502e9c78d" 0edcc72]:
 {{{
 #!CommitTicketReference repository=""
 revision="0edcc723e728f57de0314e79b40502e9c78d"
 [2.0.x] Fixed #24270 -- Doc'd that django_bash_completion is only in the
 source distribution.

 Backport of 43b148f41fa7a5c3f74e0198d9c72074abe9a9bc 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/066.1479dc8d61799916840e277700684438%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24270: Wheel package does not contain 'extras' directory

[Django]

#24270: Wheel package does not contain 'extras' directory
-+
 Reporter:  Matt Layman  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Packaging|  Version:  1.7
 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:"43b148f41fa7a5c3f74e0198d9c72074abe9a9bc" 43b148f]:
 {{{
 #!CommitTicketReference repository=""
 revision="43b148f41fa7a5c3f74e0198d9c72074abe9a9bc"
 Fixed #24270 -- Doc'd that django_bash_completion is only in the source
 distribution.
 }}}

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

Re: [Django] #28171: Raise an exception if Form's empty_permitted and use_required_attribute arguments conflict

[Django]

#28171: Raise an exception if Form's empty_permitted and use_required_attribute
arguments conflict
-+-
 Reporter:  Vlastimil Zíma   |Owner:  Herbert
 Type:   |  Fortes
  Cleanup/optimization   |   Status:  assigned
Component:  Forms|  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 Herbert Fortes):

 * owner:  (none) => Herbert Fortes
 * status:  new => assigned


Comment:

 Hi,

 I created a Pull Request to close this ticket:

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



 Regards,
 Herbert

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

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

[Django]

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

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

Re: [Django] #28862: Removing a field from index_together/unique_together and from the model generates a migration that crashes

[Django]

#28862: Removing a field from index_together/unique_together and from the model
generates a migration that crashes
-+-
 Reporter:  Artem Maslovskiy |Owner:  Ramiro
 |  Morales
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  models migrations| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ed Morley):

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

[Django] #29126: Model.update_or_create method pk issue.

[Django]

#29126: Model.update_or_create method pk issue.
-+-
   Reporter:  Théo   |  Owner:  nobody
  "Bob" Massard  |
   Type:  Bug| Status:  new
  Component:  Database   |Version:  2.0
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Upon using the `update_or_create` method on a Model which has a modified
 `pk` field, an IntegrityError happens.

 `psycopg2.IntegrityError: duplicate key value violates unique constraint
 "tags_pkey"`

 The PrimaryKey is an IntegerField with a modified `db_column`.

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

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

[Django]

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

Comment (by Carlton Gibson):

 Related #27682

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

Re: [Django] #27682: Add more dependencies to extras_require (eg sqlparse, PyYAML)

[Django]

#27682: Add more dependencies to extras_require (eg sqlparse, PyYAML)
-+-
 Reporter:  Ed Morley|Owner:  Ed Morley
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Packaging|  Version:  master
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

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


Comment:

 I'm going to resolve this as a duplicate of #28905. Whilst this issue was
 prior, #28905 is further along. (It has a 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.f9191d059baf2aa0dadb9ad5682aaa96%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

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

[Django]

#27685: Allow autoreloader to use watchman
-+-
 Reporter:  Aymeric Augustin |Owner:  Tom
 Type:   |  Forbes
  Cleanup/optimization   |   Status:  assigned
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tom Forbes):

 * owner:  nobody => Tom Forbes
 * status:  new => assigned


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

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

Re: [Django] #28236: Integrate dj-database-url into Django

[Django]

#28236: Integrate dj-database-url into Django
-+-
 Reporter:  Kenneth Reitz|Owner:  Tom
 |  Forbes
 Type:  New feature  |   Status:  assigned
Component:  Core (Other) |  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  settings, dj-| Triage Stage:
  database-url, database_url |  Someday/Maybe
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Tom Forbes):

 * owner:  nobody => Tom Forbes
 * status:  new => assigned


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

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

Re: [Django] #29125: BUG: Q object deconstruct is inconsistent when passing multiple kwargs.

[Django]

#29125: BUG: Q object deconstruct is inconsistent when passing multiple kwargs.
-+-
 Reporter:  Harro|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  has_test | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by Harro:

Old description:

> Here is a branch with a randomly failing test that proves this:
> https://github.com/hvdklauw/django/blob/bug/q_destruct/tests/queries/test_q.py#L63
>
> The biggest issue is that now makemigrations is detecting changes since
> we upgraded to django 2.0 (only with python 3.5) that aren't changes at
> all, just reordered kwargs on the Q objects in out limit_choices_to on
> some foreignkeys.
>
> This also means we randomly can't commit/release because we have pre-
> commit hooks and CI that runs ''makemigrations --check --dryrun''
>
> Upgrading to python 3.6 would fix it (because of ordered kwargs) but as
> Ubuntu 16.04 is still the latest LTS, python 3.5 is what we are stuck
> with.

New description:

 Here is a branch with a randomly failing test that proves this:
 
https://github.com/hvdklauw/django/blob/bug/q_destruct/tests/queries/test_q.py#L63

 The biggest issue is that now makemigrations is detecting changes since we
 upgraded to django 2.0 (only with python 3.5) that aren't changes at all,
 just reordered kwargs on the Q objects in out limit_choices_to on some
 foreignkeys.

 This also means we randomly can't commit/release because we have pre-
 commit hooks and CI that runs ''makemigrations --check --dryrun''

 Upgrading to python 3.6 would fix it (because of ordered kwargs) but as
 Ubuntu 16.04 is still the latest LTS, python 3.5 is what we are stuck
 with.

 This is the commit that broke it:
 
https://github.com/django/django/commit/508b5debfb16843a8443ebac82c1fb91f15da687

--

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

[Django] #29125: BUG: Q object deconstruct is inconsistent when passing multiple kwargs.

[Django]

#29125: BUG: Q object deconstruct is inconsistent when passing multiple kwargs.
-+-
   Reporter:  Harro  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  2.0
  layer (models, ORM)|
   Severity:  Release|   Keywords:  has_test
  blocker|
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Here is a branch with a randomly failing test that proves this:
 
https://github.com/hvdklauw/django/blob/bug/q_destruct/tests/queries/test_q.py#L63

 The biggest issue is that now makemigrations is detecting changes since we
 upgraded to django 2.0 (only with python 3.5) that aren't changes at all,
 just reordered kwargs on the Q objects in out limit_choices_to on some
 foreignkeys.

 This also means we randomly can't commit/release because we have pre-
 commit hooks and CI that runs ''makemigrations --check --dryrun''

 Upgrading to python 3.6 would fix it (because of ordered kwargs) but as
 Ubuntu 16.04 is still the latest LTS, python 3.5 is what we are stuck
 with.

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

Re: [Django] #24270: Wheel package does not contain 'extras' directory

[Django]

#24270: Wheel package does not contain 'extras' directory
-+
 Reporter:  Matt Layman  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Packaging|  Version:  1.7
 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 Carlton Gibson):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/9690 PR]

 Scopes reference to "source distribution" as per suggestion. Should
 resolve as Fixed. (Further PRs always welcome, if a better solution
 presents itself.)

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

Re: [Django] #18937: Use modern Python packaging metadata standard (1.2, PEP 345)

[Django]

#18937: Use modern Python packaging metadata standard (1.2, PEP 345)
-+
 Reporter:  Marc Tamlyn  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Packaging|  Version:  master
 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:

 So 5 years later this ticket is no longer applicable.

 * The original blog post linked suggested moving to Setuptools as a
 possible option. This was done in
 
[https://github.com/django/django/commit/66f546b90624297858b0f958abbe5c2b3e8bdffb
 66f546b906].
 * Setuptools handles
 
[https://github.com/pypa/setuptools/blob/d10a1bb476db25dc888b5b4aad9d81ffa245ea30/setuptools/dist.py#L39-L48
 writing the PKG-INFO file, including version 1.2 metadata]
 * The generated `PKG-INFO` file **does** use `Metadata-Version: 1.2`:

 {{{
 Metadata-Version: 1.2
 Name: Django
 Version: 2.1.dev20180208153510
 ...
 }}}

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