Re: [Django] #21799: loaddata ignorenonexistent should ignore missing models too

2014-02-20 Thread Django 
#21799: loaddata ignorenonexistent should ignore missing models too
-+-
 Reporter:  michael.clagett@…|Owner:  esauro
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Core |   Resolution:
  (Serialization)| Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  loaddata |  Patch needs improvement:  0
  ignorenonexistent  |UI/UX:  0
Has patch:  0|
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by esauro):

 I created a pull request https://github.com/django/django/pull/2335

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

Re: [Django] #21799: loaddata ignorenonexistent should ignore missing models too

2014-02-20 Thread Django 
#21799: loaddata ignorenonexistent should ignore missing models too
-+-
 Reporter:  michael.clagett@…|Owner:  esauro
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Core |   Resolution:
  (Serialization)| Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  loaddata |  Patch needs improvement:  0
  ignorenonexistent  |UI/UX:  0
Has patch:  0|
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by esauro):

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


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

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

Re: [Django] #22107: Iterating over File broken in Python 3

2014-02-20 Thread Django 
#22107: Iterating over File broken in Python 3
--+
 Reporter:  pdewacht  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Core (Other)  |  Version:  1.6
 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 bmispelon):

 Replying to [comment:2 claudep]:
 > I think this would be a good candidate for backporting...

 The problem has probably been here since 1.5 but I only backported to 1.6
 because it's the first release that has full Python 3 support (1.5 had
 "experimental" support if I remember correctly).

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

Re: [Django] #22107: Iterating over File broken in Python 3

2014-02-20 Thread Django 
#22107: Iterating over File broken in Python 3
--+
 Reporter:  pdewacht  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Core (Other)  |  Version:  1.6
 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 Baptiste Mispelon ):

 In [changeset:"12da6902e9cd8de2bc9eeef08c850a6c79aaa7cc"]:
 {{{
 #!CommitTicketReference repository=""
 revision="12da6902e9cd8de2bc9eeef08c850a6c79aaa7cc"
 [1.6.x] Fixed #22107 -- Fixed django.core.files.File object iteration.

 Due to a mixup between text and bytes, iteration over
 a File instance was broken under Python 3.

 Thanks to trac user pdewacht for the report and patch.

 Backport of 3841feee86cae65165f120db7a5d80ffc76dd520 from master.
 }}}

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

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

[django/django] 12da69: [1.6.x] Fixed #22107 -- Fixed django.core.files.Fi...

2014-02-20 Thread GitHub 
  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 12da6902e9cd8de2bc9eeef08c850a6c79aaa7cc
  
https://github.com/django/django/commit/12da6902e9cd8de2bc9eeef08c850a6c79aaa7cc
  Author: Baptiste Mispelon 
  Date:   2014-02-20 (Thu, 20 Feb 2014)

  Changed paths:
M django/core/files/base.py
M tests/files/tests.py

  Log Message:
  ---
  [1.6.x] Fixed #22107 -- Fixed django.core.files.File object iteration.

Due to a mixup between text and bytes, iteration over
a File instance was broken under Python 3.

Thanks to trac user pdewacht for the report and patch.

Backport of 3841feee86cae65165f120db7a5d80ffc76dd520 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/5306890bd735b_1c19fefd444166%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22109: clarify difference between relative and absolute STATIC_URL

2014-02-20 Thread Django 
#22109: clarify difference between relative and absolute STATIC_URL
--+---
 Reporter:  cjerdonek |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.6
 Severity:  Normal|   Keywords:  static_url,static
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+---
 It seems like there is a qualitative difference in the behavior of
 `STATIC_URL` that is worth adding to
 [https://docs.djangoproject.com/en/dev/ref/settings/#static-url its
 documentation] -- depending on whether the URL is absolute vs relative.
 Specifically, the documentation currently only mentions how to //refer//
 to static assets (i.e. by prepending `STATIC_URL`).  But it doesn't
 mention that when `STATIC_URL` is relative, Django will use this setting
 to find and serve the file (using also the settings `STATICFILES_DIRS` and
 `STATIC_ROOT`, for example).

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

Re: [Django] #22109: clarify difference between relative and absolute STATIC_URL

