Re: [Django] #17638: Link up topic guides with API reference

[Django]

#17638: Link up topic guides with API reference
---+-
 Reporter:  oinopion   |Owner:  lkitchner
 Type:  New feature|   Status:  assigned
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+-
Changes (by lkitchner):

 * owner:   => lkitchner
 * status:  new => assigned


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

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

Re: [Django] #21878: django-admin.py output Django version number

[Django]

#21878: django-admin.py output Django version number
+--
 Reporter:  wim@…   |Owner:  nobody
 Type:  New feature |   Status:  closed
Component:  Uncategorized   |  Version:  master
 Severity:  Normal  |   Resolution:  wontfix
 Keywords:  version number  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--
Changes (by russellm):

 * status:  new => closed
 * needs_better_patch:   => 0
 * resolution:   => wontfix
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 I disagree.

 When you run `manage.py shell`, you get the version number for *Python*,
 not Django. This is a feature of the Python shell; verbose output makes
 some sense here because it's an interactive shell, and some verbosity is
 to be expected.

 However, returning the version number from a non-interacive command line
 tool would be inconsistent with usual Unix command styling -- that is,
 that tools should be quiet unless they have something to actually report.
 "I'm running" isn't something interesting to report.

 If you want to get the Django version number, you can run `django-admin.py
 --version` (or `manage.py --version`), which is also consistent with Unix
 tooling.

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

[django/django] 74181c: [1.4.x] Added release note stub for 1.4.11.

[GitHub]

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: 74181c0a2c5eb52c63666f830403c9331fc1ad69
  
https://github.com/django/django/commit/74181c0a2c5eb52c63666f830403c9331fc1ad69
  Author: Tim Graham 
  Date:   2014-01-26 (Sun, 26 Jan 2014)

  Changed paths:
A docs/releases/1.4.11.txt
M docs/releases/index.txt

  Log Message:
  ---
  [1.4.x] Added release note stub for 1.4.11.

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

[django/django] 6f8e65: [1.6.x] Added release note stubs for 1.5.6 and 1.4...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 6f8e655ca0b58c40d0ad42ba388daf0b410034a5
  
https://github.com/django/django/commit/6f8e655ca0b58c40d0ad42ba388daf0b410034a5
  Author: Tim Graham 
  Date:   2014-01-26 (Sun, 26 Jan 2014)

  Changed paths:
A docs/releases/1.4.11.txt
A docs/releases/1.5.6.txt
M docs/releases/index.txt

  Log Message:
  ---
  [1.6.x] Added release note stubs for 1.5.6 and 1.4.11.

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

[django/django] b55d0e: [1.5.x] Added release note stubs for 1.5.6 and 1.4...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: b55d0ebff20c1870ea33ac9947e2accd4d436822
  
https://github.com/django/django/commit/b55d0ebff20c1870ea33ac9947e2accd4d436822
  Author: Tim Graham 
  Date:   2014-01-26 (Sun, 26 Jan 2014)

  Changed paths:
A docs/releases/1.4.11.txt
A docs/releases/1.5.6.txt
M docs/releases/index.txt

  Log Message:
  ---
  [1.5.x] Added release note stubs for 1.5.6 and 1.4.11.

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

[django/django] dfa289: Added release note stubs for 1.5.6 and 1.4.11.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: dfa28981ced2a6c005cc3c12fdc6b560080818a0
  
https://github.com/django/django/commit/dfa28981ced2a6c005cc3c12fdc6b560080818a0
  Author: Tim Graham 
  Date:   2014-01-26 (Sun, 26 Jan 2014)

  Changed paths:
A docs/releases/1.4.11.txt
A docs/releases/1.5.6.txt
M docs/releases/index.txt

  Log Message:
  ---
  Added release note stubs for 1.5.6 and 1.4.11.


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

Re: [Django] #21823: Upgrade vendor'd six to latest release

[Django]

