Re: [Django] #19889: Tutorial03 makes you refactor code that you cannot run

[Django]

#19889: Tutorial03 makes you refactor code that you cannot run
-+-
 Reporter:  jpic |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  needsinfo
 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 ptone):

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


Comment:

 I made the small clarification - going to close as needs info, if the
 ticket author can provide some other concrete suggestions for improvement,
 by all means - please reopen.

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

Re: [Django] #19902: Broken link in documentation

[Django]

#19902: Broken link in documentation
--+
 Reporter:  kolkabes@…|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  closed
Component:  Documentation |Version:  1.4
 Severity:  Normal| Resolution:  fixed
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  0 |  Easy pickings:  0
UI/UX:  0 |
--+
Changes (by Preston Holmes ):

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


Comment:

 In [changeset:"0f555f813b1bc3995d19160be17c8b2cb6a440c1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="0f555f813b1bc3995d19160be17c8b2cb6a440c1"
 [1.4.x] Fixed #19902 -- backport of as_view 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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 0f555f: [1.4.x] Fixed #19902 -- backport of as_view docs

[GitHub]

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: 0f555f813b1bc3995d19160be17c8b2cb6a440c1
  
https://github.com/django/django/commit/0f555f813b1bc3995d19160be17c8b2cb6a440c1
  Author: Preston Holmes 
  Date:   2013-02-23 (Sat, 23 Feb 2013)

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

  Log Message:
  ---
  [1.4.x] Fixed #19902 -- backport of as_view docs



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

Re: [Django] #19889: Tutorial03 makes you refactor code that you cannot run

[Django]

#19889: Tutorial03 makes you refactor code that you cannot run
-+-
 Reporter:  jpic |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   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
-+-

Comment (by Preston Holmes ):

 In [changeset:"17a28b39a8d77997f83ecd94ebcff7b198b8cb05"]:
 {{{
 #!CommitTicketReference repository=""
 revision="17a28b39a8d77997f83ecd94ebcff7b198b8cb05"
 Made a small clarification in tutorial.

 refs #19889
 }}}

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

[django/django] 17a28b: Made a small clarification in tutorial.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 17a28b39a8d77997f83ecd94ebcff7b198b8cb05
  
https://github.com/django/django/commit/17a28b39a8d77997f83ecd94ebcff7b198b8cb05
  Author: Preston Holmes 
  Date:   2013-02-23 (Sat, 23 Feb 2013)

  Changed paths:
M docs/intro/tutorial03.txt

  Log Message:
  ---
  Made a small clarification in tutorial.

refs #19889



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

Re: [Django] #19889: Tutorial03 makes you refactor code that you cannot run

[Django]

#19889: Tutorial03 makes you refactor code that you cannot run
-+-
 Reporter:  jpic |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   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
-+-

Comment (by Preston Holmes ):

 In [changeset:"f60dd6f55dcd646dcec4f7f8b2cc73af985ccba3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f60dd6f55dcd646dcec4f7f8b2cc73af985ccba3"
 [1.5.x] Made a small clarification in tutorial.

 refs #19889
 }}}

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

[django/django] f60dd6: [1.5.x] Made a small clarification in tutorial.

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: f60dd6f55dcd646dcec4f7f8b2cc73af985ccba3
  
https://github.com/django/django/commit/f60dd6f55dcd646dcec4f7f8b2cc73af985ccba3
  Author: Preston Holmes 
  Date:   2013-02-23 (Sat, 23 Feb 2013)

  Changed paths:
M docs/intro/tutorial03.txt

  Log Message:
  ---
  [1.5.x] Made a small clarification in tutorial.

refs #19889



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

Re: [Django] #19889: Tutorial03 makes you refactor code that you cannot run

[Django]

#19889: Tutorial03 makes you refactor code that you cannot run
-+-
 Reporter:  jpic |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   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
-+-

Comment (by ptone):

 I might change

 "working, just:"

 to

 "working, a file containing just:"

 But otherwise - yes, you can't cover everything simultaneously.

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

[Django] #19902: Broken link in documentation

[Django]

#19902: Broken link in documentation
--+
 Reporter:  kolkabes@…|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Reading [https://docs.djangoproject.com/en/1.4/ref/class-based-views
 /#generic-views paragraph on generic views] I followed a link to
 [https://docs.djangoproject.com/en/1.4/ref/class-based-
 views/base/#django.views.generic.base.View.as_view as_view()] which leads
 404 page.

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

[Django] #19901: introspect user model to determine REQUIRED_FIELDS

[Django]

#19901: introspect user model to determine REQUIRED_FIELDS
+
   Reporter:  ptone |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  contrib.auth  |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 |
+
 It should be possible to deduce what fields are required when prompting
 for user creation during interactive user creation. This would allow the
 REQUIRED_FIELDS attribute of custom users to go away.

 see comments on #19402

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

Re: [Django] #19888: MultiValueDictKeyError when saving Inlines without an AutoField

[Django]

#19888: MultiValueDictKeyError when saving Inlines without an AutoField
---+
 Reporter:  nickname123|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.4
 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
---+

Comment (by nickname123):

 current patch does not work if the pk field is excluded from the admin

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

Re: [Django] #18839: Field.__init__() should call super() at end.

[Django]

#18839: Field.__init__() should call super() at end.
+
 Reporter:  applegrew   |Owner:  joeri
 Type:  Bug |   Status:  new
Component:  Forms   |  Version:  1.4
 Severity:  Normal  |   Resolution:
 Keywords:  sprint2013  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+
Changes (by carljm):

 * status:  closed => new
 * resolution:  wontfix =>
 * stage:  Design decision needed => Accepted


Comment:

 Re-opening.

 There are two ways to handle inheritance in Python; either use `super()`
 everywhere, or use it not at all (and instead just make explicit calls to
 the parent method, as joeri illustrates). The `super()` approach makes
 multiple-inheritance possible (without having to choose between parent
 implementations or somehow "merge" their results). There are pros and cons
 to either approach, but the key fact is that if you are using `super()`,
 every class in the inheritance tree (including a "base" one that only
 inherits `object`) must also use `super()` or the call-chain might be
 broken, potentially in quite surprising ways in a multiple-inheritance
 scenario (i.e. a mixin right above the leaf class may never get its method
 called, because a base class much further up the tree omitted `super`).

 We could have a (endless) discussion about which approach is better, but
 in general Django's codebase does use `super()`, and because of the "all-
 or-nothing" nature of `super()`, it's pretty important that we maintain a
 consistent approach. Thus, unless we were to adopt a new policy of never
 using `super()` at all, I think `Field` not calling `super()` (and thus
 potentially breaking field mixins) is a bug and should be fixed.

 I think really the only backwards-compatibility implications here are that
 multiple-inheritance scenarios that are currently broken (i.e. mixin
 method never called) will start working properly (mixin method will be
 called). While I suppose it's possible that there is code relying on the
 broken behavior, that's true with any bug we ever fix.

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

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

Re: [Django] #18336: Static files randomly fail to load in Google Chrome

[Django]

#18336: Static files randomly fail to load in Google Chrome
---+
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   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 chipx86):

 I'm also on MacOS X.

 To do any actual development, I have to patch basehttp.py every time I
 upgrade Django, in each virtualenv. If there were a way to at least
 override this in some form globally, I could live with it, but for the
 moment, it's a complete pain and leads to odd, sometimes very subtle bugs.

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

Re: [Django] #19758: Password reset form should not leak information

[Django]

#19758: Password reset form should not leak information
--+
 Reporter:  anonymous |Owner:  zerok
 Type:  Bug   |   Status:  closed
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  sprint2013| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by carljm):

 (Aymeric is correct, I didn't intend to suggest a setting, just that we
 could document the subclassing approach.)

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

