Re: [Django] #2443: Add IntervalField to database models

[Django]

#2443: Add IntervalField to database models
-+-
 Reporter:  ben.tucker@… |Owner:  Adys
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  IntervalField|  Needs documentation:  0
  interval duration DurationField|  Patch needs improvement:  1
  feature|UI/UX:  1
Has patch:  1|
  Needs tests:  1|
Easy pickings:  0|
-+-

Comment (by k_sze):

 I think this ticket is mostly moot now that there is django-
 timedeltafield, which works quite nicely. See links below:

 https://pypi.python.org/pypi/django-timedeltafield
 https://bitbucket.org/schinckel/django-timedelta-field/

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

Re: [Django] #21510: Admin change list search field is missing the "show all" link

[Django]

#21510: Admin change list search field is missing the "show all" link
-+-
 Reporter:  moritz.pfeiffer@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.6
 Severity:  Release blocker  |   Resolution:
 Keywords:  search field show| Triage Stage:  Accepted
  all missing link   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  1
Easy pickings:  0|
-+-
Changes (by timo):

 * has_patch:  0 => 1
 * needs_tests:  0 => 1


Comment:

 Attached is a patch that seems to fix the issue although I haven't run the
 tests or checked the code in a comprehensive fashion.

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

Re: [Django] #21515: template.Context Documentation: c.pop() and c.push() return nothing in the example

[Django]

#21515: template.Context Documentation: c.pop() and c.push() return nothing in 
the
example
+
 Reporter:  oubiga  |  Owner:  nobody
 Type:  Uncategorized   | Status:  closed
Component:  Documentation   |Version:  1.6
 Severity:  Normal  | Resolution:  fixed
 Keywords:  context, pop, push  |   Triage Stage:  Unreviewed
Has patch:  0   |  Easy pickings:  0
UI/UX:  0   |
+