#21823: Upgrade vendor'd six to latest release
--+
 Reporter:  Alex  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"257f8528b722ea943b2f2113fc2135743e2d80dc"]:
 {{{
 #!CommitTicketReference repository=""
 revision="257f8528b722ea943b2f2113fc2135743e2d80dc"
 [1.4.x] Fixed #21823 -- Upgraded six to 1.5.2

 Backport of 780ae7e9f8 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/062.70fa7a866fb940b048f639df263d1ced%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 257f85: [1.4.x] Fixed #21823 -- Upgraded six to 1.5.2

[GitHub]

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: 257f8528b722ea943b2f2113fc2135743e2d80dc
  
https://github.com/django/django/commit/257f8528b722ea943b2f2113fc2135743e2d80dc
  Author: Tim Graham 
  Date:   2014-01-26 (Sun, 26 Jan 2014)

  Changed paths:
M django/utils/six.py

  Log Message:
  ---
  [1.4.x] Fixed #21823 -- Upgraded six to 1.5.2

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

[django/django] 682420: [1.5.x] Fixed #21823 -- Upgraded six to 1.5.2

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 682420d108ee3e056ea0d538b61ffa2a850a
  
https://github.com/django/django/commit/682420d108ee3e056ea0d538b61ffa2a850a
  Author: Tim Graham 
  Date:   2014-01-26 (Sun, 26 Jan 2014)

  Changed paths:
M django/utils/six.py

  Log Message:
  ---
  [1.5.x] Fixed #21823 -- Upgraded six to 1.5.2

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

Re: [Django] #21823: Upgrade vendor'd six to latest release

[Django]

#21823: Upgrade vendor'd six to latest release
--+
 Reporter:  Alex  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"682420d108ee3e056ea0d538b61ffa2a850a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="682420d108ee3e056ea0d538b61ffa2a850a"
 [1.5.x] Fixed #21823 -- Upgraded six to 1.5.2

 Backport of 780ae7e9f8 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/062.94f287102db2543614c4613feebfdfe8%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 386359: [1.6.x] Added missing items to 1.6.2 release notes...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 38635977b7e8e3f103cbdb039cc71a0a6031bbf6
  
https://github.com/django/django/commit/38635977b7e8e3f103cbdb039cc71a0a6031bbf6
  Author: Tim Graham 
  Date:   2014-01-26 (Sun, 26 Jan 2014)

  Changed paths:
M docs/releases/1.6.2.txt

  Log Message:
  ---
  [1.6.x] Added missing items to 1.6.2 release notes.

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

[django/django] 2cbe1e: Added missing items to 1.6.2 release notes.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2cbe1e28fbf0662f8398e2cb5e7c7a1df11991bf
  
https://github.com/django/django/commit/2cbe1e28fbf0662f8398e2cb5e7c7a1df11991bf
  Author: Tim Graham 
  Date:   2014-01-26 (Sun, 26 Jan 2014)

  Changed paths:
M docs/releases/1.6.2.txt

  Log Message:
  ---
  Added missing items to 1.6.2 release notes.


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

Re: [Django] #21823: Upgrade vendor'd six to latest release

[Django]

#21823: Upgrade vendor'd six to latest release
--+
 Reporter:  Alex  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"319cfd209738c11ab2c81a5aa3a19e46a13761ef"]:
 {{{
 #!CommitTicketReference repository=""
 revision="319cfd209738c11ab2c81a5aa3a19e46a13761ef"
 [1.6.x] Fixed #21823 -- Upgraded six to 1.5.2

 Backport of 780ae7e9f8 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/062.77cf6edd7dbb71b5b2c0ce8c53ab76c0%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 319cfd: [1.6.x] Fixed #21823 -- Upgraded six to 1.5.2

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 319cfd209738c11ab2c81a5aa3a19e46a13761ef
  
https://github.com/django/django/commit/319cfd209738c11ab2c81a5aa3a19e46a13761ef
  Author: Tim Graham 
  Date:   2014-01-26 (Sun, 26 Jan 2014)

  Changed paths:
M django/utils/six.py

  Log Message:
  ---
  [1.6.x] Fixed #21823 -- Upgraded six to 1.5.2

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

Re: [Django] #21874: Consistent handling for app modules with no (or empty) __path__

[Django]

#21874: Consistent handling for app modules with no (or empty) __path__
--+
 Reporter:  carljm|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 aaugustin):

 * keywords:   => app-loading


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

[django/django] 780ae7: Fixed #21823 -- Upgraded six to 1.5.2

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 780ae7e9f804037626ce29ba3707c6c8b77ce4fc
  
https://github.com/django/django/commit/780ae7e9f804037626ce29ba3707c6c8b77ce4fc
  Author: Tim Graham 
  Date:   2014-01-26 (Sun, 26 Jan 2014)

  Changed paths:
M django/utils/six.py

  Log Message:
  ---
  Fixed #21823 -- Upgraded six to 1.5.2


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

Re: [Django] #21823: Upgrade vendor'd six to latest release

[Django]

#21823: Upgrade vendor'd six to latest release
--+
 Reporter:  Alex  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"780ae7e9f804037626ce29ba3707c6c8b77ce4fc"]:
 {{{
 #!CommitTicketReference repository=""
 revision="780ae7e9f804037626ce29ba3707c6c8b77ce4fc"
 Fixed #21823 -- Upgraded six to 1.5.2
 }}}

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

Re: [Django] #21874: Consistent handling for app modules with no (or empty) __path__

[Django]

#21874: Consistent handling for app modules with no (or empty) __path__
--+
 Reporter:  carljm|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  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 carljm):

 Replying to [comment:1 aaugustin]:
 > Django has an explicity `django.template.loaders.eggs.Loader` to load
 templates from eggs, but nothing to load other files (static files,
 translations, etc.) So eggs don't work for loading files except for a
 specific case that requires explicit configuration of the template
 loaders. `app_config.path` will have a bogus value; live with it or
 upgrade to a more palatable package format ;-)

 Indeed, I agree. That's why I didn't include case (E) in my list of cases
 where I think we need better handling. If a module loader is going to
 return bogus paths, I think Django should just pass them along. (Plus,
 almost all uses of `appconfig.path` are likely to take roughly the form
 `mypath = os.path.join(appconfig.path, 'something'); if
 os.path.exists(mypath): ...` and a bogus path won't blow up that code.

 > I assume wheels don't matter here because they're expanded to regular
 files during installation (but I could be wrong).

 That's correct - wheels and unzipped eggs are both loaded by the normal
 filesystem module loading process, so there is nothing special about them
 from this perspective.

 > I agree with your proposal. I don't see any holes in the reasoning.
 >
 > As far as I know, only the AppConfigStub subclass of AppConfig has
 app_module set to None. This is a dumb class provided as a convenience for
 the migrations system. Simply adjust its `__init__` so that the tests pass
 -- it's an private API. EDIT: simply setting `path = None` on the class
 should do. Migrations don't use `path`.

 Yep, I discovered this later last night. I also discovered why Django's
 test suite may have misleadingly made it seem that egg-loaded modules
 would have no `__path__`; because our egg-template-loader tests have a
 function that creates fake eggs and stuffs them into `sys.modules`, and
 those fake eggs (unlike real ones) have no `__path__`.

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

[django/django] 10e3fa: Fixed #19774 -- Deprecated the contenttypes.generi...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 10e3faf191d8f230dde8534d1c8fad8c8717816e
  
https://github.com/django/django/commit/10e3faf191d8f230dde8534d1c8fad8c8717816e
  Author: Simon Charette 
  Date:   2014-01-26 (Sun, 26 Jan 2014)

  Changed paths:
M django/contrib/comments/models.py
A django/contrib/contenttypes/admin.py
M django/contrib/contenttypes/checks.py
A django/contrib/contenttypes/fields.py
A django/contrib/contenttypes/forms.py
M django/contrib/contenttypes/generic.py
M docs/ref/contrib/admin/index.txt
M docs/ref/contrib/comments/models.txt
M docs/ref/contrib/contenttypes.txt
M docs/ref/models/querysets.txt
M docs/releases/1.4-alpha-1.txt
M docs/releases/1.4-beta-1.txt
M docs/releases/1.4.txt
M docs/releases/1.6.txt
M docs/releases/1.7.txt
M tests/admin_inlines/models.py
M tests/admin_views/models.py
M tests/aggregation_regress/models.py
M tests/backends/models.py
M tests/contenttypes_tests/tests.py
M tests/custom_managers/models.py
M tests/delete_regress/models.py
M tests/fixtures/models.py
M tests/generic_inline_admin/admin.py
M tests/generic_inline_admin/models.py
M tests/generic_inline_admin/tests.py
M tests/generic_relations/models.py
M tests/generic_relations/tests.py
M tests/generic_relations_regress/models.py
M tests/managers_regress/models.py
M tests/multiple_database/models.py
M tests/prefetch_related/models.py
M tests/serializers_regress/models.py

  Log Message:
  ---
  Fixed #19774 -- Deprecated the contenttypes.generic module.

It contained models, forms and admin objects causing undesirable
import side effects. Refs #16368.

Thanks to Ramiro, Carl and Loïc for the review.


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

Re: [Django] #19774: contentypes generic module has core functionality plus admins-specific one

[Django]

#19774: contentypes generic module has core functionality plus admins-specific 
one
-+-
 Reporter:  ramiro   |Owner:  ramiro
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:   |   Resolution:  fixed
  contrib.contenttypes   | Triage Stage:  Ready for
 Severity:  Normal   |  checkin
 Keywords:  dependency generic   |  Needs documentation:  0
  contenttypes   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by Simon Charette ):

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


Comment:

 In [changeset:"10e3faf191d8f230dde8534d1c8fad8c8717816e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="10e3faf191d8f230dde8534d1c8fad8c8717816e"
 Fixed #19774 -- Deprecated the contenttypes.generic module.

 It contained models, forms and admin objects causing undesirable
 import side effects. Refs #16368.

 Thanks to Ramiro, Carl and Loïc for the review.
 }}}

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

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

