Re: [Django] #16891: [patch] queryset delete should return number of rows matched

[Django]

#16891: [patch] queryset delete should return number of rows matched
-+-
 Reporter:  estebistec   |Owner:
 Type:  New feature  |  estebistec
Component:  Database layer   |   Status:  new
  (models, ORM)  |  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by estebistec):

 * needs_better_patch:  1 => 0


Comment:

 The ambiguity discussed in #17435 doesn't apply to deletes. The number of
 rows matched and affected can't differ, as a match always leads to a
 delete. So I think the existing patch is fine in this respect.

 Are there any other improvements needed in this patch? It doesn't look
 like the objects at this level are generally tested in the Django test-
 suite. On the one hand, more tests are always good. On the other, the
 delete queries aren't part of Django's published object model (for me,
 they're an implementation detail change along the way to ticket #16549).

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17449: [patch] Default OPTIONS implementation in base View class

[Django]

#17449: [patch] Default OPTIONS implementation in base View class
---+--
 Reporter:  estebistec |Owner:  estebistec
 Type:  New feature|   Status:  new
Component:  Generic views  |  Version:  1.3
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by estebistec):

 * needs_better_patch:  1 => 0


Comment:

 Ready to go.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16108: File removal race condition in FileSystemStorage

[Django]

#16108: File removal race condition in FileSystemStorage
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  File |  Version:  1.3
  uploads/storage|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  FileSystemStorage|  checkin
  file deletion race condition   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by daniel@…):

 +1 for getting this into 1.3.2. I've also seen this in production with
 django_compressor.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17771: weird problem db with autocommit

[Django]

#17771: weird problem db with autocommit
-+-
 Reporter:  meister  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:  wontfix
 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 meister ):

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


Comment:

 Replying to [comment:3 meister ]:
 > Replying to [comment:2 akaariai]:
 > > The problem seems to be that you are running in a transaction with
 repeatable read semantics. I don't think Django supports autocommit for
 MySQL.
 >
 > It doesn't explain why my code works on some environments and do not
 work on others...

 It works when using MyISAM and creates some problem with InnoDB. My
 problem is explained in http://groups.google.com/group/django-
 users/msg/55fa3724d2754013?pli=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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17771: weird problem db with autocommit

[Django]

#17771: weird problem db with autocommit
-+-
 Reporter:  meister  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 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
-+-

Comment (by meister ):

 Replying to [comment:2 akaariai]:
 > The problem seems to be that you are running in a transaction with
 repeatable read semantics. I don't think Django supports autocommit for
 MySQL.

 It doesn't explain why my code works on some environments and do not work
 on others...

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17771: weird problem db with autocommit

[Django]

#17771: weird problem db with autocommit
-+-
 Reporter:  meister  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 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
-+-

Comment (by akaariai):

 The problem seems to be that you are running in a transaction with
 repeatable read semantics. I don't think Django supports autocommit for
 MySQL.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17772: Release Notes 1.4: typo implicitely (was: Docs: 1.4 release notes typo.)

[Django]

#17772: Release Notes 1.4: typo implicitely
+--
 Reporter:  blanchard.jeremy@…  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Documentation   |  Version:  1.4-beta-1
 Severity:  Normal  |   Resolution:
 Keywords:  docs,   | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--
Changes (by anonymous):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #17772: Docs: 1.4 release notes typo.

[Django]

#17772: Docs: 1.4 release notes typo.
+
 Reporter:  blanchard.jeremy@…  |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Documentation   |Version:  1.4-beta-1
 Severity:  Normal  |   Keywords:  docs,
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  1   |  UI/UX:  0
+
 From the 1.4 release notes:

 https://docs.djangoproject.com/en/dev/releases/1.4-beta-1/#backwards-
 incompatible-changes-in-1-4

 If you're implicitely relying on the path of the admin static files on
 your server's file system when you deploy your site, you have to update
 that path. The files were moved from django/contrib/admin/media/ to
 django/contrib/admin/static/admin/.

 "implicitely" should be "implicitly"

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16933: Make it more obvious on screen which version of the doc is being viewed

