Re: [Django] #20807: Inline don't care about max_num if has_add_permission is set to false

[Django]

#20807: Inline don't care about max_num if has_add_permission is set to false
--+
 Reporter:  yves.guimard@…|Owner:  polmuz
 Type:  Bug   |   Status:  closed
Component:  contrib.admin |  Version:  1.5
 Severity:  Normal|   Resolution:  fixed
 Keywords:  admin inline max_num  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by yves.guimard@…):

 Great, thanks for the fix!

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

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

Re: [Django] #21053: Missing related fields

[Django]

#21053: Missing related fields
-+-
 Reporter:  joshua.fialkoff@…|Owner:  grue
 Type:  Uncategorized|   Status:  assigned
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by grue):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * owner:  nobody => grue
 * 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/085.6ae990514274a70dfa6c862f4b4e6e39%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21043: resolve doesn't handle lazily evaluated reverses

[Django]

#21043: resolve doesn't handle lazily evaluated reverses
-+-
 Reporter:  Keryn Knight |Owner:
   |   Status:  closed
 Type:  Bug  |  Version:  master
Component:  Core (URLs)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  urlresolvers |  Needs documentation:  0
  resolve reverse|  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-

Comment (by grue):

 This has been closed as per
 
https://github.com/django/django/commit/df462cf7604578c2afd43b988b7ea1fe5e727896

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

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

Re: [Django] #21043: resolve doesn't handle lazily evaluated reverses

[Django]

#21043: resolve doesn't handle lazily evaluated reverses
-+-
 Reporter:  Keryn Knight |Owner:
   |   Status:  closed
 Type:  Bug  |  Version:  master
Component:  Core (URLs)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  urlresolvers |  Needs documentation:  0
  resolve reverse|  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by grue):

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


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

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

Re: [Django] #21062: Transition to Generic Views Reference to Changing Poll_ID to PK, Yet No change is visible

[Django]

#21062: Transition to Generic Views Reference to Changing Poll_ID to PK, Yet No
change is visible
-+-
 Reporter:  john@…   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.6-beta-1
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by john@…):

 * status:  new => closed
 * severity:  Release blocker => Normal
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0
 * resolution:   => invalid


Comment:

 Figured out where the poll_id is defined, and realized that it HAD
 changed.  So deleting the ticket.

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

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

[Django] #21062: Transition to Generic Views Reference to Changing Poll_ID to PK, Yet No change is visible

[Django]

#21062: Transition to Generic Views Reference to Changing Poll_ID to PK, Yet No
change is visible
--+
 Reporter:  john@…|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.6-beta-1
 Severity:  Release blocker   |   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 [https://docs.djangoproject.com/en/dev/intro/tutorial04/]

 On the above page, near the bottom, there's a bullet point which reads:

 {{{
 * The DetailView generic view expects the primary key value captured from
 the URL to be called "pk", so we’ve changed poll_id to pk for the generic
 views.
 }}}

 I may be missing the reference to this change, but have yet to discover
 it.

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

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

[django/django] 253073: Fixed a number of flake8 errors -- particularly ar...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2530735d2d57316d1df8177745e93a78de663ff7
  
https://github.com/django/django/commit/2530735d2d57316d1df8177745e93a78de663ff7
  Author: Alex Gaynor 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M django/contrib/auth/middleware.py
M django/contrib/auth/models.py
M django/contrib/gis/forms/fields.py
M django/contrib/sessions/tests.py
M django/core/cache/__init__.py
M django/core/management/commands/loaddata.py
M django/core/management/sql.py
M django/db/backends/oracle/schema.py
M django/db/backends/schema.py
M django/forms/formsets.py
M django/template/defaulttags.py
M django/test/client.py
M django/utils/html.py

  Log Message:
  ---
  Fixed a number of flake8 errors -- particularly around unused imports and 
local variables


  Commit: 97a626d898575fc8925700a6db7d43cf3099898e
  
https://github.com/django/django/commit/97a626d898575fc8925700a6db7d43cf3099898e
  Author: Alex Gaynor 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M tests/backends/tests.py

  Log Message:
  ---
  Fixed this syntax error on py32


Compare: https://github.com/django/django/compare/a9589dd280ba...97a626d89857

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

[Django] #21061: is_safe filter flag

[Django]

#21061: is_safe filter flag
-+
 Reporter:  justincapella@…  |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Template system  |Version:  1.5
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 From django/template/base.py:resolve

 [code]
 if getattr(func, 'is_safe', False) and isinstance(obj,
 SafeData):
 obj = mark_safe(new_obj)
 [/code]

 The isinstance(obj, SafeData) seems to prevent is_safe flag from having
 any affect on the output.
 Thinking of the use cases we have some function/tag that we want to either
 have mark_safe called on, or not called on.

 imo, this should just be

 [code]
 if getattr(func, 'is_safe', False):
 obj = mark_safe(new_obj)
 [/code]


 This allows is_safe to have an effect on the outcome... which the current
 code does not.

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

Re: [Django] #21032: pip 1.4 and pytz break installation of test requirements

[Django]

#21032: pip 1.4 and pytz break installation of test requirements
---+--
 Reporter:  marfire|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Testing framework  |  Version:  master
 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
---+--
Changes (by aaugustin):

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


Comment:

 On the other hand, it's simple enough to change the requirements files so
 it actually works with the current version of pip.

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

Re: [Django] #21032: pip 1.4 and pytz break installation of test requirements

[Django]

#21032: pip 1.4 and pytz break installation of test requirements
---+--
 Reporter:  marfire|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"a9589dd280ba84db3131f32b423ef45c67a5a236"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a9589dd280ba84db3131f32b423ef45c67a5a236"
 Fixed #21032 -- pip 1.4 can't install pytz.
 }}}

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

[django/django] a9589d: Fixed #21032 -- pip 1.4 can't install pytz.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a9589dd280ba84db3131f32b423ef45c67a5a236
  
https://github.com/django/django/commit/a9589dd280ba84db3131f32b423ef45c67a5a236
  Author: Aymeric Augustin 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M tests/requirements/base.txt

  Log Message:
  ---
  Fixed #21032 -- pip 1.4 can't install pytz.



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

Re: [Django] #16502: CreateView useless error message when template_name is not specified

[Django]

#16502: CreateView useless error message when template_name is not specified
-+-
 Reporter:  silverghost3@…   |Owner:
 Type:  Bug  |  ianawilson
Component:  Generic views|   Status:  new
 Severity:  Normal   |  Version:  master
 Keywords:  CreateView "generic  |   Resolution:
  view"  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by bhuztez):

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


Comment:

 > determining the model based off a form specified in `form_class` is not
 desirable, because this assumes the form is a ModelForm, which may not be
 the case.

 `CreateView` inherits `ModelFormMixin`. This already assumes form is a
 ModelForm.

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

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

Re: [Django] #20522: Admin formset validation cannot take submitted model instance into account when form not valid.

[Django]

#20522: Admin formset validation cannot take submitted model instance into 
account
when form not valid.
-+-
 Reporter:  meshy|Owner:  kamni
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  admin formset| Triage Stage:  Accepted
  validation |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by kamni):

 Please disregard the screenshot, as there was a mistake in the setup.

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

Re: [Django] #11811: No error raised on update(foreignkey=unsavedobject) on nullable fk

[Django]

#11811: No error raised on update(foreignkey=unsavedobject) on nullable fk
-+-
 Reporter:  Afief|Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.1
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"f855058c35db9d35ba7f310d8f9db6f4533b7424"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f855058c35db9d35ba7f310d8f9db6f4533b7424"
 [1.6.x] Fixed #11811 -- Data-loss bug in queryset.update.

 It's now forbidden to call queryset.update(field=instance) when instance
 hasn't been saved to the database ie. instance.pk is None.

 Conflicts:
 tests/queries/tests.py

 Backport of b4cd8169 from master.
 }}}

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

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

[django/django] f85505: [1.6.x] Fixed #11811 -- Data-loss bug in queryset....

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: f855058c35db9d35ba7f310d8f9db6f4533b7424
  
https://github.com/django/django/commit/f855058c35db9d35ba7f310d8f9db6f4533b7424
  Author: Aymeric Augustin 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M django/db/models/base.py
M tests/queries/models.py
M tests/queries/tests.py

  Log Message:
  ---
  [1.6.x] Fixed #11811 -- Data-loss bug in queryset.update.

It's now forbidden to call queryset.update(field=instance) when instance
hasn't been saved to the database ie. instance.pk is None.

Conflicts:
tests/queries/tests.py

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

Re: [Django] #20558: Add `response_delete` and `render_delete_form` methods to `ModelAdmin`

[Django]

