Re: [Django] #24781: lazy() may need a __repr__ for Python 2 (was: incorrect command in doc: Applications)

[Django]

#24781: lazy() may need a __repr__ for Python 2
---+
 Reporter:  jdh13  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Utilities  |  Version:  1.7
 Severity:  Normal |   Resolution:
 Keywords:  python2| Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timgraham):

 * keywords:   => python2
 * component:  Documentation => Utilities


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

Re: [Django] #26021: Standardize on hanging indent in documentation

[Django]

#26021: Standardize on hanging indent in documentation
--+
 Reporter:  timgraham |Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  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
--+
Changes (by timgraham):

 * status:  assigned => new
 * owner:  anurag-ks =>
 * easy:  0 => 1


Comment:

 I'm sure there are other places to revise, but I committed my patch for
 now since no one has picked this up in a while and those weird
 indentations bother me when I see them.

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

Re: [Django] #26021: Standardize on hanging indent in documentation

[Django]

#26021: Standardize on hanging indent in documentation
-+-
 Reporter:  timgraham|Owner:  anurag-ks
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  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:"e475e849703d937e158e75e7a6d9cb99090857f6" e475e849]:
 {{{
 #!CommitTicketReference repository=""
 revision="e475e849703d937e158e75e7a6d9cb99090857f6"
 Refs #26021 -- Used hanging indentation in some doc examples.
 }}}

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

Re: [Django] #26021: Standardize on hanging indent in documentation

[Django]

#26021: Standardize on hanging indent in documentation
-+-
 Reporter:  timgraham|Owner:  anurag-ks
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  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:"dbd72b850b487be37df2940d16697a2d57b73ac6" dbd72b8]:
 {{{
 #!CommitTicketReference repository=""
 revision="dbd72b850b487be37df2940d16697a2d57b73ac6"
 [1.9.x] Refs #26021 -- Used hanging indentation in some doc examples.

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

Re: [Django] #25897: Managers defined on non-abstract base classes are in fact inherited by child classes.

[Django]

#25897: Managers defined on non-abstract base classes are in fact inherited by
child classes.
-+-
 Reporter:  poleha   |Owner:  poleha
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  manager-inheritance  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * keywords:  manager, inheritance => manager-inheritance


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

Re: [Django] #20932: Issues with model Manager and inheritance.

[Django]

#20932: Issues with model Manager and inheritance.
-+-
 Reporter:  loic84   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  manager-inheritance  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * keywords:   => manager-inheritance


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

Re: [Django] #25556: Add DatePart db expression to allow complex lookups on date parts (e.g. year, month, day)

[Django]

#25556: Add DatePart db expression to allow complex lookups on date parts (e.g.
year, month, day)
-+-
 Reporter:  ryuusenshi   |Owner:
 |  ryuusenshi
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  db expressions   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Duplicate of #25774 as far as I can tell.

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

Re: [Django] #20888: Index ordering in index_together and unique_together

[Django]

#20888: Index ordering in index_together and unique_together
-+-
 Reporter:  anonymous|Owner:
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  index, order, db-| Triage Stage:  Accepted
  indexes|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * keywords:  index, order => index, order, db-indexes


Old description:

> Hi,
>
> Currently the index_together tuples do not support index ordering using +
> / -.
>
> If I have the following table:
> class Messages:
>user_id,
>rating,
>last_update,
>
>index_together=[
>  ['user_id', 'rating',  'last_update',] # sorted ASC by default
>   ]
>
> So for MySQL, the following query cannot make use of the index:
>
> Messages.objects.filter(user_id=xxx).order_by('+rating','-last_update')
>
> Pardon me if it actually can make use of the index.
>
> I know there are workarounds, such as negating values to make a DESC
> ordering become ASC ordering.
> But it is just nice to have such a feature.
> Btw, what is the reason for not having this feature?

New description:

 Hi,

 Currently the index_together tuples do not support index ordering using +
 / -.

 If I have the following table:
 {{{
 class Messages:
user_id,
rating,
last_update,

index_together=[
  ['user_id', 'rating',  'last_update',] # sorted ASC by default
   ]
 }}}
 So for MySQL, the following query cannot make use of the index:

 Messages.objects.filter(user_id=xxx).order_by('+rating','-last_update')

 Pardon me if it actually can make use of the index.

 I know there are workarounds, such as negating values to make a DESC
 ordering become ASC ordering.
 But it is just nice to have such a feature.
 Btw, what is the reason for not having this feature?

--

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

Re: [Django] #25201: Allow use_for_related_fields via as_manager()

[Django]

#25201: Allow use_for_related_fields via as_manager()
-+-
 Reporter:  litchfield   |Owner:
 |  andersonresende
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  use_for_related_fields |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * keywords:   => use_for_related_fields


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

Re: [Django] #26167: Support for Functional Indexes (aka Indexes on Expressions)

[Django]

#26167: Support for Functional Indexes (aka Indexes on Expressions)
-+-
 Reporter:  cancan101|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  db-indexes   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * keywords:   => db-indexes


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

Re: [Django] #26610: Case insensitive indexes

[Django]

#26610: Case insensitive indexes
-+-
 Reporter:  shadow7412   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  index charfield  | Triage Stage:  Accepted
  textfield case insensitive |
  optimisation db-indexes|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * keywords:  index charfield textfield case insensitive optimisation =>
 index charfield textfield case insensitive optimisation db-indexes


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

Re: [Django] #26573: Empty 'AssertionError' exception message on syntax error ({% else if %}) in templates

[Django]

#26573: Empty 'AssertionError' exception message on syntax error ({% else if 
%}) in
templates
-+-
 Reporter:  vakorol  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Template system  |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  assertionerror   | Triage Stage:  Accepted
  template elsif |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by inondle):

 Cool, here's my pull request:

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

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

