Re: [Django] #17750: User.get_profile() returns cached object when database object has changed

[Django]

#17750: User.get_profile() returns cached object when database object has 
changed
-+-
 Reporter:  rjalves  |Owner:  nobody
 Type:  New feature  |   Status:  new
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
-+-

Comment (by ptone):

 I'd lean strongly toward a wontfix for this. If one has specific needs for
 this in testing during deprecation, they can just manipulate the
 _profile_cache attr directly.

 I'm starting to rework the auth docs substantially and get_profile will
 have a __much__ smaller presence in the 1.5 docs.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #2443: Add IntervalField to database models

[Django]

#2443: Add IntervalField to database models
-+-
 Reporter:  ben.tucker@… |Owner:  Adys
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  IntervalField|  Needs documentation:  0
  interval duration DurationField|  Patch needs improvement:  1
  feature|UI/UX:  1
Has patch:  1|
  Needs tests:  1|
Easy pickings:  0|
-+-
Changes (by net147):

 * cc: net147 (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 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] #17974: .distint('FIELDNAME') FAILS for MySQL

[Django]

#17974: .distint('FIELDNAME') FAILS for MySQL
-+-
 Reporter:  mschettler@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:  distinct on  |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by lionelswhite):

 To lay your bets correctly and know the type of
 [http://bettingsportsonlinee.com/ betting sports] and their odds,
 understanding them is crucial, with the right amount of knowledge, will
 assist you in betting wisely.

-- 
Ticket URL: 
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] #19098: UnicodeDecodeError when including URLs in Windows with non-ASCII paths

[Django]

#19098: UnicodeDecodeError when including URLs in Windows with non-ASCII paths
-+-
 Reporter:   |  Owner:  nobody
  artamoshin | Status:  new
 Type:  Bug  |Version:  1.4
Component:  Core |   Keywords:  non-ascii unicode windows path
  (URLs) |  UnicodeDecodeError url include
 Severity:  Normal   |  Has patch:  1
 Triage Stage:   |  UI/UX:  0
  Unreviewed |
Easy pickings:  0|
-+-
 Including app URLs raises UnicodeDecodeError when project path contains
 non-ASCII characters (i.e. c:\Users\Александр\Documents\Projects')
 {{{
 Traceback (most recent call last):
   File "C:\Python27\lib\wsgiref\handlers.py", line 85, in run
 self.result = application(self.environ, self.start_response)
   File "C:\Python27\lib\site-
 packages\django\contrib\staticfiles\handlers.py", line 67, in __call__
 return self.application(environ, start_response)
   File "C:\Python27\lib\site-packages\django\core\handlers\wsgi.py", line
 241, in __call__
 response = self.get_response(request)
   File "C:\Python27\lib\site-packages\django\core\handlers\base.py", line
 146, in get_response
 response = debug.technical_404_response(request, e)
   File "C:\Python27\lib\site-packages\django\views\debug.py", line 443, in
 technical_404_response
 'reason': smart_str(exception, errors='replace'),
   File "C:\Python27\lib\site-packages\django\utils\encoding.py", line 116,
 in smart_str
 return str(s)
   File "C:\Python27\lib\site-packages\django\core\urlresolvers.py", line
 235, in __repr__
 return smart_str(u'<%s %s (%s:%s) %s>' % (self.__class__.__name__,
 self.urlconf_name, self.app_name, self.namespace, self.regex.pattern))
 UnicodeDecodeError: 'ascii' codec can't decode byte 0xef in position 37:
 ordinal
  not in range(128)
 }}}
 because string module representation is bytesting that contains non-ASCII
 path, and it fails to format with u'%s' % self.urlconf_name.

 My solution: convert string representation with
 sys.getfilesystemencoding() to Unicode.

-- 
Ticket URL: 
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] #19097: Request and Response Page misses key info

[Django]

#19097: Request and Response Page misses key info
+
 Reporter:  anonymous   |  Owner:  nobody
 Type:  Cleanup/optimization| Status:  closed
Component:  Documentation   |Version:  1.4
 Severity:  Normal  | Resolution:  fixed
 Keywords:  request, response, api  |   Triage Stage:  Unreviewed
Has patch:  0   |  Easy pickings:  1
UI/UX:  0   |
+
Changes (by Preston Holmes ):

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


Comment:

 In [changeset:"c99ad64df7f8b7bdf504ef1c329610fce3c7f1b0"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c99ad64df7f8b7bdf504ef1c329610fce3c7f1b0"
 Fixed #19097 -- documented module of origin for HttpRes/req objects
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] c99ad6: Fixed #19097 -- documented module of origin for Ht...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c99ad64df7f8b7bdf504ef1c329610fce3c7f1b0
  
https://github.com/django/django/commit/c99ad64df7f8b7bdf504ef1c329610fce3c7f1b0
  Author: Preston Holmes 
  Date:   2012-10-09 (Tue, 09 Oct 2012)

  Changed paths:
M docs/ref/request-response.txt

  Log Message:
  ---
  Fixed #19097 -- documented module of origin for HttpRes/req objects



-- 
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] #9084: File-based session does not store any data on Windows

[Django]

#9084: File-based session does not store any data on Windows
--+
 Reporter:  mizutori  |Owner:
 Type:  Bug   |   Status:  new
Component:  contrib.sessions  |  Version:  1.3
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by anonymous):

 This still happens in 1.4.1. Unfortunately it makes file-based sessions
 useless on Django in Windows (i.e., development or whatever). Also, it's
 hard to find, as the exception is caught without warning -- this wouldn't
 be so bad if it broke noisily.

-- 
Ticket URL: 
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] #16211: using negated F()-expression in update query

[Django]

#16211: using negated F()-expression in update query
-+-
 Reporter:  wdoekes  |Owner:  nobody
 Type:  New feature  |   Status:  reopened
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

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

 In [changeset:"041ef9ed68722fa5f8c38c9e39fad67714f35014"]:
 {{{
 #!CommitTicketReference repository=""
 revision="041ef9ed68722fa5f8c38c9e39fad67714f35014"
 Removed some uses of F() expression & and |

 Refs #16211
 }}}

-- 
Ticket URL: 
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] 041ef9: Removed some uses of F() expression & and |

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 041ef9ed68722fa5f8c38c9e39fad67714f35014
  
https://github.com/django/django/commit/041ef9ed68722fa5f8c38c9e39fad67714f35014
  Author: Anssi Kääriäinen 
  Date:   2012-10-09 (Tue, 09 Oct 2012)

  Changed paths:
M tests/regressiontests/expressions_regress/tests.py

  Log Message:
  ---
  Removed some uses of F() expression & and |

Refs #16211



-- 
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] f578ee: Mark the test for left/right lookup types as a kno...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: f578ee32fa41b7d2b3308d98e9d528ab4853a720
  
https://github.com/django/django/commit/f578ee32fa41b7d2b3308d98e9d528ab4853a720
  Author: Justin Bronn 
  Date:   2012-10-09 (Tue, 09 Oct 2012)

  Changed paths:
M django/contrib/gis/tests/geoapp/tests.py

  Log Message:
  ---
  Mark the test for left/right lookup types as a known failure on PostGIS 2.0.



