[Django] #20686: Many-to-many related manager method: toggle()

[Django]

#20686: Many-to-many related manager method: toggle()
--+
 Reporter:  Deacalion |  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:  toggle
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 My use case: on a few occasions I've needed to ‘**//toggle//**’ an M2M
 relation between two models, i.e. if the relation exists, it should be
 removed and if it doesn't it should be created.

 {{{
 #!div style="font-size: 80%"
 Usage – [http://git.io/NnNh0A using these models]:
   {{{#!python
   >>> a4
   
   >>> p2
   
   >>> p2.article_set.all()
   [
   ,
   ,
   ,
   ]
   >>> a4.publications.toggle(p2) # the relation is removed
   >>> p2.article_set.all()
   [
   ,
   ,
   ]
   >>> a4.publications.toggle(p2) # the relation is added
   >>> p2.article_set.all()
   [
   ,
   ,
   ,
   ]
   >>> p2.article_set.toggle(a4) # and… removed again (can be toggled from
 either model)
   [
   ,
   ,
   ]
   }}}
 }}}

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

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

Re: [Django] #8060: otjgprrsrtry (was: Admin Inlines do not respect user permissions)

[Django]

#8060: otjgprrsrtry
---+
 Reporter:  p.patruno@…|Owner:  sjaensch
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords:  zzeusxiaxkxc   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by sluhztiumfbg):

 * keywords:  inlines User authentication => zzeusxiaxkxc


Comment:

 woah, amazing site thanks bwbzoonfko http://www.dktbquqytqat.com;>click here :[ nszjs, :-( zdccwcmaer
 [url="http://www.dktbquqytqat.net"]or here[/url] :|] bpnazdhmtsqn, O:)
 uaceouopay http://dktbquqytqat.info :D umpwdoj, :3 ewgplcyvlw
 [url=http://dktbquqytqat.ru]yviavrblla[/url] :/ umpwdoj, B| umrwqoysqw
 [link=http://dktbquqytqat.se]ggahiaeyja[/link] <3 umpwdoj, >:o

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

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

Re: [Django] #8060: Admin Inlines do not respect user permissions (was: gavrxaozqxxx)

[Django]

#8060: Admin Inlines do not respect user permissions
-+-
 Reporter:  p.patruno@…  |Owner:  sjaensch
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  inlines User | Triage Stage:  Accepted
  authentication |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by ramiro):

 * keywords:  lkwocrzmewpk => inlines User authentication


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

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

Re: [Django] #8060: gavrxaozqxxx (was: Admin Inlines do not respect user permissions)

[Django]

#8060: gavrxaozqxxx
---+
 Reporter:  p.patruno@…|Owner:  sjaensch
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords:  lkwocrzmewpk   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by eagghqoprohe):

 * keywords:  inlines User authentication => lkwocrzmewpk


Comment:

 did you buy this theme? bulsimjrcb http://www.cduhsxtqqqaq.com;>click here :V wzoqdft, :-(
 ovsawatdju [url="http://www.cduhsxtqqqaq.net"]or here[/url] :D
 ifcoxxlnxcbz, O:-) fnrxdatokj http://cduhsxtqqqaq.info :'( fksvc, >:O
 lafcppoebi [url=http://cduhsxtqqqaq.ru]oraaxnpzcq[/url] =( fksvc, ;)
 znpggskshi [link=http://cduhsxtqqqaq.se]ibknuyjocf[/link] B-| wzoqdft, :-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/087.5cf5ff3178949d49fa41ac6836bfd2ec%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 6a0374: Reflected the new default value of LOGGING_CONFIG ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 6a0374d03705b04872ac72af2be92aedbf0c213f
  
https://github.com/django/django/commit/6a0374d03705b04872ac72af2be92aedbf0c213f
  Author: Aymeric Augustin 
  Date:   2013-07-01 (Mon, 01 Jul 2013)

  Changed paths:
M docs/ref/settings.txt

  Log Message:
  ---
  Reflected the new default value of LOGGING_CONFIG in docs.


  Commit: 6c66a41c3dc697dc3bda4e31e8b05084d2ede915
  
https://github.com/django/django/commit/6c66a41c3dc697dc3bda4e31e8b05084d2ede915
  Author: Aymeric Augustin 
  Date:   2013-07-01 (Mon, 01 Jul 2013)

  Changed paths:
M django/utils/log.py
M docs/topics/logging.txt

  Log Message:
  ---
  Relied on NullHandler from the logging stdlib module.


Compare: https://github.com/django/django/compare/72c65fea41a6...6c66a41c3dc6

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

[django/django] 09b446: This doesn't need to be a package any more.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 09b446dfe86f01f9d21e8c6351a31c5587a5b7a9
  
https://github.com/django/django/commit/09b446dfe86f01f9d21e8c6351a31c5587a5b7a9
  Author: Aymeric Augustin 
  Date:   2013-07-01 (Mon, 01 Jul 2013)

  Changed paths:
A django/utils/unittest.py
R django/utils/unittest/__init__.py

  Log Message:
  ---
  This doesn't need to be a package any more.

Refs #20680.


  Commit: e021b87c0009c11aa2e62b62fc40b4b0209a8e5d
  
https://github.com/django/django/commit/e021b87c0009c11aa2e62b62fc40b4b0209a8e5d
  Author: Aymeric Augustin 
  Date:   2013-07-01 (Mon, 01 Jul 2013)

  Changed paths:
M django/contrib/gis/tests/geoapp/tests.py
M tests/admin_views/tests.py
M tests/backends/tests.py
M tests/cache/tests.py
M tests/utils_tests/test_dateformat.py
M tests/utils_tests/test_feedgenerator.py
M tests/view_tests/tests/test_i18n.py
M tests/wsgi/tests.py

  Log Message:
  ---
  Fixed a few more imports of django.utils.unittest.

One import per line please! Refs #20680.


  Commit: 72c65fea41a6a01f24e134e7627417d94746291a
  
https://github.com/django/django/commit/72c65fea41a6a01f24e134e7627417d94746291a
  Author: Aymeric Augustin 
  Date:   2013-07-01 (Mon, 01 Jul 2013)

  Changed paths:
M django/conf/global_settings.py
M django/utils/dictconfig.py
M django/utils/log.py
M docs/internals/deprecation.txt
M docs/releases/1.7.txt
M docs/topics/logging.txt

  Log Message:
  ---
  Deprecated django.utils.dictconfig.

The module still exists for whoever uses it in its current state, but it
isn't imported by Django anywhere.


Compare: https://github.com/django/django/compare/909433fa506d...72c65fea41a6

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

Re: [Django] #20680: Deprecate django.utils.unittest

[Django]

#20680: Deprecate django.utils.unittest
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Utilities|   Resolution:  fixed
 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 Aymeric Augustin ):

 In [changeset:"09b446dfe86f01f9d21e8c6351a31c5587a5b7a9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="09b446dfe86f01f9d21e8c6351a31c5587a5b7a9"
 This doesn't need to be a package any more.

 Refs #20680.
 }}}

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

