Re: [Django] #29142: OuterRef not being treated as an F Expression

[Django]

#29142: OuterRef not being treated as an F Expression
-+-
 Reporter:  Michael Barr |Owner:  Matthew
 |  Schinckel
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Matthew Schinckel):

 * status:  new => assigned
 * owner:  nobody => Matthew Schinckel


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

Re: [Django] #27991: Add 'obj' kwarg to InlineModelAdmin.has_add_permission()

[Django]

#27991: Add 'obj' kwarg to InlineModelAdmin.has_add_permission()
-+-
 Reporter:  Olivier  |Owner:  Vladimir
 Type:   |  Ivanov
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  1.10
 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 Jon Dufresne):

 * needs_better_patch:  1 => 0


Comment:

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

Re: [Django] #29149: django-admin migrate fails on 2.0 when a project contains squashed migrations from an earlier version

[Django]

#29149: django-admin migrate fails on 2.0 when a project contains squashed
migrations from an earlier version
-+--
 Reporter:  Dan Collins  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  2.0
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by Dan Collins):

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


Comment:

 Oh for fuck's sake, it's because `2to3` decided that `'exams'` needed to
 be a bytestring.

 {{{
 replaces = [(b'exams', '0001_squashed_0002_auto_20170518_1851'),
 (b'exams', '0002_auto_20170519_2125')]
 }}}

 (and of course `(b'exams', 'whatever')` is not `in [('exams', 'whatever'),
 ...]`)

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

Re: [Django] #29152: management commands - more control on ArgumentParser initialization

[Django]

#29152: management commands - more control on ArgumentParser initialization
-+-
 Reporter:  Dmitry   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Management |  Version:  2.0
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Dmitry):

 * type:  New feature => Cleanup/optimization


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

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

Re: [Django] #29152: management commands - more control on ArgumentParser initialization (was: management commands rigid ArgumentParser initialization)

[Django]

#29152: management commands - more control on ArgumentParser initialization
-+-
 Reporter:  dmippolitov  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  2.0
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

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

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

[Django] #29152: management commands rigid ArgumentParser initialization

[Django]

#29152: management commands rigid ArgumentParser initialization
-+-
   Reporter:  Dmitry |  Owner:  nobody
   Type:  New| Status:  new
  feature|
  Component:  Core   |Version:  2.0
  (Management commands)  |
   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  |
-+-
 Hello everyone.
 Noticed today that there is no way to customize CommandParser
 (ArgumentParser subclass), initialized in management commands
 
(https://github.com/django/django/blob/master/django/core/management/base.py#L227).
 There is no option (or i was unable to find it - please correct me in this
 case) to pass any kwargs in CommandParser constructor. The public method
 create_parser contains some django-related hard-coded add_arguments calls,
 so overriding it directly leads to some copy paste.

 I needed to use some custom formatter for ArgumentParser
 
(https://docs.python.org/3/library/argparse.html?highlight=argparse#argparse.ArgumentDefaultsHelpFormatter)
 to add default values to help page, but was unable to do this properly.
 There is also some other usefull keyword arguments available in
 ArgumentParser.

 As a proposal a new method could be added to BaseCommand (let's say
 BaseCommand.get_parser_instance), for example like this:

 {{{
 def get_parser_instance(self):
 return CommandParser(
 self, prog="%s %s" % (os.path.basename(prog_name),
 subcommand),
 description=self.help or None,
 )

 def create_parser(self, prog_name, subcommand)::
parser = self.get_parser_instance()
... etc
 }}}

 This should not break anything in BaseCommand, but will allow have more
 control on parser's creation overriding just get_parser_instance method.
 Please sorry for mistakes.

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

Re: [Django] #29019: createsuperuser crashes if a ManyToManyField is in REQUIRED_FIELDS

[Django]

#29019: createsuperuser crashes if a ManyToManyField is in REQUIRED_FIELDS
--+---
 Reporter:  James Kirsop  |Owner:  Williams Mendez
 Type:  Bug   |   Status:  assigned
Component:  contrib.auth  |  Version:  2.0
 Severity:  Normal|   Resolution:
 Keywords:  user custom   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+---
Changes (by Williams Mendez):

 * owner:  nobody => Williams Mendez
 * 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/069.1e0a8a776d813012a65da6aeca6d3777%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29147: Postgres JSONField missing to_python

[Django]

#29147: Postgres JSONField missing to_python
-+-
 Reporter:  Javier Buzzi |Owner:  Williams
 |  Mendez
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  1.9
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Williams Mendez):

 Yeah, it's totally right:


 {{{
 will_test=# select '"hello"'::json ;
   json
 -
  "hello"
 (1 row)
 }}}

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

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

Re: [Django] #29142: OuterRef not being treated as an F Expression

[Django]

#29142: OuterRef not being treated as an F Expression
-+-
 Reporter:  Michael Barr |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Matthew Schinckel):

 Ah, is it that `F` gets turned into a `Ref`?

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

