Re: [Django] #3208: allow to generate a 'no-content' HTTP response (a response with no body)

[Django]

#3208: allow to generate a 'no-content' HTTP response (a response with no body)
-+-
 Reporter:  mihai.preda@…|Owner:  nobody
 Type:  enhancement  |   Status:  new
Component:  Core (Other) |  Version:  master
 Severity:  normal   |   Resolution:
 Keywords:  HttpResponse | Triage Stage:  Design
Has patch:  0|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by yurii.zolotko@…):

 * status:  closed => new
 * ui_ux:   => 0
 * resolution:  duplicate =>
 * easy:   => 0


Comment:

 #3362 doesn't solve the problem as it can't be done with existing
 HttpResponse class.
 There is still no way to send a response without Content-Type header with
 Django except this:
 {{{
 response = HttpResponse(open(unknown_type_file).read())
 del response['Content-Type']
 }}}
 which is very ugly.
 According to [http://www.w3.org/Protocols/rfc2616/rfc2616-sec7.html]
 Content-Type header is not mandatory and can be omitted to make client
 guess file type, but it can't be done with Django as setting content_type
 to None sets it to DEFAULT_CONTENT_TYPE and not really None.

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

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

Re: [Django] #7609: Document that PositiveIntegerField and co have a misleading name

[Django]

#7609: Document that PositiveIntegerField and co have a misleading name
-+-
 Reporter:  Gergely Kontra   |Owner:
  |  paulcollins
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  name convention, | Triage Stage:  Ready for
  rename |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by anonymous):

 +1 for UnsignedIntegerField

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #19774: contentypes generic module has core functionality plus admins-specific one

[Django]

#19774: contentypes generic module has core functionality plus admins-specific 
one
-+-
 Reporter:  ramiro   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:   |   Resolution:
  contrib.contenttypes   | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  dependency generic   |  Patch needs improvement:  0
  contenttypes   |UI/UX:  0
Has patch:  0|
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by wim@…):

 * keywords:   => dependency generic contenttypes
 * type:  Bug => Cleanup/optimization
 * 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.

[Django] #19781: Documentation on Django Comments moderation emails doesn't match actual behavior

[Django]

#19781: Documentation on Django Comments moderation emails doesn't match actual
behavior
--+
 Reporter:  mikeshultz|  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  contrib.comments  |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 django.contrib.comments.moderation(ln:239) currently uses
 settings.MANAGERS to decide who the recipients of the moderation e-mails
 are.  This isn't mentioned in the documentation.

 However, I'd like to request this to change to sending to all users with
 the {{{ Can moderate comments }}} permission.  If this would be to
 resource intensive(querying users every comment post), then I'd like to
 suggest adding {{{ settings.MODERATORS }}} that would trump {{{
 settings.MANAGERS }}} if it exists.

 I don't have a good idea for the former, but the latter, a simple change
 to something like this would help:

 {{{
 recipient_list = [manager_tuple[1] for manager_tuple in getattr(settings,
 'MODERATORS', None) or settings.MANAGERS]
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #11603: Add an assertFormSetError function to django.test.TestCase

[Django]

#11603: Add an assertFormSetError function to django.test.TestCase
-+-
 Reporter:  martin_speleo|Owner:
 Type:  New feature  |  martin_speleo
Component:  Testing framework|   Status:  new
 Severity:  Normal   |  Version:  master
 Keywords:  formset  |   Resolution:
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by timo):

 I've used this in a project with good success.  I've updated the patch to
 apply cleanly to trunk and submitted a pull request.

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

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #12728: loadata/flush issues given GenericRelation, model inheritance and postgres

[Django]

#12728: loadata/flush issues given GenericRelation, model inheritance and 
postgres
-+-
 Reporter:  pragmar  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  master
  contrib.contenttypes   |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
  psycopg2.ProgrammingError, |  Needs documentation:  0
  GenericRelation|  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

 * stage:  Accepted => Ready for checkin


Comment:

 Patch applies cleanly and tests with postgresql_psycopg2 backend pass.

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

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

Re: [Django] #8162: Changes to Permissions model

[Django]

#8162: Changes to Permissions model
--+-
 Reporter:  juliae|Owner:  wilsoniya
 Type:  Bug   |   Status:  assigned
Component:  contrib.auth  |  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 shai):

 * cc: shai@… (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] #8162: Changes to Permissions model

[Django]

#8162: Changes to Permissions model
--+-
 Reporter:  juliae|Owner:  wilsoniya
 Type:  Bug   |   Status:  assigned
Component:  contrib.auth  |  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
--+-

Comment (by shai):

 Hi wilsoniya,

 You just closed #17763 as a dupe of this one, ignoring comments 4 & 5 on
 that ticket which propose a very viable and simple solution. 5 is my own,
 I'm quoting it here:

 >
 > My own suggestion of a fix: Change
 `django.contrib.auth.management._get_all_permissions` to read:
 > {{{
 > def _get_all_permissions(opts):
 > "Returns (codename, name) for all permissions in the given opts."
 > perms = []
 > for action in ('add', 'change', 'delete'):
 > perm_name = u'Can %s %s' % (action, opts.verbose_name_raw)
 > if len(perm_name)>50:
 > perm_name= perm_name[:40] + u'...' + perm_name[-7:]
 > perms.append((_get_permission_codename(action, opts),
 perm_name))
 > return perms + list(opts.permissions)
 > }}}
 >
 > Because the name is just used for UI anyway. Of course, you can play
 with the "40" and "7" there -- that's what I thought was reasonable. And
 perhaps the two-line snippet for "make display string fit in length"
 should be factored out and used elsewhere.
 >
 > If a core developer finds the approach acceptable, but would rather have
 this as a patch, just say so.
 >

 This is fully backwards-compatible in any self-respecting backend (any
 permission whose name is affected by this could not have been saved in the
 db).

 It may generate a different perm_name for existing perms on sqlite and
 some mysql configurations (it wouldn't change anything in existing
 databases, but the same application in a new deployment will have
 different perm_names). There too -- this is a UI string; for complete
 Sqlite/!MySql backwards-compatibility, use `perm_name[:50]` instead of
 `perm_name[:40] + u'...' + perm_name[-7:]`. If this route is taken, I
 would prefer to limit this to only these backends, sacrificing a little
 cross-database compatibility for the sake of more sensible UI elsewhere.

 I must say, I find it odd that this suggestion has been so completely
 ignored, not even rebuked.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] f44922: Fixed #18906 -- Ignored to-be-deleted forms in for...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: f44922c79516b9caf0e09fb060f20c896668b90f
  
https://github.com/django/django/commit/f44922c79516b9caf0e09fb060f20c896668b90f
  Author: Claude Paroz 
  Date:   2013-02-08 (Fri, 08 Feb 2013)

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

  Log Message:
  ---
  Fixed #18906 -- Ignored to-be-deleted forms in formset validate_unique

Thanks c.pollock at bangor.ac.uk for the report.



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

Re: [Django] #18906: BaseModelFormSet.validate_unique should ignore forms marked for deletion

[Django]

#18906: BaseModelFormSet.validate_unique should ignore forms marked for deletion
-+
 Reporter:  c.pollock@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.4
 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 Claude Paroz ):

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


Comment:

 In [changeset:"f44922c79516b9caf0e09fb060f20c896668b90f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f44922c79516b9caf0e09fb060f20c896668b90f"
 Fixed #18906 -- Ignored to-be-deleted forms in formset validate_unique

 Thanks c.pollock at bangor.ac.uk for the report.
 }}}

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

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

[django/django] 15796d: [1.5.x] Cleaned up some lingering signals in the t...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 15796db507f5ce64f6935a0b634b4d1000c28401
  
https://github.com/django/django/commit/15796db507f5ce64f6935a0b634b4d1000c28401
  Author: Julien Phalip 
  Date:   2013-02-08 (Fri, 08 Feb 2013)

  Changed paths:
M tests/modeltests/update_only_fields/tests.py
M tests/regressiontests/comment_tests/tests/moderation_view_tests.py
M tests/regressiontests/multiple_database/tests.py

  Log Message:
  ---
  [1.5.x] Cleaned up some lingering signals in the test suite that were causing 
