date:20150117

Re: [Django] #24170: DateTimeRangeField: widget doesn't implement decompress()

2015-01-17 Thread Django

Comment (by ngzhian):

Error is caused because all the new fields added in 1.8
`IntegerRangeField`, `FloatRangeField`, `DateTimeRangeField`, and
`DateRangeField`, all inherit from `BaseRangeField`.

`BaseRangeField` itself defines its widget as
`forms.MultiWidget([self.base_field.widget, self.base_field.widget])`

[https://github.com/django/django/blob/master/django/contrib/postgres/forms/ranges.py#L18
postgres.forms.ranges.py#18]. However, `MultiWidget` raises `
NotImplementedError('Subclasses must implement this method.')` just like
@joelburton mentioned.

I'm not sure how to patch this. Thinking that:
1. Each of the child classes of `BaseRangeField` should overwrite
`__init__` to put in their own widgets.
2. create a new `widgets.py` file in `contrib.postgres` to define the new
widgets.

Comments?

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

--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.5d0996aab1124139d8f19f6b7183bbd8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24172: `pip install Django` with "old" pips gets 1.8a1

2015-01-17 Thread Django

#24172: `pip install Django` with "old" pips gets 1.8a1
-+--
 Reporter:  doismellburning  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Packaging|  Version:  1.8alpha1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by timgraham):

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


Comment:

 Source distribution has been removed from PyPI. Now I guess we wait for a
 ticket on problems with doing that. :-)

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.51a4ef256693e9e7e223b61fc25f07f8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24172: `pip install Django` with "old" pips gets 1.8a1

2015-01-17 Thread Django

#24172: `pip install Django` with "old" pips gets 1.8a1
-+--
 Reporter:  doismellburning  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Packaging|  Version:  1.8alpha1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by doismellburning):

 Ah, that's a very nice hack! Cheers :)

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.e5f5252062a88539a8432bfb6fdcf3bb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #13252: Use the natural key instead of the primary key when serializing

2015-01-17 Thread Django

#13252: Use the natural key instead of the primary key when serializing
-+-
 Reporter:  SmileyChris  |Owner:
 |  mtredinnick
 Type:  New feature  |   Status:  closed
Component:  Core |  Version:  master
  (Serialization)|
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"c3336e7e4f146fc62272d462288a00f8d78c1f83"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c3336e7e4f146fc62272d462288a00f8d78c1f83"
 Removed dumpdata --natural option and serializers use_natural_keys
 parameter.

 Per deprecation timeline; refs #13252.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.8beedd03dc636e7c0dff2407ddeae3c5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24172: `pip install Django` with "old" pips gets 1.8a1

2015-01-17 Thread Django

#24172: `pip install Django` with "old" pips gets 1.8a1
-+--
 Reporter:  doismellburning  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Packaging|  Version:  1.8alpha1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by timgraham):

 * component:  Uncategorized => Packaging


Comment:

 Yes, we tried uploading a "pre-release" again for 1.8 alpha (#21108).
 However, looking at that ticket again, I think I was supposed to upload
 only the wheel file, since older versions of pip that don't support
 `--pre` also don't support wheel. I'll remove the `.tar.gz` from PyPI if
 we get confirmation on this.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.1a4d37e40ea30b024fedf4f936b54268%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24172: `pip install Django` with "old" pips gets 1.8a1

2015-01-17 Thread Django

#24172: `pip install Django` with "old" pips gets 1.8a1
-+--
 Reporter:  doismellburning  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Uncategorized|  Version:  1.8alpha1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by doismellburning):

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


Comment:

 Ah, this would probably be the pip 1.4 change to only install stable
 versions by default (https://pip.pypa.io/en/latest/news.html)

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.911581e375a21c5c5388dbe4c3c23103%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #24172: `pip install Django` with "old" pips gets 1.8a1

2015-01-17 Thread Django

#24172: `pip install Django` with "old" pips gets 1.8a1
-+---
Reporter: doismellburning | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized|Version: 1.8alpha1
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0| UI/UX: 0
-+---
Just had someone turn up in #django doing the 1.7 tutorial but with 1.8
installed. They'd followed the advice at
https://docs.djangoproject.com/en/1.7/topics/install/#installing-an-
official-release-with-pip which says `pip install Django`. Alas this had
got them Django 1.8a1.

They were using Debian Wheezy (latest stable) which ships with pip 1.1. It
looks like it needs pip>=1.5.6 (at strictest) to not get 1.8a1 -
https://gist.github.com/doismellburning/fa8aa370df9835b592e0

As to whether this is considered to be:

* a packaging bug (i.e. "some users on currently-supported OSen will pick
up the alpha version")
* a documentation bug (either "the install instructions should specify a
version" (which I'd disagree with) or "the install instructions should
mention this caveat")
* something to be ignored
* some thing else

then I've no idea, but I'm personally inclined towards the first from a
"principle of least surprise" perspective.

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

--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/058.c3e8e827dac99f7b655af74d9a5308a4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21147: cache.tests.FileBasedCacheTests.test_zero_timeout fails with sqlite on windows

2015-01-17 Thread Django

#21147: cache.tests.FileBasedCacheTests.test_zero_timeout fails with sqlite on
windows
-+-
 Reporter:  manfre   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Cache system)  |  Version:
 |  1.6-beta-1
 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
-+-

Comment (by Tim Graham ):

 In [changeset:"40d6b376d4ac29c1f271bb827cd9ca24860ce4b5"]:
 {{{
 #!CommitTicketReference repository=""
 revision="40d6b376d4ac29c1f271bb827cd9ca24860ce4b5"
 Removed BaseMemcachedCacheMethods._get_memcache_timeout backwards
 compatibility shim.

 Per deprecation timeline; refs #21147.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.c20346fb56a47109bffa1c2f9330cf9e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24170: DateTimeRangeField: widget doesn't implement decompress()

2015-01-17 Thread Django

#24170: DateTimeRangeField: widget doesn't implement decompress()
-+-
 Reporter:  joelburton   |Owner:  ngzhian
 Type:  Uncategorized|   Status:  assigned
Component:  Database layer   |  Version:  1.8alpha1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  DateTimeRangeField   | Triage Stage:
  decompress |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by ngzhian):

 * owner:  nobody => ngzhian
 * needs_better_patch:   => 0
 * status:  new => assigned
 * 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.7abf5e6e922ce16ccaa42528ab448863%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #8898: `required` validation bypassed when using `DateTimeField` with `SplitDateTimeWidget`.

2015-01-17 Thread Django

#8898: `required` validation bypassed when using `DateTimeField` with
`SplitDateTimeWidget`.
-+-
 Reporter:  mrmachine|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  DateTimeField| Triage Stage:  Ready for
  SplitDateTimeWidget|  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:"714277cb4cedd8290101f9c6b3e6382f192ae177"]:
 {{{
 #!CommitTicketReference repository=""
 revision="714277cb4cedd8290101f9c6b3e6382f192ae177"
 Removed support for SplitDateTimeWidget with DateTimeField per deprecation
 timeline.

 refs #8898
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.0e17e50a20384cf7651c971a8f07aafa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20702: Using ModelAdmin.get_formsets() to filter inlines is broken.

2015-01-17 Thread Django

#20702: Using ModelAdmin.get_formsets() to filter inlines is broken.
-+-
 Reporter:  stanislas.guerra@…   |Owner:
 |  CodenameTim
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  admin inlines| Triage Stage:  Accepted
  get_formsets   |
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:"ecbe20fe20ddc54aa034530b38a73195ee3f598d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ecbe20fe20ddc54aa034530b38a73195ee3f598d"
 [1.7.x] Added versionadded to ModelAdmin.get_formsets_with_inlines(); refs
 #20702.

 Backport of 7cfcdd98dcf0dbbde7cfd656e450c52342dbe6f3 from stable/1.8.x
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/084.d40e4b5f870f1a6bd76a321f57e9b774%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20702: Using ModelAdmin.get_formsets() to filter inlines is broken.

2015-01-17 Thread Django

#20702: Using ModelAdmin.get_formsets() to filter inlines is broken.
-+-
 Reporter:  stanislas.guerra@…   |Owner:
 |  CodenameTim
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  admin inlines| Triage Stage:  Accepted
  get_formsets   |
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:"7cfcdd98dcf0dbbde7cfd656e450c52342dbe6f3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7cfcdd98dcf0dbbde7cfd656e450c52342dbe6f3"
 [1.8.x] Added versionadded to ModelAdmin.get_formsets_with_inlines(); refs
 #20702.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/084.06916024eed2ed83397d9dec5ffbee11%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20702: Using ModelAdmin.get_formsets() to filter inlines is broken.

2015-01-17 Thread Django

#20702: Using ModelAdmin.get_formsets() to filter inlines is broken.
-+-
 Reporter:  stanislas.guerra@…   |Owner:
 |  CodenameTim
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  admin inlines| Triage Stage:  Accepted
  get_formsets   |
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:"2c9e95639e5a353f9fe1b81ecd3fdc5e2212781e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2c9e95639e5a353f9fe1b81ecd3fdc5e2212781e"
 Removed ModelAdmin.get_formsets() per deprecation timeline; refs #20702.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/084.6577be6c2b5c3f47f2bff2eba68f6b02%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #24171: (1054, "Unknown column '__col1' in 'field list'") when using values, annotate and aggrregate

2015-01-17 Thread Django

#24171: (1054, "Unknown column '__col1' in 'field list'") when using values,
annotate and aggrregate
--+---
 Reporter:  abdulhaq-e|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.8alpha1
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+---
 I will try my best here to explain when this comes up:

 Say I have the following test model:
 {{{
 class Test(models.Model):

 fieldA = models.ForeignKey(AnotherModel)
 fieldB = models.IntegerField()
 }}}

 I want to sum the result of multiplying `fieldB` and `fieldC` where the
 latter is obtained by spanning the relationship as such (for example):
 `fieldA__ForeignKey2__ForeignKey3__fieldC`

 To do this:

 {{{
 
Test.objects.aggregate(Sum(F(`fieldA__ForeignKey2__ForeignKey3__fieldC`)*F('fieldB')))
 }}}

 The above will work fine:

 But I want to use the new annotations features in v1.8 to make the
 relationship spanning shorter:

 {{{
 
Test.objects.annotate(fieldC=F(`fieldA__ForeignKey2__ForeignKey3__fieldC`)).aggregate(Sum(F('fieldC')*F('fieldB')))
 }}}

 This will also work fine. However, I want a `ValuesQuerySet` (i.e. I want
 some specific fields). This will NOT WORK:

 {{{
 
Test.objects.annotate(fieldC=F(`fieldA__ForeignKey2__ForeignKey3__fieldC`)).values('fieldC',
 'fieldB').aggregate(Sum(F('fieldC')*F('fieldB')))
 }}}
 This will give the error in the title: `(1054, "Unknown column '__col1' in
 'field list'")`. The error is definitely to do with fieldB and here is how
 I proved it!:

 This works:
 {{{
 
Test.objects.annotate(fieldC=F(`fieldA__ForeignKey2__ForeignKey3__fieldC`)).values('fieldC',
 'fieldB').aggregate(Sum(F('fieldC')))
 }}}

 And surprisingly, giving an alternate annotation to fieldB works! (of
 course I can't use the field name as an alias name):
 {{{
 Test.objects.annotate(fieldC=F(`fieldA__ForeignKey2__ForeignKey3__fieldC`),
 FIELDB=F('fieldB')).values('fieldC',
 'FIELDB').aggregate(Sum(F('fieldC')*F('FIELDB')))
 }}}

 Is this normal behaviour!?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/053.65772809d094fe315f92de5f524467b4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22423: Geodjango spatial functions should leverage mysql 5.6 spatial functions.

2015-01-17 Thread Django

#22423: Geodjango spatial functions should leverage mysql 5.6 spatial functions.
-+
 Reporter:  visu |Owner:  visu
 Type:  New feature  |   Status:  new
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  gis, mysql,  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by claudep):

 See the pull request for the remaining failure with
 `test_disjoint_lookup`.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.eeba9a80b5d9a510433a54872481bbe0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24164: Oracle GIS geoapp extent test failure

2015-01-17 Thread Django

#24164: Oracle GIS geoapp extent test failure
---+-
 Reporter:  timgraham  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  GIS|  Version:  1.8alpha1
 Severity:  Normal |   Resolution:
 Keywords:  oracle | 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):

 I encountered this issue while working on #14483. This is the commit that
 passes with PostGIS but fails with MySQL or Spatialite (and most probably
 Oracle too) because of the select artifact:
 
https://github.com/claudep/django/commit/53783c93a551fe769d5395e6ee54d01729b23722

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.abe12bc9feb6ac4ae6d1fbb39685fc5d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21936: Allow delete to provide a success message through a mixin.

2015-01-17 Thread Django

#21936: Allow delete to provide a success message through a mixin.
-+-
 Reporter:  david.fischer.ch@…   |Owner:
 |  CarolineSimpson
 Type:  New feature  |   Status:  assigned
Component:  contrib.messages |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  mixin| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by CarolineSimpson):

 * needs_better_patch:  1 => 0