-- 
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] #19097: Request and Response Page misses key info

[Django]

#19097: Request and Response Page misses key info
--+
 Reporter:  anonymous |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.4
 Severity:  Normal|   Keywords:  request, response, api
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 I use this page for quick reference to the HttpRequest and HttpResponse
 objects.  However,''' what django module these belong to is not
 included.'''  Because this page doubles as API documentation, I have to
 hunt a lot more to dig up this information.

 Please include a quick reference to the parent module where these objects
 reside.

-- 
Ticket URL: 
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] #18927: bulk_create tests expect explicit query count even for database that doens't support bulk insert

[Django]

#18927: bulk_create tests expect explicit query count even for database that
doens't support bulk insert
---+--
 Reporter:  manfre |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords:  bulk_create| Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by Anssi Kääriäinen ):

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


Comment:

 In [changeset:"32ac067a6ddca465cd94fc7ee35bfe54a675979b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="32ac067a6ddca465cd94fc7ee35bfe54a675979b"
 Fixed #18927 -- Fixed bulk_create tests when no has_bulk_insert
 }}}

-- 
Ticket URL: 
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] 32ac06: Fixed #18927 -- Fixed bulk_create tests when no ha...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 32ac067a6ddca465cd94fc7ee35bfe54a675979b
  
https://github.com/django/django/commit/32ac067a6ddca465cd94fc7ee35bfe54a675979b
  Author: Michael Manfre 
  Date:   2012-10-09 (Tue, 09 Oct 2012)

  Changed paths:
M tests/regressiontests/bulk_create/tests.py

  Log Message:
  ---
  Fixed #18927 -- Fixed bulk_create tests when no has_bulk_insert



-- 
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] #16211: using negated F()-expression in update query

[Django]

#16211: using negated F()-expression in update query
-+-
 Reporter:  wdoekes  |Owner:  nobody
 Type:  New feature  |   Status:  reopened
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by akaariai):

 * status:  closed => reopened
 * resolution:  fixed =>
 * severity:  Release blocker => Normal
 * stage:  Ready for checkin => Accepted


Comment:

 The commits above were reverts, so reopening...

 The current status is that once 1.5 branch is created we can reapply the
 reverted patches (with minor modifications, of course).

-- 
Ticket URL: 
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] #16211: using negated F()-expression in update query

[Django]

#16211: using negated F()-expression in update query
-+-
 Reporter:  wdoekes  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Anssi Kääriäinen ):

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


Comment:

 In [changeset:"a8b1861fc4d0a48b4879af803bba094eef145017"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a8b1861fc4d0a48b4879af803bba094eef145017"
 Revert "Fixed #16211 -- Added comparison and negation ops to F()
 expressions"

 This reverts commit 28abf5f0ebc9d380f25dd278d7ef4642c4504545.

 Conflicts:

 docs/releases/1.5.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 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] #16211: using negated F()-expression in update query

[Django]

#16211: using negated F()-expression in update query
-+-
 Reporter:  wdoekes  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

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

 In [changeset:"b625e8272bd41714c838cfda3fb54e1f5177f009"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b625e8272bd41714c838cfda3fb54e1f5177f009"
 Moved F() '&' and '|' to .bitand() and .bitor()

 Done for consistency with Q() expressions and QuerySet combining. This
 will allow usage of '&' and '|' as boolean logical operators in the
 future. Refs #16211.
 }}}

-- 
Ticket URL: 
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] 7f4dbd: Revert "Splitted expressions tests into smaller me...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 7f4dbdc036a4439ed3e4954625fe91596b314a36
  
https://github.com/django/django/commit/7f4dbdc036a4439ed3e4954625fe91596b314a36
  Author: Anssi Kääriäinen 
  Date:   2012-10-09 (Tue, 09 Oct 2012)

  Changed paths:
M tests/modeltests/expressions/tests.py

  Log Message:
  ---
  Revert "Splitted expressions tests into smaller methods"

This reverts commit c2532825dbe2a422bbce67285637febb0ef9c9f1.


  Commit: a8b1861fc4d0a48b4879af803bba094eef145017
  
https://github.com/django/django/commit/a8b1861fc4d0a48b4879af803bba094eef145017
  Author: Anssi Kääriäinen 
  Date:   2012-10-09 (Tue, 09 Oct 2012)

  Changed paths:
M django/db/backends/__init__.py
M django/db/models/expressions.py
M django/utils/tree.py
M docs/releases/1.5.txt
M docs/topics/db/queries.txt
M tests/modeltests/expressions/models.py
M tests/modeltests/expressions/tests.py

  Log Message:
  ---
  Revert "Fixed #16211 -- Added comparison and negation ops to F() expressions"

This reverts commit 28abf5f0ebc9d380f25dd278d7ef4642c4504545.

Conflicts:

docs/releases/1.5.txt


  Commit: b625e8272bd41714c838cfda3fb54e1f5177f009
  
https://github.com/django/django/commit/b625e8272bd41714c838cfda3fb54e1f5177f009
  Author: Anssi Kääriäinen 
  Date:   2012-10-09 (Tue, 09 Oct 2012)

  Changed paths:
M django/db/models/expressions.py
M docs/releases/1.5.txt
M docs/topics/db/queries.txt
M tests/regressiontests/expressions_regress/tests.py

  Log Message:
  ---
  Moved F() '&' and '|' to .bitand() and .bitor()

Done for consistency with Q() expressions and QuerySet combining. This
will allow usage of '&' and '|' as boolean logical operators in the
future. Refs #16211.


Compare: https://github.com/django/django/compare/c2150d4d2c53...b625e8272bd4

-- 
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] #19096: SQLInsertCompiler and DatabaseOperations.return_insert_id for non standard backends

[Django]

#19096: SQLInsertCompiler and DatabaseOperations.return_insert_id for non 
standard
backends
-+-
 Reporter:  manfre   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Database layer   |   Resolution:  fixed
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by Anssi Kääriäinen ):

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


Comment:

 In [changeset:"c2150d4d2c5342488e474825c67dd3210fafc0e7"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c2150d4d2c5342488e474825c67dd3210fafc0e7"
 Fixed #19096 -- Made can_return_id_from_insert more extendable

 RETURNING is an extension of the SQL standard, which is not implemented
 the same by all databases. Allow DatabaseOperations.return_insert_id to
 return a None to allow for other 3rd party backends with a different
 implementation.
 }}}

-- 
Ticket URL: 
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] c2150d: Fixed #19096 -- Made can_return_id_from_insert mor...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c2150d4d2c5342488e474825c67dd3210fafc0e7
  
https://github.com/django/django/commit/c2150d4d2c5342488e474825c67dd3210fafc0e7
  Author: Michael Manfre 
  Date:   2012-10-09 (Tue, 09 Oct 2012)

  Changed paths:
M django/db/models/sql/compiler.py

  Log Message:
  ---
  Fixed #19096 -- Made can_return_id_from_insert more extendable

RETURNING is an extension of the SQL standard, which is not implemented
the same by all databases. Allow DatabaseOperations.return_insert_id to
return a None to allow for other 3rd party backends with a different
implementation.