Comment (by Baptiste Mispelon ):

 In [changeset:"0e98050847644f66c6aad38e359d560594a7a4cc"]:
 {{{
 #!CommitTicketReference repository=""
 revision="0e98050847644f66c6aad38e359d560594a7a4cc"
 [1.5.x] Fixed #21515 -- Corrected example of template.Context in
 documentation.

 Thanks to trac user oubiga for the report.

 Backport of 077af42139db84d88f293ab5eadc989a9169dce1 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/064.1a793fab741b758e9ea3ed3d67f69709%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 0e9805: [1.5.x] Fixed #21515 -- Corrected example of templ...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 0e98050847644f66c6aad38e359d560594a7a4cc
  
https://github.com/django/django/commit/0e98050847644f66c6aad38e359d560594a7a4cc
  Author: Baptiste Mispelon 
  Date:   2013-11-27 (Wed, 27 Nov 2013)

  Changed paths:
M docs/ref/templates/api.txt

  Log Message:
  ---
  [1.5.x] Fixed #21515 -- Corrected example of template.Context in 
documentation.

Thanks to trac user oubiga for the report.

Backport of 077af42139db84d88f293ab5eadc989a9169dce1 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/529687b8acfa_57c013afd5836134%40hookshot-fe6-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 02f9e9: [1.6.x] Fixed #21515 -- Corrected example of templ...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 02f9e90fdfe795992d674094fe25919bb885bf0d
  
https://github.com/django/django/commit/02f9e90fdfe795992d674094fe25919bb885bf0d
  Author: Baptiste Mispelon 
  Date:   2013-11-27 (Wed, 27 Nov 2013)

  Changed paths:
M docs/ref/templates/api.txt

  Log Message:
  ---
  [1.6.x] Fixed #21515 -- Corrected example of template.Context in 
documentation.

Thanks to trac user oubiga for the report.

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

Re: [Django] #21515: template.Context Documentation: c.pop() and c.push() return nothing in the example

[Django]

#21515: template.Context Documentation: c.pop() and c.push() return nothing in 
the
example
+
 Reporter:  oubiga  |  Owner:  nobody
 Type:  Uncategorized   | Status:  closed
Component:  Documentation   |Version:  1.6
 Severity:  Normal  | Resolution:  fixed
 Keywords:  context, pop, push  |   Triage Stage:  Unreviewed
Has patch:  0   |  Easy pickings:  0
UI/UX:  0   |
+

Comment (by Baptiste Mispelon ):

 In [changeset:"02f9e90fdfe795992d674094fe25919bb885bf0d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="02f9e90fdfe795992d674094fe25919bb885bf0d"
 [1.6.x] Fixed #21515 -- Corrected example of template.Context in
 documentation.

 Thanks to trac user oubiga for the report.

 Backport of 077af42139db84d88f293ab5eadc989a9169dce1 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/064.f61e060579a7e2fdbb770fe7f1af303c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 077af4: Fixed #21515 -- Corrected example of template.Cont...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 077af42139db84d88f293ab5eadc989a9169dce1
  
https://github.com/django/django/commit/077af42139db84d88f293ab5eadc989a9169dce1
  Author: Baptiste Mispelon 
  Date:   2013-11-27 (Wed, 27 Nov 2013)

  Changed paths:
M docs/ref/templates/api.txt

  Log Message:
  ---
  Fixed #21515 -- Corrected example of template.Context in documentation.

Thanks to trac user oubiga 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/5296871b8986d_385082dd5462880%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21515: template.Context Documentation: c.pop() and c.push() return nothing in the example

[Django]

#21515: template.Context Documentation: c.pop() and c.push() return nothing in 
the
example
+
 Reporter:  oubiga  |  Owner:  nobody
 Type:  Uncategorized   | Status:  closed
Component:  Documentation   |Version:  1.6
 Severity:  Normal  | Resolution:  fixed
 Keywords:  context, pop, push  |   Triage Stage:  Unreviewed
Has patch:  0   |  Easy pickings:  0
UI/UX:  0   |
+
Changes (by Baptiste Mispelon ):

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


Comment:

 In [changeset:"077af42139db84d88f293ab5eadc989a9169dce1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="077af42139db84d88f293ab5eadc989a9169dce1"
 Fixed #21515 -- Corrected example of template.Context in documentation.

 Thanks to trac user oubiga 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/064.304dd72ed37aed695e85f9e3b0f4b957%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] a5b94d: A handle of flake8 fixes

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a5b94d9d4ea7f85f687520d0d5475fbb846c
  
https://github.com/django/django/commit/a5b94d9d4ea7f85f687520d0d5475fbb846c
  Author: Alex Gaynor 
  Date:   2013-11-27 (Wed, 27 Nov 2013)

  Changed paths:
M django/contrib/gis/db/backends/postgis/schema.py
M django/contrib/gis/db/models/fields.py

  Log Message:
  ---
  A handle of flake8 fixes


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

Re: [Django] #21518: override_settings(ROOT_URLCONF) doesn't clear resolver cache

[Django]

#21518: override_settings(ROOT_URLCONF) doesn't clear resolver cache
-+
 Reporter:  gcc  |Owner:  gcc
 Type:  Bug  |   Status:  new
Component:  Core (URLs)  |  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by gcc):

 * needs_better_patch:  1 => 0


Comment:

 Modified the PR branch as requested by @aaugustin.

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

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

[django/django] df6760: Added a warning regarding risks in serving user up...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: df6760f12c2f08287e2aa7b5ddee6e567ab83220
  
https://github.com/django/django/commit/df6760f12c2f08287e2aa7b5ddee6e567ab83220
  Author: Tim Graham 
  Date:   2013-11-27 (Wed, 27 Nov 2013)

  Changed paths:
M docs/ref/settings.txt
M docs/topics/http/file-uploads.txt
M docs/topics/security.txt

  Log Message:
  ---
  Added a warning regarding risks in serving user uploaded media.

Thanks Preston Holmes for the draft text.


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

[Django] #21519: django.db.models: get_apps() includes abstract models, get_models() excludes them

[Django]

#21519: django.db.models: get_apps() includes abstract models, get_models()
excludes them
--+
 Reporter:  Kanuck54  |  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 (I'm uncertain how much of this report is bug vs. new feature; I went with
 the latter for now.)

 From the `BaseAppCache` class in
 [https://github.com/django/django/blob/master/django/db/models/loading.py
 django.db.models.loading]:

 {{{
 def get_apps(self):
 """
 Returns a list of all installed modules that contain models.
 """
 }}}

 When `get_apps()` says "all installed modules that contain models", it
 really means it: the returned list includes modules containing only
 abstract base class models.

 {{{
 def get_models(self, app_mod=None,
include_auto_created=False, include_deferred=False,
only_installed=True, include_swapped=False):
 """
 Given a module containing models, returns a list of the models.
 Otherwise returns a list of all installed models.

 ...
 """
 }}}

 `get_models()` doesn't give any indication that it should work any
 differently; yet it ignores abstract base class models, returning a list
 of concrete models only.

 This inconsistency is very counter-intuitive:

 {{{
 >>> from django.db import models
 >>> [{app: models.get_models(app)} for app in models.get_apps()]
 [{: []},
  {: [,
   ,
   ]},
  {: []},
  {: []},
  {: []},
  {: []},
  {: []},
  {: []}]
 }}}

 `get_apps()` says an app contains models, but passing that app to
 `get_models()` returns an empty list.

 The docs indicate that yes,
 [https://docs.djangoproject.com/en/dev/ref/models/options/#abstract an
 abstract base class is a model]; so I think `get_models()` should return
 them, or at least should be ''able'' to return them with an
 `include_abstract=True` argument.

 (The use case is `graph_models` in `django_extensions`, which outputs a
 [http://www.graphviz.org/ Graphviz] digraph of the models in an
 application or project. Currently it's forced to walk up the model tree to
 find abstract base classes, leading to some unexpected behaviours that
 would be much easier to resolve without this Django quirk.)

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

Re: [Django] #21518: override_settings(ROOT_URLCONF) doesn't clear resolver cache

[Django]

#21518: override_settings(ROOT_URLCONF) doesn't clear resolver cache
-+
 Reporter:  gcc  |Owner:  gcc
 Type:  Bug  |   Status:  new
Component:  Core (URLs)  |  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by aaugustin):

 * needs_better_patch:  0 => 1
 * easy:  1 => 0
 * stage:  Unreviewed => Accepted


Comment:

 The idea is sane, see comment on the PR.

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

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

Re: [Django] #10852: Add no-fuzzy-matching option to makemessages

[Django]

#10852: Add no-fuzzy-matching option to makemessages
-+-
 Reporter:  graham.carlyle@… |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:   |  Version:  master
  Internationalization   |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by acdha):

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

Re: [Django] #21518: override_settings(ROOT_URLCONF) doesn't clear resolver cache

[Django]

#21518: override_settings(ROOT_URLCONF) doesn't clear resolver cache
-+--
 Reporter:  gcc  |Owner:  gcc
 Type:  Bug  |   Status:  new
Component:  Core (URLs)  |  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+--
Changes (by gcc):

 * needs_better_patch:   => 0
 * type:  Uncategorized => Bug
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Pull request is at: https://github.com/django/django/pull/2001

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

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

[Django] #21518: override_settings(ROOT_URLCONF) doesn't clear resolver cache

[Django]

#21518: override_settings(ROOT_URLCONF) doesn't clear resolver cache
---+-
 Reporter:  gcc|  Owner:  gcc
 Type:  Uncategorized  | Status:  new
Component:  Core (URLs)|Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  1  |  UI/UX:  0
---+-
 If override_settings is used to set different URL mappings on different
 tests, by setting ROOT_URLCONF to different values, it doesn't work
 properly because the resolver cache is never cleared.

 You might argue that this behaviour is unnecessary or broken, but Django-
 CMS for example [http://docs.django-
 cms.org/en/2.4.2/extending_cms/testing.html recommends that you do]:

 Your apps need testing, but in your live site they aren’t in urls.py
 as they are attached to a CMS page. So if you want to be able to use
 reverse() in your tests, or test templates that use the url template tag,
 you need to hook up your app to a special test version of urls.py and tell
 your tests to use that... in your tests you can plug this in with the
 override_settings() decorator.

 A simple test case that fails:

 {{{#!python
 class FirstUrls:
 urlpatterns = patterns('', url(r'first/$', fake_view, name='first'))

 class SecondUrls:
 urlpatterns = patterns('', url(r'second/$', fake_view, name='second'))

 class OverrideSettingsTests(TestCase):
 """
 If neither override_settings nor a settings_changed receiver clears
 the
 URL cache between tests, then one of these two test methods will fail.
 """

 @override_settings(ROOT_URLCONF=FirstUrls)
 def test_first(self):
 reverse('first')

 @override_settings(ROOT_URLCONF=SecondUrls)
 def test_second(self):
 reverse('second')
 }}}

 In order for this to work, I think the best approach is to add another
 listener for the `settings_changed` signal in `django/test/signals.py`,
 which detects when the `ROOT_URLCONF` setting is changed and clears the
 LRU caches in `django.core.urlresolvers`.

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

Re: [Django] #15053: Make templates more reusable by Improving template loading algorithm to avoid extending infinite recursion

[Django]

#15053: Make templates more reusable by Improving template loading algorithm to
avoid extending infinite recursion
-+
 Reporter:  pmartin  |Owner:  unaizalakain
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by unaizalakain):

 I've recently been aware of some changes that could improve the API
 clearness so
 I made an other commit on top of the last one (I'll squash them before
 issuing
 the PR):

 - Global template source loader loader is now outside of `find_template`
  making it easier to reuse it.

 - The cache loader needs to be able to specify the loaders to try in
  `find_template`. So we appended just an other parameter to
 `find_template`
  making them to: `skip_template` and `loaders`.

  I noticed that the only thing that `skip_template` is useful for is for
  skipping loaders. So we could squash those two parameters into a single
 one:
  `loaders`. If that parameter isn't given the global loaders are loaded.

  The loader skipping could be done outside `find_template`: in
  `get_template` so this last function is the one that now gets the
 template
  to skip.

 - I've also added the `skip_template` parameter to the `select_template`
  function for the cohesion.

 - Docs has been updated (only documented functions are `get_template` and
  `skip_template`.

 @goinnn As a consequence of all this changes, you must first filter the
 cached
 loaders through `skip_loaders` and then pass them to `find_template`. This
 is an extra line of code but I think it enhances clarity. Before I forget
 it,
 we must update the docs that refer to loaders and tell about the new
 `never_skip` and `use_skip_template` attributes (I'd be glad to help with
 that if needed).

 Currently, the cache test fails (that's good), check that that they pass
 correctly after your commit.

 Let me know about any pitfall I made or any suggestion you have ;-)

 I think the solution to this rather big issue is evolving correctly, we
 should
 be able to issue a PR and address the django-dev mailing list asking for
 comments in a short period of time.

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

[django/django] ecd855: Fixed typo in release notes.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ecd855658960d32efeb9cd97cad1ed076520e696
  
https://github.com/django/django/commit/ecd855658960d32efeb9cd97cad1ed076520e696
  Author: Loic Bistuer 
  Date:   2013-11-27 (Wed, 27 Nov 2013)

  Changed paths:
M docs/releases/1.7.txt

  Log Message:
  ---
  Fixed typo in release notes.


  Commit: 041a076dadce547d450cf73d97401d63cde8891d
  
https://github.com/django/django/commit/041a076dadce547d450cf73d97401d63cde8891d
  Author: Anssi Kääriäinen 
  Date:   2013-11-27 (Wed, 27 Nov 2013)

  Changed paths:
M docs/releases/1.7.txt

  Log Message:
  ---
  Merge pull request #2000 from loic/docs

Fixed typo in release notes.


Compare: https://github.com/django/django/compare/01e8ac47b37c...041a076dadce

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

Re: [Django] #3871: Use custom managers in reverse relations

[Django]

#3871: Use custom managers in reverse relations
-+-
 Reporter:  EspenG   |Owner:  v1v3kn
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | 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
-+-

Comment (by Anssi Kääriäinen ):

 In [changeset:"17c3997f6828e88e4646071a8187c1318b65597d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="17c3997f6828e88e4646071a8187c1318b65597d"
 Fixed #21169 -- Reworked RelatedManager methods use default filtering

 The `remove()` and `clear()` methods of the related managers created by
 `ForeignKey`, `GenericForeignKey`, and `ManyToManyField` suffered from a
 number of issues. Some operations ran multiple data modifying queries
 without
 wrapping them in a transaction, and some operations didn't respect default
 filtering when it was present (i.e. when the default manager on the
 related
 model implemented a custom `get_queryset()`).

 Fixing the issues introduced some backward incompatible changes:

 - The implementation of `remove()` for `ForeignKey` related managers
 changed
   from a series of `Model.save()` calls to a single `QuerySet.update()`
 call.
   The change means that `pre_save` and `post_save` signals aren't called
 anymore.

 - The `remove()` and `clear()` methods for `GenericForeignKey` related
   managers now perform bulk delete so `Model.delete()` isn't called
 anymore.

 - The `remove()` and `clear()` methods for `ManyToManyField` related
   managers perform nested queries when filtering is involved, which may
   or may not be an issue depending on the database and the data itself.

 Refs. #3871, #21174.

 Thanks Anssi Kääriäinen and Tim Graham for the reviews.
 }}}

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

