Re: [Django] #19702: mysql backend: 'SHOW TABLE STATUS WHERE name=...' not compatible with MySQL 4

[Django]

#19702: mysql backend: 'SHOW TABLE STATUS WHERE name=...' not compatible with 
MySQL
4
-+-
 Reporter:  matf@…   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:  mysql|  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by claudep):

 I did get some other core developers opinion on IRC before setting this to
 `won't fix`. You can always try to get some support by writing the the
 django-developers mailing list. But generally, we are very conservative
 with the type of bugs we backport to stable releases. The fact that we
 didn't get any report while this issue was already in Django 1.3 doesn't
 plead for 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19668: Form enhancement: `Form.set_data` to set data and files

[Django]

#19668: Form enhancement: `Form.set_data` to set data and files
-+-
 Reporter:  bruth|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  1|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  1
 |UI/UX:  0
-+-

Comment (by anonymous coward):

 -1


 You don't save a single line of code (unless you copy the provided
 example, which doesn't complete the antithesis version), are adding
 another method to maintain, and are creating the potential for internal
 problems (as mentioned above), not to mention making {{{Form}}} less
 extensible.

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

Re: [Django] #13182: Remove useless whitespaces in JSON dump with indent option

[Django]

#13182: Remove useless whitespaces in JSON dump with indent option
-+-
 Reporter:  stephaner|Owner:  gptvnt
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Core |   Resolution:
  (Serialization)| Triage Stage:  Ready for
 Severity:  Normal   |  checkin
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by hekevintran@…):

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


Comment:

 This ticket should be reconsidered because Django 1.5 has removed its copy
 of simplejson in favour of json from Python's standard library (which is
 based on version 2.0.9 of simplejson). As a result there is no way to
 prevent having trailing whitespace in when using the JSON serializer.

 See https://docs.djangoproject.com/en/dev/releases/1.5/#system-version-of-
 simplejson-no-longer-used

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

[Django] #19706: Tutorial amendments

[Django]

#19706: Tutorial amendments
---+
 Reporter:  EvilDMP|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.5-beta-1
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I've worked through the first four tutorials again, and made some
 suggestions.

 https://github.com/django/django/pull/688/files

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

Re: [Django] #19642: django.utils.functional.lazy issues

[Django]

#19642: django.utils.functional.lazy issues
--+--
 Reporter:  void  |Owner:  aaugustin
 Type:  Bug   |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  wontfix
 Keywords:  lazy, functional  | Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by aaugustin):

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


Comment:

 The second item was fixed in the patch for #19160. The three others are
 fairly minor and don't have actual consequences in the current code base.

 The patch fixes a few things but it isn't quite production-ready
 (`builtin_method_names = ['__hash__', '__str__']` - ouch)

 For these reasons I don't think it's useful to keep this ticket open.

 

 However, as discussed on IRC, it could be a good idea to re-implement
 `lazy()` by overriding `__getattribute__` rather than by copying methods
 around, both design-wise and performance-wise (to be benchmarked). Feel
 free to write a patch for this and open a new ticket!

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

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

[Django] #19705: CommonMiddleware handles If-Modified-Since incorrectly

[Django]

#19705: CommonMiddleware handles If-Modified-Since incorrectly
-+
   Reporter:  aaugustin  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  HTTP handling  |Version:  master
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 Two middleware check ETags for unmodified responses: `CommonMiddleware`
 and `ConditionalGetMiddleware` and they do it inconsistently.

 If the response's ETag matches the request's If-Modified-Since:
 - `ConditionalGetMiddleware` changes the response code to 304, preserving
 all headers; the content gets removed later on
 - `CommonMiddleware` creates a new `HttpResponseNotModified` without
 content and simply restores the cookies.

 As a consequence, `CommonMiddleware` returns a response without ETag,
 which is wrong. I detected this with RedBot on a Django site I run. Any
 site with `USE_ETAGS = True` has this problem.

 In general, wiping headers sounds like a bad idea. A 304 is supposed to
 have the same headers as the 200. (Well, the RFC is more complicated, but
 I think it's the general idea. [http://tools.ietf.org/html/draft-ietf-
 httpbis-p1-messaging-21#section-3.3.2 Future versions of HTTP] will likely
 require the Content-Length not to be 0.)

 

 I believe that `CommonMiddleware` should simply generate the ETag and not
 handle conditional content removal; that's the job of
 `ConditionalGetMiddleware`.

 For example, if one is using GzipMiddleware, the correct response chain
 is:
 - `CommonMiddleware` computes the ETag,
 - `GzipMiddleware` compresses the content and modifies the ETag,
 - `ConditionalGetMiddleware` uses the modified ETag to decide if the
 response was modified or not.
 This is a good reason to keep "ETag generation" and "Etag checking"
 concerns separate. The same argument applies to any middleware that sets
 or modifies ETags.

 Unfortunately, `CommonMiddleware` is documented to "take care of sending
 Not Modified responses, if appropriate", so this would be a backwards
 incompatible change.

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

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

