date:20151021

[Django] #25589: startapp command should support unicode name

2015-10-21 Thread Django

#25589: startapp command should support unicode name
+
 Reporter:  sih4sing5hong5  |  Owner:  nobody
 Type:  Uncategorized   | Status:  new
Component:  Uncategorized   |Version:  1.8
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 In python3, variable/package/filename is ok with begining with Unicode
 character.
 But the `startapp` command cannot do that.

   python manage.py startapp 維護團隊
   CommandError: '維護團隊' is not a valid app name. Please make sure the
 name begins with a letter or underscore.

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

Re: [Django] #13879: method_decorator doesn't supports decorators with arguments

2015-10-21 Thread Django

#13879: method_decorator doesn't supports decorators with arguments
-+-
 Reporter:  marinho  |Owner:
 Type:  New feature  |   Status:  new
Component:  Utilities|  Version:  1.2
 Severity:  Normal   |   Resolution:
 Keywords:  sprintnov13, | Triage Stage:  Accepted
  decorators |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by toracle):

 * cc: toracle@… (added)


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

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

Re: [Django] #25519: "View Site" in admin shows wrong URL if site is not hosted at root

2015-10-21 Thread Django

#25519: "View Site" in admin shows wrong URL if site is not hosted at root
--+
 Reporter:  DheerendraRathor  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.admin |  Version:  1.8
 Severity:  Normal|   Resolution:
 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 timgraham):

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

Re: [Django] #25470: Serious performance impact (500x slower!) when querying distinct model dates objects

2015-10-21 Thread Django

#25470: Serious performance impact (500x slower!) when querying distinct model
dates objects
-+-
 Reporter:  stanleyxu2005|Owner:  felixxm
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 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:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"0f6d51e6a0a22e37e45c4bf452ddb49723e2f956" 0f6d51e6]:
 {{{
 #!CommitTicketReference repository=""
 revision="0f6d51e6a0a22e37e45c4bf452ddb49723e2f956"
 Fixed #25470 -- Avoided unnecessary, expensive DATETIME typecast on MySQL.
 }}}

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

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

Re: [Django] #25397: Warn of clash between generic view context variables and template context processor variables

2015-10-21 Thread Django

#25397: Warn of clash between generic view context variables and template 
context
processor variables
--+
 Reporter:  mathieuhinderyckx |Owner:  jbzdak
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.8
 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 timgraham):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/5456 PR]

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

Re: [Django] #25585: OGRGeometry.srid and OGRGeometry.srs cannot be set to None

2015-10-21 Thread Django

#25585: OGRGeometry.srid and OGRGeometry.srs cannot be set to None
+
 Reporter:  sir-sigurd  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  GIS |  Version:  master
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"0dbe897ab5ea055ed53a219f642348d98e1c3cf9" 0dbe897]:
 {{{
 #!CommitTicketReference repository=""
 revision="0dbe897ab5ea055ed53a219f642348d98e1c3cf9"
 Fixed #25585 -- Allowed setting OGRGeometry srid/srs attributes to `None`.
 }}}

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

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

Re: [Django] #25143: ArrayField should implement from_db_value()

2015-10-21 Thread Django

#25143: ArrayField should implement from_db_value()
--+
 Reporter:  Odahi |Owner:
 Type:  Bug   |   Status:  new
Component:  contrib.postgres  |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by timgraham):

 See #25579 for a related issue (querying on complex types) that could be
 fixed along with 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/063.82d986aceadb1948c92c54cdae35ce6b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25579: Lack of type adaptation in ArrayField querying/lookups

2015-10-21 Thread Django

#25579: Lack of type adaptation in ArrayField querying/lookups
-+-
 Reporter:  freshquiz|Owner:
 Type:  Bug  |   Status:  new
Component:  contrib.postgres |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  ArrayField query | Triage Stage:  Accepted
  lookup |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Unreviewed => Accepted


Comment:

 I can reproduce "can't adapt type 'Tag'" by adding
 `list(OtherTypesArrayModel.objects.filter(tags=Tag(1)))` to the PR from
 #25143.

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

Re: [Django] #25579: Lack of type adaptation in ArrayField querying/lookups (was: ArrayField query/lookup regression)

2015-10-21 Thread Django

#25579: Lack of type adaptation in ArrayField querying/lookups
-+-
 Reporter:  freshquiz|Owner:
 Type:  Bug  |   Status:  new
Component:  contrib.postgres |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  ArrayField query | Triage Stage:
  lookup |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  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/067.99305430c930d0b34fe9a5b1faf5c864%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25579: ArrayField query/lookup regression

2015-10-21 Thread Django

#25579: ArrayField query/lookup regression
-+-
 Reporter:  freshquiz|Owner:
 Type:  Bug  |   Status:  new
Component:  contrib.postgres |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  ArrayField query | Triage Stage:
  lookup |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by freshquiz):

 #25143 is to do with converting DB query result values to Python values,
 whilst this is to do with converting Python values to DB values, for the
 purpose of lookups/querying.

 I'll change the title to remove the word regression.

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

Re: [Django] #25417: Add a system check for an invalid default on a model field

2015-10-21 Thread Django

Comment (by charettes):

> I'll also note that this isn't even the first time I've had to work
around a buggy, overzealous, or plain wrong system check.

The system check is a still a ''new'' component of Django and from the
feedback we've had so far I think the prevention of misconfiguration and
footguns outweigh the nuisance caused by some initial bugs and required
adjustments.