spurious failures with Pypy and Postgres.
Backport of db09a2de6e1bc7121



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] db09a2: Cleaned up some lingering signals in the test suit...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: db09a2de6e1bc7121d301dad9610efcda9c7a925
  
https://github.com/django/django/commit/db09a2de6e1bc7121d301dad9610efcda9c7a925
  Author: Julien Phalip 
  Date:   2013-02-08 (Fri, 08 Feb 2013)

  Changed paths:
M tests/modeltests/update_only_fields/tests.py
M tests/regressiontests/comment_tests/tests/moderation_view_tests.py
M tests/regressiontests/multiple_database/tests.py

  Log Message:
  ---
  Cleaned up some lingering signals in the test suite that were causing 
spurious failures with Pypy and Postgres.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #13742: implement savepoints for sqlite3

[Django]

#13742: implement savepoints for sqlite3
-+-
 Reporter:  rctay|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  sqlite3 savepoints   |  Needs documentation:  0
  nested transactions|  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-

Comment (by claudep):

 #15506 was a duplicate with a 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.

Re: [Django] #15506: Savepoint support for sqlite3 backend

[Django]

#15506: Savepoint support for sqlite3 backend
-+-
 Reporter:  lamby|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  1.2
  (models, ORM)  |   Resolution:  duplicate
 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):

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


Comment:

 This was already reported in #13742.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #13533: queries test fails under MySQL InnoDB

[Django]

#13533: queries test fails under MySQL InnoDB
-+-
 Reporter:  russellm |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.2-beta
  (models, ORM)  |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  innodb mysql |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

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


Comment:

 I think this has been fixed along #16809.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #8162: Changes to Permissions model

[Django]

#8162: Changes to Permissions model
--+-
 Reporter:  juliae|Owner:  wilsoniya
 Type:  Bug   |   Status:  assigned
Component:  contrib.auth  |  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 wilsoniya):

 * owner:  nobody => wilsoniya
 * status:  new => assigned
 * has_patch:  1 => 0


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

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

Re: [Django] #17763: Problem with auth_permission name length

[Django]

#17763: Problem with auth_permission name length
--+-
 Reporter:  stenius@… |Owner:  anonymous
 Type:  Bug   |   Status:  closed
Component:  contrib.auth  |  Version:  1.0
 Severity:  Normal|   Resolution:  duplicate
 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 wilsoniya):

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


Comment:

 Closed as duplicate of #8162

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #5908: Cycle tag should reset after it steps out of scope(?)

[Django]

#5908: Cycle tag should reset after it steps out of scope(?)
-+-
 Reporter:  Simon Litchfield |Owner:  nobody
    |   Status:  new
 Type:   |  Version:  master
  Cleanup/optimization   |   Resolution:
Component:  Template system  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  cycle templatetag|  Patch needs improvement:  1
  tag counter for loop reset |UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by isaacsutherland@…):

 * cc: isaacsutherland@… (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] #16521: Provide keyboard shortcuts in admin

[Django]

#16521: Provide keyboard shortcuts in admin
---+-
 Reporter:  coolRR |Owner:  anonymous
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  1.3
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  1
---+-
Changes (by vgdlima@…):

 * owner:  nobody => anonymous
 * 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] #13528: db_table truncation is applied based on the properties of the default database

[Django]

#13528: db_table truncation is applied based on the properties of the default
database
-+-
 Reporter:  russellm |Owner:
 Type:  Bug  |  andrewgodwin
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:  1.2-beta
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

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


Comment:

 Using router might be a solution, however I don't know if this does
 negatively affect performance or not.

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

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

[django/django] 868e0f: Removed unneeded imports in db.models init

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 868e0f3cb4cc47418e43a08c373f0707e3cf301c
  
https://github.com/django/django/commit/868e0f3cb4cc47418e43a08c373f0707e3cf301c
  Author: Claude Paroz 
  Date:   2013-02-08 (Fri, 08 Feb 2013)

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

  Log Message:
  ---
  Removed unneeded imports in db.models init



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #9025: Nested Inline Support in Admin

[Django]

#9025: Nested Inline Support in Admin
---+
 Reporter:  pixelcort  |Owner:
 Type:  New feature|   Status:  new
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:  1
---+
Changes (by ZmjbS):

 * cc: ZmjbS (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] #19779: Regression in redirects middleware

[Django]

#19779: Regression in redirects middleware
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.redirects|  Version:  1.5-rc-1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"b8c6de31a6f08321a6cf6e3ede2dab90c9f1febd"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b8c6de31a6f08321a6cf6e3ede2dab90c9f1febd"
 [1.5.x] Fixed #19779 -- Checked contrib.sites presence in
 RedirectFallbackMiddleware

 Thanks Aymeric Augustin for the report and directions for the patch.
 Backport of 2ed90eac 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] b8c6de: [1.5.x] Fixed #19779 -- Checked contrib.sites pres...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: b8c6de31a6f08321a6cf6e3ede2dab90c9f1febd
  
https://github.com/django/django/commit/b8c6de31a6f08321a6cf6e3ede2dab90c9f1febd
  Author: Claude Paroz 
  Date:   2013-02-08 (Fri, 08 Feb 2013)

  Changed paths:
M django/contrib/redirects/middleware.py
M django/contrib/redirects/tests.py
M docs/ref/contrib/redirects.txt
M docs/ref/contrib/sites.txt
M docs/releases/1.5.txt

  Log Message:
  ---
  [1.5.x] Fixed #19779 -- Checked contrib.sites presence in 
RedirectFallbackMiddleware

Thanks Aymeric Augustin for the report and directions for the patch.
Backport of 2ed90eac 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] #19779: Regression in redirects middleware

[Django]

#19779: Regression in redirects middleware
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.redirects|  Version:  1.5-rc-1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"2ed90eac49b99d66ee4f2d59af8553274a4d095f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2ed90eac49b99d66ee4f2d59af8553274a4d095f"
 Fixed #19779 -- Checked contrib.sites presence in
 RedirectFallbackMiddleware

 Thanks Aymeric Augustin for the report and directions 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] 2ed90e: Fixed #19779 -- Checked contrib.sites presence in ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2ed90eac49b99d66ee4f2d59af8553274a4d095f
  
https://github.com/django/django/commit/2ed90eac49b99d66ee4f2d59af8553274a4d095f
  Author: Claude Paroz 
  Date:   2013-02-08 (Fri, 08 Feb 2013)

  Changed paths:
M django/contrib/redirects/middleware.py
M django/contrib/redirects/tests.py
M docs/ref/contrib/redirects.txt
M docs/ref/contrib/sites.txt
M docs/releases/1.5.txt

  Log Message:
  ---
  Fixed #19779 -- Checked contrib.sites presence in RedirectFallbackMiddleware

Thanks Aymeric Augustin for the report and directions 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] #19779: Regression in redirects middleware

[Django]

#19779: Regression in redirects middleware
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.redirects|  Version:  1.5-rc-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

 * stage:  Accepted => Ready for checkin


Comment:

 Is `_ =` necessary in `_ = RedirectFallbackMiddleware()`? Otherwise this
 looks perfect, thanks!

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

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

Re: [Django] #19779: Regression in redirects middleware

[Django]

#19779: Regression in redirects middleware
---+
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.redirects  |  Version:  1.5-rc-1
 Severity:  Release blocker|   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 claudep):

 * has_patch:  0 => 1
 * 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] #19749: Documentation needed: stdout.write line endings in management commands changed.

[Django]

#19749: Documentation needed: stdout.write line endings in management commands
changed.
-+-
 Reporter:  xian@…   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Core (Management |  1.5-beta-1
  commands)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by apollo13):

 Looks good to me, ship it :)

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

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

Re: [Django] #19779: Regression in redirects middleware

[Django]

