Re: [Django] #542: krdyvfodqypm (was: qefwwmebuxfl)

[Django]

#542: krdyvfodqypm
-+-
 Reporter:  Jason Huggins|Owner:  wilson
 Type:  enhancement  |   Status:  closed
Component:  contrib.admin|  Version:  1.5-rc-2
 Severity:  trivial  |   Resolution:  wontfix
 Keywords:  inyqvajmkchb | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by isyuioarylsn):

 * keywords:  wwyxasrqihqz => inyqvajmkchb


Comment:

 suncoast casino http://grimmschule.info/scripte/galerie/modules/picinfo.php?sort=0=9659=6062;>http://playcasinoslotmachines.weebly.com/
 8-| list casino games, casinos in kentucky, O:-) http://www.web-
 nice.com/qj/shownews.asp?id=7594">europalace casino >:O connecticut
 casino hotels, online casinos that accept paypal, >:O http://playcasinoslotmachines.weebly.com/;>mirage casino ._.
 texas casino las vegas, foxwood resort and casino, B-| http://playtopusaonlinecasinos.weebly.com/;>wholesale casino
 supplies -_- casino bonus usa, Read Full Article, :-/ http://www.ezzhelmy.com/wordpress/?p=5674;>new casino in md O:-)
 casinos in gulfport mississippi, crown casino number, xD http://www.bsscomputing.com/blog/%C2%BFque-es-
 rss/Page-2771.html">pompeii casino game :D casino theme decorations,
 eurogrand casino, :'(

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

Re: [Django] #542: rjplirgbaxlz (was: [patch] Add an "or cancel" link to add, edit, and delete admin views.)

[Django]

#542: rjplirgbaxlz
-+-
 Reporter:  Jason Huggins|Owner:  wilson
 Type:  enhancement  |   Status:  closed
Component:  contrib.admin|  Version:  1.5-rc-2
 Severity:  trivial  |   Resolution:  wontfix
 Keywords:  bvbvehlxsqjd | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by ztutsqggxsnr):

 * keywords:  cancel link => bvbvehlxsqjd
 * ui_ux:   => 0
 * version:   => 1.5-rc-2
 * easy:   => 0


Comment:

 resorts casino http://www.csape.net/qk/jrzs/html/book.asp?id=1190;>casino
 golden :-X useful site, excalibur casino las vegas, 8-| http://playtopusaonlinecasinos.weebly.com/;>no deposit online casino
 codes :[ play online casinos for real money, casinos in california,
 >:o http://usonlinecasinosgames.weebly.com/;>casino louisiana
 3:) choctaw casino resort, my link, >:-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/071.f45aa05c6c3d539957635e05f8c3430a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #542: xdwqmkyvnnvu (was: emnfdtmdxsus)

[Django]

#542: xdwqmkyvnnvu
-+-
 Reporter:  Jason Huggins|Owner:  wilson
 Type:  enhancement  |   Status:  closed
Component:  contrib.admin|  Version:  1.0-alpha
 Severity:  trivial  |   Resolution:  wontfix
 Keywords:  hsojynrconrd | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by iflcktagilpl):

 * keywords:  mkalehkzpiki => hsojynrconrd


Comment:

 lucky red casino no deposit codes http://playtopusaonlinecasinos.weebly.com/;>top usa online
 casinos <3 casino resorts in connecticut, playing poker in a casino,
 :3 http://usonlinecasinosgames.weebly.com/;>play casino card game
 online >: no deposit casino coupon, online casino reviews, :D

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

Re: [Django] #19607: prefetch_related crash

[Django]

#19607: prefetch_related crash
-+-
 Reporter:  av@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:  prefetch |  Unreviewed
  prefetch_related   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by tswaterman):

 thanks!  this one was confusing me to no end.

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

[Django] #20744: Docs imply that forms.Field.__init__ accepts any keyword arguments

[Django]

