date:20130922

Re: [Django] #21126: Potential data corruption issue with Oracle and Mysql due to SQLCompiler.resolve_columns row, fields misalignment

2013-09-22 Thread Django

#21126: Potential data corruption issue with Oracle and Mysql due to
SQLCompiler.resolve_columns row, fields misalignment
-+-
 Reporter:  manfre   |Owner:  manfre
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by akaariai):

 The test would need to have
 .annotate(someaggregate).select_related(a_model_containing_boolean_field).
 This should break MySQL's value conversion, that is, the boolean field
 isn't converted to True/False, instead it remains as the database return
 value of 1/0.

 I can try to write a test tonight, but I can't guarantee anything.

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

Re: [Django] #21001: Non working SQL generated for Oracle when doing .exclude('')

2013-09-22 Thread Django

#21001: Non working SQL generated for Oracle when doing .exclude('')
-+-
 Reporter:  greenRocker  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:  oracle   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by akaariai):

 Yes, adding a test would be good.

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

Re: [Django] #21126: Potential data corruption issue with Oracle and Mysql due to SQLCompiler.resolve_columns row, fields misalignment

2013-09-22 Thread Django

#21126: Potential data corruption issue with Oracle and Mysql due to
SQLCompiler.resolve_columns row, fields misalignment
-+-
 Reporter:  manfre   |Owner:  manfre
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by charettes):

 * cc: charettes (added)


Comment:

 @manfre I confirm I marked the patch as needing improvement because it
 lacks tests which could help spot future regressions.

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

Re: [Django] #21001: Non working SQL generated for Oracle when doing .exclude('')

2013-09-22 Thread Django

#21001: Non working SQL generated for Oracle when doing .exclude('')
-+-
 Reporter:  greenRocker  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:  oracle   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * cc: charettes (added)


Comment:

 @akaariai do you think it might be worth adding the test case to the suite
 to spot future regressions?

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

Re: [Django] #20830: Bad URL for six.moves in "Porting to Python 3 / Moved modules"

2013-09-22 Thread Django

#20830: Bad URL for six.moves in "Porting to Python 3 / Moved modules"
-+-
 Reporter:  glarrain |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  six, python3,| Triage Stage:  Accepted
  afraid-to-commit   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by timo):

 Django includes a copy of six, hence the `django.utils.six.moves`
 reference. In the context of the sentence, it makes sense to reference
 this location.

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

Re: [Django] #20830: Bad URL for six.moves in "Porting to Python 3 / Moved modules"

2013-09-22 Thread Django

#20830: Bad URL for six.moves in "Porting to Python 3 / Moved modules"
-+-
 Reporter:  glarrain |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  six, python3,| Triage Stage:  Accepted
  afraid-to-commit   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by EvilDMP):

 * cc: EvilDMP (added)
 * keywords:  six, python3 => six, python3, afraid-to-commit
 * easy:  0 => 1


Old description:

> The renderized URL is http://pythonhosted.org/six/index.html#six.moves
> and should be http://pythonhosted.org/six/index.html#module-six.moves
>
> I traced the error to lines 368 and 371 in the
> [https://github.com/django/django/blob/master/docs/topics/python3.txt rst
> source file] but my knowledge of reStructuredText is very limited.
>
> Also, it seems weird to have a hyperlink with value
> "django.utils.six.moves" pointing to the actual "six" documentation since
> Django includes a custom version of it, albeit very similar. Perhaps it
> will be clearer to have something like "six.moves ".

New description:

 The renderized URL is http://pythonhosted.org/six/index.html#six.moves and
 should be http://pythonhosted.org/six/index.html#module-six.moves

 I traced the error to lines 368 and 371 in the
 [https://github.com/django/django/blob/master/docs/topics/python3.txt rst
 source file] but my knowledge of reStructuredText is very limited.

 Also, it seems weird to have a hyperlink with value
 "django.utils.six.moves" pointing to the actual "six" documentation since
 Django includes a custom version of it, albeit very similar. Perhaps it
 will be clearer to have something like "six.moves ".

 Marked as easy-pickings for the second issue. I'm not sure what's going on
 with the first.

--

Comment:

 Sphinx on my local installation also renders the links to
 `http://pythonhosted.org/six/index.html#module-six.moves` and
 `http://pythonhosted.org/six/index.html#module-six` incorrectly, failing
 to include the `module-` part.

 There's still the second issue, which we can do something about, where our
 docs say:

 {{{
 Some modules were renamed in Python 3. The :mod:`django.utils.six.moves
 ` module provides a compatible location to import them.
 }}}

 In other words, we are referring to a Python module (``), but
 the hyperlink text (`django.utils.six.moves`) appears to refer to
 something in Django, so that hyperlink text should be changed. We could
 say something like:

 {{{
 The Python :mod:`six.moves ` module...
 }}}

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

Re: [Django] #20834: Document how user permission caching works

2013-09-22 Thread Django

