[django/django] b9a90b: Remove dsome import *

2013-10-26 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b9a90b371c90a987ed57f7a4a7cc1274c432b438
  
https://github.com/django/django/commit/b9a90b371c90a987ed57f7a4a7cc1274c432b438
  Author: Alex Gaynor 
  Date:   2013-10-26 (Sat, 26 Oct 2013)

  Changed paths:
M django/contrib/gis/db/backends/mysql/base.py
M django/contrib/gis/db/backends/oracle/base.py
M django/contrib/gis/db/backends/postgis/base.py

  Log Message:
  ---
  Remove dsome import *



-- 
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/526c8f1822b87_70fdf25d5037524%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] b35ff0: Fixed all the E203 violations

2013-10-26 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b35ff0d9208c426cc0f67c65d724972974734f57
  
https://github.com/django/django/commit/b35ff0d9208c426cc0f67c65d724972974734f57
  Author: Alex Gaynor 
  Date:   2013-10-26 (Sat, 26 Oct 2013)

  Changed paths:
M django/contrib/admin/templatetags/admin_list.py
M django/contrib/admindocs/utils.py
M django/contrib/admindocs/views.py
M django/contrib/gis/admin/options.py
M django/contrib/gis/admin/widgets.py
M django/contrib/gis/db/backends/oracle/operations.py
M django/contrib/gis/db/backends/postgis/introspection.py
M django/contrib/gis/db/backends/postgis/operations.py
M django/contrib/gis/db/backends/spatialite/introspection.py
M django/contrib/gis/db/backends/spatialite/operations.py
M django/contrib/gis/db/backends/utils.py
M django/contrib/gis/db/models/fields.py
M django/contrib/gis/db/models/query.py
M django/contrib/gis/db/models/sql/query.py
M django/contrib/gis/feeds.py
M django/contrib/gis/forms/fields.py
M django/contrib/gis/gdal/driver.py
M django/contrib/gis/gdal/geometries.py
M django/contrib/gis/gdal/geomtype.py
M django/contrib/gis/gdal/tests/test_driver.py
M django/contrib/gis/geoip/base.py
M django/contrib/gis/geoip/tests.py
M django/contrib/gis/geos/geometry.py
M django/contrib/gis/geos/tests/test_geos.py
M django/contrib/gis/management/commands/ogrinspect.py
M django/contrib/gis/maps/google/gmap.py
M django/contrib/gis/measure.py
M django/contrib/gis/sitemaps/kml.py
M django/contrib/gis/sitemaps/views.py
M django/contrib/gis/tests/geo3d/tests.py
M django/contrib/gis/tests/geoapp/feeds.py
M django/contrib/gis/tests/geoapp/sitemaps.py
M django/contrib/gis/tests/geoapp/test_regress.py
M django/contrib/gis/tests/geoapp/tests.py
M django/contrib/gis/tests/geoapp/urls.py
M django/contrib/gis/tests/geogapp/tests.py
M django/contrib/gis/tests/layermap/models.py
M django/contrib/gis/tests/layermap/tests.py
M django/contrib/gis/tests/test_spatialrefsys.py
M django/contrib/gis/utils/layermapping.py
M django/contrib/gis/utils/srs.py
M django/contrib/sites/management.py
M django/core/serializers/__init__.py
M django/core/serializers/xml_serializer.py
M django/core/urlresolvers.py
M django/forms/formsets.py
M django/test/html.py
M django/utils/translation/trans_real.py
M django/views/debug.py
M django/views/static.py
M docs/_ext/literals_to_xrefs.py
M setup.cfg
M tests/admin_views/admin.py
M tests/aggregation_regress/tests.py
M tests/cache/tests.py
M tests/forms_tests/tests/test_forms.py
M tests/model_forms/tests.py
M tests/serializers/tests.py
M tests/template_tests/filters.py
M tests/template_tests/templatetags/custom.py
M tests/template_tests/tests.py
M tests/test_client/views.py
M tests/test_utils/tests.py

  Log Message:
  ---
  Fixed all the E203 violations



-- 
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/526c6c272581a_707d90bd48125167%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21077: simple_tag does not allow kwargs with dashes in them

2013-10-26 Thread Django 
#21077: simple_tag does not allow kwargs with dashes in them
-+
 Reporter:  semenov  |Owner:
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.5
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by russellm):

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


