Re: [Django] #16455: Postgis 2.0 Compatibility

[Django]

#16455: Postgis 2.0 Compatibility
-+-
 Reporter:  ckarrie  |Owner:  jbronn
 Type:  New feature  |   Status:  closed
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  postgis 2.0  | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by rizumu):

 @fcurella ok thanks, I've done that here:
 https://code.djangoproject.com/ticket/21713#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/065.fb528ebf2bfb00122cd417346a327e63%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21713: extension "postgis" already exists' during syncdb

[Django]

#21713: extension "postgis" already exists' during syncdb
+
 Reporter:  rizumu  |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  GIS |Version:  1.6
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  1
Easy pickings:  1   |  UI/UX:  0
+
 I am hitting an error on Django 1.7 master, PostgreSQL 9.3.2, postgis
 2.1.1. 'django.db.utils.ProgrammingError: extension "postgis" already
 exists' when running tests.


 Changing "CREATE EXTENSION postgis" to "CREATE EXTENSION IF NOT EXISTS
 postgis" works around the issue.

 A pull request is here:
 https://github.com/django/django/pull/2130

-- 
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/049.910aaeaa93ae654fe73146733c2c12b3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21699: Provide a way to define a model without being registered into AppConfig

[Django]

#21699: Provide a way to define a model without being registered into AppConfig
--+-
 Reporter:  mitar |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  app-loading   | Triage Stage:  Someday/Maybe
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-

Comment (by mitar):

 > So we're talking of hacking the internals heavily here ;-)

 Yes. :-) But from such hacking new use cases emerge. :-)

 > Currently ModelBase.new always returns a class registered in the app
 registry.

 Yes. This is why we register, and then try to unregister. So maybe then
 #21698 is a better approach. The issue there is that you still send a
 signal when a new model is registered, despite then removing it almost
 immediately. Maybe an alternative would be that API could provide a way to
 register a model without sending a signal, and then to unregister. But
 this is just a hack for current approach with `get_registered_model`.

-- 
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.711100c1341c52b1986856d915f033ab%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21649: Add session signing based on the value of the user's password

[Django]

#21649: Add session signing based on the value of the user's password
--+
 Reporter:  timo  |Owner:  timo
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  Version:  master
 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
--+

Comment (by PaulM):

 I think in the past we've done work to preserve sessions across version
 upgrades. This of course has the downside of making the full benefit of
 the patch take an extra version to manifest. I personally don't mind
 sessions going away during upgrade, but I believe that some users of
 Django may not be comfortable with that.

 I'd defer to Jacob or Luke or another conservative core dev. The upgrade
 code path shouldn't be too complex in this 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/062.1f811bc93c716e31dd32d1b59475c477%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] a5e2a0: Added release notes for today's app-loading improv...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a5e2a0e569809b7ea0c379e12d637ef0e5c9c8b9
  
https://github.com/django/django/commit/a5e2a0e569809b7ea0c379e12d637ef0e5c9c8b9
  Author: Aymeric Augustin 
  Date:   2013-12-30 (Mon, 30 Dec 2013)

  Changed paths:
M docs/releases/1.7.txt

  Log Message:
  ---
  Added release notes for today's app-loading improvements.


-- 
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/52c1fd80c1a58_76e98a1d581123f8%40hookshot-fe6-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21689: Remove the only_with_models_module argument of get_app_config[s]

[Django]

#21689: Remove the only_with_models_module argument of get_app_config[s]
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  app-loading   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"bfcc686d22df10c268752635947dd242317ba156"]:
 {{{
 #!CommitTicketReference repository=""
 revision="bfcc686d22df10c268752635947dd242317ba156"
 Removed the only_with_models_module argument of get_model[s].

 Now that the refactorings are complete, it isn't particularly useful any
 more, nor very well named. Let's keep the API as simple as possible.

 Fixed #21689.
 }}}

-- 
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.46d6e745424308d6c2b2647a93bd752b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] bfcc68: Removed the only_with_models_module argument of ge...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: bfcc686d22df10c268752635947dd242317ba156
  
https://github.com/django/django/commit/bfcc686d22df10c268752635947dd242317ba156
  Author: Aymeric Augustin 
  Date:   2013-12-30 (Mon, 30 Dec 2013)

  Changed paths:
M django/apps/registry.py
M django/contrib/contenttypes/management.py
M django/core/management/base.py
M django/core/management/commands/dumpdata.py
M django/core/management/commands/flush.py
M django/core/management/commands/migrate.py
M django/core/management/sql.py
M django/db/backends/__init__.py
M django/db/migrations/loader.py
M docs/ref/applications.txt
M tests/apps/tests.py

  Log Message:
  ---
  Removed the only_with_models_module argument of get_model[s].

Now that the refactorings are complete, it isn't particularly useful any
more, nor very well named. Let's keep the API as simple as possible.

Fixed #21689.


-- 
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/52c1fad9c5b2a_a9a86fd584962b%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] ec020c: Fixed a broken link in docs/intro/tutorial01.txt.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ec020cab7ef4b1943a8fe9a4d6872f7e874db707
  
https://github.com/django/django/commit/ec020cab7ef4b1943a8fe9a4d6872f7e874db707
  Author: Tim Graham 
  Date:   2013-12-30 (Mon, 30 Dec 2013)

  Changed paths:
M docs/intro/tutorial01.txt

  Log Message:
  ---
  Fixed a broken link in docs/intro/tutorial01.txt.


-- 
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/52c1facea17f6_5a8d1333d4817963%40hookshot-fe5-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] f20da2: [1.5.x] Fixed #21708 -- Added some headings to sep...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: f20da282972628daed1d792104500600d233d897
  
https://github.com/django/django/commit/f20da282972628daed1d792104500600d233d897
  Author: Tim Graham 
  Date:   2013-12-30 (Mon, 30 Dec 2013)

  Changed paths:
M docs/topics/http/urls.txt

  Log Message:
  ---
  [1.5.x] Fixed #21708 -- Added some headings to separate unrelated topics.

Thanks ashley at ashleymills.com for the suggestion.