While I could be convinced we should remove or downgrade this check to a
warning your actual use case doesn't convince me it's worth it. I still
think this check is not buggy, overzealous nor plain wrong but that it's
your use case that is bug prone.

As Tim suggested I think gathering feedback from the developpers mailing
list could help your case here.

In the meantime if want to work around this check you can override the
`check()` method of your reusable field to filter out `'fields.E008'`
errors.

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

Re: [Django] #24855: Allow the use of django.contrib.auth.login without credentials (authentication)

2015-10-21 Thread Django

#24855: Allow the use of django.contrib.auth.login without credentials
(authentication)
--+
 Reporter:  poiati|Owner:  poiati
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

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

Re: [Django] #25584: Getting Invalid syntax error while installing Django 1.9a1 and 1.9b1

2015-10-21 Thread Django

#25584: Getting Invalid syntax error while installing Django 1.9a1 and 1.9b1
---+
 Reporter:  BlackHacker|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.9a1
 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 timgraham):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/5461 PR]

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

Re: [Django] #25546: Duplicate queries on nested Prefetch objects with custom queries

2015-10-21 Thread Django

#25546: Duplicate queries on nested Prefetch objects with custom queries
-+-
 Reporter:  piquadrat|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  prefetch,| Triage Stage:  Accepted
  prefetch_related   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * type:  Bug => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 Accepting for further investigation.

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

Re: [Django] #25550: Deprecate direct assignment to the reverse side of a related set

2015-10-21 Thread Django

#25550: Deprecate direct assignment to the reverse side of a related set
-+-
 Reporter:  timgraham|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 timgraham):

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

Re: [Django] #25587: Django fails, when trying to save object "as new" with inlines objects and form validation errors.

2015-10-21 Thread Django

#25587: Django fails, when trying to save object "as new" with inlines objects 
and
form validation errors.
---+--
 Reporter:  user0007   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.8
 Severity:  Normal |   Resolution:  duplicate
 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:   => duplicate


Comment:

 Duplicate of #23387, fixed in Django 1.9.

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

Re: [Django] #25564: Django Admin's "View on Site" ignores model's custom manager

2015-10-21 Thread Django

#25564: Django Admin's "View on Site" ignores model's custom manager
-+-
 Reporter:  yuriiz   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:   |  Version:  1.8
  contrib.contenttypes   |
 Severity:  Normal   |   Resolution:  duplicate
 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
 * component:  Uncategorized => contrib.contenttypes
 * resolution:   => duplicate
 * type:  Uncategorized => Bug


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

Re: [Django] #25588: Add spatial lookups to RasterField

2015-10-21 Thread Django

#25588: Add spatial lookups to RasterField
-+-
 Reporter:  yellowcap|Owner:  yellowcap
 Type:  New feature  |   Status:  new
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  raster gdal gis  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

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

Re: [Django] #25417: Add a system check for an invalid default on a model field

2015-10-21 Thread Django

Comment (by gavinwahl):

> Do you have any problem adding this check to SILENCED_SYSTEM_CHECKS?

Yes. This is in a reusable app. I can't make my users silence the check in
order to use it.

> That's not true, there's a whole documented layer of model validation.

This validation is only used when called explicitly or when using a
ModelForm. I expect a validation error from an initial value only to be
raised if I ask if the model is valid.

> I'm not entirely sure I understand your use case but wouldn't this
special handling belong at the form level anyway?

I need to be able to create the model instances without a form. A form is
only used later, when the user is ready to edit the object. The initial
object is created without user interaction.

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

Re: [Django] #16281: ContentType.get_object_for_this_type using wrong database for creating object

2015-10-21 Thread Django

#16281: ContentType.get_object_for_this_type using wrong database for creating
object
-+-
 Reporter:  tfrydrychewicz@… |Owner:  poirier
 Type:  Bug  |   Status:  new
Component:   |  Version:  master
  contrib.contenttypes   |
 Severity:  Normal   |   Resolution:
 Keywords:  contenttype, object  | Triage Stage:  Accepted
  get_object_for_this_type,  |
  database, multiple |
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 #25564 is a duplicate.

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

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

Re: [Django] #25585: OGRGeometry.srid and OGRGeometry.srs cannot be set to None

2015-10-21 Thread Django

#25585: OGRGeometry.srid and OGRGeometry.srs cannot be set to None
+
 Reporter:  sir-sigurd  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  GIS |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by claudep):

 * version:  1.8 => master
 * 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/068.877ff541dc00f51a821936b1e711d3f3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25584: Getting Invalid syntax error while installing Django 1.9a1 and 1.9b1

2015-10-21 Thread Django

#25584: Getting Invalid syntax error while installing Django 1.9a1 and 1.9b1
---+
 Reporter:  BlackHacker|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.9a1
 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 claudep):

 * status:  closed => new
 * resolution:  worksforme =>
 * component:  Uncategorized => Documentation
 * stage:  Unreviewed => Accepted


Comment:

 I also encountered this error when using pip 1.5.6 (default version in
 Debian stable). I guess we should at least document that (suggesting `pip
 install --upgrade pip`?), as people do use stable software :-)

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

Re: [Django] #25583: GEOSGeometry.transform should impose no constraints on SRID if called with CoordTransform

2015-10-21 Thread Django

#25583: GEOSGeometry.transform should impose no constraints on SRID if called 
with
CoordTransform
-+
 Reporter:  sir-sigurd   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by claudep):

 * version:  1.8 => master
 * type:  Uncategorized => New feature
 * stage:  Unreviewed => Accepted