[Django]

#16933: Make it more obvious on screen which version of the doc is being viewed
-+-
 Reporter:  julien   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.3
Component:  Djangoproject.com|   Resolution:  fixed
  Web site   | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  1
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by RobBednark):

 Although this was implemented, I didn't see it and spent 4 hours figuring
 out why the tutorial code wasn't working for me (I was using Django 1.3.1
 but looking at the tutorial for the dev version).  In case someone else
 comes across this, here's a screenshot showing the little green box with
 the version, which you can click on to select a different version:

 
[[Image(https://lh5.googleusercontent.com/-xocmKv68DGk/T0lYF92MVMI/GkE/mdqRxYhJFR8/s512/django%2520screenshot%2520with%2520markup.png)]]

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17771: weird problem db with autocommit

[Django]

#17771: weird problem db with autocommit
-+-
 Reporter:  meister  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 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 meister ):

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


Comment:

 A easier way to reproduce it :
 {{{
 $ ./manage.py shell
 >>> from django.contrib.auth.models import User
 >>> print User.objects.get(pk=1).first_name
 aaa
 # on the mysql server :
 update auth_user set first_name = "ooo" where id=1;
 # back in the django shell :
 >>> print User.objects.get(pk=1).first_name
 }}}
 aaa

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #17771: weird problem db with autocommit

[Django]

#17771: weird problem db with autocommit
--+
 Reporter:  meister   |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.3
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Hello,

 Here is problematic code (standard django setup, mysql backend):

 {{{
 import time

 import os, sys, re
 sys.path.append(os.path.abspath(os.path.dirname(__file__))+'/..')
 os.environ['DJANGO_SETTINGS_MODULE'] = 'settings'

 from django.conf import settings

 from django.contrib.auth.models import User

 #from django.db import connection
 #cursor = connection.cursor()
 #cursor.execute('SET autocommit = 1')

 while True:
 u = User.objects.get(pk=1)
 print u.first_name
 time.sleep(1)
 }}}

 It displays user first_name each second. On the other hand with mysql
 client :
 {{{
 $ update auth_user set first_name = "foo" where id=1;
 }}}
 Value does not update in my loop (wireshark shows the old value too in the
 mysql packets dumped). If I restart the process, it fetch the correct new
 value.
 I can fix the problem by adding the 3 autocommit lines commented out.

 Problem do not occur on my ubuntu 32b desktop (32bits django 1.3.1 /
 MySQL-python 1.2.3, mysql 5.1.58) nor a debian squeeze server (32bits
 mysql 5.1.49).

 Problem occurs on a 64 bits debian squeeze server (64bits mysql 5.1.49)
 and a ubuntu 64 server (64 bits mysql 5.1.41).

 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17449: [patch] Default OPTIONS implementation in base View class (was: [patch] Default OPTIONS and improved HEAD in base View class)

[Django]

#17449: [patch] Default OPTIONS implementation in base View class
---+--
 Reporter:  estebistec |Owner:  estebistec
 Type:  New feature|   Status:  new
Component:  Generic views  |  Version:  1.3
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by estebistec):

 Removing mention of HEAD bug in summary now that it's fixed per r17545.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #11150: ImageField validation depend on cStringIO

[Django]

#11150: ImageField validation depend on cStringIO
+
 Reporter:  vvd |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Forms   |  Version:  SVN
 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):

 * needs_tests:  1 => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17729: regression in django-admin: list_editable doesn't work when pagination

[Django]

#17729: regression in django-admin: list_editable doesn't work when pagination
-+---
 Reporter:  Velmont  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.4-alpha-1
 Severity:  Release blocker  |   Resolution:  duplicate
 Keywords:  regression   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+---

Comment (by julien):

 Oops, that was 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17198: In admin results can be omitted due to pagination and inadequate ordering clauses

[Django]

#17198: In admin results can be omitted due to pagination and inadequate 
ordering
clauses
---+
 Reporter:  lukeplant  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by julien):

 Oops, that was 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16819: list_editable breaks multipage changelists

[Django]