Re: [Django] #16368: Custom sites model overridden by contrib.sites.model.Site

[Django]

#16368: Custom sites model overridden by contrib.sites.model.Site
+
 Reporter:  briehan.lombaard@…  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  contrib.sites   |  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 Simon Charette ):

 In [changeset:"10e3faf191d8f230dde8534d1c8fad8c8717816e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="10e3faf191d8f230dde8534d1c8fad8c8717816e"
 Fixed #19774 -- Deprecated the contenttypes.generic module.

 It contained models, forms and admin objects causing undesirable
 import side effects. Refs #16368.

 Thanks to Ramiro, Carl and Loïc for the review.
 }}}

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

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

[django/django] c38819: Fixed some missing/extraneous new line warnings.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c3881944e8651ad98e29561154186e87928ca319
  
https://github.com/django/django/commit/c3881944e8651ad98e29561154186e87928ca319
  Author: Simon Charette 
  Date:   2014-01-26 (Sun, 26 Jan 2014)

  Changed paths:
M django/apps/config.py
M django/test/utils.py
M tests/apps/namespace_package_base/nsapp/apps.py
M tests/apps/tests.py

  Log Message:
  ---
  Fixed some missing/extraneous new line warnings.


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

Re: [Django] #8540: daemonize should close all open files

[Django]

#8540: daemonize should close all open files
-+-
 Reporter:  paulegan |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  daemonize|  Needs documentation:  0
  become_daemon fastcgi  |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

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


Comment:

 runfcgi is deprecated in Django 1.7 and that appears to be the only code
 in Django that uses django/utils/daemonize.py.

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

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

Re: [Django] #17081: runfcgi with daemonize=True requires aboslute path for pidfile parameter

[Django]

#17081: runfcgi with daemonize=True requires aboslute path for pidfile parameter
-+-
 Reporter:   |Owner:  nobody
  bernhard.hollaender@…  |   Status:  closed
 Type:  Bug  |  Version:  1.3
Component:  Core (Management |   Resolution:  wontfix
  commands)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  runfcgi  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

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


Comment:

 runfcgi is being deprecated in Django 1.7.

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

Re: [Django] #21751: Django doesn't do a good job of closing cursors

[Django]

#21751: Django doesn't do a good job of closing cursors
-+-
 Reporter:  manfre   |Owner:  manfre
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by timo):

 I closed #14298 and #17956 as duplicates.

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

Re: [Django] #14298: maximum open cursors exceeded on Jython and Oracle

[Django]

#14298: maximum open cursors exceeded on Jython and Oracle
-+-
 Reporter:   |Owner:  xoror
  stephanekonstantaropoulos  |   Status:  closed
 Type:  Bug  |  Version:  master
