Re: [Django] #25995: Add more sophisticated serialization support to JSONField

[Django]

#25995: Add more sophisticated serialization support to JSONField
--+
 Reporter:  jimgraham |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.postgres  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  JSONB | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by zachborboa):

 * cc: zachborboa@… (added)


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

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

Re: [Django] #24082: Unique=True on TextField or CharField should not create an index

[Django]

#24082: Unique=True on TextField or CharField should not create an index
-+-
 Reporter:  djbug|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * cc: charettes (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.e785bc68e68479ce6b928d6401c8d92f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26055: mod_wsgi docs refer to serving CSS files as static without corresponding example

[Django]

#26055: mod_wsgi docs refer to serving CSS files as static without corresponding
example
---+
 Reporter:  chmarr |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.9
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 The page
 https://docs.djangoproject.com/en/1.9/howto/deployment/wsgi/modwsgi/
 refers to serving "any CSS file" as static, but the corresponding example
 does not implement that. Easy fix, for which I'll do a mod and pull
 request, but I'd like to know the intention:

 * Remove the reference to "any CSS file", or
 * Adjust the apache example to do serve CSS as static. In which case where
 will we point it to? the `/static/` directory, or `/static/css/` ??

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

Re: [Django] #26034: Altering CharFields to have both db_index=True and unique=True crashes on postgresql

[Django]

#26034: Altering CharFields to have both db_index=True and unique=True crashes 
on
postgresql
-+-
 Reporter:  kaedroho |Owner:  timgraham
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.8
 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
-+-

Comment (by timgraham):

 [https://github.com/django/django/pull/5947 PR] (have to double check a
 few things tomorrow, so not checking 'has patch' yet)

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

Re: [Django] #26053: makemigrations generates a wrong type for a DurationField column on postgresql

[Django]

#26053: makemigrations generates a wrong type for a DurationField column on
postgresql
-+-
 Reporter:  benjellounayoub  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |   Resolution:
 Severity:  Normal   |  worksforme
 Keywords:  makemigrations,  | Triage Stage:
  DurationField, postgresql, |  Unreviewed
  psycopg2   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Can you double check you didn't make a mistake (i.e. delete the migration
 and re-run `makemigrations`)?  It's unthinkable to me that Django would
 transform `DurationField()` to `FloatField(blank=True, default=0,
 null=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/073.43b12704b58ffbb8d7f15cac2cce9357%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26034: Altering CharFields to have both db_index=True and unique=True crashes on postgresql

[Django]

#26034: Altering CharFields to have both db_index=True and unique=True crashes 
on
postgresql
-+-
 Reporter:  kaedroho |Owner:  timgraham
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.8
 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 timgraham):

 * owner:  nobody => timgraham
 * 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/066.ea773c4466e4e298196c2f1895a30a98%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26053: makemigrations generates a wrong type for a DurationField column on postgresql

[Django]

#26053: makemigrations generates a wrong type for a DurationField column on
postgresql
-+-
 Reporter:  benjellounayoub  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  makemigrations,  | Triage Stage:
  DurationField, postgresql, |  Unreviewed
  psycopg2   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by benjellounayoub):

 No, unfortunately it's not the case

 For the following model
 {{{
 class Foo(models.Model):
 bar = models.DurationField()
 }}}

 I have the following CreateModel in the generated migrations
 {{{
 ...
 operations = [
 migrations.CreateModel(
 name='Foo',
 fields=[
 ('id', models.AutoField(auto_created=True,
 primary_key=True, serialize=False, verbose_name='ID')),
 ('bar', models.FloatField(blank=True, default=0,
 null=True)),
 ],
 ...
 }}}

 Can you test it with the 9.4 postgreSQL version instead of the 9.3 ? it's
 maybe related to this part ...

--
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/073.89a6e9fcbe2a9c9677073b4bc957585d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26033: Add argon2 password hasher

[Django]

#26033: Add argon2 password hasher
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  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 timgraham):

 * needs_docs:  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/067.e88c8798378274aa1cf1baa79dc1729e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25961: remove handling of thread-non-safe GEOS functions

[Django]

#25961: remove handling of thread-non-safe GEOS functions
-+-
 Reporter:  sir-sigurd   |Owner:  sir-
 Type:   |  sigurd
  Cleanup/optimization   |   Status:  new
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 In 59ef6559a31c175c1f52668ef0ffe9b8d87aa5a5:

 Reverted #25961 -- Removed handling of thread-non-safe GEOS functions.

 This reverts commit [312fc1a] as it seems
 to cause segmentation faults as described in the ticket.

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

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

Re: [Django] #25961: remove handling of thread-non-safe GEOS functions

[Django]

#25961: remove handling of thread-non-safe GEOS functions
-+-
 Reporter:  sir-sigurd   |Owner:  sir-
 Type:   |  sigurd
  Cleanup/optimization   |   Status:  new
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * severity:  Release blocker => Normal


Comment:

 The error seems to come from `GEOSContextHandle.__del__()`. Will revert
 for now.

--
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/068.b8660b6c271edb26bcc7feab4996da8d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21113: django_admin_log table stores messages in different languages depending on which language was active while editing.

[Django]

#21113: django_admin_log table stores messages in different languages depending 
on
which language was active while editing.
-+-
 Reporter:  dimyur27@…   |Owner:
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin logs i18n  | 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 timgraham):

 * stage:  Accepted => 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/076.eb4201df3553703fbb958e662f920c82%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22608: Migrations optimizer slow (due to double working?)

[Django]

#22608: Migrations optimizer slow (due to double working?)
--+
 Reporter:  davids|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by ipmb):

 Here's a cProfile of `manage.py makemigrations --empty myapp` on my i5
 macbook with SSD.

 * Django 1.9.1
 * ~80 migrations
 * ~300 tables

 {{{
 66325365 function calls (65778093 primitive calls) in 157.981 seconds
 }}}
 https://gist.github.com/ipmb/75be883defe09fc3dc32

--
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.3bd7da7456982535735286b8f7a05ad0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25928: Documentation on THOUSAND_SEPARATOR and NUMBER_GROUPING is still misleading

[Django]

#25928: Documentation on THOUSAND_SEPARATOR and NUMBER_GROUPING is still 
misleading
---+
 Reporter:  F30|Owner:  Wingie
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Tim Graham ):

 In [changeset:"7f218d98915ef3e76a98ef72075a6bde907dfe41" 7f218d98]:
 {{{
 #!CommitTicketReference repository=""
 revision="7f218d98915ef3e76a98ef72075a6bde907dfe41"
 Fixed #25928 -- Clarified precendence of USE_THOUSAND_SEPARATOR and locale
 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/061.c022b6be157d2a3d7c349010dde56d20%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25928: Documentation on THOUSAND_SEPARATOR and NUMBER_GROUPING is still misleading

[Django]

#25928: Documentation on THOUSAND_SEPARATOR and NUMBER_GROUPING is still 
misleading
---+
 Reporter:  F30|Owner:  Wingie
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"abcf3fe68410ff9ffdfe72df9e925efd044d6ff6" abcf3fe6]:
 {{{
 #!CommitTicketReference repository=""
 revision="abcf3fe68410ff9ffdfe72df9e925efd044d6ff6"
 [1.9.x] Fixed #25928 -- Clarified precendence of USE_THOUSAND_SEPARATOR
 and locale formats.

 Backport of 7f218d98915ef3e76a98ef72075a6bde907dfe41 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/061.ce64beabe99ec39ceb21cbb11e74dc7f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26050: translation.activate does not report failure

[Django]

#26050: translation.activate does not report failure
-+-
 Reporter:  nijel|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:   |  Version:  1.9
  Internationalization   |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

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


Comment:

 Duplicate of #26046.

--
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.1d1b50f50d05771f6e11b6e3d0e7b5bb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26043: Add a hook to run queries between the start of a transaction and a view

[Django]

#26043: Add a hook to run queries between the start of a transaction and a view
---+
 Reporter:  srkunze|Owner:  nobody
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  Version:  1.8
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by timgraham):

 If I understand correctly, the [https://github.com/django/django/pull/5591
 new middleware proposal] would allow implementing a
 `TransactionMiddleware` with the same functionality as `ATOMIC_REQUESTS`
 with the benefit that you could also have other middleware to run queries
 like requested here, so that would solve this ticket.

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

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

Re: [Django] #26051: Rename ATOMIC_REQUESTS to ATOMIC_VIEWS

[Django]

#26051: Rename ATOMIC_REQUESTS to ATOMIC_VIEWS
-+-
 Reporter:  srkunze  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Agreed that if the new middleware proposal works out, that'll be better in
 the long run. Here's the [https://github.com/django/django/pull/5591 draft
 pull request].

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

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

Re: [Django] #25697: Default error views shouldn't silence TemplateDoesNotExist errors if a custom template name was specified

[Django]

#25697: Default error views shouldn't silence TemplateDoesNotExist errors if a
custom template name was specified
--+
 Reporter:  charettes |Owner:  yakky
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Generic views |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by yakky):

 Ok, I'll change the PR to avoid the deprecation period and edit the
 changelog the reflect this change

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

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

Re: [Django] #26037: HttpRequest.get_host() uses either HTTP_X_FORWARDED_HOST or HTTP_X_FORWARDED_PORT => should use both

[Django]

#26037: HttpRequest.get_host() uses either HTTP_X_FORWARDED_HOST or
HTTP_X_FORWARDED_PORT => should use both
--+
 Reporter:  benoitbryon   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * type:  Bug => Cleanup/optimization
 * component:  HTTP handling => Documentation
 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #24855: Allow the use of django.contrib.auth.login without credentials (authentication)

[Django]

#24855: Allow the use of django.contrib.auth.login without credentials
(authentication)
--+
 Reporter:  poiati|Owner:  poiati
 Type:  New feature   |   Status:  closed
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"6ea7b6776c79b7a30b32c4f0c1f2658bc49dfe6c" 6ea7b67]:
 {{{
 #!CommitTicketReference repository=""
 revision="6ea7b6776c79b7a30b32c4f0c1f2658bc49dfe6c"
 Refs #24855 -- fixed typo in 1.10 release notes
 }}}

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

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

Re: [Django] #26038: FileSystemStorage size() method does not use current MEDIA_ROOT setting value

[Django]

#26038: FileSystemStorage size() method does not use current MEDIA_ROOT setting
value
-+-
 Reporter:  voutilad |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  File |  Version:  master
  uploads/storage|
 Severity:  Normal   |   Resolution:
 Keywords:  testing fieldfile| 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 timgraham):

 * stage:  Accepted => 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.f870f2c672734b495cdabfcbc556ac3b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26045: Annotate with conditional aggregation includes non-relevant fields in GROUP BY clause

[Django]

#26045: Annotate with conditional aggregation includes non-relevant fields in 
GROUP
BY clause
-+-
 Reporter:  mark88   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  orm, sql,| Triage Stage:
  annotation |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

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


Comment:

 Mark,

 I tried a building a queryset similar to yours locally and unrelated
 fields were excluded from the `GROUP BY` clause on Django 1.9+ using
 PostgreSQL.

 If it's not the case for your query please reopen this ticket so we can
 investigate what can be done.

 Resolving as ''needsinfo'' until feedback is provided.

--
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.82f5095310c8fb0baeff76199ab74512%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26054: Migrations work on Django 1.9.0 but not on Django 1.9.1

[Django]

#26054: Migrations work on Django 1.9.0 but not on Django 1.9.1
---+--
 Reporter:  grantmcconnaughey  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Migrations |  Version:  1.9
 Severity:  Normal |   Resolution:  duplicate
 Keywords:  migrations | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by charettes):

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


Comment:

 Duplicate of #26034.

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

Re: [Django] #26026: EmptyQuerySet isinstance check broken with not QuerySet datatypes

[Django]

#26026: EmptyQuerySet isinstance check broken with not QuerySet datatypes
-+-
 Reporter:  vladimirbright   |Owner:
 |  andersonresende
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"b5f8c81ce18528ecf7cb4605dca864c961da9373" b5f8c81c]:
 {{{
 #!CommitTicketReference repository=""
 revision="b5f8c81ce18528ecf7cb4605dca864c961da9373"
 Fixed #26026 -- Fixed isinstance crash comparing EmptyQuerySet to non-
 QuerySet.
 }}}

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

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

[Django] #26054: Migrations work on Django 1.9.0 but not on Django 1.9.1

[Django]

#26054: Migrations work on Django 1.9.0 but not on Django 1.9.1
---+
 Reporter:  grantmcconnaughey  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Migrations |Version:  1.9
 Severity:  Normal |   Keywords:  migrations
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I have two migrations in an app. They work on Django 1.9.0, but when I
 upgrade to 1.9.1 they fail. It looks like an issue with altering the field
 `'name'` in the second migration. When I comment out the
 `migrations.AlterField` for `'name'`, the migrations work.

 I'm using Django 1.9.1, Python 2.7.6, and PostgreSQL 9.3.

 Here's the failure traceback:

 {{{
 Traceback (most recent call last):
   File "./manage.py", line 12, in 
 execute_from_command_line(sys.argv)
   File "/home/vagrant/.virtualenvs/django_1_9/local/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 353, in
 execute_from_command_line
 utility.execute()
   File "/home/vagrant/.virtualenvs/django_1_9/local/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 345, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/vagrant/.virtualenvs/django_1_9/local/lib/python2.7/site-
 packages/django/core/management/commands/test.py", line 30, in
 run_from_argv
 super(Command, self).run_from_argv(argv)
   File "/home/vagrant/.virtualenvs/django_1_9/local/lib/python2.7/site-
 packages/django/core/management/base.py", line 348, in run_from_argv
 self.execute(*args, **cmd_options)
   File "/home/vagrant/.virtualenvs/django_1_9/local/lib/python2.7/site-
 packages/django/core/management/commands/test.py", line 74, in execute
 super(Command, self).execute(*args, **options)
   File "/home/vagrant/.virtualenvs/django_1_9/local/lib/python2.7/site-
 packages/django/core/management/base.py", line 399, in execute
 output = self.handle(*args, **options)
   File "/home/vagrant/.virtualenvs/django_1_9/local/lib/python2.7/site-
 packages/django/core/management/commands/test.py", line 90, in handle
 failures = test_runner.run_tests(test_labels)
   File "/home/vagrant/.virtualenvs/django_1_9/local/lib/python2.7/site-
 packages/django/test/runner.py", line 532, in run_tests
 old_config = self.setup_databases()
   File "/home/vagrant/.virtualenvs/django_1_9/local/lib/python2.7/site-
 packages/django/test/runner.py", line 482, in setup_databases
 self.parallel, **kwargs
   File "/home/vagrant/.virtualenvs/django_1_9/local/lib/python2.7/site-
 packages/django/test/runner.py", line 726, in setup_databases
 serialize=connection.settings_dict.get("TEST", {}).get("SERIALIZE",
 True),
   File "/home/vagrant/.virtualenvs/django_1_9/local/lib/python2.7/site-
 packages/django/db/backends/base/creation.py", line 70, in create_test_db
 run_syncdb=True,
   File "/home/vagrant/.virtualenvs/django_1_9/local/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 119, in call_command
 return command.execute(*args, **defaults)
   File "/home/vagrant/.virtualenvs/django_1_9/local/lib/python2.7/site-
 packages/django/core/management/base.py", line 399, in execute
 output = self.handle(*args, **options)
   File "/home/vagrant/.virtualenvs/django_1_9/local/lib/python2.7/site-
 packages/django/core/management/commands/migrate.py", line 200, in handle
 executor.migrate(targets, plan, fake=fake, fake_initial=fake_initial)
   File "/home/vagrant/.virtualenvs/django_1_9/local/lib/python2.7/site-
 packages/django/db/migrations/executor.py", line 92, in migrate
 self._migrate_all_forwards(plan, full_plan, fake=fake,
 fake_initial=fake_initial)
   File "/home/vagrant/.virtualenvs/django_1_9/local/lib/python2.7/site-
 packages/django/db/migrations/executor.py", line 121, in
 _migrate_all_forwards
 state = self.apply_migration(state, migration, fake=fake,
 fake_initial=fake_initial)
   File "/home/vagrant/.virtualenvs/django_1_9/local/lib/python2.7/site-
 packages/django/db/migrations/executor.py", line 198, in apply_migration
 state = migration.apply(state, schema_editor)
   File "/home/vagrant/.virtualenvs/django_1_9/local/lib/python2.7/site-
 packages/django/db/migrations/migration.py", line 123, in apply
 operation.database_forwards(self.app_label, schema_editor, old_state,
 project_state)
   File "/home/vagrant/.virtualenvs/django_1_9/local/lib/python2.7/site-
 packages/django/db/migrations/operations/fields.py", line 201, in
 database_forwards
 schema_editor.alter_field(from_model, from_field, to_field)
   File "/home/vagrant/.virtualenvs/django_1_9/local/lib/python2.7/site-
 packages/django/db/backends/base/schema.py", line 482, in alter_field
 old_db_params, new_db_params, strict)
   File 

Re: [Django] #25704: Response time in WSGIRequestHandler.log_request

[Django]

#25704: Response time in WSGIRequestHandler.log_request
---+
 Reporter:  andreif|Owner:  andreif
 Type:  New feature|   Status:  assigned
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timgraham):

 * needs_better_patch:  0 => 1


Comment:

 Marking as "patch needs improvement" until it's updated after #25684 is
 merged.

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

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

[Django] #26053: makemigrations generates a wrong type for a DurationField column on postgresql

[Django]

#26053: makemigrations generates a wrong type for a DurationField column on
postgresql
-+-
 Reporter:  benjellounayoub  |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Database layer   |Version:  1.9
  (models, ORM)  |   Keywords:  makemigrations,
 Severity:  Normal   |  DurationField, postgresql, psycopg2
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 '''Dependencies''':
 - Django version : 1.9.1
 - PostgreSQL version : "PostgreSQL 9.4.4 on x86_64-unknown-linux-gnu,
 compiled by gcc (Ubuntu 4.9.1-16ubuntu6) 4.9.1, 64-bit"
 - DB conf :
 {{{
 DATABASES = {
 'default': {
 'ENGINE': 'django.db.backends.postgresql_psycopg2',
 'NAME': 'test',
 'USER': 'test',
 'PASSWORD': 'test',
 'HOST': 'localhost',
 'PORT': '',
 },
 }
 }}}

 '''Following those steps:'''
 1 - creating a minimal model example including a DurationField
 {{{
 class Foo(models.Model):
 bar = models.DurationField()
 }}}

 2 - migrate the new model
 {{{
 $ python manage.py makemigrations AppName
 $ python manage.py migrate
 }}}

 3 - then check the type of the 'bar' DB column related to the 'bar'
 DurationField on the 'appname_foo' generated table
 {{{
 \d appname_foo
 }}}

 => The datatype associated to the bar column is not interval as expected
 but float

--
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/058.f23e9982a1385685918ed6c767888154%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21113: django_admin_log table stores messages in different languages depending on which language was active while editing.

[Django]

#21113: django_admin_log table stores messages in different languages depending 
on
which language was active while editing.
-+
 Reporter:  dimyur27@…   |Owner:
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin logs i18n  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by timgraham):

 From a bit of searching, I guess the "good form" is to mitigate
 [http://haacked.com/archive/2009/06/25/json-hijacking.aspx/ JSON
 hijacking]? Those concerns probably aren't relevant here.

--
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.334930c64fc08765589e227988ac9775%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26052: Consider removing conditional_content_removal

[Django]

#26052: Consider removing conditional_content_removal
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  HTTP handling |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * stage:  Unreviewed => Accepted


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

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

[Django] #26052: Consider removing conditional_content_removal

[Django]

#26052: Consider removing conditional_content_removal
+
   Reporter:  aaugustin |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  HTTP handling |Version:  1.9
   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 |
+
 It's the last survivor of the "response_fixes" and I think it should go
 away.

 Graham Dumpleton has described better than I would why frameworks should
 leave the task stripping the body of HEAD requests to servers:
 http://blog.dscpl.com.au/2009/10/wsgi-issues-with-http-head-requests.html
 (first five paragraphs).

 We should check whether mod_wsgi, gunicorn and uwsgi properly strip the
 body of HEAD requests before proceeding. We should also move that behavior
 into runserver -- that is, on the other side of the WSGI.

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

Re: [Django] #23960: HTTP standard no longer requires the Location header to be an absolute URI

[Django]

#23960: HTTP standard no longer requires the Location header to be an absolute 
URI
-+-
 Reporter:  carljm   |Owner:  claudep
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  HTTP handling|  Version:  1.9
 Severity:  Normal   |   Resolution:  fixed
 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
-+-

Comment (by aaugustin):

 The version field usually represents the first version in which a bug is
 detected. It doesn't matter very much anyway.

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

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

Re: [Django] #26037: HttpRequest.get_host() uses either HTTP_X_FORWARDED_HOST or HTTP_X_FORWARDED_PORT => should use both

[Django]

#26037: HttpRequest.get_host() uses either HTTP_X_FORWARDED_HOST or
HTTP_X_FORWARDED_PORT => should use both
---+--
 Reporter:  benoitbryon|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  HTTP handling  |  Version:  1.9
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by benoitbryon):

 +1 for documentation tells "X-Forwarded-Host takes priority over X
 -Forwarded-Port". This would have saved me from trying to setup both
 USE_X_FORWARDED_PORT and USE_X_FORWARDED_HOST.

 +1 for documentation tells "X-Forwarded-Host may include port too", with a
 mention to http://tools.ietf.org/html/rfc7239#page-7 or
 http://tools.ietf.org/html/rfc7230#section-5.4.

 I updated my setup...

 * nginx with `proxy_set_header X-Forwarded-Host $host:$server_port;`
 (removed `x-forwarded-port`)
 * `settings.USE_X_FORWARDED_HOST = True` (removed `USE_X_FORWARDED_PORT`
 => False by default)

 ... and it just works as expected.

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

Re: [Django] #26050: translation.activate does not report failure

[Django]

#26050: translation.activate does not report failure
-+-
 Reporter:  nijel|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  1.9
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by nijel):

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


Comment:

 Just for the reference, testcase executed in Django 1.9:

 {{{
 >>> from django.utils import translation
 >>> translation.activate('foo')
 >>> translation.gettext('x')
 'x'
 }}}

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