Comment:

 OK, fair.

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

Re: [Django] #25587: Django fails, when trying to save object "as new" with inlines objects and form validation errors.

2015-10-21 Thread Django

#25587: Django fails, when trying to save object "as new" with inlines objects 
and
form validation errors.
---+--
 Reporter:  user0007   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.8
 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 user0007):

 Replying to [comment:4 timgraham]:
 > Could you please provide a sample project or a minimal set of models to
 reproduce the issue?

 Sure.

 models.py:

 {{{
 class User(models.Model):
 first_name = models.CharField(max_length=255)


 class Project(models.Model):
 user = models.ForeignKey(User)
 name = models.CharField(max_length=255)

 class Collaborator(models.Model):
 email = models.Email()
 user = models.ForeignKey(User)
 project = models.ForeignKey(Project)
 }}}

 admin.py:

 {{{
 class CollaboratorAdmin(admin.TabularInline):
 model = Collaborator
 extra = 1
 raw_id_fields = ('user',)

 class ProjectAdmin(admin.ModelAdmin):
 inlines = [CollaboratorAdmin]
 raw_id_fields = ('user',)
 save_as = True

 admin.site.register(Project, ProjectAdmin)
 admin.site.register(User)
 }}}

 Follow those steps:

 1. Add ''Project'' object with 2 inlines objects.
 2. Go to edit form.
 3. Clear project's "name" input and click "Save as new" button.
 4. Click "Save and continue editing".
 5. Booom :-)

 Tested on Django 1.6, 1.7, 1.8

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

Re: [Django] #25470: Serious performance impact (500x slower!) when querying distinct model dates objects

2015-10-21 Thread Django

#25470: Serious performance impact (500x slower!) when querying distinct model
dates objects
-+-
 Reporter:  stanleyxu2005|Owner:  felixxm
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 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 felixxm):

 * needs_tests:  1 => 0


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

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

Re: [Django] #25588: Add spatial lookups to RasterField

2015-10-21 Thread Django

#25588: Add spatial lookups to RasterField
-+--
 Reporter:  yellowcap|Owner:  yellowcap
 Type:  New feature  |   Status:  new
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  raster gdal gis  | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by yellowcap):

 * needs_better_patch:   => 0
 * has_patch:  0 => 1
 * needs_tests:   => 0
 * needs_docs:   => 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.7e1fe640f2c7c7d664f4df5900900663%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25588: Add spatial lookups to RasterField

2015-10-21 Thread Django

#25588: Add spatial lookups to RasterField
-+-
 Reporter:  yellowcap|  Owner:  yellowcap
 Type:  New feature  | Status:  new
Component:  GIS  |Version:  master
 Severity:  Normal   |   Keywords:  raster gdal gis
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 The raster field currently does not support spatial lookups (such as
 `__dwithin` or `__bbcontains`). This functionality is essential for
 working with spatial data. It could be ported from the geometry lookups.

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

Re: [Django] #21894: Error in example code in django.forms.Form.clean()¶

2015-10-21 Thread Django