Re: [Django] #19702: mysql backend: 'SHOW TABLE STATUS WHERE name=...' not compatible with MySQL 4

[Django]

#19702: mysql backend: 'SHOW TABLE STATUS WHERE name=...' not compatible with 
MySQL
4
-+-
 Reporter:  matf@…   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:  mysql|  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by anonymous):

 I don't see what's the problem, it's just 1 line of code that needs to be
 changed and Your documentation states that Django <= 1.4 is compatible
 with MySQL 4 which is right now simply not true...

 PS. Not every application is installed in one central server, where 1
 manager can decide to upgrade to MySQL 5. Some types of application are
 distributed to clients where older installations with MySQL4 exists (e.g.
 running another service). And frankly having them install another MySQL
 service because of that silly bug is just a bit too much. We have to
 patch, distribute patched version and re-patch in every next version.

 Again, it's just 1 line of code to be in a point when You can do what Your
 documentation states.

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

Re: [Django] #19704: Make use of new ungettext_lazy function at appropriate places

[Django]

#19704: Make use of new ungettext_lazy function at appropriate places
--+
 Reporter:  void  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Internationalization  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

 * component:  Core (Other) => Internationalization


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

Re: [Django] #19704: Make use of new ungettext_lazy function at appropriate places

[Django]

#19704: Make use of new ungettext_lazy function at appropriate places
--+
 Reporter:  void  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

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


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

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

[Django] #19704: Make use of new ungettext_lazy function at appropriate places

[Django]

#19704: Make use of new ungettext_lazy function at appropriate places
--+
 Reporter:  void  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Core (Other)  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 There are two places at the codebase, where new possibilities of
 ungettext_lazy may make code prettier:
 1. django.contrib.comments.admin
 2. django.utils.timesince

 There are hacks with lambdas at both places.

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

[django/django] 52533a: fixed minor typo #19703

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 52533a64d5866a3586dbfba69c6cb9e39bff7466
  
https://github.com/django/django/commit/52533a64d5866a3586dbfba69c6cb9e39bff7466
  Author: Simon Kerr 
  Date:   2013-01-30 (Wed, 30 Jan 2013)

  Changed paths:
M django/forms/forms.py

  Log Message:
  ---
  fixed minor typo #19703


  Commit: 5b4805ae2bbc14b159e3bfd84e78eb9189ffa6eb
  
https://github.com/django/django/commit/5b4805ae2bbc14b159e3bfd84e78eb9189ffa6eb
  Author: Claude Paroz 
  Date:   2013-01-30 (Wed, 30 Jan 2013)

  Changed paths:
M django/forms/forms.py

  Log Message:
  ---
  Merge pull request #686 from skrr/ticket_19703

Fixed #19703 -- Typo in get_declared_fields docstring


Compare: https://github.com/django/django/compare/3895ebc734c2...5b4805ae2bbc

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

Re: [Django] #19703: Minor typo in docstring (forms/forms.py)

[Django]

#19703: Minor typo in docstring (forms/forms.py)
-+-
 Reporter:  SimonKerr|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"5b4805ae2bbc14b159e3bfd84e78eb9189ffa6eb"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5b4805ae2bbc14b159e3bfd84e78eb9189ffa6eb"
 Merge pull request #686 from skrr/ticket_19703

 Fixed #19703 -- Typo in get_declared_fields docstring
 }}}

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

Re: [Django] #19702: mysql backend: 'SHOW TABLE STATUS WHERE name=...' not compatible with MySQL 4

[Django]

#19702: mysql backend: 'SHOW TABLE STATUS WHERE name=...' not compatible with 
MySQL
4
-+-
 Reporter:  matf@…   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:  mysql|  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by claudep):

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