Re: [Django] #29142: OuterRef not being treated as an F Expression

[Django]

#29142: OuterRef not being treated as an F Expression
-+-
 Reporter:  Michael Barr |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Matthew Schinckel):

 Yeah, I think this is a bug.

 I'm not sure where `F` gets it's `relabeled_clone` from, because
 `OuterRef` inherits directly from `F`.

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

[Django] #29151: Aliasing pgettext_lazy makes it work unexpected

[Django]

#29151: Aliasing pgettext_lazy makes it work unexpected
+
   Reporter:  shutterfire   |  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  Internationalization  |Version:  2.0
   Severity:  Normal|   Keywords:  i18n
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 Aliasing pgettext_lazy, e.g. to "_" or "p_" makes it "forget" to create
 the msgctxt or to work at all

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

Re: [Django] #29147: Postgres JSONField missing to_python

[Django]

#29147: Postgres JSONField missing to_python
-+-
 Reporter:  Javier Buzzi |Owner:  Williams
 |  Mendez
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  1.9
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Williams Mendez):

 At first I thought the same, but when I try to store a String into a
 postgres 'jsonb' field it crashes.  Same when I try to fetch a string as a
 json:


 {{{
 will_test=# select 'hello'::json ;
 ERROR:  invalid input syntax for type json
 LINE 1: select 'hello'::json ;
^
 DETAIL:  Token "hello" is invalid.
 CONTEXT:  JSON data, line 1: hello


 will_test=# select '{}'::json ;
  json
 --
  {}
 (1 row)
 }}}

 I'll do some research on that topic.

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

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

Re: [Django] #29133: call_command() fails if a required option is passed in via **options

[Django]

#29133: call_command() fails if a required option is passed in via **options
-+-
 Reporter:  Alex Tomic   |Owner:  Alex
 Type:   |  Tomic
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Management |  Version:  2.0
  commands)  |
 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 Tim Graham):

 * needs_better_patch:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 After looking at the fix, I simplified it a bit and I think it's fine to
 fix this. I left comments for improvement on the 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.07547f8933a197b54f52fa23757872d2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29144: DjangoTranslation.merge() loses catalog fallbacks (was: `DjangoTranslation.merge` loses catalog fallbacks)

[Django]

#29144: DjangoTranslation.merge() loses catalog fallbacks
-+-
 Reporter:  Patryk Zawadzki  |Owner:  Patryk
 |  Zawadzki
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  2.0
  Internationalization   |
 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 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/064.620b6d0c3ee98fced39f31b5c7e7e112%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29145: Allow CIText values to be compared as the database would compare them (case-insensitively) (was: CIText and __eq__)

[Django]

#29145: Allow CIText values to be compared as the database would compare them
(case-insensitively)
--+
 Reporter:  Дилян Палаузов|Owner:  nobody
 Type:  Cleanup/optimization  |   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):

 * type:  Uncategorized => Cleanup/optimization
 * component:  Uncategorized => contrib.postgres
 * stage:  Unreviewed => Accepted


Old description:

> For comparing two model instances on equality one can iterate over all
> fields in the instance and compare the fields for equality, without
> querying the database.  This does not work for
> django.contrib.postgres.fields.citext.CIText, where "a" is equal to "A".
>
> Under the premise that python and postgresql use the same collation,
> tweak the system to compare two citext-fields in a case-insensitive
> manner for equality, without touching the database (as it is done for all
> other fields).
>
> Attaching to each citext-field returned from the model an {{{__eq__}}}
> doing {{{.lower()}}} could help.

New description:

 For comparing two model instances on equality one can iterate over all
 fields in the instance and compare the fields for equality, without
 querying the database.  This does not work for
 django.contrib.postgres.fields.citext.CIText, where "a" is equal to "A".

 Under the premise that python and postgresql use the same collation, tweak
 the system to compare two citext-fields in a case-insensitive manner for
 equality, without touching the database (as it is done for all other
 fields).

 Attaching to each citext-field returned from the model an `__eq__` doing
 `.lower()` could help.

--