[django/django] f480b3: Various tweaks and additions to 'how to release Dj...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: f480b395256612de83b2f912bfecee03366bc990
  
https://github.com/django/django/commit/f480b395256612de83b2f912bfecee03366bc990
  Author: Carl Meyer 
  Date:   2013-02-23 (Sat, 23 Feb 2013)

  Changed paths:
M docs/internals/howto-release-django.txt

  Log Message:
  ---
  Various tweaks and additions to 'how to release Django' document.



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

Re: [Django] #11295: If ModelAdmin.queryset returns a filtered QS don't require a 2nd count call

[Django]

#11295: If ModelAdmin.queryset returns a filtered QS don't require a 2nd count 
call
--+
 Reporter:  Alex  |Owner:  viciu
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  contrib.admin |  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
--+

Comment (by viciu):

 I've updated patch so it applies correctly on current master.
 Also, test in original patch assumes that there are 6 queries to db
 (including messages framework).

 Currently, before applying patch there are 5 of them (including duplicated
 COUNT(*):

 {{{
 (Pdb) pprint(connection.queries)
 [{'sql': 'QUERY = \'SELECT "django_session"."session_key",
 "django_session"."session_data", "django_session"."expire_date" FROM
 "django_session" WHERE ("django_session"."session_key" = %s  AND
 "django_session"."expire_date" > %s )\' - PARAMS =
 (\'2nj8364ycp90oge7xl5tf9mviz7grety\', \'2013-02-23 17:53:11.374277\')',
   'time': '0.000'},
  {'sql': 'QUERY = \'SELECT "auth_user"."id", "auth_user"."password",
 "auth_user"."last_login", "auth_user"."is_superuser",
 "auth_user"."username", "auth_user"."first_name", "auth_user"."last_name",
 "auth_user"."email", "auth_user"."is_staff", "auth_user"."is_active",
 "auth_user"."date_joined" FROM "auth_user" WHERE "auth_user"."id" = %s \'
 - PARAMS = (100,)',
   'time': '0.001'},
  {'sql': 'QUERY = \'SELECT COUNT(*) FROM "admin_views_emptymodel" WHERE
 "admin_views_emptymodel"."id" > %s \' - PARAMS = (1,)',
   'time': '0.000'},
  {'sql': 'QUERY = \'SELECT COUNT(*) FROM "admin_views_emptymodel" WHERE
 "admin_views_emptymodel"."id" > %s \' - PARAMS = (1,)',
   'time': '0.000'},
  {'sql': 'QUERY = \'SELECT "admin_views_emptymodel"."id" FROM
 "admin_views_emptymodel" WHERE "admin_views_emptymodel"."id" > %s  ORDER
 BY "admin_views_emptymodel"."id" DESC\' - PARAMS = (1,)',
   'time': '0.000'}]
 }}}

 After patch was applied, COUNT(*) is executed once:

 {{{
 (Pdb) pprint(connection.queries)
 [{'sql': 'QUERY = \'SELECT "django_session"."session_key",
 "django_session"."session_data", "django_session"."expire_date" FROM
 "django_session" WHERE ("django_session"."session_key" = %s  AND
 "django_session"."expire_date" > %s )\' - PARAMS =
 (\'5y65r95ng27kccdmkrtoo1qom7q4vhln\', \'2013-02-23 17:54:51.024189\')',
   'time': '0.000'},
  {'sql': 'QUERY = \'SELECT "auth_user"."id", "auth_user"."password",
 "auth_user"."last_login", "auth_user"."is_superuser",
 "auth_user"."username", "auth_user"."first_name", "auth_user"."last_name",
 "auth_user"."email", "auth_user"."is_staff", "auth_user"."is_active",
 "auth_user"."date_joined" FROM "auth_user" WHERE "auth_user"."id" = %s \'
 - PARAMS = (100,)',
   'time': '0.001'},
  {'sql': 'QUERY = \'SELECT COUNT(*) FROM "admin_views_emptymodel" WHERE
 "admin_views_emptymodel"."id" > %s \' - PARAMS = (1,)',
   'time': '0.000'},
  {'sql': 'QUERY = \'SELECT "admin_views_emptymodel"."id" FROM
 "admin_views_emptymodel" WHERE "admin_views_emptymodel"."id" > %s  ORDER
 BY "admin_views_emptymodel"."id" DESC\' - PARAMS = (1,)',
   'time': '0.000'}]
 }}}

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

Re: [Django] #19327: Admin doesn't handle double login attempts

[Django]

#19327: Admin doesn't handle double login attempts
-+-
 Reporter:  KJ   |Owner:  KJ
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  sensitive_post_parameters, login   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by ptone):

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


Comment:

 One further situation, similar to the one Julien brings up, is that if the
 second login is valid, but a different user, the current user should be
 logged out. Currently the patch just issues a message and proceeds.

 The truth is, both this scenario and the one Julien mentioned, the browser
 has been left by one user with a valid session - and so this isn't really
 a Django security issue per se, but if we are going to clean and tighten
 this up, might as well cover all the bases here with multiple tabs in a
 potentially shared environment.

 Otherwise this is looking good.

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

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

Re: [Django] #19888: MultiValueDictKeyError when saving Inlines without an AutoField

[Django]

#19888: MultiValueDictKeyError when saving Inlines without an AutoField
---+
 Reporter:  nickname123|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.4
 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 nickname123):

 * cc: wgordonw1@… (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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19888: MultiValueDictKeyError when saving Inlines without an AutoField

[Django]

#19888: MultiValueDictKeyError when saving Inlines without an AutoField
---+
 Reporter:  nickname123|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.4
 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 nickname123):

 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1
 * component:  Database layer (models, ORM) => contrib.admin


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

Re: [Django] #15198: AuthenticationForm.clean call does not have request set

[Django]

#15198: AuthenticationForm.clean call does not have request set
-+-
 Reporter:  Ciantic  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  contrib.auth |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Preston Holmes ):

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


Comment:

 In [changeset:"22d82a7742c3b091857fda8612273360459110ee"]:
 {{{
 #!CommitTicketReference repository=""
 revision="22d82a7742c3b091857fda8612273360459110ee"
 Fixed #15198 -- pass request to AuthenticationForm

 Thanks to Ciantic for the report, claudep and slurms for initial work
 }}}

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

[django/django] 9d2c0a: Removed superfluous cookie check from auth login.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 9d2c0a0ae6ce931699daa87735d5b8b2afaa20f9
  
https://github.com/django/django/commit/9d2c0a0ae6ce931699daa87735d5b8b2afaa20f9
  Author: Preston Holmes 
  Date:   2013-02-23 (Sat, 23 Feb 2013)

  Changed paths:
M django/contrib/admin/forms.py
M django/contrib/auth/forms.py
M django/contrib/auth/views.py
M docs/internals/deprecation.txt

  Log Message:
  ---
  Removed superfluous cookie check from auth login.