Comment:

 This was already in 1.3 (introduced in [74d485c4ec2b]). Considering the
 probably low number of Django sites running on MySQL 4, this is probably
 not a serious enough issue to be worth fixing in a stable release. Thanks
 for the report anyway.

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

[django/django] 256352: Added file forgotten in d5ad9d3d.

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 256352a790baf8f71e114f0940cf230a273a16da
  
https://github.com/django/django/commit/256352a790baf8f71e114f0940cf230a273a16da
  Author: Aymeric Augustin 
  Date:   2013-01-30 (Wed, 30 Jan 2013)

  Changed paths:
A tests/regressiontests/generic_views/templates/generic_views/robots.txt

  Log Message:
  ---
  Added file forgotten in d5ad9d3d.



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

[django/django] 3895eb: Added file forgotten in 23e319d7.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3895ebc734c2b3be13d77cdd080b4a76bd4c36e9
  
https://github.com/django/django/commit/3895ebc734c2b3be13d77cdd080b4a76bd4c36e9
  Author: Aymeric Augustin 
  Date:   2013-01-30 (Wed, 30 Jan 2013)

  Changed paths:
A tests/regressiontests/generic_views/templates/generic_views/robots.txt

  Log Message:
  ---
  Added file forgotten in 23e319d7.



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

Re: [Django] #19034: Plural to MinLength, MaxLengt validation messages

[Django]

#19034: Plural to MinLength, MaxLengt validation messages
--+
 Reporter:  clay.evil@…   |Owner:  claudep
 Type:  Bug   |   Status:  closed
Component:  Internationalization  |  Version:  1.4
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by anonymous):

 Good Job, thank you 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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] fc8efc: Fixed #19034 -- Added proper i18n pluralization fo...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: fc8efc2d9e693923d3da272e0978e5b0631006f9
  
https://github.com/django/django/commit/fc8efc2d9e693923d3da272e0978e5b0631006f9
  Author: Claude Paroz 
  Date:   2013-01-30 (Wed, 30 Jan 2013)

  Changed paths:
M django/core/validators.py
M django/forms/fields.py

  Log Message:
  ---
  Fixed #19034 -- Added proper i18n pluralization for max/min length validation 
messages

This was made possible by commit 3f1a0c0040b9. Thanks Evil Clay
for the report and Alexey Boriskin his work on the ticket.



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

Re: [Django] #19034: Plural to MinLength, MaxLengt validation messages

[Django]

#19034: Plural to MinLength, MaxLengt validation messages
--+
 Reporter:  clay.evil@…   |Owner:  claudep
 Type:  Bug   |   Status:  closed
Component:  Internationalization  |  Version:  1.4
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"fc8efc2d9e693923d3da272e0978e5b0631006f9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="fc8efc2d9e693923d3da272e0978e5b0631006f9"
 Fixed #19034 -- Added proper i18n pluralization for max/min length
 validation messages

 This was made possible by commit 3f1a0c0040b9. Thanks Evil Clay
 for the report and Alexey Boriskin his work on the ticket.
 }}}

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

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

Re: [Django] #18000: Add Save and Goto Step to Form Wizard

[Django]

#18000: Add Save and Goto Step to Form Wizard
-+-
 Reporter:  creecode |Owner:  steph
 Type:  New feature  |   Status:  assigned
Component:  contrib.formtools|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  form wizard save | Triage Stage:  Ready for
  goto step  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by jezdez):

 * stage:  Design decision needed => Ready for checkin


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

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

[django/django] c8c7cd: Changed "versionadded" after the decision to backp...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c8c7cdc8f8f81b2f162db7acc8faaef0ece3b6ae
  
https://github.com/django/django/commit/c8c7cdc8f8f81b2f162db7acc8faaef0ece3b6ae
  Author: Aymeric Augustin 
  Date:   2013-01-30 (Wed, 30 Jan 2013)

  Changed paths:
M docs/ref/class-based-views/mixins-simple.txt

  Log Message:
  ---
  Changed "versionadded" after the decision to backport.

Refs #19076.



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

[django/django] d5ad9d: [1.5.x] Fixed #19076 -- Added content_type attribu...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: d5ad9d3dfe729f8b605965e131c787fae9f84377
  
https://github.com/django/django/commit/d5ad9d3dfe729f8b605965e131c787fae9f84377
  Author: Aymeric Augustin 
  Date:   2013-01-30 (Wed, 30 Jan 2013)

  Changed paths:
M django/views/generic/base.py
M docs/ref/class-based-views/flattened-index.txt
M docs/ref/class-based-views/mixins-simple.txt
M tests/regressiontests/generic_views/base.py
M tests/regressiontests/generic_views/urls.py

  Log Message:
  ---
  [1.5.x] Fixed #19076 -- Added content_type attribute to TemplateView.

Thanks Gavin Wahl.

Backport of 23e319d.



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

Re: [Django] #19076: TemplateView does not support setting mime type, like views.generic.simple.direct_to_template did

[Django]

#19076: TemplateView does not support setting mime type, like
views.generic.simple.direct_to_template did
---+
 Reporter:  gwahl@…|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Generic views  |  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 Aymeric Augustin ):

 In [changeset:"c8c7cdc8f8f81b2f162db7acc8faaef0ece3b6ae"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c8c7cdc8f8f81b2f162db7acc8faaef0ece3b6ae"
 Changed "versionadded" after the decision to backport.

 Refs #19076.
 }}}

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

Re: [Django] #19076: TemplateView does not support setting mime type, like views.generic.simple.direct_to_template did

[Django]

#19076: TemplateView does not support setting mime type, like
views.generic.simple.direct_to_template did
---+
 Reporter:  gwahl@…|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Generic views  |  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 Aymeric Augustin ):

 In [changeset:"d5ad9d3dfe729f8b605965e131c787fae9f84377"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d5ad9d3dfe729f8b605965e131c787fae9f84377"
 [1.5.x] Fixed #19076 -- Added content_type attribute to TemplateView.

 Thanks Gavin Wahl.

 Backport of 23e319d.
 }}}

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

Re: [Django] #19076: TemplateView does not support setting mime type, like views.generic.simple.direct_to_template did

[Django]

#19076: TemplateView does not support setting mime type, like
views.generic.simple.direct_to_template did
---+
 Reporter:  gwahl@…|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Generic views  |  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 aaugustin):

 This is a "new feature" for the class-based generic views, but it's also a
 "fix for a regression" as 1.5 removes the function-based generic views,
 and the class-based generic views don't provide this feature (yet).

 For this reason, I'm going to backport to 1.5, even though we've already
 released a RC1. A RC2 is planned. Jacob and Florian agreed on IRC.

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

Re: [Django] #19433: Allow declaration form_list and condition_dict in WizzardView subclass, not as params to as_view

[Django]

#19433: Allow declaration form_list and condition_dict in WizzardView subclass, 
not
as params to as_view
-+-
 Reporter:  migajek  |Owner:  steph
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.4
Component:  contrib.formtools|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  cbv wizzard  |  checkin
  wizzardview|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by jezdez):

 * stage:  Accepted => Ready for checkin


Comment:

 Other than `versionchanged` additions in the docs this looks good to me..

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

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

Re: [Django] #19076: TemplateView does not support setting mime type, like views.generic.simple.direct_to_template did

[Django]

#19076: TemplateView does not support setting mime type, like
views.generic.simple.direct_to_template did
---+
 Reporter:  gwahl@…|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Generic views  |  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 Aymeric Augustin ):

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


Comment:

 In [changeset:"23e319d7298c8b778181e85dd9b6cbed095f8147"]:
 {{{
 #!CommitTicketReference repository=""
 revision="23e319d7298c8b778181e85dd9b6cbed095f8147"
 Fixed #19076 -- Added content_type attribute to TemplateView.

 Thanks Gavin Wahl.
 }}}

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

[django/django] 23e319: Fixed #19076 -- Added content_type attribute to Te...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 23e319d7298c8b778181e85dd9b6cbed095f8147
  
https://github.com/django/django/commit/23e319d7298c8b778181e85dd9b6cbed095f8147
  Author: Aymeric Augustin 
  Date:   2013-01-30 (Wed, 30 Jan 2013)

  Changed paths:
M django/views/generic/base.py
M docs/ref/class-based-views/flattened-index.txt
M docs/ref/class-based-views/mixins-simple.txt
M tests/regressiontests/generic_views/base.py
M tests/regressiontests/generic_views/urls.py

  Log Message:
  ---
  Fixed #19076 -- Added content_type attribute to TemplateView.

Thanks Gavin Wahl.



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

Re: [Django] #19076: TemplateView does not support setting mime type, like views.generic.simple.direct_to_template did

[Django]