-- 
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] #16211: using negated F()-expression in update query

[Django]

#16211: using negated F()-expression in update query
-+-
 Reporter:  wdoekes  |Owner:  nobody
 Type:  New feature  |   Status:  reopened
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by akaariai):

 Yeah, it is a little bit ugly that we need to use the bitwise operators
 for their boolean meaning. But, that seems the only way forward if we want
 to support boolean operators for F() expressions. And, it seems we want
 that, this will allow using .update() in new situations with little added
 code.

 Even if we wouldn't want boolean operators for F() expressions it is
 questionable if using '&' for different meaning in Q() and F() expressions
 is a good API.

 I believe the users of '&' and '|' in their bitwise meaning are extremely
 rare, so this shouldn't be a big issue for most users.

 I will commit the removal of '&' and '|' soon.

-- 
Ticket URL: 
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] #19096: SQLInsertCompiler and DatabaseOperations.return_insert_id for non standard backends

[Django]

#19096: SQLInsertCompiler and DatabaseOperations.return_insert_id for non 
standard
backends
-+-
 Reporter:  manfre   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.4
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by manfre):

 Pull request.
 https://github.com/django/django/pull/433

-- 
Ticket URL: 
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] #17867: validate_email fails with IDN domains

[Django]

#17867: validate_email fails with IDN domains
-+-
 Reporter:  Pierre   |Owner:  nobody
 |   Status:  closed
 Type:  Bug  |  Version:
Component:  Forms|  1.4-beta-1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  idn  | 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:"252cd271e88e1c60fc49c06fac9d45e4c7f8750e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="252cd271e88e1c60fc49c06fac9d45e4c7f8750e"
 Fixed test failure after IDN domain validation fix

 Refs #17867.
 The address in test_email_regexp_for_performance used to take forever
 (security issue), then was supposed to fail after the fix (commit
 9f8287a3f).
 Now we are less strict with domain validation, due to new IDN domains,
 hence the validation of this address pass now.
 }}}

-- 
Ticket URL: 
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] 252cd2: Fixed test failure after IDN domain validation fix

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 252cd271e88e1c60fc49c06fac9d45e4c7f8750e
  
https://github.com/django/django/commit/252cd271e88e1c60fc49c06fac9d45e4c7f8750e
  Author: Claude Paroz 
  Date:   2012-10-09 (Tue, 09 Oct 2012)

  Changed paths:
M tests/regressiontests/forms/tests/fields.py

  Log Message:
  ---
  Fixed test failure after IDN domain validation fix

Refs #17867.
The address in test_email_regexp_for_performance used to take forever
(security issue), then was supposed to fail after the fix (commit 9f8287a3f).
Now we are less strict with domain validation, due to new IDN domains,
hence the validation of this address pass now.



-- 
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] #11998: IntegerField not validated for overflow

[Django]

#11998: IntegerField not validated for overflow
-+-
 Reporter:  francis.giraldeau@…  |Owner:  tobias
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by anonymous):

 * version:  1.1 => 1.4
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0
 * ui_ux:   => 0


Comment:

 Problem persists in 1.4.1

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] 0a0fe8: Fix exception message from 3190abcd. Refs #18153.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 0a0fe8f71d54e8479e3050ef3bb9d545fd734a65
  
https://github.com/django/django/commit/0a0fe8f71d54e8479e3050ef3bb9d545fd734a65
  Author: Aymeric Augustin 
  Date:   2012-10-09 (Tue, 09 Oct 2012)

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

  Log Message:
  ---
  Fix exception message from 3190abcd. Refs #18153.

Thanks Preston Holmes.



-- 
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] #18153: Erorneous OneToOneField for instances that have pk unset

[Django]

#18153: Erorneous OneToOneField for instances that have pk unset
-+-
 Reporter:  jbzdak@… |Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  fixed
 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|
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"0a0fe8f71d54e8479e3050ef3bb9d545fd734a65"]:
 {{{
 #!CommitTicketReference repository=""
 revision="0a0fe8f71d54e8479e3050ef3bb9d545fd734a65"
 Fix exception message from 3190abcd. Refs #18153.

 Thanks Preston Holmes.
 }}}

-- 
Ticket URL: 
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] #19096: SQLInsertCompiler and DatabaseOperations.return_insert_id for non standard backends

[Django]

#19096: SQLInsertCompiler and DatabaseOperations.return_insert_id for non 
standard
backends
-+-
 Reporter:  manfre   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.4
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Accepted
 * type:  Uncategorized => Cleanup/optimization
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 `RETURNING` is an extension of the SQL standard. We can't make assumptions
 about how the various databases implement it.

 Adding a `if r_fmt is None:` here looks harmless.

 I'm in favor of helping 3rd party database adapters when we can.

-- 
Ticket URL: 
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] #19096: SQLInsertCompiler and DatabaseOperations.return_insert_id for non standard backends

[Django]

#19096: SQLInsertCompiler and DatabaseOperations.return_insert_id for non 
standard
backends
--+
 Reporter:  manfre|  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 I ran in to a problem with SQLInsertCompiler while trying to allow django-
 mssql to have `can_return_id_from_insert = True`.  The problem is that
 SQLInsertCompiler requires that an SQL fragment (returned by
 ops.return_insert_id) is appended to the end of the insert statement, but
 the fragment must also accept the full quoted table and column name.

 
https://github.com/django/django/blob/master/django/db/models/sql/compiler.py#L900

 The problem for mssql, is that the OUTPUT clause doesn't conform to these
 two requirements and is better served by mangling the SQL query in its own
 SQLInsertCompiler. To make this possible (in a backwards compatible way),
 the output of return_insert_id needs to be checked and ignored if r_fmt is
 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 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] #18153: Erorneous OneToOneField for instances that have pk unset

[Django]

#18153: Erorneous OneToOneField for instances that have pk unset
-+-
 Reporter:  jbzdak@… |Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  fixed
 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 Aymeric Augustin ):

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


Comment:

 In [changeset:"3190abcd75b1fcd660353da4001885ef82cbc596"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3190abcd75b1fcd660353da4001885ef82cbc596"
 Fixed #18153 -- Reverse OneToOne lookups on unsaved instances.

 Thanks David Hatch and Anssi Kääriäinen for their inputs.
 }}}

-- 
Ticket URL: 
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] #19095: Dubious code in multiple_database tests

[Django]

#19095: Dubious code in multiple_database tests
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"c9b4e9ac3a6c56f2b006b723972e77722d3ac937"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c9b4e9ac3a6c56f2b006b723972e77722d3ac937"
 Fixed #19095 -- invalid code in multidb tests.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] c9b4e9: Fixed #19095 -- invalid code in multidb tests.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c9b4e9ac3a6c56f2b006b723972e77722d3ac937
  
https://github.com/django/django/commit/c9b4e9ac3a6c56f2b006b723972e77722d3ac937
  Author: Aymeric Augustin 
  Date:   2012-10-09 (Tue, 09 Oct 2012)

  Changed paths:
M tests/regressiontests/multiple_database/tests.py

  Log Message:
  ---
  Fixed #19095 -- invalid code in multidb tests.


  Commit: 3190abcd75b1fcd660353da4001885ef82cbc596
  