2014-02-20 Thread Django 
#22109: clarify difference between relative and absolute STATIC_URL
-+-
 Reporter:  cjerdonek|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.6
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  static_url,static|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by cjerdonek):

 * cc: chris.jerdonek@… (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


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

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

Re: [Django] #22107: Iterating over File broken in Python 3

2014-02-20 Thread Django 
#22107: Iterating over File broken in Python 3
--+
 Reporter:  pdewacht  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Core (Other)  |  Version:  1.6
 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 claudep):

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


Comment:

 I think this would be a good candidate for backporting...

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

Re: [Django] #21942: document Form.clean() in "Forms API" docs

2014-02-20 Thread Django 
#21942: document Form.clean() in "Forms API" docs
-+-
 Reporter:  cjerdonek|Owner:  lkitchner
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.6
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
  forms,clean,validation |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-

Comment (by cjerdonek):

 I made a suggestion on the first pull request that doesn't seem to be
 reflected in the second one (nor was there a response):
 https://github.com/django/django/pull/2318#discussion_r9840517

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

Re: [Django] #21942: document Form.clean() in "Forms API" docs

2014-02-20 Thread Django 
#21942: document Form.clean() in "Forms API" docs
-+-
 Reporter:  cjerdonek|Owner:  lkitchner
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.6
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
  forms,clean,validation |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-

Comment (by lkitchner):

 I've made the discussed changes from pull 2318 and have made a new pull
 request.
 https://github.com/django/django/pull/2334

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

[django/django] adcedf: Capitalize SQL keywords

2014-02-20 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: adcedfe8ba2376ab5106f0d6704770be95db6f12
  
https://github.com/django/django/commit/adcedfe8ba2376ab5106f0d6704770be95db6f12
  Author: David Sanders 
  Date:   2014-02-20 (Thu, 20 Feb 2014)

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

  Log Message:
  ---
  Capitalize SQL keywords


  Commit: 476abc7ea72fc7cbfed8e5a7b50b5d82e5d32105
  
https://github.com/django/django/commit/476abc7ea72fc7cbfed8e5a7b50b5d82e5d32105
  Author: Alex Gaynor 
  Date:   2014-02-20 (Thu, 20 Feb 2014)

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

  Log Message:
  ---
  Merge pull request #2333 from davesque/sql-doc-fixes

Capitalize SQL keywords


Compare: https://github.com/django/django/compare/c03edb58f11c...476abc7ea72f

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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/53064b89a6fd4_530dc9fd38842cf%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 6dfd02: Capitalize SQL keywords

2014-02-20 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 6dfd02f88c49ce0d39191088863f6f45b0d7784e
  
https://github.com/django/django/commit/6dfd02f88c49ce0d39191088863f6f45b0d7784e
  Author: David Sanders 
  Date:   2014-02-20 (Thu, 20 Feb 2014)

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

  Log Message:
  ---
  Capitalize SQL keywords


  Commit: c03edb58f11c76ab8041a94fbb2ed51cff452e6f
  
https://github.com/django/django/commit/c03edb58f11c76ab8041a94fbb2ed51cff452e6f
  Author: Alex Gaynor 
  Date:   2014-02-20 (Thu, 20 Feb 2014)

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

  Log Message:
  ---
  Merge pull request #2332 from davesque/sql-doc-fixes

Capitalize SQL keywords


Compare: https://github.com/django/django/compare/3841feee86ca...c03edb58f11c

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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/530649488c984_544bfc7d444571e%40hookshot-fe7-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 3841fe: Fixed #22107 -- Fixed django.core.files.File objec...

2014-02-20 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3841feee86cae65165f120db7a5d80ffc76dd520
  
https://github.com/django/django/commit/3841feee86cae65165f120db7a5d80ffc76dd520
  Author: Baptiste Mispelon 
  Date:   2014-02-20 (Thu, 20 Feb 2014)

  Changed paths:
M django/core/files/base.py
M tests/files/tests.py

  Log Message:
  ---
  Fixed #22107 -- Fixed django.core.files.File object iteration.

Due to a mixup between text and bytes, iteration over
a File instance was broken under Python 3.