[django/django] 17c399: Fixed #21169 -- Reworked RelatedManager methods us...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 17c3997f6828e88e4646071a8187c1318b65597d
  
https://github.com/django/django/commit/17c3997f6828e88e4646071a8187c1318b65597d
  Author: Loic Bistuer 
  Date:   2013-11-27 (Wed, 27 Nov 2013)

  Changed paths:
M django/db/models/fields/related.py
M docs/ref/models/querysets.txt
M docs/releases/1.7.txt
M tests/custom_managers/models.py
M tests/custom_managers/tests.py

  Log Message:
  ---
  Fixed #21169 -- Reworked RelatedManager methods use default filtering

The `remove()` and `clear()` methods of the related managers created by
`ForeignKey`, `GenericForeignKey`, and `ManyToManyField` suffered from a
number of issues. Some operations ran multiple data modifying queries without
wrapping them in a transaction, and some operations didn't respect default
filtering when it was present (i.e. when the default manager on the related
model implemented a custom `get_queryset()`).

Fixing the issues introduced some backward incompatible changes:

- The implementation of `remove()` for `ForeignKey` related managers changed
  from a series of `Model.save()` calls to a single `QuerySet.update()` call.
  The change means that `pre_save` and `post_save` signals aren't called 
anymore.

- The `remove()` and `clear()` methods for `GenericForeignKey` related
  managers now perform bulk delete so `Model.delete()` isn't called anymore.