This is ensured through the CSRF protection of the view


  Commit: 22d82a7742c3b091857fda8612273360459110ee
  
https://github.com/django/django/commit/22d82a7742c3b091857fda8612273360459110ee
  Author: Preston Holmes 
  Date:   2013-02-23 (Sat, 23 Feb 2013)

  Changed paths:
M django/contrib/auth/forms.py
M django/contrib/auth/tests/urls.py
M django/contrib/auth/tests/views.py
M django/contrib/auth/views.py

  Log Message:
  ---
  Fixed #15198 -- pass request to AuthenticationForm

Thanks to Ciantic for the report, claudep and slurms for initial work


Compare: https://github.com/django/django/compare/b902a92b71c7...22d82a7742c3

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

Re: [Django] #19543: SimpleLazyObject missing __repr__ proxy

[Django]

#19543: SimpleLazyObject missing __repr__ proxy
-+-
 Reporter:  spinus   |Owner:  fhahn
 Type:  Bug  |   Status:  assigned
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  SimpleLazyObject | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by fhahn):

 forgot to link the github pull request:
 https://github.com/django/django/pull/709

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

Re: [Django] #18404: SuspiciousOperation exception is thrown if application static path contains non-ascii characters

[Django]

#18404: SuspiciousOperation exception is thrown if application static path 
contains
non-ascii characters
-+
 Reporter:  andkit@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  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 fhahn):

 * needs_better_patch:  1 => 0
 * version:  1.4 => master
 * needs_tests:  1 => 0


Comment:

 I've added a test for the patch and created a pull request:
 https://github.com/django/django/pull/814

 I put to decoding in FileSystemStorage.__init__, because AppStaticStorage
 is only a subclass of FileSystemStorage.

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

Re: [Django] #19543: SimpleLazyObject missing __repr__ proxy

[Django]

#19543: SimpleLazyObject missing __repr__ proxy
-+-
 Reporter:  spinus   |Owner:  fhahn
 Type:  Bug  |   Status:  assigned
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  SimpleLazyObject | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by oinopion):

 * stage:  Accepted => Ready for checkin


Comment:

 Looks good!

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

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

Re: [Django] #17905: Admin documentation lists all models, even for users without access to certain applications

[Django]

#17905: Admin documentation lists all models, even for users without access to
certain applications
-+-
 Reporter:  chriscohoat  |Owner:
 Type:  New feature  |  gszczepanczyk
Component:  contrib.admindocs|   Status:  assigned
 Severity:  Normal   |  Version:
 Keywords:   |  1.4-alpha-1
Has patch:  1|   Resolution:
  Needs tests:  1| Triage Stage:  Accepted
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by gszczepanczyk):

 * owner:  Rizach => gszczepanczyk
 * status:  new => assigned


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

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

[django/django] b902a9: Sorry, accidental commit, Thanks claudep for catch...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b902a92b71c76b2c154f7e55ded9161e6d146825
  
https://github.com/django/django/commit/b902a92b71c76b2c154f7e55ded9161e6d146825
  Author: Honza Kral 
  Date:   2013-02-23 (Sat, 23 Feb 2013)

  Changed paths:
M setup.py

  Log Message:
  ---
  Sorry, accidental commit, Thanks claudep for catching it!



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

Re: [Django] #19263: DatabaseError on using empty Page .object_list in __in clause in a query

[Django]

#19263: DatabaseError on using empty Page .object_list in __in clause in a query
-+-
 Reporter:  chkwok@… |Owner:  biern
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Marcin Biernat ):

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


Comment:

 In [changeset:"2b76f19f2b89ac96bae2a169d71b23553c8101c7"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2b76f19f2b89ac96bae2a169d71b23553c8101c7"
 fixes #19263
 }}}

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

Re: [Django] #19263: DatabaseError on using empty Page .object_list in __in clause in a query

[Django]

#19263: DatabaseError on using empty Page .object_list in __in clause in a query
-+-
 Reporter:  chkwok@… |Owner:  biern
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Honza Král ):

 In [changeset:"fc38d6a92be8baec1d02fbdf95e56c4204b9425b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="fc38d6a92be8baec1d02fbdf95e56c4204b9425b"
 Merge pull request #813 from HiddenData/ticket-19263

 fixes #19263 - EmptyResultSet in subquery causes incorrect SQL
 }}}

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

[django/django] 2b76f1: fixes #19263

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2b76f19f2b89ac96bae2a169d71b23553c8101c7
  
https://github.com/django/django/commit/2b76f19f2b89ac96bae2a169d71b23553c8101c7
  Author: Marcin Biernat 
  Date:   2013-02-23 (Sat, 23 Feb 2013)

  Changed paths:
M django/db/models/sql/where.py
M tests/regressiontests/queries/tests.py

  Log Message:
  ---
  fixes #19263


  Commit: fc38d6a92be8baec1d02fbdf95e56c4204b9425b
  
https://github.com/django/django/commit/fc38d6a92be8baec1d02fbdf95e56c4204b9425b
  Author: Honza Král 
  Date:   2013-02-23 (Sat, 23 Feb 2013)

  Changed paths:
M django/db/models/sql/where.py
M tests/regressiontests/queries/tests.py

  Log Message:
  ---
  Merge pull request #813 from HiddenData/ticket-19263

fixes #19263 - EmptyResultSet in subquery causes incorrect SQL


Compare: https://github.com/django/django/compare/692902b227b4...fc38d6a92be8

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

Re: [Django] #18255: Inconsistent data type for BigIntegerField after calling full_clean()

[Django]

#18255: Inconsistent data type for BigIntegerField after calling full_clean()
-+-
 Reporter:  anonymous|Owner:  adamduren
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

 * needs_better_patch:  0 => 1


Comment:

 The patch doesn't account for Python 3 (where `long` type doesn't exist).

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

Re: [Django] #19263: DatabaseError on using empty Page .object_list in __in clause in a query

[Django]

#19263: DatabaseError on using empty Page .object_list in __in clause in a query
-+-
 Reporter:  chkwok@… |Owner:  biern
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.4
  (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
-+-

Comment (by biern):

 Fixed by checking for empty sql params
 https://github.com/django/django/pull/813

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

Re: [Django] #19899: Add attr request in user_login_failed signal

[Django]

#19899: Add attr request in user_login_failed signal
--+--
 Reporter:  anonymous |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:  wontfix
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by claudep):

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


Comment:

 Yes, #15198 is the ticket to fix so as the request is available.

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

Re: [Django] #19464: The markup for ClearableFileInput's link should be a widget template string

[Django]

#19464: The markup for ClearableFileInput's link should be a widget template 
string
-+-
 Reporter:  rubyruy  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:
 Severity:  Normal   |  1.5-beta-1
 Keywords:  widget   |   Resolution:
  ClearableFileInput | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by rubyruy):

 Err... as far as as I can tell, this is an internal implementation detail
 that is only relevant when sub-classing - it's not really documented for
 any of the other widgets.

 Nor is this change specifically testable - unless you mean this breaks an
 existing test (which I didn't think it did...)

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

Re: [Django] #19899: Add attr request in user_login_failed signal

[Django]

#19899: Add attr request in user_login_failed signal
--+--
 Reporter:  anonymous |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by alej0):

 This doesn't solve the issue of request not being passed to the
 user_login_failed signal but solves request being passed to
 authentication_form and backs claudep argument.

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

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