Thanks to trac user pdewacht for the report and patch.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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/530647cd8d9f1_5400c67d34845c1%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22107: Iterating over File broken in Python 3

2014-02-20 Thread Django 
#22107: Iterating over File broken in Python 3
--+
 Reporter:  pdewacht  |  Owner:  nobody
 Type:  Bug   | Status:  closed
Component:  Core (Other)  |Version:  1.6
 Severity:  Normal| Resolution:  fixed
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  1 |  Easy pickings:  0
UI/UX:  0 |
--+
Changes (by Baptiste Mispelon ):

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


Comment:

 In [changeset:"3841feee86cae65165f120db7a5d80ffc76dd520"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3841feee86cae65165f120db7a5d80ffc76dd520"
 Fixed #22107 -- Fixed django.core.files.File object iteration.

 Due to a mixup between text and bytes, iteration over
 a File instance was broken under Python 3.

 Thanks to trac user pdewacht for the report and patch.
 }}}

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

[Django] #22108: Release blockers graph doesn't display on dashboard

2014-02-20 Thread Django 
#22108: Release blockers graph doesn't display on dashboard
---+
   Reporter:  EvilDMP  |  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  *.djangoproject.com  |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|
---+
 https://dashboard.djangoproject.com/metric/blockers/

 All the other graphs seem OK.

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

[Django] #22107: Iterating over File broken in Python 3

2014-02-20 Thread Django 
#22107: Iterating over File broken in Python 3
--+
 Reporter:  pdewacht  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Core (Other)  |Version:  1.6
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+
 django.core.files.File has an iterator to allow line-by-line access to the
 file. This does not work in Python 3 due to string/bytestring confusion.
 Attached patch fixes this and adds a regression test.

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

Re: [Django] #19115: dumpdata should take option to output to named file

2014-02-20 Thread Django 
#19115: dumpdata should take option to output to named file
-+-
 Reporter:  murftone@…   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  dumpdata management  |  Needs documentation:  0
  command|  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by bmispelon):

 Replying to [comment:11 maa@…]:
 > how do we use this ?
 > ./manage dumpdata --stdout=file.json ?

 This ticket tracker is not the best place to ask questions like this. You
 should use our support channels instead [1].

 As for your question, since the command outputs its result, you can use
 your shell's output redirection feature:
 {{{
 ./manage dumpdata > the_name_of_the_file.json
 }}}

 [1]
 https://code.djangoproject.com/wiki/TicketClosingReasons/UseSupportChannels

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

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

[Django] #22106: Make django.views.i18n.javascript_catalog more flexible

2014-02-20 Thread Django 
#22106: Make django.views.i18n.javascript_catalog more flexible
-+-
 Reporter:  moritzs  |  Owner:  nobody
 Type:   | Status:  new
  Cleanup/optimization   |Version:  master
Component:   |   Keywords:  jsi18n javascript
  Internationalization   |  catalog
 Severity:  Normal   |  Has patch:  0
 Triage Stage:  Unreviewed   |  UI/UX:  0
Easy pickings:  0|
-+-
 Right now you can only use one instance of `javascript_catalog`, because
 they will override each other if you add more to one site.
 This problem can easily be solved by making `packages` in `kwargs` for
 `javascript_catalog` include all packages needed instead of having a
 multiple views for different packages. That however makes the
 internationalization of javascript code that does not directly lie in the
 main application somewhat inflexible.

 == Example ==

 `appA`: app that contains the widget `FunkyJSWidget` that relies on some
 javascript and needs jsi18n.
 `appMain`: your main app that contains all the views for your website.
 Your website also contains some javascript code that also uses jsi18n. It
 uses `appA.FunkyJSWidget` on some forms as well.

 `INSTALLED_APPS` now is `('appA', 'appMain')`.
 The problem now occurs on all your pages that use `appA.FunkyJSWidget`.
 Because the widget includes its javascript_catalog (per Media-class for
 example) as well as your `appMain`, one will override the other. You could
 obviously add `appA` to `appMain.views.jsi18n`'s `packages` argument but
 this shouldn't be necessary.

 == Possible Solution ==

 Modify `django.views.i18n.js_catalog_template` to detect if a catalog
 already exists. If it does, update it instead of overriding it. A minor
 issue is that the template omits some functions if they are not needed.
 That should be checked for all included javascript_catalogs, too.

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

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