Comment:

 I've updated the patch with feedback from review.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/084.61f09af26a3bbec86bd00163b28743cf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #24170: DateTimeRangeField: widget doesn't implement decompress()

2015-01-17 Thread Django

#24170: DateTimeRangeField: widget doesn't implement decompress()
-+-
 Reporter:  joelburton   |  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:  Database layer   |Version:  1.8alpha1
  (models, ORM)  |   Keywords:  DateTimeRangeField
 Severity:  Normal   |  decompress
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 1. Create a model with a DateTimeRangeField and another field (I used just
 one other, a SlugField)

 2. Via the admin, add a record with a valid slug and datetimerange

 3. Try to edit the record, changing the slug

 (This was done with a Postgres backend)

 This traceback is produced:

 {{{
 Environment:


 Request Method: POST
 Request URL: http://localhost:8000/admin/homework/homework/3/

 Django Version: 1.8a1
 Python Version: 3.4.2
 Installed Applications:
 ('django.contrib.admin',
  'django.contrib.auth',
  'django.contrib.contenttypes',
  'django.contrib.sessions',
  'django.contrib.messages',
  'django.contrib.staticfiles',
  'django.contrib.postgres',
  'homework')
 Installed Middleware:
 ('django.contrib.sessions.middleware.SessionMiddleware',
  'django.middleware.common.CommonMiddleware',
  'django.middleware.csrf.CsrfViewMiddleware',
  'django.contrib.auth.middleware.AuthenticationMiddleware',
  'django.contrib.auth.middleware.SessionAuthenticationMiddleware',
  'django.contrib.messages.middleware.MessageMiddleware',
  'django.middleware.clickjacking.XFrameOptionsMiddleware',
  'django.middleware.security.SecurityMiddleware')


 Traceback:
 File "/Users/joel/programming/django18play/venv/lib/python3.4/site-
 packages/django/core/handlers/base.py" in get_response
   131. response = wrapped_callback(request,
 *callback_args, **callback_kwargs)
 File "/Users/joel/programming/django18play/venv/lib/python3.4/site-
 packages/django/contrib/admin/options.py" in wrapper
   615. return self.admin_site.admin_view(view)(*args,
 **kwargs)
 File "/Users/joel/programming/django18play/venv/lib/python3.4/site-
 packages/django/utils/decorators.py" in _wrapped_view
   110. response = view_func(request, *args, **kwargs)
 File "/Users/joel/programming/django18play/venv/lib/python3.4/site-
 packages/django/views/decorators/cache.py" in _wrapped_view_func
   54. response = view_func(request, *args, **kwargs)
 File "/Users/joel/programming/django18play/venv/lib/python3.4/site-
 packages/django/contrib/admin/sites.py" in inner
   226. return view(request, *args, **kwargs)
 File "/Users/joel/programming/django18play/venv/lib/python3.4/site-
 packages/django/contrib/admin/options.py" in change_view
   1518. return self.changeform_view(request, object_id, form_url,
 extra_context)
 File "/Users/joel/programming/django18play/venv/lib/python3.4/site-
 packages/django/utils/decorators.py" in _wrapper
   34. return bound_func(*args, **kwargs)
 File "/Users/joel/programming/django18play/venv/lib/python3.4/site-
 packages/django/utils/decorators.py" in _wrapped_view
   110. response = view_func(request, *args, **kwargs)
 File "/Users/joel/programming/django18play/venv/lib/python3.4/site-
 packages/django/utils/decorators.py" in bound_func
   30. return func.__get__(self, type(self))(*args2,
 **kwargs2)
 File
 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/contextlib.py"
 in inner
   30. return func(*args, **kwds)
 File "/Users/joel/programming/django18play/venv/lib/python3.4/site-
 packages/django/contrib/admin/options.py" in changeform_view
   1472. change_message =
 self.construct_change_message(request, form, formsets)
 File "/Users/joel/programming/django18play/venv/lib/python3.4/site-
 packages/django/contrib/admin/options.py" in construct_change_message
   1020. if form.changed_data:
 File "/Users/joel/programming/django18play/venv/lib/python3.4/site-
 packages/django/forms/forms.py" in changed_data
   466. if field.has_changed(initial_value, data_value):
 File "/Users/joel/programming/django18play/venv/lib/python3.4/site-
 packages/django/forms/fields.py" in has_changed
   1126. initial = self.widget.decompress(initial)
 File "/Users/joel/programming/django18play/venv/lib/python3.4/site-
 packages/django/forms/widgets.py" in decompress
   850. raise NotImplementedError('Subclasses must implement this
 method.')

 Exception Type: NotImplementedError at /admin/homework/homework/3/
 Exception Value: Subclasses must implement this method.
 }}}

--
Ticket URL: 
Django 
The Web framework for

Re: [Django] #24164: Oracle GIS geoapp extent test failure

2015-01-17 Thread Django

#24164: Oracle GIS geoapp extent test failure
---+-
 Reporter:  timgraham  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  GIS|  Version:  1.8alpha1
 Severity:  Normal |   Resolution:
 Keywords:  oracle | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by jarshwah):

 Yes this does look like the same problem. Claude's idea sounds like the
 way to go. Did you open a ticket for the AsText issues? And what is the
 failing AsText test? It'll be easier to test against those backends rather
 than oragis, and the solution should translate to both.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.4ed9ff2c9cdfad430d1e387af63bfe1c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24155: Make migration generation more deterministic