#16819: list_editable breaks multipage changelists
-+
 Reporter:  anossov@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  SVN
 Severity:  Release blocker  |   Resolution:
 Keywords:  admin list_editable  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by julien):

 Oops, that was 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17764: Documentation out-of-date: django.contrib.auth.utils no longer exists.

[Django]

#17764: Documentation out-of-date: django.contrib.auth.utils no longer exists.
-+-
 Reporter:  mbt  |Owner:  mbt
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:
 Severity:  Release blocker  |  1.4-beta-1
 Keywords:  authentication   |   Resolution:
  documentation  easy-pickings   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by mbt):

 I have also added the commits as individual patch files here, in the event
 that someone wants to incorporate them into SVN directly (I don’t know for
 sure which tool Django is using as its primary, so I am doing it both
 ways).

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17764: Documentation out-of-date: django.contrib.auth.utils no longer exists.

[Django]

#17764: Documentation out-of-date: django.contrib.auth.utils no longer exists.
-+-
 Reporter:  mbt  |Owner:  mbt
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:
 Severity:  Release blocker  |  1.4-beta-1
 Keywords:  authentication   |   Resolution:
  documentation  easy-pickings   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by mbt):

 * has_patch:  0 => 1


Comment:

 I have a pull request on GitHub:

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

 This update to the documentation fixes the problem reported in this ticket
 as well as one other minor problem (lacking a "new in..." notification
 around before one of the functions).  Someone who has the ability to get
 this merged in should be able to do so at this point.  Please let me know,
 of course, if there are any problems that need addressed, but the patch is
 relatively simple and straightforward, so I do not expect that to happen
 unless I did something blatantly wrong.  :-)

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17770: Tutorial should read "from django.conf.urls.defaults import..."

[Django]

#17770: Tutorial should read "from django.conf.urls.defaults import..."
---+--
 Reporter:  RobBednark |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.3
 Severity:  Normal |   Resolution:  duplicate
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by Alex):

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


Comment:

 Dupe of #16932, you're using the docs for the wrong version of Django.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #17770: Tutorial should read "from django.conf.urls.defaults import..."

[Django]

#17770: Tutorial should read "from django.conf.urls.defaults import..."
---+
 Reporter:  RobBednark |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  1.3
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 The tutorial incorrectly specifies:

 {{{
 from django.conf.urls import ...
 }}}
 when it should be specifying:

 {{{
 from django.conf.urls.defaults import ...
 }}}


 Tutorial 2 - 1 occurrence[[BR]]
 Tutorial 3 - 4 occurrences[[BR]]
 Tutorial 4 - 3 occurrences[[BR]]

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17198: In admin results can be omitted due to pagination and inadequate ordering clauses

[Django]

#17198: In admin results can be omitted due to pagination and inadequate 
ordering
clauses
---+
 Reporter:  lukeplant  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by anonymous):

 Using a deterministic order is certainly more important than potential
 performance issues. According to akaariai's benchmark results, those
 performance issues don't seem significant in Postgres anyway. It'd be
 worth checking with MySQL/Oracle though.

 The fix should probably be done at the end of `ChangeList.get_ordering()`.
 'pk' should be appended to the list of ordering fields, unless that list
 already contains 'pk', '-pk' or the explicit primary key field (both ASC
 and DESC).

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16819: list_editable breaks multipage changelists

[Django]

#16819: list_editable breaks multipage changelists
-+
 Reporter:  anossov@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  SVN
 Severity:  Release blocker  |   Resolution:
 Keywords:  admin list_editable  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by anonymous):

 * severity:  Normal => Release blocker


Comment:

 #17729 was closed as a duplicate. Marking as release blocker since it
 actually is a regression in 1.4.

 However, I tend to think that this ticket should also be closed as a
 duplicate of #17198, which tackles the ordering issue more broadly (i.e.
 not just where `list_editable` is involved).

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17729: regression in django-admin: list_editable doesn't work when pagination

[Django]

#17729: regression in django-admin: list_editable doesn't work when pagination
-+---
 Reporter:  Velmont  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.4-alpha-1
 Severity:  Release blocker  |   Resolution:  duplicate
 Keywords:  regression   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+---