- The `remove()` and `clear()` methods for `ManyToManyField` related
  managers perform nested queries when filtering is involved, which may
  or may not be an issue depending on the database and the data itself.

Refs. #3871, #21174.

Thanks Anssi Kääriäinen and Tim Graham for the reviews.


  Commit: 52015b963d263642957aec880b52ad4063b484cd
  
https://github.com/django/django/commit/52015b963d263642957aec880b52ad4063b484cd
  Author: Anssi Kääriäinen 
  Date:   2013-11-27 (Wed, 27 Nov 2013)

  Changed paths:
M django/db/models/fields/related.py
M django/db/models/query.py
M django/db/models/sql/query.py

  Log Message:
  ---
  Used simpler queries for m2m clearing when possible.

Refs #21169


  Commit: f450bc9f44bc1270eae911daa157c155c29d1d9d
  
https://github.com/django/django/commit/f450bc9f44bc1270eae911daa157c155c29d1d9d
  Author: Loic Bistuer 
  Date:   2013-11-27 (Wed, 27 Nov 2013)

  Changed paths:
M django/contrib/contenttypes/generic.py
M django/db/models/fields/related.py
M django/db/models/query.py
M docs/ref/models/relations.txt
M docs/releases/1.7.txt
M tests/custom_managers/tests.py

  Log Message:
  ---
  Added a bulk option to RelatedManager remove() and clear() methods

