date:20150922

Re: [Django] #25426: pickling SimpleLazyObject fails just after accessing related object of wrapped model instance.

2015-09-22 Thread Django

#25426: pickling SimpleLazyObject fails just after accessing related object of
wrapped model instance.
--+
 Reporter:  iru   |Owner:  iru
 Type:  Bug   |   Status:  assigned
Component:  Core (Serialization)  |  Version:  1.8
 Severity:  Release blocker   |   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by iru):

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


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

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

Re: [Django] #25426: pickling SimpleLazyObject fails just after accessing related object of wrapped model instance.

2015-09-22 Thread Django

#25426: pickling SimpleLazyObject fails just after accessing related object of
wrapped model instance.
-+-
 Reporter:  iru  |Owner:  iru
 Type:  Bug  |   Status:  closed
Component:  Core |  Version:  1.8
  (Serialization)|
 Severity:  Release blocker  |   Resolution:  duplicate
 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 iru):

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


Comment:

 closing since this duplicates https://code.djangoproject.com/ticket/25389

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

Re: [Django] #16117: Provide decorators to easily mark functions/methods as list_display items or admin actions

2015-09-22 Thread Django

#16117: Provide decorators to easily mark functions/methods as list_display 
items
or admin actions
---+
 Reporter:  haras  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by collinanderson):

 Also, keep in mind allow_tags is deprecated #25135.

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

Re: [Django] #16117: Provide decorators to easily mark functions/methods as list_display items or admin actions

2015-09-22 Thread Django

#16117: Provide decorators to easily mark functions/methods as list_display 
items
or admin actions
---+
 Reporter:  haras  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by funkybob):

 In discussion with someone this morning, I whipped up this

 {{{
 class admin_list(object):
 def __init__(self, boolean=None, order_field=None, allow_tags=None,
 short_description=None):
 self.boolean = boolean
 self.order_field = order_field
 self.allow_tags = allow_tags
 self.short_description=short_description

 def __call__(self, attr):
 if self.boolean is not None:
 attr.boolean = self.boolean
 if self.order_field is not None:
 attr.admin_order_field = self.order_field
 if self.allow_tags is not None:
 attr.allow_tags = self.allow_tags
 if self.short_description is not None:
 attr.short_description = short_description
 return attr
 }}}

 Then asked if anyone thought it'd be useful, and @timgraham pointed me to
 this ticket.  I'll dump this here for now... feel free to bike shed the
 names, or I'll make a PR if you like.

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

Re: [Django] #25447: Better emphasize the need to restart server after adding template tag in docs

2015-09-22 Thread Django

#25447: Better emphasize the need to restart server after adding template tag in
docs
-+-
 Reporter:  henryfjordan |Owner:
 Type:   |  henryfjordan
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-

Comment (by Tim Graham ):

 In [changeset:"5add28dad0b31bd2e1d550de4d56a3c3ffbf1ec0" 5add28d]:
 {{{
 #!CommitTicketReference repository=""
 revision="5add28dad0b31bd2e1d550de4d56a3c3ffbf1ec0"
 [1.8.x] Fixed #25447 -- Emphasized the need to restart dev server when
 adding template tags.

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

Re: [Django] #25447: Better emphasize the need to restart server after adding template tag in docs

2015-09-22 Thread Django

#25447: Better emphasize the need to restart server after adding template tag in
docs
-+-
 Reporter:  henryfjordan |Owner:
 Type:   |  henryfjordan
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"af95eee9fb70dae5b3b2ce8bc73c13fc1de239ff" af95eee9]:
 {{{
 #!CommitTicketReference repository=""
 revision="af95eee9fb70dae5b3b2ce8bc73c13fc1de239ff"
 Fixed #25447 -- Emphasized the need to restart dev server when adding
 template tags.
 }}}

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

Re: [Django] #24115: Bcrypt hashers don't implement must_update

2015-09-22 Thread Django

#24115: Bcrypt hashers don't implement must_update
--+
 Reporter:  cancan101 |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  contrib.auth  |  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:"cb1e779ceb461fd1a5ad9e7659316ac4d3775a5f" cb1e779]:
 {{{
 #!CommitTicketReference repository=""
 revision="cb1e779ceb461fd1a5ad9e7659316ac4d3775a5f"
 Refs #24115 -- Added docs for password updates on bcrypt rounds change.
 }}}

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

Re: [Django] #25442: RunSQL migration is run twice (and once for real with "--fake")

2015-09-22 Thread Django

#25442: RunSQL migration is run twice (and once for real with "--fake")
+--
 Reporter:  tino|Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  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:

 I think this is a symptom of trying to migrate from the built-in auth user
 to a custom user model. This currently doesn't work very well as described
 in #25313.

 The tracebacks are you seeing aren't a migration running, but rather the
 `post_migrate` signal handler that creates user permissions.

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

Re: [Django] #25438: Oracle GIS test failures for Django 1.9

2015-09-22 Thread Django

#25438: Oracle GIS test failures for Django 1.9
+
 Reporter:  timgraham   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  GIS |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  oracle 1.9  | 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):

 Jenkins uses Oracle 11.2.0.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/067.05b1d6f4bbc86f08362bacaa32787114%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25438: Oracle GIS test failures for Django 1.9

