Re: [Django] #19057: mod_wsgi authentication handlers fail with custom user model

2012-10-06 Thread Django 
#19057: mod_wsgi authentication handlers fail with custom user model
-+-
 Reporter:  russellm |Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  contrib.auth |  Version:  master
 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 ptone):

 * stage:  Accepted => Ready for checkin


Comment:

 updated and hopefully final patch:

 https://github.com/ptone/django/compare/modwsgi-customuser

 pending final resolution on #19061

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

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

Re: [Django] #19061: Clarify the contract regarding is_active on custom users

2012-10-06 Thread Django 
#19061: Clarify the contract regarding is_active on custom users
--+
 Reporter:  russellm  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 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 ptone):

 * cc: preston@… (added)
 * has_patch:  0 => 1


Comment:

 Not sure what I had going on, but my test project where I had tried the
 property approach - later showed that going with a property is not going
 to work, there is a setattr in Model.__init__ for is_active fields - and
 that can't replace the property.

 In the current patch - I take the approach of forcing the attribute to be
 read-only unless it is explicitly implemented in a subclass, to avoid any
 chance of something assuming it is a saveable attribute.

 In the tests I try to handle what I assume would be some (odd) edge cases
 where people may want to use is_active as a non-field.  Something I think
 would be a peculiar thing to do, but since it could be accommodated
 without too gross of a __setattr__ approach.

 If we wanted to remove the __setattr__ guard - the default attr would
 still be provided, but any attempt to set the attr would result in an
 ephemeral instance attribute, and could cause confusion, hence the
 decision to put in the guard.

 https://github.com/ptone/django/compare/is-active-required

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

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

[django/django] 35e8dc: Removed ad-hoc support for usage of short names of...

2012-10-06 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 35e8dc5169013437d71ae60e05c7f3356d86236e
  
https://github.com/django/django/commit/35e8dc5169013437d71ae60e05c7f3356d86236e
  Author: Ramiro Morales 
  Date:   2012-10-06 (Sat, 06 Oct 2012)

  Changed paths:
M django/db/utils.py
M tests/regressiontests/backends/tests.py

  Log Message:
  ---
  Removed ad-hoc support for usage of short names of built-in DB backends.

This non-standard naming was deprecated in Django 1.2.



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

Re: [Django] #19078: Polish IBAN field

2012-10-06 Thread Django 
#19078: Polish IBAN field
-+--
 Reporter:  bartosak@…   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  polish IBAN  | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by bartosak):

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


Comment:

 That was my proposal based on
 https://docs.djangoproject.com/en/dev/ref/contrib/localflavor/ page

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

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

[Django] #19078: Polish IBAN field

2012-10-06 Thread Django 
#19078: Polish IBAN field
-+-
 Reporter:  bartosak@…   |  Owner:  nobody
 Type:  New feature  | Status:  new