#19076: TemplateView does not support setting mime type, like
views.generic.simple.direct_to_template did
---+
 Reporter:  gwahl@…|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Generic views  |  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):

 Replying to [comment:6 bmispelon]:
 > Would it make sense to also add a `get_content_type` method (that would
 default to just returning `self.content_type`)?
 > A lot of the other generic views implement this pattern and it's useful
 in some cases.

 The accessor pattern is useful when views may have a good reason to
 incrementally modify the return value -- eg. the template context.

 I don't see an use case for `get_content_type`, and it can be added later
 on in a backwards-compatible way in the need arises.

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

Re: [Django] #19034: Plural to MinLength, MaxLengt validation messages

[Django]

#19034: Plural to MinLength, MaxLengt validation messages
--+
 Reporter:  clay.evil@…   |Owner:  claudep
 Type:  Bug   |   Status:  assigned
Component:  Internationalization  |  Version:  1.4
 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):

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


Comment:

 Now that #19160 is fixed, the resolution will be trivial.

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

Re: [Django] #19160: Make ungettext_lazy really usable

[Django]

#19160: Make ungettext_lazy really usable
-+-
 Reporter:  claudep  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:   |  Version:  master
  Internationalization   |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"3f1a0c0040b9a950584f4b309a1b670b0e709de5"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3f1a0c0040b9a950584f4b309a1b670b0e709de5"
 Fixed #19160 -- Made lazy plural translations usable.

 Many thanks to Alexey Boriskin, Claude Paroz and Julien Phalip.
 }}}

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

[django/django] 3f1a0c: Fixed #19160 -- Made lazy plural translations usab...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3f1a0c0040b9a950584f4b309a1b670b0e709de5
  
https://github.com/django/django/commit/3f1a0c0040b9a950584f4b309a1b670b0e709de5
  Author: Aymeric Augustin 
  Date:   2013-01-30 (Wed, 30 Jan 2013)

  Changed paths:
M django/utils/functional.py
M django/utils/translation/__init__.py
M docs/releases/1.6.txt
M docs/topics/i18n/translation.txt
M tests/regressiontests/i18n/other/locale/de/LC_MESSAGES/django.mo
M tests/regressiontests/i18n/other/locale/de/LC_MESSAGES/django.po
M tests/regressiontests/i18n/tests.py

  Log Message:
  ---
  Fixed #19160 -- Made lazy plural translations usable.

Many thanks to Alexey Boriskin, Claude Paroz and Julien Phalip.



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

Re: [Django] #11679: FormWizard: security_hash() has issues with Safari leaving in \r\n

[Django]

#11679: FormWizard: security_hash() has issues with Safari leaving in \r\n
---+
 Reporter:  al@…   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.formtools  |  Version:  1.0
 Severity:  Normal |   Resolution:  invalid
 Keywords:  FormWizard | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by steph):

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


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

Re: [Django] #19703: Minor typo in docstring (forms/forms.py)

[Django]

#19703: Minor typo in docstring (forms/forms.py)
-+-
 Reporter:  SimonKerr|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by SimonKerr):

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


Comment:

 pull request at
 https://github.com/django/django/pull/686

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

Re: [Django] #18000: Add Save and Goto Step to Form Wizard

[Django]

#18000: Add Save and Goto Step to Form Wizard
-+-
 Reporter:  creecode |Owner:  steph
 Type:  New feature  |   Status:  assigned
Component:  contrib.formtools|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  form wizard save | Triage Stage:  Design
  goto step  |  decision needed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by steph):

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


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

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

Re: [Django] #18000: Add Save and Goto Step to Form Wizard

[Django]

#18000: Add Save and Goto Step to Form Wizard
-+-
 Reporter:  creecode |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.formtools|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  form wizard save | Triage Stage:  Design
  goto step  |  decision needed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by steph):

 I just wrote a bunch of code to make it possible to store the form data
 before changing the step. I don't think we should change the default
 behaviour because users except that the data is not saved. With this
 change any developer can overwrite the render_goto_step method to change
 the default behaviour. Please see this commit:
 
https://github.com/stephrdev/django/commit/1b7e25e0427888af7958f3960c31f42ff1ce3ef2

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

[Django] #19703: Minor typo in docstring (forms/forms.py)

[Django]

#19703: Minor typo in docstring (forms/forms.py)
--+
 Reporter:  SimonKerr |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 in forms/forms.py
 The docstring for get_declared_fields() has two minor typos:
 l.35 'metclasses' should read metaclasses,
 l.40 no final point.

 This is my first contribution, to get my feet wet with the whole
 trac/github workflow.

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