Backport of 270f7e2167 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/52c1fa712dfa4_69c41175d58114361%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 5dfd82: Introduced as_bytes for SafeMIMEText (and other Sa...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 5dfd824d38ec7d1f695494e46d603e89cae68661
  
https://github.com/django/django/commit/5dfd824d38ec7d1f695494e46d603e89cae68661
  Author: Florian Apolloner 
  Date:   2013-12-28 (Sat, 28 Dec 2013)

  Changed paths:
M django/core/mail/backends/smtp.py
M django/core/mail/message.py
M tests/mail/tests.py

  Log Message:
  ---
  Introduced as_bytes for SafeMIMEText (and other SafeMIME-classes).

This is to provide a consistent interface (namely bytes) for the smtp
backend which after all sends bytes over the wire; encoding with as_string
yields different results since mails as unicode are not really specified.

as_string stays for backwardscompatibilty mostly and some debug outputs.
But keep in mind that the output doesn't match as_bytes!


  Commit: c988745cca1225496bfd36910dc3cec5065d8cc4
  
https://github.com/django/django/commit/c988745cca1225496bfd36910dc3cec5065d8cc4
  Author: Florian Apolloner 
  Date:   2013-12-30 (Mon, 30 Dec 2013)

  Changed paths:
M django/core/mail/backends/console.py
M django/core/mail/backends/filebased.py
M tests/mail/tests.py

  Log Message:
  ---
  Changed console and filebackend to use msg.as_bytes to output the data as it 
would get send via smtp.


  Commit: bfe9052831c6d7ad7501b71c884525b3b471eebc
  
https://github.com/django/django/commit/bfe9052831c6d7ad7501b71c884525b3b471eebc
  Author: Florian Apolloner 
  Date:   2013-12-30 (Mon, 30 Dec 2013)

  Changed paths:
M django/core/mail/backends/console.py

  Log Message:
  ---
  Decode mails using the message encoding.


  Commit: df075c74896b63ff39c250bb52a1f168265dfeee
  
https://github.com/django/django/commit/df075c74896b63ff39c250bb52a1f168265dfeee
  Author: Florian Apolloner 
  Date:   2013-12-30 (Mon, 30 Dec 2013)

  Changed paths:
M django/core/mail/backends/console.py
M django/core/mail/backends/filebased.py
M django/core/mail/backends/smtp.py
M django/core/mail/message.py
M tests/mail/tests.py

  Log Message:
  ---
  Merge pull request #2126 from apollo13/email_bytes

Many thanks to @bitdancer and @aaugustin for answering my stupid questions 
about (mail)encodings and pointing me in the right direction.


Compare: https://github.com/django/django/compare/270f7e21676f...df075c74896b

-- 
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/52c1faaa87f15_5aa6ea9d54487f0%40hookshot-fe5-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21708: Documentation makes two distinct points but implies conjunction

[Django]

#21708: Documentation makes two distinct points but implies conjunction
---+
 Reporter:  ashley@…   |  Owner:  nobody
 Type:  Uncategorized  | Status:  closed
Component:  Documentation  |Version:  1.6
 Severity:  Normal | Resolution:  fixed
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  1
UI/UX:  0  |
---+

Comment (by Tim Graham ):

 In [changeset:"f20da282972628daed1d792104500600d233d897"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f20da282972628daed1d792104500600d233d897"
 [1.5.x] Fixed #21708 -- Added some headings to separate unrelated topics.

 Thanks ashley at ashleymills.com for the suggestion.

 Backport of 270f7e2167 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/080.6ba2716d760cc0b1343143c55c3f00ab%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21708: Documentation makes two distinct points but implies conjunction

[Django]

#21708: Documentation makes two distinct points but implies conjunction
---+
 Reporter:  ashley@…   |  Owner:  nobody
 Type:  Uncategorized  | Status:  closed
Component:  Documentation  |Version:  1.6
 Severity:  Normal | Resolution:  fixed
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  1
UI/UX:  0  |
---+

Comment (by Tim Graham ):

 In [changeset:"2d554d29f2f3b495768e4100e9b48c1bb6242799"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2d554d29f2f3b495768e4100e9b48c1bb6242799"
 [1.6.x] Fixed #21708 -- Added some headings to separate unrelated topics.

 Thanks ashley at ashleymills.com for the suggestion.

 Backport of 270f7e2167 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/080.1cc33bb2f37c3fc3e3a80d0d9a835d7f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21708: Documentation makes two distinct points but implies conjunction

[Django]

#21708: Documentation makes two distinct points but implies conjunction
---+
 Reporter:  ashley@…   |  Owner:  nobody
 Type:  Uncategorized  | Status:  closed
Component:  Documentation  |Version:  1.6
 Severity:  Normal | Resolution:  fixed
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  1
UI/UX:  0  |
---+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"270f7e21676f043464e9a3e252fec0a63e3c0b2a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="270f7e21676f043464e9a3e252fec0a63e3c0b2a"
 Fixed #21708 -- Added some headings to separate unrelated topics.

 Thanks ashley at ashleymills.com for the suggestion.
 }}}

-- 
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/080.b581974297772db010e1b9d64b230947%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 270f7e: Fixed #21708 -- Added some headings to separate un...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 270f7e21676f043464e9a3e252fec0a63e3c0b2a
  
https://github.com/django/django/commit/270f7e21676f043464e9a3e252fec0a63e3c0b2a
  Author: Tim Graham 
  Date:   2013-12-30 (Mon, 30 Dec 2013)

  Changed paths:
M docs/topics/http/urls.txt

  Log Message:
  ---
  Fixed #21708 -- Added some headings to separate unrelated topics.

Thanks ashley at ashleymills.com for the suggestion.


-- 
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/52c1fa6090c25_6b008e1d5410853e%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 2d554d: [1.6.x] Fixed #21708 -- Added some headings to sep...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 2d554d29f2f3b495768e4100e9b48c1bb6242799
  
https://github.com/django/django/commit/2d554d29f2f3b495768e4100e9b48c1bb6242799
  Author: Tim Graham 
  Date:   2013-12-30 (Mon, 30 Dec 2013)

  Changed paths:
M docs/topics/http/urls.txt

  Log Message:
  ---
  [1.6.x] Fixed #21708 -- Added some headings to separate unrelated topics.

Thanks ashley at ashleymills.com for the suggestion.

Backport of 270f7e2167 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/52c1fa75f262_6d11a01d4c109329%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21710: API reference for default User implementation misses get_short_name

[Django]

#21710: API reference for default User implementation misses get_short_name
-+
 Reporter:  Keryn Knight   |  Owner:  nobody
 Type:  Uncategorized| Status:  closed
Component:  Documentation|Version:  master
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |   Triage Stage:  Unreviewed
Has patch:  0|  Easy pickings:  1
UI/UX:  0|
-+