2015-01-17 Thread Django

#24155: Make migration generation more deterministic
--+
 Reporter:  tdobrovolny   |Owner:  MarkusH
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Migrations|  Version:  1.7
 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 MarkusH):

 * has_patch:  0 => 1


Comment:

 PR: https://github.com/django/django/pull/3943

 I don't think this change needs release notes.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.f1e0da7bc21bac9399f2dd1a023bb9b8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22232: Template extends tag can cause recursion

2015-01-17 Thread Django

#22232: Template extends tag can cause recursion
-+-
 Reporter:  galedragon   |Owner:  darkryder
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by prestontimmons):

 Your patch was marked RFC, so you don't need to change anything unless you
 get feedback otherwise, especially if this patch is considered a bug fix
 that can land in Django 1.8. My note above is more directed toward
 potential committers if this only goes into the 1.9 release cycle.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.eed710e073c05044c97b85c02fd72cb9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23884: Consider moving FlatPageSitemap to contrib.flatpages

2015-01-17 Thread Django

#23884: Consider moving FlatPageSitemap to contrib.flatpages
-+-
 Reporter:  kezabelle|Owner:
 Type:   |  berkerpeksag
  Cleanup/optimization   |   Status:  closed
Component:  contrib.sitemaps |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"c2d5f2903cfaef4f8b17d86f4db706b61073a471"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c2d5f2903cfaef4f8b17d86f4db706b61073a471"
 Removed contrib.flatpages.FlatPageSitemap per deprecation timeline; refs
 #23884.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.fbea9d2e541a77dd4de3ce390b9b649a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24169: ArrayField can't use __contained_by or __overlap queries for CharField