#20834: Document how user permission caching works
--+
 Reporter:  Giggaflop |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Documentation |  Version:
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by EvilDMP):

 * keywords:   => afraid-to-commit
 * cc: EvilDMP (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/067.1dc154d86a99bce08f9186816af71071%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20863: Sessions backend changing could be clearer

2013-09-22 Thread Django

#20863: Sessions backend changing could be clearer
-+-
 Reporter:  Keryn Knight |Owner:  nobody
   |   Status:  new
 Type:   |  Version:  master
  Cleanup/optimization   |   Resolution:
Component:  Documentation| Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by EvilDMP):

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

Re: [Django] #20910: Specify the filename (when appropriate) with code snippets

2013-09-22 Thread Django

#20910: Specify the filename (when appropriate) with code snippets
-+-
 Reporter:  jggramlich@… |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  tutorial, afraid-|  Needs documentation:  0
  to-commit  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by EvilDMP):

 * cc: EvilDMP (added)
 * keywords:  tutorial => tutorial, afraid-to-commit


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

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

Re: [Django] #20910: Specify the filename (when appropriate) with code snippets

2013-09-22 Thread Django

#20910: Specify the filename (when appropriate) with code snippets
--+
 Reporter:  jggramlich@…  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:  tutorial  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by EvilDMP):

 Replying to [comment:4 jggramlich@…]:
 > Fair enough.  Your point about "...pain in my ass" is well taken.
 >
 > What is the possibility of making the documentation into a wiki (I know
 this is not a small task) so that users can contribute easily?  Is this
 being considered?  You mentioned a "patch" earlier, which I can understand
 for code issues...but a patch...I don't know where to even begin for
 "patching" docs.  I'd be more than happy to contribute (once I figure this
 stuff out).
 >
 > If there is an process for patching docs, I'm all ears.

 There is. And if you don't know where to start, start at http://dont-be-
 afraid-to-commit.readthedocs.org, which takes you through the entire
 process and includes a section on writing up documentation. I'm happy to
 help with that if you need it.

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

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

Re: [Django] #20962: Documentation on template tag render() methods is inconsistent with core tags.

2013-09-22 Thread Django

#20962: Documentation on template tag render() methods is inconsistent with core
tags.
-+-
 Reporter:  Keryn Knight |Owner:  nobody
   |   Status:  new
 Type:   |  Version:  master
  Cleanup/optimization   |   Resolution:
Component:  Documentation| Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  afraid-to-commit |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by EvilDMP):

 * keywords:   => afraid-to-commit
 * cc: EvilDMP (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/095.d995aa99a4da5168480683105fc6f6b2%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21144: Not possible to update foreign key by id for a queryset

2013-09-22 Thread Django

#21144: Not possible to update foreign key by id for a queryset
-+-
 Reporter:  dakinsloss@… |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.5
Component:  Database layer   |   Resolution:  invalid
  (models, ORM)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:  update, related  |  Needs documentation:  0
  model, performance |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by dakinsloss@…):

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


Comment:

 My mistake--this should not have been submitted, was still debugging and
 this is not an 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/078.53007d5aa86debbd1e3e25f75b6941c3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21006: Add an example of the formset argument for inlineformset_factory

2013-09-22 Thread Django

#21006: Add an example of the formset argument for inlineformset_factory
--+
 Reporter:  treysta@… |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by EvilDMP):

 * cc: EvilDMP (added)
 * keywords:   => afraid-to-commit


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

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

Re: [Django] #21027: remember Tutorial users to invoke the shell by "python manage.py shell" before setting up the test environment

2013-09-22 Thread Django