#21894: Error in example code in django.forms.Form.clean()¶
---+
 Reporter:  richard.kellner@…  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  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:"55ed23fd3e17c7743252a967a8f9957e038d35c4" 55ed23fd]:
 {{{
 #!CommitTicketReference repository=""
 revision="55ed23fd3e17c7743252a967a8f9957e038d35c4"
 [1.9.x] Fixed #21894 -- Corrected a form.clean() example in case a
 superclass doesn't return data.

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

Re: [Django] #21894: Error in example code in django.forms.Form.clean()¶

2015-10-21 Thread Django

#21894: Error in example code in django.forms.Form.clean()¶
---+
 Reporter:  richard.kellner@…  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  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:"6861c2027da87cd9606cef8530e738613bb8c293" 6861c20]:
 {{{
 #!CommitTicketReference repository=""
 revision="6861c2027da87cd9606cef8530e738613bb8c293"
 [1.8.x] Fixed #21894 -- Corrected a form.clean() example in case a
 superclass doesn't return data.

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

Re: [Django] #21894: Error in example code in django.forms.Form.clean()¶

2015-10-21 Thread Django

#21894: Error in example code in django.forms.Form.clean()¶
---+
 Reporter:  richard.kellner@…  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"80855a4b3787bace050a8b4a2b80f79306e69812" 80855a4]:
 {{{
 #!CommitTicketReference repository=""
 revision="80855a4b3787bace050a8b4a2b80f79306e69812"
 Fixed #21894 -- Corrected a form.clean() example in case a superclass
 doesn't return data.
 }}}

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

Re: [Django] #25456: Make GenericIPAddressField normalize IPv4 addresses

2015-10-21 Thread Django

#25456: Make GenericIPAddressField normalize IPv4 addresses
-+-
 Reporter:  frankvdp |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ipaddress, ipv4, | Triage Stage:  Accepted
  database, normalization|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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

Re: [Django] #24976: admin.TabularInline custom form field header displaying as None on admin page

2015-10-21 Thread Django

#24976: admin.TabularInline custom form field header displaying as None on admin
page
---+
 Reporter:  kartikanand|Owner:  matiasb
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.8
 Severity:  Normal |   Resolution:  fixed
 Keywords:  TabularInline  | 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:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"12aeed8c949925488a36f0a3b3bf25dfc9407cbf" 12aeed8]:
 {{{
 #!CommitTicketReference repository=""
 revision="12aeed8c949925488a36f0a3b3bf25dfc9407cbf"
 Fixed #24976 -- Fixed missing form label in tabular inline.

 If the model form had a form field specified, the label rendered
 as "None".
 }}}

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

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

Re: [Django] #25587: Django fails, when trying to save object "as new" with inlines objects and form validation errors.

2015-10-21 Thread Django

#25587: Django fails, when trying to save object "as new" with inlines objects 
and
form validation errors.
---+--
 Reporter:  user0007   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.8
 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 timgraham):

 Could you please provide a sample project or a minimal set of models to
 reproduce 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/066.d98472b755e1e0eee53dad2eb529eef2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25544: prefetch_related sends duplicate ids to database

2015-10-21 Thread Django

#25544: prefetch_related sends duplicate ids to database
-+-
 Reporter:  spectras |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  prefetch duplicate   | 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):

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


Comment:

 I'm not too familiar with this, but accepting on the basis for further
 investigation.

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

Re: [Django] #21200: Inconsistent handling of "PickleError" between cache backends

2015-10-21 Thread Django

#21200: Inconsistent handling of "PickleError" between cache backends
-+-
 Reporter:  t.chaumeny@… |Owner:  Florian
 |  Apolloner 
 Type:  Bug  |   Status:  closed
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:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 The above commit only included testes and docs --
 cf7ddc576583a15dec0800f4146c2e979795bf30 included the code changes.

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

Re: [Django] #25574: A minor enhancement to "for" tag description in the reference

2015-10-21 Thread Django

#25574: A minor enhancement to "for" tag description in the reference
-+-
 Reporter:  wodny|Owner:  jbzdak
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  for tag lookup   | Triage Stage:  Accepted
  order dict defaultdict |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"3e8234b77e2698d14a7825319845e5038424f09d" 3e8234b]:
 {{{
 #!CommitTicketReference repository=""
 revision="3e8234b77e2698d14a7825319845e5038424f09d"
 [1.8.x] Fixed #25574 -- Documented {{ dict.items }} shadowing in for
 template tag docs.

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

Re: [Django] #25574: A minor enhancement to "for" tag description in the reference

2015-10-21 Thread Django

#25574: A minor enhancement to "for" tag description in the reference
-+-
 Reporter:  wodny|Owner:  jbzdak
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  for tag lookup   | Triage Stage:  Accepted
  order dict defaultdict |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"5a9e93e05423c176adfef714f804fe80e6fbb522" 5a9e93e0]:
 {{{
 #!CommitTicketReference repository=""
 revision="5a9e93e05423c176adfef714f804fe80e6fbb522"
 [1.9.x] Fixed #25574 -- Documented {{ dict.items }} shadowing in for
 template tag docs.

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

Re: [Django] #25574: A minor enhancement to "for" tag description in the reference

2015-10-21 Thread Django

#25574: A minor enhancement to "for" tag description in the reference
-+-
 Reporter:  wodny|Owner:  jbzdak
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  for tag lookup   | Triage Stage:  Accepted
  order dict defaultdict |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"32cd7069711d2e02fcd20c005c59c175d542c62e" 32cd706]:
 {{{
 #!CommitTicketReference repository=""
 revision="32cd7069711d2e02fcd20c005c59c175d542c62e"
 Fixed #25574 -- Documented {{ dict.items }} shadowing in for template tag
 docs.
 }}}

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

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

Re: [Django] #17120: FormSet max_num can be bypassed and any number of forms saved

2015-10-21 Thread Django

#17120: FormSet max_num can be bypassed and any number of forms saved
+
 Reporter:  mila|Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Forms   |  Version:  1.3
 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 timgraham):

 It might be related/duplicate of #20347 "Add an absolute_max parameter to
 formset_factory" too.

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

Re: [Django] #25587: Django fails, when trying to save object "as new" with inlines objects and form validation errors.

2015-10-21 Thread Django

#25587: Django fails, when trying to save object "as new" with inlines objects 
and
form validation errors.
---+--
 Reporter:  user0007   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.8
 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 user0007):

 Replying to [comment:2 charettes]:
 > Do you happen to have any file or image fields? This looks similar to
 #14760.

 Nope, but there is a couple of foreign keys.

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

Re: [Django] #17120: FormSet max_num can be bypassed and any number of forms saved

2015-10-21 Thread Django

#17120: FormSet max_num can be bypassed and any number of forms saved
+
 Reporter:  mila|Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Forms   |  Version:  1.3
 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
+
Changes (by charettes):

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


Comment:

 I think this has been fixed with the introduction of `validate_max` and
 the fact that if the number of forms in a data set exceeds `max_num` by
 more than 1000, then the form will fail to validate as if `validate_max`
 was set.

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

Re: [Django] #25582: Add a way to build URLs with query strings (was: reverse() to url including GET parameters: .../myview?foo=bar)

2015-10-21 Thread Django

* needs_better_patch: => 0
* needs_tests: => 0
* version: 1.8 => master
* needs_docs: => 0
* stage: Unreviewed => Accepted

Comment:

I'm not positive this is something which should live in Django, but if
not, we could probably at least add some guidance to the docs about how to
go about it. If we do add it, it likely needs a discussion on the
DevelopersMailingList to figure out what the API should look like. See
also #10941 which asks for a template tag for creating query strings in
templates.

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

Re: [Django] #25587: Django fails, when trying to save object "as new" with inlines objects and form validation errors.

2015-10-21 Thread Django

#25587: Django fails, when trying to save object "as new" with inlines objects 
and
form validation errors.
---+--
 Reporter:  user0007   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.8
 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 charettes):

 Do you happen to have any file or image fields? This looks similar to
 #14760.

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

Re: [Django] #25587: Django fails, when trying to save object "as new" with inlines objects and form validation errors.

2015-10-21 Thread Django

#25587: Django fails, when trying to save object "as new" with inlines objects 
and
form validation errors.
---+--
 Reporter:  user0007   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.8
 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 user0007):

 * needs_docs:   => 0
 * version:  1.7 => 1.8
 * needs_tests:   => 0
 * needs_better_patch:   => 0


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

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

