Re: [Django] #22349: RawQuerySet doesn't implement __len__, __bool__

[Django]

#22349: RawQuerySet doesn't implement __len__, __bool__
-+-
 Reporter:  cdestigter   |Owner:
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by loic84):

 Dunno if it's by design, but `RawQuerySet` and  `QuerySet` operate vastly
 differently as there is no such thing as an "evaluated" `RawQuerySet`:

 {{{
 list(queryset)
 with assertNumQueries(1)
 for i in range(10):
 queryset[0]

 list(raw_queryset)
 with assertNumQueries(10)
 for i in range(10):
 raw_queryset[0]
 }}}

 This fundamental difference makes having a shared ancestor impractical.

 With that in mind, I think adding `__len__` would be a nasty footgun, if
 you only want the number of rows, you can write a `COUNT` SQL query, if
 you want the count and the result, then you should definitely store the
 result in a list to avoid a second query.

 Of course we could make `RawQuerySet` maintain an internal cache akin to
 `QuerySet`, but that'd have to be a ticket in its own right.

-- 
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.3256cfb86d962b16647d00727eba58c3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22298: Rename Media to Static

[Django]

#22298: Rename Media to Static
--+
 Reporter:  aaugustin |Owner:  vlal
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Forms |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by vlal):

 * owner:  nobody => vlal
 * 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.9a305157f42c8b0c7e5f6dca337955c8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22349: RawQuerySet doesn't implement __len__, __bool__

[Django]

#22349: RawQuerySet doesn't implement __len__, __bool__
-+-
 Reporter:  cdestigter   |Owner:
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by ryanmrubin):

 * status:  assigned => new
 * owner:  ryanmrubin =>


-- 
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.0a905225955a57ac99d53d840d521663%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22349: RawQuerySet doesn't implement __len__, __bool__

[Django]

#22349: RawQuerySet doesn't implement __len__, __bool__
-+-
 Reporter:  cdestigter   |Owner:
 Type:  Bug  |  ryanmrubin
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by ryanmrubin):

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


-- 
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.e762da941e6e863806046efc18aa11ea%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21649: Add session signing based on the value of the user's password

[Django]

#21649: Add session signing based on the value of the user's password
--+
 Reporter:  timo  |Owner:  timo
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  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 timo):

 * needs_better_patch:  1 => 0


Comment:

 Here's an [https://github.com/django/django/pull/2494 updated PR] that
 uses the middleware approach suggested above.

-- 
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.1fbcc49ee6f5e0fe9a88a8844fd37bd0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21596: Add method to formset to add a form

[Django]

#21596: Add method to formset to add a form
-+--
 Reporter:  nickname123  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  1.6
 Severity:  Normal   |   Resolution:  wontfix
 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 nickname123):

 Replying to [comment:5 timo]:
 > Why not the solution I proposed?

 It does not seem intuitive to me, but it seems like your proposed solution
 would work similarly in some situations but not all.

 My major problem with it is that it requires all formsets to be created
 dynamically when needed and you can only specify to include an extra form
 initially when the factory function is called.  This seems like a very
 complicated path to take just to avoid adding a small change to the
 formset class.  Maybe this is a bad comparison, but it seems kind of like
 having a list [] that you must specify how many elements are required in
 advance vs having an append method.


 {{{
 def add_form(self, **kwargs):
 self.forms.append(self._construct_form(self.total_form_count(),
 **kwargs))
 self.forms[-1].is_bound = False
 self.data = self.data.copy()
 self.data['%s-%s' % (self.management_form.prefix,
 TOTAL_FORM_COUNT)] = self.management_form.cleaned_data[TOTAL_FORM_COUNT] +
 1
 }}}

 Note that TOTAL_FORM_COUNT is a key string imported from
 django.forms.formsets, not something I calculate elsewhere.

 My change to the formset class only needs to add 5 lines if the
 comments/verboseness isn't important.  And it makes adding forms to an
 existing formset possible and much more flexible.  The is_valid() check
 probably shouldn't be added to the main formset class.  That was just for
 a particular use case I wrote the mixin for.

 I prefer to call the formset_factory method once and use it like a form
 class definition that I import elsewhere for readability.  My preference
 probably isn't important to Django, but I figured I would mention it.

 I.e.

 {{{
 ...
 OptionalPhoneNumberModelFormset = modelformset_factory(PhoneNumber,
 form=PhoneNumberModelForm, formset=EntryOnlyAddableFormSet)
 FirstRequiredPhoneNumberModelFormset = modelformset_factory(PhoneNumber,
 form=PhoneNumberModelForm, formset=FirstRequiredEntryOnlyAddableFormSet)
 ...
 }}}

 For another case where the add_form method would be preferable see:
 https://code.djangoproject.com/ticket/18830

 I am using a version of russelm's formcontainer that I have been working
 on and it is much easier to use the "add_form" method than recreating the
 formcontainer and its children when an additional form needs to be added
 to one of the child formsets.