#21027: remember Tutorial users to invoke the shell by "python manage.py shell"
before setting up the test environment
-+-
 Reporter:  anonymous|Owner:  bussau
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  "Tutorial 1.5" / |  Needs documentation:  0
  "Test a view", afraid-to-commit|  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by EvilDMP):

 * keywords:  "Tutorial 1.5" / "Test a view" => "Tutorial 1.5" / "Test a
 view", afraid-to-commit
 * cc: EvilDMP (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/067.47e4304b4e131f7fbceb9b0e549d480a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21031: Remember to update Q#3 in the DB section of the FAQ

2013-09-22 Thread Django

#21031: Remember to update Q#3 in the DB section of the FAQ
--+
 Reporter:  ramiro|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by EvilDMP):

 * keywords:   => afraid-to-commit
 * cc: EvilDMP (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/064.e5d875fbf30fe05790a1c90237eeedf8%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21070: Clarify document DATABASES change

2013-09-22 Thread Django

#21070: Clarify document DATABASES change
--+
 Reporter:  joejasinski   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by EvilDMP):

 * keywords:   => afraid-to-commit
 * cc: EvilDMP (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/069.d7ef08ce7d955730dd83852e139a991e%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21111: generic.View.init should call super

2013-09-22 Thread Django

#2: generic.View.__init__ should call super
--+
 Reporter:  glin@…|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Generic views |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by EvilDMP):

 * keywords:   => afraid-to-commit
 * cc: EvilDMP (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/072.6e1d9f193600cef79452092be01dbb63%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21072: Square Bullets

2013-09-22 Thread Django

#21072: Square Bullets
-+-
 Reporter:  moc@…|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.6-alpha-1
 Severity:  Normal   |   Resolution:
 Keywords:  bullet indentation,  | Triage Stage:  Accepted
  afraid-to-commit   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by EvilDMP):

 * keywords:  bullet indentation => bullet indentation, afraid-to-commit
 * cc: EvilDMP (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/071.5d2ad967a3989dea2d81f3737b5046b8%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21144: Not possible to update foreign key by id for a queryset

2013-09-22 Thread Django

#21144: Not possible to update foreign key by id for a queryset
-+-
 Reporter:  dakinsloss@… |  Owner:  nobody
 Type:   | Status:  new
  Cleanup/optimization   |Version:  1.5
Component:  Database layer   |   Keywords:  update, related model,
  (models, ORM)  |  performance
 Severity:  Normal   |  Has patch:  0
 Triage Stage:  Unreviewed   |  UI/UX:  0
Easy pickings:  0|
-+-
 Attempting to minimize queries when updating list of ModelA instances that
 have foreign keys to ModelB, and I know the ids of the new ModelB
 instances I want to use for the instances of ModelA (that I only have the
 id for, not the instance).

 Trying:
 ModelA.objects.filter(pk=id_of_a_instance).update(b_id=id_of_b_instance)
 which yields 'FieldNameDoesNotExist' because 'get_field_by_name' only has
 'b' as a field name for ModelA, not b_id (which is strange given that is
 what is actually stored).

 Then I try:
 ModelA.objects.filter(pk=id_of_a_instance).update(b=id_of_b_instance),
 which says it needs an instance of ModelB, not a number.

 Which means I will be stuck with an extra query:
 model_b_list = list(ModelB.objects.filter(id_in=[list of ids for a
 instances])
 and then have to iterate through the ModelA instances and assign the
 actual ModelB instances

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

Re: [Django] #21134: Documentation for transaction.atomic needs more explicit warning about catching DatabaseErrors

2013-09-22 Thread Django

Comment (by aaugustin):

This pull request prevents running queries in `atomic` blocks that are
going to end with a rollback.

Since `atomic` is a new API, this change looks like it's backwards
compatible. Unfortunately, it isn't, because some features already take
advantage of `atomic` internally.

Specifically `django.test.TestCase` wraps each test in an `atomic` block.
As a consequence, tests that ran queries after database errors will
require modifications, even if the query is a rollback to a previous
savepoint. That said:

- If it's a test for transactional behavior, it should be in a
`TransactionTestCase`. Quite obviously high-level and low-level APIs
cannot be mixed arbitrarily.
- If the savepoint is used to recover from a database error, it's much
easier to recover with an `atomic` block. This is how I fixed the few
tests that were broken by this change in Django's test suite.

If we decide to go with this approach, I'll add this to the transactions
docs or the release notes.

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

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

[django/django] 1fa8c6: [1.5.x] Stopped a test from executing queries at t...

2013-09-22 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 1fa8c612fc764c456f4d838805ff7fd5634b1e16
  
https://github.com/django/django/commit/1fa8c612fc764c456f4d838805ff7fd5634b1e16
  Author: Florian Apolloner 
  Date:   2013-09-22 (Sun, 22 Sep 2013)

  Changed paths:
M tests/regressiontests/transactions_regress/tests.py

  Log Message:
  ---
  [1.5.x] Stopped a test from executing queries at the module level.

Currently module level queries are executed against the real database
(specified in NAME) instead of the test database; since it is to late
to fix this for 1.6, we at least ensures stable builds. Refs #21443.

Backport of 4fcc1e4ad8d153f41132b171c231b6d5d4086c28 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/523f5c411471_5a54845d50106ee%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] eb32de: [1.6.x] Stopped a test from executing queries at t...

2013-09-22 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: eb32de26145f605940f3b6fd8f708d1b4fce3a4a
  
https://github.com/django/django/commit/eb32de26145f605940f3b6fd8f708d1b4fce3a4a
  Author: Florian Apolloner 
  Date:   2013-09-22 (Sun, 22 Sep 2013)

  Changed paths:
M tests/transactions_regress/tests.py

  Log Message:
  ---
  [1.6.x] Stopped a test from executing queries at the module level.

Currently module level queries are executed against the real database
(specified in NAME) instead of the test database; since it is to late
to fix this for 1.6, we at least ensures stable builds. Refs #21443.

Backport of 4fcc1e4ad8d153f41132b171c231b6d5d4086c28 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/523f5ba8479c9_43b146fd4c73855%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 4fcc1e: Stopped a test from executing queries at the modul...

2013-09-22 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4fcc1e4ad8d153f41132b171c231b6d5d4086c28
  
https://github.com/django/django/commit/4fcc1e4ad8d153f41132b171c231b6d5d4086c28
  Author: Florian Apolloner 
  Date:   2013-09-22 (Sun, 22 Sep 2013)

  Changed paths:
M tests/transactions_regress/tests.py

  Log Message:
  ---
  Stopped a test from executing queries at the module level.

Currently module level queries are executed against the real database
(specified in NAME) instead of the test database; since it is to late
to fix this for 1.6, we at least ensures stable builds. Refs #21443.



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

[Django] #21143: runtests might execute queries against the normal database instead of the testdatabase

2013-09-22 Thread Django

#21143: runtests might execute queries against the normal database instead of 
the
testdatabase
-+
   Reporter:  apollo13   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Testing framework  |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  |
-+
 The way our testrunner currently works is that it constructs the test
 classes before creating the test database and resetting the database
 names. This causes module level queries (which you shouldn't have, but…)
 to be executed against the main database resulting in errors like:

 {{{
 Traceback (most recent call last):
   File "/usr/lib/python3.3/unittest/case.py", line 384, in
 _executeTestPart
 function()
   File "/usr/lib/python3.3/unittest/loader.py", line 32, in testFailure
 raise exception
 ImportError: Failed to import test module: transactions_regress.tests
 Traceback (most recent call last):
   File
 
"/var/lib/jenkins/jobs/Django/workspace/database/mysql_gis/python/python3.3/django/db/utils.py",
 line 101, in inner
 return func(*args, **kwargs)
   File
 
"/var/lib/jenkins/jobs/Django/workspace/database/mysql_gis/python/python3.3/django/db/backends/mysql/base.py",
 line 131, in execute
 return self.cursor.execute(query, args)
   File "/usr/local/lib/python3.3/dist-packages/MySQL_python-1.2.3-py3.3
 -linux-x86_64.egg/MySQLdb/cursors.py", line 185, in execute
 self.errorhandler(self, exc, value)
   File "/usr/local/lib/python3.3/dist-packages/MySQL_python-1.2.3-py3.3
 -linux-x86_64.egg/MySQLdb/connections.py", line 37, in defaulterrorhandler
 raise errorvalue
   File "/usr/local/lib/python3.3/dist-packages/MySQL_python-1.2.3-py3.3
 -linux-x86_64.egg/MySQLdb/cursors.py", line 172, in execute
 r = self._query(query)
   File "/usr/local/lib/python3.3/dist-packages/MySQL_python-1.2.3-py3.3
 -linux-x86_64.egg/MySQLdb/cursors.py", line 332, in _query
 rowcount = self._do_query(q)
   File "/usr/local/lib/python3.3/dist-packages/MySQL_python-1.2.3-py3.3
 -linux-x86_64.egg/MySQLdb/cursors.py", line 296, in _do_query
 db.query(q)
 _mysql_exceptions.OperationalError: (1050, "Table 'INTROSPECT_TEST'
 already exists")
 }}}

 In the case above this is caused by two parallel testruns against
 different TEST_NAMEs but the same NAME in the database config. It would be
 nice if we could fix 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/051.6f2825a5de2026bfcb72c0cf44ba7faa%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21134: Documentation for transaction.atomic needs more explicit warning about catching DatabaseErrors

2013-09-22 Thread Django

#21134: Documentation for transaction.atomic needs more explicit warning about
catching DatabaseErrors
-+-
 Reporter:  RichardOfWard|Owner:  aaugustin
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.6-beta-1
 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 aaugustin):

 * status:  closed => new
 * has_patch:  0 => 1
 * resolution:  fixed =>


Comment:

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

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

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

[django/django] e6c002: Translated a test to English for consistency.

2013-09-22 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e6c0020d1973abf168c3a2357ab4cf44fa2d47ca
  
https://github.com/django/django/commit/e6c0020d1973abf168c3a2357ab4cf44fa2d47ca
  Author: Aymeric Augustin 
  Date:   2013-09-22 (Sun, 22 Sep 2013)

  Changed paths:
M tests/get_or_create/tests.py
M tests/transactions/tests.py

  Log Message:
  ---
  Translated a test to English for consistency.

Also fixed a typo.



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

[Django] #21142: Referencing the User model and migrations

2013-09-22 Thread Django

#21142: Referencing the User model and migrations
-+-
 Reporter:  mario.pfeifer@…  |  Owner:
 Type:  Bug  | Status:  new
Component:  Migrations   |Version:  master
 Severity:  Normal   |   Keywords:  Migration, Auth
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 Hi,

 To verify this bug I use a very simple model in which I reference to the
 User model:

 {{{
 from django.conf import settings
 from django.db import models


 class Article(models.Model):
 name = models.CharField('Name', max_length=255)
 author = models.ForeignKey(settings.AUTH_USER_MODEL)
 }}}

 After running ./manage.py makemigrations everything looks fine:

 {{{
 Do you want to enable migrations for app 'articles'? [y/N] y
 Migrations for 'articles':
   0001_initial.py:
 - Create model Article
 }}}

 But running ./manage.py migrate runs into following error:

 {{{
 Traceback (most recent call last):
   File "./manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/home/mario/django-trunk/django/core/management/__init__.py", line
 397, in execute_from_command_line
 utility.execute()
   File "/home/mario/django-trunk/django/core/management/__init__.py", line
 390, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/mario/django-trunk/django/core/management/base.py", line
 242, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/home/mario/django-trunk/django/core/management/base.py", line
 289, in execute
 output = self.handle(*args, **options)
   File "/home/mario/django-
 trunk/django/core/management/commands/migrate.py", line 88, in handle
 targets = executor.loader.graph.leaf_nodes()
   File "/home/mario/django-trunk/django/utils/functional.py", line 49, in
 __get__
 res = instance.__dict__[self.func.__name__] = self.func(instance)
   File "/home/mario/django-trunk/django/db/migrations/loader.py", line
 169, in graph
 graph.add_dependency(key, parent)
   File "/home/mario/django-trunk/django/db/migrations/graph.py", line 40,
 in add_dependency
 raise KeyError("Dependency references nonexistent parent node %r" %
 (parent,))
 KeyError: "Dependency references nonexistent parent node (u'auth',
 '0001_initial')"
 }}}

 The same happens when I directly reference to the User model:

 {{{
 from django.contrib.auth.models import User
 from django.db import models


 class Article(models.Model):
 name = models.CharField('Name', max_length=255)
 author = models.ForeignKey(User)
 }}}

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

[django/django] 18fe77: [1.5.x] Fixed "Address already in use" from livese...

2013-09-22 Thread GitHub

Branch: refs/heads/stable/1.5.x
Home: https://github.com/django/django
Commit: 18fe77e4ed01a7761a24de7ec7b1c3a1314fc197

https://github.com/django/django/commit/18fe77e4ed01a7761a24de7ec7b1c3a1314fc197
Author: Florian Apolloner
Date: 2013-09-22 (Sun, 22 Sep 2013)

Changed paths:
M django/core/management/commands/runserver.py
M django/core/servers/basehttp.py
M django/test/testcases.py
M tests/regressiontests/servers/tests.py

Log Message:
---
[1.5.x] Fixed "Address already in use" from liveserver.

Our WSGIServer rewrapped the socket errors from server_bind into
WSGIServerExceptions, which is used later on to provide nicer
error messages in runserver and used by the liveserver to see if
the port is already in use. But wrapping server_bind isn't enough since
it only binds to the socket, socket.listen (which is called from
server_activate) could also raise "Address already in use".

Instead of overriding server_activate too I chose to just catch socket
errors, which seems to make more sense anyways and should be more robust
against changes in wsgiref.

Backport of 2ca00faa913754cd5860f6e1f23c8da2529c691a 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/523f4e9de7db8_4fff146bd5057734%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 56201f: [1.6.x] Fixed "Address already in use" from livese...

2013-09-22 Thread GitHub

Branch: refs/heads/stable/1.6.x
Home: https://github.com/django/django
Commit: 56201fe5a85ead96f00d8ad2eda5cfd2bc4cb4b0

https://github.com/django/django/commit/56201fe5a85ead96f00d8ad2eda5cfd2bc4cb4b0
Author: Florian Apolloner
Date: 2013-09-22 (Sun, 22 Sep 2013)

Changed paths:
M django/core/management/commands/runserver.py
M django/core/servers/basehttp.py
M django/test/testcases.py
M tests/servers/tests.py

Log Message:
---
[1.6.x] Fixed "Address already in use" from liveserver.

Instead of overriding server_activate too I chose to just catch socket
errors, which seems to make more sense anyways and should be more robust
against changes in wsgiref.

Backport of 2ca00faa913754cd5860f6e1f23c8da2529c691a 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/523f4d74d7003_4f811313d5490585%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 2ca00f: Fixed "Address already in use" from liveserver.

2013-09-22 Thread GitHub

Branch: refs/heads/master
Home: https://github.com/django/django
Commit: 2ca00faa913754cd5860f6e1f23c8da2529c691a

https://github.com/django/django/commit/2ca00faa913754cd5860f6e1f23c8da2529c691a
Author: Florian Apolloner
Date: 2013-09-22 (Sun, 22 Sep 2013)

Changed paths:
M django/core/management/commands/runserver.py
M django/core/servers/basehttp.py
M django/test/testcases.py
M tests/servers/tests.py

Log Message:
---
Fixed "Address already in use" from liveserver.

Instead of overriding server_activate too I chose to just catch socket
errors, which seems to make more sense anyways and should be more robust
against changes in wsgiref.

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

Re: [Django] #20693: Add timezone support to built-in time filter

2013-09-22 Thread Django

#20693: Add timezone support to built-in time filter
-+-
 Reporter:  warren@… |Owner:  wsmith323
 Type:  New feature  |   Status:  closed
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Ramiro Morales ):

 In [changeset:"bebb449ac334d7365a015b34b9c894dc4bf63f7f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="bebb449ac334d7365a015b34b9c894dc4bf63f7f"
 Added docs for changes in commit dd3a883894.

 Refs #20693.
 }}}

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

