date:20140620

Re: [Django] #22867: Pickling models is slow in alpha versions

2014-06-20 Thread Django

#22867: Pickling models is slow in alpha versions
--+
 Reporter:  Suor  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Utilities |  Version:  master
 Severity:  Release blocker   |   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+

Comment (by CollinAnderson):

 You know, there's a chance it may be smart to keep `get_version()`
 compatible with python 2.6 a little longer in general, especially
 considering this is the first release that drops python 2.6 support. If
 it's a headache for us, it could be a headache for others too.

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

Re: [Django] #22514: Postgres index generator does not expect db_type to be None

2014-06-20 Thread Django

#22514: Postgres index generator does not expect db_type to be None
-+-
 Reporter:  vzima|Owner:  vzima
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"d107c7bd7db183d85bb3b22e0019b3be8af262d2"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d107c7bd7db183d85bb3b22e0019b3be8af262d2"
 [1.7.x] Added refs #22514 to 1.6.6 release notes.

 Backport of 1892ced10a 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/063.9a4cb9d780ced090a6cba0d4f1064b0c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22514: Postgres index generator does not expect db_type to be None

2014-06-20 Thread Django

#22514: Postgres index generator does not expect db_type to be None
-+-
 Reporter:  vzima|Owner:  vzima
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"ef3ae3d1c94ac1d4ffac1ee544e91431e65b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ef3ae3d1c94ac1d4ffac1ee544e91431e65b"
 [1.6.x] Fixed #22514 -- Prevented indexes on virtual fields [postgres].

 Backport of 78c32f1caa 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/063.34d3afba0e65ce0d684405b2fdfadb91%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] ef3ae3: [1.6.x] Fixed #22514 -- Prevented indexes on virtu...

2014-06-20 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: ef3ae3d1c94ac1d4ffac1ee544e91431e65b
  
https://github.com/django/django/commit/ef3ae3d1c94ac1d4ffac1ee544e91431e65b
  Author: Vlastimil Zíma 
  Date:   2014-06-20 (Fri, 20 Jun 2014)

  Changed paths:
M django/db/backends/postgresql_psycopg2/creation.py
M docs/releases/1.6.6.txt
M tests/indexes/models.py
M tests/indexes/tests.py

  Log Message:
  ---
  [1.6.x] Fixed #22514 -- Prevented indexes on virtual fields [postgres].

Backport of 78c32f1caa from master


-- 
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/53a4bd71ab290_7e19120fd401100ac%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] d107c7: [1.7.x] Added refs #22514 to 1.6.6 release notes.

2014-06-20 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: d107c7bd7db183d85bb3b22e0019b3be8af262d2
  
https://github.com/django/django/commit/d107c7bd7db183d85bb3b22e0019b3be8af262d2
  Author: Tim Graham 
  Date:   2014-06-20 (Fri, 20 Jun 2014)

  Changed paths:
M docs/releases/1.6.6.txt

  Log Message:
  ---
  [1.7.x] Added refs #22514 to 1.6.6 release notes.

Backport of 1892ced10a from master


-- 
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/53a4bd731400b_7ab184dd34104572%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22514: Postgres index generator does not expect db_type to be None

2014-06-20 Thread Django

#22514: Postgres index generator does not expect db_type to be None
-+-
 Reporter:  vzima|Owner:  vzima
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"1892ced10a8c0a74a93acddecdb3329fc58a017b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1892ced10a8c0a74a93acddecdb3329fc58a017b"
 Added refs #22514 to 1.6.6 release notes.
 }}}

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

[django/django] 1892ce: Added refs #22514 to 1.6.6 release notes.

2014-06-20 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1892ced10a8c0a74a93acddecdb3329fc58a017b
  
https://github.com/django/django/commit/1892ced10a8c0a74a93acddecdb3329fc58a017b
  Author: Tim Graham 
  Date:   2014-06-20 (Fri, 20 Jun 2014)

  Changed paths:
M docs/releases/1.6.6.txt

  Log Message:
  ---
  Added refs #22514 to 1.6.6 release notes.


-- 
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/53a4ba0cb79d_5a46d11d34931ca%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22782: Add i18n to sitemap

2014-06-20 Thread Django

#22782: Add i18n to sitemap
--+
 Reporter:  luanpab   |Owner:  luanpab
 Type:  New feature   |   Status:  closed