-- 
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.7e0f37d5d02f1de280da69cfbcae04ec%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22259: Per row result for dumpdata

[Django]

#22259: Per row result for dumpdata
-+-
 Reporter:  Gwildor  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Gwildor):

 Replying to [comment:2 anubhav9042]:
 > As mentioned in #22251, this is implemented in #5423. What else is
 required?
 What I'm talking about is a whole other way of representing the data. As
 it is now, one big JSON object is created with all the model instances in
 it, like so:
 {{{
 [
 {
 'model': 'Foo',
 'pk': 1,
 'fields': {***},
 },
 {
 'model': 'Foo',
 'pk': 2,
 'fields': {***},
 },
 ]
 }}}

 What I'm going at, is changing this so one JSON object is created and
 streamed to the output per model instance, resulting in output along the
 lines as so:

 {{{
 {'model': 'Foo', 'pk': 1, 'fields': {***}}
 {'model': 'Foo', 'pk': 2, 'fields': {***}}
 {'model': 'Bar', 'pk': 1, 'fields': {***}}
 }}}

 This, in my opinion, has the big advantage that the script that loads the
 data again, does not have to load all the data into memory before it can
 start with processing the data.

 At the moment, you have to do something like this (of course you can read
 buffered):

 {{{
 #!python
 with open(args[0], 'rb') as f:
 fc = f.read()
 data = json.loads(fc)

 for row in data:
 process(row)
 }}}

 But when the output option is added the way I proposed, you can do this:

 {{{
 #!python
 with open(args[0], 'rb') as f:
 for row in f.readline():
 row = json.loads(row)
 process(row)
 }}}

 This way, you don't have to parse one big JSON object.

 Another but way smaller advantage is that if the dumpdata command crashes,
 you would still have some output to use for testing or developing purposes
 while you wait while running the dumpdata command again. As it is now, I
 believe you are left with nothing (never seen an even incomplete JSON
 object printed in the terminal, just the error and nothing more). Although
 this is a small and arguable advantage, I believe this will have a
 positive effect on the user friendliness of using the command.

 I think the best way to progress (if we want this) is to add a flag for
 the dumpdata command which enables this behaviour, and add support for it
 for the loaddata command by making a reasonable guess based on the reading
 the first line, falling back to the old behaviour if there is no
 certainty. I fear that other tools have the options to either do the same
 to support both formats, or simply support one and not the other (which
 will probably be the current format unless the new format turns out to be
 very popular).

-- 
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.d429c49cabde00685c494c11fda1fab9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22354: ModelForm has_changed on ChoiceFields reports always True if an initial argument is given

[Django]

#22354: ModelForm has_changed on ChoiceFields reports always True if an initial
argument is given
+--
 Reporter:  s3h10r  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Forms   |  Version:  1.6
 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 s3h10r):

 @claudep: Thanks! I wasn't aware of this / just stumbled into the pitfall
 of changed behaviour (could not find much about {{{.has_changed()}}} in
 the docs). TypedChoiceField works fine.

-- 
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.f3ee02382993237507645b935ecf9312%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22257: Write to specified file for dumpdata

[Django]

