Re: [Django] #21555: ValidationError is not picklable

[Django]

#21555: ValidationError is not picklable
---+
 Reporter:  zanuxzan   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by loic84):

 * cc: loic@… (added)
 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 It's a good idea as PY2 can't pickle naive exceptions see:
 http://bugs.python.org/issue1692335 (fix was backported all the way to
 python 3.2).

 Since we'd now be calling the constructor, I think it's good practice to
 pass all arguments so the `args` attribute holds meaningful information.

 I've completed the test suite to ensure the more complex scenarios like
 nested `ValidationError`, or `Validation` with `error_dict` behave as
 expected.

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

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

Re: [Django] #19869: Make changing the active language inside `LiveTestServerCase` possible

[Django]

#19869: Make changing the active language inside `LiveTestServerCase` possible
-+-
 Reporter:  void |Owner:
 Type:  New feature  |  unaizalakain
Component:  Testing framework|   Status:  assigned
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by unaizalakain):

 The ``set_language`` view could be used to change the live test server
 thread language but that would mean adding some kind of new method to the
 test case and the inability to use the already defined methods
 (`django.utils.translation.override`, `django.utils.translation.activate`,
 etc).

 Instead, the PR opts for making the thread local that holds the current
 active language a non-local. This is done in the two threads so suddenly
 one thread is capable of accessing the other one's active language. This
 is afterwards reverted to thread locals again.

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

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

Re: [Django] #16256: More class based views: formsets derived generic views

[Django]

#16256: More class based views: formsets derived generic views
---+
 Reporter:  rasca  |Owner:  rasca
 Type:  New feature|   Status:  new
Component:  Generic views  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by dpwrussell):

 * cc: dpwrussell (added)


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

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

Re: [Django] #19869: Make changing the active language inside `LiveTestServerCase` possible

[Django]

#19869: Make changing the active language inside `LiveTestServerCase` possible
-+-
 Reporter:  void |Owner:
 Type:  New feature  |  unaizalakain
Component:  Testing framework|   Status:  assigned
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by unaizalakain):

 * has_patch:  0 => 1


Comment:

 PR sent: https://github.com/django/django/pull/2021

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

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

[Django] #21555: ValidationError is not picklable

[Django]

#21555: ValidationError is not picklable
---+
 Reporter:  zanuxzan   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  0  |  UI/UX:  0
---+
 I have a use case where I'd like to pickle ValidationError however it
 throws up as error:

 For example, I'd expect the following to work:

 {{{#!python
 import pickle
 from django.core.exceptions import ValidationError
 pickle.loads(pickle.dumps(ValidationError('eggs', 'sausage')))
 }}}

 Results in:

 {{{
 TypeError: __init__() takes at least 2 arguments (1 given)
 }}}

 The reason for this is because ValidationError does not call super.

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

[Django] #21556: Date field shows in changed_data due to different format

[Django]

#21556: Date field shows in changed_data due to different format
+
 Reporter:  anonymous   |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Forms   |Version:  1.6
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 For a form, DateField can accept multiple formats, e.g. I can set


 {{{
 form['mydate'].input_formats = ('%Y-%m-%d', '%m/%d/%Y', '%m/%d/%y')
 }}}


 And if I post


 {{{
 form.data = {'mydate': '01/15/2013'}
 }}}


 The form will happily accepts the format.

 However, if the date did not really change:

 {{{

 form.initial = {'mydate': '2013-01-15'}
 form.data = {'mydate': '01/15/2013'}

 }}}

 'mydate' will show up in form.changed_data, because
 widgets.DateInput._format_value can only use one format, there's no way to
 make the widget recognize multiple formats.

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

[Django] #21554: incorrect SQL generated when using multiple inheritance

[Django]

#21554: incorrect SQL generated when using multiple inheritance
--+
 Reporter:  pegler|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:  multiple-
 Triage Stage:  Unreviewed|  inheritance
Easy pickings:  0 |  Has patch:  0
  |  UI/UX:  0
