Re: [Django] #18881: tag "trans" not working with "context"

[Django]

#18881: tag "trans" not working with "context"
+--
 Reporter:  lanyjie |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Template system |  Version:  1.4
 Severity:  Normal  |   Resolution:
 Keywords:  trans context i18n  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by lanyjie):

 @julien: I looked at that code and it seems we can do the following with
 the testempt.html:
 {{{
 def test_template_message_context_extractor(self):
 """
 Ensure that message contexts are correctly extracted for the
 {% trans %} and {% blocktrans %} template tags.
 Refs #14806.
 """
 os.chdir(self.test_dir)
 management.call_command('makemessages', locale=LOCALE,
 verbosity=0)
 self.assertTrue(os.path.exists(self.PO_FILE))
 with open(self.PO_FILE, 'r') as fp:
 po_contents = fp.read()
 # {% trans %}
 self.assertTrue('msgctxt "Special trans context #1"' in
 po_contents)
 self.assertTrue("Translatable literal #7a" in po_contents)
 self.assertTrue('msgctxt "Special trans context #2"' in
 po_contents)
 self.assertTrue("Translatable literal #7b" in po_contents)
 self.assertTrue('msgctxt "Special trans context #3"' in
 po_contents)
 self.assertTrue("Translatable literal #7c" in po_contents)

 #ticket #18881, single quote context
 self.assertTrue('msgctxt "finance"' in po_contents)
 self.assertMsgId('budget', po_contents)

 #{% blocktrans %}
 }}}

 However, the call of
 {{{
 self.assertMsgId('finance', po_contents)
 }}}
 currently does NOT check for duplicate message id in the po file, which is
 not quite adequate.
 Therefore, in the same file, where assertMsgId is defined, we can  use the
 following definition instead:
 {{{
 def assertMsgId(self, msgid, s, use_quotes=True):
 q = '"'
 if use_quotes:
 msgid = '"%s"' % msgid
 q = "'"
 needle = 'msgid %s' % msgid
 msgid = re.escape(msgid)
 matches = len(re.findall('^msgid %s' % msgid, s, re.MULTILINE))
 return self.assertTrue( matches==1,
 'Could not find %(q)s%(n)s%(q)s in generated PO file' %
 {'n':needle, 'q':q} if matches==0 else
 'Found more than one occurrences of %(q)s%(n)s%(q)s in
 generated PO file' % {'n':needle, 'q':q})

 }}}

-- 
Ticket URL: 
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] #18931: Add predicate functionality to Q objects

[Django]

#18931: Add predicate functionality to Q objects
-+-
 Reporter:  ptone|Owner:  ptone
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (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 ptone):

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


Comment:

 This is now ready for more eyes to review

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

-- 
Ticket URL: 
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] #7581: Middleware accessing HttpResponse.content breaks streaming HttpResponse objects.

[Django]

#7581: Middleware accessing HttpResponse.content breaks streaming HttpResponse
objects.
-+-
 Reporter:  mrmachine|Owner:  ccahoon
 Type:  New feature  |   Status:  new
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  stream HttpResponse  | Triage Stage:  Accepted
  Content-Length |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by mrmachine):

 * needs_docs:  0 => 1