Re: [Django] #19698: Deleting Sites through a manager does not clear cache

[Django]

#19698: Deleting Sites through a manager does not clear cache
---+
 Reporter:  ddavies@…  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.sites  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by claudep):

 * easy:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 The `delete()` method of the `Site` class should probably be replaced by a
 `pre_delete` signal.

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

Re: [Django] #19698: Deleting Sites through a manager does not clear cache

[Django]

#19698: Deleting Sites through a manager does not clear cache
---+--
 Reporter:  ddavies@…  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.sites  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by claudep):

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


Old description:

> When you delete a Site instance, i.e.
> Site.objects.get_current().delete(), the cache is cleared. However, if
> you delete all sites, Site.objects.all().delete(), the cache is not
> cleared.
>
> def test_delete_all_sites_clears_cache(self):
> """
> When all site objects are deleted the cache should  also
> be cleared and get_current should raise a DoesNotExist
> """
> from django.contrib.sites.models import Site
> site = Site.objects.create(domain='example.com', name='test')
> self.assertIsInstance(Site.objects.get_current(), Site)
> Site.objects.all().delete()
> self.assertRaises(Site.DoesNotExist, Site.objects.get_current)

New description:

 When you delete a Site instance, i.e.
 `Site.objects.get_current().delete()`, the cache is cleared. However, if
 you delete all sites, `Site.objects.all().delete()`, the cache is not
 cleared.

 {{{
 def test_delete_all_sites_clears_cache(self):
 """
 When all site objects are deleted the cache should  also
 be cleared and get_current should raise a DoesNotExist
 """
 from django.contrib.sites.models import Site
 site = Site.objects.create(domain='example.com', name='test')
 self.assertIsInstance(Site.objects.get_current(), Site)
 Site.objects.all().delete()
 self.assertRaises(Site.DoesNotExist, Site.objects.get_current)
 }}}

--

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

[Django] #19702: mysql backend: 'SHOW TABLE STATUS WHERE name=...' not compatible with MySQL 4

[Django]

#19702: mysql backend: 'SHOW TABLE STATUS WHERE name=...' not compatible with 
MySQL
4
--+
 Reporter:  matf@…|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.4
 Severity:  Normal|   Keywords:  mysql
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  1 |  UI/UX:  0
--+
 django/db/backends/mysql/base.py executes "SHOW TABLE STATUS WHERE
 Name='INTROSPECT_TEST'" query.

 "SHOW TABLE STATUS WHERE name='table_name'" syntax was introduced in mysql
 5.
 See link: http://dev.mysql.com/doc/refman/5.0/en/show-table-status.html

 Correct syntax that works with both MySQL 4 and MySQL 5 is "SHOW TABLE
 STATUS LIKE 'table_name'"
 See link: http://dev.mysql.com/doc/refman/4.1/en/show-table-status.html

 Since django <= 1.4 is compatible with MySQL 4 this is a bug. This
 functionality is used in e.g. South database migration library.

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

Re: [Django] #19160: Make ungettext_lazy really usable

[Django]

#19160: Make ungettext_lazy really usable
-+-
 Reporter:  claudep  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:   |  Version:  master
  Internationalization   |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

 * stage:  Accepted => Ready for checkin


Comment:

 Thanks Alexey! Tests have been successfully run on Python 2.6/SQLite and
 Python 3.2/SQLite.

 To prevent deprecation warnings, `self.assertRaisesRegexp` should be
 changed to `six.assertRaisesRegex`. Apart from that, it looks very nice.

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

Re: [Django] #19701: error500 default view don't include STATIC_URL

[Django]

#19701: error500 default view don't include STATIC_URL
+--
 Reporter:  hugo.arregui@…  |Owner:  nobody
 Type:  Uncategorized   |   Status:  closed
Component:  Generic views   |  Version:  1.4
 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 mlavin):

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


Comment:

 The reason why it does not use a {{{RequestContext}}} is already
 documented
 https://docs.djangoproject.com/en/1.4/topics/http/views/#the-500-server-
 error-view

 > The default 500 view passes no variables to this template and is
 rendered with an empty Context to lessen the chance of additional errors.

 You can still use the {{{get_static_prefix}}}
 https://docs.djangoproject.com/en/1.4/ref/templates/builtins/#get-static-
 prefix or {{{static}}} https://docs.djangoproject.com/en/1.4/howto/static-
 files/#with-a-template-tag to reference static files without a
 {{{RequestContext}}}.

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