Component:  Database layer   |   Resolution:  duplicate
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  Oracle Jython|  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-
Changes (by timo):

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


Comment:

 I think this is a duplicate of #21751 which has a patch to close cursors
 after they are used.

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

Re: [Django] #17956: Explicit closing cursors is required for the consistency in multithread environment

[Django]

#17956: Explicit closing cursors is required for the consistency in multithread
environment
-+-
 Reporter:  nnseva   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.3
Component:  Database layer   |   Resolution:  duplicate
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  thread, threading,   |  Patch needs improvement:  0
  cursor, close, finalization,   |UI/UX:  0
  __del__, out of sync, twisted  |
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

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


Comment:

 I think this is a duplicate of #21751 which has a patch to close cursors
 after they are used.

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

[django/django] 8f2f48: Fixed #21866 -- Replaced "COMMIT" in managmement c...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8f2f48ecc9431c4d8959354a607fa559aa85dd99
  
https://github.com/django/django/commit/8f2f48ecc9431c4d8959354a607fa559aa85dd99
  Author: Wojciech Banaś 
  Date:   2014-01-26 (Sun, 26 Jan 2014)

  Changed paths:
M django/core/management/base.py

  Log Message:
  ---
  Fixed #21866 -- Replaced "COMMIT" in managmement command SQL with backend 
hook.


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

Re: [Django] #21866: Static word "COMMIT"

[Django]

#21866: Static word "COMMIT"
-+-
 Reporter:  fizista  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |   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:  1|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"8f2f48ecc9431c4d8959354a607fa559aa85dd99"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8f2f48ecc9431c4d8959354a607fa559aa85dd99"
 Fixed #21866 -- Replaced "COMMIT" in managmement command SQL with backend
 hook.
 }}}

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

Re: [Django] #19738: "manage.py shell" on a fresh project raises RuntimeWarning about naive datetime, if IPython is installed

[Django]

#19738: "manage.py shell" on a fresh project raises RuntimeWarning about naive
datetime, if IPython is installed
-+-
 Reporter:  carljm   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Sylvain_):

 This warning is still present in:

 {{{
 $ python --version
 Python 2.7.5+

 $ python -c "import django; print(django.get_version())"
 1.5.4
 }}}

 I'm a python newcomer and I was looking a way to respect $PYTHONSTARTUP.
 Following #6682 I also installed IPython.

 both ipython, and django came from ubuntu packages
 {{{
 $ python-django   1.5.4-1ubuntu1High-level Python web development
 framework


 $ lsb_release -a
 No LSB modules are available.
 Distributor ID: Ubuntu
 Description:Ubuntu 13.10
 Release:13.10
 Codename:   saucy
 }}}


 this gives:
 {{{
 $ python manage.py shell
 /usr/lib/python2.7/dist-packages/django/db/backends/sqlite3/base.py:53:
 RuntimeWarning: SQLite received a naive datetime (2014-01-26
 18:40:37.242040) while time zone support is active.
   RuntimeWarning)

 /usr/lib/python2.7/dist-packages/IPython/frontend/terminal/embed.py:239:
 DeprecationWarning: With-statements now directly support multiple context
 managers
   with nested(self.builtin_trap, self.display_trap):

 Python 2.7.5+ (default, Sep 19 2013, 13:49:51)
 Type "copyright", "credits" or "license" for more information.

 IPython 0.13.2 -- An enhanced Interactive Python.
 ? -> Introduction and overview of IPython's features.
 %quickref -> Quick reference.
 help  -> Python's own help system.
 object?   -> Details about 'object', use 'object??' for extra details.

 In [1]:
 }}}

 I found a workaround here: http://stackoverflow.com/questions/11708821
 /django-ipython-sqlite-complains-about-naive-datetime

 But this fixes only the sqlite warning.


 {{{
 $ ipython profile create
 [ProfileCreate] Generating default config file:
 u'/home/sylvain/.config/ipython/profile_default/ipython_config.py'
 }}}

 and added those lines
 {{{
 import warnings
 import exceptions
 warnings.filterwarnings("ignore", category=exceptions.RuntimeWarning,
 module='django.db.backends.sqlite3.base', lineno=53)
 }}}

 rereading the [https://docs.djangoproject.com/en/1.5/intro/tutorial01/
 tutorial]
 I found a better way (ipython removed):

 {{{
 export PYTHONSTARTUP=$PWD/_pythonrc
 export DJANGO_SETTINGS_MODULE=mysite.settings
 $ cat _pythonrc
 # Import the model classes we just wrote.
 from polls.models import Poll, Choice
 from django.utils import timezone

 $ python
 Python 2.7.5+ (default, Sep 19 2013, 13:49:51)
 [GCC 4.8.1] on linux2
 Type "help", "copyright", "credits" or "license" for more information.
 >>> Poll.objects.all()
 []
 }}}

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

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

Re: [Django] #21875: Runtime Error with Django-Tastypie: "App registry isn't ready yet."

[Django]

#21875: Runtime Error with Django-Tastypie: "App registry isn't ready yet."
-+-
 Reporter:  benjamin.e.white1@…  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:
 Severity:  Normal   |  1.7-alpha-1
 Keywords:  app-loading  |   Resolution:
  tastypie   | 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):

 Related thread: https://groups.google.com/d/msg/django-
 developers/lmT1JxsWHPo/N2V9U5SN9gwJ

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

Re: [Django] #19774: contentypes generic module has core functionality plus admins-specific one

[Django]