Comment:

 I've updated the patch on my branch after further feedback from Aymeric
 Augustin and Anssi Kääriäinen on google groups discussion.

 The new patch refactors `HttpResponse` into `HttpResponseBase` and
 `HttpResponse` classes, and adds a new `HttpStreamingResponse` class.

 The `HttpResponse` class is simplified, and will consume iterator content
 whenever it is assigned, so that content can be safely accessed multiple
 times.

 The `HttpStreamingResponse` class exposes a new attribute,
 `streaming_content`. If you assign an iterator as streaming content, it
 will not be consumed until the response is iterated. The streaming content
 can be wrapped with a new generator (e.g. GZipMiddleware). The class
 prevents accidental assignment to the `content` attribute, to avoid
 confusing middleware that checks for a `content` attribute on response
 objects.

 Both classes use `HttpResponseBase.make_bytes()` to yield bytestrings when
 iterated, or a single bytestring when `HttpResponse.content` is accessed.
 This has simplified the implementation a little and removed some
 duplication.

 The `close()` method will now close all "file-like" content objects that
 were assigned to `content` or `streaming_content`, even if they are later
 replaced by different content. I think the old code would have left
 unclosed objects in this case.

 As an added bonus, you can now `write()` to both regular and streaming
 responses, when iterable or non-iterable content is assigned. For
 streaming responses, this just wraps the old streaming content with a new
 generator that yields an additional chunk at the end. For regular
 responses, assigned content is always normalised to a list now, so we can
 always append additional content.

 Middleware have been updated for compatibility with streaming responses.
 They now check responses for `content` or `streaming_content` before
 attempting to read or replace those attributes. New and 3rd party
 middleware should follow this example.

 We now have tests, too, and the full test suite passes here (2.7, OS X,
 SQLite). If this approach is accepted, I will add docs as well.

-- 
Ticket URL: 
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] #16835: filter users by group

[Django]

#16835: filter users by group
-+-
 Reporter:  Wim Feijen    |Owner:
 Type:  New feature  |  dloewenherz
Component:  contrib.auth |   Status:  closed
 Severity:  Normal   |  Version:  1.3
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  1|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by dloewenherz):

 Thanks!

 PS Someone else wrote the patch, I just marked RFC and became the owner
 since the person who originally wrote the issue appeared to have
 disappeared.

-- 
Ticket URL: 
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] #6148: Add generic support for database schemas

[Django]

#6148: Add generic support for database schemas
-+-
 Reporter:  ikelly   |Owner:  akaariai
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:  oracle postgresql|  decision needed
  mysql schemas  |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by maciej.maciaszek@…):

 Problem appears when you add 'south' to installed apps.

 Patched Django 1.4.1

 Unfortunately I cannot add traceback because TRAC treats me as spammer

-- 
Ticket URL: 
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] #19011: Annotating multiple Sum() objects gives wrong answer

[Django]

#19011: Annotating multiple Sum() objects gives wrong answer
-+-
 Reporter:  tBuLi|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:  annotate, sum|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by kmtracey):

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


Comment:

 This sounds like #10060 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] #18861: The test email backend (locmem) should perform more validation of messages

[Django]

#18861: The test email backend (locmem) should perform more validation of 
messages
-+-
 Reporter:  brutasse |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Mail)  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for checkin
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:"8599f64e54adfb32ee6550ed7a6ec9944034d978"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8599f64e54adfb32ee6550ed7a6ec9944034d978"
 Fixed #18861 -- Triggered message validation with locmem email backend

 Thanks Bruno Renié 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] 8599f6: Fixed #18861 -- Triggered message validation with ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8599f64e54adfb32ee6550ed7a6ec9944034d978
  
https://github.com/django/django/commit/8599f64e54adfb32ee6550ed7a6ec9944034d978
  Author: Claude Paroz 
  Date:   2012-09-22 (Sat, 22 Sep 2012)

  Changed paths:
M django/core/mail/backends/locmem.py
M tests/regressiontests/mail/tests.py

  Log Message:
  ---
  Fixed #18861 -- Triggered message validation with locmem email backend

Thanks Bruno Renié for the report and the initial patch.



-- 
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] #18968: Spatialite GML test failure

[Django]

#18968: Spatialite GML test failure
+-
 Reporter:  bkg |Owner:  bkg
 Type:  Bug |   Status:  closed