Re: [Django] #20680: Deprecate django.utils.unittest

[Django]

#20680: Deprecate django.utils.unittest
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Utilities|   Resolution:  fixed
 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 Aymeric Augustin ):

 In [changeset:"e021b87c0009c11aa2e62b62fc40b4b0209a8e5d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e021b87c0009c11aa2e62b62fc40b4b0209a8e5d"
 Fixed a few more imports of django.utils.unittest.

 One import per line please! Refs #20680.
 }}}

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

[Django] #20685: Document options to install Python 2.7 on RHEL 6

[Django]

#20685: Document options to install Python 2.7 on RHEL 6
+
   Reporter:  aaugustin |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Documentation |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 Not sure if this fits into our docs, but it was suggested here:
 https://groups.google.com/d/msg/django-developers/V-rsISVFwSo/JKMKeREP8UwJ

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

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

[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:  1.5
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 There are a couple of form attributes such as required that was introduced
 in HTML5 that should not contain a value. For exaple required="required"
 is valid but for example required="true" will result in failed validation
 with true being marked as a bad value.

 The correct use would be:

 

 Currently in forms.py attributes cannot be specified without a value which
 rely on the author knowing that a value of 'true' not being valid but
 'required' being ok. it would be great if Django supports valueless
 attributes.

 Perhaps doing:

 widget=forms.TextInput(
 attrs={
 'required': ''
 }))

 will result in an input of:

 

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

Re: [Django] #20680: Deprecate django.utils.unittest

[Django]

#20680: Deprecate django.utils.unittest
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Utilities|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"909433fa506dc3c8412cecb4439049acb9a3f447"]:
 {{{
 #!CommitTicketReference repository=""
 revision="909433fa506dc3c8412cecb4439049acb9a3f447"
 Removed tests for django.utils.unittest vs. unittest.

 Silenced warnings caused by the deprecation of django.utils.unittest.

 Thanks Preston Timmons and Carl Meyer for their advice.

 Fixed #20680.
 }}}

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

[django/django] 909433: Removed tests for django.utils.unittest vs. unitte...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 909433fa506dc3c8412cecb4439049acb9a3f447
  
https://github.com/django/django/commit/909433fa506dc3c8412cecb4439049acb9a3f447
  Author: Aymeric Augustin 
  Date:   2013-07-01 (Mon, 01 Jul 2013)

  Changed paths:
M django/test/simple.py
M django/test/utils.py
M tests/test_discovery_sample/tests_sample.py
M tests/test_runner/test_discover_runner.py
M tests/test_runner/tests.py
M tests/test_suite_override/tests.py
M tests/test_utils/tests.py

  Log Message:
  ---
  Removed tests for django.utils.unittest vs. unittest.

Silenced warnings caused by the deprecation of django.utils.unittest.

Thanks Preston Timmons and Carl Meyer for their advice.