Comment:

 I'm inclined to agree with @cbabs on this one. I can't see any compelling
 reason why a dash is helpful as a token in kwarg on a template tag. The
 fact that they're legal for the name of the template tag itself strikes me
 as an accident of parsing history, not strong design. Introducing dashes
 into kwarg syntax seems to me like something that would be syntactically
 ambiguous, and would open up a treasure trove if annoying edge case bugs.

 Marking won't fix; if anyone is particularly driven to argue the counter
 position, please open a thread on Django-dev.

-- 
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.31288aa575ce1534f85f8740bc4cd7d3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21337: backward incompability for WSGIServerException

2013-10-26 Thread Django 
#21337: backward incompability for WSGIServerException
-+--
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  HTTP handling|  Version:  1.6-beta-1
 Severity:  Release blocker  |   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 russellm):

 * severity:  Normal => Release blocker
 * needs_better_patch:   => 0
 * component:  Uncategorized => HTTP handling
 * needs_tests:   => 0
 * version:   => 1.6-beta-1
 * needs_docs:   => 0
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Comment:

 I'm not in a position to check this right now, but if true, the report is
 a release blocker.

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

Re: [Django] #21335: Bundled importlib some times won't work properly with python3.3

2013-10-26 Thread Django 
#21335: Bundled importlib some times won't work properly with python3.3
--+
 Reporter:  niwi  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Python 3  |  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 Claude Paroz ):

 In [changeset:"3b4b376bd1dde3cbe64cf8f1a4fb1756904af710"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3b4b376bd1dde3cbe64cf8f1a4fb1756904af710"
 Revert "[1.5.x] Fixed #21335 -- Use importlib from python3 when using
 python3"

 This reverts commit 1ef737416ab56a6becee36876769909a37541465.
 This would require changing some import_module calls (relative
 syntax, see ec0a3f50852), too much for a stable release.
 }}}

-- 
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.76a5bb91733d135550a54d117a1aff0c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 3b4b37: Revert "[1.5.x] Fixed #21335 -- Use importlib from...

2013-10-26 Thread GitHub 
  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 3b4b376bd1dde3cbe64cf8f1a4fb1756904af710
  
https://github.com/django/django/commit/3b4b376bd1dde3cbe64cf8f1a4fb1756904af710
  Author: Claude Paroz 
  Date:   2013-10-26 (Sat, 26 Oct 2013)

  Changed paths:
M django/utils/importlib.py

  Log Message:
  ---
  Revert "[1.5.x] Fixed #21335 -- Use importlib from python3 when using python3"

This reverts commit 1ef737416ab56a6becee36876769909a37541465.
This would require changing some import_module calls (relative
syntax, see ec0a3f50852), too much for a stable release.



-- 
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/526c360886b9_eee513d58630d4%40hookshot-fe5-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21335: Bundled importlib some times won't work properly with python3.3

2013-10-26 Thread Django 
#21335: Bundled importlib some times won't work properly with python3.3
--+
 Reporter:  niwi  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Python 3  |  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 Claude Paroz ):

 In [changeset:"ec0a3f5085219cd647d3e93841018987ce5384bf"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ec0a3f5085219cd647d3e93841018987ce5384bf"
 [1.6.x] Removed relative usage of import_module

 Python 3 version of importlib doesn't support this syntax.
 Partial backport of fdd7a355bf. Refs #21335.
 }}}

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

[django/django] ec0a3f: [1.6.x] Removed relative usage of import_module

2013-10-26 Thread GitHub 
  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: ec0a3f5085219cd647d3e93841018987ce5384bf
  
https://github.com/django/django/commit/ec0a3f5085219cd647d3e93841018987ce5384bf
  Author: Claude Paroz 
  Date:   2013-10-26 (Sat, 26 Oct 2013)

  Changed paths:
M django/contrib/gis/geometry/backend/__init__.py
M django/db/models/loading.py
M django/db/utils.py
M django/utils/formats.py

  Log Message:
  ---
  [1.6.x] Removed relative usage of import_module

Python 3 version of importlib doesn't support this syntax.
Partial backport of fdd7a355bf. Refs #21335.