Component:  Forms|Version:  1.4
 Severity:  Normal   |   Keywords:  polish IBAN
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 I would like to add polish IBAN account number field

 {{{
 from django.core.validators import EMPTY_VALUES
 from django.forms import ValidationError, RegexField
 from django.utils.translation import ugettext_lazy as _

 class PLIBANField(RegexField):
 """
 Polish International Bank Account Number (IBAN) field

 For Polish IBAN validation algorithm see
 http://pl.wikipedia.org/wiki/International_Bank_Account_Number
 """
 default_error_messages = {
 'invalid': _('Enter a valid IBAN in PLXX------
  format'),
 }

 def __init__(self, max_length=40, min_length=28, *args, **kwargs):
 super(PLIBANField, self).__init__(r'^[0-9A-Za-z\-\s]{28,40}$',
 max_length, min_length, *args, **kwargs)

 def clean(self, value):
 """
 Strips - and spaces, performs country code and checksum validation
 """
 value = super(PLIBANField, self).clean(value)
 if value in EMPTY_VALUES:
 return u''
 value = value.replace('-','')
 value = value.replace(' ','')
 value = value.upper()
 if value[0:2] != 'PL':
 raise ValidationError(self.error_messages[_('Unknown country
 code')])
 numeric_format = ''
 for char in value[4:] + value[0:4]:
 if char.isalpha():
 numeric_format += str(ord(char) - 55)
 else:
 numeric_format += char
 if int(numeric_format) % 97 != 1:
 raise ValidationError(self.error_messages[_('Invalid
 checksum')])
 return value
 }}}

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

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

Re: [Django] #18827: Exclude __pycache__ from module detection

2012-10-06 Thread Django 
#18827: Exclude __pycache__ from module detection
---+
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Python 3   |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by ramiro):

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


Comment:

 Fixed in 2100da9dcdba7a8bc18f6180fd7e61640319b48a.

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

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

[django/django] ab2329: Updated .gitignore with files created when running...

2012-10-06 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ab232937355e8f7ed959ebafd16f8ac7b2a2f85d
  
https://github.com/django/django/commit/ab232937355e8f7ed959ebafd16f8ac7b2a2f85d
  Author: Ramiro Morales 
  Date:   2012-10-06 (Sat, 06 Oct 2012)

  Changed paths:
M .gitignore

  Log Message:
  ---
  Updated .gitignore with files created when running setup.py sdist.



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

[django/django] 2100da: Ensure we ignore __pycache__ PEP 3174 dirs in a fe...

2012-10-06 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2100da9dcdba7a8bc18f6180fd7e61640319b48a
  
https://github.com/django/django/commit/2100da9dcdba7a8bc18f6180fd7e61640319b48a
  Author: Ramiro Morales 
  Date:   2012-10-06 (Sat, 06 Oct 2012)

  Changed paths:
M MANIFEST.in
M django/core/management/templates.py
M django/db/utils.py
M django/template/defaultfilters.py
M setup.py

  Log Message:
  ---
  Ensure we ignore __pycache__ PEP 3174 dirs in a few more places.



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

[django/django] 69035b: More URL mapping documentation fixes.

2012-10-06 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 69035b0b1c6e3bd4569070bf0f0c774def397f0d
  
https://github.com/django/django/commit/69035b0b1c6e3bd4569070bf0f0c774def397f0d
  Author: Ramiro Morales 
  Date:   2012-10-06 (Sat, 06 Oct 2012)

  Changed paths:
M docs/ref/urls.txt
M docs/topics/http/urls.txt

  Log Message:
  ---
  More URL mapping documentation fixes.



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

Re: [Django] #7281: Add doctype tag to webdesign template tags

2012-10-06 Thread Django 
#7281: Add doctype tag to webdesign template tags
-+-
 Reporter:  Rob Hudson   |Owner:  nobody
     |   Status:  new
 Type:  New feature  |  Version:  master
Component:  contrib.webdesign|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  webdesign|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by d1ffuz0r):

 * cc: d1fffuz0r@… (added)


Comment:

 Improvements in attached file.

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

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

[django/django] 91ef2a: Use native geometry types on PostGIS 2.0+ instead ...

2012-10-06 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 91ef2a5253a50a602523bdda943c32c4cfe719fe
  
https://github.com/django/django/commit/91ef2a5253a50a602523bdda943c32c4cfe719fe
  Author: Justin Bronn 
  Date:   2012-10-06 (Sat, 06 Oct 2012)

  Changed paths:
M django/contrib/gis/db/backends/base.py
M django/contrib/gis/db/backends/postgis/creation.py
M django/contrib/gis/db/backends/postgis/operations.py
M django/contrib/gis/db/models/fields.py

  Log Message:
  ---
  Use native geometry types on PostGIS 2.0+ instead of `AddGeometryColumn` and 
don't query database in `PostGISCreation.sql_table_creation_suffix`.



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

[django/django] b6b8a3: Refactored URL mapping documentation.

2012-10-06 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b6b8a3f66b5cf4f00bd7ce668ac04f21bb73e0b9
  
https://github.com/django/django/commit/b6b8a3f66b5cf4f00bd7ce668ac04f21bb73e0b9
  Author: Ramiro Morales 
  Date:   2012-10-06 (Sat, 06 Oct 2012)

  Changed paths:
M docs/ref/index.txt
A docs/ref/urlresolvers.txt
A docs/ref/urls.txt
M docs/topics/http/urls.txt

  Log Message:
  ---
  Refactored URL mapping documentation.

Reorganized topic document so it introduces concepts form simple to more
complex. Moved reference parts to their own documents.



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

Re: [Django] #15529: GeoJSON regexes doesn't accept some characters within a quoted string

2012-10-06 Thread Django 
#15529: GeoJSON regexes doesn't accept some characters within a quoted string
-+-
 Reporter:  woutkh   |Owner:  jbronn
 Type:  Bug  |   Status:  assigned
Component:  GIS  |  Version:  1.2
 Severity:  Normal   |   Resolution:
 Keywords:  gis geojson gdal | Triage Stage:  Accepted
  json_regex |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

 * needs_tests:  1 => 0


Comment:

 Just uploaded a patch with a test, if we want to keep going the regex
 route.

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

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

Re: [Django] #15586: Fields with missing columns populated when querying on PostgreSQL

2012-10-06 Thread Django 
#15586: Fields with missing columns populated when querying on PostgreSQL
---+
 Reporter:  sebzur |Owner:  nobody
 Type:  Bug|   Status:  reopened
Component:  Documentation  |  Version:  1.2
 Severity:  Normal |   Resolution:
 Keywords:  postgresql | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by lrekucki):

 Note that "name" is just an example here. From my understanding, you can
 swap it to any other datatype that PostgreSQL supports and instead of
 raising an error about a missing column, it will treat it as a cast of the
 whole row to that datatype.

 Anyways, I tried this on PostgreSQL 9.2 and the behavior is no longer
 there. I'm guessing it was removed in version 9, but don't have an
 instance to verify.

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

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

[django/django] 8a2216: Un-gzipped test geometries fixture as plain json

2012-10-06 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8a2216648fcc1c6e504902e612b046c213de46d7
  
https://github.com/django/django/commit/8a2216648fcc1c6e504902e612b046c213de46d7
  Author: Claude Paroz 
  Date:   2012-10-06 (Sat, 06 Oct 2012)

  Changed paths:
M django/contrib/gis/geometry/test_data.py
A django/contrib/gis/tests/data/geometries.json
R django/contrib/gis/tests/data/geometries.json.gz

  Log Message:
  ---
  Un-gzipped test geometries fixture as plain json

This is easier to track changes through the VCS.



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

Re: [Django] #17066: Exception TypeError when using GeoIP

2012-10-06 Thread Django 
#17066: Exception TypeError when using GeoIP
+-
 Reporter:  mitar   |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  GIS |  Version:  1.4
 Severity:  Normal  |   Resolution:  needsinfo
 Keywords:  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+-
Changes (by claudep):

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


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

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

Re: [Django] #15586: Fields with missing columns populated when querying on PostgreSQL

2012-10-06 Thread Django 
#15586: Fields with missing columns populated when querying on PostgreSQL
---+
 Reporter:  sebzur |Owner:  nobody
 Type:  Bug|   Status:  reopened
Component:  Documentation  |  Version:  1.2
 Severity:  Normal |   Resolution:
 Keywords:  postgresql | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by timo):

 The usefulness of adding something like the following seems very limited
 to me:

 "If you are using PostgreSQL and add a field called 'name' to an existing
 model but forget to add the column in your database, SELECT statements
 will appear to work even though the column doesn't exist (since NAME is a
 Postgres function and SELECT foo.name FROM foo is equivalent to SELECT
 name(foo) FROM foo) ."

 but since the ticket has been accepted, is that the essence of what is
 being suggested?

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

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

Re: [Django] #19038: Add Experimental Support for Python 3.3

2012-10-06 Thread Django 
#19038: Add Experimental Support for Python 3.3
-+
 Reporter:  clelland |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Python 3 |  Version:  master
 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
-+

Comment (by Claude Paroz ):

 In [changeset:"117e99511e0985701780ed1bcd3afd456e244ae3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="117e99511e0985701780ed1bcd3afd456e244ae3"
 Added assertXML[Not]Equal assertions

 This is especially needed to compare XML when hash randomization
 is on, as attribute order may vary. Refs #17758, #19038.
 Thanks Taylor Mitchell for the initial patch, and Ian Clelland for
 review and cleanup.
 }}}

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

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