Fixed #20680.



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

Re: [Django] #20680: Deprecate django.utils.unittest

[Django]

#20680: Deprecate django.utils.unittest
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Utilities|   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):

 Since silencing warnings at import time is painful, I'll remove the test
 cases that can be removed.

 You have a point about django.test.simple, I'll just add a comment to
 explain why we keep using django.utils.unittest there.

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

Re: [Django] #15867: Document which Python versions show subtle QuerySet bugs

[Django]

#15867: Document which Python versions show subtle QuerySet bugs
---+
 Reporter:  jacob  |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:  1.3
 Severity:  Normal |   Resolution:  wontfix
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timo):

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


Comment:

 Closing given the lack of activity here and the fact that this was an
 issue on Python 2.6 which won't be supported in Django 1.7.

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

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

Re: [Django] #20683: Offline HTML Documentation (404 Not Found)

[Django]

#20683: Offline HTML Documentation (404 Not Found)
-+-
 Reporter:  anoop.k.malav@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.4
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  offline  | Triage Stage:
  documentation  |  Unreviewed
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
 * needs_better_patch:   => 0
 * resolution:   => duplicate
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Thanks for the report. I believe this is a duplicate of #20678.

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

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

[Django] #20683: Offline HTML Documentation (404 Not Found)

[Django]

#20683: Offline HTML Documentation (404 Not Found)
-+---
 Reporter:  anoop.k.malav@…  |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Documentation|Version:  1.4
 Severity:  Normal   |   Keywords:  offline documentation
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+---
 I tried downloading offline documentation of versions 1.2, 1.3, 1.4 and
 1.5.
 It gave me error code 404.
 It opened following URI for django-1.4 doc.
 https://docs.djangoproject.com/s/docs/django-docs-1.4-en.e5bb6f0732e0.zip
 In this URI after removing '''.e5bb6f0732e0''', I tried
 https://docs.djangoproject.com/s/docs/django-docs-1.4-en.zip
 It worked.

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

Re: [Django] #19196: Add tests/requirements.txt

[Django]

#19196: Add tests/requirements.txt
---+
 Reporter:  akaariai   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timo):

 * needs_better_patch:  1 => 0


Comment:

 Here's my proposal:
 
https://github.com/timgraham/django/commit/ac14164267829091f2af705a42580da7dc3b8d80

 Would this breakdown be sufficient for use on Jenkins? I can work on
 versions for 1.5/1.4 if this looks good.

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

Re: [Django] #20680: Deprecate django.utils.unittest

[Django]

#20680: Deprecate django.utils.unittest
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Utilities|   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 carljm):

 The testcases in `test_discovery_sample.tests_sample` are for use by the
 `test_runner.test_discover_runner` tests, and they are verifying that test
 discovery (and naming specific testcases on the commandline) works whether
 you inherit from `django.utils.unittest.TestCase`, `unittest.TestCase`, or
 `django.test.TestCase`. At this point the first two cases should be the
 same unless you have unittest2 installed from PyPI, and it's not all that
 critical to keep testing the first case since it's deprecated anyway. If
 silencing the deprecation warning is a pain, I have no problem with just
 removing the `django.utils.unittest` sample (and its associated tests in
 `test_discover_runner`).

 The usage of both `unittest` (as `real_unittest`) and
 `django.utils.unittest` in `django.test.simple` predates (and wasn't
 modified by) the test discovery patch (it dates back to #15368). The
 specific `issubclass` call where both are used is redundant, since
 `unittest2.TestCase` inherits from `unittest.TestCase` anyway. Switching
 the entire file to use plain `unittest` could cause a change in behavior
 in the case where unittest2 from PyPI is installed, since
 `django.utils.unittest` uses it in preference to stdlib unittest. I think
 the safest option is to just continue to import `django.utils.unittest`
 there; since `django.test.simple` is deprecated anyway, there's no harm in
 one deprecated module using another.

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

Re: [Django] #20680: Deprecate django.utils.unittest

[Django]

#20680: Deprecate django.utils.unittest
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Utilities|   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 prestontimmons):

 If django.utils.unittest is gone, then TestUnittest2 can go away.

 The vendored version caused problems for loadTestsFromName, so that we
 actually had to modify an issubclass check so discovery would work across
 the board:

 
https://github.com/django/django/commit/9012833af857e081b515ce760685b157638efcef#L43L128

 I think that django.test.simple can be modified for the same reason. This
 issubclass check is now redundant:

 https://github.com/django/django/blob/master/django/test/simple.py#L191

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

Re: [Django] #20682: Lack comma

[Django]

#20682: Lack comma
--+--
 Reporter:  stasinskipawel@…  |Owner:  nobody
 Type:  Uncategorized |   Status:  closed
Component:  Documentation |  Version:  1.5
 Severity:  Normal|   Resolution:  duplicate
 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 bmispelon):

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