#19779: Regression in redirects middleware
---+--
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.redirects  |  Version:  1.5-rc-1
 Severity:  Release blocker|   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 aaugustin):

 After discussing the issue on IRC, I suggest to check in
 `RedirectFallbackMiddleware.__init__` that `django.contrib.sites` is in
 `INSTALLED_APPS` — this allows us to keep the current implementation, a
 step towards #15089, and to show a clear error message at compile time
 rather than the error I posted above at run time.

 It's still backwards-incompatible for people who enabled d.c.redirects but
 not d.c.sites. So it should be documented in the release notes as a
 backwards incompatible change:
 > Because of an implementation oversight, it was possible to use
 django.contrib.redirects without enabling django.contrib.sites. This isn't
 allowed any longer. If you're using d.c.redirects, make sure
 INSTALLED_APPS contains django.contrib.sites.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #19779: Regression in redirects middleware

[Django]

#19779: Regression in redirects middleware
---+--
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.redirects  |  Version:  1.5-rc-1
 Severity:  Release blocker|   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 aaugustin):

 Unlike the flatpages docs, the redirects docs don't say anything about
 contrib.sites.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #19780: Discrepancy in modwsgi auth handler

[Django]

#19780: Discrepancy in modwsgi auth handler
+
   Reporter:  aaugustin |  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  contrib.auth  |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 `check_password` does:
 {{{
 if not user.is_active:
 return None
 }}}
 while `groups_for_user` does:
 {{{
 try:
 if not user.is_active:
 return []
 except AttributeError as e:
 # a custom user may not support is_active
 return []
 }}}

 Shouldn't these be rewritten to:
 {{{
 if not getattr(user, 'is_active', True):
 return None / return []
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #19779: Regression in redirects middleware

[Django]

#19779: Regression in redirects middleware
---+--
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.redirects  |  Version:  1.5-rc-1
 Severity:  Release blocker|   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 aaugustin):

 Currently Django doesn't forbid importing models from apps that aren't in
 INSTALLED_APPS.

 Agreed, that's dubious, and we should probably fix it in app-loading.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #19779: Regression in redirects middleware

[Django]

#19779: Regression in redirects middleware
---+--
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.redirects  |  Version:  1.5-rc-1
 Severity:  Release blocker|   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 claudep):

 The flatpages contrib docs explicitely require that contrib.sites should
 be installed, so I think we are safe on this side.

 Looking at the redirect model, I see:
 {{{
 ...
 from django.contrib.sites.models import Site
 ...

 class Redirect(models.Model):
 site = models.ForeignKey(Site)
 ...
 }}}

 How could that work without the sites framework being installed?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #19779: Regression in redirects middleware

[Django]

#19779: Regression in redirects middleware
---+--
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.redirects  |  Version:  1.5-rc-1
 Severity:  Release blocker|   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 aaugustin):

 I searched for '.id' and '.pk' in the commit that introduced the
 regression.

 I think the flatpages middleware is also affected, but nothing else.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #19779: Regression in redirects middleware

[Django]

#19779: Regression in redirects middleware
---+--
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.redirects  |  Version:  1.5-rc-1
 Severity:  Release blocker|   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 aaugustin):

 The traceback is a bit different after
 833ccd4b5b4b294e7ca8d32faa4461be7fafb13c but the underlying problem is the
 same:
 {{{
 Environment:


 Request Method: GET
 Request URL: http://localhost:8000/s/css/base.css/

 Django Version: 1.5c1
 Python Version: 2.7.2
 Installed Applications:
 ['docs', 'haystack']
 Installed Middleware:
 ['djangosecure.middleware.SecurityMiddleware',
  'django.middleware.clickjacking.XFrameOptionsMiddleware',
  'django.contrib.sessions.middleware.SessionMiddleware',
  'django.contrib.messages.middleware.MessageMiddleware',
  'django.middleware.csrf.CsrfViewMiddleware',
  'django.contrib.auth.middleware.AuthenticationMiddleware',
  'django.middleware.common.CommonMiddleware',
  'django.contrib.flatpages.middleware.FlatpageFallbackMiddleware',
  'django.contrib.redirects.middleware.RedirectFallbackMiddleware']


 Traceback:
 File "/Users/myk/Documents/dev/django/django/core/handlers/base.py" in
 get_response
   187. response = middleware_method(request, response)
 File
 "/Users/myk/Documents/dev/django/django/contrib/redirects/middleware.py"
 in process_response
   18. r = Redirect.objects.get(site=current_site,
 old_path=full_path)
 File "/Users/myk/Documents/dev/django/django/db/models/manager.py" in get
   143. return self.get_query_set().get(*args, **kwargs)
 File "/Users/myk/Documents/dev/django/django/db/models/query.py" in get
   379. clone = self.filter(*args, **kwargs)
 File "/Users/myk/Documents/dev/django/django/db/models/query.py" in filter
   655. return self._filter_or_exclude(False, *args, **kwargs)
 File "/Users/myk/Documents/dev/django/django/db/models/query.py" in
 _filter_or_exclude
   673. clone.query.add_q(Q(*args, **kwargs))
 File "/Users/myk/Documents/dev/django/django/db/models/sql/query.py" in
 add_q
   1259. can_reuse=used_aliases,
 force_having=force_having)
 File "/Users/myk/Documents/dev/django/django/db/models/sql/query.py" in
 add_filter
   1190. connector)
 File "/Users/myk/Documents/dev/django/django/db/models/sql/where.py" in
 add
   71. value = obj.prepare(lookup_type, value)
 File "/Users/myk/Documents/dev/django/django/db/models/sql/where.py" in
 prepare
   339. return self.field.get_prep_lookup(lookup_type, value)
 File "/Users/myk/Documents/dev/django/django/db/models/fields/related.py"
 in get_prep_lookup
   143. return self._pk_trace(value, 'get_prep_lookup',
 lookup_type)
 File "/Users/myk/Documents/dev/django/django/db/models/fields/related.py"
 in _pk_trace
   216. v = getattr(field, prep_func)(lookup_type, v, **kwargs)
 File "/Users/myk/Documents/dev/django/django/db/models/fields/__init__.py"
 in get_prep_lookup
   321. return self.get_prep_value(value)
 File "/Users/myk/Documents/dev/django/django/db/models/fields/__init__.py"
 in get_prep_value
   554. return int(value)

 Exception Type: TypeError at /s/css/base.css/
 Exception Value: int() argument must be a string or a number, not
 'RequestSite'
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #19779: Regression in redirects middleware

[Django]

#19779: Regression in redirects middleware
-+--
   Reporter:  aaugustin  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  contrib.redirects  |Version:  1.5-rc-1
   Severity:  Release blocker|   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+--
 After upgrading docs.djangoproject.com to 1.5 rc 1 static files fail to
 load.

 {{{
 Environment:


 Request Method: GET
 Request URL: http://localhost:8000/s/css/base.css/

 Django Version: 1.5c1
 Python Version: 2.7.2
 Installed Applications:
 ['docs', 'haystack']
 Installed Middleware:
 ['djangosecure.middleware.SecurityMiddleware',
  'django.middleware.clickjacking.XFrameOptionsMiddleware',
  'django.contrib.sessions.middleware.SessionMiddleware',
  'django.contrib.messages.middleware.MessageMiddleware',
  'django.middleware.csrf.CsrfViewMiddleware',
  'django.contrib.auth.middleware.AuthenticationMiddleware',
  'django.middleware.common.CommonMiddleware',
  'django.contrib.flatpages.middleware.FlatpageFallbackMiddleware',
  'django.contrib.redirects.middleware.RedirectFallbackMiddleware']


 Traceback:
 File "/Users/myk/.virtualenvs/dp.com/lib/python2.7/site-
 packages/django/core/handlers/base.py" in get_response
   187. response = middleware_method(request, response)
 File "/Users/myk/.virtualenvs/dp.com/lib/python2.7/site-
 packages/django/contrib/redirects/middleware.py" in process_response
   13. r =
 Redirect.objects.get(site__id__exact=current_site.id, old_path=path)

 Exception Type: AttributeError at /s/css/base.css/
 Exception Value: 'RequestSite' object has no attribute 'id'
 }}}

 This regression was introduced in
 6c2faaceb0482267cec19da0ff432984028f9d0c.

 I'm not sure it's a good idea to use `get_current_site()`, which can
 return a `RequestSite`, in code that obviously needs a `Site`.

 Possible solutions:
 - rollback the change in the redirect middleware
 - give `RequestSite` `pk` and `id` attributes returning `settings.SITE_ID`

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords:  multipledbs| Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by claudep):

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