Changes (by anonymous):

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


Comment:

 This was actually already reported in #16819.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #56: MySQL id columns should be UNSIGNED

[Django]

#56: MySQL id columns should be UNSIGNED
-+-
 Reporter:  Manuzhai |Owner:
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  SVN
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  mysql|  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by pzinovkin):

 * stage:  Design decision needed => Accepted


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

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

Re: [Django] #56: MySQL id columns should be UNSIGNED

[Django]

#56: MySQL id columns should be UNSIGNED
-+-
 Reporter:  Manuzhai |Owner:
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  SVN
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:  mysql|  decision needed
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by pzinovkin):

 * needs_better_patch:  1 => 0
 * stage:  Accepted => Design decision needed


Comment:

 Submitted patch with unsigned option for AutoField.
 Patch includes rel_db_type_cleanup.diff from #13774

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17764: Documentation out-of-date: django.contrib.auth.utils no longer exists.

[Django]

#17764: Documentation out-of-date: django.contrib.auth.utils no longer exists.
-+-
 Reporter:  mbt  |Owner:  mbt
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:
 Severity:  Release blocker  |  1.4-beta-1
 Keywords:  authentication   |   Resolution:
  documentation  easy-pickings   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by mbt):

 * status:  new => assigned
 * cc: mbt@… (added)
 * owner:  nobody => mbt


Comment:

 I am working on it now and should have a patch for the documentation ready
 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #17769: RTL from in admin panel css

[Django]

#17769: RTL from in admin panel css
--+
 Reporter:  shark4313@…   |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  contrib.auth  |Version:  1.3
 Severity:  Normal|   Keywords:  rtl
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 RTL form in admin panel didn't apply rtl.css code as it is overridden by
 Form.css code

 I  solved this by putting '''important''' to
 .aligned label at line 157 in rtl.css as below :

 .aligned label{
 padding: 0 0 3px 1em;
 float: right  !important;
 }

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17762: Multi-db apps (no Django test suite) testing fails to create in-memory sqlite DBs

[Django]

#17762: Multi-db apps (no Django test suite) testing fails to create in-memory
sqlite DBs
-+-
 Reporter:  agriffis |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by ramiro):

 Sorry, I can't reproduce this, my previous attempt failed because it
 wasn't correctly set up.

 This is how I tested:

 1. Created a project.
 2. Added an application by simply the
 `tests/regressiontests/multiple_database` Django trunk regression test
 (here I'm trusting it to assure us multi-DB functionality is effectively
 working) to a `mdb` application directory and adding it to the
 INSTALLED_APPS setting.

This means some 'multiple_database' -> 'mdb' replacements must be made
 in the app files:
 {{{
 $ cd mdb
 $ ack -l multiple_database --type-set json=.json --py --json |xargs sed -i
 s/multiple_database/mdb/g
 }}}
 3. Edited the DATABASES setting to look like this:
 {{{
 DATABASES = {
 'default': {
 'ENGINE': 'django.db.backends.sqlite3',
 'NAME': 'data.db',
 },
 'other': {
 'ENGINE': 'django.db.backends.sqlite3',
 #'TEST_NAME': ':memory:',
 }
 }
 }}}

 4. Now I can run the tests for the 'mdb' app and they run without
 failures:
 {{{
 /manage.py test -v2 mdb
 Creating test database for alias 'default' (':memory:')...
 [...]
 Creating test database for alias 'other' (':memory:')...
 [...many lines of tests output...]
 --
 Ran 51 tests in 1.099s

 OK
 Destroying test database for alias 'default' (':memory:')...
 Destroying test database for alias 'other' (':memory:')...
 }}}
Note how with verbosity=2 the test runner reports the names of the test
 DBs it is creating/destroying.

 5. I tested this with: 1.3, 1.3.1, current 1.3.X branch tip and trunk,
 always with the same results.

 Could you give us more details how are you getting the ''"Django fails to
 create multiple in-memory SQLite databases, instead it creates only one
 (which is populated only with the table definitions for the default DB)"''
 failure you describe so others can reproduce 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17762: Multi-db apps (no Django test suite) testing fails to create in-memory sqlite DBs