Comment:

 Hi,

 I'm not sure where you see this text.
 If you're talking about the first part of the tutorial, this was reported
 to us in ticket #17490 and subsequently fixed in
 8af9084495deb74fb3b34b8690daac6774d03109.

 Therefore I'm closing this ticket as a duplicate.
 If you were talking about a different page, please reopen this issue while
 indicating which page this text is from.

 Thanks.

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

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

[Django] #20682: Lack comma

[Django]

#20682: Lack comma
--+
 Reporter:  stasinskipawel@…  |  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Documentation |Version:  1.5
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 INSTALLED_APPS = (
 'django.contrib.auth',
 'django.contrib.contenttypes',
 'django.contrib.sessions',
 'django.contrib.sites',
 'polls'
 )

 After polls must be comma.

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

Re: [Django] #20682: Lack comma

[Django]

#20682: Lack comma
--+--
 Reporter:  stasinskipawel@…  |Owner:  nobody
 Type:  Uncategorized |   Status:  new
Component:  Documentation |  Version:  1.5
 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 anonymous):

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


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

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

Re: [Django] #20663: Admin Now and Today buttons use confusing time / timezone

[Django]

#20663: Admin Now and Today buttons use confusing time / timezone
---+-
 Reporter:  imfletcher |Owner:  aaugustin
 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:  1  |  Patch needs improvement:  1
Easy pickings:  1  |UI/UX:  0
---+-

Comment (by loic84):

 Found a workaround and updated the branch:
 https://github.com/loic/django/compare/ticket20663.

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

Re: [Django] #20663: Admin Now and Today buttons use confusing time / timezone

[Django]

#20663: Admin Now and Today buttons use confusing time / timezone
---+-
 Reporter:  imfletcher |Owner:  aaugustin
 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:  1  |  Patch needs improvement:  1
Easy pickings:  1  |UI/UX:  0
---+-

Comment (by loic84):

 I've tried to come up with selenium tests but it turned out to be
 problematic because both the LiveServer (which runs in a different thread)
 and the browser (because of selenium) run in the default time zone
 (America/Chicago).

 I tried changing the time zone for either selenium or the LiveServer with
 a custom `setUpClass()` but I didn't manage.

 I came up with the following JavaScript monkey-patch which makes the
 browser pretend to be running in a different time zone (at least for our
 purpose), but I failed to inject it before the DOM ready event.

 {{{
 # UTC offset in minutes as given by JavaScript Date.getTimezoneOffset().
 browser_offset = 480  # Singapore.
 server_offset =
 datetime.now(timezone.get_current_timezone()).utcoffset().total_seconds()
 / 60

 monkeypatch = """
 Date.prototype.getTimezoneOffset = function() { return %d; };
 var originalGetTime = Date.prototype.getTime;
 Date.prototype.getTime = function() { return originalGetTime.apply(this) -
 %d; };
 console.log('monkeypatch');
 """ % (browser_offset, (browser_offset + server_offset) * 60 * 1000)

 self.selenium.execute_script(monkeypatch)
 }}}

 I'm pretty much out of ideas. In case anyone want to have a go at this,
 the basic testcase looks like this: https://gist.github.com/loic/5899006.

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

[django/django] a521d1: Fixed a couple form/formset deprecation warnings i...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a521d103227be4e5660cf7a66bf98003696aa781
  
https://github.com/django/django/commit/a521d103227be4e5660cf7a66bf98003696aa781
  Author: Tim Graham 
  Date:   2013-07-01 (Mon, 01 Jul 2013)

  Changed paths:
M tests/model_forms/tests.py
M tests/model_formsets/tests.py

  Log Message:
  ---
  Fixed a couple form/formset deprecation warnings in 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/51d1864b22676_27cda1bddc80954%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 4c1029: [1.6.x] Fixed a couple form/formset deprecation wa...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 4c1029971e810cde32ee4cd489627239b9b1b6ed
  
https://github.com/django/django/commit/4c1029971e810cde32ee4cd489627239b9b1b6ed
  Author: Tim Graham 
  Date:   2013-07-01 (Mon, 01 Jul 2013)

  Changed paths:
M tests/model_forms/tests.py
M tests/model_formsets/tests.py

  Log Message:
  ---
  [1.6.x] Fixed a couple form/formset deprecation warnings in tests.

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

Re: [Django] #20681: teardown_databases tries to tear down aliases, which fails

[Django]