Re: [Django] #25576: HttpResponse can't be wrapped by io.TextIOWrapper; add required IOBase methods

2015-10-21 Thread Django

#25576: HttpResponse can't be wrapped by io.TextIOWrapper; add required IOBase
methods
-+-
 Reporter:  jdufresne|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"05248a1009c05985b1c227a1a48b871c3068cb12" 05248a10]:
 {{{
 #!CommitTicketReference repository=""
 revision="05248a1009c05985b1c227a1a48b871c3068cb12"
 Fixed #25576 -- Added IOBase methods required by TextIOWrapper to
 HttpResponse.
 }}}

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

Re: [Django] #25584: Getting Invalid syntax error while installing Django 1.9a1 and 1.9b1

2015-10-21 Thread Django

#25584: Getting Invalid syntax error while installing Django 1.9a1 and 1.9b1
---+--
 Reporter:  BlackHacker|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Uncategorized  |  Version:  1.9a1
 Severity:  Normal |   Resolution:  worksforme
 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:   => worksforme


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

[Django] #25587: Django fails, when trying to save object "as new" with inlines objects and form validation errors.

2015-10-21 Thread Django

#25587: Django fails, when trying to save object "as new" with inlines objects 
and
form validation errors.
---+
 Reporter:  user0007   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.admin  |Version:  1.7
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Let's assume that I have one existing object in Django Admin with some
 related objects (inlines). When I try to create a clone (by clicking on
 "Save as new"), but there are some validation errors, Django will fail,
 after clicking "Save and continue editing".

 Everything works without inlines objects.

 Error:

 {{{
 django.db.models.fields in get_prep_value
 ValueError: invalid literal for int() with base 10: ''
 }}}

 Stacktrace (most recent call last):

 {{{
   File "django/core/handlers/base.py", line 113, in get_response
 response = callback(request, *callback_args, **callback_kwargs)
   File "django/contrib/admin/options.py", line 406, in wrapper
 return self.admin_site.admin_view(view)(*args, **kwargs)
   File "django/utils/decorators.py", line 91, in _wrapped_view
 response = view_func(request, *args, **kwargs)
   File "django/views/decorators/cache.py", line 89, in _wrapped_view_func
 response = view_func(request, *args, **kwargs)
   File "django/contrib/admin/sites.py", line 202, in inner
 return view(request, *args, **kwargs)
   File "django/utils/decorators.py", line 25, in _wrapper
 return bound_func(*args, **kwargs)
   File "django/utils/decorators.py", line 91, in _wrapped_view
 response = view_func(request, *args, **kwargs)
   File "django/utils/decorators.py", line 21, in bound_func
 return func(self, *args2, **kwargs2)
   File "django/db/transaction.py", line 223, in inner
 return func(*args, **kwargs)
   File "django/contrib/admin/options.py", line 1038, in add_view
 prefix=prefix, queryset=inline.queryset(request))
   File "www/forms.py", line 566, in __init__
 super(UczestnikAdminInlineFormset, self).__init__(*args, **kwargs)
   File "django/forms/models.py", line 720, in __init__
 queryset=qs, **kwargs)
   File "django/forms/models.py", line 441, in __init__
 super(BaseModelFormSet, self).__init__(**defaults)
   File "django/forms/formsets.py", line 56, in __init__
 self._construct_forms()
   File "django/forms/formsets.py", line 124, in _construct_forms
 self.forms.append(self._construct_form(i))
   File "django/forms/models.py", line 729, in _construct_form
 form = super(BaseInlineFormSet, self)._construct_form(i, **kwargs)
   File "django/forms/models.py", line 463, in _construct_form
 connection=connections[self.get_queryset().db])
   File "django/db/models/fields/__init__.py", line 340, in
 get_db_prep_lookup
 value = self.get_prep_lookup(lookup_type, value)
   File "django/db/models/fields/__init__.py", line 322, in get_prep_lookup
 return self.get_prep_value(value)
   File "django/db/models/fields/__init__.py", line 555, in get_prep_value
 return int(value)
 }}}

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

Re: [Django] #25586: Admin's tabular inline fields may be misaligned if the first form field is hidden

2015-10-21 Thread Django

#25586: Admin's tabular inline fields may be misaligned if the first form field 
is
hidden
-+-
 Reporter:  blueyed  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"1745aa000a4e859c21270371662634978371dda8" 1745aa0]:
 {{{
 #!CommitTicketReference repository=""
 revision="1745aa000a4e859c21270371662634978371dda8"
 Fixed #25586 -- Fixed possible table cell misalignment in admin's tabular
 inlines.

 The table body (tbody) was shifted by one column to the left
 if the first inline form field is hidden.
 }}}

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

[Django] #25586: Admin's tabular inline fields may be misaligned if the first form field is hidden