--+
 Our application makes use of multiple-inheritance and we've just come
 across an interesting bug.  There is a test case attached and it fails
 against the latest 1.4, 1.5, 1.6, and master versions.  Though the reason
 changes between versions 1.5 and 1.6.

 The models:
 {{{
 class Person(models.Model):
 name = models.CharField(max_length=50)

 class Politician(models.Model):
 politician_id = models.AutoField(primary_key=True)
 title = models.CharField(max_length=50)

 class Congressman(Person, Politician):
 state = models.CharField(max_length=2)

 class Senator(Congressman):
 pass
 }}}

 The statement {{{ Senator.objects.get(politician_id=1) }}} produces
 incorrect SQL for all versions, but is different between versions.

 1.4.10 and 1.5.5 result in the error "DoesNotExist: Senator matching query
 does not exist." due to it trying to join demo_politician onto
 demo_senator via demo_senator.congressman_ptr_id instead of
 demo_politician.politician_id

 {{{
 SELECT "demo_person"."id", "demo_person"."name", T5."politician_id",
 T5."title", "demo_congressman"."politician_ptr_id",
 "demo_congressman"."person_ptr_id", "demo_congressman"."state",
 "demo_senator"."congressman_ptr_id"
 FROM "demo_senator"
 INNER JOIN "demo_congressman" ON ("demo_senator"."congressman_ptr_id" =
 "demo_congressman"."person_ptr_id")
 INNER JOIN "demo_person" ON ("demo_senator"."congressman_ptr_id" =
 "demo_person"."id")
 INNER JOIN "demo_politician" T5 ON ("demo_senator"."congressman_ptr_id" =
 T5."politician_id")
 WHERE "demo_congressman"."politician_ptr_id" = 1
 }}}


 1.6 and master results in the error "OperationalError: no such column:
 demo_congressman.politician_id".  It incorrectly thinks that politician_id
 is on demo_congressman instead of demo_politician.

 {{{
 SELECT "demo_person"."id", "demo_person"."name",
 "demo_congressman"."politician_id", "demo_congressman"."title",
 "demo_congressman"."politician_ptr_id",
 "demo_congressman"."person_ptr_id", "demo_congressman"."state",
 "demo_senator"."congressman_ptr_id"
 FROM "demo_senator"
 INNER JOIN "demo_congressman" ON ( "demo_senator"."congressman_ptr_id" =
 "demo_congressman"."person_ptr_id" )
 INNER JOIN "demo_person" ON ( "demo_congressman"."person_ptr_id" =
 "demo_person"."id" )
 WHERE "demo_congressman"."politician_ptr_id" = 1
 }}}

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

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

Re: [Django] #21519: django.db.models: get_apps() includes abstract models, get_models() excludes them

[Django]

#21519: django.db.models: get_apps() includes abstract models, get_models()
excludes them
-+-
 Reporter:  Kanuck54 |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Kanuck54):

 Thank you for the thoughtful response, it's much appreciated! Here's
 hoping that there is eventually a documented method for retrieving a list
 of installed applications, and perhaps even the models defined within. One
 day!

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

Re: [Django] #19869: Make changing the active language inside `LiveTestServerCase` possible (was: Add ability to restart LiveServerThread inside a test method)

[Django]

#19869: Make changing the active language inside `LiveTestServerCase` possible
-+-
 Reporter:  void |Owner:
 Type:  New feature  |  unaizalakain
Component:  Testing framework|   Status:  assigned
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  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/062.3edb10f289d4c576ac86d99e7e7f31e8%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19869: Add ability to restart LiveServerThread inside a test method

[Django]

#19869: Add ability to restart LiveServerThread inside a test method
-+-
 Reporter:  void |Owner:
 Type:  New feature  |  unaizalakain
Component:  Testing framework|   Status:  assigned
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by unaizalakain):

 * owner:  nobody => unaizalakain
 * 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/062.8d9de513ba7c23c9c56d4b1d9da7d4f0%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #12233: Redirect logged in user

[Django]

#12233: Redirect logged in user
-+-
 Reporter:  dmathieu |Owner:
 Type:  New feature  |  aaronbassett
Component:  contrib.auth |   Status:  assigned
 Severity:  Normal   |  Version:
 Keywords:   |   Resolution:
  authentication,login   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by buchanae):

 * cc: buchanae (added)


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

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

Re: [Django] #12233: Redirect logged in user

[Django]

#12233: Redirect logged in user
-+-
 Reporter:  dmathieu |Owner:
 Type:  New feature  |  aaronbassett