Re: [Django] #17758: Do not depend on dict order in test suite

2012-10-06 Thread Django 
#17758: Do not depend on dict order in test suite
-+
 Reporter:  lrekucki |Owner:  Alex
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  1.3
 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
-+

Comment (by Claude Paroz ):

 In [changeset:"117e99511e0985701780ed1bcd3afd456e244ae3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="117e99511e0985701780ed1bcd3afd456e244ae3"
 Added assertXML[Not]Equal assertions

 This is especially needed to compare XML when hash randomization
 is on, as attribute order may vary. Refs #17758, #19038.
 Thanks Taylor Mitchell for the initial patch, and Ian Clelland for
 review and cleanup.
 }}}

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

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

[django/django] 117e99: Added assertXML[Not]Equal assertions

2012-10-06 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 117e99511e0985701780ed1bcd3afd456e244ae3
  
https://github.com/django/django/commit/117e99511e0985701780ed1bcd3afd456e244ae3
  Author: Claude Paroz 
  Date:   2012-10-06 (Sat, 06 Oct 2012)

  Changed paths:
M django/test/testcases.py
M django/test/utils.py
M docs/releases/1.5.txt
M docs/topics/testing.txt
M tests/regressiontests/test_utils/tests.py

  Log Message:
  ---
  Added assertXML[Not]Equal assertions