[django/django] bebb44: Added docs for changes in commit dd3a883894.

2013-09-22 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: bebb449ac334d7365a015b34b9c894dc4bf63f7f
  
https://github.com/django/django/commit/bebb449ac334d7365a015b34b9c894dc4bf63f7f
  Author: Ramiro Morales 
  Date:   2013-09-22 (Sun, 22 Sep 2013)

  Changed paths:
M docs/ref/templates/builtins.txt
M docs/releases/1.7.txt

  Log Message:
  ---
  Added docs for changes in commit dd3a883894.

Refs #20693.



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

Re: [Django] #21134: Documentation for transaction.atomic needs more explicit warning about catching DatabaseErrors

2013-09-22 Thread Django

#21134: Documentation for transaction.atomic needs more explicit warning about
catching DatabaseErrors
-+-
 Reporter:  RichardOfWard|Owner:  aaugustin
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.6-beta-1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 In practice there isn't any difference between "DatabaseErrors" and
 "errors that bubble out of atomic(savepoint=False)". The only non-fatal
 exceptions expected inside an atomic(savepoint=False) block in Django are
 DatabaseErrors.

 After taking into account the warning I added, your example becomes:
 {{{
 r1 = Reporter.objects.create(first_name='foo', last_name='bar')
 with transaction.atomic():
  r2 = Reporter(first_name='foo', last_name='bar2', id=r1.id)
  try:
  with transaction.atomic():
  r2.save(force_insert=True)
  except IntegrityError:
 r2.save(force_update=True)
 self.assertEqual(Reporter.objects.get(pk=r1.pk).last_name, 'bar2')
 }}}
 which behaves correctly.

 But it's unrealistic to hope that everyone will do that without
 complaining, especially people used to databases with a loose (non-atomic)
 transaction implementation.

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

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