Re: [Django] #19609: admin Inlines doesn't display help_text for readonly fields

[Django]

#19609: admin Inlines doesn't display help_text for readonly fields
-+-
 Reporter:  glic3rinu|Owner:  viciu
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  admin inline | Triage Stage:  Ready for
  help_text readonly |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-

Comment (by Honza Král ):

 In [changeset:"692902b227b4aff8a4ec66fa8d4ac2d3128bcac0"]:
 {{{
 #!CommitTicketReference repository=""
 revision="692902b227b4aff8a4ec66fa8d4ac2d3128bcac0"
 Merge pull request #778 from viciu/19609

 Fixed #19609: admin Inlines doesn't display help_text for readonly fields
 }}}

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

Re: [Django] #19609: admin Inlines doesn't display help_text for readonly fields

[Django]

#19609: admin Inlines doesn't display help_text for readonly fields
-+-
 Reporter:  glic3rinu|Owner:  viciu
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  admin inline | Triage Stage:  Ready for
  help_text readonly |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-
Changes (by Wiktor Kolodziej ):

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


Comment:

 In [changeset:"67dd54dc841a93a67eac87dc13ed047d72f920dc"]:
 {{{
 #!CommitTicketReference repository=""
 revision="67dd54dc841a93a67eac87dc13ed047d72f920dc"
 Fixed #19609: admin Inlines doesn't display help_text for readonly fields

 Refactoring: field was renamed to field_name, since flatten_fieldsets
 returns field name, not field.

 Original patch from Marc Aymerich Gubern
 }}}

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

[django/django] 67dd54: Fixed #19609: admin Inlines doesn't display help_t...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 67dd54dc841a93a67eac87dc13ed047d72f920dc
  
https://github.com/django/django/commit/67dd54dc841a93a67eac87dc13ed047d72f920dc
  Author: Wiktor Kolodziej 
  Date:   2013-02-23 (Sat, 23 Feb 2013)

  Changed paths:
M AUTHORS
M django/contrib/admin/helpers.py
M tests/regressiontests/admin_inlines/admin.py
M tests/regressiontests/admin_inlines/models.py
M tests/regressiontests/admin_inlines/tests.py

  Log Message:
  ---
  Fixed #19609: admin Inlines doesn't display help_text for readonly fields

Refactoring: field was renamed to field_name, since flatten_fieldsets returns 
field name, not field.

Original patch from Marc Aymerich Gubern


  Commit: 692902b227b4aff8a4ec66fa8d4ac2d3128bcac0
  
https://github.com/django/django/commit/692902b227b4aff8a4ec66fa8d4ac2d3128bcac0
  Author: Honza Král 
  Date:   2013-02-23 (Sat, 23 Feb 2013)

  Changed paths:
M AUTHORS
M django/contrib/admin/helpers.py
M tests/regressiontests/admin_inlines/admin.py
M tests/regressiontests/admin_inlines/models.py
M tests/regressiontests/admin_inlines/tests.py

  Log Message:
  ---
  Merge pull request #778 from viciu/19609

Fixed #19609: admin Inlines doesn't display help_text for readonly fields


Compare: https://github.com/django/django/compare/ef1e6ef1eb54...692902b227b4

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

Re: [Django] #19872: cached_property doesn't behave properly when accessed through the class

[Django]

#19872: cached_property doesn't behave properly when accessed through the class
-+-
 Reporter:  simonpercivall   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Core (Other) |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tomek Paczkowski ):

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


Comment:

 In [changeset:"b88abd684041ffa66bfe445e1ac26164e803d488"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b88abd684041ffa66bfe445e1ac26164e803d488"
 Fixed #19872

 Made cached_property to behave as property when accessed via class.
 }}}

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

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

[django/django] b88abd: Fixed #19872

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b88abd684041ffa66bfe445e1ac26164e803d488
  
https://github.com/django/django/commit/b88abd684041ffa66bfe445e1ac26164e803d488
  Author: Tomek Paczkowski 
  Date:   2013-02-23 (Sat, 23 Feb 2013)

  Changed paths:
M django/utils/functional.py
M tests/regressiontests/utils/functional.py

  Log Message:
  ---
  Fixed #19872

Made cached_property to behave as property when accessed via class.


  Commit: ef1e6ef1eb5495b168f9fc642eca235e71e51dde
  
https://github.com/django/django/commit/ef1e6ef1eb5495b168f9fc642eca235e71e51dde
  Author: Honza Kral 
  Date:   2013-02-23 (Sat, 23 Feb 2013)

  Changed paths:
M django/utils/functional.py
M tests/regressiontests/utils/functional.py

  Log Message:
  ---
  Merge branch 'ticket19872' of https://github.com/oinopion/django


Compare: https://github.com/django/django/compare/2b48fcc60701...ef1e6ef1eb54

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

Re: [Django] #19609: admin Inlines doesn't display help_text for readonly fields

[Django]

#19609: admin Inlines doesn't display help_text for readonly fields
-+-
 Reporter:  glic3rinu|Owner:  viciu
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin inline | Triage Stage:  Ready for
  help_text readonly |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-
Changes (by oinopion):

 * stage:  Accepted => Ready for checkin


Comment:

 Reviewed. Good for 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #14485: New Site.root field

[Django]

#14485: New Site.root field
---+-
 Reporter:  gsakkis|Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.sites  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Someday/Maybe
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by gszczepanczyk):

 * cc: g.szczepanczyk@… (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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19891: Travis CI support

[Django]

#19891: Travis CI support
--+
 Reporter:  marko@…   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  Travis, CI, testing   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by jacob):

 * stage:  Unreviewed => Accepted


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

Re: [Django] #19891: Travis CI support

[Django]

#19891: Travis CI support
-+-
 Reporter:  marko@…  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Testing framework|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  Travis, CI, testing  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jacob):

 Hm, 45 minutes isn't bad; Travis (or our tests) must have gotten faster
 since last I checked. So I'll drop my objection.

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

Re: [Django] #18491: When deleting a proxy model, the admin does not show warning about cascade delete for object with foreign key on the proxied model

[Django]

#18491: When deleting a proxy model, the admin does not show warning about 
cascade
delete for object with foreign key on the proxied model
-+-
 Reporter:  bdauvergne@… |Owner:
 Type:  Bug  |  gszczepanczyk
Component:  contrib.admin|   Status:  closed
 Severity:  Normal   |  Version:  1.4
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Honza Kral ):

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


Comment:

 In [changeset:"2b48fcc607010065c0f8107baf669dd41b164f3c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2b48fcc607010065c0f8107baf669dd41b164f3c"
 Fixed #18491 -- deleting a proxy doesn't show warning about cascade
 deletes
 }}}

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

[django/django] 2b48fc: Fixed #18491 -- deleting a proxy doesn't show warn...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2b48fcc607010065c0f8107baf669dd41b164f3c
  
https://github.com/django/django/commit/2b48fcc607010065c0f8107baf669dd41b164f3c
  Author: Honza Kral 
  Date:   2013-02-23 (Sat, 23 Feb 2013)

  Changed paths:
M django/contrib/admin/util.py
M setup.py
A tests/modeltests/proxy_models/fixtures/myhorses.json
M tests/modeltests/proxy_models/tests.py

  Log Message:
  ---
  Fixed #18491 -- deleting a proxy doesn't show warning about cascade deletes



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