https://github.com/django/django/commit/3190abcd75b1fcd660353da4001885ef82cbc596
  Author: Aymeric Augustin 
  Date:   2012-10-09 (Tue, 09 Oct 2012)

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

  Log Message:
  ---
  Fixed #18153 -- Reverse OneToOne lookups on unsaved instances.

Thanks David Hatch and Anssi Kääriäinen for their inputs.


Compare: https://github.com/django/django/compare/273b96ef9d3a...3190abcd75b1

-- 
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] #18153: Erorneous OneToOneField for instances that have pk unset

[Django]

#18153: Erorneous OneToOneField for instances that have pk unset
-+-
 Reporter:  jbzdak@… |Owner:  aaugustin
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by aaugustin):

 I've created #19095 to discuss the test failure above.

 That test contains the programming error that the second version of the
 patch attempts to prevent: setting a reverse relation on an unsaved
 objects.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #19095: Dubious code in multiple_database tests

[Django]

#19095: Dubious code in multiple_database tests
-+-
   Reporter:  aaugustin  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  master
  layer (models, ORM)|   Keywords:
   Severity:  Normal |  Has patch:  0
   Triage Stage: |Needs tests:  0
  Unreviewed |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 `QueryTestCase.test_o2o_cross_database_protection` contains code that
 seems invalid to me.

 In that test, `UserProfile` has a nullable one-to-one relation to `User`.

 An unsaved instance of `User` called `charlie` is created at line 655, and
 a profile is attached to this instance at line 664: `charlie.userprofile =
 bob_profile`.

 But after saving everything, that doesn't work as expected: the profile
 isn't linked to the user!

 This is easy to understand: this line basically performs
 `bob_profile.user_id = charlie.id` (and populates relation caches); but
 since `charlie` is unsaved, `charlie.id` is `None`, hence
 `bob_profile.used_id` remains `None`.

 I'm attaching a patch for this test case that reloads the objects and
 tests that `charlie.userprofile == bob_profile` ; with this patch, the
 test fails, proving my point.

 

 In #18153, I tried to catch such programming errors by raising an
 exception. And that breaks that test.

 I think this code needs to fixed, while preserving as much of the testing
 behavior as possible.

-- 
Ticket URL: 
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] #2284: [patch] Extra /sql files with whitespace break syncdb

[Django]

#2284: [patch] Extra /sql files with whitespace break syncdb
-+-
 Reporter:  scottanderson|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  syncdb   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by claudep):

 I think that the parsing solution leads us nowhere. It is not fair to
 penalize all backends because some cannot execute multiple statements.
 IMHO, we should have a backend-specific `load_sql` that take care of
 either splitting the statements or to feed the database with the read file
 at once.

-- 
Ticket URL: 
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] #1919: filter truncatewords wipes newlines from string, so not chainable with markup filters

[Django]

#1919: filter truncatewords wipes newlines from string, so not chainable with
markup filters
-+
 Reporter:  derelm   |Owner:
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  sprintsept14 | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by claudep):

 * owner:  nobody =>
 * status:  reopened => new


Comment:

 I think that the parsing solution leads us nowhere. It is not fair to
 penalize all backends because some cannot execute multiple statements.
 IMHO, we should have a backend-specific `load_sql` that take care of
 either splitting the statements or to feed the database with the read file
 at once.

-- 
Ticket URL: 
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] #19094: FakePayload should accept unicode

[Django]

#19094: FakePayload should accept unicode
---+
 Reporter:  ondrowan   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by claudep):

 * has_patch:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 Note that the modified tests in my patch are not necessary, they still
 pass with the modified !FakePayload. However I modified them to show the
 advantage of the enhanced !FakePayload.

-- 
Ticket URL: 
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] #361: Some Basic Math Filters

[Django]

#361: Some Basic Math Filters
-+--
 Reporter:  ilikeprivacy@…   |Owner:  adrian
 Type:  defect   |   Status:  closed
Component:  Template system  |  Version:
 Severity:  normal   |   Resolution:  wontfix
 Keywords:  filter math  | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by dbrgn):

 * cc: dbrgn (added)


Comment:

 As a workaround, I created a separate Django app containing "sub", "mul",
 "div" and "abs" filters: https://github.com/gwrtheyrn/django-mathfilters

 will@..., you could also add -10 instead of subtracting 10 in your case:
 `list_items|length|add:-10`

-- 
Ticket URL: 
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] #361: Some Basic Math Filters

[Django]

#361: Some Basic Math Filters
-+--
 Reporter:  ilikeprivacy@…   |Owner:  adrian
 Type:  defect   |   Status:  closed
Component:  Template system  |  Version:
 Severity:  normal   |   Resolution:  wontfix
 Keywords:  filter math  | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by ptone):

 Replying to [comment:20 will@…]:
 > I would like to have a "subtract" filter for this use case:

 If you feel you have a display related argument here - you are better off
 opening a new ticket than posting a comment on a very old wontfix ticket.

 If you choose to do so, please explicitly reference this ticket, and
 explain why you think it is a different circumstance.

-- 
Ticket URL: 
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] #19091: NoReverseMatch template errors are difficult to debug (was: NoReverseMatch template errors are impossible to debug)

[Django]

#19091: NoReverseMatch template errors are difficult to debug
--+
 Reporter:  alper |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (URLs)   |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  1
--+
Changes (by ptone):

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


Comment:

 Always worth improving error messages

-- 
Ticket URL: 
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] #8413: Django doesn't reload itself after updating files on disk that raised error on import.

[Django]

#8413: Django doesn't reload itself after updating files on disk that raised 
error
on import.
-+-
 Reporter:  buriy|Owner:  buriy
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  autoreload reload|  Needs documentation:  0
  import error fix   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by tdhutt@…):

 After more extensive testing, it's working quite well but I did get this
 one error:

 {{{
 Unhandled exception in thread started by 
 Error in sys.excepthook:
 Traceback (most recent call last):
   File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 50,
 in apport_excepthook
 if not enabled():
 TypeError: 'NoneType' object is not callable

 Original exception was:
 Traceback (most recent call last):
   File "/usr/local/lib/python2.7/dist-
 packages/django/utils/autoreload.py", line 83, in wrapper
 fn(*args, **kwargs)
   File "/usr/local/lib/python2.7/dist-
 packages/django/core/management/commands/runserver.py", line 111, in
 inner_run
 ipv6=self.use_ipv6, threading=threading)
   File "/usr/local/lib/python2.7/dist-
 packages/django/core/servers/basehttp.py", line 253, in run
 httpd.serve_forever()
   File "/usr/lib/python2.7/SocketServer.py", line 225, in serve_forever
 r, w, e = select.select([self], [], [], poll_interval)
 AttributeError: 'NoneType' object has no attribute 'select'
 }}}

-- 
Ticket URL: 
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] #10227: Support a related_default on OneToOne fields

[Django]