Component:  contrib.sitemaps  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  sitemap, i18n | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"3425d42bf1945a3e6b2562de6c71a614e6ab2845"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3425d42bf1945a3e6b2562de6c71a614e6ab2845"
 Fixed test from refs #22782.
 }}}

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

[django/django] 3425d4: Fixed test from refs #22782.

2014-06-20 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3425d42bf1945a3e6b2562de6c71a614e6ab2845
  
https://github.com/django/django/commit/3425d42bf1945a3e6b2562de6c71a614e6ab2845
  Author: Tim Graham 
  Date:   2014-06-20 (Fri, 20 Jun 2014)

  Changed paths:
M django/contrib/sitemaps/tests/base.py
M django/contrib/sitemaps/tests/test_http.py

  Log Message:
  ---
  Fixed test from refs #22782.


-- 
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/53a4ad5c92793_740b81bd341379bf%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] db9cb8: [1.7.x] Removed two unused translations

2014-06-20 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: db9cb83d2fec781f6479f19b63d50b44a35ae632
  
https://github.com/django/django/commit/db9cb83d2fec781f6479f19b63d50b44a35ae632
  Author: Claude Paroz 
  Date:   2014-06-20 (Fri, 20 Jun 2014)

  Changed paths:
M django/conf/locale/en/LC_MESSAGES/django.po

  Log Message:
  ---
  [1.7.x] Removed two unused translations

These strings were unmarked for translation in e692c5818.


-- 
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/53a49efe13e35_7f1eaa3d40115741%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22344: Migration from ForeignKey to FileField fails: AttributeError: 'NoneType' object has no attribute 'to'

2014-06-20 Thread Django

#22344: Migration from ForeignKey to FileField fails: AttributeError: 'NoneType'
object has no attribute 'to'
+
 Reporter:  blueyed |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  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 wlan):

 I just had the same problem but with altering an M2M field into a
 booleanfield, the workaround posted by melinath worked for me as well.

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

[django/django] 276414: Fixed #22838 -- Deprecated ModelChoiceField.cache_...

2014-06-20 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2764146586509c2c81ad14da4ac86efa3a949308
  
https://github.com/django/django/commit/2764146586509c2c81ad14da4ac86efa3a949308
  Author: Marc Tamlyn 
  Date:   2014-06-20 (Fri, 20 Jun 2014)

  Changed paths:
M django/forms/models.py
M docs/internals/deprecation.txt
M docs/releases/1.8.txt

  Log Message:
  ---
  Fixed #22838 -- Deprecated ModelChoiceField.cache_choices.

Undocumented, untested and probably not even useful feature.


-- 
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/53a48bb7e3c2f_3386c9d3c449f%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django]

2014-06-20 Thread GitHub

  Branch: refs/heads/ticket22838
  Home:   https://github.com/django/django

-- 
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/53a48b584c11_555412ebd4068691%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] e350f4: Fixed #22838 -- Deprecated ModelChoiceField.cache_...

2014-06-20 Thread GitHub

  Branch: refs/heads/ticket22838
  Home:   https://github.com/django/django
  Commit: e350f4102e8246507138f4cfdcb5770b776634a2
  
https://github.com/django/django/commit/e350f4102e8246507138f4cfdcb5770b776634a2
  Author: Marc Tamlyn 
  Date:   2014-06-20 (Fri, 20 Jun 2014)

  Changed paths:
M django/forms/models.py
M docs/internals/deprecation.txt
M docs/releases/1.8.txt

  Log Message:
  ---
  Fixed #22838 -- Deprecated ModelChoiceField.cache_choices.

Undocumented, untested and probably not even useful feature.


-- 
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/53a48b2f414ad_5cd4c57d4412858e%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22876: Related lookups allow models of a different type

2014-06-20 Thread Django

#22876: Related lookups allow models of a different type
-+-
 Reporter:  bendavis78   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by bendavis78):

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


Comment:

 Yep, the proposed patch there fixes the issue. Closing.

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

Re: [Django] #22734: Move SMTP / email settings to a dictionary

2014-06-20 Thread Django

Comment (by claudep):

I've written an alternative patch:
https://github.com/django/django/pull/2836.

The dict is now called SMTP_CONFIG. I also slightly modified the
`BaseSettings` object so as it would be possible to only partially
overwrite an existing dictionary setting. For example, defining
`SMTP_CONFIG = {'USE_TLS': True}` in custom settings would not overwrite
`SMTP_CONFIG` from global settings, but copy and update that dict, keeping
the other default values.
I'm not absolutely sure it's a good idea in general, as it might render
more difficult deleting an entry from a global setting (e.g. defining
`CACHES={'custom': ...}` would keep the `default` entry). An another idea
could be making this mechanism opt-in/opt-out by having a special key on
the dict (like `_keep_defaults`).

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

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