2015-09-22 Thread Django

#25438: Oracle GIS test failures for Django 1.9
+
 Reporter:  timgraham   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  GIS |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  oracle 1.9  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by felixxm):

 Replying to [ticket:25438 timgraham]:
 > After the patch for #24688 to add support for new-style GIS functions,
 some test failures remain:
 > {{{
 >
 gis_tests.geoapp.test_functions.GISFunctionsTests.test_difference_mixed_srid
 >
 > Traceback (most recent call last):
 >   File "/mnt/jenkinsdata/workspace/pull-requests-
 oracle/database/oragis11/python/python3.5/django/db/utils.py", line 102,
 in inner
 > return func(*args, **kwargs)
 >   File "/mnt/jenkinsdata/workspace/pull-requests-
 oracle/database/oragis11/python/python3.5/django/db/backends/oracle/base.py",
 line 516, in fetchmany
 > return tuple(_rowfactory(r, self.cursor) for r in
 self.cursor.fetchmany(size))
 > cx_Oracle.DatabaseError: ORA-13199: SRID does not exist.
 > ORA-06512: at "MDSYS.MD", line 1723
 > ORA-06512: at "MDSYS.MDERR", line 17
 > ORA-06512: at "MDSYS.SDO_CS", line 5264
 > ORA-06512: at "MDSYS.SDO_CS", line 3034
 > }}}

 Which Oracle  version has been used? In `test_difference_mixed_srid` test
 we can find crucial line :
 {{{
185: geom = Point(556597.4, 2632018.6, srid=3857)  # Spherical
 mercator
 }}}
 as we can see srid=3857 is needed, but it appeared in 11.2.0.3.

 http://docs.oracle.com/cd/E24693_01/appdev.11203/e11830/sdo_newfeat.htm

 In previous versions we will need to use srid=3785 instead.

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

Re: [Django] #25446: Can't use PostGIS function ST_OrderingEquals with GeoDjango

2015-09-22 Thread Django

#25446: Can't use PostGIS function ST_OrderingEquals with GeoDjango
-+
 Reporter:  ezheidtmann  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  GIS  |  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
-+

Comment (by claudep):

 It may make sense. I do recognize that using the bounding box comparison
 for `exact` (~= PostGIS operator) is at least misleading... A cross-
 backends summary would be nice. But as usual, the backwards compatibility
 is important, we cannot suddenly change the operator used by a comparison.
 Read also http://workshops.boundlessgeo.com/postgis-intro/equality.html

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

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

Re: [Django] #17664: Smart `if` tag silences exceptions

2015-09-22 Thread Django

#17664: Smart `if` tag silences exceptions
-+-
 Reporter:  mrmachine|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  smart if tag | Triage Stage:  Accepted
  queryset exception silenced|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by joshmaker):

 Replying to [comment:13 collinanderson]:
 > Why silence ValueError and TypeError? Is that for filters?

 My thought process on this was basically limited to matching the existing
 list of Exceptions listed out here:
 https://github.com/django/django/blob/1.8.4/django/template/base.py#L833-L836
 so the behavior would match that for template variable resolution.

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

Re: [Django] #25446: Can't use PostGIS function ST_OrderingEquals with GeoDjango

2015-09-22 Thread Django

#25446: Can't use PostGIS function ST_OrderingEquals with GeoDjango
-+
 Reporter:  ezheidtmann  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  GIS  |  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
-+