Re: [Django] #19115: dumpdata should take option to output to named file

2014-02-20 Thread Django 
#19115: dumpdata should take option to output to named file
-+-
 Reporter:  murftone@…   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  dumpdata management  |  Needs documentation:  0
  command|  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by maa@…):

 how do we use this ?
 ./manage dumpdata --stdout=file.json ?

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

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

Re: [Django] #21202: Atomic masks fatal database errors and instead propagates "connection already closed"

2014-02-20 Thread Django 
#21202: Atomic masks fatal database errors and instead propagates "connection
already closed"
-+-
 Reporter:  intgr|Owner:  aaugustin
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:
Component:  Database layer   |  1.6-beta-1
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by dji):

 Whatever happened to this?  Seeing this happen a lot on production with
 1.6.  Even worse, the connection then doesn't get closed, and so all
 future requests error as well.  So should we also be closing the bad
 connection... somewhere?

 Longer explanation: As it is with this patch applied (to 1.6, I can't seem
 to get dev to run), `django.db.close_old_connections()` fails on
 `conn.rollback()` (which is called by `conn.abort()`) with the same
 `InterfaceError`.  This means that `conn.close_if_unusable_or_obsolete()`
 never gets called, and the broken connection is reused for later requests,
 causing all future requests on that connection to error.

 You can replicate this behavior pretty easily as described above, by
 enabling connection pooling and terminating your own connection in a
 request, and then trying to make a subsequent request.  I suspect this is
 still the behavior in dev as well, nothing appears to have changed.

 My "solution" is to squelch `InterfaceError` as well as `DatabaseError` in
 `close_old_connections`, but I'm new to the Django internals so I'm not
 sure if this is best, or if it would be better to just close the
 connection straight away here in `__exit__` before we return, or what.
 Happy to help sort this but I'm not sure of the correct approach.

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

[Django] #22105: Model error messages overwritten by modelform django defaults

2014-02-20 Thread Django 
#22105: Model error messages overwritten by modelform django defaults
-+-
 Reporter:   |  Owner:  Dr_White
  daniel@…   | Status:  new
 Type:  Bug  |Version:  master
Component:  Forms|   Keywords:  error_messages, model, error, form,
 Severity:  Normal   |  _update_errors
 Triage Stage:   |  Has patch:  0
  Unreviewed |  UI/UX:  0
Easy pickings:  0|
-+-
 Imagine a model with custom error messages added to some of it's fields.

 {{{
 from django.db import models


 class MyModel(models.Model):
 name = models.CharField(
 max_length=255,
 error_messages={
 'required': 'my required msg..',
 }
 )
 }}}

 When a modelform is created from this model

 {{{
 from django.forms import ModelForm
 from .models import MyModel


 class MyModelForm(ModelForm):

 class Meta:
 model = MyModel
 fields = ['name']
 }}}

 I would expect to see the custom error message.
 Instead the function _update_errors from BaseModelForm simply doesn't
 care, I quote:
 '''Override any validation error messages defined at the model level
 with those defined at the form level.'''

 I believe any custom error message defined in the model should take
 precedence over the default form messages.
 Whenever error messages also defined in the modelform meta like so:


 {{{
 class MyModelForm(ModelForm):

 class Meta:
 model = MyModel
 fields = ['name']
 error_messages = {
 'name': {
 'required': "This is a custom error message from modelform
 meta",
 },
 }
 }}}

 Then the error message from the modelform should be 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.139e49ac31962fbf7f6ed6df66748550%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22104: weight loss 53