Re: [Django] #22876: Related lookups allow models of a different type

2014-06-20 Thread Django

#22876: Related lookups allow models of a different type
-+-
 Reporter:  bendavis78   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 Duplicate of #14334, I think.

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

Re: [Django] #22514: Postgres index generator does not expect db_type to be None

2014-06-20 Thread Django

#22514: Postgres index generator does not expect db_type to be None
-+-
 Reporter:  vzima|Owner:  vzima
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by vzima):

 Found it. It is a regression from 1.5. This is the commit which introduced
 the bug:

 
https://github.com/django/django/commit/c698c55966ed9179828857398d27bf69e64713a2

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

[django/django] 334037: [1.7.x] Added HTTP 308 status and its description.

2014-06-20 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 33403790e6beb93f653a38189ad0e216678d3f3c
  
https://github.com/django/django/commit/33403790e6beb93f653a38189ad0e216678d3f3c
  Author: Yazhong Liu 
  Date:   2014-06-20 (Fri, 20 Jun 2014)

  Changed paths:
M django/http/response.py

  Log Message:
  ---
  [1.7.x] Added HTTP 308 status and its description.

Backport of 97adfc2bf8 from master


-- 
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/53a4712c96b30_47c1489d3c47525%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 97adfc: Added HTTP 308 status and its description.

2014-06-20 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 97adfc2bf8393d1128917ea1f57f3c3a7ef8caa6
  
https://github.com/django/django/commit/97adfc2bf8393d1128917ea1f57f3c3a7ef8caa6
  Author: Yazhong Liu 
  Date:   2014-06-20 (Fri, 20 Jun 2014)

  Changed paths:
M django/http/response.py

  Log Message:
  ---
  Added HTTP 308 status and its description.


-- 
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/53a471109e2ef_4dc2da7d3411499c%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[Django] #22876: Related lookups allow models of a different type

2014-06-20 Thread Django

#22876: Related lookups allow models of a different type
--+
 Reporter:  bendavis78|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Django currently allows this:

 {{{
 #!python
 >>> pig = Pig.objects.get(pk=1)
 >>> duck = Duck.objects.get(pk=1)
 >>> ducklings = Duckling.objects.filter(mother_duck=pig)
 [, ]
 }}}

 Unfortunately this can lead to baby ducklings being adopted by pigs.

 A commit was made last year that was intended to fix this (
 changeset:7cca8d5 ), but the test doesn't seem to be written correctly. It
 should assert that the resulting queryset is ''empty'', not populated with
 `ob`:

 {{{
 #!diff
 diff --git a/tests/queries/tests.py b/tests/queries/tests.py
 index 60d1083..cb615bb 100644
 --- a/tests/queries/tests.py
 +++ b/tests/queries/tests.py
 @@ -3247,10 +3247,16 @@ class RelatedLookupTypeTests(TestCase):
  # be a good idea...
  self.assertQuerysetEqual(
  ObjectB.objects.filter(objecta=wrong_type),
 -[ob], lambda x: x)
 +[], lambda x: x)
  self.assertQuerysetEqual(
  ObjectB.objects.filter(objecta__in=[wrong_type]),
 -[ob], lambda x: x)
 +[], lambda x: x)
 }}}

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

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

Re: [Django] #22782: Add i18n to sitemap

2014-06-20 Thread Django

#22782: Add i18n to sitemap
--+
 Reporter:  luanpab   |Owner:  luanpab
 Type:  New feature   |   Status:  closed
Component:  contrib.sitemaps  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  sitemap, i18n | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"407d070329b4df81dab488db35bb068976e3be43"]:
 {{{
 #!CommitTicketReference repository=""
 revision="407d070329b4df81dab488db35bb068976e3be43"
 Fixed #22782 -- Added i18n attr to Sitemap class

 It makes possible to have your sitemap in multiple languages when
 using i18n in URLs.
 }}}

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

Re: [Django] #22514: Postgres index generator does not expect db_type to be None

2014-06-20 Thread Django