Comment (by ezheidtmann):

 Thank you! I updated the workaround to fix a couple edge cases. And I will
 look forward to 1.9.

 While we're on the topic, what do you think about changing the "exact"
 lookup to use ST_OrderingEquals? This would match the behavior of GEOS
 LineString objects but I am not sure of the broader implications of that
 change. Perhaps SpatiaLite does not offer an equivalent, so we cannot bake
 it into Django?

 Thanks,
 -Evan

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

Re: [Django] #25448: Ease creation of custom GIS lookups

2015-09-22 Thread Django

#25448: Ease creation of custom GIS lookups
--+
 Reporter:  claudep   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  GIS   |  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
--+

Comment (by claudep):

 Planned feature (to be tested):
 {{{
 #!diff
 diff --git a/django/contrib/gis/db/models/lookups.py
 b/django/contrib/gis/db/models/lookups.py
 index 46104a2..ed993ca 100644
 --- a/django/contrib/gis/db/models/lookups.py
 +++ b/django/contrib/gis/db/models/lookups.py
 @@ -87,13 +87,16 @@ class GISLookup(Lookup):
  rhs = connection.ops.get_geom_placeholder(self.lhs.output_field,
 geom, compiler)
  return rhs, rhs_params

 +def get_operator(connection):
 +return connection.ops.gis_operators.get[self.lookup_name]
 +
  def as_sql(self, compiler, connection):
  lhs_sql, sql_params = self.process_lhs(compiler, connection)
  rhs_sql, rhs_params = self.process_rhs(compiler, connection)
  sql_params.extend(rhs_params)

  template_params = {'lhs': lhs_sql, 'rhs': rhs_sql}
 -backend_op = connection.ops.gis_operators[self.lookup_name]
 +backend_op = self.get_operator(connection)
  return backend_op.as_sql(connection, self, template_params,
 sql_params)


 }}}

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

Re: [Django] #25448: Ease creation of custom GIS lookups

2015-09-22 Thread Django

#25448: Ease creation of custom GIS lookups
--+
 Reporter:  claudep   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  GIS   |  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
--+

Comment (by claudep):

 Planned modification (to be tested):
 {{{
 #!diff
 diff --git a/django/contrib/gis/db/models/lookups.py
 b/django/contrib/gis/db/models/lookups.py
 index 46104a2..33fa635 100644
 --- a/django/contrib/gis/db/models/lookups.py
 +++ b/django/contrib/gis/db/models/lookups.py
 @@ -93,7 +93,7 @@ class GISLookup(Lookup):
  sql_params.extend(rhs_params)

  template_params = {'lhs': lhs_sql, 'rhs': rhs_sql}
 -backend_op = connection.ops.gis_operators[self.lookup_name]
 +backend_op = connection.ops.gis_operators.get(self.lookup_name,
 self.lookup_name)
  return backend_op.as_sql(connection, self, template_params,
 sql_params)


 }}}

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

Re: [Django] #25446: Can't use PostGIS function ST_OrderingEquals with GeoDjango

2015-09-22 Thread Django

#25446: Can't use PostGIS function ST_OrderingEquals with GeoDjango
-+
 Reporter:  ezheidtmann  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  GIS  |  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):

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


Comment:

 You are right in that GeoDjango doesn't support this lookup. In Django
 1.9, GIS lookups/functions have seen many refactorings which should allow
 you to more easily add your own lookups.

 While studying your use case, I've seen a limitation in current lookup
 implementation (#25448). After fixing this one, you should be able to add
 your custom lookup like this (not portable way):

 {{{
 from django.contrib.gis.db.models import GeometryField
 from django.contrib.gis.db.models.lookups import GisLookup

 class OrderingEqualsLookup(GISLookup):
 lookup_name = 'ST_OrderingEquals'

 GeometryField.register_lookup(OrderingEqualsLookup)
 }}}

 For Django 1.8, keep your workaround...

 We should at least document that.

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

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

[Django] #25448: Ease creation of custom GIS lookups

2015-09-22 Thread Django

#25448: Ease creation of custom GIS lookups
+
   Reporter:  claudep   |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  GIS   |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 Following the use case described in #25446, the current `GISLookup` class
 is missing a small change to allow an easy definition of custom lookups.
 I plan to offer a patch soon.

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

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

Re: [Django] #25442: RunSQL migration is run twice (and once for real with "--fake")

2015-09-22 Thread Django

#25442: RunSQL migration is run twice (and once for real with "--fake")
+--
 Reporter:  tino|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  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 tino):

 Hi Tim, it didn't have that dependency, but I ran the migration in the
 order as described above. Adding the dependency does not change the
 behaviour, but does make that you only have to run `python manage.py
 migrate` once to have it display.

 Repository: https://github.com/tino/django-ticket-25442

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