-- 
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/526c34258fe0_705ae21d50861cb%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21335: Bundled importlib some times won't work properly with python3.3

2013-10-26 Thread Django 
#21335: Bundled importlib some times won't work properly with python3.3
--+
 Reporter:  niwi  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Python 3  |  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 Claude Paroz ):

 In [changeset:"1ef737416ab56a6becee36876769909a37541465"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1ef737416ab56a6becee36876769909a37541465"
 [1.5.x] Fixed #21335 -- Use importlib from python3 when using python3

 Backport of 3351e94ffa 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/062.5191db44e36016a520d6fdbc0e145d90%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 1ef737: [1.5.x] Fixed #21335 -- Use importlib from python3...

2013-10-26 Thread GitHub 
  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 1ef737416ab56a6becee36876769909a37541465
  
https://github.com/django/django/commit/1ef737416ab56a6becee36876769909a37541465
  Author: Andrey Antukh 
  Date:   2013-10-26 (Sat, 26 Oct 2013)

  Changed paths:
M django/utils/importlib.py

  Log Message:
  ---
  [1.5.x] Fixed #21335 -- Use importlib from python3 when using python3

Backport of 3351e94ffa from master.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/526c2d07cfb96_3d85713d4c53382%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] e052ad: [1.6.x] Fixed #21335 -- Use importlib from python3...

2013-10-26 Thread GitHub 
  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: e052ada0f6f21208d0f215d2f9184c4069ac1419
  
https://github.com/django/django/commit/e052ada0f6f21208d0f215d2f9184c4069ac1419
  Author: Andrey Antukh 
  Date:   2013-10-26 (Sat, 26 Oct 2013)

  Changed paths:
M django/utils/importlib.py

  Log Message:
  ---
  [1.6.x] Fixed #21335 -- Use importlib from python3 when using python3

Backport of 3351e94ffa from master.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/526c2c91ae7b7_33747b1d58267f0%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21335: Bundled importlib some times won't work properly with python3.3

2013-10-26 Thread Django 
#21335: Bundled importlib some times won't work properly with python3.3
--+
 Reporter:  niwi  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Python 3  |  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 Claude Paroz ):

 In [changeset:"e052ada0f6f21208d0f215d2f9184c4069ac1419"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e052ada0f6f21208d0f215d2f9184c4069ac1419"
 [1.6.x] Fixed #21335 -- Use importlib from python3 when using python3

 Backport of 3351e94ffa 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/062.2b987f83844a0914d254e483f43b2a74%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21335: Bundled importlib some times won't work properly with python3.3

2013-10-26 Thread Django 
#21335: Bundled importlib some times won't work properly with python3.3
--+
 Reporter:  niwi  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Python 3  |  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 Claude Paroz ):

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


Comment:

 In [changeset:"3351e94ffa37d3824a49b687125ee4a430b69bbe"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3351e94ffa37d3824a49b687125ee4a430b69bbe"
 Fixed #21335 -- Use importlib from python3 when using python3
 }}}

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

[django/django] 3351e9: Fixed #21335 -- Use importlib from python3 when us...

2013-10-26 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3351e94ffa37d3824a49b687125ee4a430b69bbe
  
https://github.com/django/django/commit/3351e94ffa37d3824a49b687125ee4a430b69bbe
  Author: Andrey Antukh 
  Date:   2013-10-26 (Sat, 26 Oct 2013)

  Changed paths:
M django/utils/importlib.py

  Log Message:
  ---
  Fixed #21335 -- Use importlib from python3 when using python3



-- 
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/526c2bd91c91c_36c56e9d58234cb%40hookshot-fe6-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21313: load tag before extends

2013-10-26 Thread Django 
#21313: load tag before extends
---+--
 Reporter:  ztorstri@… |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Uncategorized  |  Version:  1.5
 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 ztorstri@…):

 Replying to [comment:2 chrismedrela]:
 > What's wrong about putting ``BASE_TEMPLATE_NAME`` into
 ``RequestContext``? This variable doesn't seem to be secret so you don't
 need to hide it from other templates.
 >
 > Anyway, I'm -1 on emulating 'private' variables (variables visible only
 in a specific template) using template tags.

 It's not about being private, it's about being wasteful. There's no reason
 to load the variable in templates that don't relate to the app.

 I ended up writing a mixin that defines get_context and I inherit it in
 the views that need the base template.  It was a satisfactory solution,
 but I still think it's worth considering allowing template tags to be
 loaded before extends.