This is especially needed to compare XML when hash randomization
is on, as attribute order may vary. Refs #17758, #19038.
Thanks Taylor Mitchell for the initial patch, and Ian Clelland for
review and cleanup.



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

Re: [Django] #17435: document that QuerySet.update returns not the number of rows changed, but the number of rows matched

2012-10-06 Thread Django 
#17435: document that QuerySet.update returns not the number of rows changed, 
but
the number of rows matched
-+-
 Reporter:  m17.admin@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.3
 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:"c06b724a00236b086a5a64510d8bf11978f083f8"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c06b724a00236b086a5a64510d8bf11978f083f8"
 [1.4.X] Fixed #17435 - Clarified that QuerySet.update returns the number
 of rows matched

 Backport of 6d46c740d8 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] c06b72: [1.4.X] Fixed #17435 - Clarified that QuerySet.upd...

2012-10-06 Thread GitHub 
  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: c06b724a00236b086a5a64510d8bf11978f083f8
  
https://github.com/django/django/commit/c06b724a00236b086a5a64510d8bf11978f083f8
  Author: Tim Graham 
  Date:   2012-10-06 (Sat, 06 Oct 2012)

  Changed paths:
M docs/ref/models/querysets.txt
M docs/topics/db/queries.txt

  Log Message:
  ---
  [1.4.X] Fixed #17435 - Clarified that QuerySet.update returns the number of 
rows matched

Backport of 6d46c740d8 from master



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

Re: [Django] #17435: document that QuerySet.update returns not the number of rows changed, but the number of rows matched

2012-10-06 Thread Django 
#17435: document that QuerySet.update returns not the number of rows changed, 
but
the number of rows matched
-+-
 Reporter:  m17.admin@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.3
 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
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"6d46c740d80b0c7f75064bc6bb4d99b15b106ba4"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6d46c740d80b0c7f75064bc6bb4d99b15b106ba4"
 Fixed #17435 - Clarified that QuerySet.update returns the number of rows
 matched
 }}}

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

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

[django/django] 6d46c7: Fixed #17435 - Clarified that QuerySet.update retu...

2012-10-06 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 6d46c740d80b0c7f75064bc6bb4d99b15b106ba4
  
https://github.com/django/django/commit/6d46c740d80b0c7f75064bc6bb4d99b15b106ba4
  Author: Tim Graham 
  Date:   2012-10-06 (Sat, 06 Oct 2012)

  Changed paths:
M docs/ref/models/querysets.txt
M docs/topics/db/queries.txt

  Log Message:
  ---
  Fixed #17435 - Clarified that QuerySet.update returns the number of rows 
matched



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

Re: [Django] #19038: Add Experimental Support for Python 3.3

2012-10-06 Thread Django 
#19038: Add Experimental Support for Python 3.3
-+
 Reporter:  clelland |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Python 3 |  Version:  master
 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16039: syncdb with --database option fails

2012-10-06 Thread Django 
#16039: syncdb with --database option fails
-+-
 Reporter:  yedpodtrzitko|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Design
 Keywords:   |  decision needed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by mhaligowski):

 * owner:  mhaligowski => nobody


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

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

Re: [Django] #16039: syncdb with --database option fails

2012-10-06 Thread Django 
#16039: syncdb with --database option fails
-+-
 Reporter:  yedpodtrzitko|Owner:
 Type:  Bug  |  mhaligowski