#20558: Add `response_delete` and `render_delete_form` methods to  `ModelAdmin`
---+
 Reporter:  anonymous  |Owner:  polmuz
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by polmuz):

 * cc: polmuz (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/067.49e2be4168fd7f043ad2a20c771771bc%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #4287: FloatField will not handle infinity values

[Django]

#4287: FloatField will not handle infinity values
-+-
 Reporter:  oBeattie (oliver@…   |Owner:  dlanger
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  nan, infinity,   |  Needs documentation:  0
  mysql, float   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-

Comment (by dlanger):

 https://github.com/django/django/pull/1559 passes on 2.7 with sqlite and
 MySQL.

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

Re: [Django] #20917: Change the password hashers when testing

[Django]

#20917: Change the password hashers when testing
-+-
 Reporter:  mjtamlyn |Owner:
 Type:  New feature  |  ashchristopher
Component:  Testing framework|   Status:  assigned
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by ashchristopher):

 I was thinking of adding a `TEST_PASSWORD_HASHER` to the settings which by
 default is set to None. If `TEST_PASSWORD_HASHER` is None, then we don't
 override the `PASSWORD_HASHER` tuple and password hashing works as normal.

 This would allow backwards compatibility.

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

Re: [Django] #20970: Related fields docs improvements

[Django]

#20970: Related fields docs improvements
-+-
 Reporter:  akaariai |Owner:
 Type:   |  technivore
  Cleanup/optimization   |   Status:  new
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  afraid-to-commit | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by aaugustin):

 * status:  closed => new
 * has_patch:  0 => 1
 * resolution:  fixed =>


Comment:

 Please don't mark tickets as fixed until a fix is actually merged in the
 master branch; use the "has patch" flag instead. Thank you!

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

Re: [Django] #20975: Fix incorrect markup of committers list (and possibly other docs lists)

[Django]

#20975: Fix incorrect markup of committers list (and possibly other docs lists)
--+
 Reporter:  EvilDMP   |Owner:  animan1
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  afraid-to-commit  | 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:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"b69d1eac641433dba3d6e505261f9ad7db384bd7"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b69d1eac641433dba3d6e505261f9ad7db384bd7"
 Fixed #20975 -- Fixed identation in docs/internals/committers.txt

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

[django/django] 37d46b: Fixed regression introduced by efd1e60, 'map' retu...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 37d46b20fc5325b6fb082f95936a6c97c92dcf7d
  
https://github.com/django/django/commit/37d46b20fc5325b6fb082f95936a6c97c92dcf7d
  Author: Loic Bistuer 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M django/db/backends/schema.py

  Log Message:
  ---
  Fixed regression introduced by efd1e60, 'map' returns an iterator on PY3.



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

Re: [Django] #21032: pip 1.4 and pytz break installation of test requirements

[Django]

#21032: pip 1.4 and pytz break installation of test requirements
---+--
 Reporter:  marfire|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:  wontfix
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by jcatalan):

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


Comment:

 While this actually affects django in that the docs suggest to install
 pytz using pip, I don't think this is a bug that should be solved within
 django. You can just use a previous version of pip to workaround this
 while pytz fixes this issue.

 I tried for instance with pip 1.1 and it worked.

 If this still doesn't solve your problem please let me know and we can
 reopen this ticket.

 Bests,

 Juan

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

Re: [Django] #19885: Make all testing tools importable from django.test

[Django]

#19885: Make all testing tools importable from django.test
--+
 Reporter:  akaariai  |Owner:  marfire
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Testing framework |  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 marfire):

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


Comment:

 I think the
 [https://docs.djangoproject.com/en/dev/topics/testing/overview/ Testing
 Django applications] document provides a good basis for deciding what's
 common enough to fall under `django.test`. Taking that as a basis, and
 taking into account that much of it is already imported into `__init__.py`
 (and that `django.utils.unittest` is no longer necessary in 1.7), I
 propose the following changes:

 * make `override_settings` available on `django.test`.
 * update the documentation to consistently use the `django.test` versions
 (for example, right now it references both `django.test.Client` and
 `django.test.client.Client`).
 * remove `Approximate` from `django.test` (and update the few references
 to it accordingly). This is undocumented and seemingly little used, so it
 makes more sense to leave it at `django.test.utils`.

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

[django/django] 2a2ac5: Merge pull request #1566 from adamsc64/ticket_1185...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 2a2ac5c1400c67f25388621a39749c918a4efe98
  
https://github.com/django/django/commit/2a2ac5c1400c67f25388621a39749c918a4efe98
  Author: Russell Keith-Magee 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M AUTHORS
M django/core/files/temp.py
M tests/files/tests.py

  Log Message:
  ---
  Merge pull request #1566 from adamsc64/ticket_11857

Fixed #11857 -- Added missing 'closed' property on TemporaryFile class.

Backport of 926bc42 from trunk.



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

Re: [Django] #20836: to_field lost when adding via raw_id_fields

[Django]

#20836: to_field lost when adding via raw_id_fields
+--
 Reporter:  CollinAnderson  |Owner:  sheats
 Type:  Bug |   Status:  assigned
Component:  contrib.admin   |  Version:  1.6-beta-1
 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 sheats):

 * needs_tests:  1 => 0


Comment:

 I added a selenium test for this issue and added a little to
 CollinAnderson's solution.

 https://github.com/django/django/pull/1585

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

Re: [Django] #11857: TemporaryFile class is missing the closed - attribute

[Django]

#11857: TemporaryFile class is missing the closed - attribute
-+-
 Reporter:  andi100  |Owner:
 Type:  Bug  |  Christopher Adams
Component:  File |  
  uploads/storage|   Status:  closed
 Severity:  Normal   |  Version:
 Keywords:  TemporaryFile|   Resolution:  fixed
  closed windows | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Russell Keith-Magee ):

 In [changeset:"2a2ac5c1400c67f25388621a39749c918a4efe98"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2a2ac5c1400c67f25388621a39749c918a4efe98"
 Merge pull request #1566 from adamsc64/ticket_11857

 Fixed #11857 -- Added missing 'closed' property on TemporaryFile class.

 Backport of 926bc42 from trunk.
 }}}

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

[django/django] ded401: Fixed #20007 -- Configured psycopg2 to return Unic...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ded40142a92813a8901faa4a6ca398e6679152f6
  
https://github.com/django/django/commit/ded40142a92813a8901faa4a6ca398e6679152f6
  Author: Eric Boersma 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M AUTHORS
M django/db/backends/postgresql_psycopg2/base.py
M tests/backends/tests.py

  Log Message:
  ---
  Fixed #20007 -- Configured psycopg2 to return UnicodeArrays

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

Re: [Django] #20007: psycopg2 should convert SQL arrays into python unicode-arrays

[Django]

#20007: psycopg2 should convert SQL arrays into python unicode-arrays
-+-
 Reporter:  hogbait@…|Owner:
 Type:  Bug  |  EricBoersma
Component:  Database layer   |   Status:  closed
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  psycopg2 unicode | Triage Stage:  Accepted
  python2|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"ded40142a92813a8901faa4a6ca398e6679152f6"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ded40142a92813a8901faa4a6ca398e6679152f6"
 Fixed #20007 -- Configured psycopg2 to return UnicodeArrays

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

Re: [Django] #20558: Add `response_delete` and `render_delete_form` methods to `ModelAdmin`

[Django]

#20558: Add `response_delete` and `render_delete_form` methods to  `ModelAdmin`
---+
 Reporter:  anonymous  |Owner:  polmuz
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by polmuz):

 * has_patch:  0 => 1
 * needs_tests:  1 => 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/067.f78353a44d333af44c7300cbf1758786%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] cd4068: Fixed instructions for running a subset of tests.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: cd4068f35900f22d0384717db0dd7b882d72a4f9
  
https://github.com/django/django/commit/cd4068f35900f22d0384717db0dd7b882d72a4f9
  Author: Tim Graham 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M docs/internals/contributing/writing-code/unit-tests.txt

  Log Message:
  ---
  Fixed instructions for running a subset of tests.



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

Re: [Django] #21060: Refactor admin's autodiscover method to make it reusable

[Django]

#21060: Refactor admin's autodiscover method to make it reusable
-+
 Reporter:  jcatalan |Owner:  jcatalan
 Type:  New feature  |   Status:  new
Component:  Utilities|  Version:  1.5
 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 jcatalan):

 * has_patch:  0 => 1


Comment:

 Here's the [https://github.com/django/django/pull/1584 PR] I made for this
 ticket.

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

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

[django/django] b2f5ac: Fixed #11857 -- Added missing 'closed' property on...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b2f5ac16565605f20a0c4e90acc6beed5a5ac1ce
  
https://github.com/django/django/commit/b2f5ac16565605f20a0c4e90acc6beed5a5ac1ce
  Author: Christopher Adams 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M django/core/files/temp.py