Comment (by Tim Graham ):

 In [changeset:"3cf9ba5fa31083b17c7363e512d365bac0f57c24"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3cf9ba5fa31083b17c7363e512d365bac0f57c24"
 [1.5.x] Fixed #21710 -- Documented User.get_short_name()

 Thanks Keryn Knight for the report.

 Backport of 0150830687 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/095.26e10f17008f03afa18600d354deffdf%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 3cf9ba: [1.5.x] Fixed #21710 -- Documented User.get_short_...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 3cf9ba5fa31083b17c7363e512d365bac0f57c24
  
https://github.com/django/django/commit/3cf9ba5fa31083b17c7363e512d365bac0f57c24
  Author: Tim Graham 
  Date:   2013-12-30 (Mon, 30 Dec 2013)

  Changed paths:
M docs/ref/contrib/auth.txt

  Log Message:
  ---
  [1.5.x] Fixed #21710 -- Documented User.get_short_name()

Thanks Keryn Knight for the report.

Backport of 0150830687 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/52c1f7ecedee5_c1d901d48132371%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21710: API reference for default User implementation misses get_short_name

[Django]

#21710: API reference for default User implementation misses get_short_name
-+
 Reporter:  Keryn Knight   |  Owner:  nobody
 Type:  Uncategorized| Status:  closed
Component:  Documentation|Version:  master
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |   Triage Stage:  Unreviewed
Has patch:  0|  Easy pickings:  1
UI/UX:  0|
-+

Comment (by Tim Graham ):

 In [changeset:"51d6a7d53e956ee0b32bb45e33d09b07d796429e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="51d6a7d53e956ee0b32bb45e33d09b07d796429e"
 [1.6.x] Fixed #21710 -- Documented User.get_short_name()

 Thanks Keryn Knight for the report.

 Backport of 0150830687 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/095.101476e1758187ed393dad4e735bd6ae%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 51d6a7: [1.6.x] Fixed #21710 -- Documented User.get_short_...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 51d6a7d53e956ee0b32bb45e33d09b07d796429e
  
https://github.com/django/django/commit/51d6a7d53e956ee0b32bb45e33d09b07d796429e
  Author: Tim Graham 
  Date:   2013-12-30 (Mon, 30 Dec 2013)

  Changed paths:
M docs/ref/contrib/auth.txt

  Log Message:
  ---
  [1.6.x] Fixed #21710 -- Documented User.get_short_name()

Thanks Keryn Knight for the report.

Backport of 0150830687 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/52c1f7bfb179e_5b129cfd4c763d7%40hookshot-fe5-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 015083: Fixed #21710 -- Documented User.get_short_name()

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 0150830687188681ba7e4ae9b6da1a832a6d5141
  
https://github.com/django/django/commit/0150830687188681ba7e4ae9b6da1a832a6d5141
  Author: Tim Graham 
  Date:   2013-12-30 (Mon, 30 Dec 2013)

  Changed paths:
M docs/ref/contrib/auth.txt

  Log Message:
  ---
  Fixed #21710 -- Documented User.get_short_name()

Thanks Keryn Knight 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/52c1f6e3adf4f_cb4727d4c670d0%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21710: API reference for default User implementation misses get_short_name

[Django]

#21710: API reference for default User implementation misses get_short_name
-+
 Reporter:  Keryn Knight   |  Owner:  nobody
 Type:  Uncategorized| Status:  closed
Component:  Documentation|Version:  master
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |   Triage Stage:  Unreviewed
Has patch:  0|  Easy pickings:  1
UI/UX:  0|
-+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"0150830687188681ba7e4ae9b6da1a832a6d5141"]:
 {{{
 #!CommitTicketReference repository=""
 revision="0150830687188681ba7e4ae9b6da1a832a6d5141"
 Fixed #21710 -- Documented User.get_short_name()

 Thanks Keryn Knight 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/095.f1a1a1dd75e829c9892a373cd7949d5f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21712: Move admin.autodiscover() to AppConfig.setup()

[Django]

#21712: Move admin.autodiscover() to AppConfig.setup()
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  app-loading   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by aaugustin):

 It may be more appropriate to put it in the admin AppConfig (once there's
 one, #21675) and to document how do disable it (via subclassing).

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

Re: [Django] #21712: Move admin.autodiscover() to AppConfig.setup()

[Django]

#21712: Move admin.autodiscover() to AppConfig.setup()
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  app-loading   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Old description:

> It doesn't belong to urls.py!
>
> This probably requires shipping an app.py with an AppConfig in the
> default project template and adding lots of documentation, including in
> the tutorial.

New description:

 It doesn't belong to urls.py!

 This probably requires shipping an apps.py with an AppConfig in the
 default project template and adding lots of documentation, including in
 the tutorial.

--

Comment (by aaugustin):

 In fact, we don't have a good API for project-level startup code. Many
 projects have a "project app" for projectwide templates, staticfiles, etc.
 but the tutorial doesn't. This requires a bit more thought.

-- 
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.7887aa2a9c05713d0575c31726bb02f5%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21712: Move admin.autodiscover() to AppConfig.setup()

[Django]

#21712: Move admin.autodiscover() to AppConfig.setup()
-+-
   Reporter:  aaugustin  |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |Version:  master
  Component: |   Keywords:  app-loading
  contrib.admin  |  Has patch:  0
   Severity:  Normal |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 It doesn't belong to urls.py!

 This probably requires shipping an app.py with an AppConfig in the default
 project template and adding lots of documentation, including in the
 tutorial.

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

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

Re: [Django] #21681: Simplify Apps.populate_models

[Django]

#21681: Simplify Apps.populate_models
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:  fixed
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  app-loading  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 This issue is fixed by the two commits above. The part about `ModelBase`
 was moved to #21711.

-- 
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.81cf54bdf0a2465ce478622bca183886%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 1c242a: Merged Apps.populate_apps() and populate_models().

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1c242a297b5b1857d76cab9b24f9f1d3b7f5240d
  
https://github.com/django/django/commit/1c242a297b5b1857d76cab9b24f9f1d3b7f5240d
  Author: Aymeric Augustin 
  Date:   2013-12-30 (Mon, 30 Dec 2013)

  Changed paths:
M django/__init__.py
M django/apps/base.py
M django/apps/registry.py
M django/core/management/__init__.py

  Log Message:
  ---
  Merged Apps.populate_apps() and populate_models().

After the recent series of refactorings, there's no reason to keep
two distinct methods.

Refs #21681.


-- 
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/52c1f2b18979b_6d80135bd48331c2%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21681: Simplify Apps.populate_models

[Django]

#21681: Simplify Apps.populate_models
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  app-loading  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"1c242a297b5b1857d76cab9b24f9f1d3b7f5240d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1c242a297b5b1857d76cab9b24f9f1d3b7f5240d"
 Merged Apps.populate_apps() and populate_models().

 After the recent series of refactorings, there's no reason to keep
 two distinct methods.

 Refs #21681.
 }}}

-- 
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.9980a65d3298e2255b3fd6f2f425e419%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21711: Check for duplicate model names

[Django]

#21711: Check for duplicate model names
+-
   Reporter:  aaugustin |  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  Core (Other)  |Version:  master
   Severity:  Normal|   Keywords:  app-loading
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+-
 (Extracted from #21681.)

 `ModelBase.__new__` has an interesting behavior: it checks for a model
 class with the target name in the app registry and return it instead of
 creating a new class if found.

 {{{
 # myapp/models.py

 from django.db import models

 class MyModel(models.Model):
 pass

 first_model_class = MyModel  # save a reference

 class MyModel(models.Model):
 pass

 second_model_class = MyModel  # save a reference

 if second_model_class is first_model_class:
 raise RuntimeError("WTF")
 }}}

 It would be better to raise an error in that case than silently return the
 first model. See also #21679 which is essentially the same issue for
 applications.

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

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

[django/django] 966de8: Removed postponing in Apps.populate_models.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 966de8497373dc47756105516b4b839734ed316e
  
https://github.com/django/django/commit/966de8497373dc47756105516b4b839734ed316e
  Author: Aymeric Augustin 
  Date:   2013-12-30 (Mon, 30 Dec 2013)

  Changed paths:
M django/apps/registry.py

  Log Message:
  ---
  Removed postponing in Apps.populate_models.

To the best of my understanding, since populate_models() is now called
as soon as Django starts, it cannot be called while a models module is
being imported, and that removes the need for postponing.

(If hell breaks loose we'll revert this commit.)

Refs #21681.


-- 
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/52c1ee1554894_273bf95d5887649%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21681: Simplify Apps.populate_models

[Django]

#21681: Simplify Apps.populate_models
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  app-loading  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"966de8497373dc47756105516b4b839734ed316e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="966de8497373dc47756105516b4b839734ed316e"
 Removed postponing in Apps.populate_models.

 To the best of my understanding, since populate_models() is now called
 as soon as Django starts, it cannot be called while a models module is
 being imported, and that removes the need for postponing.

 (If hell breaks loose we'll revert this commit.)

 Refs #21681.
 }}}

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

Re: [Django] #21676: Provide a way to run code when Django starts

[Django]

#21676: Provide a way to run code when Django starts
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  app-loading  | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 Fixed in e187caa3afd7d292353fb32be1647da2cf0968da.

-- 
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.8ef73202e8c1dad84ecdaa76bb8ce671%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #1796: [patch] "Cannot resolve keyword ___ into field" error when working with ManyToMany relation

[Django]

#1796: [patch] "Cannot resolve keyword ___ into field" error when working with
ManyToMany relation
-+-
   Reporter:  anonymous  |Owner:
   Type:  defect |  mtredinnick
  Component:  Database layer |   Status:  closed
  (models, ORM)  |  Version:  master
   Severity:  critical   |   Resolution:  fixed
   Keywords: | Triage Stage:  Accepted
  Has patch:  0  |  Needs documentation:  0
Needs tests:  0  |  Patch needs improvement:  0
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"0d2c8ff2be733c7cc83a023bbafe0258faa5603c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="0d2c8ff2be733c7cc83a023bbafe0258faa5603c"
 Populated the app registry earlier at startup.

 Refs #1796, #21676.
 }}}

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