#20744: Docs imply that forms.Field.__init__ accepts any keyword arguments
---+
 Reporter:  gthb   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 At https://docs.djangoproject.com/en/dev/ref/forms/fields/ there is this:

 {{{
 class Field(**kwargs)
 }}}

 with no stated constraints on `kwargs`, thus implying (incorrectly) that
 any keyword argument can safely be passed to the `forms.Field`
 constructor.

 That leads to code which worked in previous Django versions but regresses
 in the current version. The case I have in mind is
 [https://github.com/jezdez/django-
 
authority/blob/11461f808160e09bb992f9c602c342718892bb6a/authority/admin.py#L28-L33
 in django-authority's admin.py] where the `kwargs` passed to
 `formfield_callback` (which can include `request`) are passed on to
 `Field.formfield`, whose documentation says “All of the `kwargs`
 dictionary is passed directly to the form field’s `__init__()` method” ...
 and that `__init__` method ''can't'' include `request`. So upgrading
 Django yields this somewhat tricky-to-troubleshoot error in a django-
 authority admin action:

 {{{
 TypeError: __init__() got an unexpected keyword argument 'request'

   ...
   File "django/forms/models.py", line 170, in fields_for_model
 formfield = formfield_callback(f, **kwargs)
   File "authority/admin.py", line 33, in formfield_for_dbfield
 return db_field.formfield(**kwargs)
   File "django/db/models/fields/__init__.py", line 646, in formfield
 return super(CharField, self).formfield(**defaults)
   File "django/db/models/fields/__init__.py", line 499, in formfield
 return form_class(**defaults)
   File "django/forms/fields.py", line 188, in __init__
 super(CharField, self).__init__(*args, **kwargs)
 }}}

 At some point in this chain, the `request` keyword argument must be popped
 out. Presumably directly before the call to `Field.formfield`. In any
 case, this requirement should be documented.

 (Or `forms.Field.__init__` could be changed to tolerate and ignore unknown
 keyword arguments. But that's a riskier change.)

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

Re: [Django] #542: uynauonbkyaf (was: atoxyimqmtqv)

[Django]

#542: uynauonbkyaf
-+-
 Reporter:  Jason Huggins|Owner:  wilson
 Type:  enhancement  |   Status:  closed
Component:  contrib.admin|  Version:  1.5
 Severity:  trivial  |   Resolution:  wontfix
 Keywords:  qtzcyhmwfpjp | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by uxhtaegttbfu):

 * keywords:  ubxcionsvvob => qtzcyhmwfpjp


Comment:

 red rock casino in las vegas http://moneygamingslot.weebly.com/;>best no deposit bonus casino
 :( harrah s casino, casino dealer, :-/ http://bestonlineslotsgame.weebly.com/;>best online slots <3 las
 vegas new casinos, check my site, :-(

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

Re: [Django] #542: atoxyimqmtqv (was: [patch] Add an "or cancel" link to add, edit, and delete admin views.)

[Django]

#542: atoxyimqmtqv
-+-
 Reporter:  Jason Huggins|Owner:  wilson
 Type:  enhancement  |   Status:  closed
Component:  contrib.admin|  Version:  1.5
 Severity:  trivial  |   Resolution:  wontfix
 Keywords:  ubxcionsvvob | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by mumoaygvsnva):

 * keywords:  cancel link => ubxcionsvvob
 * ui_ux:   => 0
 * version:   => 1.5
 * easy:   => 0


Comment:

 hardrock casino las vegas http://g-soft.sakura.ne.jp/cgi-
 bin/bbsV2.cgi?user_hp=libero_no=3948">golden moon casino -_-
 maryland live casino - home, soboba casino, >:-O http://bestonlineslotsgame.weebly.com/;>casino codes no deposit
 :3 coushatta casino, casino world, B| http://moneygamingslot.weebly.com/;>download casino >:-O no
 deposit casino bonus codes 2011, casino in maryland, B-|

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

Re: [Django] #15574: IndexError: list index out of range caused by inline formsets

[Django]

#15574: IndexError: list index out of range caused by inline formsets
+
 Reporter:  poswald |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Forms   |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  inline formset  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by joseph@…):

 * cc: joseph@… (added)


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

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

Re: [Django] #20740: GenericIPAddressField does not pass protocol to formfield()

[Django]

#20740: GenericIPAddressField does not pass protocol to formfield()
-+
 Reporter:  Jeff250  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+

Comment (by timo):

 Thanks Jeff.

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

[django/django] 7f2105: [1.6.x] Fixed backport of #20740

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 7f210563ab90d4d3957e7e1efc5b102777357e8b
  
https://github.com/django/django/commit/7f210563ab90d4d3957e7e1efc5b102777357e8b
  Author: Tim Graham 
  Date:   2013-07-12 (Fri, 12 Jul 2013)

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

  Log Message:
  ---
  [1.6.x] Fixed backport of #20740



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

Re: [Django] #20740: GenericIPAddressField does not pass protocol to formfield()

[Django]

#20740: GenericIPAddressField does not pass protocol to formfield()
-+
 Reporter:  Jeff250  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+

Comment (by Jeff250):

 Tim, the 1.6.x backport isn't quite right, since the 1.6.x constructor
 doesn't already set self.protocol.  I've attached a trivial patch against
 1.6.x that should fix 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/065.d6c420399ee7e3a5e193238ec2da798d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20740: GenericIPAddressField does not pass protocol to formfield()

[Django]

#20740: GenericIPAddressField does not pass protocol to formfield()
-+
 Reporter:  Jeff250  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+

Comment (by Tim Graham ):

 In [changeset:"45fab74561a2b339cde922c196ab3ccf998bad10"]:
 {{{
 #!CommitTicketReference repository=""
 revision="45fab74561a2b339cde922c196ab3ccf998bad10"
 [1.6.x] Fixed #20740 -- GenericIPAddressField should pass protocol to
 formfield()

 Thanks Jeff250.

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

[django/django] f2cb94: Fixed #20740 -- GenericIPAddressField should pass ...

[GitHub]

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

  Changed paths:
M django/db/models/fields/__init__.py
M tests/model_fields/tests.py

  Log Message:
  ---
  Fixed #20740 -- GenericIPAddressField should pass protocol to formfield()

Thanks Jeff250.



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

[django/django] 45fab7: [1.6.x] Fixed #20740 -- GenericIPAddressField shou...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 45fab74561a2b339cde922c196ab3ccf998bad10
  
https://github.com/django/django/commit/45fab74561a2b339cde922c196ab3ccf998bad10
  Author: Tim Graham 
  Date:   2013-07-12 (Fri, 12 Jul 2013)

  Changed paths:
M django/db/models/fields/__init__.py
M tests/model_fields/tests.py

  Log Message:
  ---
  [1.6.x] Fixed #20740 -- GenericIPAddressField should pass protocol to 
formfield()

Thanks Jeff250.

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

Re: [Django] #20740: GenericIPAddressField does not pass protocol to formfield()

[Django]

#20740: GenericIPAddressField does not pass protocol to formfield()
-+
 Reporter:  Jeff250  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"f2cb94f1c0dc98663e7d493411bf9b82d1894559"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f2cb94f1c0dc98663e7d493411bf9b82d1894559"
 Fixed #20740 -- GenericIPAddressField should pass protocol to formfield()

 Thanks Jeff250.
 }}}

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

Re: [Django] #19153: Deprecate GzipMiddleware

[Django]

#19153: Deprecate GzipMiddleware
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  HTTP handling |  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 timo):

 Should we mark this as "won't fix" then?

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

Re: [Django] #542: lbjwpvblnuks (was: [patch] Add an "or cancel" link to add, edit, and delete admin views.)

[Django]

#542: lbjwpvblnuks
-+-
 Reporter:  Jason Huggins|Owner:  wilson
 Type:  enhancement  |   Status:  closed
Component:  contrib.admin|  Version:
 Severity:  trivial  |  1.5-alpha-1
 Keywords:  oryaypghqwqd |   Resolution:  wontfix
Has patch:  1| Triage Stage:  Design
  Needs tests:  0|  decision needed
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by lxddqnfdceae):

 * keywords:  cancel link => oryaypghqwqd
 * ui_ux:   => 0
 * version:   => 1.5-alpha-1
 * easy:   => 0