2014-02-20 Thread Django 
#22104: weight loss 53
---+--
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:  strawberry garcinia cambogia
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+--
 just thirsty which thirst is very oftentimes mistaken for hunger and once
 you have some water and I want you to walk away from the fridge not be fit
 drink water take a walk K the next question to ask yourself if you say I'm
 not thirsty it how am I feeling this is the big one because nine times out
 have 10 we are feeling bored or lonely our staff had promotional in some
 way we[http://strawberrygarciniacambogiapro.com/ strawberry garcinia
 cambogia] are feeling upset where routine its American Idols on where the
 chipsspray ever reaching for the pantry but we're not hungry reaching for
 cookies or cake ice cream because it's that time of day or we just got an
 unexpected bill in the mail a how my ass orgasms hired and I justneed a
 little pick me up but tired a hungry see your challenge is to only eat
 when you're hungry stop when you're truly fall and let me know how it goes
 let me know how many times you're reaching for that pantry for that
 refrigerator and how many times the light ball when of like out it
 something else and let me know I was left now and share and chicken
 sharing is caring because so many people that I I coach every
  single one of them is every single one of them a ever reaching for
 something up and it’s not hunger every chain because their husbands
 doesn't love them the way they need them to you or because their doctor I
 or because their child has a disability saw think about why you're
 reaching think about what you're feeling ask yourself am I hungry and ask
 yourself what deeper issue okay and report back any help please let me
 http://strawberrygarciniacambogiapro.com/

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

[django/django] cb8444: Fixed #22097 -- Fixed change detection for TypedCh...

2014-02-20 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: cb844497d01ddb45603e47891cdf36ae0b006d03
  
https://github.com/django/django/commit/cb844497d01ddb45603e47891cdf36ae0b006d03
  Author: Claude Paroz 
  Date:   2014-02-20 (Thu, 20 Feb 2014)

  Changed paths:
M django/forms/fields.py
M tests/forms_tests/tests/test_fields.py

  Log Message:
  ---
  Fixed #22097 -- Fixed change detection for TypedChoiceField

Thanks Igor Mitrenko for the report.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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/5305f860cfe1f_52b4bd1d3411972%40hookshot-fe7-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22097: IntegerField with given choices leads to wrong has_changed() work

2014-02-20 Thread Django 
#22097: IntegerField with given choices leads to wrong has_changed() work
-+---
 Reporter:  igor.mitrenko@…  |Owner:  claudep
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.7-alpha-1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+---
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"cb844497d01ddb45603e47891cdf36ae0b006d03"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cb844497d01ddb45603e47891cdf36ae0b006d03"
 Fixed #22097 -- Fixed change detection for TypedChoiceField

 Thanks Igor Mitrenko for the report.
 }}}

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

Re: [Django] #21643: QuerySets that use F() + timedelta() crash when compiling their query more than once

2014-02-20 Thread Django 
#21643: QuerySets that use F() + timedelta() crash when compiling their query 
more
than once
-+-
 Reporter:  despawn@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   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
-+-

Comment (by mrmachine):

 The test from the fix already applied also fails in 1.5, but the following
 test passes in 1.5 and fails in 1.6 showing that this is a regression.

 {{{
 def test_query_clone(self):
 # Ticket #21643
 qs = Experiment.objects.filter(end__lt=F('start') +
 datetime.timedelta(hours=1))
 qs2 = qs.all()
 list(qs)
 list(qs2)
 }}}

 Is it enough to back port the existing commit, or should this new test
 also be committed and back ported?

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

[Django] #22103: weight loss 3

2014-02-20 Thread Django 
#22103: weight loss 3
---+--
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:  strawberry garcinia cambogia
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+--
 your initial respond I was horrible and I thought I was terrible idea how
 to explain that we're going to varieties in your body and I could feel a
 moving around them back that was a very creepy yeah but they say my life
 media you when she took them out yeah I had to have my want to say was
 three days there and then they cut that plastic thing only back imp they
 all came out just the smell up the stuff that port on my back was
 sickening yet and you must have been life must have been very difficult
 for you then you know bathing just so much pain I couldn’t buy are you
 confer the hill now I have big scabs on my back and big
 scars by this policy over’s it'l[http://strawberrygarciniacambogiapro.com/
 strawberry garcinia cambogia]l ever be so what are you doing these days I
 what’s my granddaughter and I'm going back to school medical malpractice
 cases as we learn from our and everywhere we go are very difficult to win
 fall a real reasons what is your opinion marks firm in what he was able to
 do for you I think he was the only truthful lawyer courthouse but they
 hear that week there sometimes you ask yourself how these other guys
 representing kids
 http://strawberrygarciniacambogiapro.com/

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