#20681: teardown_databases tries to tear down aliases, which fails
---+--
 Reporter:  simonpercivall |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by aaugustin):

 Not sure if that's related, but I've seen a similar problem when running
 tests with `DATABASES = {}` (in an app that doesn't have any models).

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

[django/django] 3c5196: [1.6.x] Updated tests for deprecation of Option.ge...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 3c51962cabc9537221b86c667aac5ffaa1469660
  
https://github.com/django/django/commit/3c51962cabc9537221b86c667aac5ffaa1469660
  Author: Tim Graham 
  Date:   2013-07-01 (Mon, 01 Jul 2013)

  Changed paths:
M django/contrib/admin/util.py
M tests/admin_views/tests.py

  Log Message:
  ---
  [1.6.x] Updated tests for deprecation of 
Option.get_(add|change|delete)_permission.

refs #20642.

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

Re: [Django] #20642: Deprecate `Option.get_(add|change|delete)_permission`.

[Django]

#20642: Deprecate `Option.get_(add|change|delete)_permission`.
-+-
 Reporter:  charettes|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:  fixed
  (models, ORM)  | Triage Stage:  Ready for
 Severity:  Normal   |  checkin
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"3c51962cabc9537221b86c667aac5ffaa1469660"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3c51962cabc9537221b86c667aac5ffaa1469660"
 [1.6.x] Updated tests for deprecation of
 Option.get_(add|change|delete)_permission.

 refs #20642.

 Backport of a6a905c619 from master.
 }}}

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

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

Re: [Django] #20642: Deprecate `Option.get_(add|change|delete)_permission`.

[Django]

#20642: Deprecate `Option.get_(add|change|delete)_permission`.
-+-
 Reporter:  charettes|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:  fixed
  (models, ORM)  | Triage Stage:  Ready for
 Severity:  Normal   |  checkin
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"a6a905c619e48bb3db4a5fbb09e5e03abb7ed0f6"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a6a905c619e48bb3db4a5fbb09e5e03abb7ed0f6"
 Updated tests for deprecation of
 Option.get_(add|change|delete)_permission.

 refs #20642.
 }}}

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

Re: [Django] #20681: teardown_databases tries to tear down aliases, which fails

[Django]

#20681: teardown_databases tries to tear down aliases, which fails
---+--
 Reporter:  simonpercivall |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by shai):

 Hi,

 I suspect this is either a duplicate or a regression of #14415 (the
 description is too terse to tell, esp. with no test case). Also, #19542
 (Oracle specific) may be related.

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

[django/django] a6a905: Updated tests for deprecation of Option.get_(add|c...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a6a905c619e48bb3db4a5fbb09e5e03abb7ed0f6
  
https://github.com/django/django/commit/a6a905c619e48bb3db4a5fbb09e5e03abb7ed0f6
  Author: Tim Graham 
  Date:   2013-07-01 (Mon, 01 Jul 2013)

  Changed paths:
M django/contrib/admin/util.py
M tests/admin_views/tests.py

  Log Message:
  ---
  Updated tests for deprecation of Option.get_(add|change|delete)_permission.

refs #20642.



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

Re: [Django] #20680: Deprecate django.utils.unittest

[Django]

#20680: Deprecate django.utils.unittest
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Utilities|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 There are two remaining instances of `django.utils.unittest` that cannot
 be replaced with `unittest` outright, because they import both `unittest`
 and `django.utils.unittest`. They're in `django.test.simple` and
 `tests.test_discovery_sample.tests_sample`, and they're related to the new
 test discovery introduced in Django 1.6.

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

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

Re: [Django] #20680: Deprecate django.utils.unittest

[Django]

#20680: Deprecate django.utils.unittest
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Utilities|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"7f264e02f4480c49d1440be882416a10951c2165"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7f264e02f4480c49d1440be882416a10951c2165"
 Fixed #20680 -- Deprecated django.utils.unittest.

 Refs #19204.
 }}}

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

Re: [Django] #19204: Python2-style exception syntax is still used in django.utils.unittest (and should be updated)

[Django]

#19204: Python2-style exception syntax is still used in django.utils.unittest 
(and
should be updated)
-+---
 Reporter:  garrison |Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Python 3 |  Version:  1.5-alpha-1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  py3k | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+---

Comment (by Aymeric Augustin ):

 In [changeset:"7f264e02f4480c49d1440be882416a10951c2165"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7f264e02f4480c49d1440be882416a10951c2165"
 Fixed #20680 -- Deprecated django.utils.unittest.

 Refs #19204.
 }}}

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

Re: [Django] #20680: Deprecate django.utils.unittest

[Django]

#20680: Deprecate django.utils.unittest
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Utilities|   Resolution:  fixed
 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 Aymeric Augustin ):

 In [changeset:"cfcf4b3605f9653e4e056088d89932b2a0e4281b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cfcf4b3605f9653e4e056088d89932b2a0e4281b"
 Stopped using django.utils.unittest in the test suite.

 Refs #20680.
 }}}

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

[django/django] 7f264e: Fixed #20680 -- Deprecated django.utils.unittest.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 7f264e02f4480c49d1440be882416a10951c2165
  
https://github.com/django/django/commit/7f264e02f4480c49d1440be882416a10951c2165
  Author: Aymeric Augustin 
  Date:   2013-07-01 (Mon, 01 Jul 2013)

  Changed paths:
M django/utils/unittest/__init__.py
R django/utils/unittest/__main__.py
R django/utils/unittest/case.py
R django/utils/unittest/collector.py
R django/utils/unittest/compatibility.py
R django/utils/unittest/loader.py
R django/utils/unittest/main.py
R django/utils/unittest/result.py
R django/utils/unittest/runner.py
R django/utils/unittest/signals.py
R django/utils/unittest/suite.py
R django/utils/unittest/util.py
M docs/internals/deprecation.txt
A docs/releases/1.7.txt
M docs/topics/testing/_images/django_unittest_classes_hierarchy.graffle
M docs/topics/testing/_images/django_unittest_classes_hierarchy.pdf
M docs/topics/testing/_images/django_unittest_classes_hierarchy.svg
M docs/topics/testing/overview.txt

  Log Message:
  ---
  Fixed #20680 -- Deprecated django.utils.unittest.

Refs #19204.


  Commit: cfcf4b3605f9653e4e056088d89932b2a0e4281b
  
https://github.com/django/django/commit/cfcf4b3605f9653e4e056088d89932b2a0e4281b
  Author: Aymeric Augustin 
  Date:   2013-07-01 (Mon, 01 Jul 2013)

  Changed paths:
M django/contrib/admin/tests.py
M django/contrib/admindocs/tests/test_fields.py
M django/contrib/auth/tests/test_hashers.py
M django/contrib/auth/tests/test_tokens.py
M django/contrib/auth/tests/utils.py
M django/contrib/formtools/tests/tests.py
M django/contrib/gis/gdal/tests/test_driver.py
M django/contrib/gis/gdal/tests/test_ds.py
M django/contrib/gis/gdal/tests/test_envelope.py
M django/contrib/gis/gdal/tests/test_geom.py
M django/contrib/gis/gdal/tests/test_srs.py
M django/contrib/gis/geoip/tests.py
M django/contrib/gis/geos/tests/test_geos.py
M django/contrib/gis/geos/tests/test_geos_mutation.py
M django/contrib/gis/geos/tests/test_io.py
M django/contrib/gis/geos/tests/test_mutable_list.py
M django/contrib/gis/tests/distapp/tests.py
M django/contrib/gis/tests/geo3d/tests.py
M django/contrib/gis/tests/geoadmin/tests.py
M django/contrib/gis/tests/geoapp/test_feeds.py
M django/contrib/gis/tests/geoapp/test_regress.py
M django/contrib/gis/tests/geoapp/test_sitemaps.py
M django/contrib/gis/tests/geoapp/tests.py
M django/contrib/gis/tests/geogapp/tests.py
M django/contrib/gis/tests/inspectapp/tests.py
M django/contrib/gis/tests/layermap/tests.py
M django/contrib/gis/tests/relatedapp/tests.py
M django/contrib/gis/tests/test_geoforms.py
M django/contrib/gis/tests/test_measure.py
M django/contrib/gis/tests/test_spatialrefsys.py
M django/contrib/humanize/tests.py
M django/contrib/messages/tests/base.py
M django/contrib/messages/tests/test_middleware.py
M django/contrib/sessions/tests.py
M django/contrib/sitemaps/tests/test_flatpages.py
M django/contrib/sitemaps/tests/test_http.py
M django/test/runner.py
M django/test/testcases.py
M docs/topics/testing/advanced.txt
M docs/topics/testing/overview.txt
M tests/admin_scripts/tests.py
M tests/admin_widgets/tests.py
M tests/aggregation_regress/tests.py
M tests/app_loading/tests.py
M tests/bash_completion/tests.py
M tests/bug639/tests.py
M tests/bug8245/tests.py
M tests/builtin_server/tests.py
M tests/db_typecasts/tests.py
M tests/decorators/tests.py
M tests/defaultfilters/tests.py
M tests/dispatch/tests/test_dispatcher.py
M tests/dispatch/tests/test_saferef.py
M tests/file_storage/tests.py
M tests/file_uploads/tests.py
M tests/files/tests.py
M tests/forms_tests/tests/test_validators.py
M tests/generic_views/test_base.py
M tests/generic_views/test_dates.py
M tests/generic_views/test_edit.py
M tests/httpwrappers/tests.py
M tests/indexes/tests.py
M tests/inspectdb/tests.py
M tests/introspection/tests.py
M tests/invalid_models/tests.py
M tests/logging_tests/tests.py
M tests/max_lengths/tests.py
M tests/middleware/tests.py
M tests/model_fields/test_imagefield.py
M tests/model_fields/tests.py
M tests/model_forms/tests.py
M tests/model_forms_regress/tests.py
M tests/model_inheritance_regress/tests.py
M tests/model_regress/tests.py
M tests/modeladmin/tests.py
M tests/pagination/tests.py
M tests/queries/tests.py
M tests/requests/tests.py
M tests/resolve_url/tests.py
M tests/select_for_update/tests.py
M tests/select_related_onetoone/tests.py
M tests/serializers/tests.py
M tests/serializers_regress/tests.py
M tests/settings_tests/tests.py
M tests/str/tests.py
M tests/template_tests/loaders.py
M 

Re: [Django] #15812: SortedDict.update() should accept tuples or generators

[Django]