Comment:

 party supplies casino http://www.s24service.co.kr/bbs/bbs_view.php?idx=8;>las vegas casino
 signs ;) game of casino, online slots casinos, :[ http://playbestslotsonlinegames.weebly.com/;>best slots online
 :V rated online casinos, no deposit casinos bonus codes, :) http://znanie.cogia.net/index.php?t=materials=527;>real money
 slots xD online vegas casino games, online slots casino, :-( http://www.festspielhaus-
 
muenchen.de/bildershow/modules/picinfo.php?bild=1043=wer_hat_angst_vorm_schwarzen_mann">gambling
 casinos online B| clay casino chips, promotion codes double down
 casino, >:o http://playrealmoneyslotsgames.weebly.com/;>real
 money slots 8-| real casino slots, real casino slots, :D

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

Re: [Django] #13142: Add support for SSL connections in core.mail.backends.smtp

[Django]

#13142: Add support for SSL connections in core.mail.backends.smtp
-+--
 Reporter:  serg.partizan@…  |Owner:  jwmayfield
 Type:  New feature  |   Status:  closed
Component:  Core (Mail)  |  Version:  master
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+--
Changes (by claudep):

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


Comment:

 I opened a new ticket dedicated to the keyfile/certfile issue: #20743

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

[Django] #20743: Support keyfile/certfile in SMTP connections

[Django]

#20743: Support keyfile/certfile in SMTP connections
---+
   Reporter:  claudep  |  Owner:  nobody
   Type:  New feature  | Status:  new
  Component:  Core (Mail)  |Version:  master
   Severity:  Normal   |   Keywords:
   Triage Stage:  Accepted |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 This was initially included in a patch on #13142
 (https://github.com/django/django/pull/347), but the SSL support was added
 in commit for #17471.

 `keyfile`/`certfile` are optional parameters to either
 [http://docs.python.org/2/library/smtplib.html#smtplib.SMTP.starttls
 `SMTP.starttls`] or
 [http://docs.python.org/2/library/smtplib.html#smtplib.SMTP_SSL
 `smtplib.SMTP_SSL`].

 Is there another way than adding two new settings?

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

Re: [Django] #20740: GenericIPAddressField does not pass protocol to formfield()

[Django]

#20740: GenericIPAddressField does not pass protocol to formfield()
-+
 Reporter:  Jeff250  |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:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+

Comment (by Jeff250):

 Sure, I've just attached a patch including tests.

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

Re: [Django] #9532: Add min_num on formsets (was: min_num on formsets)

[Django]

#9532: Add min_num on formsets
-+-
 Reporter:  gsf  |Owner:  yokomizor
 Type:  New feature  |   Status:  assigned
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
-+-
Changes (by timo):

 * cc: timograham@… (added)
 * needs_better_patch:  0 => 1
 * needs_docs:  0 => 1


Comment:

 Thanks, the patch no longer merges cleanly so it needs to be rebased. It
 also needs documentation including a mention in the 1.7 release notes. If
 you could add that, I will try to review and commit 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/061.57d6498e6d6206efbeae5cd83477884b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #542: oxjyrqisiiwe (was: [patch] Add an "or cancel" link to add, edit, and delete admin views.)

[Django]

#542: oxjyrqisiiwe
-+-
 Reporter:  Jason Huggins|Owner:  wilson
 Type:  enhancement  |   Status:  closed
Component:  contrib.admin|  Version:  1.1-rc
 Severity:  trivial  |   Resolution:  wontfix
 Keywords:  gkidgsikjhnj | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by sdksekufgktb):

 * keywords:  cancel link => gkidgsikjhnj
 * version:   => 1.1-rc
 * easy:   => 0
 * ui_ux:   => 0


Comment:

 casino playing card http://playcanadianonlinecasinos.weebly.com/;>check here :-/
 casino slots no download, golden pony casino, =) http://playrealmoneyslotsgames.weebly.com/;>real money slots >:o
 las vegas casino chip, blog here, :) http://powerfulnoise.rulez.jp/cgi/bbs/noisy_bbs.cgi?com%2525252525252525253C%25252525252525252F%252525252525253C%25252525252%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%252525C2%252525A0%252525C2%252525A0%252525C2%252525A0%252525C2%252525A0%252525C2%252525A0%2525253Cstrong%2525253E%252525E0%252525B9%25252580%252525E0%252525B8%252525A1%252525E0%252525B8%252525B7%252525E0%252525B9%25252588%252525E0%252525B8%252525AD%25252520%25253A%25252520%2525253C%25252Fstrong%2525253E%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%252525E0%252525B8%252525A7%252525E0%252525B8%252525B1%252525E0%252525B8%25252599%252525E0%252525B8%25252597%252525E0%252525B8%252525B5%252525E0%252525B9%25252588%2525252027%25252520%252525E0%252525B8%2525259E%252525E0%252525B8%252525A4%252525E0%252525B8%252525A9%252525E0%252525B8%252525A0%252525E0%252525B8%252525B2%252525E0%252525B8%25252584%252525E0%252525B8%252525A1%252525202556%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%2525252008%25253A53%25253A51%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%2525253C%25252Fspan%2525253E%2525253C%25252Ftd%2525253E%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%2525253C%25252Ftr%2525253E%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%2525253C%25252Ftable%2525253E%2525253C%25252Ftd%2525253E%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%2525253C%25252Ftr%2525253E%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%2525253C%25252Ftable%2525253E%2525253C%25252Ftd%2525253E%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%2525253C%25252Ftr%2525253E%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%2525253Ctr%2525253E%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%2525253Ctd%2525253E%252525C2%252525A0%2525253C%25252Ftd%2525253E%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%2525253C%25252Ftr%2525253E%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%2525253C%25252Ftable%2525253E%2525253C%25252Ftd%2525253E%25252520%25252520%25252520%25252520%25252520%25252520%2525253C%25252Ftr%2525253E%25252520%25252520%25252520%25252520%25252520%25252520%2525253Ctr%2525253E%25252520%25252520%25252520%25252520%25252520%25252520%25252520%25252520%2525253Ctd%2525253E%2525253Ca%25252520href=;>popular
 online casinos :-X largest online casino, mirage casino, =) http://www.stvlangendorf.ch/showit/2005/modules/picinfo.php?bild=4933=baenzenjass;>link
 xD online usa casinos, ip casino resort biloxi, O:) http://m-sahm.de/mgv/showit/modules/picinfo.php?sort==7741=sonntag;>palace
 station casinos :D cool cats casino, casino dice game rules, >:-O

-- 
Ticket URL: 

Re: [Django] #10414: select_related ignores unrecognized fields

[Django]

#10414: select_related ignores unrecognized fields
-+-
 Reporter:  trebor74hr   |Owner:
 Type:  Bug  |  trebor74hr
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:
 Severity:  Normal   |   Resolution:
 Keywords:  select_related   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

 * cc: timograham@… (added)
 * needs_better_patch:  0 => 1


Comment:

 I don't think the patch is correct as it causes several tests to fail,
 including some in `select_related_onetoone` and `known_related_objects`.

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

Re: [Django] #13137: GenericForeignKey does not allow content type PK 0

[Django]

#13137: GenericForeignKey does not allow content type PK 0
-+-
 Reporter:  devesine |Owner:  woodlee
 Type:  Bug  |   Status:  closed
Component:   |  Version:  master
  contrib.contenttypes   |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  contenttype  |  Needs documentation:  0
  genericforeignkey  |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

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


Comment:

 Fixed in [6bdc47f75ca].

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

Re: [Django] #542: abfzpnlbyzjc (was: wcjlfmaltwgv)

[Django]

#542: abfzpnlbyzjc
-+-
 Reporter:  Jason Huggins|Owner:  wilson
 Type:  enhancement  |   Status:  closed
Component:  contrib.admin|  Version:  1.3
 Severity:  trivial  |   Resolution:  wontfix
 Keywords:  suovdnnprflx | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by fanmeakyohal):

 * keywords:  xzceddzoatnk => suovdnnprflx


Comment:

 apps for the android phone http://www.myreefgarden.com/guestbook.php?owner=5028;>real money
 blackjack :((( online blackjack 21, site here, :|] http://www
 .fotostudio-
 lehmann.de/modules/picinfo.php?sort==2859=hochzeit">real money
 blackjack 3:) best usa casinos online, list of online casinos, :( http://roulettegamesonlines.weebly.com/;>roulette games :-/ apps
 for tablet, blackjack games.com, :'( http://playwithrealmoneyblackjack.weebly.com/;>the best casino
 games >:O best casino app android, casino iphone app real money, :[ http://www.elprogresoparatodos.com/galerias/item/187/asInline;>online
 casinos in usa :-0 play casinos online, online games online, :/

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

Re: [Django] #542: wcjlfmaltwgv (was: lkvjbuwpcmly)

[Django]

#542: wcjlfmaltwgv
-+-
 Reporter:  Jason Huggins|Owner:  wilson
 Type:  enhancement  |   Status:  closed
Component:  contrib.admin|  Version:  1.3
 Severity:  trivial  |   Resolution:  wontfix
 Keywords:  xzceddzoatnk | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by bfavdyucdhef):

 * keywords:  icaeayckfpsf => xzceddzoatnk


Comment:

 riverbelle casino http://playwithrealmoneyblackjack.weebly.com/;>real money
 blackjack 8| reputable online casinos, royal vegas casino download,
 :-( http://playrealmoneyslotsgames.weebly.com/;>games at a
 casino >:-O double down casino slot games, casino europa, >: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/071.a49545e96fc54d49374261feca388660%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16963: relocate base View class to views.base from views.generic.base

[Django]

#16963: relocate base View class to views.base from views.generic.base
--+
 Reporter:  ptone |Owner:  ptone
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Generic views |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timo):

 * needs_better_patch:  0 => 1


Comment:

 No longer applies cleanly.

-- 
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.a8f9b1bcd2f115d300f1cc7d53b689ae%40djangoproject.com.
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:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  psycopg2 unicode |  Needs documentation:  0
  python2|  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by timo):

 * needs_better_patch:  0 => 1


Comment:

 The test needs to be incorporated into the Django test suite as well.

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

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

Re: [Django] #16028: Consolidate default template filters' tests

[Django]

#16028: Consolidate default template filters' tests
--+
 Reporter:  julien|Owner:  tobych
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Testing framework |  Version:  1.3
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timo):

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