Re: [Django] #14415: Multiple aliases for one database: testing problems

[Django]

#14415: Multiple aliases for one database: testing problems
-+-
 Reporter:  shai |Owner:  boaz85
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  multidb, multiple| Triage Stage:  Accepted
  databases, multiple aliases|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timgraham):

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

Re: [Django] #26602: Provide a way to manage grouping with RawSQL (was: RawSQL window functions break count())

[Django]

#26602: Provide a way to manage grouping with RawSQL
-+-
 Reporter:  daggaz   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  QuerySet.extra   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * type:  Uncategorized => New feature


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

Re: [Django] #25774: Refactor of datetime expressions and better, official support for right-hand-side date part extraction

[Django]

#25774: Refactor of datetime expressions and better, official support for right-
hand-side date part extraction
-+-
 Reporter:  ryuusenshi   |Owner:  jarshwah
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  db,expressions,date,time,extract,transform|
  1.10   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * keywords:  db,expressions,date,time,extract,transform =>
 db,expressions,date,time,extract,transform 1.10
 * needs_better_patch:  0 => 1


Comment:

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

Re: [Django] #24075: Can't migrate contenttypes and auth to zero

[Django]

#24075: Can't migrate contenttypes and auth to zero
+-
 Reporter:  apollo13|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Ready for checkin
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+-
Changes (by timgraham):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #21379: class AbstractUser: validators should compile re with Unicode

[Django]

#21379: class AbstractUser: validators should compile re with Unicode
--+
 Reporter:  anonymous |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  1.10  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * keywords:   => 1.10
 * severity:  Release blocker => Normal


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

Re: [Django] #15667: Implement template-based widget rendering

[Django]

#15667: Implement template-based widget rendering
-+
 Reporter:  brutasse |Owner:
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  form-rendering 1.10  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by timgraham):

 * keywords:  form-rendering => form-rendering 1.10


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

Re: [Django] #24227: isinstance checks on ForeignKey/ManyToManyField should be replaced with field.many_to_one/field.many_to_many

[Django]

#24227: isinstance checks on ForeignKey/ManyToManyField should be replaced with
field.many_to_one/field.many_to_many
-+-
 Reporter:  coldmind |Owner:
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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

Re: [Django] #24305: Allow overriding abstract model fields (was: Allow to override abstract model fields)

[Django]

#24305: Allow overriding abstract model fields
-+-
 Reporter:  knbk |Owner:  ar45
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

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

Re: [Django] #24227: isinstance checks on ForeignKey/ManyToManyField should be replaced with field.many_to_one/field.many_to_many (was: isinstance checks on ManyToManyField should be replaced with fie

[Django]

#24227: isinstance checks on ForeignKey/ManyToManyField should be replaced with
field.many_to_one/field.many_to_many
-+-
 Reporter:  coldmind |Owner:  coldmind
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:  0 => 1
 * stage:  Ready for checkin => Accepted