#22257: Write to specified file for dumpdata
-+-
 Reporter:  Gwildor  |Owner:
 Type:  New feature  |  anubhav9042
Component:  Core (Management |   Status:  closed
  commands)  |  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 Gwildor):

 Thanks everyone for the quick implementation :)

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.b19412f881ee2e6f593c1458df83f61c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22216: There is no mention of non_field_errors on the forms api page

[Django]

#22216: There is no mention of non_field_errors on the forms api page
--+
 Reporter:  anonymous |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timo):

 * has_patch:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.ca9d9c88345e3eddaaed97fc8b74ddc7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22355: Humanize timedelta objects in templates

[Django]

#22355: Humanize timedelta objects in templates
-+-
 Reporter:  atmb4u   |Owner:
 Type:  New feature  |   Status:  new
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  templates, filter,   | Triage Stage:
  timedelta, humanize, timesince |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by atmb4u):

 * cc: atmb4u (added)
 * needs_better_patch:   => 0
 * 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/064.097c06890ee8062378b0d00fddb12c35%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22355: Humanize timedelta objects in templates

[Django]

#22355: Humanize timedelta objects in templates
-+-
 Reporter:  atmb4u   |  Owner:
 Type:  New  | Status:  new
  feature|Version:  master
Component:   |   Keywords:  templates, filter, timedelta,
  Utilities  |  humanize, timesince
 Severity:  Normal   |  Has patch:  1
 Triage Stage:   |  UI/UX:  0
  Unreviewed |
Easy pickings:  0|
-+-
 A filter for humanizing datetime.timedelta objects for templates utilizing
 on the timesince function already existing. Tests and Documentation
 included in the patch.

 {{time_delta|delta}}

 will give the humanized version of timedelta object. Follows the same
 pattern as of timesince in defaultfilters.py

 Eg. 4 weeks, 2 days

-- 
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/049.30697be7c3c9048d7ab68f82a6840810%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22354: ModelForm has_changed on ChoiceFields reports always True if an initial argument is given

[Django]

#22354: ModelForm has_changed on ChoiceFields reports always True if an initial
argument is given
+--
 Reporter:  s3h10r  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Forms   |  Version:  1.6
 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 claudep):

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


Comment:

 I can reproduce what you describe. However, the proper field to use here
 should be a `TypedChoiceField(..., coerce=int)`. I'll keep the ticket open
 to see if another core developer has another opinion on the matter, or if
 something should be added in the documentation.

-- 
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.3b092bb918e07e7a8b36467fbf910728%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] f356b6: Increased memoization cache size for language code...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: f356b6ecc3fe15634d504690c1793460e5fe9bee
  
https://github.com/django/django/commit/f356b6ecc3fe15634d504690c1793460e5fe9bee
  Author: Aymeric Augustin 
  Date:   2014-03-29 (Sat, 29 Mar 2014)

  Changed paths:
M django/utils/translation/trans_real.py

  Log Message:
  ---
  Increased memoization cache size for language codes.

There may be more than 100 (default maxsize) commonly seen xx-yy values
on some sites. The additional memory consumption isn't significant.

Also added a comment explaining why this cache must have a maxsize.


-- 
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/53371583460d5_7f825ddd38604c7%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 18b2c0: [1.7.x] Increased memoization cache size for langu...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 18b2c03ea31027d2f102df3c6b173cb6e63da52d
  
https://github.com/django/django/commit/18b2c03ea31027d2f102df3c6b173cb6e63da52d
  Author: Aymeric Augustin 
  Date:   2014-03-29 (Sat, 29 Mar 2014)

  Changed paths:
M django/utils/translation/trans_real.py

  Log Message:
  ---
  [1.7.x] Increased memoization cache size for language codes.

There may be more than 100 (default maxsize) commonly seen xx-yy values
on some sites. The additional memory consumption isn't significant.

Also added a comment explaining why this cache must have a maxsize.

Backport of f356b6e from master.


-- 
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/5337157ede4f6_d64bbdd34611b6%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22257: Write to specified file for dumpdata

[Django]