#10227: Support a related_default on OneToOne fields
-+-
 Reporter:  rvdrijst |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  onetoone related |  Needs documentation:  0
  expection null |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by olau):

 Well, if the conceptual model is adding objects lazily, it's not really a
 problem that you need to save the user profile to get your changes to
 stick - they wouldn't stick otherwise. My example would never have worked
 without the save if the intention was to change the name persistently.

 But it's true that one would have to careful to make sure the user object
 was saved so it had an id. You have the same problem if you write the code
 manually, though.

 I had some trouble understanding your example on the difference to the
 foreign key default parameter - it seems what you are thinking about is a
 zero-or-one to one mapping, not a zero-or-one to zero-to-one (that would
 be related_default=None). Yes, it's less powerful in the related end in
 that you can't avoid confounding null and default. But there's no way
 around that. When I said relatively in line with the existing API, I just
 meant that the conceptual idea of returning an in-memory object when
 nothing exists yet was the same.

 Thanks for looking at this, by the way. :)

-- 
Ticket URL: 
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] #19094: FakePayload should accept unicode

[Django]

#19094: FakePayload should accept unicode
---+--
 Reporter:  ondrowan   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by ondrowan):

 * needs_docs:   => 0
 * type:  New feature => Bug
 * needs_tests:   => 0
 * needs_better_patch:   => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #19094: FakePayload should accept unicode

[Django]

#19094: FakePayload should accept unicode
---+
 Reporter:  ondrowan   |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  Testing framework  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 As discussed
 
[https://github.com/django/django/commit/d7dfab59ead97b35c6f6786784225f377783e376#commitcomment-1967165
 on GitHub], I think
 [https://github.com/django/django/blob/master/django/test/client.py#L39
 FakePayload] should accept unicode. Current implementation breaks stuff
 that worked in 1.4. @claudep had some ideas, so I'm creating this ticket
 for his 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 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] #16304: Add HTML5 'placeholder' attribute support to form fields.

[Django]

#16304: Add HTML5 'placeholder' attribute support to form fields.
-+-
 Reporter:  rich@…   |Owner:  j4nu5
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  forms, placeholder,  | Triage Stage:  Accepted
  html5  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  1
Easy pickings:  1|
-+-

Comment (by tonnzor):

 Any blockers for landing it in the master? It looks like it is done but
 not merged for some reason.

 It is really needed and useful feature, it improves user experience
 without tons of workarounds.

 Just to note -- all major browsers already support it for more than a
 year:
 {{{
 browser: Firefox Safari Chrome  Opera   IE  iPhone  Android
 version: 4.0+4.0+   4.0+11.0+   10.0+   4.0+2.1+
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #10227: Support a related_default on OneToOne fields

[Django]

#10227: Support a related_default on OneToOne fields
-+-
 Reporter:  rvdrijst |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  onetoone related |  Needs documentation:  0
  expection null |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by akaariai):

 The example of related_default usage is exactly what I am afraid. That
 code contains a serious pitfall: the user.profile isn't saved, and it will
 not be associated to the user if you don't save it. And, you do get that
 default value even for saved user instances.

 There is a big difference to how foreign key default argument works:
 {{{
 class A(models.Model):
 pass

 def get_a():
 return A.objects.get_or_create(pk=1)[0]

 class B(models.Model):
 a = models.ForeignKey(A, null=True, default=get_a)

 b = B()
 print b.a
 b = B(a=None)
 print b.a
 b = B(a=None)
 b.save()
 b = B.objects.get()
 print b.a
 }}}

 The output is:
 {{{
 A object
 None
 None
 }}}

 My understanding is that the "related_default" would return "A object" for
 each case. This is broken - what you get from b.a doesn't reflect the
 database state.

 The related_none could work. Here I am mainly worried of not knowing what
 happens when I write:
 {{{
 p = request.user.profile
 }}}
 does it raise `DoesNotExist` if the profile doesn't exists, or will p just
 be None? However, I do not feel too strongly about this case.

 The good thing about b.nget('a') is that when you see the code, you
 immediately know what the code does. You are explicitly asking for a value
 that can be None value, so you will be prepared to handle the None case.
 This is relatively simple to do in user code, so there is no strong reason
 to have this convenience method in Django core.

-- 
Ticket URL: 
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] #19093: threading._Event doesn't exist in python 3.3

[Django]

#19093: threading._Event doesn't exist in python 3.3
---+--
 Reporter:  alex_po|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Python 3   |  Version:  master
 Severity:  Normal |   Resolution:  duplicate
 Keywords:  threading  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by aaugustin):

 * status:  new => closed
 * needs_better_patch:   => 0
 * resolution:   => duplicate
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 This is #19038.

-- 
Ticket URL: 
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] #15667: Implement template-based widget rendering

[Django]

#15667: Implement template-based widget rendering
+
 Reporter:  brutasse|Owner:  brutasse
 Type:  New feature |   Status:  new
Component:  Forms   |  Version:
 Severity:  Normal  |   Resolution:
 Keywords:  form-rendering  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  1
  Needs tests:  0   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+
Changes (by chronos):

 * cc: philipe.rp@… (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 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] #19093: threading._Event doesn't exist in python 3.3

[Django]

#19093: threading._Event doesn't exist in python 3.3
+---
 Reporter:  alex_po |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Python 3|Version:  master
 Severity:  Normal  |   Keywords:  threading
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+---
 I got this error when tried to launch django using python 3.3:

 {{{
 Traceback (most recent call last):
   File "/Users/developer/Development/Projects/python/django/django-
 trunk/django/core/management/base.py", line 222, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/Users/developer/Development/Projects/python/django/django-
 trunk/django/core/management/base.py", line 247, in execute
 translation.activate('en-us')
   File "/Users/developer/Development/Projects/python/django/django-
 trunk/django/utils/translation/__init__.py", line 90, in activate
 return _trans.activate(language)
   File "/Users/developer/Development/Projects/python/django/django-
 trunk/django/utils/translation/trans_real.py", line 181, in activate
 _active.value = translation(language)
   File "/Users/developer/Development/Projects/python/django/django-
 trunk/django/utils/translation/trans_real.py", line 170, in translation
 default_translation = _fetch(settings.LANGUAGE_CODE)
   File "/Users/developer/Development/Projects/python/django/django-
 trunk/django/utils/translation/trans_real.py", line 152, in _fetch
 app = import_module(appname)
   File "/Users/developer/Development/Projects/python/django/django-
 trunk/django/utils/importlib.py", line 35, in import_module
 __import__(name)
   File "/Users/developer/Development/Projects/python/django/django-
 trunk/django/contrib/admin/__init__.py", line 6, in 
 from django.contrib.admin.sites import AdminSite, site
   File "/Users/developer/Development/Projects/python/django/django-
 trunk/django/contrib/admin/sites.py", line 4, in 
 from django.contrib.admin.forms import AdminAuthenticationForm
   File "/Users/developer/Development/Projects/python/django/django-
 trunk/django/contrib/admin/forms.py", line 6, in 
 from django.contrib.auth.forms import AuthenticationForm
   File "/Users/developer/Development/Projects/python/django/django-
 trunk/django/contrib/auth/forms.py", line 14, in 
 from django.contrib.auth.models import User
   File "/Users/developer/Development/Projects/python/django/django-
 trunk/django/contrib/auth/models.py", line 18, in 
 from django.contrib.auth.hashers import (
   File "/Users/developer/Development/Projects/python/django/django-
 trunk/django/contrib/auth/hashers.py", line 8, in 
 from django.test.signals import setting_changed
   File "/Users/developer/Development/Projects/python/django/django-
 trunk/django/test/__init__.py", line 6, in 
 from django.test.testcases import (TestCase, TransactionTestCase,
   File "/Users/developer/Development/Projects/python/django/django-
 trunk/django/test/testcases.py", line 871, in 
 _ImprovedEvent = threading._Event
 AttributeError: 'module' object has no attribute '_Event'
 AttributeError: 'module' object has no attribute '_Event'
 }}}

-- 
Ticket URL: 
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] #16630: Support for HTML5 input types

[Django]

#16630: Support for HTML5 input types
-+-
 Reporter:  jonash   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  html5| 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 chronos):

 * cc: philipe.rp@… (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 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] #19092: formats.py for Lithuanian language