Re: [Django] #25447: Better emphasize the need to restart server after adding template tag in docs

2015-09-22 Thread Django

#25447: Better emphasize the need to restart server after adding template tag in
docs
-+-
 Reporter:  henryfjordan |Owner:
 Type:   |  henryfjordan
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  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:  1|UI/UX:  1
-+-
Changes (by henryfjordan):

 * owner:  nobody => henryfjordan
 * needs_better_patch:   => 0
 * status:  new => assigned
 * needs_tests:   => 0
 * needs_docs:   => 0


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

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

[Django] #25447: Better emphasize the need to restart server after adding template tag in docs

2015-09-22 Thread Django

#25447: Better emphasize the need to restart server after adding template tag in
docs
--+
 Reporter:  henryfjordan  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.8
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  1
--+
 Right now, it is not very clear and very very easy to skim over the need
 to restart your development server when adding a template tag/filter to
 your project. I suggest bolding that sentence in the docs to make this
 information more clear.

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

Re: [Django] #25445: `AttributeError` when `app_config` is missing attribute `models_module` in contenttypes/management.py

2015-09-22 Thread Django

#25445: `AttributeError` when `app_config` is missing attribute `models_module` 
in
contenttypes/management.py
-+-
 Reporter:  pygeek   |Owner:  pygeek
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Uncategorized|  Version:  1.8
 Severity:  Normal   |   Resolution:  needsinfo
 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 aaugustin):

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


Comment:

 Have you encountered an error in practice or are you simply suggesting
 this fix based on code inspection?

 Considering that `AppConfig.__init__` assigns `self.models_module = None`,
 I fail to see how `models_module` can be missing.

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

Re: [Django] #25434: Missing documentation for request.site attribute

2015-09-22 Thread Django

#25434: Missing documentation for request.site attribute
---+
 Reporter:  ngnpope|Owner:  ngnpope
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.7
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by timgraham):

 Okay with me.

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

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

Re: [Django] #25434: Missing documentation for request.site attribute

2015-09-22 Thread Django

Comment (by ngnpope):

You've suggested exactly what I was thinking as an alternative - a
separate section detailing the attributes that are added to the request by
middleware. As well as `request.user` and `request.site`, there is also
`request.session` which is set by middleware but currently doesn't mention
the fact. I feel that it is useful to know where these attributes are
meant to come from if they have not been set on the request object.

Would you rather that I just altered this ticket and the pull request
instead of creating a separate ticket? One ticket along the lines of
"separated docs for attributes set by middleware and added missing
entries" seems sufficient.

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

Re: [Django] #17664: Smart `if` tag silences exceptions

2015-09-22 Thread Django

#17664: Smart `if` tag silences exceptions
-+-
 Reporter:  mrmachine|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  smart if tag | Triage Stage:  Accepted
  queryset exception silenced|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by collinanderson):

 Silencing AttributeError, KeyError, IndexError makes sense to me. Why
 silence ValueError and TypeError? Is that for filters? I suppose the more
 exceptions we catch the better backwards compatibility we get.

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

Re: [Django] #25446: Can't use PostGIS function ST_OrderingEquals with GeoDjango

2015-09-22 Thread Django

#25446: Can't use PostGIS function ST_OrderingEquals with GeoDjango
-+--
 Reporter:  ezheidtmann  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  GIS  |  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 ezheidtmann):

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


Old description:

> Unless I'm missing something, Django 1.8 provides no facility in the ORM
> to use the ST_OrderingEquals() function to compare two geometries. I
> would like to use this function in a query.
>
> Am I correct? If so, I may attempt a patch or at least a workaround.
>
> Thanks!
>
> Ref: http://postgis.net/docs/manual-1.3/ch06.html#ST_OrderingEquals