Component:  GIS |  Version:  master
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  | Triage Stage:  Ready for checkin
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"0ab8c58ca896643ea0bb0830a96274160d14cc69"]:
 {{{
 #!CommitTicketReference repository=""
 revision="0ab8c58ca896643ea0bb0830a96274160d14cc69"
 Fixed #18968 -- Only use separate GML regex for SpatiaLite < 3.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/django] 0ab8c5: Fixed #18968 -- Only use separate GML regex for Sp...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 0ab8c58ca896643ea0bb0830a96274160d14cc69
  
https://github.com/django/django/commit/0ab8c58ca896643ea0bb0830a96274160d14cc69
  Author: Brian Galey 
  Date:   2012-09-22 (Sat, 22 Sep 2012)

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

  Log Message:
  ---
  Fixed #18968 -- Only use separate GML regex for SpatiaLite < 3.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.

Re: [Django] #18057: Docs should say that caches are not cleared after each test

[Django]

#18057: Docs should say that caches are not cleared after each test
-+-
 Reporter:  guettli  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"bd514f28e49887e8555c289546286dc27a17ddcc"]:
 {{{
 #!CommitTicketReference repository=""
 revision="bd514f28e49887e8555c289546286dc27a17ddcc"
 [1.4.X] Fixed #18057 - Documented that caches are not cleared after each
 test; thanks guettli for the suggestion.

 Backport of 2aaa467a2a from master
 }}}

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

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

[django/django] bd514f: [1.4.X] Fixed #18057 - Documented that caches are ...

[GitHub]

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: bd514f28e49887e8555c289546286dc27a17ddcc
  
https://github.com/django/django/commit/bd514f28e49887e8555c289546286dc27a17ddcc
  Author: Tim Graham 
  Date:   2012-09-22 (Sat, 22 Sep 2012)

  Changed paths:
M docs/topics/testing.txt

  Log Message:
  ---
  [1.4.X] Fixed #18057 - Documented that caches are not cleared after each 
test; thanks guettli for the suggestion.

Backport of 2aaa467a2a from master



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

Re: [Django] #18057: Docs should say that caches are not cleared after each test

[Django]

#18057: Docs should say that caches are not cleared after each test
-+-
 Reporter:  guettli  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"2aaa467a2ab57d5616d384a70e2b6f8217ece63e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2aaa467a2ab57d5616d384a70e2b6f8217ece63e"
 Fixed #18057 - Documented that caches are not cleared after each test;
 thanks guettli for the suggestion.
 }}}

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

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

[django/django] 2aaa46: Fixed #18057 - Documented that caches are not clea...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2aaa467a2ab57d5616d384a70e2b6f8217ece63e
  
https://github.com/django/django/commit/2aaa467a2ab57d5616d384a70e2b6f8217ece63e
  Author: Tim Graham 
  Date:   2012-09-22 (Sat, 22 Sep 2012)

  Changed paths:
M docs/topics/testing.txt

  Log Message:
  ---
  Fixed #18057 - Documented that caches are not cleared after each test; thanks 
guettli for the suggestion.



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

Re: [Django] #18919: GEOSGeometry transform method is dropping Z attribute on 3D geometries

[Django]

#18919: GEOSGeometry transform method is dropping Z attribute on 3D geometries
---+
 Reporter:  luizvital  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  GIS|  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):

 * needs_better_patch:  1 => 0


Comment:

 While working on #16594, I realized that the 3D dimension was stripped out
 from the wkb of geometries. I think that difference between wkb and ewkb
 should only be the srid, not the Z dimension. Unfortunately, I'm unable to
 download the latest OGC spec to confirm this, but at least the PostGIS
 documentation for ST_AsBinary mentions that it supports 3D.

 The patch is then more invasive that initially thought. Please test and
 comment!

-- 
Ticket URL: 
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] #18951: Datetime microseconds cutoff first zero in Django templates

[Django]

#18951: Datetime microseconds cutoff first zero in Django templates
-+-
 Reporter:  olofom@… |Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.4
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  datetime | Triage Stage:  Accepted
  microseconds   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"822cfce3df53301d9f9f4c14bd8a0cb2a1956e2e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="822cfce3df53301d9f9f4c14bd8a0cb2a1956e2e"
 Fixed #18951 -- Formatting of microseconds.

 Thanks olofom at gmail com for the report.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] 822cfc: Fixed #18951 -- Formatting of microseconds.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 822cfce3df53301d9f9f4c14bd8a0cb2a1956e2e
  