Old description:

> For version 1.4 and dev documentation on multiple databases the text
> seems to imply that you can choose not to define a "default" db
>
> https://docs.djangoproject.com/en/1.4/topics/db/multi-db/#defining-your-
> databases
>
> """
> ... Django uses the database with the alias of default when no other
> database has been selected. If you don’t have a default database, you
> need to be careful to always specify the database that you want to use.
>
> """
>
> However, when you actually remove, or do not include a "default" and
> attempt to syncdb with Postgresql, you get the following error that
> explicitly tells you, that you *must* define a "default" database:
>
> >python manage.py syncdb
> Traceback (most recent call last):
>   File "manage.py", line 16, in 
> execute_manager(settings)
>   File "C:\Python27\lib\site-
> packages\django\core\management\__init__.py", line 459, in
> execute_manager
> utility.execute()
>   File "C:\Python27\lib\site-
> packages\django\core\management\__init__.py", line 382, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "C:\Python27\lib\site-
> packages\django\core\management\__init__.py", line 261, in fetch_command
> klass = load_command_class(app_name, subcommand)
>   File "C:\Python27\lib\site-
> packages\django\core\management\__init__.py", line 69, in
> load_command_class
> module = import_module('%s.management.commands.%s' % (app_name,
> name))
>   File "C:\Python27\lib\site-packages\django\utils\importlib.py", line
> 35, in import_module
> __import__(name)
>   File "C:\Python27\lib\site-
> packages\django\core\management\commands\syncdb.py", line 8, in 
> from django.core.management.sql import custom_sql_for_model,
> emit_post_sync_signal
>   File "C:\Python27\lib\site-packages\django\core\management\sql.py",
> line 6, in 
> from django.db import models
>   File "C:\Python27\lib\site-packages\django\db\__init__.py", line 12, in
> 
> raise ImproperlyConfigured("You must define a '%s' database" %
> DEFAULT_DB_ALIAS)
> django.core.exceptions.ImproperlyConfigured: You must define a 'default'
> database