M tests/files/tests.py

  Log Message:
  ---
  Fixed #11857 -- Added missing 'closed' property on TemporaryFile class.

- TemporaryFile now minimally mocks the API of the Python standard
  library class tempfile.NamedTemporaryFile to avoid AttributeError
  exceptions.
- The symbol django.core.files.NamedTemporaryFile is actually assigned
  as a different class on different operating systems.
- The bug only occurred if Django is running on Windows, hence why it
  was hard to diagnose.


  Commit: 0756a4d664b3d243a70aa53567cec5d8d25e37f7
  
https://github.com/django/django/commit/0756a4d664b3d243a70aa53567cec5d8d25e37f7
  Author: Christopher Adams 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M AUTHORS

  Log Message:
  ---
  Added Christopher Adams to the AUTHORS file.

- Note that 'Chris Adams' and 'Christopher Adams' are two different
  contributors.


  Commit: 926bc421d9bcf04a79f0026a60d3d4b0570b7fe2
  
https://github.com/django/django/commit/926bc421d9bcf04a79f0026a60d3d4b0570b7fe2
  Author: Russell Keith-Magee 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M AUTHORS
M django/core/files/temp.py
M tests/files/tests.py

  Log Message:
  ---
  Merge pull request #1566 from adamsc64/ticket_11857

Fixed #11857 -- Added missing 'closed' property on TemporaryFile class.


Compare: https://github.com/django/django/compare/b7451b72edfd...926bc421d9bc

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

Re: [Django] #11857: TemporaryFile class is missing the closed - attribute

[Django]

#11857: TemporaryFile class is missing the closed - attribute
-+-
 Reporter:  andi100  |Owner:
 Type:  Bug  |  Christopher Adams
Component:  File |  
  uploads/storage|   Status:  closed
 Severity:  Normal   |  Version:
 Keywords:  TemporaryFile|   Resolution:  fixed
  closed windows | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Christopher Adams ):

 * status:  new => closed
 * owner:   => Christopher Adams 
 * resolution:   => fixed


Comment:

 In [changeset:"b2f5ac16565605f20a0c4e90acc6beed5a5ac1ce"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b2f5ac16565605f20a0c4e90acc6beed5a5ac1ce"
 Fixed #11857 -- Added missing 'closed' property on TemporaryFile class.

 - TemporaryFile now minimally mocks the API of the Python standard
   library class tempfile.NamedTemporaryFile to avoid AttributeError
   exceptions.
 - The symbol django.core.files.NamedTemporaryFile is actually assigned
   as a different class on different operating systems.
 - The bug only occurred if Django is running on Windows, hence why it
   was hard to diagnose.
 }}}

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

Re: [Django] #11857: TemporaryFile class is missing the closed - attribute

[Django]

#11857: TemporaryFile class is missing the closed - attribute
-+-
 Reporter:  andi100  |Owner:
 Type:  Bug  |  Christopher Adams
Component:  File |  
  uploads/storage|   Status:  closed
 Severity:  Normal   |  Version:
 Keywords:  TemporaryFile|   Resolution:  fixed
  closed windows | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Russell Keith-Magee ):

 In [changeset:"926bc421d9bcf04a79f0026a60d3d4b0570b7fe2"]:
 {{{
 #!CommitTicketReference repository=""
 revision="926bc421d9bcf04a79f0026a60d3d4b0570b7fe2"
 Merge pull request #1566 from adamsc64/ticket_11857

 Fixed #11857 -- Added missing 'closed' property on TemporaryFile class.
 }}}

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

[django/django] b7451b: Fixed deprecation warning on Python 3

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b7451b72edfde0c1ad3c6e33a7a170f16fc53083
  
https://github.com/django/django/commit/b7451b72edfde0c1ad3c6e33a7a170f16fc53083
  Author: Tim Graham 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M tests/serializers/tests.py

  Log Message:
  ---
  Fixed deprecation warning on Python 3



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

Re: [Django] #20558: Add `response_delete` and `render_delete_form` methods to `ModelAdmin`

[Django]

#20558: Add `response_delete` and `render_delete_form` methods to  `ModelAdmin`
---+
 Reporter:  anonymous  |Owner:  polmuz
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by polmuz):

 * owner:  zyegfryed => polmuz


Comment:

 Since this been quiet for a couple of months, I started to work on it.
 Here is the pull request: https://github.com/django/django/pull/1583

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

[django/django] adc0ab: Fixed #21037 -- Made MigrationWriter raise a Value...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: adc0ab3386520874dbc96c2f905fd66769b8f16d
  
https://github.com/django/django/commit/adc0ab3386520874dbc96c2f905fd66769b8f16d
  Author: Loic Bistuer 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M django/db/migrations/writer.py
M tests/migrations/test_writer.py

  Log Message:
  ---
  Fixed #21037 -- Made MigrationWriter raise a ValueError when serializing 
lambda functions.



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

Re: [Django] #21037: MigrationWriter.serialize() output invalid python for lambda functions.

[Django]

#21037: MigrationWriter.serialize() output invalid python for lambda functions.
-+-
 Reporter:  loic84   |Owner:  Tim
 Type:  Bug  |  Graham 
Component:  Migrations   |   Status:  closed
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Tim Graham ):

 * owner:   => Tim Graham 
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"adc0ab3386520874dbc96c2f905fd66769b8f16d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="adc0ab3386520874dbc96c2f905fd66769b8f16d"
 Fixed #21037 -- Made MigrationWriter raise a ValueError when serializing
 lambda 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/064.d79d9473acfcaab21f87b17e06da642b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 6ba01f: [1.6.x] Fixed Python 3 syntax error introduced in ...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 6ba01f64c1e5baf1e876cabd3d625ad53f39a5e4
  
https://github.com/django/django/commit/6ba01f64c1e5baf1e876cabd3d625ad53f39a5e4
  Author: Tim Graham 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M django/core/serializers/__init__.py

  Log Message:
  ---
  [1.6.x] Fixed Python 3 syntax error introduced in [c72392da]

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

[django/django] 498014: Fixed Python 3 syntax error introduced in [c72392d...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 498014ccd5f0ab6281e60fd29d754376aed93111
  
https://github.com/django/django/commit/498014ccd5f0ab6281e60fd29d754376aed93111
  Author: Tim Graham 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M django/core/serializers/__init__.py

  Log Message:
  ---
  Fixed Python 3 syntax error introduced in [c72392da]



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

[django/django] 3df964: [1.6.x] Merge pull request #1582 from rca/12756-mi...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 3df9647ad96eb0f1919be921bb96e949f1a518a0
  
https://github.com/django/django/commit/3df9647ad96eb0f1919be921bb96e949f1a518a0
  Author: Russell Keith-Magee 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M AUTHORS
M django/core/management/commands/dumpdata.py
M django/core/serializers/__init__.py
M tests/serializers/tests.py
M tests/serializers_regress/tests.py
M tests/timezones/tests.py

  Log Message:
  ---
  [1.6.x] Merge pull request #1582 from 
rca/12756-missing-yaml-module-serializer-error-message

Fixed #12756: Improved error message when yaml module is missing.

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

Re: [Django] #12756: dumpdata error message should note pyyaml requirement

[Django]

#12756: dumpdata error message should note pyyaml requirement
--+
 Reporter:  abeld@…   |Owner:  berto
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Serialization)  |  Version:  1.1
 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 Russell Keith-Magee ):

 In [changeset:"3df9647ad96eb0f1919be921bb96e949f1a518a0"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3df9647ad96eb0f1919be921bb96e949f1a518a0"
 [1.6.x] Merge pull request #1582 from rca/12756-missing-yaml-module-
 serializer-error-message

 Fixed #12756: Improved error message when yaml module is missing.

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

[django/django] 67863b: Fixed test failure introduced in efd1e6096ee87fe33...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 67863b3bfebaa5bc3556d2c7612c7fcc2e3b2348
  
https://github.com/django/django/commit/67863b3bfebaa5bc3556d2c7612c7fcc2e3b2348
  Author: Tim Graham 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M tests/bash_completion/tests.py

  Log Message:
  ---
  Fixed test failure introduced in efd1e6096ee87fe332cf989ba5479e9461d0fb3a 
(sqlmigrate)



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

Re: [Django] #20684: Support form element attributes with no value

[Django]

#20684: Support form element attributes with no value
--+
 Reporter:  sneethling@…  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Forms |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+

Comment (by jacob):

 This  is a pretty bad error message - `'The meaning of boolean values for
 widget attributes will change in Django 1.8'` doesn't give anyone any
 clues about *what* will change, what it'll change *to*, and what they
 should do about it.

 Can we think a bit and change this error message to something more user-
 friendly?

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

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

Re: [Django] #20372: using registration/logged_out.html template overrides admin logout

[Django]

#20372: using registration/logged_out.html template overrides admin logout
---+-
 Reporter:  tomerz@…   |Owner:  alexisbellido
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  1  |UI/UX:  0
---+-
Changes (by alexisbellido):

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


Comment:

 Pull request here:

 https://github.com/django/django/pull/1563

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

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

Re: [Django] #14512: Documentation & tools for decorating class-based-views.

[Django]

#14512: Documentation & tools for decorating class-based-views.
---+
 Reporter:  lrekucki   |Owner:  lrekucki
 Type:  New feature|   Status:  closed
Component:  Generic views  |  Version:  master
 Severity:  Normal |   Resolution:  wontfix
 Keywords:  class-based-views  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by garrypolley):

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