Re: [Django] #542: lkvjbuwpcmly (was: [patch] Add an "or cancel" link to add, edit, and delete admin views.)

[Django]

#542: lkvjbuwpcmly
-+-
 Reporter:  Jason Huggins|Owner:  wilson
 Type:  enhancement  |   Status:  closed
Component:  contrib.admin|  Version:  1.3
 Severity:  trivial  |   Resolution:  wontfix
 Keywords:  icaeayckfpsf | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by odykwphtmyan):

 * keywords:  cancel link => icaeayckfpsf
 * ui_ux:   => 0
 * version:   => 1.3
 * easy:   => 0


Comment:

 casino on internet http://playwithrealmoneyblackjack.weebly.com/;>playing games for
 money =) play casino slots for real money, android real money casino,
 :-X http://www.kobe-aiken.com/cgi-
 bin/bbs/bbs.cgi?mode=res=">free casino apps for android :D mobile
 blackjack free, list of online casinos, :( http://playrealmoneyslotsgames.weebly.com/;>palace casino resort
 biloxi mississippi :((( play game win real money, making money with
 app, 8-| http://www.xjyfyc.com/2sc/wymaiche_show.asp?id=7694;>make money
 playing games 8| live dealer casino, play blackjack game, =( http://servomart.com/view.php?id=187;>online black jack casino
 :( real money games, online blackjack money, -_- http://www.gebirgsweibsen.at/galerie/modules/picinfo.php?sort==6760=weibsenausfahrt;>casino
 games for real money >:o play free black jack, play casino games
 online for real money, :|] http://miffy.halfmoon.jp/champ/s-bbs/apeboard_plus.cgi?command=2233;>free
 games for money :[ play 21 blackjack online, free blackjack 21, >: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/071.834975ff13ea1da9e320b7653865fa76%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20653: Rename new checksetup manage command

[Django]

#20653: Rename new checksetup manage command
-+-
 Reporter:  russellm |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Core (Management |   Resolution:  fixed
  commands)  | Triage Stage:  Accepted
 Severity:  Release blocker  |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"b30a872973b6903e52d93532175d60d3bf68f888"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b30a872973b6903e52d93532175d60d3bf68f888"
 [1.6.x] Fixed #20653 -- Renamed checksetup -> check missed in [03465639]

 Thanks CollinAnderson for the report.

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

Re: [Django] #20653: Rename new checksetup manage command

[Django]

#20653: Rename new checksetup manage command
-+-
 Reporter:  russellm |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Core (Management |   Resolution:  fixed
  commands)  | Triage Stage:  Accepted
 Severity:  Release blocker  |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"a7d97a6778ca528199920901ed2f66e289ee5a44"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a7d97a6778ca528199920901ed2f66e289ee5a44"
 Fixed #20653 -- Renamed checksetup -> check missed in [03465639]

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

[django/django] a7d97a: Fixed #20653 -- Renamed checksetup -> check missed...

[GitHub]

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

  Changed paths:
M docs/ref/django-admin.txt
M docs/releases/1.6.txt

  Log Message:
  ---
  Fixed #20653 -- Renamed checksetup -> check missed in [03465639]

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

[django/django] b30a87: [1.6.x] Fixed #20653 -- Renamed checksetup -> chec...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: b30a872973b6903e52d93532175d60d3bf68f888
  
https://github.com/django/django/commit/b30a872973b6903e52d93532175d60d3bf68f888
  Author: Tim Graham 
  Date:   2013-07-12 (Fri, 12 Jul 2013)

  Changed paths:
M docs/ref/django-admin.txt
M docs/releases/1.6.txt

  Log Message:
  ---
  [1.6.x] Fixed #20653 -- Renamed checksetup -> check missed in [03465639]

Thanks CollinAnderson for the report.

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

Re: [Django] #20653: Rename new checksetup manage command

[Django]

#20653: Rename new checksetup manage command
-+-
 Reporter:  russellm |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Core (Management |   Resolution:
  commands)  | Triage Stage:  Accepted
 Severity:  Release blocker  |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by CollinAnderson):

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


Comment:

 checksetup is still in the django-admin docs
 https://github.com/django/django/blob/master/docs/ref/django-admin.txt#L92

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

 (i figure this is small enough to not warrant a new ticket number.)

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

Re: [Django] #19941: Make running django's test suite easier

[Django]

#19941: Make running django's test suite easier
--+
 Reporter:  akaariai  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  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):

 * cc: timograham@… (added)
 * needs_docs:  1 => 0


Comment:

 [https://github.com/django/django/pull/1352 PR] with update docs.

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

Re: [Django] #7664: MultiWidget to support named sub widgets

[Django]

#7664: MultiWidget to support named sub widgets
+
 Reporter:  CollinAnderson  |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  Forms   |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  multiwidget | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  1
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by anonymous):

 Please also add the ability to override the `_` separator. Creating a
 multiwidget for autocompletion ends up making `field_1` and `field_2` in
 POST when I'd really like to be able to generate `field` and `field_text`,
 because keeping `field` will make sure using the widget doesn't break any
 tests that use POSTdata. There are workarounds, but I feel like it's not
 something so complicated it deserves its own hack.

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

Re: [Django] #13142: Add support for SSL connections in core.mail.backends.smtp

[Django]

#13142: Add support for SSL connections in core.mail.backends.smtp
-+--
 Reporter:  serg.partizan@…  |Owner:  jwmayfield
 Type:  New feature  |   Status:  assigned
Component:  Core (Mail)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+--

Comment (by timo):

 #17471 is a duplicate which was recently committed but lacks the cert/key
 file setting options in the PR.

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

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

Re: [Django] #17471: Add ability to use smtplib.SMTP_SSL connection when sending email

[Django]

#17471: Add ability to use smtplib.SMTP_SSL connection when sending email
-+-
 Reporter:  dje  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Mail)  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  smtp sprints-| Triage Stage:  Accepted
  django-ar  |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by timo):

 #13142 is a duplicate which contains some additional settings for the
 cert/key files.

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

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

Re: [Django] #11521: QuerySet.update() doesn't accept fkey assignment by id (with patch)

[Django]

#11521: QuerySet.update() doesn't accept fkey assignment by id (with patch)
-+-
 Reporter:  Adys |Owner:  Adys
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

 * stage:  Accepted => Ready for checkin


Comment:

 We can make this change for 1.7. Patch still applies cleanly and tests
 pass.

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

Re: [Django] #8467: For ManyToMany manager, we should convert objects being added or removed to the pk type if they are not.

[Django]

#8467: For ManyToMany manager, we should convert objects being added or removed 
to
the pk type if they are not.
-+-
 Reporter:  Wonlay   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  Duplicate entry, |  Needs documentation:  0
  add, remove, ManyToManyField   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_better_patch:  0 => 1
 * needs_tests:  0 => 1


Comment:

 Patch needs improvement per @akaariai's comment as well as tests.

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

Re: [Django] #17988: BaseModelFormset.save doesn't honor commit=False when deleting objects.

[Django]

#17988: BaseModelFormset.save doesn't honor commit=False when deleting objects.
+-
 Reporter:  rem |Owner:  tuxcanfly
 Type:  Bug |   Status:  assigned
Component:  Forms   |  Version:  1.3
 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 timo):

 * cc: timograham@… (added)


Comment:

 Duplicate of #10284 which argues for changing the behavior and forcing
 users to handle `formset.deleted_objects` manually. Even though it's
 backwards incompatible, IMO, it's a cleaner fix as I wouldn't expect any
 data changing operations when using `commit=False`. Perhaps a django-
 developers discussion 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/061.b768d7849b121de2eef260139868cd8d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #10284: ModelFormSet - objects are deleted even if commit=False

[Django]

#10284: ModelFormSet - objects are deleted even if commit=False
+
 Reporter:  laureline.guerin@…  |Owner:  Wedg
 Type:  Bug |   Status:  assigned
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:  0   |UI/UX:  0
+

Comment (by timo):

 Duplicate of #17988 in which @akaariai suggests changing the current
 behavior would be backwards-incompatible (of course, all bug fixes are --
 I guess it's whether or not you consider the current design a bug or a
 feature). This is what Jacob meant by "related objects will never get
 deleted by anyone" -- the pull request solves this by a documentation
 update which informs users they must handle `formset.deleted_objects`
 manually.

 IMO, the justification for changing the behavior is that it's unexpected
 that anything DB related happens with `commit=False`.

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

Re: [Django] #542: mpxzwsgffkyx (was: [patch] Add an "or cancel" link to add, edit, and delete admin views.)

[Django]

#542: mpxzwsgffkyx
-+-
 Reporter:  Jason Huggins|Owner:  wilson
 Type:  enhancement  |   Status:  closed
Component:  contrib.admin|  Version:
 Severity:  trivial  |  1.0-beta-2
 Keywords:  sttqlrgjorjx |   Resolution:  wontfix
Has patch:  1| Triage Stage:  Design
  Needs tests:  0|  decision needed
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by eboqmpcbnquj):

 * keywords:  cancel link => sttqlrgjorjx
 * ui_ux:   => 0
 * version:   => 1.0-beta-2
 * easy:   => 0