-- 
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/076.fdd737b668f368262dc1b2541d633b3c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 9d740e: Fix all violators of E231

2013-10-26 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 9d740eb8b15de31f1c5520659df683d90342bb44
  
https://github.com/django/django/commit/9d740eb8b15de31f1c5520659df683d90342bb44
  Author: Alex Gaynor 
  Date:   2013-10-26 (Sat, 26 Oct 2013)

  Changed paths:
M setup.cfg
M tests/admin_scripts/management/commands/base_command.py
M tests/admin_widgets/models.py
M tests/admin_widgets/tests.py
M tests/aggregation_regress/tests.py
M tests/basic/models.py
M tests/cache/tests.py
M tests/csrf_tests/tests.py
M tests/custom_columns/models.py
M tests/custom_columns_regress/models.py
M tests/decorators/tests.py
M tests/defaultfilters/tests.py
M tests/delete_regress/tests.py
M tests/dispatch/tests/test_dispatcher.py
M tests/distinct_on_fields/tests.py
M tests/extra_regress/models.py
M tests/extra_regress/tests.py
M tests/file_storage/tests.py
M tests/file_uploads/tests.py
M tests/fixtures_model_package/tests.py
M tests/forms_tests/tests/test_extra.py
M tests/forms_tests/tests/test_fields.py
M tests/forms_tests/tests/test_forms.py
M tests/forms_tests/tests/test_formsets.py
M tests/forms_tests/tests/test_input_formats.py
M tests/forms_tests/tests/test_media.py
M tests/forms_tests/tests/test_widgets.py
M tests/forms_tests/tests/tests.py
M tests/generic_views/test_dates.py
M tests/generic_views/views.py
M tests/i18n/commands/extraction.py
M tests/i18n/models.py
M tests/i18n/patterns/tests.py
M tests/inspectdb/tests.py
M tests/lookup/tests.py
M tests/m2m_recursive/tests.py
M tests/m2m_signals/tests.py
M tests/m2m_through/tests.py
M tests/m2m_through_regress/tests.py
M tests/many_to_many/tests.py
M tests/many_to_one/tests.py
M tests/max_lengths/tests.py
M tests/model_forms/tests.py
M tests/model_forms_regress/tests.py
M tests/model_formsets_regress/tests.py
M tests/model_inheritance_regress/models.py
M tests/model_inheritance_regress/tests.py
M tests/modeladmin/tests.py
M tests/multiple_database/tests.py
M tests/prefetch_related/tests.py
M tests/queries/tests.py
M tests/queryset_pickle/models.py
M tests/raw_query/tests.py
M tests/select_related_regress/tests.py
M tests/serializers/tests.py
M tests/serializers_regress/tests.py
M tests/template_tests/filters.py
M tests/template_tests/test_response.py
M tests/template_tests/test_smartif.py
M tests/template_tests/tests.py
M tests/test_client/tests.py
M tests/test_client/views.py
M tests/test_client_regress/tests.py
M tests/test_client_regress/urls.py
M tests/test_client_regress/views.py
M tests/test_runner/tests.py
M tests/update_only_fields/tests.py
M tests/urlpatterns_reverse/tests.py
M tests/utils_tests/test_datastructures.py
M tests/utils_tests/test_html.py
M tests/utils_tests/test_termcolors.py
M tests/validation/test_unique.py
M tests/validation/tests.py
M tests/view_tests/tests/test_debug.py

  Log Message:
  ---
  Fix all violators of E231



-- 
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/526c14bcdf85_330e97bd5073972%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21335: Bundled importlib some times won't work properly with python3.3

2013-10-26 Thread Django 
#21335: Bundled importlib some times won't work properly with python3.3
--+
 Reporter:  niwi  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Python 3  |  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
--+

Comment (by aaugustin):

 I'm OK with 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/062.b369f02e554638dcd92d14b71ecafbb8%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] f2d802: Fixed up some more flake8 violations (this particu...

2013-10-26 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: f2d8027c9aea93750fc4213d9e733c8575e89502
  