Comment:

 Talked to Jacob, the solution here is to bring mixins into Django
 directly.

 Since mixins are not decorators, this ticket is on longer valid.

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

Re: [Django] #15215: API for simpler (permission or any) checks for generic view classes

[Django]

#15215: API for simpler (permission or any) checks for generic view classes
---+
 Reporter:  Ciantic|Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Generic views  |  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 garrypolley):

 After spending some time on this, I don't think this is worth the effort
 at.  I think this ticket and the related one

 https://code.djangoproject.com/ticket/14512

 should both be closed, in favor of mixins.

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

Re: [Django] #15215: API for simpler (permission or any) checks for generic view classes

[Django]

#15215: API for simpler (permission or any) checks for generic view classes
---+
 Reporter:  Ciantic|Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Generic views  |  Version:  master
 Severity:  Normal |   Resolution:  wontfix
 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 garrypolley):

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


Comment:

 Talked to Jacob, the solution here is to bring mixins into Django
 directly.

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

Re: [Django] #20745: Document the template language's silencing of TypeError (was: {{ block.super }} silences/hides errors)

[Django]

#20745: Document the template language's silencing of TypeError
-+
 Reporter:  robin|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.5
 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 bmispelon):

 * easy:  0 => 1


Comment:

 After some digging, I think I'm starting to understand what's happening
 here.

 When django finds a callable element in a template (which `{{ block.super
 }}` is, since it refers to a `BlockNode`'s `super` method), it attempts to
 call it (without passing any argument), wrapping the calling in a
 `try/except` and catching a `TypeError` (which happens when you call a
 function/method without enough arguments).

 In our case, a `TypeError` is raised from inside the function and
 subsequently caught and silenced in the `except` clause.

 Before 4397c587a43ff9bfddd295d48d850676778c6e77, any exception raised
 while rendering a template would be wrapped in a `TemplateSyntaxError`.
 This `TemplateSyntaxError` would then not be caught by the aforementionned
 `except TypeError` clause and would bubble up.
 Note that this would only happen with `settings.TEMPLATE_DEBUG = True`
 (this discrepancy between the two values of `TEMPLATE_DEBUG` is actually
 one of the reason why this change was introduced in the first place).

 This is therefore a limitation of django's implementation, which stems
 from the fact that it can't distinguish between a `TypeError` caused by
 calling a function without enough arguments and a `TypeError` raised from
 inside the function.
 This limitation is noted in a comment in the code [1], but as far as I can
 tell, it's not documented.


 I'm leaving this ticket open but I see it as a documentation issue, unless
 someone can come up with a clever way of side-stepping the problem but I'm
 not sure there is one.

 Since this details is somehow technical, I think a good place for it would
 be this section: https://docs.djangoproject.com/en/1.5/ref/templates/api
 /#variables-and-lookups

 [1]
 
https://github.com/django/django/blob/028db9750357d504c55a7ac686c9abaa3c847ac6/django/template/base.py#L791-L794

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

[django/django] 77da81: Added myself to the contributors list.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 77da814827bcdb32e62aca55c486a1cf447d420d
  
https://github.com/django/django/commit/77da814827bcdb32e62aca55c486a1cf447d420d
  Author: Max Burstein 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M AUTHORS

  Log Message:
  ---
  Added myself to the contributors list.


  Commit: 70440a8bd17a9798f2164115dfa6068bc0a0f4f2
  
https://github.com/django/django/commit/70440a8bd17a9798f2164115dfa6068bc0a0f4f2
  Author: Tim Graham 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M AUTHORS

  Log Message:
  ---
  Merge pull request #1581 from mburst/patch-1

Added myself to the contributors list for work on #21049


Compare: https://github.com/django/django/compare/4f5faa1916e7...70440a8bd17a

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

Re: [Django] #12030: PositiveIntegerField in model form does not validate max value

[Django]

#12030: PositiveIntegerField in model form does not validate max value
-+-
 Reporter:  paul@…   |Owner:  elbarto
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.1
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by amcharg@…):

 How would the following be handled?

 {{{
 if form.is_valid():
instance = form.save(commit=False)
instance.save(using='nowforsomethingcompletelydifferent')
 }}}

 I can't think of a generic way solve this. However I am working on a patch
 that consults the backend's features to get the correct min and max value.

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

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

[django/django] a5bcc0: documented RelatedManager calling save() behind th...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a5bcc09c8f2b0c1cc06a6039a700fbf6103656f7
  
https://github.com/django/django/commit/a5bcc09c8f2b0c1cc06a6039a700fbf6103656f7
  Author: Matthew Rich 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M docs/ref/models/relations.txt

  Log Message:
  ---
  documented RelatedManager calling save() behind the scenes, added section on 
direct replacement of related object set


  Commit: ffe21e1f40b99d82d441eb46de323c6bfb0687e9
  
https://github.com/django/django/commit/ffe21e1f40b99d82d441eb46de323c6bfb0687e9
  Author: Jacob Kaplan-Moss 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M docs/ref/models/relations.txt

  Log Message:
  ---
  Merge pull request #1560 from technivore/ticket_20970

Related Fields documentation improvements


Compare: https://github.com/django/django/compare/b69d1eac6414...ffe21e1f40b9

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

[django/django] d8d61d: Added tests for missing pyyaml.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d8d61d8260badd87b85accaf5776587f2d355c10
  
https://github.com/django/django/commit/d8d61d8260badd87b85accaf5776587f2d355c10
  Author: Roberto Aguilar 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M tests/fixtures/tests.py
M tests/serializers/tests.py

  Log Message:
  ---
  Added tests for missing pyyaml.

This test makes sure an YAML import errors are communicated to the
caller rather than stating the serializer does not exist.


  Commit: c72392dab4b4cf6f5d9b35a3dcb582fbfe38ebb8
  
https://github.com/django/django/commit/c72392dab4b4cf6f5d9b35a3dcb582fbfe38ebb8
  Author: Roberto Aguilar 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M django/core/serializers/__init__.py

  Log Message:
  ---
  Added yaml directly into BUILTIN_SERIALIZERS.

The serializer definitely exists, but the dependent yaml module may not
be installed.  The register_serializer() function will catch exceptions
and will stub in a fake serializer object that will raise the exception
when the serializer is used.


  Commit: 076cf131ec8084ce6d9cc3a05b0f4bcc167d6cbc
  
https://github.com/django/django/commit/076cf131ec8084ce6d9cc3a05b0f4bcc167d6cbc
  Author: Roberto Aguilar 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M django/core/management/commands/dumpdata.py

  Log Message:
  ---
  Moved get_serializer() call in dumpdata command.

Moved the get_serializer() call within the condition that checks public
serializers.  This will allow exceptions other than
SerializerDoesNotExist to be raised in order to provide the caller with
useful information, e.g when pyyaml is not installed.


  Commit: ca3ac4a3e37cc844bef7f7553c6b1a6cc642e6e6
  
https://github.com/django/django/commit/ca3ac4a3e37cc844bef7f7553c6b1a6cc642e6e6
  Author: Roberto Aguilar 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M tests/serializers/tests.py

  Log Message:
  ---
  Updated NoYamlSerializerTestCase to run with yaml.

In order to verify the behavior of using the yaml serializer when yaml
is on the system, fake the ImportError when the serializer is being
registered.


  Commit: 0ac5e8d8e945b2232333fd777e7684c4c2c68316
  
https://github.com/django/django/commit/0ac5e8d8e945b2232333fd777e7684c4c2c68316
  Author: Roberto Aguilar 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M AUTHORS

  Log Message:
  ---
  Added name to AUTHORS (per Russell Keith-Magee)


  Commit: 9587d4eea09bc8d8a852dfb24c2a9227c74fd8ad
  
https://github.com/django/django/commit/9587d4eea09bc8d8a852dfb24c2a9227c74fd8ad
  Author: Roberto Aguilar 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M tests/serializers_regress/tests.py
M tests/timezones/tests.py

  Log Message:
  ---
  Fixed existing tests to handle BadSerializer.