Comment:

 Claude abandoned [https://github.com/django/django/pull/6236 the PR] to
 change instances of `isinstance(field, ForeignKey)` to
 `field.many_to_one`. If someone sees an advantage to those changes, feel
 free to send a 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/066.4e3d7926aabd31c2c6a6bdb71066bc04%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24588: Improve handling apps without migrations while running migrate command.

[Django]

#24588: Improve handling apps without migrations while running migrate command.
--+
 Reporter:  coldmind  |Owner:  coldmind
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Migrations|  Version:  1.8
 Severity:  Normal|   Resolution:  wontfix
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

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


Comment:

 I guess that boat has sailed now.

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

Re: [Django] #15667: Implement template-based widget rendering

[Django]

#15667: Implement template-based widget rendering
+
 Reporter:  brutasse|Owner:
 Type:  New feature |   Status:  new
Component:  Forms   |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  form-rendering  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by timgraham):

 * needs_better_patch:  1 => 0
 * needs_docs:  1 => 0


Comment:

 A small issue detailed in the PR description remains, but otherwise I
 think the [https://github.com/django/django/pull/6498 updated PR] is ready
 for review.

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

Re: [Django] #21379: class AbstractUser: validators should compile re with Unicode

[Django]

#21379: class AbstractUser: validators should compile re with Unicode
-+
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  master
 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
-+

Comment (by claudep):

 So beside the [https://github.com/django/django/pull/6494 original PR]
 which also added Unicode username on Python 2, we have now the
 [https://github.com/django/django/pull/6600 alternative PR] to keep ASCII-
 only usernames on Python 2 and Unicode usernames on Python 3. This is more
 or less the same situation as Django 1.9, but with the ability to change
 the default behavior, and with improvements regarding Unicode
 normalization.

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

Re: [Django] #26610: Case insensitive indexes

[Django]

#26610: Case insensitive indexes
-+-
 Reporter:  shadow7412   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  index charfield  | Triage Stage:  Accepted
  textfield case insensitive |
  optimisation   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by shadow7412):

 I've done some reading on {{{citext}}} - and it would indeed do the job I
 want it to do.

 My only concern is that iexact effectively becomes implicit, which may
 surprise some developers.
 I guess the question is: would people value being able to do both
 insensitive and sensitive searches on the same field?

 The only other way I could think to do this would be creating a functional
 index, which would give the ability to have the different index kwargs as
 I had in the original report, but I'm not sure which wins from a
 performance point of view.
 And, again, if people would find having both a useful feature.

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

Re: [Django] #26610: Case insensitive indexes

[Django]

#26610: Case insensitive indexes
-+-
 Reporter:  shadow7412   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  index charfield  | Triage Stage:  Accepted
  textfield case insensitive |
  optimisation   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 `citext` would make all queries and unicity checks case-insensitive. It's
 still case-preserving so I assume it would work for you even if "case is
 important".

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

Re: [Django] #26610: Case insensitive indexes

[Django]

#26610: Case insensitive indexes
-+-
 Reporter:  shadow7412   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  index charfield  | Triage Stage:  Accepted
  textfield case insensitive |
  optimisation   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by shadow7412):

 My current backend is indeed postgres. In my specific usage - case is
 important. It's just when users are searching for models in my search box
 the filter needs to be case insensitive because... well... users are very
 sensitive about case insensitivity.

 With the {{{citext}}} idea - would programmers have control enough to have
 both a sensitive and insensitive index if required? Or would that make all
 filters implicitly case insensitive?

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

Re: [Django] #26573: Empty 'AssertionError' exception message on syntax error ({% else if %}) in templates

[Django]

#26573: Empty 'AssertionError' exception message on syntax error ({% else if 
%}) in
templates
-+-
 Reporter:  vakorol  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Template system  |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  assertionerror   | Triage Stage:  Accepted
  template elsif |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by vakorol):

 Replying to [comment:2 inondle]:

 Yes, i think this will work perfectly.

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

Re: [Django] #26592: Add support for GDAL 2.1

[Django]

#26592: Add support for GDAL 2.1
-+
 Reporter:  yellowcap|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  GIS  |  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 claudep):

 I've tested this, and I'm unfortunately still getting the test failure. It
 seems that no GDALException is raised with the empty band.

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

Re: [Django] #26592: Add support for GDAL 2.1

[Django]

#26592: Add support for GDAL 2.1
-+
 Reporter:  yellowcap|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  GIS  |  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 claudep):

 I'm fine with that approach!

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

Re: [Django] #26610: Case insensitive indexes

[Django]

#26610: Case insensitive indexes
-+-
 Reporter:  shadow7412   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  index charfield  | Triage Stage:  Accepted
  textfield case insensitive |
  optimisation   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 If we're talking about Postgres, I suggest adding a case-insensitive,
 case-preserving char/text field backed by the `citext` type to
 `django.contrib.postgres`. This should cover most use cases.

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

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

[Django]

#21523: Models DateField to_python method no longer supports mock dates.
-+-
 Reporter:  hugo@…   |Owner:  akki
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

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