2015-01-17 Thread Django

#24169: ArrayField can't use __contained_by or __overlap queries for CharField
--+--
 Reporter:  joelburton|Owner:
 Type:  Uncategorized |   Status:  new
Component:  contrib.postgres  |  Version:  1.8alpha1
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by joelburton):

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


Old description:

> ArrayField's lookup.py uses the @> operator for __contains, the <@
> operator for __contained_by, and the && operator for __overlap.
>
> When the field uses CharField (Postgres' varchar()), __contains works,
> but __contained_by and __overlap do not, as Postgres does not define <@
> and && operators for an array of varchar[] (it does for text[]).
>
> __contains works because, in array.py, there is a custom lookup,
> "ArrayOverlap", the outputs a cast to cast the array query value to, say,
> "::varchar(10)[]"
>
> If there are similar custom lookups for __contained_by and __overlap,
> these then work.

New description:

 ArrayField's lookup.py uses the @> operator for !__contains, the <@
 operator for !__contained_by, and the && operator for !__overlap.

 When the field uses CharField (Postgres' varchar()), !__contains works,
 but !__contained_by and !__overlap do not, as Postgres does not define <@
 and && operators for an array of varchar[] (it does for text[]).

 !__contains works because, in array.py, there is a custom lookup,
 "ArrayOverlap", the outputs a cast to cast the array query value to, say,
 "::varchar(10)[]"

 If there are similar custom lookups for !__contained_by and !__overlap,
 these then work.

--

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.50fa7fd7b20f4b2c3adad49e3cc2341f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #24169: ArrayField can't use __contained_by or __overlap queries for CharField

2015-01-17 Thread Django

#24169: ArrayField can't use __contained_by or __overlap queries for CharField
--+---
 Reporter:  joelburton|  Owner:
 Type:  Uncategorized | Status:  new
Component:  contrib.postgres  |Version:  1.8alpha1
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+---
 ArrayField's lookup.py uses the @> operator for __contains, the <@
 operator for __contained_by, and the && operator for __overlap.

 When the field uses CharField (Postgres' varchar()), __contains works, but
 __contained_by and __overlap do not, as Postgres does not define <@ and &&
 operators for an array of varchar[] (it does for text[]).

 __contains works because, in array.py, there is a custom lookup,
 "ArrayOverlap", the outputs a cast to cast the array query value to, say,
 "::varchar(10)[]"

 If there are similar custom lookups for __contained_by and __overlap,
 these then work.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/053.b17aae814ca381d87eac0b1bc2ab240d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22838: Deprecate ModelChoiceField.cache_choices

2015-01-17 Thread Django

#22838: Deprecate ModelChoiceField.cache_choices
-+-
 Reporter:  mjtamlyn |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Forms|  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
-+-

Comment (by Tim Graham ):

 In [changeset:"2788c46d46bc4d7afb906765ce1f484faef180c5"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2788c46d46bc4d7afb906765ce1f484faef180c5"
 Removed Multiple/ModelChoiceField cache_choices option; refs #22838.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.d944969e7de2a77aeac910b005ddeaa4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #18773: Enable optional logging of invalid variable lookups

2015-01-17 Thread Django

#18773: Enable optional logging of invalid variable lookups
-+-
 Reporter:  wrigley  |Owner:
 |  CarolineSimpson
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  Version:  1.4
 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 CarolineSimpson):

 * needs_better_patch:  1 => 0


Comment:

 I have submitted a new pull request with the updates requested for the
 previous pull request.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.70011fa751df07e20918b157c572d24a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21939: Deprecate loading ssi/url tags from future

2015-01-17 Thread Django

#21939: Deprecate loading ssi/url tags from future
--+
 Reporter:  timo  |Owner:  zsiciarz
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Template system   |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"bd93032191f96bc7086aa46b91b4177601c6fce9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="bd93032191f96bc7086aa46b91b4177601c6fce9"
 Removed ssi/url tags from future per deprecation timeline; refs #21939.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.3594978c87022a0f93164317f307e01e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21725: Javascript translations fail with non-BMP characters

2015-01-17 Thread Django

#21725: Javascript translations fail with non-BMP characters
-+-
 Reporter:  nedbatchelder|Owner:  MattBlack
 Type:  Bug  |   Status:  closed
Component:   |  Version:  1.6
  Internationalization   |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  nlsprint14   | Triage Stage:  Ready for
 |  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:"df3f3bbe2927b9bad80088c6adbf5e8c5ba778c9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="df3f3bbe2927b9bad80088c6adbf5e8c5ba778c9"
 Removed utils.text.javascript_quote() per deprecation timeline; refs
 #21725.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.ac4512129c2d2a9b1fd9903ae2620f59%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23741: [System Check for migrations] Check presence of all foreign keys

2015-01-17 Thread Django

#23741: [System Check for migrations] Check presence of all foreign keys
--+
 Reporter:  notsqrt   |Owner:  notsqrt
 Type:  New feature   |   Status:  closed
Component:  Core (System checks)  |  Version:  1.7
 Severity:  Normal|   Resolution:  wontfix
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

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


Comment:

 I think the time to add this check has passed since 1.8 is feature frozen
 and 1.9 won't support apps without migrations.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.c38ace0ca02092d7c67513d839e68d5a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #18149: Form.prefix example gives wrong separator between prefix and field name

2015-01-17 Thread Django

#18149: Form.prefix example gives wrong separator between prefix and field name
---+--
 Reporter:  matt@… |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by Tim Graham ):

 In [changeset:"f0a1df0b0139a7f5a576dff966210b5d52247650"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f0a1df0b0139a7f5a576dff966210b5d52247650"
 Removed deprecated Chinese language codes; refs #18149.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/078.d5d8b0006c98faaa0e6b54f1d607cc12%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22232: Template extends tag can cause recursion

2015-01-17 Thread Django

Comment (by darkryder):

Replying to [comment:19 prestontimmons]:
> FYI - This behavior is also addressed as part of #15053. If this patch
is committed, it's implementation via a context variable may be obsoleted
by the new origin api discussed here:
>
> https://groups.google.com/forum/#!topic/django-developers/VFBLAoPSplI

Since this was my first attempt at contributing, I have no clue what the
logical next step should be. Should this ticket be put on hold or is there
any other way to proceed? And if the Loader API is implemented, I guess
that fixes this ticket 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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.c59a1d70a15908a271027e7b5684e4c3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24164: Oracle GIS geoapp extent test failure

2015-01-17 Thread Django

#24164: Oracle GIS geoapp extent test failure
---+-
 Reporter:  timgraham  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  GIS|  Version:  1.8alpha1
 Severity:  Normal |   Resolution:
 Keywords:  oracle | 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):

 I've encountered similar issues on other tests with SQLite and MySQL
 `AsText` converters. Ideally, the subquery should know it is a subquery
 and not call `select_format` when compiling.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.505956307b36875f9741bdaf7b7b3b9c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22423: Geodjango spatial functions should leverage mysql 5.6 spatial functions.

2015-01-17 Thread Django

#22423: Geodjango spatial functions should leverage mysql 5.6 spatial functions.
-+
 Reporter:  visu |Owner:  visu
 Type:  New feature  |   Status:  new
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  gis, mysql,  | 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:

 https://github.com/django/django/pull/3941, MySQL 5.6.1+ testers welcome.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.f60bc3f58317dd885d84a350395a9372%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24055: Keep reference to view class for resolve()

2015-01-17 Thread Django

#24055: Keep reference to view class for resolve()
+
 Reporter:  collinanderson  |Owner:  nobody
 Type:  New feature |   Status:  closed
Component:  Generic views   |  Version:  master
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  1
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by Loic Bistuer ):

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


Comment:

 In [changeset:"a420f83e7d2e446ca01ef7c13d30c2ef3e975e5c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a420f83e7d2e446ca01ef7c13d30c2ef3e975e5c"
 Fixed #24055 -- Keep reference to view class for resolve()
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.5bf9fa46dc5154233055f50fd79e52bf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22232: Template extends tag can cause recursion

2015-01-17 Thread Django

#22232: Template extends tag can cause recursion
-+-
 Reporter:  galedragon   |Owner:  darkryder
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by prestontimmons):

 FYI - This behavior is also addressed as part of #15053. If this patch is
 committed, it's implementation via a context variable may be obsoleted by
 the new origin api discussed here:

 https://groups.google.com/forum/#!topic/django-developers/VFBLAoPSplI

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.e53b119305e871369de271d100cc1d65%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21012: Provide shared "caches" dict to avoid creating multiple cache class instances.

2015-01-17 Thread Django

#21012: Provide shared "caches" dict to avoid creating multiple cache class
instances.
-+-
 Reporter:  FunkyBob |Owner:  aaugustin
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Core (Cache system)  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"d038c547b5ce585cbf9ef5bb7e5298f52e4a243b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d038c547b5ce585cbf9ef5bb7e5298f52e4a243b"
 Removed django.core.cache.get_cache() per deprecation timeline; refs
 #21012.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.f487034fd3b231c7c66d0f2d1b449295%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #17262: Refactor the implementations of tzinfo classes

2015-01-17 Thread Django

#17262: Refactor the implementations of tzinfo classes
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Utilities|  Version:  1.4
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  timezone tzinfo  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"1b0365ad34151f266fe3faecb4edf31a51a8642c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1b0365ad34151f266fe3faecb4edf31a51a8642c"
 Removed django.utils.tzinfo per deprecation timeline; refs #17262.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.87da848a5aef1ba91df341959885e32c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #18681: get_fieldsets not hooked in properly

2015-01-17 Thread Django

#18681: get_fieldsets not hooked in properly
---+
 Reporter:  msopacua   |Owner:  loic84
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Tim Graham ):

 In [changeset:"d4ee6cda5802adc5a38d266ccebe78fb67066179"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d4ee6cda5802adc5a38d266ccebe78fb67066179"
 Removed ModelAdmin.declared_fieldsets per deprecation timeline; refs
 #18681.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.670b2baf3782e9e885ce2c1d89ebacb4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24164: Oracle GIS geoapp extent test failure

2015-01-17 Thread Django

#24164: Oracle GIS geoapp extent test failure
---+-
 Reporter:  timgraham  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  GIS|  Version:  1.8alpha1
 Severity:  Normal |   Resolution:
 Keywords:  oracle | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by shaib):

 The failing SQL is:
 {{{#!sql
 SELECT SDO_AGGR_MBR("__COL1") FROM (
SELECT * FROM (
   SELECT "_SUB".*, ROWNUM AS "_RN" FROM (
  SELECT "GEOAPP_CITY"."ID" AS Col1, "GEOAPP_CITY"."NAME" AS Col2,
 SDO_UTIL.TO_WKTGEOMETRY("GEOAPP_CITY"."POINT") AS Col3,
 SDO_UTIL.TO_WKTGEOMETRY("GEOAPP_CITY"."POINT") AS "__COL1"
  FROM "GEOAPP_CITY"
   ) "_SUB" WHERE ROWNUM <= 3
) WHERE "_RN" > 0) subquery
 }}}

 An earlier query which succeeds in that test is
 {{{#!sql
 SELECT SDO_UTIL.TO_WKTGEOMETRY(SDO_AGGR_MBR("GEOAPP_CITY"."POINT")) AS
 "POINT__EXTENT"
 FROM "GEOAPP_CITY"
 }}}
 So it seems the problem is that `SDO_UTIL.TO_WKTGEOMETRY` is being called
 "too soon"; it apparently needs to be called on geometric result values in
 order to return the right type to the user, but here it is applied to an
 intermediate result (before it is passed to the aggregate).

 In particular, this means there is a real problem here, not just a testing
 problem; skipping is the wrong solution.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.c7cfa25de239a9702da5b2df43e14918%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20766: Deprecate fastcgi support