When a BadSerializer instance is stubbed in for the yaml serializer,
make sure tests do not fail.


  Commit: 01a5359477fbc82488dddf9476581fe72c049b51
  
https://github.com/django/django/commit/01a5359477fbc82488dddf9476581fe72c049b51
  Author: Roberto Aguilar 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M AUTHORS
M django/core/serializers/__init__.py
M tests/fixtures/tests.py
M tests/serializers/tests.py
M tests/serializers_regress/tests.py

  Log Message:
  ---
  Cleanup commit after peer review.


  Commit: 4f5faa1916e7c8cb72cc9ebf1a1fd964ba6e707b
  
https://github.com/django/django/commit/4f5faa1916e7c8cb72cc9ebf1a1fd964ba6e707b
  Author: Russell Keith-Magee 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M AUTHORS
M django/core/management/commands/dumpdata.py
M django/core/serializers/__init__.py
M tests/serializers/tests.py
M tests/serializers_regress/tests.py
M tests/timezones/tests.py

  Log Message:
  ---
  Merge pull request #1582 from 
rca/12756-missing-yaml-module-serializer-error-message

Fixed #12756: Improved error message when yaml module is missing.


Compare: https://github.com/django/django/compare/9b2dc12b8332...4f5faa1916e7

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

Re: [Django] #12756: dumpdata error message should note pyyaml requirement

[Django]

#12756: dumpdata error message should note pyyaml requirement
--+
 Reporter:  abeld@…   |Owner:  berto
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Serialization)  |  Version:  1.1
 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 Russell Keith-Magee ):

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


Comment:

 In [changeset:"4f5faa1916e7c8cb72cc9ebf1a1fd964ba6e707b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="4f5faa1916e7c8cb72cc9ebf1a1fd964ba6e707b"
 Merge pull request #1582 from rca/12756-missing-yaml-module-serializer-
 error-message

 Fixed #12756: Improved error message when yaml module is missing.
 }}}

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

Re: [Django] #20888: Index ordering in index_together and unique_together

[Django]

#20888: Index ordering in index_together and unique_together
-+-
 Reporter:  anonymous|Owner:  animan1
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  index, order |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by animan1):

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


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

Re: [Django] #21054: SimpleLazyObject for request.user not correctly evaluated inside RequestContext

[Django]

#21054: SimpleLazyObject for request.user not correctly evaluated inside
RequestContext
-+-
 Reporter:  giohappy |Owner:
 Type:  Uncategorized|   Status:  new
Component:  Template system  |  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  template, form view  | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by DanRJohnson):

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


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

Re: [Django] #21060: Refactor admin's autodiscover method to make it reusable

[Django]

#21060: Refactor admin's autodiscover method to make it reusable
-+
 Reporter:  jcatalan |Owner:  jcatalan
 Type:  New feature  |   Status:  new
Component:  Utilities|  Version:  1.5
 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 jcatalan):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Accepted
 * 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/066.7bf3429014b43119b2ea38fdbe978a3d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 9b7f4a: adds fix and test for when a template is not speci...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 9b7f4aab326067a3ad503887a4e42c9d76d0bc25
  
https://github.com/django/django/commit/9b7f4aab326067a3ad503887a4e42c9d76d0bc25
  Author: Ian Wilson 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M AUTHORS
M django/views/debug.py
M tests/view_tests/tests/test_debug.py
M tests/view_tests/urls.py
M tests/view_tests/views.py

  Log Message:
  ---
  adds fix and test for when a template is not specified at all to render(). 
fixes #21058. by jambonrose and ianawilson


  Commit: e12de0ac0485d8799d08fda556b66399c6f89fc9
  
https://github.com/django/django/commit/e12de0ac0485d8799d08fda556b66399c6f89fc9
  Author: Ian Wilson 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M tests/view_tests/tests/test_debug.py

  Log Message:
  ---
  Removed unnecessary, leftover imports


  Commit: 122020fdb93980df850ae02f61d97da27e2cb515
  
https://github.com/django/django/commit/122020fdb93980df850ae02f61d97da27e2cb515
  Author: Russell Keith-Magee 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M AUTHORS
M django/views/debug.py
M tests/view_tests/tests/test_debug.py
M tests/view_tests/urls.py
M tests/view_tests/views.py

  Log Message:
  ---
  Merge pull request #1579 from ianawilson/ticket_21058

Fixed #21058 -- Fixed debug view blowing up when no template is provided to the 
template rendering functions.

Assistance on this commit from @jambonrose.


Compare: https://github.com/django/django/compare/e844e10b4f06...122020fdb939

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

Re: [Django] #21058: Template Error during render results in 500 error

[Django]

#21058: Template Error during render results in 500 error
-+-
 Reporter:  jambonrose   |Owner:
 Type:  Bug  |  ianawilson
Component:  Template system  |   Status:  closed
 Severity:  Normal   |  Version:  1.5
 Keywords:  template,|   Resolution:  fixed
  TemplateDoesNotExist, render   | Triage Stage:
Has patch:  1|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Russell Keith-Magee ):

 In [changeset:"b917458f4752e98dc7866261f40e296de3701130"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b917458f4752e98dc7866261f40e296de3701130"
 Merge pull request #1579 from ianawilson/ticket_21058

 [1.6.x] Fixed #21058 -- Fixed debug view blowing up when no template is
 provided to the template rendering functions.

 Assistance on this commit from @jambonrose.

 Backport of 122020fdb93980df850ae02f61d97da27e2cb515 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/068.839d6c77ad6098ed9f8630389c47446d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21058: Template Error during render results in 500 error

[Django]

#21058: Template Error during render results in 500 error
-+-
 Reporter:  jambonrose   |Owner:
 Type:  Bug  |  ianawilson
Component:  Template system  |   Status:  closed
 Severity:  Normal   |  Version:  1.5
 Keywords:  template,|   Resolution:  fixed
  TemplateDoesNotExist, render   | Triage Stage:
Has patch:  1|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Russell Keith-Magee ):

 In [changeset:"122020fdb93980df850ae02f61d97da27e2cb515"]:
 {{{
 #!CommitTicketReference repository=""
 revision="122020fdb93980df850ae02f61d97da27e2cb515"
 Merge pull request #1579 from ianawilson/ticket_21058

 Fixed #21058 -- Fixed debug view blowing up when no template is provided
 to the template rendering functions.

 Assistance on this commit from @jambonrose.
 }}}

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

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

Re: [Django] #21058: Template Error during render results in 500 error

[Django]

#21058: Template Error during render results in 500 error
-+-
 Reporter:  jambonrose   |Owner:
 Type:  Bug  |  ianawilson
Component:  Template system  |   Status:  closed
 Severity:  Normal   |  Version:  1.5
 Keywords:  template,|   Resolution:  fixed
  TemplateDoesNotExist, render   | Triage Stage:
Has patch:  1|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Ian Wilson ):

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


Comment:

 In [changeset:"9b7f4aab326067a3ad503887a4e42c9d76d0bc25"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9b7f4aab326067a3ad503887a4e42c9d76d0bc25"
 adds fix and test for when a template is not specified at all to render().
 fixes #21058. by jambonrose and ianawilson
 }}}

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

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

Re: [Django] #16502: CreateView useless error message when template_name is not specified

[Django]

#16502: CreateView useless error message when template_name is not specified
-+-
 Reporter:  silverghost3@…   |Owner:  krak3n
 Type:  Bug  |   Status:  new
Component:  Generic views|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  CreateView "generic  | Triage Stage:  Accepted
  view"  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by jambonrose):

 This is all a little convoluted. There is no longer one problem at hand,
 and a little clarification might be useful.

 Bug 1: `get_template_names()` (as defined in
 `SingleObjectTemplateResponseMixin`) is returning `None`, which is causing
 Django to throw a `TemplateDoesNotExist`. This should instead throw a
 `ImproperlyConfigured` error, as it does not have the information to
 determine the template file to load. This is more eloquently described in
 #18853 (marked as duplicate to this topic)

 Bug 2: The `TemplateDoesNotExist` exception is causing the server error
 message, as detailed (and solved) in #21058.

 Feature Request 1: Creating a CBGV by only overriding the `form_class`
 variable. The patch provided creates the ability to do so, but does not
 actually solve the bugs detailed.

 I spoke to Russel about the possibility of the new feature. Unfortunately,
 determining the model based off a form specified in `form_class` is not
 desirable, because this assumes the form is a ModelForm, which may not be
 the case. As such, this feature (and patch) will therefore not be approved
 for Django.

 This leaves only Bug 1 to be solved.

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

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

Re: [Django] #19924: Some jQuery selectors in actions.js use hardcoded values instead of pulling from options.

[Django]

#19924: Some jQuery selectors in actions.js use hardcoded values instead of 
pulling
from options.
---+
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  javascript | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  1  |UI/UX:  0
---+
Changes (by polmuz):

 * needs_better_patch:  0 => 1
 * component:  contrib.auth => contrib.admin