New description:

 Unless I'm missing something, Django 1.8 provides no facility in the ORM
 to use the ST_OrderingEquals() function to compare two geometries. I would
 like to use this function in a query.

 Am I correct? If so, I may attempt a patch or at least a workaround.

 Thanks!

 Ref: http://postgis.net/docs/manual-1.3/ch06.html#ST_OrderingEquals

 P.S. It's another question entirely whether the '__exact' lookup should
 use this function. For comparison, two LineString objects with opposite
 vertex ordering are not considered equal, so why should they be considered
 equal at the DB level?

--

Comment:

 For other users who may find this, here's my workaround that allows me to
 find the geometry that matches an input geometry, both in vertex values
 and in vertex ordering. A Django wizard may be able to improve this and I
 would welcome any criticism.

 {{{
 class SegmentModel(models.Model):
 ...

 @classmethod
 def get_or_create_for_line(cls, line):
 from django.contrib.gis.db.backends.postgis.adapter import
 PostGISAdapter

 sql = 'SELECT * FROM ride_segment WHERE line ~= {line_serialized}
 AND ST_OrderingEquals(line, {line_serialized})'.format(
 line_serialized=str(PostGISAdapter(line)))

 segments = list(cls.objects.raw(sql))

 if len(segments) > 1:
 from django.db import IntegrityError
 raise IntegrityError('Multiple segments for line
 {}'.format(line.ewkt))
 elif len(segments) == 0:
 return (True, cls.objects.create(line=line))
 else:
 return (False, segments[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/069.08166c2bbd81d15fbb24524928cd0d0c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #17664: Smart `if` tag silences exceptions

2015-09-22 Thread Django

Comment (by joshmaker):

I think that the behavior most developers would expect from the `{% if ...
%}` template tag is for it to handle exceptions similar to how they are
handled in template variable resolution (see:
`django.template.base.Variable`). In other words, `AttributeError`,
`KeyError`, `ValueError`, and `IndexError` as well as exceptions where
`silent_variable_failure == True` would be silenced and `False` returned,
but all other exceptions would be raised.

Here is one proposed solution:
https://github.com/django/django/compare/master...theatlantic:ticket_17664

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

Re: [Django] #25445: `AttributeError` when `app_config` is missing attribute `models_module` in contenttypes/management.py

2015-09-22 Thread Django

#25445: `AttributeError` when `app_config` is missing attribute `models_module` 
in
contenttypes/management.py
-+-
 Reporter:  pygeek   |Owner:  pygeek
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Uncategorized|  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 pygeek):

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


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

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

Re: [Django] #25445: `AttributeError` when `app_config` is missing attribute `models_module` in contenttypes/management.py (was: `AttributeError` when `app_config` is missing attribute `models_module`

2015-09-22 Thread Django

#25445: `AttributeError` when `app_config` is missing attribute `models_module` 
in
contenttypes/management.py
-+-
 Reporter:  pygeek   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Uncategorized|  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 pygeek):

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


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

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

[Django] #25446: Can't use PostGIS function ST_OrderingEquals with GeoDjango

2015-09-22 Thread Django

#25446: Can't use PostGIS function ST_OrderingEquals with GeoDjango
-+
 Reporter:  ezheidtmann  |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  GIS  |Version:  1.8
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 Unless I'm missing something, Django 1.8 provides no facility in the ORM
 to use the ST_OrderingEquals() function to compare two geometries. I would
 like to use this function in a query.

 Am I correct? If so, I may attempt a patch or at least a workaround.

 Thanks!

 Ref: http://postgis.net/docs/manual-1.3/ch06.html#ST_OrderingEquals

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

[Django] #25445: `AttributeError` when `app_config` is missing attribute `models_module` in contenttypes/mananagent.py

2015-09-22 Thread Django

#25445: `AttributeError` when `app_config` is missing attribute `models_module` 
in
contenttypes/mananagent.py
--+
 Reporter:  pygeek|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Uncategorized |Version:  1.8
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+
 ```
 if not app_config.models_module:
 return
 ```

 The return statement is never reached since if app_config doesn't have a
 `models_module` attribute it raises an AttributeError.

 Regardless of whether to allow the return statement to catch or return an
 AttributeError, this code should perhaps be changed to be more clear. I
 suggest either raising an AttributeError explicitly or using gettattr.

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

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

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

Re: [Django] #25445: `AttributeError` when `app_config` is missing attribute `models_module` in contenttypes/management.py

2015-09-22 Thread Django

#25445: `AttributeError` when `app_config` is missing attribute `models_module` 
in
contenttypes/management.py
-+-
 Reporter:  pygeek   |Owner:  pygeek
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Uncategorized|  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
-+-
Description changed by pygeek:

Old description:

> ```
> if not app_config.models_module:
> return
> ```
>
> The return statement is never reached since if app_config doesn't have a
> `models_module` attribute it raises an AttributeError.
>
> Regardless of whether to allow the return statement to catch or return an
> AttributeError, this code should perhaps be changed to be more clear. I
> suggest either raising an AttributeError explicitly or using gettattr.
>
> https://github.com/django/django/pull/5338

New description:

 {{{
 if not app_config.models_module:
 return
 }}}


 The return statement is never reached since if `app_config` doesn't have a
 `models_module` attribute it raises an `AttributeError`.

 Regardless of whether to allow the return statement to catch or return an
 `AttributeError`, this code should perhaps be changed to be more clear. I
 suggest either raising an `AttributeError` explicitly or using `gettattr`.

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

--

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

Re: [Django] #25385: Allow importing django.views.generic.View from django.views.View

2015-09-22 Thread Django

#25385: Allow importing django.views.generic.View from django.views.View
-+-
 Reporter:  jambonrose   |Owner:
 Type:   |  jambonrose
  Cleanup/optimization   |   Status:  new
Component:  Generic views|  Version:  master
 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):

 [https://groups.google.com/d/topic/django-
 developers/sdYPQnfcXGU/discussion django-developers thread]

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

Re: [Django] #25392: Allow contrib.auth to work without sessions

2015-09-22 Thread Django

#25392: Allow contrib.auth to work without sessions
--+--
 Reporter:  rdaysky   |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:  needsinfo
 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:   => needsinfo


Comment:

 rdaysky (or anyone else interested in this), if you have a patch to share,
 please send a pull request and reopen this ticket. Absent that, it's
 unclear to me what particular changes should be done (especially given
 Collin's comments about simply not using Django's built in functionality
 and building something that matches your needs).

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

Re: [Django] #25421: Twice run tests with --keepdb option in Oracle fails

2015-09-22 Thread Django

#25421: Twice run tests with --keepdb option in Oracle fails
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  Oracle test keepdb   | 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
 * stage:  Unreviewed => Accepted


Comment:

 [https://github.com/django/django/pull/5312 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/065.84eb83d09dda1c2819cd4d05ce4c8aa3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23854: Add custom SelectRelated classes

2015-09-22 Thread Django

#23854: Add custom SelectRelated classes
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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):

 See #25403 for a related or duplicate issue; in particular comment 4. If
 the solution for this ticket doesn't address that, please reopen that
 ticket.

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

Re: [Django] #25403: Subqueries: a common case where people get tempted to use .extra()

2015-09-22 Thread Django

#25403: Subqueries: a common case where people get tempted to use .extra()
-+-
 Reporter:  PaoloC68 |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  QuerySet.extra   | 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:

 I don't know, I guess it depends what's actually implemented. I'll add a
 comment on #25403 asking to reopen this ticket if it doesn't address this
 issue if/when it's completed.

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

Re: [Django] #25439: Add `SUCCESS` style to termcolor palettes

2015-09-22 Thread Django

#25439: Add `SUCCESS` style to termcolor palettes
-+-
 Reporter:  Deacalion|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  termcolor| Triage Stage:  Ready for
  termcolour colors colours  |  checkin
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:  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.f800621e9c4bff5af3a3f94920c45f43%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25443: tutorial 1: database setup fails

2015-09-22 Thread Django

#25443: tutorial 1: database setup fails
---+--
 Reporter:  xtrick |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.8
 Severity:  Normal |   Resolution:  worksforme
 Keywords:  SECRET_KEY | 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/064.78884aa4e0fb182874895ad3f928832c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25443: tutorial 1: database setup fails

2015-09-22 Thread Django

#25443: tutorial 1: database setup fails
---+--
 Reporter:  xtrick |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.8
 Severity:  Normal |   Resolution:
 Keywords:  SECRET_KEY | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by collinanderson):

 Hi, there should be a SECRECT_KEY listed in your settings.py that was
 generated when you ran startproject. Please ask on django-users for ideas
 to help diagnose. https://groups.google.com/forum/#!forum/django-users

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

Re: [Django] #25434: Missing documentation for request.site attribute

2015-09-22 Thread Django

* stage: Unreviewed => Accepted

Comment:

It seems a bit odd to me to document attributes that middleware set as
"attributes of `HttpRequest`" but given we have `request.user` documented
like that, I don't see a big reason not to document this other than
`request.user` is far more common (enabled my default in new projects)
than `request.site`. Maybe such attributes could be documented in a
separate section (as a separate ticket) to make it more obvious.

FYI, we aren't making non-critical updates to the 1.7 docs since there's
no workflow for allowing translating those updates, so we'll probably
limit this to 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/065.b6192a06c0040644de8cca0e376fb7c6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25426: pickling SimpleLazyObject fails just after accessing related object of wrapped model instance.

2015-09-22 Thread Django

#25426: pickling SimpleLazyObject fails just after accessing related object of
wrapped model instance.
--+
 Reporter:  iru   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Serialization)  |  Version:  1.8
 Severity:  Release blocker   |   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by 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/061.2516da848f17d9ebc4c7421b9fe9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24509: Allow Expressions when saving new models