Re: [Django] #21643: QuerySets that use F() + timedelta() crash when compiling their query more than once

2014-02-20 Thread Django 
#21643: QuerySets that use F() + timedelta() crash when compiling their query 
more
than once
-+-
 Reporter:  despawn@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   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
-+-

Comment (by mrmachine):

 This is a regression in 1.6, I believe due to the deep copy changes when
 cloning querysets. I confirmed that `F() + timedelta()` does work in 1.5.

 Previously, the `DateModifierNode` expression would  have been deep copied
 every time a queryset was cloned, so it would never have been evaluated
 twice.

 So I think this should be backported.

 Also #22101 was a duplicate.

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

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

Re: [Django] #22101: Querysets using F() expressions with time deltas are not cloned correctly.

2014-02-20 Thread Django 
#22101: Querysets using F() expressions with time deltas are not cloned 
correctly.
-+-
 Reporter:  mrmachine|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:  queryset timedelta   |  Unreviewed
  expression regression  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by mrmachine):

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


Comment:

 Duplicate of #21643. Will add comments there about back porting the fix to
 1.6.

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

Re: [Django] #22101: Querysets using F() expressions with time deltas are not cloned correctly.

2014-02-20 Thread Django 
#22101: Querysets using F() expressions with time deltas are not cloned 
correctly.
-+-
 Reporter:  mrmachine|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  queryset timedelta   |  Unreviewed
  expression regression  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by mrmachine):

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


Comment:

 Pull request opened.

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

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

[Django] #22102: Wrong test ordering

2014-02-20 Thread Django 
#22102: Wrong test ordering
---+
 Reporter:  aptiko |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Testing framework  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 According to the
 [https://docs.djangoproject.com/en/dev/topics/testing/overview/#order-in-
 which-tests-are-executed documentation], the order of test execution is
 first (1) `django.test.TestCase` subclasses, then (2) "all other unittests
 (including `unittest.TestCase`, ...)", then (3) doctests. However,
 `doctest.DocTestCase` is a subclass of `unittest.TestCase`. Therefore the
 documentation is inaccurate: it implies that doctests do not descend from
 `unittest.TestCase`.

 The `django.test.runner` has
 
[https://github.com/django/django/blob/821fc925f0e384966d0b06d03fc1dd0d14cd8ec0/django/test/runner.py#L21
 this]:

 {{{
 #!python
 reorder_by = (TestCase, )
 }}}

 where `TestCase` is actually `django.test.TestCase`. Therefore, in
 contrast to the documentation, no other `unittest.TestCase` subclasses
 seem to be taken into account. Indeed, I'm debugging an application in
 which some doctests insist running before some `LiveServerTestCase` tests;
 the problem goes away if I use a `django.test.runner.DiscoverRunner`
 subclass that has

 {{{
 #!python
 reorder_by = (django.test.TestCase, django.test.SimpleTestCase)
 }}}

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

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

[Django] #22101: Querysets using F() expressions with time deltas are not cloned correctly.

2014-02-20 Thread Django 
#22101: Querysets using F() expressions with time deltas are not cloned 
correctly.
-+-
 Reporter:  mrmachine|  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Database layer   |Version:  1.6
  (models, ORM)  |   Keywords:  queryset timedelta
 Severity:  Normal   |  expression regression
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 This appears to be a regression in 1.6. Possibly refs #16759.

 Looks like expression nodes are no longer deep copied, so when a query
 that uses `DateModifierNode` is cloned, the second clone to be evaluated
 will generate an exception when the `DateModifierNode` tries to pop the
 timedelta off `node.children`.

 Suspected fix is to persist the timedelta as an attribute on
 `DateModifierNode` expression in `__init__` so we don't need to pop it off
 `node.children` when the node is evaluated.

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

Re: [Django] #15730: RequestFactory Example Doesn't Address Class-Based Views

2014-02-20 Thread Django 
#15730: RequestFactory Example Doesn't Address Class-Based Views
---+
 Reporter:  bryanveloso|Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:  1.3
 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 raymond@…):

 Although more verbose, the format of

 generic_view =  GenericViewClass.as_view()
 generic_view(request)

 makes it a bit easier to see what's happening

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