Comment:

 watch casino online http://onlinecasinosusaslot.weebly.com/;>rtg
 casino bonus codes ;) casinoonline, casino night party theme
 decorations, >:o http://www.zj-
 motel.com.tw/guestbook.php?totalRows_im_guestbook_get=1859">bestcasino
 O:-) aqueduct casino jobs, hotel foxwoods casino, :) http://bestcasinoonlines.weebly.com/;>no deposit online casino
 codes >:O station casino las vegas, which casino, 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/071.9a80b648c68e316279d4db8abb54db10%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18170: [PATCH] Break-out password reset confirmation so that it is re-usable.

[Django]

#18170: [PATCH] Break-out password reset confirmation so that it is re-usable.
-+-
 Reporter:   |Owner:  nobody
  thomas.david.vaughan@… |   Status:  closed
 Type:  New feature  |  Version:  1.4
Component:  contrib.auth |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

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


Comment:

 Given the comments on the PR and the fact that it was closed, I'm going to
 close this.

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

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

Re: [Django] #20582: Default label_suffix should be translatable

[Django]

#20582: Default label_suffix should be translatable
-+
 Reporter:  claudep  |Owner:  nobody
 Type:  Bug  |   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:  0|UI/UX:  0
-+
Changes (by timo):

 * cc: timograham@… (added)
 * needs_better_patch:  0 => 1
 * needs_docs:  0 => 1


Comment:

 Patch no longer applies cleanly. Also I think it should be documented that
 this is translatable (ref/forms/api.txt)? Does it need tests?

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

Re: [Django] #15691: TEST_DEPENDENCIES doesn't use TEST_NAME in circular dependency detection.

[Django]

#15691: TEST_DEPENDENCIES doesn't use TEST_NAME in circular dependency 
detection.
---+
 Reporter:  slinkp@…   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.2
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timo):

 * needs_tests:  0 => 1


Comment:

 This needs a test.

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

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

Re: [Django] #10284: ModelFormSet - objects are deleted even if commit=False

[Django]

#10284: ModelFormSet - objects are deleted even if commit=False
+
 Reporter:  laureline.guerin@…  |Owner:  Wedg
 Type:  Bug |   Status:  assigned
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:  0   |UI/UX:  0
+
Changes (by timo):

 * cc: timograham@… (added)


Comment:

 Updated [https://github.com/django/django/pull/1351 PR]. Seems
 straightforward to me.

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

Re: [Django] #15624: annotate + aggregate produces incorrect sql statement (was: aggregate produces incorrect sql statement)

[Django]

#15624: annotate + aggregate produces incorrect sql statement
-+-
 Reporter:  zeroos <232002@…>|Owner:  fhahn
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  aggregate sql|  checkin
  syntax error   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * stage:  Accepted => Ready for checkin


Comment:

 Patch applies cleanly and tests pass. Would like someone more familiar
 with the code to +1 before committing.

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

Re: [Django] #20741: Add extra context to templates of « start{app,project} » management commands

[Django]

#20741: Add extra context to templates of « start{app,project} » management
commands
-+-
 Reporter:  palkeo   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  1.5
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by palkeo):

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


Comment:

 I have added a patch that works.

 But, my help text is far from perfect.
 I also didn't understood why the content of the « options » variable was
 added to the context. I have removed it for now, but I don't know if that
 was the right thing to do :/

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

Re: [Django] #20741: Add extra context to templates of « start{app,project} » management commands

[Django]

#20741: Add extra context to templates of « start{app,project} » management
commands
-+-
 Reporter:  palkeo   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  1.5
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by palkeo):

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

Re: [Django] #20625: Custom Chainable QuerySets

[Django]

#20625: Custom Chainable QuerySets
-+-
 Reporter:  danols   |Owner:  loic84
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  QuerySet,|  Needs documentation:  0
  models.Manager, chainable  |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by loic84):

 Rebased to remove the new proxy method introduced by #20429.

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

[django/django] 6272d2: Fixed #20429 -- Added QuerySet.update_or_create

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 6272d2f155adb4f32ef129d57e9eb5493ebde6ed
  
https://github.com/django/django/commit/6272d2f155adb4f32ef129d57e9eb5493ebde6ed
  Author: Karol Sikora 
  Date:   2013-07-12 (Fri, 12 Jul 2013)

  Changed paths:
M AUTHORS
M django/db/models/manager.py
M django/db/models/query.py
M docs/ref/models/querysets.txt
M docs/releases/1.7.txt
M tests/get_or_create/tests.py

  Log Message:
  ---
  Fixed #20429 -- Added QuerySet.update_or_create

Thanks tunixman for the suggestion and Loic Bistuer for the review.



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

Re: [Django] #20429: Add QuerySet.update_or_create method

[Django]