#22514: Postgres index generator does not expect db_type to be None
-+-
 Reporter:  vzima|Owner:  vzima
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"6e5a7367524d3e3abd3d0f60f2e8a41796908101"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6e5a7367524d3e3abd3d0f60f2e8a41796908101"
 [1.7.x] Fixed #22514 -- Prevented indexes on virtual fields [postgres].

 Backport of 78c32f1caa 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/063.f3f05024c02dd3b27626e21ca7e8e64a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 407d07: Fixed #22782 -- Added i18n attr to Sitemap class

2014-06-20 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 407d070329b4df81dab488db35bb068976e3be43
  
https://github.com/django/django/commit/407d070329b4df81dab488db35bb068976e3be43
  Author: Luan Pablo 
  Date:   2014-06-20 (Fri, 20 Jun 2014)

  Changed paths:
M AUTHORS
M django/contrib/sitemaps/__init__.py
M django/contrib/sitemaps/tests/base.py
M django/contrib/sitemaps/tests/test_http.py
M django/contrib/sitemaps/tests/urls/http.py
M docs/ref/contrib/sitemaps.txt
M docs/releases/1.8.txt

  Log Message:
  ---
  Fixed #22782 -- Added i18n attr to Sitemap class

It makes possible to have your sitemap in multiple languages when
using i18n in URLs.


-- 
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/53a469b94c559_7843555d341119c8%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 6e5a73: [1.7.x] Fixed #22514 -- Prevented indexes on virtu...

2014-06-20 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 6e5a7367524d3e3abd3d0f60f2e8a41796908101
  
https://github.com/django/django/commit/6e5a7367524d3e3abd3d0f60f2e8a41796908101
  Author: Vlastimil Zíma 
  Date:   2014-06-20 (Fri, 20 Jun 2014)

  Changed paths:
M django/db/backends/postgresql_psycopg2/creation.py
M tests/indexes/models.py
M tests/indexes/tests.py

  Log Message:
  ---
  [1.7.x] Fixed #22514 -- Prevented indexes on virtual fields [postgres].

Backport of 78c32f1caa from master


-- 
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/53a469b86a25c_74071433d38772fb%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22514: Postgres index generator does not expect db_type to be None

2014-06-20 Thread Django

#22514: Postgres index generator does not expect db_type to be None
-+-
 Reporter:  vzima|Owner:  vzima
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by vzima):

 Is there any chance for a backport to 1.6? That version is also affected.

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

Re: [Django] #22514: Postgres index generator does not expect db_type to be None

2014-06-20 Thread Django

#22514: Postgres index generator does not expect db_type to be None
-+-
 Reporter:  vzima|Owner:  vzima
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by timo):

 Not unless it's a regression from 1.5.

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

Re: [Django] #22756: Technical 404 could say which view was run, if any.

2014-06-20 Thread Django

#22756: Technical 404 could say which view was run, if any.
-+-
 Reporter:  Keryn Knight |Owner:  jooyous
   |   Status:  assigned
 Type:  New feature  |  Version:  master
Component:  Core (URLs)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_better_patch:  0 => 1


Comment:

 I left comments for improvement on PR. Please uncheck "Patch needs
 improvement" when you update it, thanks.

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

[django/django] 78c32f: Fixed #22514 -- Prevented indexes on virtual field...

2014-06-20 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 78c32f1caa9cb9b28be2d867aff586a2016122ed
  
https://github.com/django/django/commit/78c32f1caa9cb9b28be2d867aff586a2016122ed
  Author: Vlastimil Zíma 
  Date:   2014-06-20 (Fri, 20 Jun 2014)

  Changed paths:
M django/db/backends/postgresql_psycopg2/creation.py
M tests/indexes/models.py
M tests/indexes/tests.py

  Log Message:
  ---
  Fixed #22514 -- Prevented indexes on virtual fields [postgres].


-- 
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/53a45a55d583b_5975819d40784d8%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22514: Postgres index generator does not expect db_type to be None

2014-06-20 Thread Django

#22514: Postgres index generator does not expect db_type to be None
-+-
 Reporter:  vzima|Owner:  vzima
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"78c32f1caa9cb9b28be2d867aff586a2016122ed"]:
 {{{
 #!CommitTicketReference repository=""
 revision="78c32f1caa9cb9b28be2d867aff586a2016122ed"
 Fixed #22514 -- Prevented indexes on virtual fields [postgres].
 }}}

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

Re: [Django] #17745: Support for PostgreSQL Arrays

2014-06-20 Thread Django