#19774: contentypes generic module has core functionality plus admins-specific 
one
-+-
 Reporter:  ramiro   |Owner:  ramiro
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:   |   Resolution:
  contrib.contenttypes   | Triage Stage:  Ready for
 Severity:  Normal   |  checkin
 Keywords:  dependency generic   |  Needs documentation:  0
  contenttypes   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by ramiro):

 Simon,

 I had some unfinished work in that direction and was a bit uncomfortable
 about still having the formset definition in the new fields module. Good
 call on creating forms.py

 Please go ahead, my review didn't find 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/064.39a341d287bc2376fc99bfa0202bd99a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21880: from django.utils.timezone import * does not work as expected

[Django]

#21880: from django.utils.timezone import * does not work as expected
--+
 Reporter:  wim@… |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  closed
Component:  Uncategorized |Version:  1.6
 Severity:  Normal| Resolution:  fixed
 Keywords:  timezone import * |   Triage Stage:  Unreviewed
Has patch:  0 |  Easy pickings:  0
UI/UX:  0 |
--+

Comment (by Aymeric Augustin ):

 In [changeset:"db60a520857dfe1564d824809dacfffd55662a16"]:
 {{{
 #!CommitTicketReference repository=""
 revision="db60a520857dfe1564d824809dacfffd55662a16"
 [1.6.x] Fixed #21880 -- Added missing items to
 django.utils.timezone.__all__.

 Thanks Wim for the report.

 Backport of 2b154ae 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/074.b5b021fd8a81eec1eae37c22e4940b66%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] db60a5: [1.6.x] Fixed #21880 -- Added missing items to dja...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: db60a520857dfe1564d824809dacfffd55662a16
  
https://github.com/django/django/commit/db60a520857dfe1564d824809dacfffd55662a16
  Author: Aymeric Augustin 
  Date:   2014-01-26 (Sun, 26 Jan 2014)

  Changed paths:
M django/utils/timezone.py

  Log Message:
  ---
  [1.6.x] Fixed #21880 -- Added missing items to django.utils.timezone.__all__.

Thanks Wim for the report.

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

[django/django] 2b154a: Fixed #21880 -- Added missing items to django.util...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2b154ae2803d46c68d3ec78789866d22231a92d0
  
https://github.com/django/django/commit/2b154ae2803d46c68d3ec78789866d22231a92d0
  Author: Aymeric Augustin 
  Date:   2014-01-26 (Sun, 26 Jan 2014)

  Changed paths:
M django/utils/timezone.py

  Log Message:
  ---
  Fixed #21880 -- Added missing items to django.utils.timezone.__all__.

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

Re: [Django] #21880: from django.utils.timezone import * does not work as expected

[Django]

#21880: from django.utils.timezone import * does not work as expected
--+
 Reporter:  wim@… |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  closed
Component:  Uncategorized |Version:  1.6
 Severity:  Normal| Resolution:  fixed
 Keywords:  timezone import * |   Triage Stage:  Unreviewed
Has patch:  0 |  Easy pickings:  0
UI/UX:  0 |
--+
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"2b154ae2803d46c68d3ec78789866d22231a92d0"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2b154ae2803d46c68d3ec78789866d22231a92d0"
 Fixed #21880 -- Added missing items to django.utils.timezone.__all__.

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

Re: [Django] #21688: Invalidate internal caches when INSTALLED_APPS changes

[Django]

#21688: Invalidate internal caches when INSTALLED_APPS changes
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  app-loading   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by aaugustin):

 * has_patch:  0 => 1


Comment:

 PR: https://github.com/django/django/pull/2217

 This doesn't have much to do with app-loading, in fact...

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

Re: [Django] #21879: Error in reverse m2m query if the model with ManyToManyField has CharField primary key

[Django]

#21879: Error in reverse m2m query if the model with ManyToManyField has 
CharField
primary key
-+-
 Reporter:  prashant.a.borde@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Uncategorized|  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  many-to-many | Triage Stage:
  relationships reverse m2m query|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by edrobap):

 Replying to [comment:3 bruno@…]:
 > This hardly qualifies as a bug : according to
 https://docs.djangoproject.com/en/1.6/topics/auth/customizing/#specifying-a
 -custom-user-model `contrib.auth` expects your custom User model to have
 an integer primary key.
 >


 You are right to point out that only interger primary key can be used in
 custom User model. But, this bug is not related to only User model. Let's
 say the models were, you still get the error:

 {{{

 from django.db import models
 import uuid

 class Publication(models.Model):
 title = models.CharField(max_length=30)

 class Article(models.Model):
 id = models.CharField(primary_key=True, max_length=32,
 default=str(uuid.uuid4()).replace('-', ''))
 headline = models.CharField(max_length=100)
 publications = models.ManyToManyField(Publication)
 }}}

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

Re: [Django] #21879: Error in reverse m2m query if the model with ManyToManyField has CharField primary key

[Django]

#21879: Error in reverse m2m query if the model with ManyToManyField has 
CharField
primary key
-+-
 Reporter:  prashant.a.borde@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Uncategorized|  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  many-to-many | Triage Stage:
  relationships reverse m2m query|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by bruno@…):

 This hardly qualifies as a bug : according to
 https://docs.djangoproject.com/en/1.6/topics/auth/customizing/#specifying-a
 -custom-user-model `contrib.auth` expects your custom User model to have
 an integer primary key.

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

[Django] #21880: from django.utils.timezone import * does not work as expected

[Django]