#20429: Add QuerySet.update_or_create method
-+-
 Reporter:  tunixman |Owner:
 Type:  New feature  |  elektrrrus
Component:  Database layer   |   Status:  closed
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"6272d2f155adb4f32ef129d57e9eb5493ebde6ed"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6272d2f155adb4f32ef129d57e9eb5493ebde6ed"
 Fixed #20429 -- Added QuerySet.update_or_create

 Thanks tunixman for the suggestion and Loic Bistuer for the review.
 }}}

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

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

Re: [Django] #20742: ModelForm primary_key update with instance set is executed as INSERT caused by is_valid() changing the instance (was: ModelForm primary_key update with instance set is executed as

[Django]

#20742: ModelForm primary_key update with instance set is executed as INSERT 
caused
by is_valid() changing the instance
-+-
 Reporter:  amin@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  modelform instance   |  Unreviewed
  primary_key update |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by amin@…):

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

Re: [Django] #542: khmkrcgbcfhj (was: svkjaxqyxoio)

[Django]

#542: khmkrcgbcfhj
-+-
 Reporter:  Jason Huggins|Owner:  wilson
 Type:  enhancement  |   Status:  closed
Component:  contrib.admin|  Version:  1.0-alpha
 Severity:  trivial  |   Resolution:  wontfix
 Keywords:  mvllsetnpcjt | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by unxdvgrpwtck):

 * keywords:  zcggbwitolsz => mvllsetnpcjt


Comment:

 montecito casino http://playwithtoponlinecasinosgames.weebly.com/;>top online
 casinos B-| live casino, casinos in ms, :((( http://www
 .reign-of-
 fantasy.de/weltenbrand/showit_v2.1.07/showit/modules/picinfo.php?bild=657
 =weltenbrand-chars">royal ace casino no deposit bonus codes :D us
 friendly online casinos, coushatta casino coupons, O:-) http://video.okayclip.com?w=6217;>http://vegascasinosonline.weebly.com/
 B| largest casino in north america, sandscasino.com, :'( http://vegascasinosonline.weebly.com/;>casino in maryland arundel
 mills :-/ live casino slots, wild vegas casino, ._.

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

[Django] #20742: ModelForm primary_key update with instance set is executed as INSERT caused by is_valid() chaning the instance

[Django]

#20742: ModelForm primary_key update with instance set is executed as INSERT 
caused
by is_valid() chaning the instance
-+-
 Reporter:  amin@…   |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Database layer   |Version:  1.5
  (models, ORM)  |   Keywords:  modelform instance
 Severity:  Normal   |  primary_key update
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 I do agree this is a bad database design but it's executed without any
 warning or anything in the docs so i want to open this ticket to allow the
 discussion of raising an Error or anything (e.g. an info in the docs
 @primary_key or modelform) not let anyone run into this mistake.


 class Test(models.Model):
   email = models.CharField(max_length=100, primary_key=True)

 class TestForm(forms.ModelForm):
   class Meta:
  model = Test

 # assuming this object exists
 x = Test.objects.get(email='o...@example.com')

 form = TestForm(email='n...@example.com', instance=x)

 # here instance is updated with n...@example.com as pkey and django thinks
 it has to create a new model instance not updating the old instance
 if form.is_valid():
new_x = form.save()
new_x.save()

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

Re: [Django] #19031: Add a warning that @override_settings may not work with DATABASES

[Django]

#19031: Add a warning that @override_settings may not work with DATABASES
---+
 Reporter:  jonash |Owner:  joeri
 Type:  New feature|   Status:  closed
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"66f3d57b79eee0381c29ee4c76582d6b182bfad9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="66f3d57b79eee0381c29ee4c76582d6b182bfad9"
 Fixed #19031 -- Added a warning when using override_settings with
 'DATABASES'
 }}}

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

[django/django] 66f3d5: Fixed #19031 -- Added a warning when using overrid...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 66f3d57b79eee0381c29ee4c76582d6b182bfad9
  
https://github.com/django/django/commit/66f3d57b79eee0381c29ee4c76582d6b182bfad9
  Author: Joeri Bekker 
  Date:   2013-07-12 (Fri, 12 Jul 2013)

  Changed paths:
M django/test/signals.py
M django/test/utils.py
M docs/ref/signals.txt
M docs/releases/1.7.txt
M docs/topics/testing/overview.txt
M tests/settings_tests/tests.py

  Log Message:
  ---
  Fixed #19031 -- Added a warning when using override_settings with 'DATABASES'



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

Re: [Django] #19934: Switch to a Python 3-compatible imaging library

[Django]

#19934: Switch to a Python 3-compatible imaging library
-+-
 Reporter:  aaugustin|Owner:
 Type:   |  daniellindsley
  Cleanup/optimization   |   Status:  closed
Component:  Python 3 |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"b82a2c41387648f81387b1e03371331db3630269"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b82a2c41387648f81387b1e03371331db3630269"
 Merge pull request #1349 from chrismedrela/ticket19934-comment

 Added clarification comments to django.utils.image; refs #19934
 }}}

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

[django/django] b4c61c: Added clarification comments to django.utils.image...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b4c61c2665c0aa06dcdc4f823be03f23b9696408
  
https://github.com/django/django/commit/b4c61c2665c0aa06dcdc4f823be03f23b9696408
  Author: Christopher Medrela 
  Date:   2013-07-12 (Fri, 12 Jul 2013)

  Changed paths:
M django/utils/image.py

  Log Message:
  ---
  Added clarification comments to django.utils.image; refs #19934


  Commit: b82a2c41387648f81387b1e03371331db3630269
  
https://github.com/django/django/commit/b82a2c41387648f81387b1e03371331db3630269
  Author: Tim Graham 
  Date:   2013-07-12 (Fri, 12 Jul 2013)

  Changed paths:
M django/utils/image.py

  Log Message:
  ---
  Merge pull request #1349 from chrismedrela/ticket19934-comment

Added clarification comments to django.utils.image; refs #19934


Compare: https://github.com/django/django/compare/3cdeb572d73f...b82a2c413876

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

Re: [Django] #19934: Switch to a Python 3-compatible imaging library

[Django]

#19934: Switch to a Python 3-compatible imaging library
-+-
 Reporter:  aaugustin|Owner:
 Type:   |  daniellindsley
  Cleanup/optimization   |   Status:  closed
Component:  Python 3 |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Christopher Medrela ):

 In [changeset:"b4c61c2665c0aa06dcdc4f823be03f23b9696408"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b4c61c2665c0aa06dcdc4f823be03f23b9696408"
 Added clarification comments to django.utils.image; refs #19934
 }}}

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

Re: [Django] #542: svkjaxqyxoio (was: dkuserveuvqu)

[Django]

#542: svkjaxqyxoio
-+-
 Reporter:  Jason Huggins|Owner:  wilson
 Type:  enhancement  |   Status:  closed
Component:  contrib.admin|  Version:  1.0-alpha
 Severity:  trivial  |   Resolution:  wontfix
 Keywords:  zcggbwitolsz | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by ivrhuzgnqmiw):

 * keywords:  ukgdqigdoeai => zcggbwitolsz


Comment:

 canada online casinos http://playtoponlinecasinogames.weebly.com/;>casino portal 3:-)
 largest casino in america, casino las vegas chips, >: http://topinternetgambling.weebly.com/;>online slot casino games
 :3 internet gambling, search casino, <3

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