Re: [Django] #21676: Provide a way to run code when Django starts

[Django]

#21676: Provide a way to run code when Django starts
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  app-loading  | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"0d2c8ff2be733c7cc83a023bbafe0258faa5603c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="0d2c8ff2be733c7cc83a023bbafe0258faa5603c"
 Populated the app registry earlier at startup.

 Refs #1796, #21676.
 }}}

-- 
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.2744c86f44f9eb06d72a4671e44f7883%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 0d2c8f: Populated the app registry earlier at startup.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 0d2c8ff2be733c7cc83a023bbafe0258faa5603c
  
https://github.com/django/django/commit/0d2c8ff2be733c7cc83a023bbafe0258faa5603c
  Author: Aymeric Augustin 
  Date:   2013-12-30 (Mon, 30 Dec 2013)

  Changed paths:
M django/core/management/__init__.py
M django/core/management/base.py
M django/core/management/commands/shell.py
M django/core/wsgi.py

  Log Message:
  ---
  Populated the app registry earlier at startup.

Refs #1796, #21676.


  Commit: e187caa3afd7d292353fb32be1647da2cf0968da
  
https://github.com/django/django/commit/e187caa3afd7d292353fb32be1647da2cf0968da
  Author: Aymeric Augustin 
  Date:   2013-12-30 (Mon, 30 Dec 2013)

  Changed paths:
M django/apps/base.py
M django/apps/registry.py
M docs/ref/applications.txt

  Log Message:
  ---
  Added AppConfig.setup() to run setup code.


  Commit: c31d7c48139260ccb72deda9b0033db0db86e84a
  
https://github.com/django/django/commit/c31d7c48139260ccb72deda9b0033db0db86e84a
  Author: Aymeric Augustin 
  Date:   2013-12-30 (Mon, 30 Dec 2013)

  Changed paths:
M docs/ref/signals.txt
M docs/topics/signals.txt

  Log Message:
  ---
  Updated advice on connecting signals at startup.


  Commit: 7ed20e015335076fc98ad805eaf241f8a0d872d5
  
https://github.com/django/django/commit/7ed20e015335076fc98ad805eaf241f8a0d872d5
  Author: Aymeric Augustin 
  Date:   2013-12-30 (Mon, 30 Dec 2013)

  Changed paths:
M django/apps/registry.py
M django/db/migrations/state.py
M tests/apps/models.py
M tests/apps/tests.py
M tests/migrations/test_state.py

  Log Message:
  ---
  Populated Apps instances immediately by default.


  Commit: 80d74097b4bd7186ad99b6d41d0ed90347a39b21
  
https://github.com/django/django/commit/80d74097b4bd7186ad99b6d41d0ed90347a39b21
  Author: Aymeric Augustin 
  Date:   2013-12-30 (Mon, 30 Dec 2013)

  Changed paths:
M django/__init__.py
M django/apps/base.py
M django/apps/registry.py
M django/contrib/admin/sites.py
M django/contrib/admin/validation.py
M django/core/serializers/base.py
M django/core/serializers/python.py
M django/core/wsgi.py
M django/db/models/loading.py
M docs/intro/tutorial01.txt
M docs/ref/django-admin.txt
M docs/releases/1.7.txt
M tests/runtests.py

  Log Message:
  ---
  Stopped populating the app registry as a side effect.

Since it triggers imports, it shouldn't be done lightly.

This commit adds a public API for doing it explicitly, django.setup(),
and does it automatically when using manage.py and wsgi.py.


Compare: https://github.com/django/django/compare/d6dc88cbc1eb...80d74097b4bd

-- 
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/52c1e63d6ea7f_6c961309d5410355a%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16735: Queryset values should be aliasable

[Django]

#16735: Queryset values should be aliasable
-+-
 Reporter:  alex.latchford@… |Owner:  nate_b
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  queryset, alias, |  Needs documentation:  0
  values |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by mjtamlyn):

 Agreed this should be possible.

 As a side note Russ - I've found the main optimisation for using values
 was in fact avoiding calling `Model.__init__` a few thousand times, not
 the lack of data on the wire.

-- 
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/094.7458e8c433d8ec5aaf15b44d6e299653%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] d6dc88: Avoided leaking state on exceptions in populate_mo...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d6dc88cbc1ebc4cfba6faf39edf6eebd41873029
  
https://github.com/django/django/commit/d6dc88cbc1ebc4cfba6faf39edf6eebd41873029
  Author: Aymeric Augustin 
  Date:   2013-12-30 (Mon, 30 Dec 2013)

  Changed paths:
M django/apps/registry.py

  Log Message:
  ---
  Avoided leaking state on exceptions in populate_models().


-- 
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/52c1e17255e15_c6511b1d58113383%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21702: Consider providing apps.get_model("app_label.ModelName")

[Django]

#21702: Consider providing apps.get_model("app_label.ModelName")
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  app-loading   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by mjtamlyn):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 And also avoids repeating the logic in multiple external applications.

-- 
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.88c09baaf4ddc1b1e0ef5c57f9e2d62e%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18350: Incorrect behavior when inadvertently building a query using two different models.

[Django]

#18350: Incorrect behavior when inadvertently building a query using two 
different
models.
-+-
 Reporter:  django@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  query model  |  Needs documentation:  0
  incorrect behavior |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

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


Comment:

 Duplicate of #14334

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

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

Re: [Django] #18350: Incorrect behavior when inadvertently building a query using two different models.

[Django]

#18350: Incorrect behavior when inadvertently building a query using two 
different
models.
-+-
 Reporter:  django@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  query model  |  Needs documentation:  0
  incorrect behavior |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by anonymous):

 I just got bitten by this bug again (different project). Is there a fix
 possible?

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

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

[django/django] 99649d: Assumed Python 3 throughout docs/intro.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 99649ddcb21b5c07258569d4585ffe3cf9eb4f38
  
https://github.com/django/django/commit/99649ddcb21b5c07258569d4585ffe3cf9eb4f38
  Author: Aymeric Augustin 
  Date:   2013-12-30 (Mon, 30 Dec 2013)

  Changed paths:
M docs/intro/contributing.txt
M docs/intro/index.txt
M docs/intro/install.txt
M docs/intro/overview.txt
M docs/intro/reusable-apps.txt
M docs/intro/tutorial01.txt
M docs/topics/install.txt

  Log Message:
  ---
  Assumed Python 3 throughout docs/intro.

Various small fixes while I was proof-reading.


  Commit: e5c89c62f2ea0b4d873eea8945d61cec3ba82673
  
https://github.com/django/django/commit/e5c89c62f2ea0b4d873eea8945d61cec3ba82673
  Author: Aymeric Augustin 
  Date:   2013-12-30 (Mon, 30 Dec 2013)

  Changed paths:
M docs/conf.py

  Log Message:
  ---
  Pointed intersphinx links to Python's default version.

Currently it's 3.3.


Compare: https://github.com/django/django/compare/7d7b27d2b125...e5c89c62f2ea

-- 
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/52c1d1bdbd688_69bd6d7d4c58196%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21710: API reference for default User implementation misses get_short_name

[Django]

#21710: API reference for default User implementation misses get_short_name
-+
 Reporter:  Keryn Knight   |  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:  Documentation|Version:  master
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  1|  UI/UX:  0
-+
 Off the back of #21709, I've noticed
 [https://docs.djangoproject.com/en/1.6/ref/contrib/auth/ this document]
 neglects to mention the `get_short_name` method defined on `AbstractUser`
 (and thus indirectly, on `User`), which is a requirement for a complete
 implementation of custom users.

-- 
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/080.f64783219795a7b73f63607b88abcb03%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21709: Admin template bug if there is no username field (custom user)

[Django]

#21709: Admin template bug if there is no username field (custom user)
+--
 Reporter:  mpecov@…|Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  contrib.admin   |  Version:  1.6
 Severity:  Normal  |   Resolution:  invalid
 Keywords:  admin template  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--
Changes (by charettes):

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


Comment:

 As pointed out by Keryn, the documentation '''clearly''' states that you
 must implement this method when specifying a custom `User` model.

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

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

Re: [Django] #21709: Admin template bug if there is no username field (custom user)

[Django]

#21709: Admin template bug if there is no username field (custom user)
+--
 Reporter:  mpecov@…|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  contrib.admin   |  Version:  1.6
 Severity:  Normal  |   Resolution:
 Keywords:  admin template  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--

Comment (by Keryn Knight ):

 This is correct behaviour -- the reason you're seeing it crash is, I
 believe, because your custom user implementation is incomplete, see
 [https://docs.djangoproject.com/en/1.6/topics/auth/customizing/#specifying-a
 -custom-user-model the "specifying a custom user model" documentation],
 which outlines the attributes (methods/properties) that need to exist for
 a complete implementation, one of which is `get_short_name`, which is set
 to raise a `NotImplementedError` if inheriting from `AbstractBaseUser`.
 There is, additionally, an
 [https://docs.djangoproject.com/en/1.6/ref/contrib/auth/ API reference for
 the default auth implementation], which enumerates an overview of what is
 expected.

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

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

Re: [Django] #16455: Postgis 2.0 Compatibility

[Django]

#16455: Postgis 2.0 Compatibility
-+-
 Reporter:  ckarrie  |Owner:  jbronn
 Type:  New feature  |   Status:  closed
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  postgis 2.0  | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by fcurella):

 I don't see any reason why we shouldn't add the 'IF NOT EXISTS' clause.

 @rizumu Can you create a new ticket for it and provide a pull request?

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