Re: [Django] #19896: Running `clear.cache()` using PostgreSQL does not remove rows

[Django]

#19896: Running `clear.cache()` using PostgreSQL does not remove rows
-+
 Reporter:  gsong|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Cache system)  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+

Comment (by gsong):

 Attempt at fix: https://github.com/django/django/pull/811

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

Re: [Django] #19526: CachedFilesMixin.patterns should be case-insensitive

[Django]

#19526: CachedFilesMixin.patterns should be case-insensitive
-+-
 Reporter:  mike@…   |Owner:  ethlinn
 Type:  Bug  |   Status:  closed
Component:  contrib.staticfiles  |  Version:  1.4
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  CachedFilesMixin | Triage Stage:  Ready for
  staticfiles|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Honza Král ):

 In [changeset:"83ecb7b145644a1489db4137ac4d779bf1f294ca"]:
 {{{
 #!CommitTicketReference repository=""
 revision="83ecb7b145644a1489db4137ac4d779bf1f294ca"
 Merge pull request #809 from asendecka/ticket19526

 Fixed #19526 - make regexes for css case insensitive
 }}}

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

Re: [Django] #19526: CachedFilesMixin.patterns should be case-insensitive

[Django]

#19526: CachedFilesMixin.patterns should be case-insensitive
-+-
 Reporter:  mike@…   |Owner:  ethlinn
 Type:  Bug  |   Status:  closed
Component:  contrib.staticfiles  |  Version:  1.4
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  CachedFilesMixin | Triage Stage:  Ready for
  staticfiles|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Aleksandra Sendecka ):

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


Comment:

 In [changeset:"32a7ab21482ef06f7e01a70fad8495f659c4d29f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="32a7ab21482ef06f7e01a70fad8495f659c4d29f"
 Fixed #19526

 CSS specifications governs that syntax is case insensitive.
 This modifies CachedFilesMixin to support that.
 }}}

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

[django/django] 32a7ab: Fixed #19526

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 32a7ab21482ef06f7e01a70fad8495f659c4d29f
  
https://github.com/django/django/commit/32a7ab21482ef06f7e01a70fad8495f659c4d29f
  Author: Aleksandra Sendecka 
  Date:   2013-02-23 (Sat, 23 Feb 2013)

  Changed paths:
M django/contrib/staticfiles/storage.py
A 
tests/regressiontests/staticfiles_tests/project/documents/cached/styles_insensitive.css
M tests/regressiontests/staticfiles_tests/tests.py

  Log Message:
  ---
  Fixed #19526

CSS specifications governs that syntax is case insensitive.
This modifies CachedFilesMixin to support that.


  Commit: 83ecb7b145644a1489db4137ac4d779bf1f294ca
  
https://github.com/django/django/commit/83ecb7b145644a1489db4137ac4d779bf1f294ca
  Author: Honza Král 
  Date:   2013-02-23 (Sat, 23 Feb 2013)

  Changed paths:
M django/contrib/staticfiles/storage.py
A 
tests/regressiontests/staticfiles_tests/project/documents/cached/styles_insensitive.css
M tests/regressiontests/staticfiles_tests/tests.py

  Log Message:
  ---
  Merge pull request #809 from asendecka/ticket19526

Fixed #19526 - make regexes for css case insensitive


Compare: https://github.com/django/django/compare/1c11ee63459c...83ecb7b14564

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

Re: [Django] #18255: Inconsistent data type for BigIntegerField after calling full_clean()

[Django]

#18255: Inconsistent data type for BigIntegerField after calling full_clean()
-+-
 Reporter:  anonymous|Owner:  adamduren
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by adamduren):

 * has_patch:  0 => 1


Comment:

 Fixed and tests written, pull request
 https://github.com/django/django/pull/810

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

Re: [Django] #19526: CachedFilesMixin.patterns should be case-insensitive

[Django]

#19526: CachedFilesMixin.patterns should be case-insensitive
-+-
 Reporter:  mike@…   |Owner:  ethlinn
 Type:  Bug  |   Status:  assigned
Component:  contrib.staticfiles  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  CachedFilesMixin | Triage Stage:  Ready for
  staticfiles|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by oinopion):

 * stage:  Accepted => Ready for checkin


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

Re: [Django] #19263: DatabaseError on using empty Page .object_list in __in clause in a query

[Django]

#19263: DatabaseError on using empty Page .object_list in __in clause in a query
-+-
 Reporter:  chkwok@… |Owner:  biern
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.4
  (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 gszczepanczyk):

 * stage:  Accepted => Ready for checkin


Comment:

 seems ok

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

Re: [Django] #19526: CachedFilesMixin.patterns should be case-insensitive

[Django]

#19526: CachedFilesMixin.patterns should be case-insensitive
-+-
 Reporter:  mike@…   |Owner:  ethlinn
 Type:  Bug  |   Status:  assigned
Component:  contrib.staticfiles  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  CachedFilesMixin | Triage Stage:  Accepted
  staticfiles|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by ethlinn):

 * cc: asendecka@… (added)
 * status:  new => assigned
 * has_patch:  0 => 1
 * owner:  nobody => ethlinn


Comment:

 I added patch:
 https://github.com/django/django/pull/809

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

Re: [Django] #19526: CachedFilesMixin.patterns should be case-insensitive

[Django]

#19526: CachedFilesMixin.patterns should be case-insensitive
-+-
 Reporter:  mike@…   |Owner:  ethlinn
 Type:  Bug  |   Status:  assigned
Component:  contrib.staticfiles  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  CachedFilesMixin | Triage Stage:  Accepted
  staticfiles|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by ethlinn):

 * owner:  nobody => ethlinn
 * cc: asendecka@… (added)
 * has_patch:  0 => 1
 * status:  new => assigned


Comment:

 I added patch:
 https://github.com/django/django/pull/809

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

Re: [Django] #19526: CachedFilesMixin.patterns should be case-insensitive

[Django]

#19526: CachedFilesMixin.patterns should be case-insensitive
-+-
 Reporter:  mike@…   |Owner:  ethlinn
 Type:  Bug  |   Status:  assigned
Component:  contrib.staticfiles  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  CachedFilesMixin | Triage Stage:  Accepted
  staticfiles|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by ethlinn):

 * cc: asendecka@… (added)
 * status:  new => assigned
 * has_patch:  0 => 1
 * owner:  nobody => ethlinn


Comment:

 I added patch:
 https://github.com/django/django/pull/809

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

Re: [Django] #19526: CachedFilesMixin.patterns should be case-insensitive

[Django]

#19526: CachedFilesMixin.patterns should be case-insensitive
-+-
 Reporter:  mike@…   |Owner:  ethlinn
 Type:  Bug  |   Status:  assigned
Component:  contrib.staticfiles  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  CachedFilesMixin | Triage Stage:  Accepted
  staticfiles|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by ethlinn):

 * cc: asendecka@… (added)
 * status:  new => assigned
 * has_patch:  0 => 1
 * owner:  nobody => ethlinn


Comment:

 I added patch:
 https://github.com/django/django/pull/809

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

Re: [Django] #19263: DatabaseError on using empty Page .object_list in __in clause in a query

[Django]