Component:  contrib.auth |   Status:  assigned
 Severity:  Normal   |  Version:
 Keywords:   |   Resolution:
  authentication,login   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by buchanae):

 I've done some work on this here:
 https://github.com/abuchanan/django/tree/ticket_12233
 Still needs work.

 I changed the argument name to "redirect_authenticated_user" and the value
 type to Boolean (whether authenticated users should be redirected) which
 defaults to False because I figured that would be more backwards-
 compatible.

 The redirect URL would use the same mechanism as normal user login.

 I'm not sure yet how to handle a case where the redirect url is the login
 page (creating an infinite redirect loop). I guess I could chalk that up
 to user error and just let it happen.

 I've also considered that this may be cleaner as a view decorator.
 Thoughts on that?
 Something to the effect of:

 {{{
 @redirect_authenticated_user(redirect_field_name=REDIRECT_FIELD_NAME,
 redirect_url=settings.LOGIN_REDIRECT_URL)
 def your_view(request): pass
 }}}

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

[Django] #21553: InterfaceError in Postgres

[Django]

#21553: InterfaceError in Postgres
--+
 Reporter:  anonymous |  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.6
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 I think this is a hole in the fix for #15901 -- in Postgres,
 connection.is_usable accesses the cursor directly, with the result that
 base exceptions (eg. InterfaceError) are thrown without the normal wrapper
 and thus not caught:

 {{{
 def is_usable(self):
 try:
 # Use a psycopg cursor directly, bypassing Django's utilities.
 self.connection.cursor().execute("SELECT 1")
 except DatabaseError:
 return False
 else:
 return True
 }}}

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

Re: [Django] #21544: Problem with number format when not using L10N

[Django]

#21544: Problem with number format when not using L10N
---+
 Reporter:  yceruto@…  |Owner:  Yonel Ceruto
 Type:  Bug|   Status:  new
Component:  Utilities  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  number format  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by yceruto@…):

 So the following example will not take effect:

 USE_L10N = False
 USE_THOUSAND_SEPARATOR = True
 THOUSAND_SEPARATOR = ','
 NUMBER_GROUPING = 3
 DECIMAL_SEPARATOR = '.'

 You should see 1,000.23
 When today really shows 1000.23 //due to the problem that I explain above

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

Re: [Django] #21544: Problem with number format when not using L10N

[Django]

#21544: Problem with number format when not using L10N
---+
 Reporter:  yceruto@…  |Owner:  Yonel Ceruto
 Type:  Bug|   Status:  new
Component:  Utilities  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  number format  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by yceruto@…):

 I do not understand why mention the word "unexpectedly"?

 It is understood that if I have enabled the thousands separator
 USE_THOUSAND_SEPARATOR = True and NUMBER_GROUPING > 0 to display all
 numbers with the pattern:

 #THOUSAND_SEPARATOR###DECIMAL_SEPARATOR##

 If is enabled or not USE_L10N only determines the "values" of
 DECIMAL_SEPARATOR and THOUSAND_SEPARATOR according to the current locate
 set to LANGUAGE_CODE, but if USE_L10N = False then is display the default
 values.

 Why USE_L10N determining use of thousands separator?

 https://docs.djangoproject.com/en/dev/ref/settings/#use-l10n
 Here not speak of this variable determines the use of the thousands
 separator.

 Please clarify, thanks

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

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

Re: [Django] #21544: Problem with number format when not using L10N

[Django]

#21544: Problem with number format when not using L10N
---+
 Reporter:  yceruto@…  |Owner:  Yonel Ceruto
 Type:  Bug|   Status:  new
Component:  Utilities  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  number format  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by claudep):

 The current behavior is documented:
 ''When USE_L10N is set to True and if this is also set to True, Django
 will use the values of THOUSAND_SEPARATOR and NUMBER_GROUPING to format
 numbers.''
 https://docs.djangoproject.com/en/dev/ref/settings/#use-thousand-separator

 If suddenly we change the rules, people might unexpectedly see thousands
 separators, for example in a section where they have temporarily disabled
 l10n. So the change you proposes is not applicable as is.

 I'll let someone else decide if something should/could be done here or
 simply closed again.

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

Re: [Django] #10190: Charset should be customizable with HttpResponse

[Django]

#10190: Charset should be customizable with HttpResponse
-+-
 Reporter:  Wonlay   |Owner:  aaugustin
 Type:  New feature  |   Status:  assigned
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  HttpResponse,| Triage Stage:  Accepted
  charset, runtime   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * owner:  unaizalakain => aaugustin