Re: [Django] #20346: cache middleware should vary on full URL

[Django]

#20346: cache middleware should vary on full URL
-+
 Reporter:  jamey|Owner:
 Type:  Bug  |   Status:  new
Component:  Core (Cache system)  |  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by timo):

 This needs a test to demonstrate the change in behavior.

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

[django/django] 61c8c1: [1.5.x] Fixed #17528 -- Documented that add() and ...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 61c8c1b6dcd267a7d4777ff3b0a78eaedb9b95d3
  
https://github.com/django/django/commit/61c8c1b6dcd267a7d4777ff3b0a78eaedb9b95d3
  Author: Tim Graham 
  Date:   2013-07-12 (Fri, 12 Jul 2013)

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

  Log Message:
  ---
  [1.5.x] Fixed #17528 -- Documented that add() and remove() with a 
many-to-many relationship do not call Model.save()

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

[django/django] 1c8e53: [1.6.x] Fixed #17528 -- Documented that add() and ...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 1c8e539a7723fe2d76b5c5a8b83c8a3da2d9fc39
  
https://github.com/django/django/commit/1c8e539a7723fe2d76b5c5a8b83c8a3da2d9fc39
  Author: Tim Graham 
  Date:   2013-07-12 (Fri, 12 Jul 2013)

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

  Log Message:
  ---
  [1.6.x] Fixed #17528 -- Documented that add() and remove() with a 
many-to-many relationship do not call Model.save()

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

Re: [Django] #17528: Document that add() and remove() with a many-to-many relationship do not call Model.save()

[Django]

#17528: Document that add() and remove() with a many-to-many relationship do not
call Model.save()
-+-
 Reporter:  mmoya@…  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.3
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  m2m, related |  Needs documentation:  0
  manager, save  |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"1c8e539a7723fe2d76b5c5a8b83c8a3da2d9fc39"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1c8e539a7723fe2d76b5c5a8b83c8a3da2d9fc39"
 [1.6.x] Fixed #17528 -- Documented that add() and remove() with a many-to-
 many relationship do not call Model.save()

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

Re: [Django] #17528: Document that add() and remove() with a many-to-many relationship do not call Model.save()

[Django]

#17528: Document that add() and remove() with a many-to-many relationship do not
call Model.save()
-+-
 Reporter:  mmoya@…  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.3
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  m2m, related |  Needs documentation:  0
  manager, save  |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"61c8c1b6dcd267a7d4777ff3b0a78eaedb9b95d3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="61c8c1b6dcd267a7d4777ff3b0a78eaedb9b95d3"
 [1.5.x] Fixed #17528 -- Documented that add() and remove() with a many-to-
 many relationship do not call Model.save()

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

[django/django] 3cdeb5: Fixed #17528 -- Documented that add() and remove()...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3cdeb572d73fca3d7966318c760f61ba73e5ad5f
  
https://github.com/django/django/commit/3cdeb572d73fca3d7966318c760f61ba73e5ad5f
  Author: Tim Graham 
  Date:   2013-07-12 (Fri, 12 Jul 2013)

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

  Log Message:
  ---
  Fixed #17528 -- Documented that add() and remove() with a many-to-many 
relationship do not call Model.save()



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

Re: [Django] #17528: Document that add() and remove() with a many-to-many relationship do not call Model.save()

[Django]

#17528: Document that add() and remove() with a many-to-many relationship do not
call Model.save()
-+-
 Reporter:  mmoya@…  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.3
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  m2m, related |  Needs documentation:  0
  manager, save  |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"3cdeb572d73fca3d7966318c760f61ba73e5ad5f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3cdeb572d73fca3d7966318c760f61ba73e5ad5f"
 Fixed #17528 -- Documented that add() and remove() with a many-to-many
 relationship do not call Model.save()
 }}}

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

[Django] #20741: Add extra context to templates of « start{app,project} » management commands

[Django]

#20741: Add extra context to templates of « start{app,project} » management
commands
+
 Reporter:  palkeo  |  Owner:  nobody
 Type:  New feature | Status:  new
Component:  Core (Management commands)  |Version:  1.5
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  1   |  UI/UX:  0
+
 Hi,

 When creating a new app or a new project, you can generate it from a
 template. It will contain files, and some files can be rendered by the
 template engine.
 See the docs : https://docs.djangoproject.com/en/dev/ref/django-admin
 /#startapp-appname-destination

 I would like to add the possibility of passing extra template context,
 though command line parameters.

 For example, that would allows us to pass an extra variable, « author »,
 in the template context… so the generated app can correctly reference the
 author.
 We could also use it to choose a license…


 The code that needs to be modified is here :
 
https://github.com/django/django/blob/master/django/core/management/templates.py#L113
 I think it would be quite easy to change, and I can do a patch if you
 want.

 What do you think about 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/049.a052914cdd7500ba378a5f42bb9a2f6f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20735: Confusing ManyToManyField constructor documentation

[Django]

#20735: Confusing ManyToManyField constructor documentation
--+
 Reporter:  chrismedrela  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.5
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"80a7dd6f7fa0b2fe56978eafdf4a1c7eaf0ad29b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="80a7dd6f7fa0b2fe56978eafdf4a1c7eaf0ad29b"
 [1.5.x] Fixed #20735 -- clarified ManyToManyField constructor doc

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

[django/django] 80a7dd: [1.5.x] Fixed #20735 -- clarified ManyToManyField ...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 80a7dd6f7fa0b2fe56978eafdf4a1c7eaf0ad29b
  
https://github.com/django/django/commit/80a7dd6f7fa0b2fe56978eafdf4a1c7eaf0ad29b
  Author: Christopher Medrela 
  Date:   2013-07-12 (Fri, 12 Jul 2013)

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

  Log Message:
  ---
  [1.5.x] Fixed #20735 -- clarified ManyToManyField constructor doc

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

[django/django] 9bb04b: [1.6.x] Fixed #20735 -- clarified ManyToManyField ...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 9bb04b1a6bcb98e7061f475aaac58add89d048ba
  
https://github.com/django/django/commit/9bb04b1a6bcb98e7061f475aaac58add89d048ba
  Author: Christopher Medrela 
  Date:   2013-07-12 (Fri, 12 Jul 2013)

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

  Log Message:
  ---
  [1.6.x] Fixed #20735 -- clarified ManyToManyField constructor doc

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

Re: [Django] #20735: Confusing ManyToManyField constructor documentation

[Django]

#20735: Confusing ManyToManyField constructor documentation
--+
 Reporter:  chrismedrela  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.5
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"9bb04b1a6bcb98e7061f475aaac58add89d048ba"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9bb04b1a6bcb98e7061f475aaac58add89d048ba"
 [1.6.x] Fixed #20735 -- clarified ManyToManyField constructor doc

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

[django/django] ac223f: Fixed #20735 -- clarified ManyToManyField construc...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ac223ff6d1efda56ab1d2e5afe250f744a0a4e64
  
https://github.com/django/django/commit/ac223ff6d1efda56ab1d2e5afe250f744a0a4e64
  Author: Christopher Medrela 
  Date:   2013-07-12 (Fri, 12 Jul 2013)

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

  Log Message:
  ---
  Fixed #20735 -- clarified ManyToManyField constructor doc


  Commit: d1d09fecf87e9139c9493218c9211e6c91f791a3
  