https://github.com/django/django/commit/822cfce3df53301d9f9f4c14bd8a0cb2a1956e2e
  Author: Aymeric Augustin 
  Date:   2012-09-22 (Sat, 22 Sep 2012)

  Changed paths:
M django/utils/dateformat.py
M docs/ref/templates/builtins.txt
M tests/regressiontests/utils/dateformat.py

  Log Message:
  ---
  Fixed #18951 -- Formatting of microseconds.

Thanks olofom at gmail com for the report.



-- 
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] #19011: Annotating multiple Sum() objects gives wrong answer

[Django]

#19011: Annotating multiple Sum() objects gives wrong answer
--+---
 Reporter:  tBuLi |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.4
 Severity:  Normal|   Keywords:  annotate, sum
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+---
 This is best explained with an example:

 {{{
 queryset = Member.objects.annotate(payed=Sum('payment__amount'))
 queryset =
 Member.objects.annotate(discount=Sum('membership__discount__amount'))
 }}}

 These give the right payed and discount amount for the member, whereas

 {{{
 queryset =
 Member.objects.annotate(discount=Sum('membership__discount__amount'),
 payed=Sum('payment__amount'))
 }}}

 gives a value for payed which is a factor 2 higher, and the discount is a
 factor 3 higher. Using exactly the same syntax with Count() gives the
 correct answer in both cases, so I suspect something goes wrong with
 Sum().

 using distinct = True does not matter.

-- 
Ticket URL: 
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] #18951: Datetime microseconds cutoff first zero in Django templates

[Django]

#18951: Datetime microseconds cutoff first zero in Django templates
-+-
 Reporter:  olofom@… |Owner:  aaugustin
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  datetime | Triage Stage:  Accepted
  microseconds   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by aaugustin):

 Technically, this is the documented behavior.
 https://docs.djangoproject.com/en/dev/ref/templates/builtins/ says:
 > u Microseconds.   0 to 99
 and not:
 > u Microseconds.   00 to 99

 That said, it isn't a very useful behavior :)

 Django's `dateformat` mimicks PHP's `date`. I just checked that PHP left-
 pads the result with zeros.

 I think it's just a bug that dates back to 2005, and I'm going to commit a
 fix shortly.

-- 
Ticket URL: 
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] #16218: Class-based month archive doesn't behave like previous generic view

[Django]

#16218: Class-based month archive doesn't behave like previous generic view
---+-
 Reporter:  nnrcschmdt |Owner:  aaugustin
 Type:  Bug|   Status:  closed
Component:  Generic views  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"baa33cd8faa16737524b1ac355802a10dd63571c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="baa33cd8faa16737524b1ac355802a10dd63571c"
 Fixed #16218 -- date_list order in generic CBVs.

 Thanks nnrcschmdt for the report and bpeschier for the initial
 version of the patch.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] baa33c: Fixed #16218 -- date_list order in generic CBVs.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: baa33cd8faa16737524b1ac355802a10dd63571c
  
https://github.com/django/django/commit/baa33cd8faa16737524b1ac355802a10dd63571c
  Author: Aymeric Augustin 
  Date:   2012-09-22 (Sat, 22 Sep 2012)

  Changed paths:
M django/views/generic/dates.py
M docs/ref/class-based-views/mixins-date-based.txt
M docs/releases/1.5.txt
M tests/regressiontests/generic_views/dates.py

  Log Message:
  ---
  Fixed #16218 -- date_list order in generic CBVs.

Thanks nnrcschmdt for the report and bpeschier for the initial
version of the patch.



-- 
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] 59afc1: Made geo3d tests independent from each other

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 59afc18f3735abfd7ab4b1a904000a547daed4ca
  
https://github.com/django/django/commit/59afc18f3735abfd7ab4b1a904000a547daed4ca
  Author: Claude Paroz 
  Date:   2012-09-22 (Sat, 22 Sep 2012)

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

  Log Message:
  ---
  Made geo3d tests independent from each other