Re: [Django] #21709: Admin template bug if there is no username field (custom user)

[Django]

#21709: Admin template bug if there is no username field (custom user)
+--
 Reporter:  mpecov@…|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  contrib.admin   |  Version:  1.6
 Severity:  Normal  |   Resolution:
 Keywords:  admin template  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--

Comment (by mpecov@…):

 the function get_short_name is crashing the whole template with
 NotImplementedError

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

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

Re: [Django] #21709: Admin template bug if there is no username field (custom user)

[Django]

#21709: Admin template bug if there is no username field (custom user)
+--
 Reporter:  mpecov@…|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  contrib.admin   |  Version:  1.6
 Severity:  Normal  |   Resolution:
 Keywords:  admin template  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--

Comment (by anonymous):

 yup, but try to put USERNAME_FIELD = 'id' there and see what happens

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

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

Re: [Django] #21709: Admin template bug if there is no username field (custom user)

[Django]

#21709: Admin template bug if there is no username field (custom user)
+--
 Reporter:  mpecov@…|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  contrib.admin   |  Version:  1.6
 Severity:  Normal  |   Resolution:
 Keywords:  admin template  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--
Changes (by Siecje):

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


Comment:

 When you subclass AbstractBaseUser you need to specify a field to be used
 as the 'username'

 USERNAME_FIELD = 'email'

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

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

[Django] #21709: Admin template bug if there is no username field (custom user)

[Django]

#21709: Admin template bug if there is no username field (custom user)
---+
 Reporter:  mpecov@…   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.admin  |Version:  1.6
 Severity:  Normal |   Keywords:  admin template
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 Today is pretty normal to expect that someone will use a custom user model
 without the username field because he wants to have a simple login via
 email form.

 If you exclude the username field from the user model, the base.html in
 the contrib.admin will crash because of this line:
 {{{
  {% firstof user.get_short_name user.get_username %}.
 }}}
 So, my suggestion is to make a simple check
 {{{ {% if user.username %} }}}
 in this line, and avoid the potential problems

-- 
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/058.8adb49ff8edb68e68af681a2eba1661b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16455: Postgis 2.0 Compatibility

[Django]

#16455: Postgis 2.0 Compatibility
-+-
 Reporter:  ckarrie  |Owner:  jbronn
 Type:  New feature  |   Status:  closed
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  postgis 2.0  | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by rizumu):

 I am hitting an error on Django 1.7 master, PostgreSQL 9.3.2, postgis
 2.1.1. 'django.db.utils.ProgrammingError: extension "postgis" already
 exists' when running tests.

 
https://github.com/django/django/blob/master/django/contrib/gis/db/backends/postgis/creation.py#L92

 Changing the call line 92 to "CREATE EXTENSION IF NOT EXISTS postgis"
 fixes it, but I imagine it could be something with my environment as I
 haven't seen it before. Is this something worth opening a new ticket for?

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

Re: [Django] #16455: Postgis 2.0 Compatibility

[Django]

#16455: Postgis 2.0 Compatibility
-+-
 Reporter:  ckarrie  |Owner:  jbronn
 Type:  New feature  |   Status:  closed
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  postgis 2.0  | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by rizumu):

 * cc: tom@… (added)


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

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

Re: [Django] #21676: Provide a way to run code when Django starts

[Django]

#21676: Provide a way to run code when Django starts
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  app-loading  | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 Pull request is ready. Waiting for feedback on the mailing list.

-- 
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.5887a7688a533df8dee10978f062cc04%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21681: Simplify Apps.populate_models

[Django]

#21681: Simplify Apps.populate_models
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  app-loading  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * version:  1.6 => 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.e8ed9ba25c16ff8f3e6ce361fe372387%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21703: `exclude` query with `F` object across relationship fails

[Django]

#21703: `exclude` query with `F` object across relationship fails
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (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 pipermerriam):

 * type:  Uncategorized => Bug
 * component:  Uncategorized => Database layer (models, ORM)


-- 
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.305d542a759c937e20b86569bf9a3b09%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21706: Outdated Instructions - admin.py is not created from 1.6 onwards

[Django]

#21706: Outdated Instructions - admin.py is not created from 1.6 onwards
-+-
 Reporter:  vincentwoon@…|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.6
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  admin.py |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 I suspect your installation mixes Django 1.5 and 1.6, and manage.py /
 django-admin.py don't point to the same version as `import django`.

 What does `manage.py --version` return?

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

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

Re: [Django] #21706: Outdated Instructions - admin.py is not created from 1.6 onwards

[Django]

#21706: Outdated Instructions - admin.py is not created from 1.6 onwards
-+-
 Reporter:  vincentwoon@…|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.6
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  admin.py |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by charettes):

 I just tried `startapp` with 1.6 and admin.py was created correctly.

 {{{
 #!python
 simon@simon-laptop:~$ mktmpenv
 New python executable in 50d988b1f14121f7/bin/python
 Installing
 
Setuptools..done.
 Installing
 
Pip.done.
 This is a temporary environment. It will be deleted when you run
 'deactivate'.
 (50d988b1f14121f7)simon@simon-laptop:~/.virtualenvs/50d988b1f14121f7$ pip
 install "django==1.6.1"
 Downloading/unpacking django==1.6.1
   Using download cache from
 
/home/simon/.pip/cache/https%3A%2F%2Fpypi.python.org%2Fpackages%2Fsource%2FD%2FDjango%2FDjango-1.6.1.tar.gz
   Running setup.py egg_info for package django

 warning: no previously-included files matching '__pycache__' found
 under directory '*'
 warning: no previously-included files matching '*.py[co]' found under
 directory '*'
 Installing collected packages: django
   Running setup.py install for django
 changing mode of build/scripts-2.7/django-admin.py from 644 to 755

 warning: no previously-included files matching '__pycache__' found
 under directory '*'
 warning: no previously-included files matching '*.py[co]' found under
 directory '*'
 changing mode of /home/simon/.virtualenvs/50d988b1f14121f7/bin/django-
 admin.py to 755
 Successfully installed django
 Cleaning up...
 (50d988b1f14121f7)simon@simon-laptop:~/.virtualenvs/50d988b1f14121f7$
 django-admin.py startapp app
 (50d988b1f14121f7)simon@simon-laptop:~/.virtualenvs/50d988b1f14121f7$ ls
 app/
 admin.py  __init__.py  models.py  tests.py  views.py
 (50d988b1f14121f7)simon@simon-laptop:~/.virtualenvs/50d988b1f14121f7$
 deactivate
 }}}

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

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