Comment:

 I reviewed the code and it looks good.

 Here are the instructions to compile the javascript for django
 https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
 /submitting-patches/#javascript-patches

 I think if you add that and you create a pull request this could be
 merged.

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

[django/django] 0b7cf5: Add -l alias for migrate --list

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 0b7cf56e28078a6d5e2a9cd21ef08176ad9a453b
  
https://github.com/django/django/commit/0b7cf56e28078a6d5e2a9cd21ef08176ad9a453b
  Author: Andrew Godwin 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

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

  Log Message:
  ---
  Add -l alias for migrate --list



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

[django/django] 99952b: [1.6.x] Merge pull request #1580 from ianawilson/t...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 99952bab3008622b05613ed6ec54c3e1c63c0a1d
  
https://github.com/django/django/commit/99952bab3008622b05613ed6ec54c3e1c63c0a1d
  Author: Russell Keith-Magee 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M django/views/generic/detail.py
M tests/generic_views/test_base.py
M tests/generic_views/views.py

  Log Message:
  ---
  [1.6.x] Merge pull request #1580 from ianawilson/ticket_16502

Fixed #16502 -- Fixed a TemplateDoesNotExist error that should be an 
ImproperlyConfigured.

Assistance on the patch from #jambronrose.

Backport of 9b2dc12b8332389d1bfb9e83123a088a084a6a47 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/522a59bef40ff_3faeccfd581097d3%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20821: Permission names can be longer than the select box they are in

[Django]

#20821: Permission names can be longer than the select box they are in
---+
 Reporter:  django@…   |Owner:  rmutter
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.5
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Julien Phalip ):

 In [changeset:"d5df914fe14fd96cec1cd3465852b8da72e7c5f6"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d5df914fe14fd96cec1cd3465852b8da72e7c5f6"
 Merge pull request #1578 from rmutter/ticket_20821

 Fixed #20821 -- Added tooltips to Admin SelectBox widget
 }}}

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

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

[django/django] db3de5: Fixed #20646 -- Clarified the use of AbstractBaseU...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: db3de528071ac66903f82c2fe5b34db4a5281f5b
  
https://github.com/django/django/commit/db3de528071ac66903f82c2fe5b34db4a5281f5b
  Author: Tim Graham 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

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

  Log Message:
  ---
  Fixed #20646 -- Clarified the use of AbstractBaseUser.REQUIRED_FIELDS

Thanks craigbruce.



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

Re: [Django] #10164: sqlite3 backend: AutoField values aren't monotonically increasing

[Django]

#10164: sqlite3 backend: AutoField values aren't monotonically increasing
-+-
 Reporter:  malte|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.2
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  sqlite   |  Needs documentation:  0
  autoincrement  |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 I'm sorry, but the release notes look wrong to me. Do you think my
 proposal makes sense?
 
https://github.com/django/django/commit/eade315da1c8372ac1dfcf1fd20ea87f454d71ac#commitcomment-4034261

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

[Django] #21060: Refactor admin's autodiscover method to make it reusable

[Django]

#21060: Refactor admin's autodiscover method to make it reusable
-+--
 Reporter:  jcatalan |  Owner:  jcatalan
 Type:  New feature  | Status:  new
Component:  Utilities|Version:  1.5
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+--
 It would be nice to be able to reuse admin's autodiscover method to be
 able to use it for instance with tasks.py modules.

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

Re: [Django] #20876: Polls in polls

[Django]

#20876: Polls in polls
-+-
 Reporter:  anonymous|Owner:
 Type:   |  rodolfo2488
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  afraid-to-commit | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-
Changes (by rodolfo2488):

 * owner:  nobody => rodolfo2488
 * 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/067.f63a304dc0f28fe5bf313f69c6e28471%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20347: Note that initializing a formset will be limited by max_num

[Django]

#20347: Note that initializing a formset will be limited by max_num
--+-
 Reporter:  CarstenF  |Owner:  ethurgood
 Type:  Bug   |   Status:  assigned
Component:  Forms |  Version:  1.5
 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 ethurgood):

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


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

Re: [Django] #18480: Inherited model fails to handle blank field properly

[Django]

#18480: Inherited model fails to handle blank field properly
-+-
 Reporter:  yuval_a  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (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|
-+-

Comment (by anonymous):

 Seems all related accessor name are not validated against existing fields.

 class A(models.Model):
 a = models.IntegerField()
 br = models.IntegerField()

 class B(models.Model):
 a = models.ForeignKey(A, related_name='br')

 raises an error.

 Should fixing this wait till the validation changes hit?

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

Re: [Django] #16502: CreateView useless error message when template_name is not specified

[Django]

#16502: CreateView useless error message when template_name is not specified
-+-
 Reporter:  silverghost3@…   |Owner:
 Type:  Bug  |  ianawilson
Component:  Generic views|   Status:  closed
 Severity:  Normal   |  Version:  master
 Keywords:  CreateView "generic  |   Resolution:  fixed
  view"  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Russell Keith-Magee ):

 In [changeset:"99952bab3008622b05613ed6ec54c3e1c63c0a1d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="99952bab3008622b05613ed6ec54c3e1c63c0a1d"
 [1.6.x] Merge pull request #1580 from ianawilson/ticket_16502

 Fixed #16502 -- Fixed a TemplateDoesNotExist error that should be an
 ImproperlyConfigured.

 Assistance on the patch from #jambronrose.

 Backport of 9b2dc12b8332389d1bfb9e83123a088a084a6a47 from master.
 }}}

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

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

Re: [Django] #10811: Assigning unsaved model to a ForeignKey leads to silent failures

[Django]