[Django]

#17762: Multi-db apps (no Django test suite) testing fails to create in-memory
sqlite DBs
-+-
 Reporter:  agriffis |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by lrekucki):

 Actually, see #17758 how to reproduce this with Django's test suite.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17762: Multi-db apps (no Django test suite) testing fails to create in-memory sqlite DBs (was: Multi-db testing fails to create multiple databases)

[Django]

#17762: Multi-db apps (no Django test suite) testing fails to create in-memory
sqlite DBs
-+-
 Reporter:  agriffis |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by ramiro):

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


Comment:

 I can reproduce the reported problem with tests of an standalone app that
 uses multiple database (the problem doesn't happen with Django's own test
 suite).

 The patch doesn't seem to make any sense, though.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17761: save_base() does not properly detect when MTI parent key is unset

[Django]

#17761: save_base() does not properly detect when MTI parent key is unset
-+-
 Reporter:  agriffis |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by ramiro):

 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #17761: save_base() does not properly detect when MTI parent key is unset

[Django]

#17761: save_base() does not properly detect when MTI parent key is unset
-+-
 Reporter:  agriffis |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by ramiro):

 * needs_tests:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #17768: Explain the expected failure on UpdateViewTests.test_update_put

[Django]

#17768: Explain the expected failure on UpdateViewTests.test_update_put
--+
 Reporter:  claudep   |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Generic views |Version:  SVN
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  1 |  UI/UX:  0
--+
 Attached patch is only adding comments so the @expectedFailure decorator
 is given some more explanations.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17759: FormMixin instantiates form with dict stored on the class

[Django]

#17759: FormMixin instantiates form with dict stored on the class
---+
 Reporter:  agriffis   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Generic views  |  Version:  1.3
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by claudep):

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


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

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

[Changeset] r17587 - django/branches/releases/1.3.X/docs/topics/i18n

[noreply]

Author: timo
Date: 2012-02-25 04:55:41 -0800 (Sat, 25 Feb 2012)
New Revision: 17587

Modified:
   django/branches/releases/1.3.X/docs/topics/i18n/index.txt
Log:
[1.3.X] Fixed #17743 - Typo in topics/i18n/index.txt

Modified: django/branches/releases/1.3.X/docs/topics/i18n/index.txt
===
--- django/branches/releases/1.3.X/docs/topics/i18n/index.txt   2012-02-24 
23:24:30 UTC (rev 17586)
+++ django/branches/releases/1.3.X/docs/topics/i18n/index.txt   2012-02-25 
12:55:41 UTC (rev 17587)
@@ -45,7 +45,7 @@
 Glossary
 
 
-First lets define some terms that will help us to handle a common language:
+First let's define some terms that will help us to handle a common language:
 
 .. glossary::
 

-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17743: Punctuation Error on Internationalization Page

[Django]

#17743: Punctuation Error on Internationalization Page
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  closed
Component:  Documentation  |Version:  1.3
 Severity:  Normal | Resolution:  fixed
 Keywords:  punctuation|   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  1
UI/UX:  0  |
---+
Changes (by timo):

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