#17745: Support for PostgreSQL Arrays
-+-
 Reporter:  dbrgn|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:  Design
 Keywords:   |  decision needed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by dbrgn):

 Fortunately support for Postgres arrays has been added in
 https://github.com/django/django/pull/2485. So the status could be changed
 from "wontfix" to "fixed", as a reference for people looking for this
 feature via Google.

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

Re: [Django] #17745: Support for PostgreSQL Arrays

2014-06-20 Thread Django

#17745: Support for PostgreSQL Arrays
-+-
 Reporter:  dbrgn|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Design
 Keywords:   |  decision needed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * resolution:  wontfix => fixed


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

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

Re: [Django] #10938: add inlines into fieldsets

2014-06-20 Thread Django

#10938: add inlines into fieldsets
---+-
 Reporter:  ctao   |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  duplicate
 Keywords:  inlines fieldsets  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  1
---+-
Changes (by charettes):

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


Comment:

 Please don't reopen tickets anonymously without providing an explanation.
 You may have a good reason for reopening this ticket; if so, say it!

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

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

Re: [Django] #10938: add inlines into fieldsets

2014-06-20 Thread Django

#10938: add inlines into fieldsets
---+
 Reporter:  ctao   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  inlines fieldsets  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  1
---+
Changes (by neamat@…):

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


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

Re: [Django] #22862: makemigrations --merge broken because --noinput isn't registered

2014-06-20 Thread Django

#22862: makemigrations --merge broken because --noinput isn't registered
-+--
 Reporter:  art@…|Owner:  whoshuu
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by Tim Graham ):

 In [changeset:"d9a83d597ee5aa510cf1aaa086e2fc3f1d7ee4c6"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d9a83d597ee5aa510cf1aaa086e2fc3f1d7ee4c6"
 [1.7.x] Fixed #22862 -- Added --noinput option to makemigrations.

 Thanks artortenburger for the report.

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

[django/django] 9a4683: Moved a line outside of try/except to prevent an e...

2014-06-20 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 9a46836a0c3e15021df242f3dd5a33306f7e27bc
  
https://github.com/django/django/commit/9a46836a0c3e15021df242f3dd5a33306f7e27bc
  Author: Tim Graham 
  Date:   2014-06-20 (Fri, 20 Jun 2014)

  Changed paths:
M tests/migrations/test_commands.py

  Log Message:
  ---
  Moved a line outside of try/except to prevent an error in finally.

Thanks Ian Foote.


-- 
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/53a4338f84e0e_5da8b31d34541a4%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] d9a83d: [1.7.x] Fixed #22862 -- Added --noinput option to ...

2014-06-20 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: d9a83d597ee5aa510cf1aaa086e2fc3f1d7ee4c6
  
https://github.com/django/django/commit/d9a83d597ee5aa510cf1aaa086e2fc3f1d7ee4c6
  Author: Huu Nguyen 
  Date:   2014-06-20 (Fri, 20 Jun 2014)

  Changed paths:
M django/core/management/commands/makemigrations.py
M docs/ref/django-admin.txt
M tests/migrations/test_commands.py

  Log Message:
  ---
  [1.7.x] Fixed #22862 -- Added --noinput option to makemigrations.

Thanks artortenburger for the report.

Backport of fbb684d95e from master


-- 
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/53a4338ea5a97_7a7cfc1d404615e%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22862: makemigrations --merge broken because --noinput isn't registered

2014-06-20 Thread Django

#22862: makemigrations --merge broken because --noinput isn't registered
-+--
 Reporter:  art@…|Owner:  whoshuu
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"fbb684d95ed71487fe16135321d59ddb043ee903"]:
 {{{
 #!CommitTicketReference repository=""
 revision="fbb684d95ed71487fe16135321d59ddb043ee903"
 Fixed #22862 -- Added --noinput option to makemigrations.

 Thanks artortenburger for the report.
 }}}

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

[django/django] fbb684: Fixed #22862 -- Added --noinput option to makemigr...

2014-06-20 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: fbb684d95ed71487fe16135321d59ddb043ee903
  
https://github.com/django/django/commit/fbb684d95ed71487fe16135321d59ddb043ee903
  Author: Huu Nguyen 
  Date:   2014-06-20 (Fri, 20 Jun 2014)

  Changed paths:
M django/core/management/commands/makemigrations.py
M docs/ref/django-admin.txt
M tests/migrations/test_commands.py

  Log Message:
  ---
  Fixed #22862 -- Added --noinput option to makemigrations.