Re: [Django] #21134: Documentation for transaction.atomic needs more explicit warning about catching DatabaseErrors

2013-09-22 Thread Django

#21134: Documentation for transaction.atomic needs more explicit warning about
catching DatabaseErrors
-+-
 Reporter:  RichardOfWard|Owner:  aaugustin
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.6-beta-1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by akaariai):

 The committed documentation changes aren't about what I have been
 complaining about. I have said numerous times that *this is not about
 DatabaseErrors*. This is about any error that bubbles out of
 atomic(savepoint=False) block.

 The problem is this:
 {{{
 r1 = Reporter.objects.create(first_name='foo', last_name='bar')
 with transaction.atomic():
  r2 = Reporter(first_name='foo', last_name='bar2', id=r1.id)
  try:
  r2.save(force_insert=True)
  except IntegrityError:
 r2.save(force_update=True)
 self.assertEqual(Reporter.objects.get(pk=r1.pk).last_name, 'bar2')
 }}}

 The last assert fails. This is unexpected for anybody using a database
 where this pattern is allowed (as far as I know any db other than
 PostgreSQL). Note that there isn't any explicit use of
 atomic(savepoint=False) blocks. Also, the exception *does not need to be
 DatabaseError subclass at all*.

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

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

Re: [Django] #21141: Update Sphinx URL