[Django]

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

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


Comment:

 Please also ask your language coordinator to confirm this 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 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] #10227: Support a related_default on OneToOne fields

[Django]

#10227: Support a related_default on OneToOne fields
-+-
 Reporter:  rvdrijst |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  onetoone related |  Needs documentation:  0
  expection null |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by olau):

 As much as I would love to see a A.objects.none_get() or perhaps a more
 Pythonic A.objects.getdefault(), IMHO that is orthogonal to this issue. I
 don't think your obj.nget('o2ofield') is intuitive.

 Regarding related_default: I just need None (that's why I proposed
 related_null), but you can conceivably do a lambda that makes sense, e.g.
 {{{
 class UserProfile(models.Model):
 user = models.OneToOneField(User, related_default=lambda u:
 UserProfile(user=u))
 ...

 if not request.user.profile.name:
 request.user.profile.name = ...
 request.user.profile.save()
 }}}
 And it is arguably relatively in line with the existing API, except the
 lambda must receive the instance which I don't believe it does for the
 ordinary default (without the instance, you can't set the one-to-one key
 to the original object and then it's really confusing :).

 I don't understand why you think it would be a problem to change the API
 based on a field setting. That's already happening with null and default
 today?

-- 
Ticket URL: 
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] #8413: Django doesn't reload itself after updating files on disk that raised error on import.

[Django]

#8413: Django doesn't reload itself after updating files on disk that raised 
error
on import.
-+-
 Reporter:  buriy|Owner:  buriy
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  autoreload reload|  Needs documentation:  0
  import error fix   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by anonymous):

 Damnit. Try again:


 {{{
 53a54
 > _error_files = []
 57c58
 < for filename in filter(lambda v: v, map(lambda m: getattr(m,
 "__file__", None), sys.modules.values())):
 ---
 > for filename in filter(lambda v: v, map(lambda m: getattr(m,
 "__file__", None), sys.modules.values())) + _error_files:
 72a74,76
 > try:
 > del _error_files[_error_files.index(filename)]
 > except ValueError: pass
 75a80,92
 > def check_errors(fn):
 > def wrapper(*args, **kwargs):
 > try:
 > fn(*args, **kwargs)
 > except (ImportError, IndentationError, NameError,
 > SyntaxError, TypeError), msg:
 > et, ev, tb = sys.exc_info()
 > if ev.filename not in _error_files:
 > _error_files.append(ev.filename)
 >
 > raise
 > return wrapper
 >
 144,145c161,162
 < reloader(main_func, args, kwargs)
 <
 ---
 > wrapped_main_func = check_errors(main_func)
 > reloader(wrapped_main_func, args, kwargs)

 }}}

-- 
Ticket URL: 
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] #8413: Django doesn't reload itself after updating files on disk that raised error on import.

[Django]

#8413: Django doesn't reload itself after updating files on disk that raised 
error
on import.
-+-
 Reporter:  buriy|Owner:  buriy
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  autoreload reload|  Needs documentation:  0
  import error fix   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by tdhutt@…):

 PS: Here is the patch, since apparently github doesn't let you download
 them. Tested on django 1.4.1. The relavent file is in (usually) in
 /usr/local/lib/python2.7/dist-packages/django/utils/autoreload.py so you
 can apply it like this:

 cd /usr/local/lib/python2.7/dist-packages/django/utils/autoreload.py
 sudo patch autoreload.py ~/autoreload_patch.diff

 where autoreload_patch.diff contains the following:

 53a54
 > _error_files = []
 57c58
 < for filename in filter(lambda v: v, map(lambda m: getattr(m,
 "__file__", None), sys.modules.values())):
 ---
 > for filename in filter(lambda v: v, map(lambda m: getattr(m,
 "__file__", None), sys.modules.values())) + _error_files:
 72a74,76
 > try:
 > del _error_files[_error_files.index(filename)]
 > except ValueError: pass
 75a80,92
 > def check_errors(fn):
 > def wrapper(*args, **kwargs):
 > try:
 > fn(*args, **kwargs)
 > except (ImportError, IndentationError, NameError,
 > SyntaxError, TypeError), msg:
 > et, ev, tb = sys.exc_info()
 > if ev.filename not in _error_files:
 > _error_files.append(ev.filename)
 >
 > raise
 > return wrapper
 >
 144,145c161,162
 < reloader(main_func, args, kwargs)
 <
 ---
 > wrapped_main_func = check_errors(main_func)
 > reloader(wrapped_main_func, args, kwargs)

-- 
Ticket URL: 
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] #8413: Django doesn't reload itself after updating files on disk that raised error on import.

[Django]

#8413: Django doesn't reload itself after updating files on disk that raised 
error
on import.
-+-
 Reporter:  buriy|Owner:  buriy
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  autoreload reload|  Needs documentation:  0
  import error fix   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by tdhutt@…):

 This is really annoying. I briefly tested ebas's patch and it seems to
 work. Can somebody please apply 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 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] #18153: Erorneous OneToOneField for instances that have pk unset

[Django]

#18153: Erorneous OneToOneField for instances that have pk unset
-+-
 Reporter:  jbzdak@… |Owner:  aaugustin
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * needs_better_patch:  0 => 1


Comment:

 {{{

 ==
 ERROR: test_o2o_cross_database_protection
 (regressiontests.multiple_database.tests.QueryTestCase)
 Operations that involve sharing FK objects across databases raise an error
 --
 Traceback (most recent call last):
   File
 
"/Users/aaugustin/Documents/dev/django/tests/regressiontests/multiple_database/tests.py",
 line 664, in test_o2o_cross_database_protection
 charlie.userprofile = bob_profile
   File
 "/Users/aaugustin/Documents/dev/django/django/db/models/fields/related.py",
 line 311, in __set__
 (value, self.related.opts.object_name))
 ValueError: Cannot assign "":
 "UserProfile" instance isn't saved in the database.

 --
 }}}

-- 
Ticket URL: 
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] #17867: validate_email fails with IDN domains

[Django]

#17867: validate_email fails with IDN domains
-+-
 Reporter:  Pierre   |Owner:  nobody
 |   Status:  closed
 Type:  Bug  |  Version:
Component:  Forms|  1.4-beta-1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  idn  | 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:"273b96ef9d3acb25d69e206555412774abab6022"]:
 {{{
 #!CommitTicketReference repository=""
 revision="273b96ef9d3acb25d69e206555412774abab6022"
 Fixed #17867 -- Made email validation pass with IDN domains

 Thanks Pierre Matri for the report and the initial patch.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] a8f888: Improved assertion error messages in validators te...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a8f888feb464afd7cfbe024242fa2a405a2d5f90
  
https://github.com/django/django/commit/a8f888feb464afd7cfbe024242fa2a405a2d5f90
  Author: Claude Paroz 
  Date:   2012-10-09 (Tue, 09 Oct 2012)

  Changed paths:
M tests/modeltests/validators/tests.py

  Log Message:
  ---
  Improved assertion error messages in validators tests


  Commit: 8cb9968a91cf533cb82e1e13948551e91b510878
  
https://github.com/django/django/commit/8cb9968a91cf533cb82e1e13948551e91b510878
  Author: Claude Paroz 
  Date:   2012-10-09 (Tue, 09 Oct 2012)

  Changed paths:
M tests/modeltests/validators/tests.py
M tests/regressiontests/forms/tests/fields.py

  Log Message:
  ---
  Moved some email validation tests to validators tests


  Commit: 273b96ef9d3acb25d69e206555412774abab6022
  
https://github.com/django/django/commit/273b96ef9d3acb25d69e206555412774abab6022
  Author: Claude Paroz 
  Date:   2012-10-09 (Tue, 09 Oct 2012)

  Changed paths:
M django/core/validators.py
M tests/modeltests/validators/tests.py

  Log Message:
  ---
  Fixed #17867 -- Made email validation pass with IDN domains

Thanks Pierre Matri for the report and the initial patch.


Compare: https://github.com/django/django/compare/9a2bceed1aab...273b96ef9d3a

-- 
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] #19092: formats.py for Lithuanian language

[Django]

#19092: formats.py for Lithuanian language
--+
 Reporter:  skirsdeda |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Translations  |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+
 Current formats.py for Lithuanian (lt) doesn't adhere to official formats
 used in language.
 Provided is a patch to fix this.
 Note that in DATE_FORMAT and DATETIME_FORMAT "E" is used (alternative
 month translation in translation files), however current Lithuanian
 translations for alternative month names are incorrect (e.g. "January"
 should be "Sausio" instead of "Sausis" when used in long date format). I
 intend to fix that through Transifex as soon as I get confirmed as team
 member.

-- 
Ticket URL: 
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] #18153: Erorneous OneToOneField for instances that have pk unset

[Django]

#18153: Erorneous OneToOneField for instances that have pk unset
-+-
 Reporter:  jbzdak@… |Owner:  aaugustin
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


-- 
Ticket URL: 
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] #18153: Erorneous OneToOneField for instances that have pk unset

[Django]

#18153: Erorneous OneToOneField for instances that have pk unset
-+-
 Reporter:  jbzdak@… |Owner:  dhatch
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by aaugustin):

 The first version of the patch deals with getting the reverse related
 object.

 The second version of the patch also deals with setting it. A similar bug
 existed.

-- 
Ticket URL: 
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] #10227: Support a related_default on OneToOne fields

[Django]

#10227: Support a related_default on OneToOne fields
-+-
 Reporter:  rvdrijst |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  onetoone related |  Needs documentation:  0
  expection null |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by akaariai):

 The problem is that changing reverse o2o field handling will break
 existing code. The API might not be ideal, but that is what we got.

 Adding a related_default argument doesn't seem like a nice solution to me.
 Specifically, if the related_default can be anything else than None it
 will lead to surprising situations. Also, having the API of obj.o2ofield
 change based on field setting could be somewhat annoying...

 I would love to have a more generic approach to this, something like a
 "nget()" method which returns None if no objects found. We could hook this
 into the fields by:
 {{{
 # works like obj.o2ofield except no DoesNotExist...
 obj.nget('o2ofield')
 # Could also be used as
 Code.objects.nget(type='imei', value='bar')
 }}}

 This is nicer to write than:
 {{{
 try:
res = obj.o2ofield
 except obj.DoesNotExist:
res = None
 }}}

 To me this seems like an explicit and easy to implement approach. Does
 this approach seem workable to others? If not, IMO we should just wontfix
 this issue, as I don't see any nice way to change the API without breaking
 existing code.

-- 
Ticket URL: 
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] #18153: Erorneous OneToOneField for instances that have pk unset

[Django]

#18153: Erorneous OneToOneField for instances that have pk unset
-+-
 Reporter:  jbzdak@… |Owner:  dhatch
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by akaariai):

 Looks like a good approach to me.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #10227: Support a related_default on OneToOne fields (was: OneToOne fields with null=True raise DoesNotExist exception on related model)

[Django]

#10227: Support a related_default on OneToOne fields
-+-
 Reporter:  rvdrijst |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  onetoone related |  Needs documentation:  0
  expection null |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by aaugustin):

 This problem was discussed again in #18153. I still believe that Luke's
 comment 13 nails it.

 I'm updating the title to better reflect the design decision.

-- 
Ticket URL: 
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] #18153: Erorneous OneToOneField for instances that have pk unset

[Django]

#18153: Erorneous OneToOneField for instances that have pk unset
-+-
 Reporter:  jbzdak@… |Owner:  dhatch
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by aaugustin):

 (1) I agree with Andrew that !SingleRelatedObjectDescriptor should return
 an error in this case, and it's what I've implemented in the patch I
 attached to #19089.

 (2) The asymmetry between forwards relations and backwards relations
 exists on purpose. The underlying relation in the database is asymmetric.
 So, at first sight, I disagree with the `and not self.related.field.null`
 part.

 I'm willing to reconsider (2), which is tracked in #10227. We can continue
 that part of the discussion over there.

 But I think we can fix (1), which is an obvious bug, without waiting for
 the decision on (2).

 Since I independently wrote the same patch as dhatch, it's probably a
 reasonable solution. I plan combine both patches — mine doesn't break on
 legit values of `pk` such as `''` or `0`, dhaty's has more tests — and
 commit the result soon.

-- 
Ticket URL: 
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] #18153: Erorneous OneToOneField for instances that have pk unset

[Django]

#18153: Erorneous OneToOneField for instances that have pk unset
-+-
 Reporter:  jbzdak@… |Owner:  dhatch
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by aaugustin):

 #19089 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 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] #361: Some Basic Math Filters

[Django]

#361: Some Basic Math Filters
-+--
 Reporter:  ilikeprivacy@…   |Owner:  adrian
 Type:  defect   |   Status:  closed
Component:  Template system  |  Version:
 Severity:  normal   |   Resolution:  wontfix
 Keywords:  filter math  | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by will@…):

 I would like to have a "subtract" filter for this use case:
 I want to only show the first 10 items in a list, then have a final line
 saying how many other items there were,
 E.g.
 "And 3 other items..."

 This is purely a display (template) logic, so it should be supported by
 the template language (same as 'add').

 {{{
 {% for l in list_items %}
 {% if forloop.counter < 10 %}
 l 
 {% else %}
 {% ifequal forloop.counter 10 %}
 
 And {{ list_items|length|subtract:10 }} other objects...
 
 {% endifequal %}
 {% endif %}
 {% endfor %}
 }}}