Thanks artortenburger for the report.


-- 
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/53a42f431a2c5_47c1489d3c31162%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22836: Issue on the code in the documentation

2014-06-20 Thread Django

#22836: Issue on the code in the documentation
--+
 Reporter:  anonymous |Owner:  maxocub
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"0b871ec22a3397063a0150d26efc0d1e1a293108"]:
 {{{
 #!CommitTicketReference repository=""
 revision="0b871ec22a3397063a0150d26efc0d1e1a293108"
 [1.7.x] Fixed #22836 -- Linked tutorial05 to the right section of
 tutorial04.

 Backport of 608aa8d101 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.13e8a005be66635b4d7a4bdd59d89c0d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 0b871e: [1.7.x] Fixed #22836 -- Linked tutorial05 to the r...

2014-06-20 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 0b871ec22a3397063a0150d26efc0d1e1a293108
  
https://github.com/django/django/commit/0b871ec22a3397063a0150d26efc0d1e1a293108
  Author: Maxime Turcotte 
  Date:   2014-06-20 (Fri, 20 Jun 2014)

  Changed paths:
M docs/intro/tutorial04.txt
M docs/intro/tutorial05.txt

  Log Message:
  ---
  [1.7.x] Fixed #22836 -- Linked tutorial05 to the right section of tutorial04.

Backport of 608aa8d101 from master


-- 
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/53a42651d499d_73f2817d3879682%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22836: Issue on the code in the documentation

2014-06-20 Thread Django

#22836: Issue on the code in the documentation
--+
 Reporter:  anonymous |Owner:  maxocub
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"608aa8d101b03004ed2181fac82d8f3d28253bbd"]:
 {{{
 #!CommitTicketReference repository=""
 revision="608aa8d101b03004ed2181fac82d8f3d28253bbd"
 Fixed #22836 -- Linked tutorial05 to the right section of tutorial04.
 }}}

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

[django/django] 608aa8: Fixed #22836 -- Linked tutorial05 to the right sec...

2014-06-20 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 608aa8d101b03004ed2181fac82d8f3d28253bbd
  
https://github.com/django/django/commit/608aa8d101b03004ed2181fac82d8f3d28253bbd
  Author: Maxime Turcotte 
  Date:   2014-06-20 (Fri, 20 Jun 2014)

  Changed paths:
M docs/intro/tutorial04.txt
M docs/intro/tutorial05.txt

  Log Message:
  ---
  Fixed #22836 -- Linked tutorial05 to the right section of tutorial04.


-- 
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/53a426078a641_4cf3c41d3c59630%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 900589: [1.7.x] Swapped placeholders in [sql]migrate comma...

2014-06-20 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 90058942338528a9e6b0995c8cd0f357ca0ed900
  
https://github.com/django/django/commit/90058942338528a9e6b0995c8cd0f357ca0ed900
  Author: Claude Paroz 
  Date:   2014-06-20 (Fri, 20 Jun 2014)

  Changed paths:
M django/core/management/commands/migrate.py
M django/core/management/commands/sqlmigrate.py

  Log Message:
  ---
  [1.7.x] Swapped placeholders in [sql]migrate command error

Backport of b67e9ed8c9 from master.


-- 
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/53a42154c30e1_4e09119dd44481df%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] b67e9e: Swapped placeholders in [sql]migrate command error

2014-06-20 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b67e9ed8c991830acdc12f2b97f92769719556a7
  
https://github.com/django/django/commit/b67e9ed8c991830acdc12f2b97f92769719556a7
  Author: Claude Paroz 
  Date:   2014-06-20 (Fri, 20 Jun 2014)

  Changed paths:
M django/core/management/commands/migrate.py
M django/core/management/commands/sqlmigrate.py

  Log Message:
  ---
  Swapped placeholders in [sql]migrate command error


-- 
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/53a420b6af8fd_7a20141fd382602f%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21113: django_admin_log table stores messages in different languages depending on which language was active while editing.

2014-06-20 Thread Django

#21113: django_admin_log table stores messages in different languages depending 
on
which language was active while editing.
-+
 Reporter:  dimyur27@…   |Owner:  jooyous
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin logs i18n  | 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):

 Fixing existing history might be impossible to achieve. I wouldn't set
 that as a goal for this ticket.

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

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

Re: [Django] #22857: Django 1.7 runserver auto-reload : setting behaviour by extensions

2014-06-20 Thread Django