2013-09-22 Thread Django

#21141: Update Sphinx URL
-+-
 Reporter:  yokomizor|Owner:  yokomizor
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Rogério Yokomizo ):

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


Comment:

 In [changeset:"1b4b710355057b279c1e7d10b6b0d846ee98444e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1b4b710355057b279c1e7d10b6b0d846ee98444e"
 Fixed #21141 -- Update Sphinx URL
 Updated Sphinx URL from http://sphinx.pocoo.org/ to http://sphinx-
 doc.org/.
 }}}

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

Re: [Django] #21141: Update Sphinx URL

2013-09-22 Thread Django

#21141: Update Sphinx URL
-+-
 Reporter:  yokomizor|Owner:  yokomizor
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"5a64f9bcbd922a5b7024e621b375f025ae30d2a1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5a64f9bcbd922a5b7024e621b375f025ae30d2a1"
 Merge pull request #1658 from yokomizor/updated_sphinx_url

 Fixed #21141 -- Updated Sphinx URL.
 }}}

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

[django/django] 1b4b71: Fixed #21141 -- Update Sphinx URL

2013-09-22 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1b4b710355057b279c1e7d10b6b0d846ee98444e
  
https://github.com/django/django/commit/1b4b710355057b279c1e7d10b6b0d846ee98444e
  Author: Rogério Yokomizo 
  Date:   2013-09-22 (Sun, 22 Sep 2013)

  Changed paths:
M docs/README
M docs/conf.py
M docs/internals/contributing/writing-documentation.txt
M docs/intro/whatsnext.txt
M docs/releases/1.0-beta-2.txt

  Log Message:
  ---
  Fixed #21141 -- Update Sphinx URL
Updated Sphinx URL from http://sphinx.pocoo.org/ to http://sphinx-doc.org/.


  Commit: 5a64f9bcbd922a5b7024e621b375f025ae30d2a1
  
https://github.com/django/django/commit/5a64f9bcbd922a5b7024e621b375f025ae30d2a1
  Author: Aymeric Augustin 
  Date:   2013-09-22 (Sun, 22 Sep 2013)

  Changed paths:
M docs/README
M docs/conf.py
M docs/internals/contributing/writing-documentation.txt
M docs/intro/whatsnext.txt
M docs/releases/1.0-beta-2.txt

  Log Message:
  ---
  Merge pull request #1658 from yokomizor/updated_sphinx_url

Fixed #21141 -- Updated Sphinx URL.


Compare: https://github.com/django/django/compare/ce0c5c38ea77...5a64f9bcbd92

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

Re: [Django] #21141: Update Sphinx URL

2013-09-22 Thread Django

#21141: Update Sphinx URL
-+-
 Reporter:  yokomizor|Owner:  yokomizor
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by yokomizor):

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


Comment:

 Path: https://github.com/django/django/pull/1658

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

[Django] #21141: Update Sphinx URL

2013-09-22 Thread Django