Re: [Django] #21705: Generic Relations fail to detect validation error appropritely

[Django]

#21705: Generic Relations fail to detect validation error appropritely
-+-
 Reporter:  mo_ttds@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.6
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  AdminSite,   | Triage Stage:
  GenericRelation, unique_together,  |  Unreviewed
  IntegrityError |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by mo_ttds...):

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


-- 
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.42168966a4a18fc0e3df4e9c4e273229%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21706: Outdated Instructions - admin.py is not created from 1.6 onwards

[Django]

#21706: Outdated Instructions - admin.py is not created from 1.6 onwards
-+-
 Reporter:  vincentwoon@…|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.6
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  admin.py |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by woonzai):

 I'm using 1.6.1.

 admin.py is not created when I run "startapp".

 Inline image 1

 However the documentation for 1.6 assumes that admin.py still gets
 created.

 Inline image 2

 Part 2 assumes that polls/admin.py can be found, when in reality we need
 to create the file from scratch.


 Inline image 3

 Let me know if I have missed out anything.

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

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

Re: [Django] #19954: Storing of Binary fields leads to Exceptions

[Django]

#19954: Storing of Binary fields leads to Exceptions
-+-
 Reporter:  marcel.ryser.ch@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:  fixed
 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|
-+-

Comment (by loutrea@…):

 Replying to [comment:9 webadmin@…]:
 > Since this was introduced in django 1.5 can the fix also be included in
 the 1.5 branch?

 It should.

 I met this bug in the 1.5 branch so I fixed it as described here :
 http://stackoverflow.com/a/18923501

-- 
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/083.8a6aac1f387c9a11b1fd69a8823fec88%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21676: Provide a way to run code when Django starts

[Django]

#21676: Provide a way to run code when Django starts
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  app-loading   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by aaugustin):

 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1


Comment:

 Mailing list discussion: https://groups.google.com/d/msg/django-
 developers/_iggZzrYtJQ/9Tzi-kmS8RsJ

 Pull request: https://github.com/django/django/pull/2128

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

[Django] #21708: Documentation makes two distinct points but implies conjunction

[Django]

#21708: Documentation makes two distinct points but implies conjunction
---+
 Reporter:  ashley@…   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 As a django newbie I was confused by the following section:

 https://docs.djangoproject.com/en/1.6/topics/http/urls/#notes-on-
 capturing-text-in-urls

 The first section talks about the difference between URL matching types
 and the types passed as view arguments, the latter being only strings.

 This is followed by what I thought was a conjunction "A convenient trick
 is to...", implying a solution to the type disparity described above.

 Interpreted thus, the next section implies that setting a default
 parameter will cause an implicit type conversion to occur.

 In fact, the next section simply talks about a completely separate point,
 namely using a parameterised function for a non-parameterised url.

 Perhaps I'm just splitting hairs here, but I think the documentation would
 be improved if these two different notes were delineated in the
 documentation. Perhaps via bullet points.

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

Re: [Django] #21699: Provide a way to define a model without being registered into AppConfig

[Django]

#21699: Provide a way to define a model without being registered into AppConfig
--+-
 Reporter:  mitar |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  app-loading   | Triage Stage:  Someday/Maybe
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-
Changes (by aaugustin):

 * stage:  Unreviewed => Someday/Maybe


-- 
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.35ce7948450d646898726bcfac0b2941%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21699: Provide a way to define a model without being registered into AppConfig

[Django]