#22257: Write to specified file for dumpdata
-+-
 Reporter:  Gwildor  |Owner:
 Type:  New feature  |  anubhav9042
Component:  Core (Management |   Status:  closed
  commands)  |  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 anubhav9042):

 Thanks for 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/065.6b6d0542de80f211a36db2de6748a23a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22334: Postgis version check discards dev versions

[Django]

#22334: Postgis version check discards dev versions
+--
 Reporter:  xowap   |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  GIS |  Version:  1.6
 Severity:  Normal  |   Resolution:  worksforme
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+--

Comment (by Claude Paroz ):

 In [changeset:"e819a3cd622fe9404b1f5ea7891906c4cdabbb12"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e819a3cd622fe9404b1f5ea7891906c4cdabbb12"
 Skipped PostGIS version tests when psycopg2 not installed

 Refs #22334. Thanks Tim Graham for spotting the issue.
 }}}

-- 
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.e647fe1b404bea0e2750ac5b4906f188%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] e819a3: Skipped PostGIS version tests when psycopg2 not in...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e819a3cd622fe9404b1f5ea7891906c4cdabbb12
  
https://github.com/django/django/commit/e819a3cd622fe9404b1f5ea7891906c4cdabbb12
  Author: Claude Paroz 
  Date:   2014-03-29 (Sat, 29 Mar 2014)

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

  Log Message:
  ---
  Skipped PostGIS version tests when psycopg2 not installed

Refs #22334. Thanks Tim Graham for spotting the issue.


-- 
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/5337106d19330_1849687d389852e%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21565: values() and values_list() don't work when datetime fields are specified and a GeoManager is used

[Django]

#21565: values() and values_list() don't work when datetime fields are specified
and a GeoManager is used
---+
 Reporter:  brett_energysavvy  |Owner:
 Type:  Bug|   Status:  new
Component:  GIS|  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by claudep):

 The problem is caused by `resolve_columns` in
 `django/contrib/gis/db/models/sql/compiler.py`, which calls
 `self.query.convert_values` if `self.query.geo_values` is `True`. However,
 the date value is already converted in a proper Python `Datetime` at the
 start of the method. It happens only in Spatialite because the basic
 `convert_values` don't touch date/time values, only the `sqlite3` backend
 does. I see two ways forward:
 1. Just test in `parse_datetime` that the value is not already a
 `Datetime` object.
 2. Try to be more clever at the `resolve_columns` level to only call
 `convert_values` on geometry values (ORM knowledge required).

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.a7417944a6f8cdc1b2cb8e70b6b4d82f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22354: ModelForm has_changed on ChoiceFields reports always True if an initial argument is given

[Django]

#22354: ModelForm has_changed on ChoiceFields reports always True if an initial
argument is given
+
 Reporter:  s3h10r  |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Forms   |Version:  1.6
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 example model + form:


 {{{
 class Host(models.Model):
 DM=0
 PP=1
 KIND_CHOICES = (
 (DM, 'native mpio'),
 (PP, 'PowerPath'),
 )
 mpio = models.IntegerField(choices=KIND_CHOICES, default=DM)

 class HostForm(ModelForm):
 DM=0
 PP=1
 KIND_CHOICES = (
 (DM, 'native mpio'),
 (PP, 'PowerPath'),
 )

 mpio = forms.ChoiceField(choices=KIND_CHOICES, label="Multipathing
 Software", required=True, initial=DM)

 class Meta:
 model = Host
 }}}

 testcase:

 {{{
 from formprob16.models import Host
 from formprob16.forms import HostForm


 fm = HostForm() # unbound
 fm = HostForm({'mpio' : 0 }) # bound

 print "has_changed:", fm.has_changed()
 print "changed_data:", fm.changed_data
 }}}

 output in Django 1.5.5 (and 1.4) is as expected:

 {{{
 >>> has_changed: False
 >>> changed_data: []
 }}}

 output in Django 1.6.2 says the form-content was changed:

 {{{
 >>> has_changed: True
 >>> changed_data: ['mpio']
 }}}

 If the initial argument is not used / the Form is just derived from the
 model like in the following example:

 {{{
 class HostForm(ModelForm):

 class Meta:
 model = Host
 }}}

 it works fine in 1.6.2 too, but i think that's not the expected behaviour
 (or: at least not expected by 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 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/049.241098c33071fb8a51ce7c693242c7aa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22334: Postgis version check discards dev versions

[Django]

#22334: Postgis version check discards dev versions
+--
 Reporter:  xowap   |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  GIS |  Version:  1.6
 Severity:  Normal  |   Resolution:  worksforme
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+--
Changes (by claudep):

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


Comment:

 Thanks for the tests!

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.6662f56b0b453d416727ff6c014dd4bd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22334: Postgis version check discards dev versions

[Django]

#22334: Postgis version check discards dev versions
+
 Reporter:  xowap   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  GIS |  Version:  1.6
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+

Comment (by Claude Paroz ):

 In [changeset:"88f1e3d93d8f48a302ff75b1936e471c4a52fff9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="88f1e3d93d8f48a302ff75b1936e471c4a52fff9"
 Unit testing Postgis version check

 Refs #22334.
 }}}