#21141: Update Sphinx URL
--+---
 Reporter:  yokomizor |  Owner:  yokomizor
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  1 |  UI/UX:  0
--+---
 The official website changed from http://sphinx.pocoo.org/ to http
 ://sphinx-doc.org/.

 https://bitbucket.org/birkenfeld/sphinx

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

[django/django] 8e51be: [1.5.x] Fixed a couple of typos in GeoDjango docs.

2013-09-22 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 8e51bea4fb2302a636547ed3f938b16628621478
  
https://github.com/django/django/commit/8e51bea4fb2302a636547ed3f938b16628621478
  Author: Ramiro Morales 
  Date:   2013-09-22 (Sun, 22 Sep 2013)

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

  Log Message:
  ---
  [1.5.x] Fixed a couple of typos in GeoDjango docs.

8b366a50f4 from master.


  Commit: b5eddde09523bd55cde1cf8e22d46d3f594503d7
  
https://github.com/django/django/commit/b5eddde09523bd55cde1cf8e22d46d3f594503d7
  Author: Ramiro Morales 
  Date:   2013-09-22 (Sun, 22 Sep 2013)

  Changed paths:
M docs/topics/db/optimization.txt

  Log Message:
  ---
  [1.5.x] Reference Meta.index_together in DB performance guide.

9dc45efeba from master.


Compare: https://github.com/django/django/compare/177270ea73bd...b5eddde09523

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

[django/django] aef809: [1.6.x] Reference Meta.index_together in DB perfor...

2013-09-22 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: aef809f90cf9fda0bc2d7337a2e1c61d69b8e621
  
https://github.com/django/django/commit/aef809f90cf9fda0bc2d7337a2e1c61d69b8e621
  Author: Ramiro Morales 
  Date:   2013-09-22 (Sun, 22 Sep 2013)

  Changed paths:
M docs/topics/db/optimization.txt

  Log Message:
  ---
  [1.6.x] Reference Meta.index_together in DB performance guide.

9dc45efeba from master.


  Commit: b2876c0c914be0f12b57c7e6e4f6fae671108096
  
https://github.com/django/django/commit/b2876c0c914be0f12b57c7e6e4f6fae671108096
  Author: Ramiro Morales 
  Date:   2013-09-22 (Sun, 22 Sep 2013)

  Changed paths:
M docs/ref/urls.txt
M docs/topics/http/urls.txt
M docs/topics/http/views.txt

  Log Message:
  ---
  [1.6.x] A few doc additions for changes from d228c1192e.

ce0c5c38ea from master.


Compare: https://github.com/django/django/compare/14f76b15c4b2...b2876c0c914b

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

[django/django] 9dc45e: Reference Meta.index_together in DB performance gu...

2013-09-22 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 9dc45efebae4ad46151a9d059d62e7713ccf469b
  
https://github.com/django/django/commit/9dc45efebae4ad46151a9d059d62e7713ccf469b
  Author: Ramiro Morales 
  Date:   2013-09-22 (Sun, 22 Sep 2013)

  Changed paths:
M docs/topics/db/optimization.txt

  Log Message:
  ---
  Reference Meta.index_together in DB performance guide.


  Commit: ce0c5c38ea77a32e5d6d24082d3a8119ad8714cd
  
https://github.com/django/django/commit/ce0c5c38ea77a32e5d6d24082d3a8119ad8714cd
  Author: Ramiro Morales 
  Date:   2013-09-22 (Sun, 22 Sep 2013)

  Changed paths:
M docs/ref/urls.txt
M docs/topics/http/urls.txt
M docs/topics/http/views.txt

  Log Message:
  ---
  A few doc additions for changes from d228c1192e.


Compare: https://github.com/django/django/compare/51ed1ef1d56b...ce0c5c38ea77

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

Re: [Django] #21127: on_delete=models.SET_NULL should be the default for nullable FKs

2013-09-22 Thread Django

Comment (by loic84):

@russellm, I don't recommend a static check for this, but rather a dynamic
one which requires an explicit `on_delete` to silence (when `null=True`).

That way, if you intend to keep the old behavior, silencing the warning
actually solves the long-term issue. If you intend to switch to the new
behavior, you get to use it right away and save another auditing when the
switch of default behavior is about to happen.

Also, by silencing the "check" by code like the GSoC project offers, you
put yourself at risk if new FKs are introduced in a project after the
initial auditing + silencing took place.

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

[django/django] 51ed1e: Fixed a mistake in my previous commit.

2013-09-22 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 51ed1ef1d56b383210830f69594b789ab3457b95
  
https://github.com/django/django/commit/51ed1ef1d56b383210830f69594b789ab3457b95
  Author: Aymeric Augustin 
  Date:   2013-09-22 (Sun, 22 Sep 2013)

  Changed paths:
M django/shortcuts/__init__.py

  Log Message:
  ---
  Fixed a mistake in my previous commit.



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

[django/django] ee0ef1: Partial revert of 165f44aa.

2013-09-22 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ee0ef1b0948c19bc5fee06a6b9b4286b879f81c1
  
https://github.com/django/django/commit/ee0ef1b0948c19bc5fee06a6b9b4286b879f81c1
  Author: Aymeric Augustin 
  Date:   2013-09-22 (Sun, 22 Sep 2013)

  Changed paths:
M django/contrib/humanize/tests.py
M tests/i18n/tests.py
M tests/one_to_one_regress/tests.py
M tests/test_utils/tests.py
M tests/transactions/tests.py
M tests/view_tests/tests/test_i18n.py

  Log Message:
  ---
  Partial revert of 165f44aa.

That commit didn't always improve readability.

See discussion on django-developers for details.


  Commit: a5b062576bda29abe93504dbcb126e644d07f9dd
  
https://github.com/django/django/commit/a5b062576bda29abe93504dbcb126e644d07f9dd
  Author: Aymeric Augustin 
  Date:   2013-09-22 (Sun, 22 Sep 2013)

  Changed paths:
M django/conf/__init__.py
M django/contrib/auth/management/__init__.py
M django/contrib/auth/tests/test_remote_user.py
M django/db/models/sql/expressions.py
M django/shortcuts/__init__.py
M django/template/response.py
M django/templatetags/i18n.py
M django/test/client.py
M django/test/testcases.py
M django/utils/encoding.py
M django/utils/feedgenerator.py
M django/utils/html_parser.py
M django/utils/http.py
M tests/urlpatterns_reverse/tests.py

  Log Message:
  ---
  Removed a few trailing backslashes.

We have always been at war with trailing backslashes.


Compare: https://github.com/django/django/compare/222460a99407...a5b062576bda

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

Re: [Django] #6544: Regression with new templates extends checks

2013-09-22 Thread Django

#6544: Regression with new templates extends checks
-+-
 Reporter:  Bastian Kleineidam   |Owner:
   |   Status:  closed
 Type:  Bug  |  Version:  master
Component:  Template system  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by FunkyBob):

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


Comment:

 Clearly nobody has strong feelings about this any more.

 Also, there are two simple solutions:
 - move your comment below the extends tag
 - don't wrap your comment in a tag.

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

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

Re: [Django] #21120: documentation talks about validators but separates definition and usage

2013-09-22 Thread Django

#21120: documentation talks about validators but separates definition and usage
-+-
 Reporter:  nicolas@…|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.6-beta-1
 Severity:  Normal   |   Resolution:
 Keywords:  afraid-to-commit | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by EvilDMP):

 * cc: EvilDMP (added)
 * keywords:   => afraid-to-commit


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

Re: [Django] #20287: BaseContext (and it's subclasses) lack emulation of dictionary items()

2013-09-22 Thread Django

#20287: BaseContext (and it's subclasses) lack emulation of dictionary items()
-+-
 Reporter:  Keryn Knight |Owner:  cannona
   |   Status:  assigned
 Type:  New feature  |  Version:  master
Component:  Template system  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by FunkyBob):

 Just noting that currently ChainMap is implemented in python in py3, so it
 is back-portable to py2 almost verbatim.

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

Re: [Django] #6544: Regression with new templates extends checks

2013-09-22 Thread Django

#6544: Regression with new templates extends checks
-+-
 Reporter:  Bastian Kleineidam   |Owner:
   |   Status:  new
 Type:  Bug  |  Version:  master
Component:  Template system  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by FunkyBob):

 Given that nothing outside of a {% block %} is rendered in a template that
 {% extends %} ... why even wrap your comments in a comment tag?

 The template engine allows text nodes to precede the {% extends %} node,
 so why not just write your comments there, unadorned?

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

Re: [Django] #6544: Regression with new templates extends checks

2013-09-22 Thread Django

#6544: Regression with new templates extends checks
-+-
 Reporter:  Bastian Kleineidam   |Owner:
   |   Status:  new
 Type:  Bug  |  Version:  master
Component:  Template system  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by FunkyBob):

 * cc: FunkyBob (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/096.893882ee84a30f88e9156f198aadb0cc%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21140: Perfomance documentation should mention cached sessions

2013-09-22 Thread Django

#21140: Perfomance documentation should mention cached sessions
-+-
   Reporter:  EvilDMP|  Owner:  nobody
   Type: | Status:  new
  Uncategorized  |Version:  master
  Component: |   Keywords:  afraid-to-commit
  Documentation  |  Has patch:  0
   Severity:  Normal |Needs tests:  0
   Triage Stage: |  Easy pickings:  1
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 The HTTP section of /topics/performance should:

 * link to /topics/http/sessions/#using-cached-sessions
 * briefly summarise performance advantages

 https://twitter.com/brutasse/status/381309117635522560

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

Re: [Django] #21126: Potential data corruption issue with Oracle and Mysql due to SQLCompiler.resolve_columns row, fields misalignment

2013-09-22 Thread Django

#21126: Potential data corruption issue with Oracle and Mysql due to
SQLCompiler.resolve_columns row, fields misalignment
-+-
 Reporter:  manfre   |Owner:  manfre
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * severity:  Release blocker => Normal


Comment:

 Thanks for the clarification. I was asking because this is the only issue
 that prevents the release of 1.6 RC 1.

 Since it isn't a regression, I'm going to downgrade the severity. If a
 patch with tests is finished quickly enough -- we haven't set a date for
 RC 1 yet -- it can go in.

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

52 matches

Mail list logo