Comment:

 Tentatively accepting, although I'm not certain about the complexity this
 will require. I'm thinking that whenever a value is assigned to a CI
 field, that value will be have to wrapped in a `str` subclass that
 implements `__eq__()` to do the case-insensitive comparison. I guess a
 perfect implementation that considers database collation, for example, may
 not be feasible.

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

Re: [Django] #29149: django-admin migrate fails on 2.0 when a project contains squashed migrations from an earlier version

[Django]

#29149: django-admin migrate fails on 2.0 when a project contains squashed
migrations from an earlier version
-+--
 Reporter:  Dan Collins  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by Tim Graham):

 Can you provide a minimal project that reproduces the issue? I'm not sure
 we can debug the issue without that.

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

Re: [Django] #29147: Postgres JSONField missing to_python

[Django]

#29147: Postgres JSONField missing to_python
-+-
 Reporter:  Javier Buzzi |Owner:  Williams
 |  Mendez
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  1.9
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham):

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


Comment:

 I don't think that change is correct because
 
[https://github.com/django/django/blob/16436f3751e9eec67a7b80b25c8e7d29a34be67e/tests/postgres_tests/test_json.py#L46-L50
 a string is valid JSON] -- to treat it differently would break backwards
 compatibility.

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

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

Re: [Django] #29142: OuterRef not being treated as an F Expression

[Django]

#29142: OuterRef not being treated as an F Expression
-+-
 Reporter:  Michael Barr |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * cc: Matthew Schinckel (added)
 * 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/073.141f32655aac62518eba405826152142%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29062: "database table locked errors" when using sqlite in-memory database with LiveServerTestCase

[Django]

#29062: "database table locked errors" when using sqlite in-memory database with
LiveServerTestCase
-+-
 Reporter:  Juozas Masiulis  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  2.0
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  sqlite, testing, | Triage Stage:
  databases  |  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:   => needsinfo


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

Re: [Django] #29150: Pretty display of JSONField data in forms

[Django]

#29150: Pretty display of JSONField data in forms
-+-
 Reporter:  Andrew Wilson|Owner:  (none)
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  contrib.postgres |  Version:  2.0
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-
Changes (by Tim Graham):

 * status:  new => closed
 * resolution:   => duplicate
 * has_patch:  1 => 0
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Ready for checkin => Unreviewed


Comment:

 Duplicate of #26482 (closed as wontfix).

-- 
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.8a1ea2acf893c2c05b8d9283b41bccec%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:
 |  ChillarAnand
 Type:  Bug  |   Status:  assigned
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 Patryk Zawadzki):

 * cc: Patryk Zawadzki (added)


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

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

Re: [Django] #29150: Pretty display of JSONField data in forms

[Django]

#29150: Pretty display of JSONField data in forms
-+-
 Reporter:  Andrew Wilson|Owner:  (none)
 Type:  Uncategorized|   Status:  new
Component:  contrib.postgres |  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-
Changes (by Herbert Fortes):

 * cc: Herbert Fortes (added)
 * stage:  Unreviewed => Ready for checkin


Comment:

 Hi,

 IMHO it is a good idea.

 Assign the ticket to yourself and do the PR.



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

Re: [Django] #29141: Warning about password truncation with BCryptPasswordHasher incorrect

[Django]

#29141: Warning about password truncation with BCryptPasswordHasher incorrect
-+-
 Reporter:  Markus Holtermann|Owner:  Markus
 Type:   |  Holtermann
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  2.0
 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 Markus Holtermann):

 * needs_docs:  1 => 0


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

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

Re: [Django] #22449: Colorize output of test results

[Django]

#22449: Colorize output of test results
-+-
 Reporter:  Jake Rothenbuhler|Owner:  Yuri
 |  Shikanov
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 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 Yuri Shikanov):

 * needs_better_patch:  1 => 0


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

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

Re: [Django] #28988: Multi-table inheritance breaks GenericRelation querying

[Django]

#28988: Multi-table inheritance breaks GenericRelation querying
--+
 Reporter:  robwa |Owner:  (none)
 Type:  Bug   |   Status:  new
Component:  contrib.contenttypes  |  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:  0 |UI/UX:  0
--+
Changes (by robwa):

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


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

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

Re: [Django] #28988: Multi-table inheritance breaks GenericRelation querying

[Django]

#28988: Multi-table inheritance breaks GenericRelation querying
--+
 Reporter:  robwa |Owner:  robwa
 Type:  Bug   |   Status:  assigned
Component:  contrib.contenttypes  |  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:  0 |UI/UX:  0
--+
Changes (by Carlton Gibson):

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