Refs #21169


  Commit: 01e8ac47b37ccf1b4d9b9710ae2d9b6b486c3c7a
  
https://github.com/django/django/commit/01e8ac47b37ccf1b4d9b9710ae2d9b6b486c3c7a
  Author: Anssi Kääriäinen 
  Date:   2013-11-27 (Wed, 27 Nov 2013)

  Changed paths:
M tests/custom_managers/models.py
M tests/custom_managers/tests.py

  Log Message:
  ---
  PEP-8 cleanup

Refs #21169


Compare: https://github.com/django/django/compare/0b3c8fc85168...01e8ac47b37c

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

Re: [Django] #21169: Deletion in custom reverse managers

[Django]

#21169: Deletion in custom reverse managers
-+-
 Reporter:  sebastian|Owner:  loic84
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Release blocker  | 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 Anssi Kääriäinen ):

 In [changeset:"01e8ac47b37ccf1b4d9b9710ae2d9b6b486c3c7a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="01e8ac47b37ccf1b4d9b9710ae2d9b6b486c3c7a"
 PEP-8 cleanup

 Refs #21169
 }}}

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

Re: [Django] #21169: Deletion in custom reverse managers

[Django]

#21169: Deletion in custom reverse managers
-+-
 Reporter:  sebastian|Owner:  loic84
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Release blocker  | 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 Anssi Kääriäinen ):

 In [changeset:"52015b963d263642957aec880b52ad4063b484cd"]:
 {{{
 #!CommitTicketReference repository=""
 revision="52015b963d263642957aec880b52ad4063b484cd"
 Used simpler queries for m2m clearing when possible.

 Refs #21169
 }}}

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