#22857: Django 1.7 runserver auto-reload : setting behaviour by extensions
-+-
 Reporter:  artscoop |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:
  commands)  |  1.7-beta-2
 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 aaugustin):

 * severity:  Release blocker => Normal


Comment:

 I agree that this change of behaviour is annoying for rosetta but I don't
 think we should delay 1.7 for this edge case.

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

Re: [Django] #22872: Backwards incompatible change: Can't proxy User model: RuntimeError: App registry isn't ready yet.

2014-06-20 Thread Django

#22872: Backwards incompatible change: Can't proxy User model: RuntimeError: App
registry isn't ready yet.
---+--
Reporter: jdufresne |Owner: nobody
Type: Bug| Status: new
Component: Uncategorized | Version: 1.7-beta-2
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 aaugustin):

Indeed, my suggestion doesn't work.

Replying to [comment:2 jdufresne]:
> Or, I guess, implement another `get_user_model()` style function and
sprinkle it all over.

I'm not sure that helps, because you still need to resolve the model at
compile time.

The only thing that works at compile time currently is
settings.AUTH_USER_MODEL. It can be used a an FK target because Django
specifically delays resolution of FKs until the target model is imported
(search for `class_prepared` in the code).

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

Re: [Django] #21113: django_admin_log table stores messages in different languages depending on which language was active while editing.

2014-06-20 Thread Django

#21113: django_admin_log table stores messages in different languages depending 
on
which language was active while editing.
-+
 Reporter:  dimyur27@…   |Owner:  jooyous
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin logs i18n  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by jooyous):

 So at this point I understand how to change this so all subsequent log
 entries behave correctly. But currently the translated strings are being
 saved away as part of the object, and I think (?) this means we've lost
 the information of the starting language, so the only way I can think of
 fixing *existing* histories is by writing a script and having the user run
 it, specifying their relevant languages?

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

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

Re: [Django] #22857: Django 1.7 runserver auto-reload : setting behaviour by extensions

2014-06-20 Thread Django

#22857: Django 1.7 runserver auto-reload : setting behaviour by extensions
-+-
 Reporter:  artscoop |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:
  commands)  |  1.7-beta-2
 Severity:  Release blocker  |   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 andrewgodwin):

 If we can reset the translation cache then let's try that, but I'm really
 pushed to define this as a release blocker (it is not breaking any part of
 Django directly, and the behaviour it produces can be worked around with
 ``--noreload`` if you need to file translations), so if we get down to the
 release time and this is what's left... it might not make it.

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

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

Re: [Django] #22874: Swappable dependency breaks if swappable model not in first migration of its app

2014-06-20 Thread Django

#22874: Swappable dependency breaks if swappable model not in first migration of
its app
-+
 Reporter:  melinath |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by Andrew Godwin ):

 In [changeset:"44b00af9bc3e6e8a561103aa5ca564995ca3c594"]:
 {{{
 #!CommitTicketReference repository=""
 revision="44b00af9bc3e6e8a561103aa5ca564995ca3c594"
 [1.7.x] Fixed #22874: Document that AUTH_USER_MODEL must be in first
 migration
 }}}

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

Re: [Django] #22874: Swappable dependency breaks if swappable model not in first migration of its app

2014-06-20 Thread Django

#22874: Swappable dependency breaks if swappable model not in first migration of
its app
-+
 Reporter:  melinath |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Andrew Godwin ):

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


Comment:

 In [changeset:"08221d1b5c1eec782c792818a2aa4a74ca7f1fcb"]:
 {{{
 #!CommitTicketReference repository=""
 revision="08221d1b5c1eec782c792818a2aa4a74ca7f1fcb"
 Fixed #22874: Document that AUTH_USER_MODEL must be in first migration
 }}}

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

[django/django] 44b00a: [1.7.x] Fixed #22874: Document that AUTH_USER_MODE...

2014-06-20 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 44b00af9bc3e6e8a561103aa5ca564995ca3c594
  
https://github.com/django/django/commit/44b00af9bc3e6e8a561103aa5ca564995ca3c594
  Author: Andrew Godwin 
  Date:   2014-06-19 (Thu, 19 Jun 2014)

  Changed paths:
M docs/ref/settings.txt
M docs/topics/auth/customizing.txt

  Log Message:
  ---
  [1.7.x] Fixed #22874: Document that AUTH_USER_MODEL must be in first migration