2015-10-21 Thread Django

#25586: Admin's tabular inline fields may be misaligned if the first form field 
is
hidden
-+
   Reporter:  blueyed|  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  contrib.admin  |Version:  1.8
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 If the first form field in a tabular inline is hidden, the first 
 won't have colspan=2 which is meant to account for the first  which doesn't have a corresponding . This will cause
 the table cells to be misaligned. More details on the
 [https://github.com/django/django/pull/5445 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/050.f8e8bf73e0b015635fc03ab8ae2af456%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25586: Admin's tabular inline fields may be misaligned if the first form field is hidden

2015-10-21 Thread Django

#25586: Admin's tabular inline fields may be misaligned if the first form field 
is
hidden
-+-
 Reporter:  blueyed  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.8
 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 timgraham):

 * stage:  Unreviewed => 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/065.eb9398220027f67b7ff0c424be831642%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25585: OGRGeometry.srid and OGRGeometry.srs cannot be set to None

2015-10-21 Thread Django

#25585: OGRGeometry.srid and OGRGeometry.srs cannot be set to None
+--
 Reporter:  sir-sigurd  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  GIS |  Version:  1.8
 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 sir-sigurd):

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


Comment:

 PR -- https://github.com/django/django/pull/5458

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

[Django] #25585: OGRGeometry.srid and OGRGeometry.srs cannot be set to None

2015-10-21 Thread Django

#25585: OGRGeometry.srid and OGRGeometry.srs cannot be set to None
+
 Reporter:  sir-sigurd  |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  GIS |Version:  1.8
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  1
Easy pickings:  0   |  UI/UX:  0
+
 {{{
 In [1]: from django.contrib.gis.gdal import OGRGeometry

 In [2]: p = OGRGeometry('POINT(1 1)')

 In [3]: print p.srs
 None

 In [4]: p.srs = p.srs
 ---
 TypeError Traceback (most recent call
 last)
  in ()
 > 1 p.srs = p.srs

 /home/sergey/dev/django/django/contrib/gis/gdal/geometries.pyc in
 _set_srs(self, srs)
 272 srs_ptr = sr.ptr
 273 else:
 --> 274 raise TypeError('Cannot assign spatial reference with
 object of type: %s' % type(srs))
 275 capi.assign_srs(self.ptr, srs_ptr)
 276

 TypeError: Cannot assign spatial reference with object of type: 

 In [5]: print p.srid
 None

 In [6]: p.srid = p.srid
 ---
 TypeError Traceback (most recent call
 last)
  in ()
 > 1 p.srid = p.srid

 /home/sergey/dev/django/django/contrib/gis/gdal/geometries.pyc in
 _set_srid(self, srid)
 288 self.srs = srid
 289 else:
 --> 290 raise TypeError('SRID must be set with an integer.')
 291
 292 srid = property(_get_srid, _set_srid)

 TypeError: SRID must be set with an integer.
 }}}

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

Re: [Django] #25579: ArrayField query/lookup regression

2015-10-21 Thread Django

#25579: ArrayField query/lookup regression
-+-
 Reporter:  freshquiz|Owner:
 Type:  Bug  |   Status:  new
Component:  contrib.postgres |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  ArrayField query | Triage Stage:
  lookup |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Looks similar to #25143 but I think it's a separate issue. I'm not sure
 about the characterization of the issue as a regression since `ArrayField`
 was never present in a stable release without the commit you pointed out,
 but it might be okay to backport anyway under the "bug in a new feature"
 rationale.

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

Re: [Django] #25573: Add simple way to use SplitDateTimeField on ModelForms

2015-10-21 Thread Django

#25573: Add simple way to use SplitDateTimeField on ModelForms
-+-
 Reporter:  seddonym |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Forms|  Version:  1.9a1
 Severity:  Normal   |   Resolution:  duplicate
 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
 * needs_better_patch:   => 0
 * resolution:   => duplicate
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 The `ModelForm.Meta.field_classes` feature added in Django 1.9 should
 allow this (#24295).

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

Re: [Django] #25570: Using a templatetag in a Python file in a project template causes an Exception

2015-10-21 Thread Django

#25570: Using a templatetag in a Python file in a project template causes an
Exception
---+--
 Reporter:  danielsamuels  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Utilities  |  Version:  1.8
 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
---+--
Changes (by timgraham):

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


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

Re: [Django] #25577: Squashed migrations do not work if deletion of indexed field can't be optimized on postgresql database

2015-10-21 Thread Django

#25577: Squashed migrations do not work if deletion of indexed field can't be
optimized on postgresql database
+--
 Reporter:  jbzdak  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.8
 Severity:  Normal  |   Resolution:  duplicate
 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:   => duplicate


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

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

Re: [Django] #25530: Deferred foreign keys operations fail when the column is changed during the same migration

2015-10-21 Thread Django

#25530: Deferred foreign keys operations fail when the column is changed during 
the
same migration
--+
 Reporter:  simonphilips  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Migrations|  Version:  1.8
 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 timgraham):

 I closed #25577 as a duplicate as it seems to be the same underlying
 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/070.384aad7bf1faa4cb5525976a325e94b9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25584: Getting Invalid syntax error while installing Django 1.9a1 and 1.9b1

2015-10-21 Thread Django

#25584: Getting Invalid syntax error while installing Django 1.9a1 and 1.9b1
---+--
 Reporter:  BlackHacker|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  1.9a1
 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 timgraham):

 What version of pip? I have no trouble with Python 2.7.6 and pip 7.1.2.

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