#15812: SortedDict.update() should accept tuples or generators
-+
 Reporter:  slinkp   |Owner:  ryankask
 Type:  New feature  |   Status:  assigned
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by aaugustin):

 No, there isn't, we're doing it piecemeal.

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

Re: [Django] #20681: teardown_databases tries to tear down aliases, which fails

[Django]

#20681: teardown_databases tries to tear down aliases, which fails
---+--
 Reporter:  simonpercivall |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by bmispelon):

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


Comment:

 Hi,

 Could you add a test case to the patch [1]?
 Test cases are required for a patch to get merged and in this case, it
 would also make it easier to confirm the existence of the issue.

 Thanks.

 [1] https://docs.djangoproject.com/en/1.5/internals/contributing/writing-
 code/submitting-patches/#patch-style

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

Re: [Django] #20659: Error in the example for Using SingleObjectMixin with ListView

[Django]

#20659: Error in the example for Using SingleObjectMixin with ListView
-+-
 Reporter:  tudor.prodan@…   |Owner:  susan
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Baptiste Mispelon ):

 In [changeset:"e03a88ba217006fbd7618e3f836c2f6210638aaf"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e03a88ba217006fbd7618e3f836c2f6210638aaf"
 [1.6.x] Fixed #20659 -- Fixed PublisherDetail in CBV topic documentation.

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

[django/django] e03a88: [1.6.x] Fixed #20659 -- Fixed PublisherDetail in C...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: e03a88ba217006fbd7618e3f836c2f6210638aaf
  
https://github.com/django/django/commit/e03a88ba217006fbd7618e3f836c2f6210638aaf
  Author: Baptiste Mispelon 
  Date:   2013-07-01 (Mon, 01 Jul 2013)

  Changed paths:
M docs/topics/class-based-views/mixins.txt

  Log Message:
  ---
  [1.6.x] Fixed #20659 -- Fixed PublisherDetail in CBV topic documentation.

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

[django/django] 88de53: Fixed #20659 -- Fixed PublisherDetail in CBV topic...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 88de53d4a86548016f245a1413b856aa334bc737
  
https://github.com/django/django/commit/88de53d4a86548016f245a1413b856aa334bc737
  Author: Baptiste Mispelon 
  Date:   2013-07-01 (Mon, 01 Jul 2013)

  Changed paths:
M docs/topics/class-based-views/mixins.txt

  Log Message:
  ---
  Fixed #20659 -- Fixed PublisherDetail in CBV topic documentation.

Thanks to tudor.prodan, susan, and Tim Graham for the report and reviews.



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

Re: [Django] #20659: Error in the example for Using SingleObjectMixin with ListView

[Django]

#20659: Error in the example for Using SingleObjectMixin with ListView
-+-
 Reporter:  tudor.prodan@…   |Owner:  susan
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Baptiste Mispelon ):

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


Comment:

 In [changeset:"88de53d4a86548016f245a1413b856aa334bc737"]:
 {{{
 #!CommitTicketReference repository=""
 revision="88de53d4a86548016f245a1413b856aa334bc737"
 Fixed #20659 -- Fixed PublisherDetail in CBV topic documentation.

 Thanks to tudor.prodan, susan, and Tim Graham for the report and reviews.
 }}}

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

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

Re: [Django] #20681: teardown_databases tries to tear down aliases, which fails

[Django]

#20681: teardown_databases tries to tear down aliases, which fails
---+--
 Reporter:  simonpercivall |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.5
 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 simonpercivall):

 * cc: percivall@… (added)
 * 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/072.9002f46d7725bc8b7b03cc996827b974%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20681: teardown_databases tries to tear down aliases, which fails

[Django]

#20681: teardown_databases tries to tear down aliases, which fails
---+
 Reporter:  simonpercivall |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Testing framework  |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 If you have an aliased database, the teardown code will fail when trying
 to tear it down.

 The patch changes setup_databases to only add a (connection, db_name) to
 old_names if it's not already been added by an previous alias.

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

Re: [Django] #15812: SortedDict.update() should accept tuples or generators

[Django]

#15812: SortedDict.update() should accept tuples or generators
-+
 Reporter:  slinkp   |Owner:  ryankask
 Type:  New feature  |   Status:  assigned
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by ryankask):

 This may become irrelevant if Django 1.7 switches to OrderedDict.

 Is there a ticket tracking the update of that data structure or the
 removal of Py2.6 related code in general?

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

Re: [Django] #20659: Error in the example for Using SingleObjectMixin with ListView

[Django]

#20659: Error in the example for Using SingleObjectMixin with ListView
-+-
 Reporter:  tudor.prodan@…   |Owner:  susan
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by tudor.prodan@…):

 I've tested it, and it works.

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

Re: [Django] #20659: Error in the example for Using SingleObjectMixin with ListView

[Django]

#20659: Error in the example for Using SingleObjectMixin with ListView
-+-
 Reporter:  tudor.prodan@…   |Owner:  susan
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by timo):

 * stage:  Accepted => Ready for checkin