Component:  Database layer   |   Status:  new
  (models, ORM)  |  Version:  1.4
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by mhaligowski):

 * stage:  Accepted => Design decision needed


Comment:

 Not sure about the design decision, as discussed in IRC.

 The provided patch will be fine when ContentType should be synchronized in
 all databases. This could lead to discrepancies in IDs, though, as pointed
 out by @freakyboy3742.

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

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

Re: [Django] #18990: 'manage.py loaddata' does not report if the loading file does not exist

2012-10-06 Thread Django 
#18990: 'manage.py loaddata' does not report if the loading file does not exist
-+-
 Reporter:  sergzach |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  1.4
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  loaddata |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by d1ffuz0r):

 Hmm. Every time the commands "loaddata" and "flush" trying to load the
 'initial_data' fixture, how be with it. Ignore? Because that be generate
 the errors. Setup  "--no-initial-data" default value to False can break
 backward compatibilities

 django/core/management/commands/syncdb.py:
 {{{
 # Load initial_data fixtures (unless that has been disabled)
 if load_initial_data:
 call_command('loaddata', 'initial_data', verbosity=verbosity,
  database=db, skip_validation=True)

 }}}


 
 Sorry for my English

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

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

Re: [Django] #19077: UserAdmin.add_view should handle USERNAME_FIELD on custom User models

2012-10-06 Thread Django 
#19077: UserAdmin.add_view should handle USERNAME_FIELD on custom User models
-+
 Reporter:  gwahl@…  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  contrib.auth |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by russellm):

 * stage:  Design decision needed => Accepted


Comment:

 One immediate improvement I can see is to actually make USERNAME_FIELD
 required, like it says in the docs, rather than a "defaults to username"
 attribute. That simplifies a lot of internal logic. Beyond that: I can
 certainly see the benefit in having a get_username()-esque field.

 As for the admin registration issues: UserAdmin will really only ever work
 for auth.User. If you subclass AbstractBaseUser, you'll have a completely
 different set of fields to display in admin; If you're subclassing
 AbstractUser, you're doing so do add fields, so you'll have at least
 *some* different admin requirements. Writing your own UserAdmin is
 inevitable; all we can do is make it easier.

 The good news is that if you subclass UserAdmin, you can just override the
 fieldset and form definitions, register your User class, and everything
 will work as you expect. This warrants documentation, but I don't think
 massive changes to UserAdmin (the original issue raised in this ticket
 notwithstanding) are called for.

 Admin registrations for Comments (and any other model that references
 User) are an other issue entirely... however I think we can get some
 traction with lazy evaluation of attributes.

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

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

Re: [Django] #17435: document that QuerySet.update returns not the number of rows changed, but the number of rows matched

2012-10-06 Thread Django 
#17435: document that QuerySet.update returns not the number of rows changed, 
but
the number of rows matched
-+-
 Reporter:  m17.admin@…  |Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Documentation|  Version:  1.3
 Severity:  Normal   |   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 claudep):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #19069: improve error when attempting to use a swapped model

2012-10-06 Thread Django 
#19069: improve error when attempting to use a swapped model
--+
 Reporter:  ptone |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  closed
Component:  Database layer (models, ORM)  |Version:  1.4
 Severity:  Normal| Resolution:  fixed
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  0 |  Easy pickings:  0
UI/UX:  0 |
--+
Changes (by Russell Keith-Magee ):

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


Comment:

 In [changeset:"cc337a74f1808b216fff96f1695d8b066d2636f6"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cc337a74f1808b216fff96f1695d8b066d2636f6"
 Fixed #19069 -- Improved the error message when trying to query a swapped
 model.

 Thanks to Preston Holmes for the suggestion.
 }}}

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

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

[django/django] cc337a: Fixed #19069 -- Improved the error message when tr...

2012-10-06 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: cc337a74f1808b216fff96f1695d8b066d2636f6
  
https://github.com/django/django/commit/cc337a74f1808b216fff96f1695d8b066d2636f6
  Author: Russell Keith-Magee 
  Date:   2012-10-05 (Fri, 05 Oct 2012)

  Changed paths:
M django/db/models/manager.py
M tests/regressiontests/managers_regress/models.py
M tests/regressiontests/managers_regress/tests.py

  Log Message:
  ---
  Fixed #19069 -- Improved the error message when trying to query a swapped 
model.

Thanks to Preston Holmes for the suggestion.



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