-- 
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] #15619: Logout link should be protected

[Django]

#15619: Logout link should be protected
---+--
 Reporter:  void   |Owner:  ashchristopher
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by aaugustin):

 #7989 was a duplicate.

-- 
Ticket URL: 
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] #7989: Logout view should require POST request

[Django]

#7989: Logout view should require POST request
-+-
 Reporter:  jcassee  |Owner:
 Type:  Uncategorized|   Status:  closed
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  authentication   | Triage Stage:  Design
Has patch:  0|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 Reported again as #15619, with a longer discussion.

-- 
Ticket URL: 
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] #18919: GEOSGeometry transform method is dropping Z attribute on 3D geometries

[Django]

#18919: GEOSGeometry transform method is dropping Z attribute on 3D geometries
---+
 Reporter:  luizvital  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  GIS|  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by claudep):

 * needs_better_patch:  0 => 1


Comment:

 You are totally right, the test of my current patch is broken (Z should
 not be changed to 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.

Re: [Django] #16835: filter users by group

[Django]

#16835: filter users by group
-+-
 Reporter:  Wim Feijen    |Owner:
 Type:  New feature  |  dloewenherz
Component:  contrib.auth |   Status:  closed
 Severity:  Normal   |  Version:  1.3
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  1|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Preston Holmes ):

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


Comment:

 In [changeset:"69ff1b7390e140f332a5aa55c44a091c838923fb"]:
 {{{
 #!CommitTicketReference repository=""
 revision="69ff1b7390e140f332a5aa55c44a091c838923fb"
 Fixed #16835 -- add groups to auth.user admin list_filter
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] 69ff1b: Fixed #16835 -- add groups to auth.user admin list...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 69ff1b7390e140f332a5aa55c44a091c838923fb
  
https://github.com/django/django/commit/69ff1b7390e140f332a5aa55c44a091c838923fb
  Author: Dan Loewenherz 
  Date:   2012-09-22 (Sat, 22 Sep 2012)

  Changed paths:
M django/contrib/auth/admin.py
M docs/releases/1.5.txt

  Log Message:
  ---
  Fixed #16835 -- add groups to auth.user admin list_filter



-- 
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] #16835: filter users by group

[Django]

#16835: filter users by group
-+-
 Reporter:  Wim Feijen    |Owner:
 Type:  New feature  |  dloewenherz
Component:  contrib.auth |   Status:  assigned
 Severity:  Normal   |  Version:  1.3
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  1|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by ptone):

 * component:  contrib.admin => contrib.auth


Comment:

 Thanks for the patch - landing it in a second - just FYI in general avoid
 RFCing your own patches, for small patches like this where docs/tests
 essentially don't apply - it can be OK, but even then it is preferred to
 wait a bit after attaching the patch to see if someone might RFC it first.

 https://docs.djangoproject.com/en/dev/internals/contributing/triaging-
 tickets/#ready-for-checkin

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

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

Re: [Django] #18616: New auth signal: user_login_failed

[Django]

#18616: New auth signal: user_login_failed
-+-
 Reporter:  micolous |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.auth |  Version:  master
 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
-+-

Comment (by ptone):

 I've reviewed, merged locally, verified docs, tests and ready to land, but
 have asked Paul to weigh in on the idea of sending credentials in the
 signal. While a project author '''should''' be able to fully control what
 listeners register for the signal, I'd feel better with Paul's quick
 opinion on 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] #19010: Typo error in docs: a space missing

[Django]

#19010: Typo error in docs: a space missing
---+--
 Reporter:  edepe  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  invalid
 Keywords:  typo   | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by edepe):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #19010: Typo error in docs: a space missing

[Django]

#19010: Typo error in docs: a space missing
---+
 Reporter:  edepe  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.4
 Severity:  Normal |   Keywords:  typo
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 In https://docs.djangoproject.com/en/dev/ref/templates/builtins/ where
 say:
 "{% ifchanged match.ballot_id %}" should be "{% if changed match.ballot_id
 %}"

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

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