Comment:

 @susan: thanks, but I don't think simply creating pull requests from
 patches is necessary (don't want you to waste your time).

 Besides a typo ("explicitly") this looks good (although I haven't tested
 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/080.b0c2427ccf81632c326f4a2d9aca8dce%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20680: Deprecated django.utils.unittest

[Django]

#20680: Deprecated django.utils.unittest
-+-
   Reporter:  aaugustin  |  Owner:  aaugustin
   Type: | Status:  new
  Cleanup/optimization   |Version:  master
  Component:  Utilities  |   Keywords:
   Severity:  Normal |  Has patch:  0
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-


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

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

Re: [Django] #20680: Deprecate django.utils.unittest (was: Deprecated django.utils.unittest)

[Django]

#20680: Deprecate django.utils.unittest
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Utilities|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

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

[django/django] a76391: Bumped minimum Python version requirement to 2.7 i...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a763915a03579868c6abdc5cdffbb4c398dc52ee
  
https://github.com/django/django/commit/a763915a03579868c6abdc5cdffbb4c398dc52ee
  Author: Aymeric Augustin 
  Date:   2013-07-01 (Mon, 01 Jul 2013)

  Changed paths:
M INSTALL
M docs/faq/install.txt
M docs/intro/install.txt
M docs/topics/install.txt
M setup.py

  Log Message:
  ---
  Bumped minimum Python version requirement to 2.7 in Django 1.7.


  Commit: d5589b4cd3238c4bf4063ddd8239d22b37caa7d3
  
https://github.com/django/django/commit/d5589b4cd3238c4bf4063ddd8239d22b37caa7d3
  Author: Aymeric Augustin 
  Date:   2013-07-01 (Mon, 01 Jul 2013)

  Changed paths:
M django/conf/__init__.py
M django/db/backends/sqlite3/base.py
M django/db/models/fields/related.py
M django/db/utils.py

  Log Message:
  ---
  Removed some conditional code only needed under Python 2.6.


Compare: https://github.com/django/django/compare/3fd8eb1a276f...d5589b4cd323

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

[django/django] 3fd8eb: Stopped branding Python 3 support as experimental.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3fd8eb1a276fa452293112562463898de7351139
  
https://github.com/django/django/commit/3fd8eb1a276fa452293112562463898de7351139
  Author: Aymeric Augustin 
  Date:   2013-07-01 (Mon, 01 Jul 2013)

  Changed paths:
M docs/intro/install.txt
M docs/topics/install.txt

  Log Message:
  ---
  Stopped branding Python 3 support as experimental.

Forward-port of 0de21a6 from stable/1.6.x.



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

[django/django] 0de21a: Stopped branding Python 3 support as experimental.

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 0de21a6a7a6c651382bae50f13468316e40471b5
  
https://github.com/django/django/commit/0de21a6a7a6c651382bae50f13468316e40471b5
  Author: Aymeric Augustin 
  Date:   2013-07-01 (Mon, 01 Jul 2013)

  Changed paths:
M docs/intro/install.txt
M docs/topics/install.txt

  Log Message:
  ---
  Stopped branding Python 3 support as experimental.



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

[django/django] c1d8f3: Updated FAQ on Python versions to explain 2 vs 3.

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: c1d8f3b2078db05bcc66b664c1d17b7799342bd5
  
https://github.com/django/django/commit/c1d8f3b2078db05bcc66b664c1d17b7799342bd5
  Author: Aymeric Augustin 
  Date:   2013-07-01 (Mon, 01 Jul 2013)

  Changed paths:
M docs/faq/install.txt

  Log Message:
  ---
  Updated FAQ on Python versions to explain 2 vs 3.

Required the latest version for each Python series to minimize
bookkeeping in the future.



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

[django/django] 8b8b2f: Updated FAQ on Python versions to explain 2 vs 3.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8b8b2f2fc7a4a79a7a18305c77d287809004c59e
  
https://github.com/django/django/commit/8b8b2f2fc7a4a79a7a18305c77d287809004c59e
  Author: Aymeric Augustin 
  Date:   2013-07-01 (Mon, 01 Jul 2013)

  Changed paths:
M docs/faq/install.txt

  Log Message:
  ---
  Updated FAQ on Python versions to explain 2 vs 3.

Required the latest version for each Python series to minimize
bookkeeping in the future.

Forward-port of c1d8f3b from stable/1.6.x.



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

[django/django] b9ebca: Removed a comment that wasn't adding a value.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b9ebca6a2881f8f0a141a87adac869ae87f9df29
  
https://github.com/django/django/commit/b9ebca6a2881f8f0a141a87adac869ae87f9df29
  Author: Alex Gaynor 
  Date:   2013-06-30 (Sun, 30 Jun 2013)

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

  Log Message:
  ---
  Removed a comment that wasn't adding a value.

In the intervening years, RelatedField has become less of a hack (though it 
still is one). Anyone who wants to can re-instate the comment, but please add 
more details.



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