https://github.com/django/django/commit/f2d8027c9aea93750fc4213d9e733c8575e89502
  Author: Alex Gaynor 
  Date:   2013-10-26 (Sat, 26 Oct 2013)

  Changed paths:
M django/contrib/gis/geos/linestring.py
M django/contrib/gis/geos/tests/test_geos_mutation.py
M django/contrib/gis/geos/tests/test_mutable_list.py
M django/contrib/gis/tests/geo3d/tests.py
M django/contrib/gis/tests/geoapp/tests.py
M django/contrib/gis/tests/inspectapp/tests.py
M django/contrib/gis/tests/layermap/tests.py
M django/contrib/gis/utils/ogrinfo.py
M django/core/management/color.py
M django/core/management/commands/dumpdata.py
M django/dispatch/saferef.py
M django/forms/forms.py
M django/forms/widgets.py
M django/http/cookie.py
M django/templatetags/i18n.py
M django/test/testcases.py
M django/test/utils.py
M django/utils/cache.py
M django/utils/checksums.py
M django/utils/dates.py
M django/utils/http.py
M django/utils/translation/trans_real.py
M django/views/debug.py

  Log Message:
  ---
  Fixed up some more flake8 violations (this particular violation still has 
many occurrences in the tests/ dir so it can't be removed from setup.cfg yet)



-- 
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/526c00f3d83c5_17e2118fd4886291%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21305: Implement initial migration detection

2013-10-26 Thread Django 
#21305: Implement initial migration detection
+
 Reporter:  timo|Owner:  andrewgodwin
 Type:  Bug |   Status:  new
Component:  Migrations  |  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 CodenameTim):

 I wrote a test for this here: https://github.com/tim-
 schilling/django/commit/302ad27c2cfe0cd8765ebfa5312600056f797d27

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

Re: [Django] #21336: ListView doesnt work with context_object_name

2013-10-26 Thread Django 
#21336: ListView doesnt work with context_object_name
---+--
 Reporter:  anamsarfraz@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.5
 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 alasdair):

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