-- 
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/53a3d9646ac2b_486ee49d3c1243f%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 08221d: Fixed #22874: Document that AUTH_USER_MODEL must b...

2014-06-20 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 08221d1b5c1eec782c792818a2aa4a74ca7f1fcb
  
https://github.com/django/django/commit/08221d1b5c1eec782c792818a2aa4a74ca7f1fcb
  Author: Andrew Godwin 
  Date:   2014-06-19 (Thu, 19 Jun 2014)

  Changed paths:
M docs/ref/settings.txt
M docs/topics/auth/customizing.txt

  Log Message:
  ---
  Fixed #22874: Document that AUTH_USER_MODEL must be in first migration


-- 
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/53a3d95a60d4f_5469e01d3451826%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22874: Swappable dependency breaks if swappable model not in first migration of its app

2014-06-20 Thread Django

#22874: Swappable dependency breaks if swappable model not in first migration of
its app
-+
 Reporter:  melinath |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   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 andrewgodwin):

 One of the caveats we had to do to be able to support swappable models was
 that they MUST be in the first migration of their respective app (as
 you've seen, otherwise dependency problems occur). There's literally no
 way to fix this, as it's logically impossible to construct a dependency
 graph otherwise with our model.

 I'll add documentation highlighting this next to the existing warning
 about dependencies from unmigrated apps.

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

[django/django] 9f4852: Fixed #22863: Improve clarity of makemigrations fo...

2014-06-20 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 9f4852f649fad459a451995c4a17a7d8db5972c9
  
https://github.com/django/django/commit/9f4852f649fad459a451995c4a17a7d8db5972c9
  Author: Andrew Godwin 
  Date:   2014-06-19 (Thu, 19 Jun 2014)

  Changed paths:
M django/core/management/commands/migrate.py
M docs/topics/migrations.txt

  Log Message:
  ---
  Fixed #22863: Improve clarity of makemigrations for non-db params


-- 
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/53a3d7cca33b_5f91132dd446799d%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] bfe5f7: [1.7.x] Fixed #22863: Improve clarity of makemigra...

2014-06-20 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: bfe5f72c7ee4ecec374af9a52c320c019abfc338
  
https://github.com/django/django/commit/bfe5f72c7ee4ecec374af9a52c320c019abfc338
  Author: Andrew Godwin 
  Date:   2014-06-19 (Thu, 19 Jun 2014)

  Changed paths:
M django/core/management/commands/migrate.py
M docs/topics/migrations.txt

  Log Message:
  ---
  [1.7.x] Fixed #22863: Improve clarity of makemigrations for non-db params


-- 
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/53a3d7d84a8a0_5f4e1007d40138782%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22863: Document that changing model options unrelated to the database will create migrations

2014-06-20 Thread Django

#22863: Document that changing model options unrelated to the database will 
create
migrations
-+-
 Reporter:  davidray |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Migrations   |  1.7-beta-2
 Severity:  Release blocker  |   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 andrewgodwin):

 That output is the same no matter what options you change - it means:

  - No migrations are needed to run
  - You've got changes, so you need to run makemigrations

 We added this as a hint to people who were just running migrate and
 getting confused. I'll update the message to be less confusing and add a
 docs paragraph about makemigrations and non-database-affecting parameters.

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

Re: [Django] #22863: Document that changing model options unrelated to the database will create migrations

2014-06-20 Thread Django

#22863: Document that changing model options unrelated to the database will 
create
migrations
-+-
 Reporter:  davidray |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Migrations   |  1.7-beta-2
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Andrew Godwin ):

 In [changeset:"bfe5f72c7ee4ecec374af9a52c320c019abfc338"]:
 {{{
 #!CommitTicketReference repository=""
 revision="bfe5f72c7ee4ecec374af9a52c320c019abfc338"
 [1.7.x] Fixed #22863: Improve clarity of makemigrations for non-db params
 }}}

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

Re: [Django] #22863: Document that changing model options unrelated to the database will create migrations

2014-06-20 Thread Django

#22863: Document that changing model options unrelated to the database will 
create
migrations
-+-
 Reporter:  davidray |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Migrations   |  1.7-beta-2
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Andrew Godwin ):

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


Comment:

 In [changeset:"9f4852f649fad459a451995c4a17a7d8db5972c9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9f4852f649fad459a451995c4a17a7d8db5972c9"
 Fixed #22863: Improve clarity of makemigrations for non-db params
 }}}

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

60 matches

Mail list logo