Re: [Django] #21169: Deletion in custom reverse managers

[Django]

#21169: Deletion in custom reverse managers
-+-
 Reporter:  sebastian|Owner:  loic84
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Release blocker  | 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 Anssi Kääriäinen ):

 In [changeset:"f450bc9f44bc1270eae911daa157c155c29d1d9d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f450bc9f44bc1270eae911daa157c155c29d1d9d"
 Added a bulk option to RelatedManager remove() and clear() methods

 Refs #21169
 }}}

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

Re: [Django] #21174: Transaction handling broken in related manager modification methods

[Django]

#21174: Transaction handling broken in related manager modification methods
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |  1.6-beta-1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Anssi Kääriäinen ):

 In [changeset:"17c3997f6828e88e4646071a8187c1318b65597d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="17c3997f6828e88e4646071a8187c1318b65597d"
 Fixed #21169 -- Reworked RelatedManager methods use default filtering

 The `remove()` and `clear()` methods of the related managers created by
 `ForeignKey`, `GenericForeignKey`, and `ManyToManyField` suffered from a
 number of issues. Some operations ran multiple data modifying queries
 without
 wrapping them in a transaction, and some operations didn't respect default
 filtering when it was present (i.e. when the default manager on the
 related
 model implemented a custom `get_queryset()`).

 Fixing the issues introduced some backward incompatible changes:

 - The implementation of `remove()` for `ForeignKey` related managers
 changed
   from a series of `Model.save()` calls to a single `QuerySet.update()`
 call.
   The change means that `pre_save` and `post_save` signals aren't called
 anymore.

 - The `remove()` and `clear()` methods for `GenericForeignKey` related
   managers now perform bulk delete so `Model.delete()` isn't called
 anymore.

 - The `remove()` and `clear()` methods for `ManyToManyField` related
   managers perform nested queries when filtering is involved, which may
   or may not be an issue depending on the database and the data itself.

 Refs. #3871, #21174.

 Thanks Anssi Kääriäinen and Tim Graham for the reviews.
 }}}

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

Re: [Django] #21169: Deletion in custom reverse managers

[Django]

#21169: Deletion in custom reverse managers
-+-
 Reporter:  sebastian|Owner:  loic84
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Anssi Kääriäinen ):

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


Comment:

 In [changeset:"17c3997f6828e88e4646071a8187c1318b65597d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="17c3997f6828e88e4646071a8187c1318b65597d"
 Fixed #21169 -- Reworked RelatedManager methods use default filtering

 The `remove()` and `clear()` methods of the related managers created by
 `ForeignKey`, `GenericForeignKey`, and `ManyToManyField` suffered from a
 number of issues. Some operations ran multiple data modifying queries
 without
 wrapping them in a transaction, and some operations didn't respect default
 filtering when it was present (i.e. when the default manager on the
 related
 model implemented a custom `get_queryset()`).

 Fixing the issues introduced some backward incompatible changes:

 - The implementation of `remove()` for `ForeignKey` related managers
 changed
   from a series of `Model.save()` calls to a single `QuerySet.update()`
 call.
   The change means that `pre_save` and `post_save` signals aren't called
 anymore.

 - The `remove()` and `clear()` methods for `GenericForeignKey` related
   managers now perform bulk delete so `Model.delete()` isn't called
 anymore.

 - The `remove()` and `clear()` methods for `ManyToManyField` related
   managers perform nested queries when filtering is involved, which may
   or may not be an issue depending on the database and the data itself.

 Refs. #3871, #21174.

 Thanks Anssi Kääriäinen and Tim Graham for the reviews.
 }}}

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