#19263: DatabaseError on using empty Page .object_list in __in clause in a query
-+-
 Reporter:  chkwok@… |Owner:  biern
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.4
  (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 gszczepanczyk):

 * stage:  Accepted => Ready for checkin


Comment:

 seems ok

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

Re: [Django] #19899: Add attr request in user_login_failed signal

[Django]

#19899: Add attr request in user_login_failed signal
--+--
 Reporter:  anonymous |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by anonymous):

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


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

Re: [Django] #18583: exclude generates wrong SQL query

[Django]

#18583: exclude generates wrong SQL query
-+-
 Reporter:  rbreu|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  query exclude sql|  Needs documentation:  0
  sprints-django-ar  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by fgallina):

 * keywords:  query exclude sql => query exclude sql sprints-django-ar
 * status:  new => closed
 * resolution:   => fixed


Comment:

 this shows as working in current HEAD.

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

Re: [Django] #19899: Add attr request in user_login_failed signal

[Django]

#19899: Add attr request in user_login_failed signal
--+--
 Reporter:  anonymous |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:  wontfix
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by anonymous):

 How, if form is not receive request?

 contrib.auth.view:

 @sensitive_post_parameters()
 @csrf_protect
 @never_cache
 def login(request, template_name='registration/login.html',
   redirect_field_name=REDIRECT_FIELD_NAME,
   authentication_form=AuthenticationForm,
   current_app=None, extra_context=None):
 """
 Displays the login form and handles the login action.
 """
 redirect_to = request.REQUEST.get(redirect_field_name, '')

 if request.method == "POST":
 form = authentication_form(data=request.POST)  # THIS NEED APPEND
 request
 if form.is_valid():
 ...

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

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

Re: [Django] #19899: Add attr request in user_login_failed signal

[Django]

#19899: Add attr request in user_login_failed signal
--+--
 Reporter:  anonymous |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:  wontfix
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by anonymous):

 How, if form is not receive request?

 contrib.auth.view:

 @sensitive_post_parameters()
 @csrf_protect
 @never_cache
 def login(request, template_name='registration/login.html',
   redirect_field_name=REDIRECT_FIELD_NAME,
   authentication_form=AuthenticationForm,
   current_app=None, extra_context=None):
 """
 Displays the login form and handles the login action.
 """
 redirect_to = request.REQUEST.get(redirect_field_name, '')

 if request.method == "POST":
 form = authentication_form(data=request.POST)  # THIS NEED APPEND
 request
 if form.is_valid():
 ...

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

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

Re: [Django] #19582: Add tutorial on static files

[Django]

#19582: Add tutorial on static files
-+-
 Reporter:  jpic |Owner:  reinout
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  docs, static files,  |  Needs documentation:  0
  sprint2013 |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by timo):

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


Comment:

 This isn't quite RFC, I've left some comments on the pull request.

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

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

Re: [Django] #19263: DatabaseError on using empty Page .object_list in __in clause in a query

[Django]

#19263: DatabaseError on using empty Page .object_list in __in clause in a query
-+-
 Reporter:  chkwok@… |Owner:  biern
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by biern):

 * component:  Core (Other) => Database layer (models, ORM)


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

Re: [Django] #19763: LocaleMiddleware should check for supported languages in settings.LANGUAGE_CODE too

[Django]

#19763: LocaleMiddleware should check for supported languages in
settings.LANGUAGE_CODE too
--+
 Reporter:  kozz  |Owner:  ambv
 Type:  Bug   |   Status:  assigned
Component:  Internationalization  |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:  locale| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by oinopion):

 * needs_tests:  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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19263: DatabaseError on using empty Page .object_list in __in clause in a query

[Django]

#19263: DatabaseError on using empty Page .object_list in __in clause in a query
--+
 Reporter:  chkwok@…  |Owner:  biern
 Type:  Bug   |   Status:  assigned
Component:  Core (Other)  |  Version:  1.4
 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 biern):

 * has_patch:  0 => 1


Comment:

 This was a bug related to improper behaviour of querysets sliced with
 equal indices, which generated empty sql that caused errors when used in
 subqueries.

 This query failed:
 Book.objects.filter(author__in=Author.objects.empty()[0:0])
 while this succeded:
 Book.objects.filter(author__in=Author.objects.empty())

 Instead of later returning empty sql string, a QuerySet with equal indices
 is now immediately converted to QuerySet.none().

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

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

Re: [Django] #18829: ModelChoiceIterator doesn't adjust its length to account for an empty item.

[Django]

#18829: ModelChoiceIterator doesn't adjust its length to account for an empty 
item.
-+-
 Reporter:  facundo.olano@…  |Owner:
 Type:  Bug  |  vanschelven
Component:  Forms|   Status:  closed
 Severity:  Normal   |  Version:  1.4
 Keywords:  ModelChoiceIterator  |   Resolution:  fixed
  ModelForm  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"1c11ee63459c4362affbd6a20f2ddf9c2ecd8dce"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1c11ee63459c4362affbd6a20f2ddf9c2ecd8dce"
 Fixed #18829 -- Fixed ModelChoiceIterator length

 Thanks facundo.olano at gmail.com for the report and thikonom for
 the initial patch.
 }}}

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

[django/django] 1c11ee: Fixed #18829 -- Fixed ModelChoiceIterator length

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1c11ee63459c4362affbd6a20f2ddf9c2ecd8dce
  
https://github.com/django/django/commit/1c11ee63459c4362affbd6a20f2ddf9c2ecd8dce
  Author: Klaas van Schelven 
  Date:   2013-02-23 (Sat, 23 Feb 2013)

  Changed paths:
M django/forms/models.py
M tests/modeltests/model_forms/tests.py

  Log Message:
  ---
  Fixed #18829 -- Fixed ModelChoiceIterator length

Thanks facundo.olano at gmail.com for the report and thikonom for
the initial patch.



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

Re: [Django] #19898: Document why/when of class-based views

[Django]

#19898: Document why/when of class-based views
-+--
 Reporter:  estebistec   |Owner:  estebistec
 Type:  Uncategorized|   Status:  assigned
Component:  Uncategorized|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  docs sprint2013  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by estebistec):

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


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

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

Re: [Django] #19898: Document why/when of class-based views

[Django]

#19898: Document why/when of class-based views
-+
 Reporter:  estebistec   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Uncategorized|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  docs sprint2013  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by estebistec):

 * keywords:  docs => docs sprint2013


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

Re: [Django] #18583: exclude generates wrong SQL query

[Django]

#18583: exclude generates wrong SQL query
-+-
 Reporter:  rbreu|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  query exclude sql|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by fgallina):

 This bug is invalid, as the generated SQL is correct.

 Given this full example:

 #models
 from django.utils.encoding import python_2_unicode_compatible
 from django.contrib.auth.models import Group


 # Models for #19659
 @python_2_unicode_compatible
 class A(models.Model):
 pass

 def __str__(self):
 return str(self.pk)

 @python_2_unicode_compatible
 class B(models.Model):
 a = models.ForeignKey(A)

 def __str__(self):
 return str(self.pk)

 @python_2_unicode_compatible
 class C(models.Model):
 b = models.ForeignKey(B)

 def __str__(self):
 return str(self.pk)

 @python_2_unicode_compatible
 class D(models.Model):
 a = models.ForeignKey(A)
 group = models.ForeignKey(Group)

 def __str__(self):
 return str(self.pk)

 The following query:

 C.objects.exclude(b__a__d__group__in=[foo]).order_by('pk')

 Results in:

 SELECT "queries_c"."id", "queries_c"."b_id" FROM "queries_c"