#21880: from django.utils.timezone import * does not work as expected
--+---
 Reporter:  wim@… |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Uncategorized |Version:  1.6
 Severity:  Normal|   Keywords:  timezone import *
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+---
 Hi,

 {{{from django.utils.timezone import * }}} does not work as expected.

 1. Not all functions documented
 (https://docs.djangoproject.com/en/1.6/ref/utils/#module-
 django.utils.timezone ) are in __all__

 2. In Django 1.7, there is one more, but many are missing:
 {{{
 __all__ = [
 'utc', 'get_fixed_timezone',
 'get_default_timezone', 'get_current_timezone',
 'activate', 'deactivate', 'override',
 'is_naive', 'is_aware', 'make_aware', 'make_naive',
 ]
 }}}

 It would be very convenient for testing to be able to import * and get all
 the available functions

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

[django/django] 4f03b7: Fixed #21877 -- Renamed django.apps.base to config...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4f03b718f712b39f306f6dfe177e1f65b5437ac2
  
https://github.com/django/django/commit/4f03b718f712b39f306f6dfe177e1f65b5437ac2
  Author: Aymeric Augustin 
  Date:   2014-01-26 (Sun, 26 Jan 2014)

  Changed paths:
M django/apps/__init__.py
R django/apps/base.py
A django/apps/config.py
M django/apps/registry.py
M django/db/models/base.py

  Log Message:
  ---
  Fixed #21877 -- Renamed django.apps.base to config.


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

Re: [Django] #21877: Rename django.apps.base to django.apps.config

[Django]

#21877: Rename django.apps.base to django.apps.config
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Core (Other) |   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  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:"4f03b718f712b39f306f6dfe177e1f65b5437ac2"]:
 {{{
 #!CommitTicketReference repository=""
 revision="4f03b718f712b39f306f6dfe177e1f65b5437ac2"
 Fixed #21877 -- Renamed django.apps.base to config.
 }}}

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

Re: [Django] #21879: Error in reverse m2m query if the model with ManyToManyField has CharField primary key (was: Error in reverse m2m query if the table with ManyToManyField has CharField primary key

[Django]

#21879: Error in reverse m2m query if the model with ManyToManyField has 
CharField
primary key
-+-
 Reporter:  prashant.a.borde@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Uncategorized|  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  many-to-many | Triage Stage:
  relationships reverse m2m query|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/084.65a66b822e54ff2f501ea95fc82f86ac%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 the app registry / Get rid of get_registered_model (was: Provide a way to define a model without being registered int

[Django]

#21699: Provide a way to define a model without being registered into the app
registry / Get rid of get_registered_model
--+-
 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 aaugustin):

 mitar, how should relations (foreign keys, one to one, many to many)
 between such a model and other models behave?

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

Re: [Django] #21877: Rename django.apps.base to django.apps.config

[Django]

#21877: Rename django.apps.base to django.apps.config
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Core (Other) |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * has_patch:  0 => 1
 * stage:  Unreviewed => Ready for checkin


Comment:

 PR: https://github.com/django/django/pull/2216

-- 
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.b306a23fc0d5a432c57cc44409ba0e35%40djangoproject.com.
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:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Core (Other) |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  app-loading  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 `get_registered_model` doesn't need the same treatment because it's used
 in only two places, it's a private API and I'd like to remove it
 eventually.

-- 
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.b64f5bd3e0f91fe828900045712779fd%40djangoproject.com.
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:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Core (Other) |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  app-loading  |  checkin
Has patch:  1|  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:"3c47786cb91617b3757e57b6bfeda06ef14e561a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3c47786cb91617b3757e57b6bfeda06ef14e561a"
 Fixed #21702 -- get_model('app_label.ModelName').

 Also added tests for get_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/067.f8e8f89a2a0e75c6bc80e9ca05dc0c45%40djangoproject.com.
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:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Core (Other) |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  app-loading  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"f901b4d6c869f4cfb4fc28a861c481f28e46bb3f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f901b4d6c869f4cfb4fc28a861c481f28e46bb3f"
 Took advantage of the new get_model API. Refs #21702.
 }}}

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

[django/django] 3c4778: Fixed #21702 -- get_model('app_label.ModelName').

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3c47786cb91617b3757e57b6bfeda06ef14e561a
  
https://github.com/django/django/commit/3c47786cb91617b3757e57b6bfeda06ef14e561a
  Author: Aymeric Augustin 
  Date:   2014-01-26 (Sun, 26 Jan 2014)

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

  Log Message:
  ---
  Fixed #21702 -- get_model('app_label.ModelName').

Also added tests for get_model.


  Commit: f901b4d6c869f4cfb4fc28a861c481f28e46bb3f
  
https://github.com/django/django/commit/f901b4d6c869f4cfb4fc28a861c481f28e46bb3f
  Author: Aymeric Augustin 
  Date:   2014-01-26 (Sun, 26 Jan 2014)

  Changed paths:
M django/contrib/admindocs/views.py
M django/contrib/auth/__init__.py
M django/contrib/auth/checks.py
M django/contrib/comments/views/comments.py
M django/core/management/commands/dumpdata.py
M django/core/serializers/python.py
M django/core/serializers/xml_serializer.py
M django/db/migrations/state.py
M django/db/models/base.py

  Log Message:
  ---
  Took advantage of the new get_model API. Refs #21702.


Compare: https://github.com/django/django/compare/8e1fc0349124...f901b4d6c869

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

Re: [Django] #21879: Error in reverse m2m query if the table with ManyToManyField has CharField primary key (was: Error in reverse m2m query if if the table with ManyToManyField has CharField primary

[Django]