-- 
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.1c45d084492782be25c39c6dadb64fe4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 88f1e3: Unit testing Postgis version check

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 88f1e3d93d8f48a302ff75b1936e471c4a52fff9
  
https://github.com/django/django/commit/88f1e3d93d8f48a302ff75b1936e471c4a52fff9
  Author: Rémy Sanchez 
  Date:   2014-03-29 (Sat, 29 Mar 2014)

  Changed paths:
A django/contrib/gis/tests/tests.py

  Log Message:
  ---
  Unit testing Postgis version check

Refs #22334.


-- 
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/5336dac965134_c281395d40295af%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21858: Clarify 1.6 release notes regarding ManyToManyField help_text

[Django]

#21858: Clarify 1.6 release notes regarding ManyToManyField help_text
---+
 Reporter:  lee@…  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.6
 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:"c139e3e0a0d190b9b06e0cf2ec0c0c409ca978c3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c139e3e0a0d190b9b06e0cf2ec0c0c409ca978c3"
 [1.7.x] Fixed #21858 -- Clarified 1.6 release note regarding M2M help text
 changes.

 Thanks lee at semel.net for the report.

 Backport of f30e6590f4 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 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.7e8b18063cc3299aeae7ed4cfc7b91f4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21858: Clarify 1.6 release notes regarding ManyToManyField help_text

[Django]