INNER JOIN "queries_b" ON ("queries_c"."b_id" = "queries_b"."id")
WHERE NOT (("queries_b"."a_id" IN
(SELECT U3."a_id" FROM "queries_d" U3 WHERE
 U3."group_id" IN (1))
AND "queries_b"."a_id" IS NOT NULL))

 Which is correct, as the filtering is taken to the a.id field (see the
 inner SELECT).

 Attached is a diff which adds tests showing the query is returning
 expected results.

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

Re: [Django] #19891: Travis CI support

[Django]

#19891: Travis CI support
-+-
 Reporter:  marko@…  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Testing framework|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  Travis, CI, testing  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by dokterbob):

 There's a pull request now, running the tests:
 https://github.com/django/django/pull/805

 The tests take 25-45 minutes to run, which is not 'forever' AFAIK. Travis
 runs 3-5 builds in parallel which actually makes it fairly fast. However,
 somehow, Travis adds up the time for the individual builds to come up with
 a rather unrealistic build time of multiple hours.

 As the core dev's have a Jenkins CI anyways, this shouldn't matter too
 much for them. However, many contributors would benefit tremendously by
 being able to test their code throughly even before firing pull requests -
 which is the main point of this patch. And lastly, it *might* happen that
 Travis finds issues which (somehow) slip through the mazes of the Jenkins
 CI, as was the case while we set up the testing system. (Ref:
 
https://github.com/django/django/commit/8c1cc4b3b04f639ae40bc806380bc4a9dd568eb0)

 However, having it run on 4 Python versions might indeed be too much.
 Which two Python releases do you suggest we use?

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

Re: [Django] #19897: Improve static files documentation

[Django]

#19897: Improve static files documentation
-+-
 Reporter:  wimfeijen|Owner:  wimfeijen
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  staticfiles  |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by wimfeijen):

 For the record: this patch was written by Jan Murre, Reinout van Rees and
 Wim Feijen, and reviewed by Remco Wendt

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

Re: [Django] #19582: Add tutorial on static files

[Django]

#19582: Add tutorial on static files
-+-
 Reporter:  jpic |Owner:  reinout
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  docs, static files,  |  checkin
  sprint2013 |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by wimfeijen):

 Well written!

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

Re: [Django] #19872: cached_property doesn't behave properly when accessed through the class

[Django]

#19872: cached_property doesn't behave properly when accessed through the class
-+-
 Reporter:  simonpercivall   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Core (Other) |   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 oinopion):

 * stage:  Accepted => Ready for checkin


Comment:

 I've squashed patches into one.

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

Re: [Django] #19898: Document why/when of class-based views

[Django]

#19898: Document why/when of class-based views
---+
 Reporter:  estebistec |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  docs   | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by jacob):

 * stage:  Unreviewed => Accepted


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

Re: [Django] #19896: Running `clear.cache()` using PostgreSQL does not remove rows

[Django]

#19896: Running `clear.cache()` using PostgreSQL does not remove rows
-+
 Reporter:  gsong|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Cache system)  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by jacob):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Accepted
 * needs_tests:   => 0
 * needs_docs:   => 0


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

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

Re: [Django] #17919: Release process could use some more detail about beta and release candidates

[Django]

#17919: Release process could use some more detail about beta and release
candidates
-+-
 Reporter:  ptone|Owner:  aaugustin
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 Tentatively assigning to myself.

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

Re: [Django] #19891: Travis CI support

[Django]

#19891: Travis CI support
-+-
 Reporter:  marko@…  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Testing framework|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  Travis, CI, testing  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by jacob):

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


Comment:

 I don't think having Travis test all versions is such a good idea. Right
 now the build generates 12 different builds for each pull request which'll
 take approximately forever to run. Asking people to wait on pull requests
 while a dozen different builds run is... not so good.

 Instead, how about using Travis to augment what we already have in
 Jenkins? Just have it run maybe two builds -- Python 2 and Python 3? That
 was contributors can get a quick feedback on a pull request, but don't
 have to wait forever.

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

[django/django] 150e20: Some style fixes for stuff that was clearly brough...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 150e202172034adb5175663411b15efacca52aae
  
https://github.com/django/django/commit/150e202172034adb5175663411b15efacca52aae
  Author: Alex Gaynor 
  Date:   2013-02-23 (Sat, 23 Feb 2013)

  Changed paths:
M tests/regressiontests/transactions_regress/models.py
M tests/regressiontests/transactions_regress/tests.py

  Log Message:
  ---
  Some style fixes for stuff that was clearly brough tover from doctests.



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

Re: [Django] #19775: database configuration without "default" not supported

[Django]

#19775: database configuration without "default" not supported
---+-
 Reporter:  monkut |Owner:  wsmith323
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 Keywords:  multipledbs| 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:"72db38facc2b713046ad25a1a5034fcbc328478c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="72db38facc2b713046ad25a1a5034fcbc328478c"
 [1.5.X] Added an example of "default" database dictionary left blank; refs
 #19775.

 Thanks wsmith323 for the patch.

 Backport of cf890c110e 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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 72db38: [1.5.X] Added an example of "default" database dic...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 72db38facc2b713046ad25a1a5034fcbc328478c
  
https://github.com/django/django/commit/72db38facc2b713046ad25a1a5034fcbc328478c
  Author: Tim Graham 
  Date:   2013-02-23 (Sat, 23 Feb 2013)

  Changed paths:
M docs/topics/db/multi-db.txt

  Log Message:
  ---
  [1.5.X] Added an example of "default" database dictionary left blank; refs 
#19775.

Thanks wsmith323 for the patch.

Backport of cf890c110e 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #8424: Implement time filters

[Django]

#8424: Implement time filters
-+-
 Reporter:  gnuvince |Owner:  UloPe
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  datetime filter  |  Needs documentation:  0
  hour minute second |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 Fixed in e74e207cce54802f897adcb42149440ee154821e.

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

Re: [Django] #19775: database configuration without "default" not supported

[Django]

#19775: database configuration without "default" not supported
---+-
 Reporter:  monkut |Owner:  wsmith323
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 Keywords:  multipledbs| 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:"cf890c110e159de16d54a59dc878272776d38514"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cf890c110e159de16d54a59dc878272776d38514"
 Added an example of "default" database dictionary left blank; refs #19775.

 Thanks wsmith323 for the patch.
 }}}

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

[django/django] cf890c: Added an example of "default" database dictionary ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: cf890c110e159de16d54a59dc878272776d38514
  
https://github.com/django/django/commit/cf890c110e159de16d54a59dc878272776d38514
  Author: Tim Graham 
  Date:   2013-02-23 (Sat, 23 Feb 2013)

  Changed paths:
M docs/topics/db/multi-db.txt

  Log Message:
  ---
  Added an example of "default" database dictionary left blank; refs #19775.

Thanks wsmith323 for the patch.



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

Re: [Django] #19890: ifchanged tag renders the nodelist_true part twice

[Django]