2015-01-17 Thread Django

#20766: Deprecate fastcgi support
--+
 Reporter:  timo  |Owner:  timo
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  fastcgi   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"41f0d3d3bc8b0a6831530e1176c6415f9ba45b0b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="41f0d3d3bc8b0a6831530e1176c6415f9ba45b0b"
 Removed FastCGI support per deprecation timeline; refs #20766.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.098e5a6f12202a5eb4e2403be9fb3ab9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #18659: Remove `request.REQUEST`

2015-01-17 Thread Django

#18659: Remove `request.REQUEST`
--+
 Reporter:  aaugustin |Owner:  bouke
 Type:  Cleanup/optimization  |   Status:  closed
Component:  HTTP handling |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"37b7776a015102e97b9bdd64d88c732883ff9989"]:
 {{{
 #!CommitTicketReference repository=""
 revision="37b7776a015102e97b9bdd64d88c732883ff9989"
 Removed django.utils.datastructures.MergeDict per deprecation timeline;
 refs #18659.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.2f064d381728cac9752f6562cd549e75%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #18659: Remove `request.REQUEST`

2015-01-17 Thread Django

#18659: Remove `request.REQUEST`
--+
 Reporter:  aaugustin |Owner:  bouke
 Type:  Cleanup/optimization  |   Status:  closed
Component:  HTTP handling |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"75f107b8842dfc890ddd65262bd09ca87c3a15be"]:
 {{{
 #!CommitTicketReference repository=""
 revision="75f107b8842dfc890ddd65262bd09ca87c3a15be"
 Removed request.REQUEST per deprecation timeline; refs #18659.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.f651fe8cfde0fb305482c0835bbf4221%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21351: memoize function needs tests and improvements

2015-01-17 Thread Django

#21351: memoize function needs tests and improvements
--+
 Reporter:  EvilDMP   |Owner:  bouke
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Utilities |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"61ad1ea92b1f4df992b0ef1dcc7c781da2413815"]:
 {{{
 #!CommitTicketReference repository=""
 revision="61ad1ea92b1f4df992b0ef1dcc7c781da2413815"
 Removed django.utils.functional.memoize per deprecation timeline.

 refs #21351.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.534c4195e3c69f2632cb21548a587ad6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #17627: contrib.admin.util is misnamed

2015-01-17 Thread Django

#17627: contrib.admin.util is misnamed
--+
 Reporter:  PaulM |Owner:  lukegb
 Type:  Cleanup/optimization  |   Status:  closed
Component:  contrib.admin |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"9ce36512fa925231b0496cc10f7d114c069c7c06"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9ce36512fa925231b0496cc10f7d114c069c7c06"
 Removed backwards compatibility shims for "util" modules per deprecation
 timeline.

 refs #17627.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.ea4b3aca89b63b5b0b067fbbbabf73d9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24165: add request.messages attribute

2015-01-17 Thread Django

#24165: add request.messages attribute
--+--
 Reporter:  collinanderson|Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.messages  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by timgraham):

 Did you research the decision about putting `request.user` where it is?
 I'm not sure the rationale of setting attributes on the `request` instead
 of using context processors is a good one. If this is simply an effort to
 avoid context processors, have you considered other alternatives like a
 template tag?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.cdb12c5e4fd81acb7ca2d57956cc7ee7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22232: Template extends tag can cause recursion

2015-01-17 Thread Django

#22232: Template extends tag can cause recursion
-+-
 Reporter:  galedragon   |Owner:  darkryder
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by MarkusH):

 * needs_better_patch:  1 => 0
 * stage:  Accepted => Ready for checkin


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.8fa8584cb065afc87f7db5703922d8e6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24154: Fix check_aggregate_support for Expressions

2015-01-17 Thread Django

#24154: Fix check_aggregate_support for Expressions
-+-
 Reporter:  jarshwah |Owner:  jarshwah
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.8alpha1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 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 claudep):

 * type:  Uncategorized => Cleanup/optimization


Comment:

 I've just complemented a GIS test in
 
https://github.com/django/django/commit/d69ecf922ddf6d4e3698e0dfd42d9ae387df182c

 If this still passes after your patch, I'm confirming the RFC status 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.9c5969b45973c4e90ef1042f3efab601%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #24168: TemplateResponse and TemplateView cannot select a specific template engine

2015-01-17 Thread Django

#24168: TemplateResponse and TemplateView cannot select a specific template 
engine
-+-
   Reporter:  aaugustin  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Template   |Version:  master
  system |   Keywords:  multiple-template-
   Severity:  Normal |  engines 1.8
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 `TemplateResponse` should gain an `engine` argument.

 `TemplateResponseMixin` should gain an `engine` attribute.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.42c63ac9da1b43a38e8ddde4c8a48d50%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23299: Add some interoperability to _() function calls parsing in templatize function.

2015-01-17 Thread Django

#23299: Add some interoperability to _() function calls parsing in templatize
function.
-+-
 Reporter:  niwibe   |Owner:  aaugustin
 Type:  New feature  |   Status:  assigned
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  template-refactor| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.ad5bd816b3390fba16fa58dd38270eae%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23299: Add some interoperability to _() function calls parsing in templatize function.

2015-01-17 Thread Django

#23299: Add some interoperability to _() function calls parsing in templatize
function.
--+
 Reporter:  niwibe|Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Internationalization  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  template-refactor | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by aaugustin):

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


Comment:

 Reopening because I will include this as a stopgap solution in Django 1.8
 until #24167 can be tackled.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.6b841802800d7f53a6d3276bc34b6617%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20811: Makemessages currently does not support alternative template languages

2015-01-17 Thread Django

#20811: Makemessages currently does not support alternative template languages
--+
 Reporter:  cordery@… |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  Internationalization  |  Version:  master
 Severity:  Normal|   Resolution:  wontfix
 Keywords:  makemessages i18n | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by aaugustin):

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


Comment:

 Given the implementation of multiple template engines that landed in
 Django 1.8, Django template loaders aren't the right point to fix this
 problem anymore. For this reason I'm closing the ticket.

 Unfortunately internationalization didn't make it in Django 1.8. Further
 work is tracked in 24167#.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/075.efa5f61779bb848b7682a90095155df9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24167: Backend-agnostic template internationalization

2015-01-17 Thread Django

#24167: Backend-agnostic template internationalization
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:  New feature  |   Status:  assigned
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  multiple-template-   | Triage Stage:  Accepted
  engines|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 Since this ticket describes a new feature and wasn't implemented before
 1.8 alpha, it will make it into 1.9 at best. I will use the approach
 described in #23299 in 1.8 because it's less invasive.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.388801d244ec65b16fba74c429cef3f4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #24167: Backend-agnostic template internationalization

2015-01-17 Thread Django

#24167: Backend-agnostic template internationalization
-+-
   Reporter:  aaugustin  |  Owner:  nobody
   Type:  New| Status:  new
  feature|
  Component: |Version:  master
  Internationalization   |   Keywords:  multiple-template-
   Severity:  Normal |  engines
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Currently `makemessages` calls `django.utils.translation.templatize` to
 turn Django templates into something gettext understands. There is no way
 for alternate template engines to hook into the string extraction
 machinery.

 This supersedes #20811 and #23299.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.61ebd9e954135376e3014a168a0b4e70%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24167: Backend-agnostic template internationalization

2015-01-17 Thread Django

#24167: Backend-agnostic template internationalization
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:  New feature  |   Status:  assigned
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  multiple-template-   | Triage Stage:  Accepted
  engines|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.be9ea7adeff60a9fb8d0d8975ca0158c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24166: Provide plain alternatives to common built-in template tags, filters or context processors

2015-01-17 Thread Django

#24166: Provide plain alternatives to common built-in template tags, filters or
context processors
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  multiple-template-   | Triage Stage:  Accepted
  engines 1.8|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * owner:  nobody => aaugustin
 * status:  new => assigned
 * stage:  Unreviewed => Accepted


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.c91c1f688ea9aea2472872209c4eb902%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #24166: Provide plain alternatives to common built-in template tags, filters or context processors

2015-01-17 Thread Django

#24166: Provide plain alternatives to common built-in template tags, filters or
context processors
-+-
   Reporter:  aaugustin  |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |
  Component:  Template   |Version:  master
  system |   Keywords:  multiple-template-
   Severity:  Normal |  engines 1.8
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Common functionality that is provided through DTL-specific APIs such as
 `{% static ... %}` should be made available through plain Python functions
 for use in non-DTL engines.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.61b15b602ffc02cfaa352eedff9e8940%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

56 matches

Mail list logo