2015-09-22 Thread Django

#24509: Allow Expressions when saving new models
-+-
 Reporter:  AlexHill |Owner:  Josh
 |  Smeaton 
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 Josh Smeaton ):

 * owner:   => Josh Smeaton 
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"134ca4d438bd7cbe8f0f287a00d545f96fa04a01" 134ca4d]:
 {{{
 #!CommitTicketReference repository=""
 revision="134ca4d438bd7cbe8f0f287a00d545f96fa04a01"
 Fixed #24509 -- Added Expression support to SQLInsertCompiler
 }}}

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

Re: [Django] #25443: tutorial 1: database setup fails

2015-09-22 Thread Django

#25443: tutorial 1: database setup fails
---+--
 Reporter:  xtrick |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.8
 Severity:  Normal |   Resolution:
 Keywords:  SECRET_KEY | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by xtrick):

 i have checked thoroughly and get the same result. Please Help!
  i find mention of a 'secret key' strange in itself given your database is
 not a complex one and maybe a clue in itself.
 Suggestion: Perhaps the tutorial used to work however some change has
 invalidated it.i'm also surprised to be confronted with this problem.
 i'll abandon database use until i get explanation and press on.

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

Re: [Django] #25436: Use protocol-relative URLs for OpenLayers JS / media files