https://github.com/django/django/commit/d1d09fecf87e9139c9493218c9211e6c91f791a3
  Author: Tim Graham 
  Date:   2013-07-12 (Fri, 12 Jul 2013)

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

  Log Message:
  ---
  Merge pull request #1350 from chrismedrela/ticket20735

Fixed #20735 -- clarified ManyToManyField constructor doc


Compare: https://github.com/django/django/compare/59ebe3981285...d1d09fecf87e

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

Re: [Django] #20735: Confusing ManyToManyField constructor documentation

[Django]

#20735: Confusing ManyToManyField constructor documentation
--+
 Reporter:  chrismedrela  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.5
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Christopher Medrela ):

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


Comment:

 In [changeset:"ac223ff6d1efda56ab1d2e5afe250f744a0a4e64"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ac223ff6d1efda56ab1d2e5afe250f744a0a4e64"
 Fixed #20735 -- clarified ManyToManyField constructor doc
 }}}

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

Re: [Django] #20735: Confusing ManyToManyField constructor documentation

[Django]

#20735: Confusing ManyToManyField constructor documentation
--+
 Reporter:  chrismedrela  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.5
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"d1d09fecf87e9139c9493218c9211e6c91f791a3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d1d09fecf87e9139c9493218c9211e6c91f791a3"
 Merge pull request #1350 from chrismedrela/ticket20735

 Fixed #20735 -- clarified ManyToManyField constructor doc
 }}}

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

Re: [Django] #20735: Confusing ManyToManyField constructor documentation

[Django]

#20735: Confusing ManyToManyField constructor documentation
--+
 Reporter:  chrismedrela  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  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 chrismedrela):

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

Re: [Django] #20735: Confusing ManyToManyField constructor documentation

[Django]

#20735: Confusing ManyToManyField constructor documentation
--+
 Reporter:  chrismedrela  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  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
--+

Comment (by chrismedrela):

 That's much better. Additionally, I would like to remove some words:
 "including ~~all the options regarding~~ recursive and lazy
 relationships". One may think about `**options` keyword arguments when
 they glance at "including all the options" and don't read to the very end
 of the statement. I've created a pull request:
 https://github.com/django/django/pull/1350.

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

Re: [Django] #542: dkuserveuvqu (was: exrvtqvdwudx)

[Django]

#542: dkuserveuvqu
-+-
 Reporter:  Jason Huggins|Owner:  wilson
 Type:  enhancement  |   Status:  closed
Component:  contrib.admin|  Version:  1.0-alpha
 Severity:  trivial  |   Resolution:  wontfix
 Keywords:  ukgdqigdoeai | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by gsbgwbbskans):

 * keywords:  lfyyfbkqraik => ukgdqigdoeai


Comment:

 free casino play online http://topinternetgambling.weebly.com/;>maryland live casino -
 home =) free roulette wheel game, poker game online, >: http://roulettecasinoslot.weebly.com/;>roulette casino >:-O
 gamble online poker, click to read more, :/ http://www.carknow.cn/Show/NewShow.aspx?iSCID=7BFAA265CCCA8E64=2457;>roulette
 casino B-| online roulette game, best roulette strategy, ;) http://www.erster-haager-
 
westernclub.de/show/modules/picinfo.php?bild=5447=10_j._westernclub">roulette
 casino ;) win at roulette, free roulette games to play, 8|

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

Re: [Django] #20740: GenericIPAddressField does not pass protocol to formfield() (was: GenericIPAddressField gives misleading error in ModelForm)

[Django]

#20740: GenericIPAddressField does not pass protocol to formfield()
-+
 Reporter:  Jeff250  |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:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by timo):

 * cc: timograham@… (added)
 * needs_better_patch:   => 0
 * component:  Uncategorized => Forms
 * needs_tests:   => 1
 * easy:  0 => 1
 * needs_docs:   => 0
 * has_patch:  0 => 1
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Comment:

 Could you add a test for this?

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

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

Re: [Django] #542: exrvtqvdwudx (was: piruvevjrvdd)

[Django]

#542: exrvtqvdwudx
-+-
 Reporter:  Jason Huggins|Owner:  wilson
 Type:  enhancement  |   Status:  closed
Component:  contrib.admin|  Version:  1.0-alpha
 Severity:  trivial  |   Resolution:  wontfix
 Keywords:  lfyyfbkqraik | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by rqrhpnqhijtc):

 * keywords:  vhofcpkwwnkp => lfyyfbkqraik


Comment:

 reel deal casino games http://roulettecasinoslot.weebly.com/;>free gambling online :-/
 bills casino las vegas, los vegas casino, :-* http://www.atelier-
 keller.ch/blog/index.php?abuse=9424=em042jml">roulette casino :|]
 green valley casino, casino titan online casino, :V http://playbestcasinoonlinegames.weebly.com/;>casino online
 games 8-| foxwood casino directions, casino riviera, <3

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

Re: [Django] #19934: Switch to a Python 3-compatible imaging library

[Django]

#19934: Switch to a Python 3-compatible imaging library
-+-
 Reporter:  aaugustin|Owner:
 Type:   |  daniellindsley
  Cleanup/optimization   |   Status:  closed
Component:  Python 3 |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by chrismedrela):

 @daniellindsley - Thank you for your answer. I created a pull request
 clarifying the situation https://github.com/django/django/pull/1349.

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

Re: [Django] #542: piruvevjrvdd (was: kljrlswdcwfd)

[Django]

#542: piruvevjrvdd
-+-
 Reporter:  Jason Huggins|Owner:  wilson
 Type:  enhancement  |   Status:  closed
Component:  contrib.admin|  Version:  1.0-alpha
 Severity:  trivial  |   Resolution:  wontfix
 Keywords:  vhofcpkwwnkp | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by zjfhwhtprgiz):

 * keywords:  gzssbonngrux => vhofcpkwwnkp


Comment:

 double down casino poker http://lunatic.kill.jp/cgi-
 bin/u_bbs/apeboard_plus.cgi?command=877">More Bonuses :-* mobile
 casino no deposit bonus, directions to foxwoods casino, ._. http://playwithtopinternetcasinos.weebly.com/;>casino windsor
 3:-) boomtown casino biloxi ms, orleans casino, =) http://topinternetgambling.weebly.com/;>internet gambling B-|
 internet casino game, directions to foxwoods casino, <3

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

Re: [Django] #542: kljrlswdcwfd (was: [patch] Add an "or cancel" link to add, edit, and delete admin views.)

[Django]

#542: kljrlswdcwfd
-+-
 Reporter:  Jason Huggins|Owner:  wilson
 Type:  enhancement  |   Status:  closed
Component:  contrib.admin|  Version:  1.0-alpha
 Severity:  trivial  |   Resolution:  wontfix
 Keywords:  gzssbonngrux | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by troqhfiktaml):

 * keywords:  cancel link => gzssbonngrux
 * ui_ux:   => 0
 * version:   => 1.0-alpha
 * easy:   => 0


Comment:

 play free roulette online games http://playwithtopinternetcasinos.weebly.com/;>las vegas mgm
 casino :D real money casino online, free games online no downloads no
 registration, =) http://roulettecasinoslot.weebly.com/;>roulette
 casino :-* free roulette strategy, scrabble online, :'(

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