Comment:

 In [17587]:
 {{{
 #!CommitTicketReference repository="" revision="17587"
 [1.3.X] Fixed #17743 - Typo in topics/i18n/index.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 this group at 
http://groups.google.com/group/django-updates?hl=en.

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

[Django]

#17758: Do not depend on dict order in test suite
-+
 Reporter:  lrekucki |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  1.3
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by claudep):

 Note that #17762 addresses the issue about test_db_signature when NAME is
 empty or ":memory:".

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17754: Django GIS Measure refactor

[Django]

#17754: Django GIS Measure refactor
--+
 Reporter:  riccardodivirgilio|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  GIS   |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by riccardodivirgilio):

 maybe it would be useful to use number_format when calling string, to easy
 use the class in django templates and i18n format number

 def __str__(self):
 return '%s %s' % (number_format(getattr(self,
 self._default_unit)), self._default_unit)

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

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

[Django]

#17758: Do not depend on dict order in test suite
-+
 Reporter:  lrekucki |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  1.3
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by lrekucki):

 OK, I found 2 major bugs so far:

 1) {{{django.test.simple.dependency_order()}}}

 There are two problems here:

 a) The result of this functions depends on the order of aliases for given
 DB signature (which in turn depends on the order in settings.DATABASES
 dict) - i.e. if you have a DB with aliases {{{["A", "B"]}}} and "A"
 depends on "B" then it will raise an error. If the alias list is ["B",
 "A"] it will pass (I think it should always fail, right?).

 b) The way setup_databases() in the runner treat databases with no
 {{{NAME}}} - they get the same signature. There's a special case later to
 fix this, but it messes up dependency_order(). In particular, the Django
 test suite has two DBs: "default" and "other". If they're assigned the
 same test_signature, they're treated as aliases (which isn't correct). As
 documented, the "other" database has an implicit dependency on "default"
 because we gave no explicit {{{TEST_DEPENDENCIES}}}. And that's how we
 arrive at a).

 So right now, you have about 50% chance of even running the test suite ;)
 I don't have a patch for a general case yet. ATM, I modified the backend
 code to return NaN instead of empty string for databases with no
 {{{NAME}}}, which prevents them from being aliases. This should also be
 the case for SQLite databases where {{{NAME == ":memory:"}}}. And of
 course, {{{dependency_order()}}} needs fixing.

 2) An ORM bug

 {{{
 FAIL: test_tickets_8921_9188 (regressiontests.queries.tests.Queries6Tests)
 --
 Traceback (most recent call last):
   File
 "/home/lrekucki/django/django_lqc/tests/regressiontests/queries/tests.py",
 line 1443, in test_tickets_8921_9188
 ['', '', '']
   File "/home/lrekucki/django/django_lqc/django/test/testcases.py", line
 774, in assertQuerysetEqual
 return self.assertEqual(map(transform, qs), values)
 AssertionError: Lists differ: ['', ''] != ['',
 '', 'https://code.djangoproject.com/ticket/17758#comment:2>
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17754: Django GIS Measure refactor

[Django]

#17754: Django GIS Measure refactor
--+
 Reporter:  riccardodivirgilio|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  GIS   |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by riccardodivirgilio):

 sorry i've done a mess with attachments...

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17754: Django GIS Measure refactor

[Django]

#17754: Django GIS Measure refactor
--+
 Reporter:  riccardodivirgilio|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  GIS   |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by riccardodivirgilio):

 Improvements are:

 1: class names are printed in exceptions
 2: div and mul with distance retruns correct instances of other classes
 (example 3m * 3m = 3sq_m
 3: div with two instances of same class returns a number (example: 3m / 3m
 = 1)

 feel free to choose the correct prefix for volume API, just change the
 string in the code.

 todo: remove tests at the end.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17754: Django GIS Measure refactor

[Django]

#17754: Django GIS Measure refactor
--+
 Reporter:  riccardodivirgilio|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  GIS   |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by riccardodivirgilio):

 i've attached a new measure.py, with tests at the end.

 just lunch python measure.2.py to test it

 there is also the new diff file in unified format.

 i've created also a Weight class to see how much it's easy to create a new
 measure class,

 maybe it would be useful for developers to include a weight class
 somewhere in django

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17767: add signed cookie session backed to session engine settings docs

[Django]

#17767: add signed cookie session backed to session engine settings docs
-+-
 Reporter:  ptone|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by claudep):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Ready for checkin
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 This is a missing bit from r16466 (#16199).

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17766: Clarify impact of HttpOnly flag for JS access to session cookie

[Django]

#17766: Clarify impact of HttpOnly flag for JS access to session cookie
-+-
 Reporter:  ptone|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  SVN
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Ready for checkin
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 For reference, the original ticket that produced the change is #16847.

 The location of this paragraph has moved meanwhile, but the patch is still
 applicable.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.