2015-09-22 Thread Django

#25436: Use protocol-relative URLs for OpenLayers JS / media files
-+-
 Reporter:  blueyed  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
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
 * type:  Bug => Cleanup/optimization
 * stage:  Unreviewed => Someday/Maybe


Comment:

 Feel free to bump the ticket back to "accepted" when you resolve the
 third-party issues mentioned on the pull request.

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

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

Re: [Django] #25443: tutorial 1: database setup fails

2015-09-22 Thread Django

#25443: tutorial 1: database setup fails
---+--
 Reporter:  xtrick |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.8
 Severity:  Normal |   Resolution:
 Keywords:  SECRET_KEY | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by xtrick):

 * status:  closed => new
 * 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/064.10d2bfeedd32236442f9663eacf4c5a5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25443: tutorial 1: database setup fails

2015-09-22 Thread Django

#25443: tutorial 1: database setup fails
---+--
 Reporter:  xtrick |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.8
 Severity:  Normal |   Resolution:  worksforme
 Keywords:  SECRET_KEY | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by xtrick):

 no further comment

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

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

Re: [Django] #25420: Bash completion helper always with exit-code 1

2015-09-22 Thread Django

#25420: Bash completion helper always with exit-code 1
-+-
 Reporter:  blueyed  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |
 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 timgraham):

 * stage:  Unreviewed => Accepted


Comment:

 I haven't looked into the issue, but it seems reasonable to at least
 document why it exits with status code 1 if it's not a 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/065.fc353c2673e667029461b378b675d7b8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25444: Restructure expressions documentation to better highlight ORM support

2015-09-22 Thread Django

#25444: Restructure expressions documentation to better highlight ORM support
--+
 Reporter:  jarshwah  |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 timgraham):

 * component:  Uncategorized => Documentation
 * needs_docs:  1 => 0
 * type:  Uncategorized => Cleanup/optimization
 * 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/066.51ee631aa60abf1ea8bd1367e992836a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25442: RunSQL migration is run twice (and once for real with "--fake")