Comment:

 Tentatively assigning the ticket to myself to review the latest iteration
 of the 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/064.fa8d46554fe0c85213a2ad70f5fb0485%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21544: Problem with number format when not using L10N

[Django]

#21544: Problem with number format when not using L10N
---+
 Reporter:  yceruto@…  |Owner:  Yonel Ceruto
 Type:  Bug|   Status:  new
Component:  Utilities  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  number format  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by yceruto@…):

 I think the configuration of the variable USE_L10N aims at in this case to
 determine the format of number and not condition the use of the grouping
 of thousands.

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

Re: [Django] #20780: collectstatic --link causes IOError when dangling symlink exists

[Django]

#20780: collectstatic --link causes IOError when dangling symlink exists
-+
 Reporter:  vdboor   |Owner:  johngian
 Type:  Bug  |   Status:  assigned
Component:  contrib.staticfiles  |  Version:  1.5
 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 johngian):

 Updated patch with tests.

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

Re: [Django] #20780: collectstatic --link causes IOError when dangling symlink exists

[Django]

#20780: collectstatic --link causes IOError when dangling symlink exists
-+
 Reporter:  vdboor   |Owner:  johngian
 Type:  Bug  |   Status:  assigned
Component:  contrib.staticfiles  |  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by johngian):

 * needs_tests:  1 => 0


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

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

Re: [Django] #21551: 1.6 regression: Can't load fixtures from subdir

[Django]

#21551: 1.6 regression: Can't load fixtures from subdir
-+-
 Reporter:  jonash   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  1.6
  commands)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:
 Keywords:  loaddata, fixtures   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * needs_better_patch:   => 0
 * severity:  Normal => Release blocker
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Marking as a release blocker since it's a regression.

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

Re: [Django] #21544: Problem with number format when not using L10N

[Django]

#21544: Problem with number format when not using L10N
---+
 Reporter:  yceruto@…  |Owner:  Yonel Ceruto
 Type:  Bug|   Status:  new
Component:  Utilities  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  number format  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by yceruto@…):

 * status:  closed => new
 * version:  1.6 => master
 * resolution:  wontfix =>


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

Re: [Django] #21544: Problem with number format when not using L10N

[Django]

#21544: Problem with number format when not using L10N
---+
 Reporter:  yceruto@…  |Owner:  Yonel Ceruto
 Type:  Bug|   Status:  closed
Component:  Utilities  |  Version:  1.6
 Severity:  Normal |   Resolution:  wontfix
 Keywords:  number format  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by yceruto@…):

 I want to use the grouping of thousands in my numeric formats, for which I
 use the "floatformat" filter.

 My configuration in "settings.py" is:
 USE_L10N = False
 USE_THOUSAND_SEPARATOR = True
 NUMBER_GROUPING = 3

 Showing my numbers without the grouping of thousands.

 When I check in depth the why, I realize that the grouping of thousands is
 subject to the value of the Variable settings.USE_L10N:

 django/utils/numberformat.py:

 def format (...):
 ...
 use_grouping = '''settings.USE_L10N and '''settings.USE_THOUSAND_SEPARATOR

 Think it would be correct to eliminate the constraint that prohibits the
 display grouping of thousands, if not L10N 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/075.e94ea240eeab21b13d3e700811761935%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21544: Problem with number format when not using L10N

[Django]

#21544: Problem with number format when not using L10N
---+
 Reporter:  yceruto@…  |Owner:  Yonel Ceruto
 Type:  Bug|   Status:  closed
Component:  Utilities  |  Version:  1.6
 Severity:  Normal |   Resolution:  wontfix
 Keywords:  number format  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by yceruto@…):

 My proposal is clear here https://github.com/django/django/pull/2015 and I
 see no reason to make a custom filter when I should show the grouping of
 thousands according to my configuration, thanks.

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

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

Re: [Django] #21552: Cannot use None as a query value for iexact lookup

[Django]

#21552: Cannot use None as a query value for iexact lookup
-+-
 Reporter:  denya|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by denya):

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


Comment:

 See the pull request, please:
 https://github.com/django/django/pull/2020

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

[Django] #21552: Cannot use None as a query value for iexact lookup

[Django]

#21552: Cannot use None as a query value for iexact lookup
--+
 Reporter:  denya |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 Current behavior is "None is interpreted as an SQL NULL, but only in exact
 queries."
 '''i'''exact=None lookup fails now. It's wrong behavior.
 iexact=None lookup must behave like exact=None query.

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