#21858: Clarify 1.6 release notes regarding ManyToManyField help_text
---+
 Reporter:  lee@…  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.6
 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:"30ba506e978b31e16676b8da7b5e6cd8b4c4d8d4"]:
 {{{
 #!CommitTicketReference repository=""
 revision="30ba506e978b31e16676b8da7b5e6cd8b4c4d8d4"
 [1.6.x] Fixed #21858 -- Clarified 1.6 release note regarding M2M help text
 changes.

 Thanks lee at semel.net for the report.

 Backport of f30e6590f4 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 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.112fd0048f5795377c836d2c93d2e026%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 30ba50: [1.6.x] Fixed #21858 -- Clarified 1.6 release note...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 30ba506e978b31e16676b8da7b5e6cd8b4c4d8d4
  
https://github.com/django/django/commit/30ba506e978b31e16676b8da7b5e6cd8b4c4d8d4
  Author: Tim Graham 
  Date:   2014-03-29 (Sat, 29 Mar 2014)

  Changed paths:
M docs/releases/1.6.txt

  Log Message:
  ---
  [1.6.x] Fixed #21858 -- Clarified 1.6 release note regarding M2M help text 
changes.

Thanks lee at semel.net for the report.

Backport of f30e6590f4 from master


-- 
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/5336d76ab4165_7f825ddd385802f%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] c139e3: [1.7.x] Fixed #21858 -- Clarified 1.6 release note...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: c139e3e0a0d190b9b06e0cf2ec0c0c409ca978c3
  
https://github.com/django/django/commit/c139e3e0a0d190b9b06e0cf2ec0c0c409ca978c3
  Author: Tim Graham 
  Date:   2014-03-29 (Sat, 29 Mar 2014)

  Changed paths:
M docs/releases/1.6.txt

  Log Message:
  ---
  [1.7.x] Fixed #21858 -- Clarified 1.6 release note regarding M2M help text 
changes.

Thanks lee at semel.net for the report.

Backport of f30e6590f4 from master


-- 
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/5336d769dfb53_167ce19d442087d%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21858: Clarify 1.6 release notes regarding ManyToManyField help_text

[Django]

#21858: Clarify 1.6 release notes regarding ManyToManyField help_text
---+
 Reporter:  lee@…  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.6
 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 Tim Graham ):

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


Comment:

 In [changeset:"f30e6590f40c8b008cbe5833579fca4fd93ecc61"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f30e6590f40c8b008cbe5833579fca4fd93ecc61"
 Fixed #21858 -- Clarified 1.6 release note regarding M2M help text
 changes.

 Thanks lee at semel.net 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 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.025388002aaafb45fda25c4ce163e19c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] f30e65: Fixed #21858 -- Clarified 1.6 release note regardi...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: f30e6590f40c8b008cbe5833579fca4fd93ecc61
  
https://github.com/django/django/commit/f30e6590f40c8b008cbe5833579fca4fd93ecc61
  Author: Tim Graham 
  Date:   2014-03-29 (Sat, 29 Mar 2014)

  Changed paths:
M docs/releases/1.6.txt

  Log Message:
  ---
  Fixed #21858 -- Clarified 1.6 release note regarding M2M help text changes.

Thanks lee at semel.net for the report.


-- 
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/5336d75259c31_db9134bd44143bb%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22329: Use label_tag() in admin auth templates to remove hardcoded class='required'

[Django]

#22329: Use label_tag() in admin auth templates to remove hardcoded
class='required'
-+-
 Reporter:  timo |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  contrib.admin|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"ed4c2e1c0d9e43c09767b02fd8b4bd74a5dfe512"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ed4c2e1c0d9e43c09767b02fd8b4bd74a5dfe512"
 Fixed #22329 -- Used label_tag() in some admin auth templates.

 refs #17922.
 }}}

-- 
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.ce615fa67a6be87e9aeb41ada0f79ef1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #17922: Add default "required" css classes to form labels

[Django]

#17922: Add default "required" css classes to form labels
-+---
 Reporter:  hanson2010   |Owner:  anubhav9042
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  sprint2013   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+---

Comment (by Tim Graham ):

 In [changeset:"ed4c2e1c0d9e43c09767b02fd8b4bd74a5dfe512"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ed4c2e1c0d9e43c09767b02fd8b4bd74a5dfe512"
 Fixed #22329 -- Used label_tag() in some admin auth templates.

 refs #17922.
 }}}

-- 
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.d7753fd1986593e7b2a52d4ec3f79da0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] ed4c2e: Fixed #22329 -- Used label_tag() in some admin aut...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ed4c2e1c0d9e43c09767b02fd8b4bd74a5dfe512
  
https://github.com/django/django/commit/ed4c2e1c0d9e43c09767b02fd8b4bd74a5dfe512
  Author: Tim Graham 
  Date:   2014-03-29 (Sat, 29 Mar 2014)

  Changed paths:
M django/contrib/admin/forms.py
M django/contrib/admin/sites.py
M django/contrib/admin/templates/admin/auth/user/change_password.html
M django/contrib/admin/templates/admin/login.html
M django/contrib/admin/templates/registration/password_change_form.html
M django/contrib/auth/forms.py

  Log Message:
  ---
  Fixed #22329 -- Used label_tag() in some admin auth templates.

refs #17922.


-- 
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/5336c546c4f8d_a2d8a7d341791e%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 2cc884: Removed unused imports.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2cc8840397bff8e5f99a7a2486dd295c42769e65
  
https://github.com/django/django/commit/2cc8840397bff8e5f99a7a2486dd295c42769e65
  Author: Tim Graham 
  Date:   2014-03-29 (Sat, 29 Mar 2014)

  Changed paths:
M django/contrib/gis/gdal/geometries.py
M django/contrib/gis/geos/tests/test_io.py
M django/contrib/gis/tests/relatedapp/tests.py

  Log Message:
  ---
  Removed unused imports.


-- 
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/5336c292e28d0_bffc83d4055234%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 0f1f12: Confirmed GEOS 3.4 support

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 0f1f12c5641acfbbf1fe58b0e6dd6f755fbbe61e
  
https://github.com/django/django/commit/0f1f12c5641acfbbf1fe58b0e6dd6f755fbbe61e
  Author: Claude Paroz 
  Date:   2014-03-29 (Sat, 29 Mar 2014)

  Changed paths:
M django/contrib/gis/tests/geo3d/tests.py
M django/contrib/gis/tests/relatedapp/tests.py
M docs/ref/contrib/gis/install/geolibs.txt

  Log Message:
  ---
  Confirmed GEOS 3.4 support


  Commit: e62dea9ad5a4695cbcdec3c7e51b5914d0b2485d
  
https://github.com/django/django/commit/e62dea9ad5a4695cbcdec3c7e51b5914d0b2485d
  Author: Claude Paroz 
  Date:   2014-03-29 (Sat, 29 Mar 2014)

  Changed paths:
M django/contrib/gis/tests/geoapp/tests.py
M docs/ref/contrib/gis/install/geolibs.txt

  Log Message:
  ---
  Confirmed Spatialite 4 support


  Commit: c6ffa4cab6d9dd0b54386bc6cafe6e8658b3fb2a
  
https://github.com/django/django/commit/c6ffa4cab6d9dd0b54386bc6cafe6e8658b3fb2a
  Author: Claude Paroz 
  Date:   2014-03-29 (Sat, 29 Mar 2014)

  Changed paths:
M docs/ref/contrib/gis/install/geolibs.txt

  Log Message:
  ---
  Added note in geo library docs


  Commit: c5d1df70a415ecbb0e8f00fe76122cb2ed100d53
  
https://github.com/django/django/commit/c5d1df70a415ecbb0e8f00fe76122cb2ed100d53
  Author: Claude Paroz 
  Date:   2014-03-29 (Sat, 29 Mar 2014)

  Changed paths:
M django/contrib/gis/geos/geometry.py
M django/contrib/gis/geos/prototypes/errcheck.py
M django/contrib/gis/geos/prototypes/topology.py
M django/contrib/gis/geos/tests/test_geos.py
M django/contrib/gis/geos/tests/test_io.py
M django/contrib/gis/tests/distapp/tests.py
M docs/ref/contrib/gis/install/geolibs.txt
M docs/releases/1.8.txt

  Log Message:
  ---
  Dropped support for GEOS 3.1


  Commit: 41903d025a6ea79ccc4cc38a398b1286ef6e1319
  
https://github.com/django/django/commit/41903d025a6ea79ccc4cc38a398b1286ef6e1319
  Author: Claude Paroz 
  Date:   2014-03-29 (Sat, 29 Mar 2014)

  Changed paths:
M django/contrib/gis/admin/options.py
M django/contrib/gis/forms/widgets.py
M django/contrib/gis/gdal/geometries.py
M docs/ref/contrib/gis/install/geolibs.txt
M docs/releases/1.8.txt

  Log Message:
  ---
  Dropped support for GDAL 1.6


Compare: https://github.com/django/django/compare/21f208e66e64...41903d025a6e

-- 
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/53369bfa30bcb_b45d3dd44754e%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22350: Django 1.7 migration files do not support Python 3.2

[Django]

#22350: Django 1.7 migration files do not support Python 3.2
-+--
 Reporter:  treyhunner   |Owner:  loic84
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by loic84):

 * has_patch:  0 => 1


Comment:

 I'm not too fond of it, but here is a tentative patch, note the generated
 migrations are hideous.

 POC https://github.com/loic/django/tree/ticket22350.

-- 
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.e908f1b21473b296cc8b0f6a809154d1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.