Re: [Django] #25584: Getting Invalid syntax error while installing Django 1.9a1 and 1.9b1

2015-10-21 Thread Django

#25584: Getting Invalid syntax error while installing Django 1.9a1 and 1.9b1
---+--
 Reporter:  BlackHacker|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  1.9a1
 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):

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


Old description:

> When I am trying to install django 1.9a1 or 1.9b1 using pip on python
> version 2.7.6. I am getting syntax error though installation is not
> getting effected because of this.
>
> Compiling /tmp/pip_build_root/django/django/conf/app_template/apps.py ...
>   File "/tmp/pip_build_root/django/django/conf/app_template/apps.py",
> line 4
> class {{ camel_case_app_name }}Config(AppConfig):
>   ^
> SyntaxError: invalid syntax
>
> and
>
> Compiling /tmp/pip_build_root/django/django/conf/app_template/models.py
> ...
>   File "/tmp/pip_build_root/django/django/conf/app_template/models.py",
> line 1
> {{ unicode_literals }}from django.db import models
>  ^
> SyntaxError: invalid syntax

New description:

 When I am trying to install django 1.9a1 or 1.9b1 using pip on python
 version 2.7.6. I am getting syntax error though installation is not
 getting effected because of this.
 {{{
 Compiling /tmp/pip_build_root/django/django/conf/app_template/apps.py ...
   File "/tmp/pip_build_root/django/django/conf/app_template/apps.py", line
 4
 class {{ camel_case_app_name }}Config(AppConfig):
   ^
 SyntaxError: invalid syntax

 and

 Compiling /tmp/pip_build_root/django/django/conf/app_template/models.py
 ...
   File "/tmp/pip_build_root/django/django/conf/app_template/models.py",
 line 1
 {{ unicode_literals }}from django.db import models
  ^
 SyntaxError: invalid syntax
 }}}

--

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

[Django] #25584: Getting Invalid syntax error while installing Django 1.9a1 and 1.9b1

2015-10-21 Thread Django

#25584: Getting Invalid syntax error while installing Django 1.9a1 and 1.9b1
---+
 Reporter:  BlackHacker|  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  1.9a1
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 When I am trying to install django 1.9a1 or 1.9b1 using pip on python
 version 2.7.6. I am getting syntax error though installation is not
 getting effected because of this.

 Compiling /tmp/pip_build_root/django/django/conf/app_template/apps.py ...
   File "/tmp/pip_build_root/django/django/conf/app_template/apps.py", line
 4
 class {{ camel_case_app_name }}Config(AppConfig):
   ^
 SyntaxError: invalid syntax

 and

 Compiling /tmp/pip_build_root/django/django/conf/app_template/models.py
 ...
   File "/tmp/pip_build_root/django/django/conf/app_template/models.py",
 line 1
 {{ unicode_literals }}from django.db import models
  ^
 SyntaxError: invalid syntax

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

Re: [Django] #25583: GEOSGeometry.transform should impose no constraints on SRID if called with CoordTransform

2015-10-21 Thread Django

#25583: GEOSGeometry.transform should impose no constraints on SRID if called 
with
CoordTransform
---+--
 Reporter:  sir-sigurd |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  GIS|  Version:  1.8
 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 sir-sigurd):

 This behavior is problematic when you have coordinates in some custom SRS
 with no SRID assigned and you need to transform these coordinates.

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

Re: [Django] #25548: FormView.form_invalid() discards its form argument resulting in duplicated validation

2015-10-21 Thread Django

#25548: FormView.form_invalid() discards its form argument resulting in 
duplicated
validation
-+-
 Reporter:  acatton  |Owner:  dudepare
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Generic views|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  performance  | Triage Stage:  Accepted
  FormView form_invalid  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by dudepare):

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


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

Re: [Django] #25583: GEOSGeometry.transform should impose no constraints on SRID if called with CoordTransform

2015-10-21 Thread Django

#25583: GEOSGeometry.transform should impose no constraints on SRID if called 
with
CoordTransform
---+--
 Reporter:  sir-sigurd |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  GIS|  Version:  1.8
 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 claudep):

 I'm not sure about that. I think requiring the SRID being set for a
 geometry to be transformed is some sort of safeguard against badly written
 code.
 Maybe you could tell me about a use case where this behavior is
 problematic and where defining the proper SRID beforehand is not possible?

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

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

Re: [Django] #25578: Correct the spelling of GitHub

2015-10-21 Thread Django