#21879: Error in reverse m2m query if the table with ManyToManyField has 
CharField
primary key
-+-
 Reporter:  prashant.a.borde@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Uncategorized|  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  many-to-many | Triage Stage:
  relationships reverse m2m query|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by prashant.a.borde@…):

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


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

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

[Django] #21879: Error in reverse m2m query if if the table with ManyToManyField has CharField primary key

[Django]

#21879: Error in reverse m2m query if if the table with ManyToManyField has
CharField primary key
-+-
 Reporter:   |  Owner:  nobody
  prashant.a.borde@… | Status:  new
 Type:  Bug  |Version:  1.5
Component:   |   Keywords:  many-to-many relationships reverse
  Uncategorized  |  m2m query
 Severity:  Normal   |  Has patch:  0
 Triage Stage:   |  UI/UX:  0
  Unreviewed |
Easy pickings:  0|
-+-
 Here is my models.py file:


 {{{
 from django.db import models
 import uuid

 class Group(models.Model):
 Name = models.CharField('Name', max_length=100)

 class UserProfile(models.Model):
 id = models.CharField(primary_key=True, max_length=32,
 default=str(uuid.uuid4()).replace('-', ''))
 Name = models.CharField('Name', max_length=100)
 groups = models.ManyToManyField(Group, null=True, blank=True)

 }}}

 I execute following commands on Django shell (manage.py shell):


 {{{
 >>> g1=Group(Name='g1')
 >>> g1.save()
 >>> u1=UserProfile(Name='u1')
 >>> u1.save()
 >>> u1.groups.add(g1)
 >>> Groups.objects.filter(userprofile=u1)

 }}}

 The last command (a reverse m2m query) throws following error:

 {{{

 Traceback (most recent call last):
   File "", line 1, in 
 NameError: name 'Groups' is not defined
 >>> Group.objects.filter(userprofile=u1)
 Traceback (most recent call last):
   File "", line 1, in 
   File "/usr/local/lib/python2.7/dist-
 packages/django/db/models/manager.py", line 155, in filter
 return self.get_query_set().filter(*args, **kwargs)
   File "/usr/local/lib/python2.7/dist-packages/django/db/models/query.py",
 line 655, in filter
 return self._filter_or_exclude(False, *args, **kwargs)
   File "/usr/local/lib/python2.7/dist-packages/django/db/models/query.py",
 line 673, in _filter_or_exclude
 clone.query.add_q(Q(*args, **kwargs))
   File "/usr/local/lib/python2.7/dist-
 packages/django/db/models/sql/query.py", line 1266, in add_q
 can_reuse=used_aliases, force_having=force_having)
   File "/usr/local/lib/python2.7/dist-
 packages/django/db/models/sql/query.py", line 1197, in add_filter
 connector)
   File "/usr/local/lib/python2.7/dist-
 packages/django/db/models/sql/where.py", line 71, in add
 value = obj.prepare(lookup_type, value)
   File "/usr/local/lib/python2.7/dist-
 packages/django/db/models/sql/where.py", line 339, in prepare
 return self.field.get_prep_lookup(lookup_type, value)
   File "/usr/local/lib/python2.7/dist-
 packages/django/db/models/fields/related.py", line 143, in get_prep_lookup
 return self._pk_trace(value, 'get_prep_lookup', lookup_type)
   File "/usr/local/lib/python2.7/dist-
 packages/django/db/models/fields/related.py", line 216, in _pk_trace
 v = getattr(field, prep_func)(lookup_type, v, **kwargs)
   File "/usr/local/lib/python2.7/dist-
 packages/django/db/models/fields/__init__.py", line 322, in
 get_prep_lookup
 return self.get_prep_value(value)
   File "/usr/local/lib/python2.7/dist-
 packages/django/db/models/fields/__init__.py", line 555, in get_prep_value
 return int(value)
 ValueError: invalid literal for int() with base 10:
 'c4adb615aa3c466185065997309e1c70'

 }}}

-- 
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.fe6a296ad571c0c2f8eed359b35c1021%40djangoproject.com.
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:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Core (Other) |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  app-loading  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 PR: https://github.com/django/django/pull/2215

 Anyone interested in reviewing it?

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

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

[Django] #21878: django-admin.py output Django version number

[Django]

#21878: django-admin.py output Django version number
---+
 Reporter:  wim@…  |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  Uncategorized  |Version:  master
 Severity:  Normal |   Keywords:  version number
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 When I do:

 {{{
 python manage.py shell
 }}}

 the output is very helpful and tells me the current date and time and the
 Django version number.

 When I do:
 {{{
 django-admin.py startproject my_project
 }}}
 however, I get no output at all.

 For me, it would be very helpful to know the Django versioning number,
 because the output of startproject differs per version and because
 sometimes I have an older Django installed.

 Continuing, outputting the Django version number when using {{{ python
 manage.py shell }}} would be helpful as well.

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

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

[Django] #21877: Rename django.apps.base to django.apps.config

[Django]

#21877: Rename django.apps.base to django.apps.config
+
   Reporter:  aaugustin |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Core (Other)  |Version:  master
   Severity:  Release blocker   |   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 This module defines the AppConfig class. I don't think `base` is a
 particularly good or helpful name.

 Thoughts?

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

Re: [Django] #21840: LazyObject wrapped instances can no longer be coerced to Bool due to #20924

[Django]

#21840: LazyObject wrapped instances can no longer be coerced to Bool due to 
#20924
--+
 Reporter:  gabejackson   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Utilities |  Version:  master
 Severity:  Release blocker   |   Resolution:
 Keywords:  LazyObject utils  | 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):

 I left a note on the commit, asking the authors for ideas:
 