New description:

 For version 1.4 and dev documentation on multiple databases the text seems
 to imply that you can choose not to define a "default" db

 https://docs.djangoproject.com/en/1.4/topics/db/multi-db/#defining-your-
 databases

 ''
 ... Django uses the database with the alias of default when no other
 database has been selected. If you don’t have a default database, you need
 to be careful to always specify the database that you want to use.
 ''

 However, when you actually remove, or do not include a "default" and
 attempt to syncdb with Postgresql, you get the following error that
 explicitly tells you, that you *must* define a "default" database:

 {{{
 >python manage.py syncdb
 Traceback (most recent call last):
   File "manage.py", line 16, in 
 execute_manager(settings)
   File "C:\Python27\lib\site-packages\django\core\management\__init__.py",
 line 459, in execute_manager
 utility.execute()
   File "C:\Python27\lib\site-packages\django\core\management\__init__.py",
 line 382, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "C:\Python27\lib\site-packages\django\core\management\__init__.py",
 line 261, in fetch_command
 klass = load_command_class(app_name, subcommand)
   File "C:\Python27\lib\site-packages\django\core\management\__init__.py",
 line 69, in load_command_class
 module = import_module('%s.management.commands.%s' % (app_name, name))
   File "C:\Python27\lib\site-packages\django\utils\importlib.py", line 35,
 in import_module
 __import__(name)
   File "C:\Python27\lib\site-
 packages\django\core\management\commands\syncdb.py", line 8, in 
 from django.core.management.sql import custom_sql_for_model,
 emit_post_sync_signal
   File "C:\Python27\lib\site-packages\django\core\management\sql.py", line
 6, in 
 from django.db import models
   File "C:\Python27\lib\site-packages\django\db\__init__.py", line 12, in
 
 raise ImproperlyConfigured("You must define a '%s' database" 

[django/django] e48647: Moved import in db.backends.creation

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e486475a13ba626f67008ade3544c74003f0a881
  
https://github.com/django/django/commit/e486475a13ba626f67008ade3544c74003f0a881
  Author: Claude Paroz 
  Date:   2013-02-08 (Fri, 08 Feb 2013)

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

  Log Message:
  ---
  Moved import in db.backends.creation



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #19753: Custom user system shouldn't be dependent on all installed apps

[Django]

#19753: Custom user system shouldn't be dependent on all installed apps
---+--
 Reporter:  abraham@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  contrib.auth   |  Version:  1.5-beta-1
 Severity:  Normal |   Resolution:  needsinfo
 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 daniel):

 Creating circular references is all too easy. If you want to avoid a lot
 of pain going forward, you're going to want to take a serious look at this
 issue.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #19333: Collect static copies a .py file

[Django]

#19333: Collect static copies a .py file
-+-
 Reporter:  camilonova   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.4
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Julien Phalip ):

 In [changeset:"be5369fd24adfc788e59eaf0363d4d137ded6ef8"]:
 {{{
 #!CommitTicketReference repository=""
 revision="be5369fd24adfc788e59eaf0363d4d137ded6ef8"
 [1.5.x] Fixed #19333 -- Moved compress.py outside of the admin static
 folder. Thanks to camilonova, Russell Keith-Magee, Aymeric Augustin and
 Ramiro Morales for the feedback.
 Backport of c9c40bc6bc64e6
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #19776: test fails in git stable/1.5.x branch

[Django]

#19776: test fails in git stable/1.5.x branch
---+
 Reporter:  robvdl |  Owner:  nobody
 Type:  Uncategorized  | Status:  closed
Component:  Testing framework  |Version:  1.5-beta-1
 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:"830b9fde460cedeb9a9a52e11a2d456d08c5198f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="830b9fde460cedeb9a9a52e11a2d456d08c5198f"
 [1.5.x] Fixed #19776 -- Added missing import for backport

 line was present on master from 1520748dac95a7f114e4bb2f04d46c720494
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] 830b9f: [1.5.x] Fixed #19776 -- Added missing import for b...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 830b9fde460cedeb9a9a52e11a2d456d08c5198f
  
https://github.com/django/django/commit/830b9fde460cedeb9a9a52e11a2d456d08c5198f
  Author: Preston Holmes 
  Date:   2013-02-08 (Fri, 08 Feb 2013)

  Changed paths:
M django/contrib/auth/tests/auth_backends.py

  Log Message:
  ---
  [1.5.x] Fixed #19776 -- Added missing import for backport

line was present on master from 1520748dac95a7f114e4bb2f04d46c720494



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #16218: Class-based month archive doesn't behave like previous generic view

[Django]

#16218: Class-based month archive doesn't behave like previous generic view
---+-
 Reporter:  nnrcschmdt |Owner:  aaugustin
 Type:  Bug|   Status:  closed
Component:  Generic views  |  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
---+-

Comment (by Aymeric Augustin ):

 In [changeset:"11f6295551fbcedae50df0efcae5eb34555a46dd"]:
 {{{
 #!CommitTicketReference repository=""
 revision="11f6295551fbcedae50df0efcae5eb34555a46dd"
 [1.5.x] Documented ArchiveIndexView's date_list context variable.

 Refs #16218.

 Backport of a0c67c6.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #19706: Tutorial amendments

[Django]

#19706: Tutorial amendments
-+-
 Reporter:  EvilDMP  |Owner:  timo
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.5-beta-1
 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
-+-

Comment (by Tim Graham ):

 In [changeset:"ad2311dfc68fb10710093c5b8c827249852402dd"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ad2311dfc68fb10710093c5b8c827249852402dd"
 [1.5.x] Fixed #19706 - Tweaks to the tutorial.

 Thanks Daniele Procida.

 Backport of aa85ccf8ce 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.

Re: [Django] #19772: Redirects don't honor APPEND_SLASH

[Django]

#19772: Redirects don't honor APPEND_SLASH
---+
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.redirects  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Aymeric Augustin ):

 In [changeset:"833ccd4b5b4b294e7ca8d32faa4461be7fafb13c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="833ccd4b5b4b294e7ca8d32faa4461be7fafb13c"
 [1.5.x] Fixed #19772 -- Handled APPEND_SLASH correctly in the redirects
 app.

 Backport of 64623a2.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #19662: Explain correct `authenticate` usage with custom user model.

[Django]

#19662: Explain correct `authenticate` usage with custom user model.
-+--
 Reporter:  tomchristie  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  1.5-beta-1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by Preston Holmes ):

 In [changeset:"660f80c3d60083ecba26c83c0670ccca7fc56e09"]:
 {{{
 #!CommitTicketReference repository=""
 revision="660f80c3d60083ecba26c83c0670ccca7fc56e09"
 [1.5.x] Fixed #19662 -- alter auth modelbackend to accept custom username
 fields

 Thanks to Aymeric and Carl for the review.
 }}}

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

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

Re: [Django] #19756: .add or .create on ManyToManyField doc page

[Django]

#19756: .add or .create on ManyToManyField doc page
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  closed
Component:  Documentation  |Version:  1.4
 Severity:  Normal | Resolution:  fixed
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  1
UI/UX:  0  |
---+

Comment (by Tim Graham ):

 In [changeset:"a81363d85accfe09fe6885b255355dfb108e25af"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a81363d85accfe09fe6885b255355dfb108e25af"
 [1.5.x] Fixed #19756 - Corrected a ManyToMany example and added some links
 and markup.

 Backport of 43efefae69 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.

Re: [Django] #19743: Document limitations of django.contrib.auth

[Django]

#19743: Document limitations of django.contrib.auth
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   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 Tim Graham ):

 In [changeset:"3b952123ac29f66371f5c51a00026faf7cb945c1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3b952123ac29f66371f5c51a00026faf7cb945c1"
 [1.5.x] Fixed #19743 - Documented some limitations of contrib.auth.

 Thanks Aymeric for the suggestion.

 Backport of afa3e16334 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.

Re: [Django] #19725: `createsuperuser` command fails with custom User model

[Django]

#19725: `createsuperuser` command fails with custom User model
-+--
 Reporter:  michisu  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  1.5-beta-1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+--

Comment (by Claude Paroz ):

 In [changeset:"f5232597ea31bf274b02983f32ba89be4f7bf02b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f5232597ea31bf274b02983f32ba89be4f7bf02b"
 [1.5.x] Fixed #19725 -- Made createsuperuser handle non-ascii prompts

 Thanks Michisu for the report.
 Backport of 55c585f1c 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.

Re: [Django] #19734: missing values in DATETIME_INPUT_FORMATS docs

[Django]

#19734: missing values in DATETIME_INPUT_FORMATS docs
-+-
 Reporter:  minddust |Owner:  charettes
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by Simon Charette ):

 In [changeset:"f58aae9311ade7a59ca97ec1e5dee7c08ab86f28"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f58aae9311ade7a59ca97ec1e5dee7c08ab86f28"
 [1.5.x] Fixed #19734 -- Missing values in `DATETIME_INPUT_FORMATS` doc.

 Also changed formating of `DATE_INPUT_FORMATS` and
 `TIME_INPUT_FORMATS` for readability.

 Thanks minddust for the report!

 Backport of 5c70299a71 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.

Re: [Django] #19237: The use of > in single or double quoted attributes in strip_tags

[Django]

#19237: The use of > in single or double quoted attributes in strip_tags
--+---
 Reporter:  chris.khoo@…  |Owner:  khoomeister
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  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 Claude Paroz ):

 In [changeset:"20ac33100cd20c17d1ceab075d96698974cc4778"]:
 {{{
 #!CommitTicketReference repository=""
 revision="20ac33100cd20c17d1ceab075d96698974cc4778"
 Partially revert 9efe1a721, strip_tags improvements

 The new regex seems not stable enough for being released. Stripping
 with regex might need reevaluation for the next release.
 Refs #19237.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #19745: Wrong prompt for `createuser` management command ()

[Django]

#19745: Wrong prompt for `createuser` management command
()
-+-
 Reporter:  bmispelon|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:
 Severity:  Release blocker  |  1.5-beta-1
 Keywords:  createuser repr py3  |   Resolution:  fixed
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  1|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"933e956ba4b1ad5f8823f0a294ffc795e949edf1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="933e956ba4b1ad5f8823f0a294ffc795e949edf1"
 [1.5.x] Fixed #19745 -- Forced resolution of verbose names in
 createsupersuser

 Thanks Baptiste Mispelon for the report and Preston Holmes for the review.
 Backport of 2390fe3f4 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.

Re: [Django] #19700: BoundField documentation: original field

[Django]

#19700: BoundField documentation: original field
---+--
 Reporter:  tga|Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by Tim Graham ):

 In [changeset:"f28fbe7314712d3e594a0f6509361378162cc7ea"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f28fbe7314712d3e594a0f6509361378162cc7ea"
 [1.5.x] Fixed #19700 - Added documentation for BoundField.field.

 Thanks Tiberiu Ana for the report and patch.

 Backport of fdaaa24171 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.

Re: [Django] #19445: Fieldsets' validation doesn't call get_form

[Django]

#19445: Fieldsets' validation doesn't call get_form
---+
 Reporter:  KJ |Owner:  slurms
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by Julien Phalip ):

 In [changeset:"e18bd68dbc64dfe08ae0fbb54591d5c8f7e456eb"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e18bd68dbc64dfe08ae0fbb54591d5c8f7e456eb"
 [1.5.x] Fixed #19445 -- Skip admin fieldsets validation when the
 ModelAdmin.get_form() method is overridden.
 Backport of 0694d2196f0fad
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #18144: MD5PasswordHasher: broken backwards compatibility with empty salt

[Django]

#18144: MD5PasswordHasher: broken backwards compatibility with empty salt
-+-
 Reporter:  apreobrazhensky@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  1.4
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  MD5PasswordHasher| Triage Stage:  Accepted
  check_password salt|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Claude Paroz ):

 In [changeset:"c39be8b836282c1060e64dc17c6cb8184c14cf0b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c39be8b836282c1060e64dc17c6cb8184c14cf0b"
 [1.5.x] Fixed #18144 -- Added backwards compatibility with old unsalted
 MD5 passwords

 Thanks apreobrazhensky at gmail.com for the report.
 Backport of 63d6a50dd 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.

Re: [Django] #19708: django.utils.timezone.override helper may raise AttributeError

[Django]

#19708: django.utils.timezone.override helper may raise AttributeError
+-
 Reporter:  rafales |Owner:  aaugustin
 Type:  Bug |   Status:  closed
Component:  Uncategorized   |  Version:  1.4
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  timezone utils  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+-

Comment (by Aymeric Augustin ):

 In [changeset:"db49b6d2b298bc53b55df9ee7cf80e6492d3116b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="db49b6d2b298bc53b55df9ee7cf80e6492d3116b"
 [1.5.x] Fixed #19708 -- Exception in timezone.override(None).

 Thanks rafales.

 Backport of 9a4a1ce.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #17228: params context variable from TemplateView is inconsistent with other get_context_data implementations

[Django]

#17228: params context variable from TemplateView is inconsistent with other
get_context_data implementations
--+
 Reporter:  ptone |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Generic views |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Claude Paroz ):

 In [changeset:"5ebd0452ba6ff93980e6f9a8958f6ea01c835ffe"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5ebd0452ba6ff93980e6f9a8958f6ea01c835ffe"
 [1.5.x] Fixed #19714 -- Updated documentation about TemplateView context

 Thanks Aramgutang for the report. Refs #17228.
 Backport of 56e553129 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.

Re: [Django] #19714: Documentation for TemplateView incorrectly refers to "params" context variable.

[Django]

#19714: Documentation for TemplateView incorrectly refers to "params" context
variable.
-+-
 Reporter:  Aramgutang   |Owner:  claudep
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:
 Severity:  Release blocker  |  1.5-beta-1
 Keywords:  TemplateView params  |   Resolution:  fixed
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"5ebd0452ba6ff93980e6f9a8958f6ea01c835ffe"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5ebd0452ba6ff93980e6f9a8958f6ea01c835ffe"
 [1.5.x] Fixed #19714 -- Updated documentation about TemplateView context

 Thanks Aramgutang for the report. Refs #17228.
 Backport of 56e553129 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.

Re: [Django] #19690: Class in ajax example doesn't inherit from imported SingleObjectTemplateResponseMixin

[Django]

#19690: Class in ajax example doesn't inherit from imported
SingleObjectTemplateResponseMixin
-+-
 Reporter:  lucianu  |Owner:  lucianu
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  0|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"a22480797d8b4992f92854624dbf4ac328cbf765"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a22480797d8b4992f92854624dbf4ac328cbf765"
 [1.5.x] Fixed #19690 - Removed unused import in doc examples.

 Backport of c6560e4843 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.

Re: [Django] #19692: Replace HttpResponse.mimetype (deprecated) with content_type in doc examples

[Django]

#19692: Replace HttpResponse.mimetype (deprecated) with content_type in doc
examples
-+-
 Reporter:  timo |Owner:  aaugustin
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"11ec0253ab4cc926ab9e77619132cb398231ac33"]:
 {{{
 #!CommitTicketReference repository=""
 revision="11ec0253ab4cc926ab9e77619132cb398231ac33"
 [1.5.x] Fixed #19692 -- Completed deprecation of mimetype in favor of
 content_type.

 Thanks Tim for the report and initial patch.

 Backport of 89cb771 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.

Re: [Django] #19577: admin doc may encourage bad practices

[Django]

#19577: admin doc may encourage bad practices
-+-
 Reporter:  foo@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.4
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"42fcfcaa529dac1fe3066797d7e4ab7aa6f6cdf3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="42fcfcaa529dac1fe3066797d7e4ab7aa6f6cdf3"
 [1.5.x] Fixed #19577 - Added HTML escaping to admin examples.

 Thanks foo@ for the report and Florian Apolloner for the review.

 Backport of eafc036476 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.

Re: [Django] #19683: A minor mistake?

[Django]

#19683: A minor mistake?
---+
 Reporter:  sunsongxp@…|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 Keywords:  signing| Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Tim Graham ):

 In [changeset:"f6075b0596e20951bd8232f09d97fb7fac08308c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f6075b0596e20951bd8232f09d97fb7fac08308c"
 [1.5.x] Fixed #19683 - Added a missing import in signing example.

 Thanks sunsongxp@ for the report.

 Backport of 537d44b1b9 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.

Re: [Django] #19076: TemplateView does not support setting mime type, like views.generic.simple.direct_to_template did

[Django]

#19076: TemplateView does not support setting mime type, like
views.generic.simple.direct_to_template did
---+
 Reporter:  gwahl@…|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Generic views  |  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
---+

Comment (by Aymeric Augustin ):

 In [changeset:"d5ad9d3dfe729f8b605965e131c787fae9f84377"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d5ad9d3dfe729f8b605965e131c787fae9f84377"
 [1.5.x] Fixed #19076 -- Added content_type attribute to TemplateView.

 Thanks Gavin Wahl.

 Backport of 23e319d.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #19665: 'Command' object has no attribute 'stderr'

[Django]

#19665: 'Command' object has no attribute 'stderr'
-+-
 Reporter:  stefankoegl  |Owner:  claudep
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |   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 Claude Paroz ):

 In [changeset:"2d8b0315f46d24c6567a05422bd609f3a689bda8"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2d8b0315f46d24c6567a05422bd609f3a689bda8"
 [1.5.x] Fixed #19665 -- Ensured proper stderr output for
 Command.run_from_argv

 Thanks Stefan Koegl for the report and Simon Charette for the review.
 Backport of b9c8bbf37 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.

Re: [Django] #19652: Fix for #19524 introduced a backward compatiblity issue with related managers on 1.5.X

[Django]

#19652: Fix for #19524 introduced a backward compatiblity issue with related
managers on 1.5.X
-+-
 Reporter:  charettes|Owner:  charettes
 Type:  Bug  |   Status:  closed
Component:  ORM aggregation  |  Version:
 Severity:  Release blocker  |  1.5-beta-1
 Keywords:  none EmptyQuerySet   |   Resolution:  fixed
  none   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

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

 In [changeset:"f4132140f52c88b67d11743d4062a9d455959ffc"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f4132140f52c88b67d11743d4062a9d455959ffc"
 [1.5.x] Fixed #19652 -- Fixed .none() regression in related fields

 The regression was caused by using .none() when querying for related
 models, and the origin field's value was None. This resulted in missing
 custom related manager subclass as .none() returns plain QuerySet.

 This isn't backport from master, in master .none() correctly preserves
 the queryset's class.

 Patch provided by Simon Charette, with some minor polish by committer.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #19024: FormWizard WizardView.get_form_prefix form argument is unused

[Django]

#19024: FormWizard WizardView.get_form_prefix form argument is unused
-+-
 Reporter:  kenth|Owner:  steph
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  contrib.formtools|   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
-+-

Comment (by Claude Paroz ):

 In [changeset:"f16eb0b0d049595f837005986b1db539528fef2f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f16eb0b0d049595f837005986b1db539528fef2f"
 [1.5.x] Fixed #19024 -- Corrected form wizard docs for get_form_prefix.

 Backport of 17f8496fe 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.

Re: [Django] #19610: Include enctype in example forms

[Django]

#19610: Include enctype in example forms
-+-
 Reporter:  will@…   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   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
-+-

Comment (by Tim Graham ):

 In [changeset:"2e6b0c5ca7265b3cee2ff68a9ef5d1865afb9a49"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2e6b0c5ca7265b3cee2ff68a9ef5d1865afb9a49"
 [1.5.x] Fixed #19610 - Added enctype note to forms topics doc.

 Thanks will@ for the suggestion.

 Backport of 0de2645c00 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.

Re: [Django] #19639: Choices in model fields best practices consistency

[Django]

#19639: Choices in model fields best practices consistency
---+
 Reporter:  charettes  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by Tim Graham ):

 In [changeset:"d571894fc09b34b8b43cb8f1790c743a47679851"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d571894fc09b34b8b43cb8f1790c743a47679851"
 [1.5.x] Fixed #19639 - Updated contributing to reflect model choices best
 practices.

 Thanks charettes.

 Backport of eaa716a413 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.

Re: [Django] #19652: Fix for #19524 introduced a backward compatiblity issue with related managers on 1.5.X

[Django]

#19652: Fix for #19524 introduced a backward compatiblity issue with related
managers on 1.5.X
-+-
 Reporter:  charettes|Owner:  charettes
 Type:  Bug  |   Status:  closed
Component:  ORM aggregation  |  Version:
 Severity:  Release blocker  |  1.5-beta-1
 Keywords:  none EmptyQuerySet   |   Resolution:  fixed
  none   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"9328ef0e84db2559af56d24c40e6b24b74e29a6f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9328ef0e84db2559af56d24c40e6b24b74e29a6f"
 [1.5.x] Avoided a possible regression in 5097d3c5.

 QuerySet.none() returns an instance of EmptyQuerySet, which may have
 undesirable side effects in the presence of custom query set classes.

 The implementation of .none() was refactored in master to have the same
 effect as .filter(pk__in=[]).

 Refs #19652.

 Thanks Simon Charrette for the report.
 }}}

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

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

Re: [Django] #19477: Docs needed for generic_inlineformset_factory

[Django]

#19477: Docs needed for generic_inlineformset_factory
---+
 Reporter:  epicserve  |Owner:  nobody
 Type:  Bug|   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
---+

Comment (by Tim Graham ):

 In [changeset:"dc0bf53276f28421006d041dc21c7dc8d0393b2d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="dc0bf53276f28421006d041dc21c7dc8d0393b2d"
 [1.5.x] Fixed #19477 - Documented generic_inlineformset_factory

 Thanks epicserve for the suggestion.

 Backport of 214fb700b9 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.

Re: [Django] #19606: Oracle unicode insert fails.

[Django]

#19606: Oracle unicode insert fails.
-+-
 Reporter:  jtiai|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  oracle orm unicode   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

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

 In [changeset:"457290326fa38297467922d827c630ae2026e88b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="457290326fa38297467922d827c630ae2026e88b"
 [1.5.x] Fixed #19606 -- Adjusted cx_Oracle unicode detection.

 Backpatch of d194f290571f7e9dda7d2fd7a6f2b171120f2f14
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #19633: Docs should discourage using gunicorn's Django integration

[Django]

#19633: Docs should discourage using gunicorn's Django integration
---+
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   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
---+

Comment (by Tim Graham ):

 In [changeset:"54887d686b1552ae98e3eb4fa57a64036eea72a5"]:
 {{{
 #!CommitTicketReference repository=""
 revision="54887d686b1552ae98e3eb4fa57a64036eea72a5"
 [1.5.x] Fixed #19633 - Discouraged use of gunicorn's Django integration.

 Backport of 0db86273ae 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.

Re: [Django] #19596: Django admin should use "_default_manager" not "objects" on csutom auth model class.

[Django]

#19596: Django admin should use "_default_manager" not "objects" on csutom auth
model class.
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:
 Severity:  Release blocker  |  1.5-beta-1
 Keywords:  auth, objects|   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
-+-

Comment (by Florian Apolloner ):

 In [changeset:"5f3c45f7458825b5ca88fb60e5349762fb74d5ae"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5f3c45f7458825b5ca88fb60e5349762fb74d5ae"
 [1.5.X] Fixed #19596 -- Use `_default_manager` instead of `objects` in the
 auth app.

 This is needed to support custom user models which don't define a manager
 named `objects`.

 Backport of cc4de61a2b36abf418d6f4c720d9e62c405e0612 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.

Re: [Django] #19632: Sample code is wrong in page: "Using the Django authentication system"

[Django]

#19632: Sample code is wrong in page: "Using the Django authentication system"
-+-
 Reporter:  grossmanandy@…   |Owner:  charettes
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"d90abcc9dad9b239e77aa67bfdd0c431072e2434"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d90abcc9dad9b239e77aa67bfdd0c431072e2434"
 [1.5.x] Fixed #19632 -- Bug in code sample.

 Thanks grossmanandy at bfusa com and Simon Charette.

 Backport of 1dd7492.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #19640: inlineformset_factory is not documented well like other formset_factories

[Django]

#19640: inlineformset_factory is not documented well like other 
formset_factories
-+-
 Reporter:  wim@…|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
  inlineformset_factory  |  Patch needs improvement:  0
  documentation  |UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  1|
-+-

Comment (by Tim Graham ):

 In [changeset:"34718395edec9aaf01443b7c9d89ebe14400721e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="34718395edec9aaf01443b7c9d89ebe14400721e"
 [1.5.x] Fixed #19640 - Added inlineformset_factory to reference docs.

 Thanks wim@ for the suggestion.

 Backport of 5b2d9bacd2 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.

Re: [Django] #19628: Add to the documentation note about AUTH_USER_MODEL

[Django]

#19628: Add to the documentation note about AUTH_USER_MODEL
---+--
 Reporter:  dpravdin   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.5-beta-1
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by Tim Graham ):

 In [changeset:"f6257a147df0be2f21c390ad10f6cd724b99cd93"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f6257a147df0be2f21c390ad10f6cd724b99cd93"
 [1.5.x] Fixed #19628 - Noted that app for custom user model must be in
 INSTALLED_APPS

 Thanks dpravdin and Jordan Messina.

 Backport of 0375244eae 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.

Re: [Django] #19024: FormWizard WizardView.get_form_prefix form argument is unused

[Django]

#19024: FormWizard WizardView.get_form_prefix form argument is unused
-+-
 Reporter:  kenth|Owner:  steph
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  contrib.formtools|   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
-+-

Comment (by Tim Graham ):

 In [changeset:"b7828705c8a87a079b6226caf959c821bd51fa91"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b7828705c8a87a079b6226caf959c821bd51fa91"
 [1.5.x] Clarified WizardView.get_form_prefix doc, refs #19024

 Backport of c9b577ead6 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.

Re: [Django] #19614: Error in docs example

[Django]

#19614: Error in docs example
---+--
 Reporter:  Dima Pravdin   |Owner:  aaugustin
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.5-beta-1
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Aymeric Augustin ):

 In [changeset:"6428f1cb72b912a94217fb22eb187f5b80f7088f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6428f1cb72b912a94217fb22eb187f5b80f7088f"
 [1.5.x] Fixed #19614 -- Missing request argument in render call.

 Thanks Dima Pravdin for the report.

 Backport of 74d72e2.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #19597: jquery.js recommendations; minified jQuery not documented

[Django]

#19597: jquery.js recommendations; minified jQuery not documented
--+
 Reporter:  EvilDMP   |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
--+

Comment (by Tim Graham ):

 In [changeset:"40d8b6e28c06a04631014d1eaee63c0ef957937f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="40d8b6e28c06a04631014d1eaee63c0ef957937f"
 [1.5.x] Fixed #19597 - Added some notes on jQuery in admin.

 Thanks Daniele Procida.

 Backport of d406afe12e 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.

Re: [Django] #19605: Unnecessary import in code examples from the docs

[Django]

#19605: Unnecessary import in code examples from the docs
-+-
 Reporter:  sergzach |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.5-beta-1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"360676d9d86ed36a2ffcf1318904b2b56cfae641"]:
 {{{
 #!CommitTicketReference repository=""
 revision="360676d9d86ed36a2ffcf1318904b2b56cfae641"
 [1.5.x] Fixed #19605 - Removed unused url imports from doc examples.

 Thanks sergzach for the suggestion.

 Backport of 43f89e0ad6 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.

Re: [Django] #19092: formats.py for Lithuanian language

[Django]

#19092: formats.py for Lithuanian language
--+
 Reporter:  skirsdeda |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Translations  |  Version:  1.4
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Claude Paroz ):

 In [changeset:"5a53f1043cc86feef82864e4f5a57de78d57664b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5a53f1043cc86feef82864e4f5a57de78d57664b"
 [1.5.x] Fixed #19092 -- Completed Lithuanian date/time formats

 Thanks Tadas Dailyda for the report and the patch.
 Backport of 2f8ab2f1b0 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.

Re: [Django] #18026: can't update extra_data in process_step of form wizard

[Django]

#18026: can't update extra_data in process_step of form wizard
-+-
 Reporter:  creecode |Owner:  steph
 Type:  Bug  |   Status:  closed
Component:  contrib.formtools|  Version:  1.4
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  form wizard  | Triage Stage:  Accepted
  extra_data process_step can't  |  Needs documentation:  0
  update |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by Claude Paroz ):

 In [changeset:"fb130cb40ea9b93bae741a4f359f19819597a112"]:
 {{{
 #!CommitTicketReference repository=""
 revision="fb130cb40ea9b93bae741a4f359f19819597a112"
 [1.5.x] Fixed #18026 -- Don't return an anonymous dict if extra_data in
 storage is empty.

 Backport of 97121cb9 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.

Re: [Django] #19488: Locale middleware with settings.APPEND_SLASH enabled is buggy (doesn't redirect) with valid URLs not ending with slash

[Django]

#19488: Locale middleware with settings.APPEND_SLASH enabled is buggy (doesn't
redirect) with valid URLs not ending with slash
-+-
 Reporter:  danger@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Other) |  Version:  1.4
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  redirect, i18n,  | Triage Stage:  Accepted
  locale middleware  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Claude Paroz ):

 In [changeset:"b3887ab98ac5317ebe7889e8b35752ebfd9740f9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b3887ab98ac5317ebe7889e8b35752ebfd9740f9"
 [1.5.x] Fixed #19488 -- Made i18n_patterns redirect work with non-slash-
 ending paths

 Thanks Daniel Gerzo for the report and the initial patch.
 Backport of bcdb4898c 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.

Re: [Django] #19546: Add logging configuration to test_sqlite.py

[Django]

#19546: Add logging configuration to test_sqlite.py
-+-
 Reporter:  bak1an   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Testing framework|   Resolution:  fixed
 Severity:  Release blocker  | 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 Preston Holmes ):

 In [changeset:"af8e858c1596623ffcccedc57433a009455bc314"]:
 {{{
 #!CommitTicketReference repository=""
 revision="af8e858c1596623ffcccedc57433a009455bc314"
 [1.5.x] Fixed #19546 - ensure that deprecation warnings are shown during
 tests

 refs #18985
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #19585: Unable to load cookie values as a dict

[Django]

#19585: Unable to load cookie values as a dict
-+-
 Reporter:  claudep  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  regression   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"1d03ff06bbcc726c815f26f79067692019b2c71a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1d03ff06bbcc726c815f26f79067692019b2c71a"
 [1.5.x] Fixed #19585 -- Fixed loading cookie value as a dict

 This regression was introduced by the 'unicode_literals' patch.
 Backport of f08e739bc2 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.

Re: [Django] #19437: improved documentation for django installation

[Django]

#19437: improved documentation for django installation
--+
 Reporter:  dodger|Owner:  dodger
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.4
 Severity:  Normal|   Resolution:  fixed
 Keywords:  documentation | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"b86c3ddce88390dacc04094fbdce1b722fb8127b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b86c3ddce88390dacc04094fbdce1b722fb8127b"
 [1.5.x] Fixed #19437 - Clarified pip install instructions in contributing
 tutorial.

 Backport of 9f9a7f03d7 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.

Re: [Django] #19588: UserManager documentation is missing create_superuser

[Django]

#19588: UserManager documentation is missing create_superuser
--+
 Reporter:  minddust  |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:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"72ef63bf86b12e752f186d562d9094cfde30af27"]:
 {{{
 #!CommitTicketReference repository=""
 revision="72ef63bf86b12e752f186d562d9094cfde30af27"
 [1.5.x] Fixed #19588 - Added create_superuser to UserManager docs.

 Thanks minddust for the report.

 Backport of 4da5947a87 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.

Re: [Django] #10239: Document modelform_factory

[Django]

#10239: Document modelform_factory
-+-
 Reporter:  ingenieroariel   |Owner:  timo
 Type:  New feature  |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  dceu2011 | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"c94fcc4117987c4ebe29ad63da01035230c8afd5"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c94fcc4117987c4ebe29ad63da01035230c8afd5"
 [1.5.x] Fixed #10239 - Added docs for modelform_factory

 Thanks ingenieroariel for the suggestion and slurms for the review.

 Backport of 71d76ec011 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.

Re: [Django] #19546: Add logging configuration to test_sqlite.py

[Django]

#19546: Add logging configuration to test_sqlite.py
-+-
 Reporter:  bak1an   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Testing framework|   Resolution:  fixed
 Severity:  Release blocker  | 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 Florian Apolloner ):

 In [changeset:"1d3368b587c786128d1cf0b6f172f35e03269ecc"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1d3368b587c786128d1cf0b6f172f35e03269ecc"
 [1.5.X] Fixed lockups in jenkins, refs #19546.

 Backport of ce580dd8ea04237cfe34cd02df0b8944a5345f4f 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.

Re: [Django] #19586: URL_VALIDATOR_USER_AGENT is said to be deprecated, but has actually been removed

[Django]

#19586: URL_VALIDATOR_USER_AGENT is said to be deprecated, but has actually been
removed
---+--
 Reporter:  m@…|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by Tim Graham ):

 In [changeset:"7f7b6a369b5d8749bf7ef3324803b8041ff59b56"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7f7b6a369b5d8749bf7ef3324803b8041ff59b56"
 [1.5.x] Fixed #19586 - Removed URL_VALIDATOR_USER_AGENT from setting docs.

 It was removed in Django 1.5, not deprecated.

 Backport of 066cf2d70e 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.

Re: [Django] #19546: Add logging configuration to test_sqlite.py

[Django]

#19546: Add logging configuration to test_sqlite.py
-+-
 Reporter:  bak1an   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Testing framework|   Resolution:  fixed
 Severity:  Release blocker  | 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 Claude Paroz ):

 In [changeset:"785ec24720b3d7b38cf683f298b730c0c4014ac9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="785ec24720b3d7b38cf683f298b730c0c4014ac9"
 [1.5.x] Skipped deprecation warning test on Python 2.6

 Refs #19546. On Python 2.6, DeprecationWarnings are visible by
 default.
 Backport of e6949373b 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.

Re: [Django] #19573: It is not possible to overwrite field label in AuthenticationForm

[Django]

#19573: It is not possible to overwrite field label in AuthenticationForm
-+-
 Reporter:  jan.munclinger@… |Owner:  slurms
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  contrib.auth |  1.5-beta-1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"b4544dbd5bf7fec73d03f31c0e59135d64fd818c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b4544dbd5bf7fec73d03f31c0e59135d64fd818c"
 [1.5.x] Fixed #19573 -- Allow override of username field label in
 AuthenticationForm

 Backport of cdad0b28d 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.

Re: [Django] #18985: DeprecationWarning no longer loud by default in Python 2.7+

[Django]

#18985: DeprecationWarning no longer loud by default in Python 2.7+
--+
 Reporter:  dstufft   |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Core (Other)  |  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
--+

Comment (by Preston Holmes ):

 In [changeset:"af8e858c1596623ffcccedc57433a009455bc314"]:
 {{{
 #!CommitTicketReference repository=""
 revision="af8e858c1596623ffcccedc57433a009455bc314"
 [1.5.x] Fixed #19546 - ensure that deprecation warnings are shown during
 tests

 refs #18985
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #19555: tutorial pt 1 - update year for examples to work

[Django]

#19555: tutorial pt 1 - update year for examples to work
--+
 Reporter:  rodrigorosa.lg@…  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  year  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"c95ae7729f713a300e67bf30e9506ba78919113a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c95ae7729f713a300e67bf30e9506ba78919113a"
 [1.5.x] Fixed #19555 - Removed '2012' from tutorial 1.

 Thanks rodrigorosa.lg and others for the report.

 Backport of 99315f709e 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.

Re: [Django] #19571: Django 1.5 Tutorial Need to update Version on First page

[Django]

#19571: Django 1.5 Tutorial Need to update Version on First page
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.5-beta-1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"7c39e041b1e107f437f61e97a11ce9e011d9ad2b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7c39e041b1e107f437f61e97a11ce9e011d9ad2b"
 [1.5.x] Added sphinx substitutions in place of hardcoded version numbers.

 Refs #19571

 Backport of 1884868adc 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.

Re: [Django] #19441: No Postgres _like index when unique=True

[Django]

#19441: No Postgres _like index when unique=True
-+-
 Reporter:  dyve |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  postgresql   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"012229914cb1391ee4fcb6c183a341a6491cd377"]:
 {{{
 #!CommitTicketReference repository=""
 revision="012229914cb1391ee4fcb6c183a341a6491cd377"
 [1.5.x] Created special PostgreSQL text indexes when unique is True

 Refs #19441.
 Backport of c698c55966 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.

Re: [Django] #17541: Unexpected ForeignKey Behavior with self.pk == None

[Django]

#17541: Unexpected ForeignKey Behavior with self.pk == None
-+-
 Reporter:  sheats   |Owner:  anonymous
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

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

 In [changeset:"9d6d0de7c1704fa39efb1f725bd8f80961ce3496"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9d6d0de7c1704fa39efb1f725bd8f80961ce3496"
 [1.5.x] Fixed #17541 -- Fixed non-saved/nullable fk querying

 Backpatch of 55da775ce1bfba20db33b56c29957faa63917980
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #19576: Use `six.with_metaclass` uniformously accross code base

[Django]

#19576: Use `six.with_metaclass` uniformously accross code base
-+-
 Reporter:  charettes|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Python 3 |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  six  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"78739faedb01baee06e84c69f6fab84c9e8b718e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="78739faedb01baee06e84c69f6fab84c9e8b718e"
 [1.5.x] Fixed #19576 -- Use `six.with_metaclass` uniformously accross code
 base.

 Backport of f58efd07f 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.

Re: [Django] #19562: Documentation: How Django stores passwords out of date

[Django]

#19562: Documentation: How Django stores passwords out of date
--+
 Reporter:  startup.canada@…  |Owner:  ptone
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Preston Holmes ):

 In [changeset:"f02e1167d788280e33de3df68fa41e89cb083619"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f02e1167d788280e33de3df68fa41e89cb083619"
 [1.5.x] Fixed #19562 -- cleaned up password storage docs

 Conflicts:

 docs/topics/auth/passwords.txt
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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.