#25578: Correct the spelling of GitHub
--+
 Reporter:  ymyzk |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  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:"a083d7019230b1823a02614189bd1911aa62c054" a083d701]:
 {{{
 #!CommitTicketReference repository=""
 revision="a083d7019230b1823a02614189bd1911aa62c054"
 [1.9.x] Fixed #25578 -- Corrected the casing of "GitHub".

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

Re: [Django] #25578: Correct the spelling of GitHub

2015-10-21 Thread Django

#25578: Correct the spelling of GitHub
--+
 Reporter:  ymyzk |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  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
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"230d8c7301281176a31443a2f4f425828291e46d" 230d8c73]:
 {{{
 #!CommitTicketReference repository=""
 revision="230d8c7301281176a31443a2f4f425828291e46d"
 Fixed #25578 -- Corrected the casing of "GitHub".
 }}}

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

Re: [Django] #25581: trac: Search for "Description" contains "foo" AND "bar"

2015-10-21 Thread Django

#25581: trac: Search for "Description" contains "foo" AND "bar"
-+--
 Reporter:  guettli  |Owner:
 Type:  Bug  |   Status:  closed
Component:  Error reporting  |  Version:  1.8
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Description changed by guettli:

Old description:

> current custom search in trac does not support searching for for
> "Descriptions" contains "foo" AND "bar"
>
> If I try it, the second description automatically adds the second text-
> input below the first one and combines them with OR.

New description:

 current custom search in trac does not support searching for
 "Descriptions" contains "foo" AND "bar"

 If I try it, the second description automatically adds the second text-
 input below the first one and combines them with OR.

--

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

Re: [Django] #25581: trac: Search for "Description" contains "foo" AND "bar"

2015-10-21 Thread Django

#25581: trac: Search for "Description" contains "foo" AND "bar"
-+--
 Reporter:  guettli  |Owner:
 Type:  Bug  |   Status:  closed
Component:  Error reporting  |  Version:  1.8
 Severity:  Normal   |   Resolution:  invalid
 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:   => invalid


Comment:

 The issue belongs in the Trac issue tracker, not Django. It seems to be
 described here: http://trac.edgewall.org/ticket/10152.

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

Re: [Django] #25583: GEOSGeometry.transform should impose no constraints on SRID if called with CoordTransform

2015-10-21 Thread Django

#25583: GEOSGeometry.transform should impose no constraints on SRID if called 
with
CoordTransform
---+--
 Reporter:  sir-sigurd |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  GIS|  Version:  1.8
 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 sir-sigurd):

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


Comment:

 added PR https://github.com/django/django/pull/5457

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

[Django] #25583: GEOSGeometry.transform should impose no constraints on SRID if called with CoordTransform

2015-10-21 Thread Django

#25583: GEOSGeometry.transform should impose no constraints on SRID if called 
with
CoordTransform
---+
 Reporter:  sir-sigurd |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  GIS|Version:  1.8
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  0  |  UI/UX:  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/053.160a17cf7cb49b3cfbd337063f765e12%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25582: reverse() to url including GET parameters: .../myview?foo=bar

2015-10-21 Thread Django

#25582: reverse() to url including GET parameters: .../myview?foo=bar
-+
 Reporter:  guettli  |  Owner:  nobody
 Type:  New feature  | Status:  new
Component:  Core (URLs)  |Version:  1.8
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 It is a common question on stackoverflow and other places:

 How to reverse() to url including GET parameters? Example:
 .../myview?foo=bar

 http://stackoverflow.com/questions/9585491/how-do-i-pass-get-parameters-
 using-django-urlresolvers-reverse

 http://stackoverflow.com/a/27641445/633961

 It would be very nice if django could implement a short-cut which provides
 this.

 It would be useful for python code and template, too.

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

Re: [Django] #25581: trac: Search for "Description" contains "foo" AND "bar" (was: trac: Seach for "Description" contains "foo" AND "bar")

2015-10-21 Thread Django

#25581: trac: Search for "Description" contains "foo" AND "bar"
-+--
 Reporter:  guettli  |Owner:
 Type:  Bug  |   Status:  new
Component:  Error reporting  |  Version:  1.8
 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
-+--

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

Re: [Django] #25581: trac: Seach for "Description" contains "foo" AND "bar" (was: trac: Seach for "Descriptions" contains "foo" AND "bar")

2015-10-21 Thread Django

#25581: trac: Seach for "Description" contains "foo" AND "bar"
-+--
 Reporter:  guettli  |Owner:
 Type:  Bug  |   Status:  new
Component:  Error reporting  |  Version:  1.8
 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 guettli):

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

[Django] #25581: trac: Seach for "Descriptions" contains "foo" AND "bar"

2015-10-21 Thread Django

#25581: trac: Seach for "Descriptions" contains "foo" AND "bar"
-+-
 Reporter:  guettli  |  Owner:
 Type:  Bug  | Status:  new
Component:  Error reporting  |Version:  1.8
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 current custom search in trac does not support searching for for
 "Descriptions" contains "foo" AND "bar"

 If I try it, the second description automatically adds the second text-
 input below the first one and combines them with OR.

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

Re: [Django] #25580: GEOSGeometry.srid cannot be set to None

2015-10-21 Thread Django

#25580: GEOSGeometry.srid cannot be set to None
+--
 Reporter:  sir-sigurd  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  GIS |  Version:  1.8
 Severity:  Normal  |   Resolution:  fixed
 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 Claude Paroz ):

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


Comment:

 In [changeset:"a272db70085887209946f28c9407409bfc0c7ee1" a272db7]:
 {{{
 #!CommitTicketReference repository=""
 revision="a272db70085887209946f28c9407409bfc0c7ee1"
 Fixed #25580 -- Allowed `None` to be set as SRID value.
 }}}

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

Re: [Django] #25578: Correct the spelling of GitHub

2015-10-21 Thread Django

#25578: Correct the spelling of GitHub
--+
 Reporter:  ymyzk |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  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 claudep):

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


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

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

Re: [Django] #25576: HttpResponse can't be wrapped by io.TextIOWrapper; add required IOBase methods

2015-10-21 Thread Django

#25576: HttpResponse can't be wrapped by io.TextIOWrapper; add required IOBase
methods
-+-
 Reporter:  jdufresne|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  HTTP handling|  Version:  master
 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):

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

76 matches

Mail list logo