#21699: Provide a way to define a model without being registered into AppConfig
--+--
 Reporter:  mitar |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  app-loading   | 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):

 So we're talking of hacking the internals heavily here ;-)

 The implementation of Apps has become very straightforward if you ignore
 all the deprecated code. In the short term I'd just go for `del
 apps.all_models[app_label][model_name]` or `del
 apps.get_app_config(app_label).models[model_name]`, followed by
 `apps.clear_cache()`. The first one is marginally faster, the second one
 is marginally less likely to change. Make sure `model_name` is lowercase.

 Yesterday I tried to stop storing deferred models with the app registry.
 It would have solved your use case nicely -- what you're doing looks a lot
 like deferred models. Sadly it didn't work.

 This request has larger ramifications. Currently ModelBase.__new__ always
 returns a class registered in the app registry. It's quite a hack, and
 it's done for bad reasons that no longer exist since Django 1.4 (new
 project layout). I'm going to keep the ticket open with the following
 scope: get rid of get_registered_model, and then figure out what the
 registration API becomes.

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

Re: [Django] #21675: Provide an AppConfig for contrib apps with a translatable verbose_name

[Django]

#21675: Provide an AppConfig for contrib apps with a translatable verbose_name
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  app-loading   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by mjtamlyn):

 Setup code should likely by default include `admin.site.autodiscover()` as
 this clearly does not belong in a `urls.py` file.

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

Re: [Django] #21675: Provide an AppConfig for contrib apps with a translatable verbose_name

[Django]

#21675: Provide an AppConfig for contrib apps with a translatable verbose_name
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  app-loading   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by aaugustin):

 When #21676 is done, we should try to move setup code in AppConfigs too.
 As is, it won't work for people still using the app name in
 INSTALLED_APPS, unless we reintroduce some kind of autodiscovery.

-- 
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.302a305a68deb52cafea5fbaae770b61%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21699: Provide a way to define a model without being registered into AppConfig

[Django]

#21699: Provide a way to define a model without being registered into AppConfig
--+--
 Reporter:  mitar |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  app-loading   | Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by mitar):

 I am just copying from #21698, to make things more clear here. So my
 comment how I see that unregistering could help:
 > So there are two ways to allow making custom subclasses of models which
 should not be registered. One is to somehow allow some configuration in
 Meta (#21682), another is to call current metaclass which adds it, but be
 able to remove it from registry immediately afterwards (a bad side-effect
 is that registration signal has been already made).

 I didn't know about "no-op subclass" approach. This seems interesting
 idea.

 > Maybe the goal is to avoid leaking memory when creating a large number
 of such models?

 Yes. So what we are doing is developing support for dynamic schema. Users
 can add dynamically fields from the many hop away models. In a way we make
 proxy fields to things you would need multiple hops and we do one big join
 instead in the background to not have to fetch them again and again as you
 are hopping around. (Those hops can cross content type relations as well.)
 (Which mean you can change concrete implementation of a model, but the
 rest of your code can still work as it is referencing them through
 registered names.) We add those fields as virtual fields into base model
 and create a dummy proxy model to keep them, when we return a new queryset
 for them. So the syntax is something like:

 {{{
 queryset = models.Node.objects.regpoint('config').registry_fields(
 name='core.general#name',
 type='core.type#type',
 router_id='core.routerid#router_id',
 project='core.project#project.name',
 ).regpoint('monitoring').registry_fields(
 last_seen='core.general#last_seen',
 network_status='core.status#network',
 monitored_status='core.status#monitored',
 health_status='core.status#health',
 peers='network.routing.topology#link_count',
 ).order_by('type')
 }}}

 So, after you fetch those additional fields, returned queryset contains a
 dynamically created proxy model to `models.Node`, with `name` and others
 added as virtual fields. As this proxy model is useful only for this
 particular queryset, we do not want to register it globally. `core.status`
 is a registered name for a particular registry point, which can be
 implemented by any model which announces that it is implementing it. So a
 concrete related model can change (be extended by an app), but your
 queryset does not have to change.

 All this is a bit involved and we do not yet have good documentation, but
 you can check [https://dev.wlan-si.net/wiki/Nodewatcher/Registry this
 description] and our
 
[https://github.com/wlanslovenija/nodewatcher/blob/77ec018255fa0546b362376976db2f7b874968c1/nodewatcher/core/registry/lookup.py#L138
 current implantation of creating a dynamic proxy model and unregistered
 immediately afterwards is here]. We do not want that such models pile up.

 I know this is not public API, but it would still be good to have some
 clear way to: or not register a model when created, or be able to remove
 it from the registry. As you are planing on rewriting AppConfig, I just
 wanted to raise a point that some internal API (which I understand can
 change at any time) would be useful here.

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

Re: [Django] #21582: URL namespaces and included URLconfs: the example might be confusing

[Django]

#21582: URL namespaces and included URLconfs: the example might be confusing
-+-
 Reporter:  oubiga   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  url, include,| Triage Stage:  Accepted
  URLconf, documentation |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by oubiga):

 Tim, I'm late... sorry.
 Working with you is always a pleasure.

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

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

[Django] #21707: Uninformative error if block.super is used inside the block tag of a base template

[Django]

#21707: Uninformative error if block.super is used inside the block tag of a 
base
template
--+
 Reporter:  mitar |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Template system   |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 If `block.super` is used inside the block tag of a base template, an
 uninformative error is thrown:

 {{{
 'BlockNode' object has no attribute 'context'
 }}}

 It is thrown in `super` method when doing:

 {{{
 render_context = self.context.render_context
 }}}

 I think code should check for missing `self.context` and throw a more
 informative exception.

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

Re: [Django] #21705: Generic Relations fail to detect validation error appropritely

[Django]

#21705: Generic Relations fail to detect validation error appropritely
-+-
 Reporter:  mo_ttds@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  AdminSite,   | Triage Stage:
  GenericRelation, unique_together,  |  Unreviewed
  IntegrityError |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by anonymous):

 sorry.
 admin.site.register(Blog, BlogAdmin) should be admin.site.register(News,
 NewsAdmin).

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

Re: [Django] #21705: Generic Relations fail to detect validation error appropritely

[Django]

#21705: Generic Relations fail to detect validation error appropritely
-+-
 Reporter:  mo_ttds@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  AdminSite,   | Triage Stage:
  GenericRelation, unique_together,  |  Unreviewed
  IntegrityError |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by anonymous):

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


Comment:

 admin.site.register(Blog, BlogAdmin) should be admin.site.register(News,
 BlogAdmin).

-- 
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.63a3084b2a42e1bdca6c1881989c09d5%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17903: `ModelBackend.get_all_permissions` returns permissions for inactive users

[Django]

#17903: `ModelBackend.get_all_permissions` returns permissions for inactive 
users
--+
 Reporter:  SmileyChris   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by jorgecarleitao):

 * cc: jorgecarleitao (added)


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

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

Re: [Django] #17903: `ModelBackend.get_all_permissions` returns permissions for inactive users

[Django]

#17903: `ModelBackend.get_all_permissions` returns permissions for inactive 
users
--+
 Reporter:  SmileyChris   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  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 jorgecarleitao):

 I checked the code, and get_all_permissions does the following:
 {{{
 If user is anonymous: returns empty set.
 else: joins "user permissions" with "user groups permissions".
 }}}
 In "user groups permissions", if the user is superuser, this returns all
 permissions.

 So, in {{{has_perm}}} and {{{has_module_perms}}} we check for
 {{{is_active}}}, but in {{{get_all_permissions}}} we check for
 {{{is_anonymous}}}.
 Shouldn't this be consistent?

-- 
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.93887ebdfbd48fb7c01722fc9cbb%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21706: Outdated Instructions - admin.py is not created from 1.6 onwards

[Django]

#21706: Outdated Instructions - admin.py is not created from 1.6 onwards
-+-
 Reporter:  vincentwoon@…|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.6
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  admin.py |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 Can you double-check the version of Django you're using?

 This ticket describes exactly the behavior of Django < 1.6.

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

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

Re: [Django] #10827: django.auth create_permissions must clear the content type cache before creating permissions

[Django]

#10827: django.auth create_permissions must clear the content type cache before
creating permissions
--+
 Reporter:  seanl |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by jorgecarleitao):

 * cc: jorgecarleitao (added)


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

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

Re: [Django] #7599: add get_user_permissions method to ModelBackend

[Django]

#7599: add get_user_permissions method to ModelBackend
--+
 Reporter:  gwilson   |Owner:
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by jorgecarleitao):

 * cc: jorgecarleitao (added)


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

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

Re: [Django] #7599: add get_user_permissions method to ModelBackend

[Django]

#7599: add get_user_permissions method to ModelBackend
--+
 Reporter:  gwilson   |Owner:
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by jorgecarleitao):

 timo is right. I added a pull request,
 https://github.com/django/django/pull/2127, that fixes the docs of
 ModelBackend and apply the patch.

 I didn't added a test case because, like timo argued, the backend is not
 tested anyway. I will fill a ticket reporting this.

-- 
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.975975fd3db0829d0942dd61915d213b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.