https://github.com/django/django/commit/aa01c99f5587b36c354e80c682ad52e1a3b41455#commitcomment-5180010

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

Re: [Django] #21559: Generic relations regression in Django 1.6

[Django]

#21559: Generic relations regression in Django 1.6
-+-
 Reporter:  khoobks@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * severity:  Release blocker => Normal


Comment:

 Given the akaariai's explanation, I don't think this is a release blocker.
 Something that didn't work still doesn't work. This shouldn't prevent 1.7
 from moving forwards.

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

[Django] #21876: Boost your size using Vimax

[Django]

#21876: Boost your size using Vimax
-+
 Reporter:  anonymous|  Owner:  nobody
 Type:  New feature  | Status:  new
Component:  Python 3 |Version:  1.6
 Severity:  Normal   |   Keywords:  ok
 Triage Stage:  Unreviewed   |  Has patch:  1
Easy pickings:  1|  UI/UX:  1
-+
 Testing for bug website

 [http://about.me/vimaxdiscount/ Vimax]

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

Re: [Django] #7623: Multi-table inheritance does not allow linking new instance of child model to existing parent model instance.

[Django]

#7623: Multi-table inheritance does not allow linking new instance of child 
model
to existing parent model instance.
-+-
 Reporter:  brooks.travis@…  |Owner:
 Type:  Bug  |  elektrrrus
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  model-inheritance,   | Triage Stage:  Accepted
  multi-table-inheritance|  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Reza Mohammadi ):

 `raw=True` doesn't always work. `raw` is used for two different purposes:

   The 'raw' argument is telling save_base not to save any parent models
 and
   not to do any changes to the values before save. This is used by fixture
 loading.

 For the purpose of this ticket, we want save_base ignore the first part
 but we need the second part to be done.

 I think `raw` argument should be split to two different arguments, as its
 functionality is already separated. Not as a workaround for this bug, but
 to make the code more readable.

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

Re: [Django] #7623: Multi-table inheritance does not allow linking new instance of child model to existing parent model instance.

[Django]

#7623: Multi-table inheritance does not allow linking new instance of child 
model
to existing parent model instance.
-+-
 Reporter:  brooks.travis@…  |Owner:
 Type:  Bug  |  elektrrrus
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  model-inheritance,   | Triage Stage:  Accepted
  multi-table-inheritance|  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Reza Mohammadi ):

 * cc: reza@… (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/081.d4b4093164eaf64da7c4f3a9489a5892%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21680: Stop supporting models in non-installed apps

[Django]

#21680: Stop supporting models in non-installed apps
--+
 Reporter:  aaugustin |Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  app-loading 1.9   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by aaugustin):

 * owner:  aaugustin =>
 * status:  assigned => new


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

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

[django/django] 8e1fc0: Fixed typo. Refs #21836.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8e1fc0349124d4a792e02bfd4c90576f9e3bda95
  
https://github.com/django/django/commit/8e1fc0349124d4a792e02bfd4c90576f9e3bda95
  Author: Aymeric Augustin 
  Date:   2014-01-26 (Sun, 26 Jan 2014)

  Changed paths:
M docs/topics/db/transactions.txt

  Log Message:
  ---
  Fixed typo. Refs #21836.


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

Re: [Django] #21836: clarify behavior of autocommit mode in presence of transaction

[Django]

#21836: clarify behavior of autocommit mode in presence of transaction
-+-
 Reporter:  cjerdonek|Owner:  aaugustin
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.6
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
  autocommit,transactions,database   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"a0a6112afc08c7471b70ee5e35170dfee3b488f3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a0a6112afc08c7471b70ee5e35170dfee3b488f3"
 [1.6.x] Fixed typo. Refs #21836.

 Backport of 8e1fc03 from master
 }}}

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

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

[django/django] a0a611: [1.6.x] Fixed typo. Refs #21836.

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: a0a6112afc08c7471b70ee5e35170dfee3b488f3
  
https://github.com/django/django/commit/a0a6112afc08c7471b70ee5e35170dfee3b488f3
  Author: Aymeric Augustin 
  Date:   2014-01-26 (Sun, 26 Jan 2014)

  Changed paths:
M docs/topics/db/transactions.txt

  Log Message:
  ---
  [1.6.x] Fixed typo. Refs #21836.

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

Re: [Django] #21874: Consistent handling for app modules with no (or empty) __path__

[Django]

#21874: Consistent handling for app modules with no (or empty) __path__
--+
 Reporter:  carljm|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  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 aaugustin):

 * stage:  Unreviewed => Accepted


Comment:

 Django has an explicity `django.template.loaders.eggs.Loader` to load
 templates from eggs, but nothing to load other files (static files,
 translations, etc.) So eggs don't work for loading files except for a
 specific case that requires explicit configuration of the template
 loaders. `app_config.path` will have a bogus value; live with it or
 upgrade to a more palatable package format ;-)

 I assume wheels don't matter here because they're expanded to regular
 files during installation (but I could be wrong).

 I agree with your proposal. I don't see any holes in the reasoning.

 As far as I know, only the AppConfigStub subclass of AppConfig has
 app_module set to None. This is a dumb class provided as a convenience for
 the migrations system. Simply adjust its `__init__` so that the tests pass
 -- it's an private API.

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

Re: [Django] #21680: Stop supporting models in non-installed apps

[Django]

#21680: Stop supporting models in non-installed apps
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Core (Other) |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  app-loading 1.9  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * has_patch:  1 => 0
 * severity:  Release blocker => Normal


Comment:

 This is still open, but postponed until the deprecation completes.

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