Re: [Django] #11407: --version weirdness

[Django]

#11407: --version weirdness
-+-
 Reporter:  kmtracey |Owner:
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  management django-   |  Needs documentation:  0
  admin.py manage.py |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by Siecje):

 * keywords:   => management django-admin.py manage.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.296bf91241dfabf6ec275c78a7ea8612%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 67b51b: Include deferred SQL in sqlmigrate output

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 67b51b98959025c7a5e928f640488e230efde82e
  
https://github.com/django/django/commit/67b51b98959025c7a5e928f640488e230efde82e
  Author: Andrew Godwin 
  Date:   2013-11-27 (Wed, 27 Nov 2013)

  Changed paths:
M django/db/migrations/executor.py

  Log Message:
  ---
  Include deferred SQL in sqlmigrate output


  Commit: 0b3c8fc85168bac7327e7c4372e92b52575547e9
  
https://github.com/django/django/commit/0b3c8fc85168bac7327e7c4372e92b52575547e9
  Author: Andrew Godwin 
  Date:   2013-11-27 (Wed, 27 Nov 2013)

  Changed paths:
M docs/intro/tutorial01.txt

  Log Message:
  ---
  Update tutorial part 1 to discuss migrations properly


Compare: https://github.com/django/django/compare/5e63977c0e5d...0b3c8fc85168

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

Re: [Django] #17713: allows_primary_key_0 is misnamed

[Django]

#17713: allows_primary_key_0 is misnamed
-+-
 Reporter:  claudep  |Owner:  nobody
 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 vajrasky):

 @timo: or we can add another attribute (allows_auto_pk_0) and keep this
 one (allows_primary_key_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/065.6d4cd05b9ecfe3f157eca98cd9baa4a1%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 19b34f: Field.deconstruct() howto docs

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 19b34fbe63a8ec5edd61777b7ff681370cff14f2
  
https://github.com/django/django/commit/19b34fbe63a8ec5edd61777b7ff681370cff14f2
  Author: Andrew Godwin 
  Date:   2013-11-27 (Wed, 27 Nov 2013)

  Changed paths:
M docs/howto/custom-model-fields.txt

  Log Message:
  ---
  Field.deconstruct() howto docs


  Commit: 5e63977c0e5d0dff755817b86364a5c8882deaf7
  
https://github.com/django/django/commit/5e63977c0e5d0dff755817b86364a5c8882deaf7
  Author: Andrew Godwin 
  Date:   2013-11-27 (Wed, 27 Nov 2013)

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

  Log Message:
  ---
  Fixed #21438: makemigrations now detects ManyToManyFields


Compare: https://github.com/django/django/compare/eece3c224e00...5e63977c0e5d

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

Re: [Django] #21438: Migrations do not detect many to many fields

[Django]

#21438: Migrations do not detect many to many fields
-+-
 Reporter:  zaharid@…|Owner:
 Type:  Bug  |  andrewgodwin
Component:  Migrations   |   Status:  closed
 Severity:  Normal   |  Version:  master
 Keywords:  manytomany   |   Resolution:  fixed
  foreignkey | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Andrew Godwin ):

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


Comment:

 In [changeset:"5e63977c0e5d0dff755817b86364a5c8882deaf7"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5e63977c0e5d0dff755817b86364a5c8882deaf7"
 Fixed #21438: makemigrations now detects ManyToManyFields
 }}}

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

Re: [Django] #17713: allows_primary_key_0 is misnamed

[Django]

#17713: allows_primary_key_0 is misnamed
-+-
 Reporter:  claudep  |Owner:  nobody
 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 vajrasky):

 This is the separate ticket for adding unit test exercising the capability
 of having zero non-autoincrement primary key, #21517.

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