#10811: Assigning unsaved model to a ForeignKey leads to silent failures
-+-
 Reporter:  Glenn|Owner:  aaugustin
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (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|
-+-

Comment (by aaugustin):

 I'm attaching a new patch that fixes a few test failures:
 - by saving the objects before assigning them to foreign keys,
 - by removing explicit tests for the behavior this ticket wants to
 prevent, introduced (among other more reasonable changes) in #8070.

 With this patch, there are still two tests failures related to admin
 inlines.

 {{{
 ==
 ERROR: test_create_inlines_on_inherited_model
 (admin_inlines.tests.TestInline)
 --
 Traceback (most recent call last):
   File "/Users/myk/Documents/dev/django/tests/admin_inlines/tests.py",
 line 192, in test_create_inlines_on_inherited_model
 response =
 self.client.post('/admin/admin_inlines/extraterrestrial/add/', data)
   File "/Users/myk/Documents/dev/django/django/test/client.py", line 460,
 in post
 response = super(Client, self).post(path, data=data,
 content_type=content_type, **extra)
   File "/Users/myk/Documents/dev/django/django/test/client.py", line 289,
 in post
 return self.generic('POST', path, post_data, content_type, **extra)
   File "/Users/myk/Documents/dev/django/django/test/client.py", line 339,
 in generic
 return self.request(**r)
   File "/Users/myk/Documents/dev/django/django/test/client.py", line 421,
 in request
 six.reraise(*exc_info)
   File "/Users/myk/Documents/dev/django/django/utils/six.py", line 491, in
 reraise
 raise value
   File "/Users/myk/Documents/dev/django/django/core/handlers/base.py",
 line 114, in get_response
 response = wrapped_callback(request, *callback_args,
 **callback_kwargs)
   File "/Users/myk/Documents/dev/django/django/contrib/admin/options.py",
 line 467, in wrapper
 return self.admin_site.admin_view(view)(*args, **kwargs)
   File "/Users/myk/Documents/dev/django/django/utils/decorators.py", line
 99, in _wrapped_view
 response = view_func(request, *args, **kwargs)
   File "/Users/myk/Documents/dev/django/django/views/decorators/cache.py",
 line 52, in _wrapped_view_func
 response = view_func(request, *args, **kwargs)
   File "/Users/myk/Documents/dev/django/django/contrib/admin/sites.py",
 line 198, in inner
 return view(request, *args, **kwargs)
   File "/Users/myk/Documents/dev/django/django/utils/decorators.py", line
 29, in _wrapper
 return bound_func(*args, **kwargs)
   File "/Users/myk/Documents/dev/django/django/utils/decorators.py", line
 99, in _wrapped_view
 response = view_func(request, *args, **kwargs)
   File "/Users/myk/Documents/dev/django/django/utils/decorators.py", line
 25, in bound_func
 return func(self, *args2, **kwargs2)
   File "/Users/myk/Documents/dev/django/django/db/transaction.py", line
 360, in inner
 return func(*args, **kwargs)
   File "/Users/myk/Documents/dev/django/django/contrib/admin/options.py",
 line 1161, in add_view
 if all_valid(formsets) and form_validated:
   File "/Users/myk/Documents/dev/django/django/forms/formsets.py", line
 415, in all_valid
 if not formset.is_valid():
   File "/Users/myk/Documents/dev/django/django/forms/formsets.py", line
 292, in is_valid
 err = self.errors
   File "/Users/myk/Documents/dev/django/django/forms/formsets.py", line
 267, in errors
 self.full_clean()
   File "/Users/myk/Documents/dev/django/django/forms/formsets.py", line
 315, in full_clean
 self._errors.append(form.errors)
   File "/Users/myk/Documents/dev/django/django/forms/forms.py", line 121,
 in errors
 self.full_clean()
   File "/Users/myk/Documents/dev/django/django/forms/forms.py", line 275,
 in full_clean
 self._post_clean()
   File "/Users/myk/Documents/dev/django/django/forms/models.py", line 387,
 in _post_clean
 self.instance = construct_instance(self, self.instance, opts.fields,
 opts.exclude)
   File "/Users/myk/Documents/dev/django/django/forms/models.py", line 57,
 in construct_instance
 f.save_form_data(instance, cleaned_data[f.name])
   File
 "/Users/myk/Documents/dev/django/django/db/models/fields/__init__.py",
 line 637, in save_form_data
 setattr(instance, self.name, data)
   F

[django/django] c438cc: Fixed #20821 -- Added tooltips to Admin SelectBox ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c438cc2a3653644ea42987f7e65f6f638ca85f6c
  
https://github.com/django/django/commit/c438cc2a3653644ea42987f7e65f6f638ca85f6c
  Author: Rudy Mutter 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M django/contrib/admin/static/admin/js/SelectBox.js
M tests/admin_widgets/tests.py

  Log Message:
  ---
  Fixed #20821 -- Added tooltips to Admin SelectBox widget

The Admin widget, which can be used to filter multiple selects
can sometimes be too narrow and hide information such as
user permissions. This commit adds tooltips to the select
options so that a user can hover over and see the hidden text.


  Commit: d5df914fe14fd96cec1cd3465852b8da72e7c5f6
  
https://github.com/django/django/commit/d5df914fe14fd96cec1cd3465852b8da72e7c5f6
  Author: Julien Phalip 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M django/contrib/admin/static/admin/js/SelectBox.js
M tests/admin_widgets/tests.py

  Log Message:
  ---
  Merge pull request #1578 from rmutter/ticket_20821

Fixed #20821 -- Added tooltips to Admin SelectBox widget


Compare: https://github.com/django/django/compare/ce5e09353d4a...d5df914fe14f

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

[Django] #21056: AdminSite app_list may be reverse()'d into an invalid URL endpoint

[Django]

#21056: AdminSite app_list may be reverse()'d into an invalid URL endpoint
-+
 Reporter:  Keryn Knight   |  Owner:  nobody
 Type:  Cleanup/optimization | Status:  new
Component:  contrib.admin|Version:  master
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 Because of the way the
 
[https://github.com/django/django/blob/a962286b74f1e8c8cb19fb45a057800da8c2fb56/django/contrib/admin/sites.py#L235
 regular expression] for the `app_index` view is set, it allows pretty much
 anything to be reversed to a valid URL, even if that URL will generate a
 404 when visited. This is in contrast to any of the views defined in the
 `ModelAdmin`'s own `get_urls`, because they are included by way of the
 `app_label` for that ModelAdmin's Model class, and are usually resolved
 using the named url which is a combination of the app label + model name.

 {{{
 >>> from django.core.urlresolvers import reverse
 >>> reverse('admin:index') # this is ok!
 '/admin/'
 >>> reverse('admin:app_list', kwargs={'app_label': 'auth'}) # this is ok!
 '/admin/auth/'
 >>> reverse('admin:app_list', kwargs={'app_label':
 'test_anything_is_allowed'}) # chances are this isn't right.
 '/admin/test_anything_is_allowed/'
 }}}

 As the registry already maintains a list of ModelAdmins, it would probably
 be reasonably simple to iterate over those and get all distinct app
 labels, and compile one regex that ORs them altogether, reducing the
 ability to accidentally create invalid links.

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

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

[django/django] da44a8: [1.6.x] Fixed #20646 -- Clarified the use of Abstr...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: da44a8bdc2524424bfd3e904e394457028265619
  
https://github.com/django/django/commit/da44a8bdc2524424bfd3e904e394457028265619
  Author: Tim Graham 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

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

  Log Message:
  ---
  [1.6.x] Fixed #20646 -- Clarified the use of AbstractBaseUser.REQUIRED_FIELDS

Thanks craigbruce.

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

[django/django] e844e1: Moved a settings usage up the stack in utils/forma...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e844e10b4f06c13d24d405fe0d2e80a23d260508
  
https://github.com/django/django/commit/e844e10b4f06c13d24d405fe0d2e80a23d260508
  Author: Adrian Holovaty 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M django/utils/formats.py
M tests/i18n/tests.py

  Log Message:
  ---
  Moved a settings usage up the stack in utils/formats.py #unsettings



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

Re: [Django] #12756: dumpdata error message should note pyyaml requirement

[Django]

#12756: dumpdata error message should note pyyaml requirement
--+
 Reporter:  abeld@…   |Owner:  berto
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (Serialization)  |  Version:  1.1
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by berto):

 New PR: https://github.com/django/django/pull/1582

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

Re: [Django] #20077: Document that Ubuntu can occassionally require installing sqlite

[Django]

#20077: Document that Ubuntu can occassionally require installing sqlite
---+
 Reporter:  jacob  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.5
 Severity:  Normal |   Resolution:  invalid
 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 timo):

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


Comment:

 I've confirmed that Ubuntu 12.04, 12.10, 13.04 all don't have the
 `sqlite3` package installed by default, but also that you can use SQLite
 in Python without that package. I don't think this is needed.

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

Re: [Django] #11811: No error raised on update(foreignkey=unsavedobject) on nullable fk

[Django]

#11811: No error raised on update(foreignkey=unsavedobject) on nullable fk
-+-
 Reporter:  Afief|Owner:  aaugustin
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.1
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by aaugustin):

 In fact, this may be fixed independently from #10811, which turned out to
 be extremely hard.

 While I can imagine use cases for the behavior #10811 is trying to
 prevent, I don't see any for this one. It's clearly a data-loss bug.

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

Re: [Django] #16992: MySQL InnoDB AUTO_INCREMENT bug (next value to use forgotten at restart)

[Django]

#16992: MySQL InnoDB AUTO_INCREMENT bug (next value to use forgotten at restart)
-+-
 Reporter:  kent@…   |Owner:  kedmiston
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.3
Component:  Documentation|   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:  1|
-+-
Changes (by kedmiston):

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


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

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

Re: [Django] #20841: NotImplementedErrors should provide exception messages

[Django]

#20841: NotImplementedErrors should provide exception messages
-+-
 Reporter:  joseph@… |Owner:
 Type:   |  TimClifford
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  NotImplementedError  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by TimClifford):

 Pull request submitted and awaiting review. 92 instances of "raise
 NotImplementedError" used to placehold base class methods for subclassing
 were given verbose may/must subclass explanations, and two instances of
 not-implemented features were written up as well (found in
 /utils/datetime.py line #67 and /utils/regex_helper.py line #95).

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

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

Re: [Django] #16134: django.db.models.fields.Field instance can not be compared with None

[Django]

#16134: django.db.models.fields.Field instance can not be compared with None
-+-
 Reporter:  amcharg@…|Owner:  adamsc64
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by adamsc64):

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


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

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

[django/django] b79df0: adds fix for SingleObjectTemplateResponseMixin rai...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b79df0b35861400f573e74d0305d7298c221e7ff
  
https://github.com/django/django/commit/b79df0b35861400f573e74d0305d7298c221e7ff
  Author: Ian Wilson 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M django/views/generic/detail.py
M tests/generic_views/test_base.py
M tests/generic_views/views.py

  Log Message:
  ---
  adds fix for SingleObjectTemplateResponseMixin raising a TemplateDoesNotExist 
when it should have raised an ImproperlyConfigured. fixes 16502. by 
@ianawilson, @jambonrose


  Commit: d0051308450880dbc2df6de96a6d1aab954df000
  
https://github.com/django/django/commit/d0051308450880dbc2df6de96a6d1aab954df000
  Author: Ian Wilson 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M tests/generic_views/test_base.py

  Log Message:
  ---
  fixed test name from an old, overly specific iteration of the test


  Commit: 9b2dc12b8332389d1bfb9e83123a088a084a6a47
  
https://github.com/django/django/commit/9b2dc12b8332389d1bfb9e83123a088a084a6a47
  Author: Russell Keith-Magee 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M django/views/generic/detail.py
