Re: [Django] #24887: Remove one-arg limitation from django.db.models.aggregate

2015-06-21 Thread Django 
#24887: Remove one-arg limitation from django.db.models.aggregate
-+-
 Reporter:  akaariai |Owner:  gchp
 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:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by jarshwah):

 * needs_better_patch:  1 => 0


Comment:

 I've extended @ghcp's PR with code that handles default_alias and a
 recursive contains_aggregate. https://github.com/django/django/pull/4900

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

Re: [Django] #24983: "domain" in sites framework should clarify if it is a fully-qualified domain name

2015-06-21 Thread Django 
#24983: "domain" in sites framework should clarify if it is a fully-qualified
domain name
-+-
 Reporter:  mandm|Owner:
 Type:   |  bipsandbytes
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.8
 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 bipsandbytes):

 Pull request here: https://github.com/django/django/pull/4903

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

Re: [Django] #24985: Warn about invalid RSS characters in syndication docs

2015-06-21 Thread Django 
#24985: Warn about invalid RSS characters in syndication docs
-+-
 Reporter:  michaelgwood |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"1c90a3dccadc7d2da3704ff17ac9ff1a67743934" 1c90a3dc]:
 {{{
 #!CommitTicketReference repository=""
 revision="1c90a3dccadc7d2da3704ff17ac9ff1a67743934"
 Fixed #24985 -- Added note about possible invalid feed content

 Thanks Michael Wood for the report and Tim Graham for the 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/070.c448a2ee9ebc810a17f66c61e8643f56%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25005: DateField, DateTimeField defaults needed even when auto_now=True

2015-06-21 Thread Django 
#25005: DateField, DateTimeField defaults needed even when auto_now=True
-+-
 Reporter:  monobotsoft  |Owner:  coldmind
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  DateField,   | Triage Stage:  Accepted
  DateTimeField, TimeField   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by coldmind):

 * keywords:  DateField, DateTimeField => DateField, DateTimeField,
   TimeField
 * version:  1.8 => master


Comment:

 Opened new PR - https://github.com/django/django/pull/4902
 This will not backported to 1.8

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

Re: [Django] #25012: Migration doesn't seem to detect foreignKey type changes

2015-06-21 Thread Django 
#25012: Migration doesn't seem to detect foreignKey type changes
-+-
 Reporter:  Hedde|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Uncategorized|  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  postgres,| Triage Stage:
  migrations |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by Hedde:

Old description:

> Example:
>
> {{{
> #!div style="font-size: 80%"
> {{{#!python
> class Foo(models.Model):
> id = models.AutoField()  # Now change this to
> models.CharField(primary_key=True, max_length=...) and migrate, the
> migration doesn't complain
>
> class Bar(object):
> foo = models.ForeignKey(Foo)  # but Postgres will still say
> Bar.foo is an Integer value.
> }}}
> }}}

New description:

 Example:

 {{{
 #!div style="font-size: 80%"
 {{{#!python
 class Foo(models.Model):
 id = models.AutoField()  # Now change this to
 models.CharField(primary_key=True, max_length=...) and migrate, the
 migration doesn't complain

 class Bar(object):
 foo = models.ForeignKey(Foo)  # but Postgres will still say
 Bar.foo is an Integer value.
 }}}
 }}}

 DataError at /myapp/bar/add/
 invalid input syntax for integer: "TEST"
 LINE 1: ...d") VALUES (NULL, '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/063.4989a4972579d3a0e9ae915c4325899d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25012: Migration doesn't seem to detect foreignKey type changes

2015-06-21 Thread Django 
#25012: Migration doesn't seem to detect foreignKey type changes
-+-
 Reporter:  Hedde|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Uncategorized|  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  postgres,| Triage Stage:
  migrations |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Hedde):

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


Old description:

> Example:
>
> {{{
> #!div style="font-size: 80%"
> Code highlighting:
> {{{#!python
> class Foo(models.Model):
> id = models.AutoField()  # Now change this to
> models.CharField(primary_key=True) and migrate, the migration doesn't
> complain
>
> class Bar(object):
> foo = models.ForeignKey(Foo)  # but Postgres will still say
> Bar.foo is an Integer value.
> }}}
> }}}

New description:

 Example:

 {{{
 #!div style="font-size: 80%"
 {{{#!python
 class Foo(models.Model):
 id = models.AutoField()  # Now change this to
 models.CharField(primary_key=True, max_length=...) and migrate, the
 migration doesn't complain

 class Bar(object):
 foo = models.ForeignKey(Foo)  # but Postgres will still say
 Bar.foo is an Integer 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/063.2f0d3854aaa178b6cd330468fe38f4d0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25012: Migration doesn't seem to detect foreignKey type changes

2015-06-21 Thread Django 
#25012: Migration doesn't seem to detect foreignKey type changes
---+--
 Reporter:  Hedde  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.8
 Severity:  Normal |   Keywords:  postgres, migrations
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+--
 Example:

 {{{
 #!div style="font-size: 80%"
 Code highlighting:
 {{{#!python
 class Foo(models.Model):
 id = models.AutoField()  # Now change this to
 models.CharField(primary_key=True) and migrate, the migration doesn't
 complain

 class Bar(object):
 foo = models.ForeignKey(Foo)  # but Postgres will still say
 Bar.foo is an Integer 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/048.fb9dbc860f9c60e5e09ae7f5ee3b8e55%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24983: "domain" in sites framework should clarify if it is a fully-qualified domain name

2015-06-21 Thread Django 
#24983: "domain" in sites framework should clarify if it is a fully-qualified
domain name
-+-
 Reporter:  mandm|Owner:
 Type:   |  bipsandbytes
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.8
 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 bipsandbytes):

 Fixed in [https://github.com/bipsandbytes/django/tree/ticket_24983]

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

Re: [Django] #25006: Allow for custom Time shortcut in DateTimeShortCuts.js

2015-06-21 Thread Django 
#25006: Allow for custom Time shortcut in DateTimeShortCuts.js
-+-
 Reporter:  RamezIssac   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  1.8
 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 MarkusH):

 * stage:  Accepted => Ready for checkin


Comment:

 The "6 p.m." PR is ready-for-commit.

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

Re: [Django] #25002: Postgresql migration fails when changing a CharField to a TimeField

2015-06-21 Thread Django 
#25002: Postgresql migration fails when changing a CharField to a TimeField
-+-
 Reporter:  dirkcuys |Owner:  charettes
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  migrations   | 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 MarkusH):

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

Re: [Django] #24983: "domain" in sites framework should clarify if it is a fully-qualified domain name

2015-06-21 Thread Django 
#24983: "domain" in sites framework should clarify if it is a fully-qualified
domain name
-+-
 Reporter:  mandm|Owner:
 Type:   |  bipsandbytes
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.8
 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 bipsandbytes):

 * status:  new => assigned
 * owner:  nobody => bipsandbytes


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

Re: [Django] #25005: DateField, DateTimeField defaults needed even when auto_now=True

2015-06-21 Thread Django 
#25005: DateField, DateTimeField defaults needed even when auto_now=True
-+-
 Reporter:  monobotsoft  |Owner:  coldmind
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  DateField,   | Triage Stage:  Accepted
  DateTimeField  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by MarkusH):

 Replying to [comment:3 coldmind]:
 > When we have some model, then adding DateField or DateTimeField with
 auto_now/auto_now_add, and disable promting for default, it throws
 integrity errors for null. So seems it not works on existing objects. Is
 that normal behavior or it is a bug?

 That's expected behavior. `auto_now` and `auto_now_add` are purely handled
 in Python (`default` too, but on a different level) and thus don't
 influence the default value for the database.

 As far as I can tell, combining `auto_now`, `auto_now_add` and `default`
 is not allowed, since those three options are supposed to be mutual
 exclusive:
 
https://docs.djangoproject.com/en/1.8/ref/models/fields/#django.db.models.DateField

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

Re: [Django] #24994: Document/check that settings.SECRET_KEY should be a valid unicode string

2015-06-21 Thread Django 
#24994: Document/check that settings.SECRET_KEY should be a valid unicode string
-+-
 Reporter:  bmispelon|Owner:
 Type:   |  bipsandbytes
  Cleanup/optimization   |   Status:  assigned
Component:  Core (System |  Version:  1.8
  checks)|
 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 bipsandbytes):

 * owner:  nobody => bipsandbytes
 * status:  new => assigned


Comment:

 Would it be appropriate to check for it
 `django/core/checks/security/base.py`? There are already checks for
 `SECRET_KEY`'s length and unique characters there.

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