Re: [Django] #22095: Migrations containing RunPython operations cannot be reversed regardless of reverse_code

2014-02-20 Thread Django 
#22095: Migrations containing RunPython operations cannot be reversed 
regardless of
reverse_code
+-
 Reporter:  andrewsg|Owner:  andrewsg
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Ready for checkin
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+-
Changes (by mjtamlyn):

 * stage:  Unreviewed => Ready for checkin


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

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

[Django] #22100: weight loss 0210

2014-02-20 Thread Django 
#22100: weight loss 0210
---+--
 Reporter:  anonymous  |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:  Strawberry Garcinia Cambogia
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+--
 amazing I quit soon in when I stopped eating I do you sometimes but I
 cannot do you find eat quite a bit it will make a dramatic difference in
 your skin prominent separate you on that sometimes talking about like you
 know how to use and things like that happen wow that ended up being
 [http://strawberrygarciniacambogiapro.com/ Strawberry Garcinia Cambogia]
 like huge motivator for me to continue the nutritious because I saw such a
 change in my skin honorees course exercise in street chain my doctor
 recommends getting at least150 minutes cardio week so that would you know
 it’s like 30 minutes tax five I do more than but you know every week not
 is not necessarily like a $200 minutes house up the heavy cardio but I do
 NBC 150minutes a week strength training mix it up so do works for you ever
 going to work out and work for you or you don't have to do that 30 minutes
 five this week whatever plan works for you everyone move makes you feel
 great you know yak know working on the streets loll that’s definitely
 apartment last night number four was taking one day at a time know that's
 it slogan you might know being like slogan help you with addiction but I
 just saw my past life style as in addition to get one did times it seems
 too hard for you how many do this like this is going to take me soling
 just take it one day at a time take intone meal in time one workout time
 if you keep doing one healthy meal in time one workout time overtime will
 feature also if your goal to seems to be was just breaking up take Monday
 59 it was a weekly weigh in recorded watt every week this helped me
 tremendously really helped me see my progress overtime kept me on my
 general goals like a pound a week you know to lose 40 pounds I'm so we
 sell some or something last last but either way just looking back at those
 past weeks in seeing how came really out and that's something I’m going to
 continue doing means as well just trying to keep myself in check have to
 be at like the exact week now forever but keeping weekly weigh in is very
 helpful to me and my some to on number six is to stay motivated up
 whatever keeps you motivated keep that in your life every day for me I
 like slicing my Biggest Loser Extreme Makeover weight loss edition I’m
 read like motivational quotes on Interest use my computer backgrounds who
 like a motivational quote: interest change every week and you don't have
 enough picture beach on your computer me this disclosed really motivates
 you stay motivated books movies whatever you watching Americas next top
 model you work out last act whatever works for you stay motivated on
 number seven 8 are things that I already did continue to do to me healthy
 lifestyle nasty practice and drink lots of waters he's done those things
 into a little different now is that really being practiced it makes sense
 to me as much in the morning as you can I missed something don't mind
 don't is I don't eat a lot night eat too much before so my new plan now is
 a work earlier in the day makes me feel much better throughout the day you
 don't really need a lot energy at night just sleep so I practice safe sex
 every day favorite day and of course I drink lots water helps me stay away
 from bad foods batch thanks to you so I hope this is helpful for you guys
 I would like to do like food blogs like 18 no I didn't tell you guys too
 much like what I actually do eat but there's just too much to say just
 keeping this one video so I would like to do more health and fitness
 videos in the future please give this video a thumbs up if you like this
 if you want to see more videos like this and leave me some comments below
 what are your favorite movies novels what you do to stay in what motivates
 you so really enjoy reading your comments interacting you guys I hope you
 guys are doing great I hope this was helpful and I'll see you in the next
 video thank you for watching
 http://strawberrygarciniacambogiapro.com/

-- 
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

Re: [Django] #22097: IntegerField with given choices leads to wrong has_changed() work

2014-02-20 Thread Django 
#22097: IntegerField with given choices leads to wrong has_changed() work
-+---
 Reporter:  igor.mitrenko@…  |Owner:  claudep
 Type:  Bug  |   Status:  assigned
Component:  Forms|  Version:  1.7-alpha-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+---
Changes (by claudep):

 * status:  new => assigned
 * severity:  Normal => Release blocker
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * owner:  nobody => claudep
 * needs_docs:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 This regression was introduced in a0f3eeccf3d5a90f9914bfe20b15df05673ea59d
 in response to the use case described in #21397.

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

[Django] #22099: weight loss

2014-02-20 Thread Django 
#22099: weight loss
---+--
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:  Strawberry Garcinia Cambogia
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+--
 weight loss that was the one thing that it can cut out with Mike Colder
 everything first month we must guys still have my ok every day and then
 just decided no you don't cut it out and my fiancé and I actually made a
 promise to each other the only so that we do have on occasion spray Diet
 Sprite on occasion I know that’s not good I should really cut it out
 completely I'm just being realistic do still sometimes sprite but we did
 make a promise to each other about six months ago averaging dark sodas
 again this more promise I made to help him dark so it
 [http://strawberrygarciniacambogiapro.com/Strawberry Garcinia Cambogia]
 was something that used to have a lot he's also lost 30 so now herbal
 target we and we’re just working help rest so to something that's not part
 my anymore we also give up fast food forever and that was something that
 again was more his issue mind you for every feels great so that’s
 something that's still number five I don't you from box I was never raised
 eating Lean Cuisines from a box honestly not really creeps me out I want
 to have like.
 http://strawberrygarciniacambogiapro.com/

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

[Django] #22098: weight loss

2014-02-20 Thread Django 
#22098: weight loss
-+-
 Reporter:   |  Owner:  nobody
  anonymous  | Status:  new
 Type:  New  |Version:  1.6
  feature|   Keywords:  weight lossStrawberry Garcinia
Component:   |  Cambogia
  Uncategorized  |  Has patch:  0
 Severity:  Normal   |  UI/UX:  0
 Triage Stage:   |
  Unreviewed |
Easy pickings:  0|
-+-
 money there and it's not good for you don't know what's in your food we
 eat out even when you order something they thinks healthy it's probably
 not parents probably not as healthy as you think so eating out is not
 something that's really apartment game plan really like just knowing where
 my food comes from and that's something that I like to reserve for special
 occasions now and it's great for your waistline and it's free your wallet
 if you avoid I'm for things
 [http://strawberrygarciniacambogiapro.com/Strawberry Garcinia Cambogia]
 that don't previous owner I was never so did you could tell he started
 working in an office a meeting of the college seventy Sony wasn't
 something you really had in the house growing up for some reason when I
 started working in an office my employer provides free zone I started
 thinking like one day okay you know that might not be terrible I know
 Sinus very common in the American diet but it it's not good and like the
 first month .
 http://strawberrygarciniacambogiapro.com/

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

Re: [Django] #20856: Error with admin popups: expected a character buffer object

2014-02-20 Thread Django 
#20856: Error with admin popups: expected a character buffer object
-+-
 Reporter:  heppner.mark@…   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.6
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  admin, str,  | Triage Stage:
  character, inline, popup   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by claudep):

 Thanks, I was able to reproduce the error. However, the answer is:
 `__unicode__` should return unicode and not bytestring.
 It might be that previous versions of Django were more permissive
 regarding this requirement.
 We could of course add some warning like this:
 {{{
 --- a/django/utils/encoding.py
 +++ b/django/utils/encoding.py
 @@ -97,7 +97,12 @@ def force_text(s, encoding='utf-8', strings_only=False,
 errors='strict'):
  try:
  if not isinstance(s, six.string_types):
  if hasattr(s, '__unicode__'):
 +s_class = s.__class__.__name__
  s = s.__unicode__()
 +if not isinstance(s, six.text_type):
 +warnings.warn(
 +"The __unicode__ method of an %s object didn't
 return "
 +"unicode content." % s_class, UnicodeWarning)
  else:
  if six.PY3:
  if isinstance(s, bytes):
 }}}

 But this would add a slight overhead in a frequently-used method for a
 relatively obvious error. Hence I'm -0 for adding this. Others may
 disagree, of course.

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