-- 
Ticket URL: 
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] #18758: non-DRY e-mail regex

[Django]

#18758: non-DRY e-mail regex
--+
 Reporter:  yedpodtrzitko |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Uncategorized |  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:  1 |UI/UX:  0
--+
Changes (by claudep):

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


-- 
Ticket URL: 
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] #19091: NoReverseMatch template errors are impossible to debug

[Django]

#19091: NoReverseMatch template errors are impossible to debug
--+
 Reporter:  alper |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Core (URLs)   |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  1
--+
 I've been using django for ages and I'd never really used {% url %} before
 and now I know why. First the transition to 1.5 URL names' and the rest of
 the documentation is a bit of a mess, but that is not what this bug is
 about.

 If your URL tag can't find something useful this is the error message you
 receive:

 NoReverseMatch at /
 Reverse for 'topic_detail' with arguments '(2, u'professor-wever')' and
 keyword arguments '{}' not found.

 (Full paste log attached.)


 For somebody not wholly familiar with this system this error message which
 only outputs  a traceback from the template renderer this error message is
 not very helpful. Could this be improved? (Not for me I've learnt my
 lesson, but I imagine this is going to cause tons of frustration to any
 new learners.)






 Environment:


 Request Method: GET
 Request URL: http://127.0.0.1:8000/

 Django Version: 1.4
 Python Version: 2.7.1
 Installed Applications:
 ('django.contrib.auth',
  'django.contrib.contenttypes',
  'django.contrib.sessions',
  'django.contrib.sites',
  'django.contrib.messages',
  'django.contrib.staticfiles',
  'south',
  'boogie',
  'django.contrib.admin')
 Installed Middleware:
 ('django.middleware.common.CommonMiddleware',
  'django.contrib.sessions.middleware.SessionMiddleware',
  'django.middleware.csrf.CsrfViewMiddleware',
  'django.contrib.auth.middleware.AuthenticationMiddleware',
  'django.contrib.messages.middleware.MessageMiddleware')


 Template error:
 In template
 /Users/alper/Documents/projects/sake/victory/templates/boogie/index.html,
 error at line 8
Reverse for 'topic_detail' with arguments '(2, u'professor-wever')' and
 keyword arguments '{}' not found.
1 : {% extends "base.html" %}


2 : {% load url from future %}


3 :


4 : {% block content %}


5 : Frontpage


6 :


7 : {% for topic in topics %}


8 : Onderwerp: {{ topic.title }}


9 : {% endfor %}


10 :


11 : Bijdragen


12 :


13 : {% for piece in pieces %}


14 : {{ piece.text }}


15 : {% endfor %}


16 :


17 : {% endblock %}

 Traceback:
 File "/Users/alper/Documents/projects/sake/victory/venv/lib/python2.7
 /site-packages/django/core/handlers/base.py" in get_response
   111. response = callback(request,
 *callback_args, **callback_kwargs)
 File "/Users/alper/Documents/projects/sake/victory/boogie/views.py" in
 index
   20. return HttpResponse(t.render(c))
 File "/Users/alper/Documents/projects/sake/victory/venv/lib/python2.7
 /site-packages/django/template/base.py" in render
   140. return self._render(context)
 File "/Users/alper/Documents/projects/sake/victory/venv/lib/python2.7
 /site-packages/django/template/base.py" in _render
   134. return self.nodelist.render(context)
 File "/Users/alper/Documents/projects/sake/victory/venv/lib/python2.7
 /site-packages/django/template/base.py" in render
   823. bit = self.render_node(node, context)
 File "/Users/alper/Documents/projects/sake/victory/venv/lib/python2.7
 /site-packages/django/template/debug.py" in render_node
   74. return node.render(context)
 File "/Users/alper/Documents/projects/sake/victory/venv/lib/python2.7
 /site-packages/django/template/loader_tags.py" in render
   123. return compiled_parent._render(context)
 File "/Users/alper/Documents/projects/sake/victory/venv/lib/python2.7
 /site-packages/django/template/base.py" in _render
   134. return self.nodelist.render(context)
 File "/Users/alper/Documents/projects/sake/victory/venv/lib/python2.7
 /site-packages/django/template/base.py" in render
   823. bit = self.render_node(node, context)
 File "/Users/alper/Documents/projects/sake/victory/venv/lib/python2.7
 /site-packages/django/template/debug.py" in render_node
   74. return node.render(context)
 File "/Users/alper/Documents/projects/sake/victory/venv/lib/python2.7
 /site-packages/django/template/loader_tags.py" in render
   62. result = block.nodelist.render(context)
 File "/Users/alper/Documents/projects/sake/victory/venv/lib/python2.7
 /site-packages/django/template/base.py" in render
   823. bit = self.render_node(node, context)
 File "/Users/alper/Documents/projects/sake/victory/venv/lib/python2.7
 /site-packages/django/template/debug.py" in render_node
   74. return node.r

Re: [Django] #18758: non-DRY e-mail regex

[Django]

#18758: non-DRY e-mail regex
--+
 Reporter:  yedpodtrzitko |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Uncategorized |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by yedpodtrzitko):

 This ticket can be closed now (fixed in #3011).

-- 
Ticket URL: 
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] #14497: ModelAdmin.readonly_fields isn't graceful with filefields.

[Django]

#14497: ModelAdmin.readonly_fields isn't graceful with filefields.
-+-
 Reporter:  Keryn Knight |Owner:
|  paulcollins
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  1.2
 Severity:  Normal   |   Resolution:
 Keywords:  feature admin| Triage Stage:  Design
  readonly filefield |  decision needed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-

Comment (by anonymous):

 +1!
 Really want to have this feature available!

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #19087: Annotate() followed by exclude() raises an exception

[Django]

#19087: Annotate() followed by exclude() raises an exception
-+-
 Reporter:  ivan_virabyan|Owner:  akaariai
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by ivan_virabyan):

 works great, 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 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] #14497: ModelAdmin.readonly_fields isn't graceful with filefields.

[Django]

#14497: ModelAdmin.readonly_fields isn't graceful with filefields.
-+-
 Reporter:  Keryn Knight |Owner:
|  paulcollins
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  1.2
 Severity:  Normal   |   Resolution:
 Keywords:  feature admin| Triage Stage:  Design
  readonly filefield |  decision needed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-

Comment (by zout):

 +1
 Weird it isn't there, please include this in the next minor release

-- 
Ticket URL: 
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] #19089: Incorrect reverse one-to-one lookup on unsaved objects

[Django]

#19089: Incorrect reverse one-to-one lookup on unsaved objects
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * status:  new => closed
 * needs_docs:   => 0
 * resolution:   => duplicate
 * needs_tests:   => 0
 * needs_better_patch:   => 0


Comment:

 This is duplicate of #18153 (thanks Ramiro).

-- 
Ticket URL: 
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.