Re: [Django] #19701: error500 default view don't include STATIC_URL

[Django]

#19701: error500 default view don't include STATIC_URL
+--
 Reporter:  hugo.arregui@…  |Owner:  nobody
 Type:  Uncategorized   |   Status:  new
Component:  Generic views   |  Version:  1.4
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by anonymous):

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


Comment:

 A friend point me to: https://code.djangoproject.com/ticket/5617

 But this is a problem.. maybe the default view could insert STATIC_URL
 from settings without RequestContext?

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

[Django] #19701: error500 default view don't include STATIC_URL

[Django]

#19701: error500 default view don't include STATIC_URL
+
 Reporter:  hugo.arregui@…  |  Owner:  nobody
 Type:  Uncategorized   | Status:  new
Component:  Generic views   |Version:  1.4
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 Hi,

 i was playing with this behaviour when I found this:

 https://github.com/django/django/blob/master/django/views/defaults.py#L41

 error500 is the only default view which doesn't use RequestContext, then,
 STATIC_URL is not included.

 Is there a reason for that?

 Thanks.

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

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

Re: [Django] #17657: ModelForm does not respect ModelMultipleChoiceField's to_field_name attribute

[Django]

#17657: ModelForm does not respect ModelMultipleChoiceField's to_field_name
attribute
-+-
 Reporter:  andreyfedoseev   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by mjtamlyn):

 * cc: marc.tamlyn@… (added)


Comment:

 I came across this today - I would like the patch to be applied. I know
 I'm messing with an internal API but it'd be good if it 'just worked'.

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

Re: [Django] #19700: BoundField documentation: original field

[Django]

#19700: BoundField documentation: original field
---+--
 Reporter:  tga|Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by tga):

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


Comment:

 Created pull request: https://github.com/django/django/pull/685

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

[Django] #19700: BoundField documentation: original field

[Django]

#19700: BoundField documentation: original field
---+
 Reporter:  tga|  Owner:  nobody
 Type:  New feature| Status:  new
Component:  Documentation  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 Please add in the documentation a mention on how to get the original field
 of a BoundField.

 Locations:
 https://docs.djangoproject.com/en/dev/topics/forms/#looping-over-the-
 form-s-fields
 https://docs.djangoproject.com/en/dev/ref/forms/api/#django.forms.BoundField

 In these two locations it would be very useful to have a mention like:

 --

 '''{{ field.field }}'''
 The original field instance, as added to the form object, e.g. a
 forms.CharField instance.

 --


 Details:
 When adding field programatically to a form, it comes naturally to want to
 add extra fields to that object and then read them back in the template.
 However, as the docs clearly state, iterating over a (bound) form returns
 BoundFields instead of the original Field objects put into the form. There
 is no mention in the docs how to get to the original field instance in the
 template.

 Cheers!

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

[Django] #19699: Documentation for "index_together" is an infinite loop.

[Django]

#19699: Documentation for "index_together" is an infinite loop.
---+
 Reporter:  vernondcole|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.5-beta-1
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 The documintation in the 1.5 Release Notes reads:

 {{{
 Multi-column indexes can now be created on models. Read the index_together
 documentation for more information.

 }}}

 Following the link on "index_together" gets to this:


 {{{
 Options.index_together
 New in Django 1.5: Please see the release notes

 Sets of field names that, taken together, are indexed:

 index_together = [
 ["pub_date", "deadline"],
 ]

 This list of fields will be indexed together (i.e. the appropriate
 CREATE INDEX statement will be issued.)
 }}}

 where the "release notes" link takes you back to the first instance...

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

Re: [Django] #9025: Nested Inline Support in Admin

[Django]

#9025: Nested Inline Support in Admin
---+
 Reporter:  pixelcort  |Owner:
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  1
---+
Changes (by Stefan Klug ):

 * cc: klug.stefan@… (added)