Re: [Django] #21517: Add unit test for non-autoincrement primary key with value 0 (zero)

[Django]

#21517: Add unit test for non-autoincrement primary key with value 0 (zero)
-+-
 Reporter:  vajrasky |Owner:  vajrasky
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Uncategorized|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by vajrasky):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * owner:  nobody => vajrasky
 * needs_docs:   => 0
 * has_patch:  0 => 1


Comment:

 This is the PR: https://github.com/django/django/pull/1999

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

[Django] #21517: Add unit test for non-autoincrement primary key with value 0 (zero)

[Django]

#21517: Add unit test for non-autoincrement primary key with value 0 (zero)
--+
 Reporter:  vajrasky  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Uncategorized |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 This ticket is related with ticket #17713.

 MySQL has the capability to use primary key with value 0 but only if the
 primary key is non-autoincrement. So this unit test exercises that
 capability.

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

[django/django] db4527: Fix squashed migration loading ordering issue

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: db4527e3c0486c46356e3d625931369e8b3bec19
  
https://github.com/django/django/commit/db4527e3c0486c46356e3d625931369e8b3bec19
  Author: Andrew Godwin 
  Date:   2013-11-27 (Wed, 27 Nov 2013)

  Changed paths:
M django/db/migrations/loader.py

  Log Message:
  ---
  Fix squashed migration loading ordering issue


  Commit: 96dd48c83f429688629b866f8fc64e1a4f3249f3
  
https://github.com/django/django/commit/96dd48c83f429688629b866f8fc64e1a4f3249f3
  Author: Andrew Godwin 
  Date:   2013-11-27 (Wed, 27 Nov 2013)

  Changed paths:
A django/conf/app_template/migrations/__init__.py
M django/db/migrations/autodetector.py

  Log Message:
  ---
  Change initial migration writing to work as docs suggest.

Application template now includes an empty migrations module, and
the autodetector will only make initial migrations for apps with
empty modules.


  Commit: 4fcfc31865240d635c6e13e1f71ed52c0f6bd72c
  
https://github.com/django/django/commit/4fcfc31865240d635c6e13e1f71ed52c0f6bd72c
  Author: Andrew Godwin 
  Date:   2013-11-27 (Wed, 27 Nov 2013)

  Changed paths:
M django/contrib/gis/db/models/fields.py
M django/db/backends/schema.py

  Log Message:
  ---
  Add gis deconstruct() method (this does not make schema work)


  Commit: eece3c224e0019a30aa491a44ef66193d93f7ce8
  
https://github.com/django/django/commit/eece3c224e0019a30aa491a44ef66193d93f7ce8
  Author: Andrew Godwin 
  Date:   2013-11-27 (Wed, 27 Nov 2013)

  Changed paths:
M django/contrib/gis/db/backends/postgis/base.py
A django/contrib/gis/db/backends/postgis/schema.py

  Log Message:
  ---
  PostGIS schema editor support


Compare: https://github.com/django/django/compare/0c46ca83e820...eece3c224e00

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

Re: [Django] #21142: Cannot run migrations that reference django.contrib.auth.models.User

[Django]

#21142: Cannot run migrations that reference django.contrib.auth.models.User
-+
 Reporter:  mario.pfeifer@…  |Owner:
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  Migration, Auth  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by robin):

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

Re: [Django] #21514: Session expiry dates should be in an ISO string instead of datetime

[Django]

#21514: Session expiry dates should be in an ISO string instead of datetime
--+--
 Reporter:  n142857@… |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.sessions  |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by anonymous):

 You're right. it's django-social-auth (views.py, function
 complete_process) who sets an expiry date. (For future readers who use
 Django 1.6 and cannot log in through Facebook: use
 `SOCIAL_AUTH_SESSION_EXPIRATION=False`).

 But django-social-auth does the right thing in passing a datetime, because
 it cannot do otherwise: passing a string to `set_expiry` is not documented
 (it's also not as easy as passing a date). So I think set_expiry should
 accept datetime (as it does now) and convert to string when storing.
 At least, issue a warning/error in set_expiry if
 `SESSION_SERIALIZER`=JsonSerializer.

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