#19890: ifchanged tag renders the nodelist_true part twice
--+
 Reporter:  vdboor|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Template system   |  Version:  1.4
 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 jacob):

 * stage:  Unreviewed => Accepted


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

Re: [Django] #14263: Allow fields to support custom double-underscore lookup methods

[Django]

#14263: Allow fields to support custom double-underscore lookup methods
-+-
 Reporter:  carljm   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by marcosmoyano):

 I believe this is related: https://code.djangoproject.com/ticket/6439

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

Re: [Django] #19900: Upgrade admin buttons

[Django]

#19900: Upgrade admin buttons
-+-
 Reporter:  Pedro Mourelle   |Owner:  anonymous
  |   Status:  assigned
 Type:  Uncategorized|  Version:
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  sprints-django-ar|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  1
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * stage:  Unreviewed => Accepted


Comment:

 Absolutely — this defect is noticeable on hipster-displays (aka retina).

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

Re: [Django] #19874: Add id to element in CheckboxSelectMultiple

[Django]

#19874: Add id to  element in CheckboxSelectMultiple
--+
 Reporter:  l3on  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Forms |  Version:
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by oinopion):

 * needs_docs:  0 => 1
 * needs_tests:  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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #6585: admin foreignkey dropdown does not adhere to model's admin ordering

[Django]

#6585: admin foreignkey dropdown does not adhere to model's admin ordering
-+-
 Reporter:  gwilson  |Owner:  fisadev
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  newforms-
 Severity:  Normal   |  admin
 Keywords:  #sprints-django-ar   |   Resolution:
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  1
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by fisadev):

 * keywords:   => #sprints-django-ar


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

Re: [Django] #6585: admin foreignkey dropdown does not adhere to model's admin ordering

[Django]

#6585: admin foreignkey dropdown does not adhere to model's admin ordering
---+--
 Reporter:  gwilson|Owner:  fisadev
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  newforms-admin
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by fisadev):

 (pull request done as part of #sprints-django-ar :)

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

Re: [Django] #19282: intcomma for decimal no longer works as expected

[Django]

#19282: intcomma for decimal no longer works as expected
-+-
 Reporter:  judy |Owner:  hernantz
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  contrib.humanize |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  intcomma, humanize,  |  checkin
  decimal, sprints-django-ar |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"7e6ad76b24a003bfb4ced8d9b3b22a46c1590e02"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7e6ad76b24a003bfb4ced8d9b3b22a46c1590e02"
 Fixed #19282 -- Restored ability to pass Decimals to intcomma filter
 }}}

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

[django/django] 7e6ad7: Fixed #19282 -- Restored ability to pass Decimals ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 7e6ad76b24a003bfb4ced8d9b3b22a46c1590e02
  
https://github.com/django/django/commit/7e6ad76b24a003bfb4ced8d9b3b22a46c1590e02
  Author: Hernan Lozano 
  Date:   2013-02-23 (Sat, 23 Feb 2013)

  Changed paths:
M django/contrib/humanize/templatetags/humanize.py
M django/contrib/humanize/tests.py

  Log Message:
  ---
  Fixed #19282 -- Restored ability to pass Decimals to intcomma filter



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

Re: [Django] #5849: Strip indentation and leading/trailing spaces/linebreaks from contents of blocktrans block.

[Django]

#5849: Strip indentation and leading/trailing spaces/linebreaks from contents of
blocktrans block.
-+-
 Reporter:  Dmitri Fedortchenko  |Owner:  mpessas
  |   Status:  assigned
 Type:  New feature  |  Version:  master
Component:   |   Resolution:
  Internationalization   | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  blocktrans strip |  Patch needs improvement:  0
  indentation|UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by mpessas):

 * owner:  nobody => mpessas
 * needs_better_patch:  1 => 0
 * status:  new => assigned


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

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

Re: [Django] #6585: admin foreignkey dropdown does not adhere to model's admin ordering

[Django]

#6585: admin foreignkey dropdown does not adhere to model's admin ordering
---+--
 Reporter:  gwilson|Owner:  fisadev
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  newforms-admin
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by fisadev):

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


Comment:

 Proposed implementation on pull request 806:

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

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

Re: [Django] #19775: database configuration without "default" not supported

[Django]

#19775: database configuration without "default" not supported
---+-
 Reporter:  monkut |Owner:  wsmith323
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 Keywords:  multipledbs| Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by wsmith323):

 At Jacob's urging, I improved the documentation patch to include a
 settings.py example.

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

[django/django] b6f4a9: Proposed fix for #18162.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b6f4a92ff45d98a63dc29402d8ad86b88e6a6697
  
https://github.com/django/django/commit/b6f4a92ff45d98a63dc29402d8ad86b88e6a6697
  Author: Tomek Paczkowski 
  Date:   2013-02-23 (Sat, 23 Feb 2013)

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

  Log Message:
  ---
  Proposed fix for #18162.


  Commit: 10026c2ad0da99591567ba13afe4b489e050ca4a
  
https://github.com/django/django/commit/10026c2ad0da99591567ba13afe4b489e050ca4a
  Author: Honza Král 
  Date:   2013-02-23 (Sat, 23 Feb 2013)

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

  Log Message:
  ---
  Merge pull request #804 from oinopion/ticket18162

Fixes #18162 --  Specifying choices to Field overrides any form_class argument


Compare: https://github.com/django/django/compare/24a2bcbcdd9e...10026c2ad0da

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

Re: [Django] #18162: Specifying choices to Field overrides any form_class argument

[Django]

#18162: Specifying choices to Field overrides any form_class argument
-+
 Reporter:  rafallo  |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:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by Honza Král ):

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


Comment:

 In [changeset:"10026c2ad0da99591567ba13afe4b489e050ca4a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="10026c2ad0da99591567ba13afe4b489e050ca4a"
 Merge pull request #804 from oinopion/ticket18162

 Fixes #18162 --  Specifying choices to Field overrides any form_class
 argument
 }}}

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

Re: [Django] #19402: django.contrib.auth.models.CustomUser.REQUIRED_FIELDS needs better docs

[Django]

#19402: django.contrib.auth.models.CustomUser.REQUIRED_FIELDS needs better docs
--+
 Reporter:  pydanny   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  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:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"1702be89c86d1b1a01efb16fa7836335ad709184"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1702be89c86d1b1a01efb16fa7836335ad709184"
 [1.5.X] Fixed #19402 - Clarified purpose of CustomUser.REQUIRED_FIELDS

 Thanks pydanny for the report and ptone for the patch.

 Backport of 24a2bcbcdd 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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 1702be: [1.5.X] Fixed #19402 - Clarified purpose of Custom...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 1702be89c86d1b1a01efb16fa7836335ad709184
  
https://github.com/django/django/commit/1702be89c86d1b1a01efb16fa7836335ad709184
  Author: Tim Graham 
  Date:   2013-02-23 (Sat, 23 Feb 2013)

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

  Log Message:
  ---
  [1.5.X] Fixed #19402 - Clarified purpose of CustomUser.REQUIRED_FIELDS

Thanks pydanny for the report and ptone for the patch.

Backport of 24a2bcbcdd 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19898: Document why/when of class-based views

[Django]

#19898: Document why/when of class-based views
---+--
 Reporter:  estebistec |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  docs   | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by estebistec):

 From the intro text on the topic index page, there will likely be two new
 pages:

 * usage-patterns
 * testing

 /plan

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