Comment:

 Hi, could anyone with better knowledge summarize the status of this
 feature? I'd like to give it a try and potentially add some fixes. To my
 knowledge the status is as follows:
 * There is a patch (nested_inlines_finished.diff) by Gargamel which has
 docs and tests but still contains some bugs described in #comment:127,
 #comment:134 bjola did some work on this. @bjola: Is there any public
 version of this work available?
 * The bugs seemed so severe that Gargamel restarted from scratch, did some
 progress but hasn't got enough spare time to push it further. I'd love to
 see the status of this work as it seems a waste of time to debug the old
 patch when Gargamel decided to abandon it.
 @Gragamel: Could you post a patch or link a git repository where the
 status of your new work can be seen? - Or did you dump the whole thing
 (#comment:140 seems like that)

 It would be a lot easier to help, if there was a central place with the
 current state. Maybe one of the core devs could put up a git branch for
 this feature?

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

[Django] #19698: Deleting Sites through a manager does not clear cache

[Django]

#19698: Deleting Sites through a manager does not clear cache
---+
 Reporter:  ddavies@…  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.sites  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 When you delete a Site instance, i.e. Site.objects.get_current().delete(),
 the cache is cleared. However, if you delete all sites,
 Site.objects.all().delete(), the cache is not cleared.

 def test_delete_all_sites_clears_cache(self):
 """
 When all site objects are deleted the cache should  also
 be cleared and get_current should raise a DoesNotExist
 """
 from django.contrib.sites.models import Site
 site = Site.objects.create(domain='example.com', name='test')
 self.assertIsInstance(Site.objects.get_current(), Site)
 Site.objects.all().delete()
 self.assertRaises(Site.DoesNotExist, Site.objects.get_current)

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

Re: [Django] #18924: test.Client.logout doesn't send user_logged_out signal

[Django]

#18924: test.Client.logout doesn't send user_logged_out signal
---+
 Reporter:  awsum  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by mjtamlyn):

 * needs_better_patch:  0 => 1
 * stage:  Ready for checkin => Accepted


Comment:

 Patch has now gone stale - it will need updating for custom user models.

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

Re: [Django] #3544: Fix {% include %} to allow recursive includes

[Django]

#3544: Fix {% include %} to allow recursive includes
-+-
 Reporter:  David Danier |Owner:  nobody
  |   Status:  new
 Type:  New feature  |  Version:  master
Component:  Template system  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  tplrf-patched|  Needs documentation:  1
Has patch:  0|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by anonymous):

 Any progress?

 It seems quite demanded feature as soon as you deal with hierarchical
 trees rendering.

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

Re: [Django] #18924: test.Client.logout doesn't send user_logged_out signal

[Django]

#18924: test.Client.logout doesn't send user_logged_out signal
-+-
 Reporter:  awsum|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  1
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by anonymous):

 Can we have this anytime soon?

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

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

[Django] #19697: Add an overview of good practices for production settings

[Django]

#19697: Add an overview of good practices for production settings
-+
   Reporter:  aaugustin  |  Owner:  nobody
   Type:  New feature| Status:  new
  Component:  Documentation  |Version:  master
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 Quoting Claude:

 > add a section in the docs where we explain what settings should be
 typically added in deployed projects, but not suitable in public
 repositories (DEBUG=False, DATABASES, STATIC_ROOT, SECRET_KEY, ADMINS,
 SERVER_EMAIL, etc.) and link to this section in the template.

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

Re: [Django] #19598: Bug in inlines.js

[Django]

#19598: Bug in inlines.js
-+-
 Reporter:  rj@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
  javascript,inlines.js  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-

Comment (by bpeschier):

 The bundled jQuery handles the {{{attr}}}-call correctly, and though it is
 not the most up-to-date code there is, it should work (checked against a
 stock 1.4 admin).

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

Re: [Django] #19598: Bug in inlines.js

[Django]

#19598: Bug in inlines.js
-+-
 Reporter:  rj@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
  javascript,inlines.js  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-

Comment (by bpeschier):

 Closed #19623 as a duplicate.

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

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

Re: [Django] #19623: Update inlines.js to use jQuery 1.9

[Django]

#19623: Update inlines.js to use jQuery 1.9
-+-
 Reporter:  jordanorc|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  contrib.admin|  Version:  1.4
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  jquery admin | Triage Stage:
  inlines.js |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by bpeschier):

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


Comment:

 Closing as a duplicate of #19598

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

Re: [Django] #19696: Collectstatic management command: unicodeerror

[Django]

#19696: Collectstatic management command: unicodeerror
-+-
 Reporter:  arn.breton@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  unicodeerror,| Triage Stage:
  collectstatic, css, assets |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

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


Comment:

 This looks like #18430, which is fixed in Django 1.5. Could you try if it
 still crashes with 1.5?

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