Comment:

 template_object_name was definitely replaced with context_object_name when
 changing from function to class-based generic views.

 If you grep the source code for 1.5, you can see that template_object_name
 does not appear any where in the code:

 {{{
 [django]$ git checkout 1.5
 HEAD is now at b170c07... [1.5.x] Correct final element of version tuple.
 [django]$ git grep template_object_name
 [django]$
 }}}

 Note [https://docs.djangoproject.com/en/1.4/topics/generic-views-migration
 /#the-list-suffix-on-list-views the warning in the docs] that the
 template_object_name was appended with the suffix '_list', but in a class-
 based ListView, the context_object_name is used verbatim.

 If you need further help please see
 https://code.djangoproject.com/wiki/TicketClosingReasons/UseSupportChannels

-- 
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/079.7c9fc6068673680eab84c97681d2c7d5%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21337: backward incompability for WSGIServerException

2013-10-26 Thread Django 
#21337: backward incompability for WSGIServerException
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 
https://github.com/django/django/commit/2ca00faa913754cd5860f6e1f23c8da2529c691a

 Hi this commit is backward incompatible, I think it would be better to
 assign socket.error to WSGIServerException name. Or fill documentation and
 describe this change. I just updated from Beta 1 to RC 1 and non of my
 servers works.

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

Re: [Django] #19750: Postgres conflict on CREATE INDEX: "relation exists"

2013-10-26 Thread Django 
#19750: Postgres conflict on CREATE INDEX: "relation exists"
-+-
 Reporter:  pricco@… |Owner:
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |  1.5-beta-1
 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 claudep):

 This ''might'' be a solution:
 {{{
 --- a/django/db/backends/postgresql_psycopg2/creation.py
 +++ b/django/db/backends/postgresql_psycopg2/creation.py
 @@ -65,8 +65,9 @@ class DatabaseCreation(BaseDatabaseCreation):
  "(%s%s)" % (style.SQL_FIELD(qn(f.column)),
 opclass) +
  "%s;" % tablespace_sql)

 +index_name = "%s_%s" % (model._meta.db_table,
 self._digest([f.name]))
  if not f.unique:
 -output = [get_index_sql('%s_%s' % (db_table, f.column))]
 +output = [get_index_sql(index_name)]

  # Fields with database column types of `varchar` and `text`
 need
  # a second index that specifies their operator class, which
 is
 @@ -74,9 +75,9 @@ class DatabaseCreation(BaseDatabaseCreation):
  # C locale. See #12234.
  db_type = f.db_type(connection=self.connection)
  if db_type.startswith('varchar'):
 -output.append(get_index_sql('%s_%s_like' % (db_table,
 f.column),
 +output.append(get_index_sql('%s_like' % index_name,
  ' varchar_pattern_ops'))
  elif db_type.startswith('text'):
 -output.append(get_index_sql('%s_%s_like' % (db_table,
 f.column),
 +output.append(get_index_sql('%s_like' % index_name,
  ' text_pattern_ops'))
  return output
 }}}

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

Re: [Django] #19750: Postgres conflict on CREATE INDEX: "relation exists"

2013-10-26 Thread Django 
#19750: Postgres conflict on CREATE INDEX: "relation exists"
-+-
 Reporter:  pricco@… |Owner:
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |  1.5-beta-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

 * needs_better_patch:  0 => 1
 * needs_tests:  1 => 0


Comment:

 Thanks for the updated patch.
 However, I investigated some more, and I think I found the basic issue. At
 some point in time, `sql_indexes_for_field` has been customized for
 PostgreSQL because it needed some special indexes (see [f1ea26dd99415d]).
 Then, the common `sql_indexes_for_field` received several fixes and
 improvements, namely a change in the index naming using a hash of column
 names ([9d8492c169d]), without having the PostgreSQL version being
 updated.
 For example, while investigating this, I found a bug in that `sqlindexes`
 and `sqldropindexes` do not use the same index names and are therefore
 broken for PostgreSQL!
 I think that the proper fix for this ticket is to somewhat reconcile
 `sql_indexes_for_field` implementations. The new index naming usage will
 automatically fix the current 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/074.20eaee86cbebf56cad133c4d959ec2ca%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21077: simple_tag does not allow kwargs with dashes in them

2013-10-26 Thread Django 
#21077: simple_tag does not allow kwargs with dashes in them
-+
 Reporter:  semenov  |Owner:
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by marfire):

 The template language doesn't appear to have been designed to be as
 restrictive as you are calling for. For example, `{% foo-bar %}` ''is'' a
 perfectly valid template tag name. `{{ my_var|my-filter }}` and `{% my_tag
 my-arg %}` are also valid.

 And `{% my_tag my-kwarg=5 %}` is valid if the template tag author doesn't
 use `simple_tag()`. The question is why it shouldn't also be possible to
 use `simple_tag()` in this case. The original reason, presumably, was to
 ensure that keyword arguments could be listed in the function signature
 (as noted, though, `kwarg_re` fails to ensure that).

 To me it seems better to treat these keyword arguments like other strings
 in the template language (allowing `-`, etc.); in addition to being more
 consistent, this would improve the usefulness of `simple_tag()`, as in
 semenov's use case. This solution also appears to be backwards compatible.

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

Re: [Django] #21335: Bundled importlib some times won't work properly with python3.3

2013-10-26 Thread Django 
#21335: Bundled importlib some times won't work properly with python3.3
--+
 Reporter:  niwi  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Python 3  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Bug
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 I think this is a safe change and I'm ready to do the backporting job.
 However, I'd like to get fellow core devs approval before going forward.

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

Re: [Django] #21333: Undocumented queryset OR should be documented, probably

2013-10-26 Thread Django 
#21333: Undocumented queryset OR should be documented, probably
--+
 Reporter:  EvilDMP   |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
--+

Comment (by mjtamlyn):

 Whilst we shouldn't say this isn't possible, we do need to be careful with
 it as there is an obvious footgun - you could easily end up with
 additional queries if one of your earlier querysets got executed for some
 reason

 Personally, I'm not completely sure why this is 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/065.842725b954db7d7890811234098561f3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19750: Postgres conflict on CREATE INDEX: "relation exists"

2013-10-26 Thread Django 
#19750: Postgres conflict on CREATE INDEX: "relation exists"
-+-
 Reporter:  pricco@… |Owner:
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |  1.5-beta-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by pricco):

 New pull request with tests:
 https://github.com/django/django/pull/1813

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