M tests/generic_views/test_base.py
M tests/generic_views/views.py

  Log Message:
  ---
  Merge pull request #1580 from ianawilson/ticket_16502

Fixed #16502 -- Fixed a TemplateDoesNotExist error that should be an 
ImproperlyConfigured.

Assistance on the patch from #jambronrose.


Compare: https://github.com/django/django/compare/b4cd8169de60...9b2dc12b8332

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

Re: [Django] #16502: CreateView useless error message when template_name is not specified

[Django]

#16502: CreateView useless error message when template_name is not specified
-+-
 Reporter:  silverghost3@…   |Owner:
 Type:  Bug  |  ianawilson
Component:  Generic views|   Status:  closed
 Severity:  Normal   |  Version:  master
 Keywords:  CreateView "generic  |   Resolution:  fixed
  view"  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Russell Keith-Magee ):

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


Comment:

 In [changeset:"9b2dc12b8332389d1bfb9e83123a088a084a6a47"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9b2dc12b8332389d1bfb9e83123a088a084a6a47"
 Merge pull request #1580 from ianawilson/ticket_16502

 Fixed #16502 -- Fixed a TemplateDoesNotExist error that should be an
 ImproperlyConfigured.

 Assistance on the patch from #jambronrose.
 }}}

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

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

Re: [Django] #16134: django.db.models.fields.Field instance can not be compared with None

[Django]

#16134: django.db.models.fields.Field instance can not be compared with None
-+-
 Reporter:  amcharg@…|Owner:  adamsc64
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by adamsc64):

 Simon Charette's commit at 5cbfb48b (intended to fix #17851) actually
 resolves this issue also. This commit made its way into stable/1.5.x but
 is not yet in stable/1.4.x. As this is not a security issue, both Russell
 Keith-Magee and Andrew Godwin tell me not to bother with a pull request.

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

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

Re: [Django] #20841: NotImplementedErrors should provide exception messages

[Django]

#20841: NotImplementedErrors should provide exception messages
-+-
 Reporter:  joseph@… |Owner:
 Type:   |  TimClifford
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  NotImplementedError  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by TimClifford):

 * has_patch:  0 => 1


Comment:

 Added a patch in the form of a Pull Request, visible here:
 https://github.com/django/django/pull/1569

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

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

[django/django] 73f38e: Minor factorization.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 73f38eb4d15d3da4707d8637178334c2f105ca19
  
https://github.com/django/django/commit/73f38eb4d15d3da4707d8637178334c2f105ca19
  Author: Aymeric Augustin 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M django/db/models/sql/subqueries.py

  Log Message:
  ---
  Minor factorization.


  Commit: b4cd8169de604943f8aaee3666282c95e650e5f4
  
https://github.com/django/django/commit/b4cd8169de604943f8aaee3666282c95e650e5f4
  Author: Aymeric Augustin 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M django/db/models/base.py
M tests/queries/models.py
M tests/queries/tests.py

  Log Message:
  ---
  Fixed #11811 -- Data-loss bug in queryset.update.

It's now forbidden to call queryset.update(field=instance) when instance
hasn't been saved to the database ie. instance.pk is None.


Compare: https://github.com/django/django/compare/122020fdb939...b4cd8169de60

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

Re: [Django] #10811: Assigning unsaved model to a ForeignKey leads to silent failures

[Django]

#10811: Assigning unsaved model to a ForeignKey leads to silent failures
-+-
 Reporter:  Glenn|Owner:
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 I'm admitting defeat. If you want to tackle this, my advice in to untangle
 the loop in InlineModelAdmin.

 The patch also needs release notes as it's probably going to break at
 least a few people's code. People who relied on this possibility in tests
 should switch to mocking.

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

Re: [Django] #11811: No error raised on update(foreignkey=unsavedobject) on nullable fk

[Django]

#11811: No error raised on update(foreignkey=unsavedobject) on nullable fk
-+-
 Reporter:  Afief|Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.1
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"b4cd8169de604943f8aaee3666282c95e650e5f4"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b4cd8169de604943f8aaee3666282c95e650e5f4"
 Fixed #11811 -- Data-loss bug in queryset.update.

 It's now forbidden to call queryset.update(field=instance) when instance
 hasn't been saved to the database ie. instance.pk is None.
 }}}

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

[django/django] b91745: Merge pull request #1579 from ianawilson/ticket_21...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: b917458f4752e98dc7866261f40e296de3701130
  
https://github.com/django/django/commit/b917458f4752e98dc7866261f40e296de3701130
  Author: Russell Keith-Magee 
  Date:   2013-09-06 (Fri, 06 Sep 2013)

  Changed paths:
M AUTHORS
M django/views/debug.py
M tests/view_tests/tests/test_debug.py
M tests/view_tests/urls.py
M tests/view_tests/views.py

  Log Message:
  ---
  Merge pull request #1579 from ianawilson/ticket_21058

[1.6.x] Fixed #21058 -- Fixed debug view blowing up when no template is 
provided to the template rendering functions.

Assistance on this commit from @jambonrose.

Backport of 122020fdb93980df850ae02f61d97da27e2cb515 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/522a53f8c3e65_3fa69a3d50114716%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20995: {% include %} uses get_template where it could select_template

[Django]

#20995: {% include %} uses get_template where it could select_template
-+-
 Reporter:  Keryn Knight |Owner:
   |  amberdoctor
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by amberdoctor):

 * owner:  nobody => amberdoctor
 * status:  new => assigned
 * needs_docs:   => 0
 * needs_tests:   => 0
 * needs_better_patch:   => 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/095.12b07744be30a0ac13c5e53d6d2dad24%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20917: Change the password hashers when testing

[Django]

#20917: Change the password hashers when testing
-+-
 Reporter:  mjtamlyn |Owner:
 Type:  New feature  |  ashchristopher
Component:  Testing framework|   Status:  assigned
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by ashchristopher):

 If people have overridden the `PASSWORD_HASHER` with their own custom
 hasher, or if they have updated the `PASSWORD_HASHER` in say a
 test_settings.py file (which is how we solved this) then having an opinion
 on the password hasher in tests would break their tests.

 I know that our test suite would break if we defaulted to a specific
 hasher in tests (though this is basically a data point of 1).

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

Re: [Django] #10811: Assigning unsaved model to a ForeignKey leads to silent failures

[Django]

#10811: Assigning unsaved model to a ForeignKey leads to silent failures
-+-
 Reporter:  Glenn|Owner:  aaugustin
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * status:  new => assigned
 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1
 * needs_docs:  0 => 1


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

Re: [Django] #20821: Permission names can be longer than the select box they are in

[Django]

#20821: Permission names can be longer than the select box they are in
---+
 Reporter:  django@…   |Owner:  rmutter
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.5
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Rudy Mutter ):

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


Comment:

 In [changeset:"c438cc2a3653644ea42987f7e65f6f638ca85f6c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c438cc2a3653644ea42987f7e65f6f638ca85f6c"
 Fixed #20821 -- Added tooltips to Admin SelectBox widget

 The Admin widget, which can be used to filter multiple selects
 can sometimes be too narrow and hide information such as
 user permissions. This commit adds tooltips to the select
 options so that a user can hover over and see the hidden text.
 }}}

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

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

Re: [Django] #19298: MultiValueField should override __deepcopy__

[Django]

#19298: MultiValueField should override __deepcopy__
-+
 Reporter:  nick.phillips@…  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by anonymous):

 * has_patch:  0 => 1
 * easy:  0 => 1


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

Re: [Django] #21043: resolve doesn't handle lazily evaluated reverses

[Django]

#21043: resolve doesn't handle lazily evaluated reverses
-+-
 Reporter:  Keryn Knight |Owner:
   |   Status:  new
 Type:  Bug  |  Version:  master
Component:  Core (URLs)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  urlresolvers |  Needs documentation:  0
  resolve reverse|  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  1|
-+-
Changes (by DanRJohnson):

 * owner:  DanRJohnson =>
 * 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/095.b177aa9ef47b1bb811b4ef564ea736ab%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20821: Permission names can be longer than the select box they are in

[Django]

#20821: Permission names can be longer than the select box they are in
---+
 Reporter:  django@…   |Owner:  rmutter
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  1.5
 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 rmutter):

 * owner:  nobody => rmutter
 * 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/077.a76b14c0df46a6bea36ddf4be40b0b23%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13724: Calling QuerySet.delete() through a relation the DB router is ignored.

[Django]

#13724: Calling QuerySet.delete() through a relation the DB router is ignored.
-+-
 Reporter:  Chris Targett|Owner:  nobody
|   Status:  new
 Type:  Bug  |  Version:  1.3
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:  multidb  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by barnardo):

 Attached is a test case for 1.3.7. I was not able to duplicate. Please
 verify.

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