2015-09-22 Thread Django

#25442: RunSQL migration is run twice (and once for real with "--fake")
+--
 Reporter:  tino|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  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):

 Does your "users" migration have a dependency on "auth" to ensure that its
 migrations run after auth's? If you could provide a sample project that
 will save the ticket triagers some time. Thanks.

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

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

Re: [Django] #25440: Fix failing tests on Oracle GIS

2015-09-22 Thread Django

#25440: Fix failing tests on Oracle GIS
-+--
 Reporter:  jtiai|Owner:  jtiai
 Type:  Uncategorized|   Status:  closed
Component:  GIS  |  Version:  1.8
 Severity:  Release blocker  |   Resolution:  duplicate
 Keywords:  oracle gis   | 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:  assigned => closed
 * resolution:   => duplicate


Comment:

 I guess you didn't see I already created #25438 (tried to CC you, maybe it
 didn't work).

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

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

Re: [Django] #9061: formsets with can_delete=True shouldn't add delete field to extra forms

2015-09-22 Thread Django

#9061: formsets with can_delete=True shouldn't add delete field to extra forms
-+--
 Reporter:  gsf  |Owner:  danielward
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+--

Comment (by timgraham):

 Thanks for the updating patch. After you do so, don't forget to uncheck
 "Patch needs improvement" so the ticket returns to the review queue. I'll
 leave it checked for now as we've hit the feature freeze for 1.9 and the
 patch will need to be updated for 1.10 once we cut the stable/1.9.x branch
 this week.

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

Re: [Django] #24509: Allow Expressions when saving new models

2015-09-22 Thread Django

#24509: Allow Expressions when saving new models
-+-
 Reporter:  AlexHill |Owner:
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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

Re: [Django] #25426: pickling SimpleLazyObject fails just after accessing related object of wrapped model instance.

2015-09-22 Thread Django

#25426: pickling SimpleLazyObject fails just after accessing related object of
wrapped model instance.
-+-
 Reporter:  iru  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core |  Version:  1.8
  (Serialization)|
 Severity:  Release blocker  |   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 iru):

 updated model regression test :
 
https://github.com/knifenomad/django/commit/7cb818b33a0f9b8ebb658661916cefa39d438109

 test case for this issue :
 
https://github.com/knifenomad/django/commit/bf7f68f5897e5cf1b6ca2fa39bb6e901e6aaa53f

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

Re: [Django] #25426: pickling SimpleLazyObject fails just after accessing related object of wrapped model instance.

2015-09-22 Thread Django

#25426: pickling SimpleLazyObject fails just after accessing related object of
wrapped model instance.
-+-
 Reporter:  iru  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core |  Version:  1.8
  (Serialization)|
 Severity:  Release blocker  |   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 iru):

 the patch is for saving django version info as unpickler's argument
 instead of setting it as model instance's attribute which results in
 RuntimeError depending on pickling protocol.

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

Re: [Django] #25426: pickling SimpleLazyObject fails just after accessing related object of wrapped model instance.

2015-09-22 Thread Django

#25426: pickling SimpleLazyObject fails just after accessing related object of
wrapped model instance.
-+-
 Reporter:  iru  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core |  Version:  1.8
  (Serialization)|
 Severity:  Release blocker  |   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 iru):

 * Attachment "patch_25426.diff" 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/061.24561165057a133fd06bbb05de6838b3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25426: pickling SimpleLazyObject fails just after accessing related object of wrapped model instance.

2015-09-22 Thread Django

#25426: pickling SimpleLazyObject fails just after accessing related object of
wrapped model instance.
-+-
 Reporter:  iru  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core |  Version:  1.8
  (Serialization)|
 Severity:  Release blocker  |   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 iru):

 * has_patch:  0 => 1


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

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

Re: [Django] #25426: pickling SimpleLazyObject fails just after accessing related object of wrapped model instance.

2015-09-22 Thread Django

#25426: pickling SimpleLazyObject fails just after accessing related object of
wrapped model instance.
-+-
 Reporter:  iru  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core |  Version:  1.8
  (Serialization)|
 Severity:  Release blocker  |   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 iru):

 * Attachment "patch_25426.diff" 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/061.5573c6caa8d1fddd99beda312fc10b1c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

57 matches

Mail list logo