date:20140625

Re: [Django] #20189: Collectstatic ignore list expansion on a per project basis

2014-06-25 Thread Django

#20189: Collectstatic ignore list expansion on a per project basis
-+
 Reporter:  mark0978 |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.staticfiles  |  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 Elvard):

 * needs_better_patch:  1 => 0


Comment:

 Patch updated, see PR https://github.com/django/django/pull/2854

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

Re: [Django] #22907: ArrayField querying doesn't work with CharField

2014-06-25 Thread Django

#22907: ArrayField querying doesn't work with CharField
--+--
 Reporter:  Suor  |Owner:
 Type:  Bug   |   Status:  new
Component:  contrib.postgres  |  Version:  master
 Severity:  Release blocker   |   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 Suor):

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


Comment:

 Created a failing test in a pull request
 https://github.com/django/django/pull/2853

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

[Django] #22907: ArrayField querying doesn't work with CharField

2014-06-25 Thread Django

#22907: ArrayField querying doesn't work with CharField
--+
 Reporter:  Suor  |  Owner:
 Type:  Bug   | Status:  new
Component:  contrib.postgres  |Version:  master
 Severity:  Release blocker   |   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 When trying to make query with
 `CharArrayModel.objects.filter(field__contains=['text'])` I get:

 {{{
 ProgrammingError: operator does not exist: character varying[] @> text[]
 LINE 1: ...el" WHERE "postgres_tests_chararraymodel"."field" @> ARRAY['...
  ^
 HINT:  No operator matches the given name and argument type(s). You might
 need to add explicit type casts.
 }}}

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

Re: [Django] #22906: Give ModelState a repr() (was: ModelState.repr)

2014-06-25 Thread Django

#22906: Give ModelState a __repr__()
+--
 Reporter:  CollinAnderson  |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  Migrations  |  Version:  1.7-beta-2
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by CollinAnderson):

 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * type:  Uncategorized => New feature
 * needs_tests:   => 0


Comment:

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

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

[Django] #22906: ModelState.repr

2014-06-25 Thread Django

#22906: ModelState.__repr__
+
 Reporter:  CollinAnderson  |  Owner:  nobody
 Type:  Uncategorized   | Status:  new
Component:  Migrations  |Version:  1.7-beta-2
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  1
Easy pickings:  0   |  UI/UX:  0
+
 I've gotten a number of `InvalidBasesError("Cannot resolve bases for %r" %
 new_unrendered_models)` errors. Could we make a repr for `ModelState`
 objects?

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

Re: [Django] #8162: Increase Permission.name max_length

2014-06-25 Thread Django

#8162: Increase Permission.name max_length
-+-
 Reporter:  juliae   |Owner:  wilsoniya
 Type:  Bug  |   Status:  assigned
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  schemamigration  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by anonymous):

 Replying to [comment:32 anonymous]:
 > There is no validation right now for verbose_name less than 39
 characters, and after migrating the app with south, it will fail 'after'
 creating the tables...so you have a database with all the tables, but no
 permission rows added.
 > This is REALLY annoying and this bug is 6 years old. I understand
 there's always something more important to do, but please it's time to fix
 it.

 Agreed.

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

Re: [Django] #22905: admin template 404.html and 500.html not found

2014-06-25 Thread Django

#22905: admin template 404.html and 500.html not found
-+-
 Reporter:  d182@…   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  admin, templates,|  Unreviewed
  404|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_docs:   => 0
 * version:  1.6 => master
 * type:  Uncategorized => Cleanup/optimization
 * needs_tests:   => 0
 * needs_better_patch:   => 0


Comment:

 I cannot think of any case where they would be used by default. Seems like
 they could be deleted, although it's possible they could be referenced by
 a custom handler404/500.

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

[Django] #22905: admin template 404.html and 500.html not found

2014-06-25 Thread Django

#22905: admin template 404.html and 500.html not found
---+---
 Reporter:  d182@… |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  contrib.admin  |Version:  1.6
 Severity:  Normal |   Keywords:  admin, templates, 404
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+---
 django 1.6.5

 pages 404.html and 500.html exists here
 "./django/contrib/admin/templates/admin/", but app_directories loader
 looking this path "./django/contrib/admin/templates/"

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

Re: [Django] #22894: make admin add related behaviour customizable

2014-06-25 Thread Django

#22894: make admin add related behaviour customizable
--+
 Reporter:  rm_   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  1
--+
Changes (by timo):

 * needs_better_patch:  0 => 1
 * 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/061.d13c06c526c87c339b1304e6b17ba873%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21739: When running tests fixture error output isn't visible (was: When running tests, the fixture loading process has verbosity = 0 hardcoded)

2014-06-25 Thread Django

#21739: When running tests fixture error output isn't visible
-+-
 Reporter:  camilo.lopez.a@… |Owner:  Olek
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  test fixture | Triage Stage:  Accepted
  verbosity  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

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


Comment:

 I don't think the current approach is desirable. We run the tests with `-v
 2` on our continuous integration and this would made the logs *much*
 nosier (lots of things like "No fixture 'authtestdata' in
 '/home/tim/code/django/tests/comment_tests/fixtures'."). Also the PR
 should be against master as we won't make the change in earlier versions.

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

Re: [Django] #22734: Move SMTP / email settings to a dictionary

2014-06-25 Thread Django

#22734: Move SMTP / email settings to a dictionary
-+-
 Reporter:  jwa  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Core (Mail)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  settings, email, |  Needs documentation:  0
  mail, smtp |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-

Comment (by timo):

 I agree the current implementation of `timeout` is odd and we should move
 it to the dictionary setting.

 In terms of grouping email settings, I was thinking it would allow us to
 group other backend options like `EMAIL_FILE_PATH`:
 {{{
 EMAIL = {
'BACKEND': 'django.core.mail.backends.filebased.FileBackend',
'FILE_PATH': '...',
 }
 }}}
 A better grouping might be to have an `EMAIL['BACKEND_OPTIONS']` key
 (mirroring how we have `OPTIONS` in `DATABASES`) with value `{'FILE_PATH':
 '...'}` (or the dictionary that's equivalent to the proposed `SMTP_CONFIG`
 if `'BACKEND'` were `smtp.EmailBackend`).

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

Re: [Django] #18586: Rewrite unit tests migrated from doctests

2014-06-25 Thread Django

#18586: Rewrite unit tests migrated from doctests
--+
 Reporter:  konk  |Owner:  judy2k
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Testing framework |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  unit tests| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timo):

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

Re: [Django] #21158: Set an implicit wait for selenium.

2014-06-25 Thread Django

#21158: Set an implicit wait for selenium.
-+-
 Reporter:  apollo13 |Owner:
 Type:   |  bsilverberg
  Cleanup/optimization   |   Status:  closed
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 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 timo):

 * status:  assigned => closed
 * 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/066.9bf2806e627ae822c502aaeeb303f062%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 7e2c80: Split tests.basic.ModelTests in several tests; ref...

2014-06-25 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 7e2c804c9417617934cd731a4537719a1bd8d985
  
https://github.com/django/django/commit/7e2c804c9417617934cd731a4537719a1bd8d985
  Author: zsoldosp 
  Date:   2014-06-25 (Wed, 25 Jun 2014)

  Changed paths:
M tests/basic/tests.py
M tests/dates/tests.py
M tests/datetimes/tests.py
M tests/queries/models.py
M tests/queries/tests.py

  Log Message:
  ---
  Split tests.basic.ModelTests in several tests; refs #18586.


-- 
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/53ab25d282b37_77191025d402681c%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #18586: Rewrite unit tests migrated from doctests

2014-06-25 Thread Django

#18586: Rewrite unit tests migrated from doctests
--+
 Reporter:  konk  |Owner:  judy2k
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Testing framework |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  unit tests| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"7e2c804c9417617934cd731a4537719a1bd8d985"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7e2c804c9417617934cd731a4537719a1bd8d985"
 Split tests.basic.ModelTests in several tests; refs #18586.
 }}}

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

Re: [Django] #21158: Set an implicit wait for selenium.

2014-06-25 Thread Django

#21158: Set an implicit wait for selenium.
-+-
 Reporter:  apollo13 |Owner:
 Type:   |  bsilverberg
  Cleanup/optimization   |   Status:  assigned
Component:  Testing framework|  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 apollo13):

 We currently don't have any random failures (or at least not really
 often), so I think we can close this 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/066.5ffed84cbcddf60fdab6f02c836a8f50%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #16487: F expression with timedelta does not work with __range query filter

2014-06-25 Thread Django

#16487: F expression with timedelta does not work with __range query filter
-+-
 Reporter:  bendavis78   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by bendavis78):

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

Re: [Django] #22791: makemigrations interactive questioner ignores app labels

2014-06-25 Thread Django

#22791: makemigrations interactive questioner ignores app labels
-+-
 Reporter:  bendavis78   |Owner:  whoshuu
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Migrations   |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by bendavis78):

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

Re: [Django] #22752: PasswordResetForm email context is missing current_app

2014-06-25 Thread Django

#22752: PasswordResetForm email context is missing current_app
--+
 Reporter:  bendavis78|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by bendavis78):

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

Re: [Django] #22752: PasswordResetForm email context is missing current_app

2014-06-25 Thread Django

#22752: PasswordResetForm email context is missing current_app
--+
 Reporter:  bendavis78|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by bendavis78):

 @bmispelon, I think one would expect the context to be identical in both
 the body and the subject. Whether or not there's a use case, I can't think
 of any justification for making them separate. I plan on working on this
 (as well as various other tickets I've submitted) once I get a little more
 free time.

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

Re: [Django] #20743: Support keyfile/certfile in SMTP connections

2014-06-25 Thread Django

#20743: Support keyfile/certfile in SMTP connections
-+
 Reporter:  claudep  |Owner:  andialbrecht
 Type:  New feature  |   Status:  assigned
Component:  Core (Mail)  |  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 timo):

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


Comment:

 To avoid the new setting, we could use the same technique that we used for
 adding
 
[https://docs.djangoproject.com/en/dev/topics/email/#django.core.mail.backends.smtp.EmailBackend.timeout
 timeout] in 1.7, but only if we go that route for resolving #22734.
 Otherwise, we can go with whatever solution we adopt in #22734.

 Marking this as "Patch needs improvement" for now. Once #22734 is resolved
 and this is updated, please uncheck.

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

Re: [Django] #22734: Move SMTP / email settings to a dictionary

2014-06-25 Thread Django

#22734: Move SMTP / email settings to a dictionary
-+-
 Reporter:  jwa  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Core (Mail)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  settings, email, |  Needs documentation:  0
  mail, smtp |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-

Comment (by claudep):

 I think that choosing to customize some behavior by a setting or by code
 depends on:

  * the configured value is strongly instance-specific, and might change
 for each environment: -> setting
  * the configured value is project-specific and is not supposed to change
 on each deployment environment: -> code

 For example, the SMTP host and port are completely dependent on the
 machine on which the code is running. I find a bit strange to ask people
 to change the code of a project or application each time they want to
 deploy it on another environment. With this reasoning, I think that even
 the timeout might be better set by a setting :-/

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

Re: [Django] #22857: Django 1.7 runserver auto-reload : setting behaviour by extensions

2014-06-25 Thread Django

#22857: Django 1.7 runserver auto-reload : setting behaviour by extensions
-+-
 Reporter:  artscoop |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:
  commands)  |  1.7-beta-2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by artscoop):

 @claudep Works flawlessly. Could not test on the master branch since it
 breaks many third party apps, but copied the autoreload.py file into the
 working 1.7b4. the server did not restart on .mo file changes, yet the new
 translation was properly taken into account.

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

Re: [Django] #22900: ugettext_lazy with arguments causes RuntimeError

2014-06-25 Thread Django

#22900: ugettext_lazy with arguments causes RuntimeError
-+-
 Reporter:  Karmux   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:   |  Version:
  Internationalization   |  1.7-beta-2
 Severity:  Normal   |   Resolution:
 Keywords:  app-loading  | 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):

 * type:  Uncategorized => New feature
 * component:  Translations => Internationalization
 * stage:  Unreviewed => Accepted


Comment:

 This is expected behavior with the current implementation, the `%` (mod)
 operator on lazy strings does produce the final string.
 We might experiment with delaying the translation in this case and find
 out (a) if it's possible and (b) if the behavior change is not too much
 backwards incompatible.
 At the very least, we could improve the documentation.

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

Re: [Django] #22894: make admin add related behaviour customizable

2014-06-25 Thread Django

#22894: make admin add related behaviour customizable
-+-
 Reporter:  rm_  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-

Comment (by timo):

 Yes, please add it to the PR and I'll add some comments.

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

Re: [Django] #22894: make admin add related behaviour customizable

2014-06-25 Thread Django

#22894: make admin add related behaviour customizable
-+-
 Reporter:  rm_  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-

Comment (by rm_):

 If change looks ok i've done the same for raw_id_fields widget and unified
 common js code here
 https://github.com/xrmx/django/commits/morepopupcleanup

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

Re: [Django] #21158: Set an implicit wait for selenium.

2014-06-25 Thread Django

#21158: Set an implicit wait for selenium.
-+-
 Reporter:  apollo13 |Owner:
 Type:   |  bsilverberg
  Cleanup/optimization   |   Status:  assigned
Component:  Testing framework|  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 timo):

 * cc: timo (added)
 * needs_better_patch:  0 => 1


Comment:

 I left an idea for improvement on the pull request.

 @apollo13, any thoughts on the comments in the thread? Was the idea to
 commit this and see if it helps with the random failures on Jenkins?

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

Re: [Django] #20189: Collectstatic ignore list expansion on a per project basis

2014-06-25 Thread Django

#20189: Collectstatic ignore list expansion on a per project basis
-+
 Reporter:  mark0978 |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.staticfiles  |  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 timo):

 * needs_better_patch:  0 => 1


Comment:

 We try to avoid new settings at all costs, although I don't have any
 alternate suggestions in this case. Anyway, the patch needs to be updated.

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

Re: [Django] #22734: Move SMTP / email settings to a dictionary

2014-06-25 Thread Django

#22734: Move SMTP / email settings to a dictionary
-+-
 Reporter:  jwa  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Core (Mail)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  settings, email, |  Needs documentation:  0
  mail, smtp |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-

Comment (by timo):

 Another option: we could deprecate the SMTP settings completely and
 recommend setting them the same way as
 
[https://docs.djangoproject.com/en/dev/topics/email/#django.core.mail.backends.smtp.EmailBackend.timeout
 timeout].

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

[django/django] 54a6ab: [1.7.x] Fixed typo in revamped forms intro doc.

2014-06-25 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 54a6ab207762bf581bf74e7e3d6b9e0520864baa
  
https://github.com/django/django/commit/54a6ab207762bf581bf74e7e3d6b9e0520864baa
  Author: Ramiro Morales 
  Date:   2014-06-25 (Wed, 25 Jun 2014)

  Changed paths:
M docs/topics/forms/index.txt

  Log Message:
  ---
  [1.7.x] Fixed typo in revamped forms intro doc.

Backport of 77c0a904cb 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/53aaf9951c963_36f5d3d383581e%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 77c0a9: Fixed typo in revamped forms intro doc.

2014-06-25 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 77c0a904cbb2ff144dc42deac4e9fbca0c370f1b
  
https://github.com/django/django/commit/77c0a904cbb2ff144dc42deac4e9fbca0c370f1b
  Author: Ramiro Morales 
  Date:   2014-06-25 (Wed, 25 Jun 2014)

  Changed paths:
M docs/topics/forms/index.txt

  Log Message:
  ---
  Fixed typo in revamped forms intro doc.


-- 
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/53aae86fbd646_73061397d3493489%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22903: Cannot generate a migration if index_together or unique_together is removed from a model

2014-06-25 Thread Django

#22903: Cannot generate a migration if index_together or unique_together is 
removed
from a model
-+-
 Reporter:  timo |Owner:  timo
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:
 Severity:  Release blocker  |  1.7-beta-2
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"e0cd07ec2f394e6db3d17de19809a8f377cd1578"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e0cd07ec2f394e6db3d17de19809a8f377cd1578"
 Fixed #22903 -- Fixed migration generation if index_together or
 unique_together is removed from a model.
 }}}

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

Re: [Django] #22903: Cannot generate a migration if index_together or unique_together is removed from a model

2014-06-25 Thread Django

#22903: Cannot generate a migration if index_together or unique_together is 
removed
from a model
-+-
 Reporter:  timo |Owner:  timo
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:
 Severity:  Release blocker  |  1.7-beta-2
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"f1428dc796817a241d49319122663129d78ca853"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f1428dc796817a241d49319122663129d78ca853"
 [1.7.x] Fixed #22903 -- Fixed migration generation if index_together or
 unique_together is removed from a model.

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

[django/django] f1428d: [1.7.x] Fixed #22903 -- Fixed migration generation...

2014-06-25 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: f1428dc796817a241d49319122663129d78ca853
  
https://github.com/django/django/commit/f1428dc796817a241d49319122663129d78ca853
  Author: Tim Graham 
  Date:   2014-06-25 (Wed, 25 Jun 2014)

  Changed paths:
M django/db/migrations/autodetector.py
M django/db/migrations/operations/models.py
M tests/migrations/test_autodetector.py

  Log Message:
  ---
  [1.7.x] Fixed #22903 -- Fixed migration generation if index_together or 
unique_together is removed from a model.

Backport of e0cd07ec2f 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/53aad70378146_53ac10edd40251b6%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] e0cd07: Fixed #22903 -- Fixed migration generation if inde...

2014-06-25 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e0cd07ec2f394e6db3d17de19809a8f377cd1578
  
https://github.com/django/django/commit/e0cd07ec2f394e6db3d17de19809a8f377cd1578
  Author: Tim Graham 
  Date:   2014-06-25 (Wed, 25 Jun 2014)

  Changed paths:
M django/db/migrations/autodetector.py
M django/db/migrations/operations/models.py
M tests/migrations/test_autodetector.py

  Log Message:
  ---
  Fixed #22903 -- Fixed migration generation if index_together or 
unique_together is removed from a model.


-- 
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/53aad6ead7a5f_5bf51265d444501f%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22904: Django returns an HTTP 200 on a HEAD request for a non-existing file in the media folder

2014-06-25 Thread Django

#22904: Django returns an HTTP 200 on a HEAD request for a non-existing file in 
the
media folder
-+-
 Reporter:  sHtev|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  File |  Version:  1.5
  uploads/storage|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  staticfiles HEAD |  Unreviewed
  request HTTP   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

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


Comment:

 I can't reproduce this. How are you serving content in the media folder? I
 tested using [https://docs.djangoproject.com/en/1.6/howto/static-files
 /#serving-files-uploaded-by-a-user-during-development static()] and saw
 the following in the development server logs:

 `[25/Jun/2014 13:56:21] "HEAD /media/foo HTTP/1.1" 404 0`

 after running:

 `$ curl -i -X HEAD http://localhost:8000/media/foo`

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

[Django] #22904: Django returns an HTTP 200 on a HEAD request for a non-existing file in the media folder

2014-06-25 Thread Django

#22904: Django returns an HTTP 200 on a HEAD request for a non-existing file in 
the
media folder
-+-
 Reporter:  sHtev|  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  File |Version:  1.5
  uploads/storage|   Keywords:  staticfiles HEAD
 Severity:  Normal   |  request HTTP
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 I have some Javascript code in a django app that performs a HEAD request
 on a file to test if it exists. This file is in the media folder of the
 standard static files setup in development.

 However, django returns an HTTP 200 code regardless of whether the file
 exists or not. Expected behaviour is that it should return a 404 when the
 file does not exist.

 GET requests return a 404 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/048.09d421f22ff44861f613ef53174d097a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22900: ugettext_lazy with arguments causes RuntimeError

2014-06-25 Thread Django

#22900: ugettext_lazy with arguments causes RuntimeError
---+--
 Reporter:  Karmux |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Translations   |  Version:  1.7-beta-2
 Severity:  Normal |   Resolution:
 Keywords:  app-loading| Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by timo):

 Note this will raise a different message on master due to
 9618d68b345fe69c787f8426b07e920e647e05f3.

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

Re: [Django] #22903: Cannot generate a migration if index_together or unique_together is removed from a model

2014-06-25 Thread Django

#22903: Cannot generate a migration if index_together or unique_together is 
removed
from a model
-+-
 Reporter:  timo |Owner:  timo
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:
 Severity:  Release blocker  |  1.7-beta-2
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by charettes):

 * stage:  Accepted => Ready for checkin


Comment:

 Added some minor nitpick comments on the PR. If the build succeeds this
 should be RFC.

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

Re: [Django] #22900: ugettext_lazy with arguments causes RuntimeError

2014-06-25 Thread Django

#22900: ugettext_lazy with arguments causes RuntimeError
---+--
 Reporter:  Karmux |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Translations   |  Version:  1.7-beta-2
 Severity:  Normal |   Resolution:
 Keywords:  app-loading| Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by aaugustin):

 * keywords:   => app-loading
 * 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/064.c665ef0be1a5bdcefb67939f1d8e7fad%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22902: "No changes detected" with SQLite, wrong answer

2014-06-25 Thread Django

Comment (by timo):

I'm not sure how to produce the behavior you're describing. For example if
I change the `Choice.votes` field in the tutorial to `vote`, I get the
following prompt:
{{{
$ python manage.py makemigrations polls
Did you rename choice.votes to choice.vote (a IntegerField)? [y/N] y
Migrations for 'polls':
0002_auto_20140625_1306.py:
- Rename field votes on choice to vote
}}}

SQLite does have
[https://docs.djangoproject.com/en/dev/topics/migrations/#sqlite some
documented caveats], but as far as I know, the autodetector behavior is
independent of the database you are using.

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

Re: [Django] #22903: Cannot generate a migration if index_together or unique_together is removed from a model

2014-06-25 Thread Django

#22903: Cannot generate a migration if index_together or unique_together is 
removed
from a model
-+--
 Reporter:  timo |Owner:  timo
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-beta-2
 Severity:  Release blocker  |   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 timo):

 [https://github.com/django/django/pull/2849 PR]

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

[Django] #22903: Cannot generate a migration if index_together or unique_together is removed from a model

2014-06-25 Thread Django

#22903: Cannot generate a migration if index_together or unique_together is 
removed
from a model
---+
   Reporter:  timo |  Owner:  timo
   Type:  Bug  | Status:  new
  Component:  Migrations   |Version:  1.7-beta-2
   Severity:  Release blocker  |   Keywords:
   Triage Stage:  Accepted |  Has patch:  1
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 {{{
 Traceback (most recent call last):
 ...
   File "/home/tim/code/django/django/db/migrations/autodetector.py", line
 50, in changes
 changes = self._detect_changes(convert_apps)
   File "/home/tim/code/django/django/db/migrations/autodetector.py", line
 178, in _detect_changes
 self.generate_altered_index_together()
   File "/home/tim/code/django/django/db/migrations/autodetector.py", line
 788, in generate_altered_index_together
 index_together=new_model_state.options['index_together'],
 KeyError: u'index_together'

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

[django/django] e76984: Removed unused variable.

2014-06-25 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e769846eec14d3b522c132104e2ecba9cf96d3b0
  
https://github.com/django/django/commit/e769846eec14d3b522c132104e2ecba9cf96d3b0
  Author: Tim Graham 
  Date:   2014-06-25 (Wed, 25 Jun 2014)

  Changed paths:
M tests/defer_regress/tests.py

  Log Message:
  ---
  Removed unused variable.


-- 
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/53aac2853a6db_59046e3d4093b6%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22902: "No changes detected" with SQLite, wrong answer

2014-06-25 Thread Django

#22902: "No changes detected" with SQLite, wrong answer
-+--
 Reporter:  d.kzlv.ru@…  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Migrations   |  Version:  master
 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 Dan ):

 For example, changing name of a field.

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

Re: [Django] #18320: Unit test model_formsets_regress.FormsetTests.test_extraneous_query_is_not_run expects wrong number of queries

2014-06-25 Thread Django

#18320: Unit test
model_formsets_regress.FormsetTests.test_extraneous_query_is_not_run
expects wrong number of queries
---+--
 Reporter:  manfre |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:  worksforme
 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 manfre):

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


Comment:

 I found another solution and forgot about this case. Closing.

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

Re: [Django] #22902: "No changes detected" with SQLite, wrong answer

2014-06-25 Thread Django

#22902: "No changes detected" with SQLite, wrong answer
-+--
 Reporter:  d.kzlv.ru@…  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Migrations   |  Version:  master
 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 timo):

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


Comment:

 Which changes are these?

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

Re: [Django] #22734: Move SMTP / email settings to a dictionary

2014-06-25 Thread Django

#22734: Move SMTP / email settings to a dictionary
-+-
 Reporter:  jwa  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Core (Mail)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  settings, email, |  Needs documentation:  0
  mail, smtp |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-

Comment (by claudep):

 For me, email backend is one thing, and SMTP settings an other. I don't
 see the gain in trying to group them, but... it's just me :-)

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

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

[Django] #22902: "No changes detected" with SQLite, wrong answer

2014-06-25 Thread Django

#22902: "No changes detected" with SQLite, wrong answer
-+
 Reporter:  d.kzlv.ru@…  |  Owner:  nobody
 Type:  New feature  | Status:  new
Component:  Migrations   |Version:  master
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 If you make any changes, that SQLite doesn't allow to change via ALTER sql
 statement, Django shouldn't say "No changes detected", but it should say
 "You're using a piece of chick, so we cannot ALTER your changes".

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

Re: [Django] #18150: Uploading a file ending with a backslash fails

2014-06-25 Thread Django

#18150: Uploading a file ending with a backslash fails
-+-
 Reporter:  Peter Kuma   |Owner:
 Type:  Bug  |  supersteve9219
Component:  File |   Status:  assigned
  uploads/storage|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 Patch no longer applies cleanly. Also, if we drop `IE_santize`, we need to
 document the consequences of that in the release notes.

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

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

Re: [Django] #13694: SafeMIMEText argument names incompatible with those from MIMEText

2014-06-25 Thread Django

#13694: SafeMIMEText argument names incompatible with those from MIMEText
-+
 Reporter:  davenaff |Owner:  ramiro
 Type:  Bug  |   Status:  assigned
Component:  Core (Mail)  |  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 timo):

 * needs_better_patch:  0 => 1


Comment:

 Removing `__init__` doesn't look like an option anymore as there is much
 more logic in there 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/066.5e3106a4ed22b4fd44546ac22621f4fe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19721: Django admin allows filtering using the field lookups such as "in", but it is impossible to include a value that contains a comma

2014-06-25 Thread Django

#19721: Django admin allows filtering using the field lookups such as "in", but 
it
is impossible to include a value that contains a comma
---+
 Reporter:  aruseni|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timo):

 * needs_better_patch:  0 => 1


Comment:

 Patch no longer applies cleanly.

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

Re: [Django] #22901: Django and fastcgi upstream application timeout

2014-06-25 Thread Django

#22901: Django and fastcgi upstream application timeout
---+--
 Reporter:  atarkowska |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  HTTP handling  |  Version:  1.6
 Severity:  Normal |   Resolution:  invalid
 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 timo):

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


Comment:

 I don't think so. In fact, FastCGI support has been deprecated in Django
 1.7 and will be removed in Django 1.9.

 Also as this seems more of a usage question, it's more appropriate to ask
 using the resources found in 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/068.af32d33ee3ac8c7e51d3b4acc4f9e2e3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22050: defer('related__subfield') and select_related() on proxy model raises error

2014-06-25 Thread Django

#22050: defer('related__subfield') and select_related() on proxy model raises 
error
-+-
 Reporter:  lovasb   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  defer,proxy,query|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"9385aa3198e7ab460990dd8f82e466fd243557a0"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9385aa3198e7ab460990dd8f82e466fd243557a0"
 Fixed #22050 -- Fixed defer fields on proxy related models.
 }}}

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

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

[django/django] 9385aa: Fixed #22050 -- Fixed defer fields on proxy relate...

2014-06-25 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 9385aa3198e7ab460990dd8f82e466fd243557a0
  
https://github.com/django/django/commit/9385aa3198e7ab460990dd8f82e466fd243557a0
  Author: Lovas Bence 
  Date:   2014-06-25 (Wed, 25 Jun 2014)

  Changed paths:
M django/db/models/sql/query.py
M tests/defer_regress/models.py
M tests/defer_regress/tests.py

  Log Message:
  ---
  Fixed #22050 -- Fixed defer fields on proxy related models.


-- 
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/53aab0b6d6d1c_72a188fd382634%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22901: Django and fastcgi upstream application timeout

2014-06-25 Thread Django

#22901: Django and fastcgi upstream application timeout
---+--
 Reporter:  atarkowska |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  HTTP handling  |  Version:  1.6
 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 A.Tarkowska@…):

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

Re: [Django] #20128: csrfmiddleware sometimes raises IOError via _load_post_and_files

2014-06-25 Thread Django

#20128: csrfmiddleware sometimes raises IOError via _load_post_and_files
--+
 Reporter:  wdoekes   |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.csrf  |  Version:  1.5
 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 Tim Graham ):

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


Comment:

 In [changeset:"815e7a57216b3e6ef716e924016acb09633ea8d1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="815e7a57216b3e6ef716e924016acb09633ea8d1"
 Fixed #20128 -- Made CsrfViewMiddleware ignore IOError when reading POST
 data.

 Thanks Walter Doekes.
 }}}

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

[django/django] 815e7a: Fixed #20128 -- Made CsrfViewMiddleware ignore IOE...

2014-06-25 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 815e7a57216b3e6ef716e924016acb09633ea8d1
  
https://github.com/django/django/commit/815e7a57216b3e6ef716e924016acb09633ea8d1
  Author: Tim Graham 
  Date:   2014-06-25 (Wed, 25 Jun 2014)

  Changed paths:
M django/middleware/csrf.py
M tests/csrf_tests/tests.py

  Log Message:
  ---
  Fixed #20128 -- Made CsrfViewMiddleware ignore IOError when reading POST data.

Thanks Walter Doekes.


-- 
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/53aaadb217173_590b9f7d38923a8%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[Django] #22901: Django and fastcgi upstream application timeout

2014-06-25 Thread Django

#22901: Django and fastcgi upstream application timeout
---+
Reporter: atarkowska | Owner: nobody
Type: Uncategorized | Status: new
Component: HTTP handling |Version: 1.6
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
---+
I have been trying to compare django application deployment on nginx and
apache and what I came across is an issue with fastcgi upstream
application timeout. Basically the following configs return as stated:

{{{
location / {
...
fastcgi_read_timeout 60
}

504 Gateway Time-out 1m

}}}

{{{
FastCGIExternalServer "/path/to/myapp.fcgi" 0.0.0.0:4080 -idle-timeout 60

500 Internal Server Error 1m
}}}

With my custom handler500 ('django.views.defaults.server_error') I am
catching that as standards error, that is not really what I feel should
happen. Definitely 504 Gateway Timeout is more intuitive. Although, I have
no way of catching 504 with default django HttpResponse. Is there any plan
to help developers to handle it better and unify it?

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

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

Re: [Django] #16406: Allow separate access to matches from urlpatterns and extra_context args

2014-06-25 Thread Django

#16406: Allow separate access to matches from urlpatterns and extra_context args
--+
 Reporter:  apollo13  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (URLs)   |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  resolvers, reverse| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timo):

 * needs_better_patch:  0 => 1


Comment:

 Patch no longer applies cleanly.

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

Re: [Django] #18320: Unit test model_formsets_regress.FormsetTests.test_extraneous_query_is_not_run expects wrong number of queries

2014-06-25 Thread Django

#18320: Unit test
model_formsets_regress.FormsetTests.test_extraneous_query_is_not_run
expects wrong number of queries
---+
 Reporter:  manfre |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by timo):

 Is this still desired or did you find another solution in the past 2
 years? It looks like it was just forgotten.

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

Re: [Django] #22838: Deprecate ModelChoiceField.cache_choices

2014-06-25 Thread Django

#22838: Deprecate ModelChoiceField.cache_choices
-+-
 Reporter:  mjtamlyn |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Forms|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 In 2764146586509c2c81ad14da4ac86efa3a949308:

 Fixed #22838 -- Deprecated ModelChoiceField.cache_choices.

 Undocumented, untested and probably not even useful feature.

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

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

Re: [Django] #15610: Generic Foreign Keys break when used with multi-db.

2014-06-25 Thread Django

#15610: Generic Foreign Keys break when used with multi-db.
--+
 Reporter:  legutierr |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.contenttypes  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by timo):

 We have [https://docs.djangoproject.com/en/dev/internals/contributing/ a
 lot of documentation] with tips for new contributors. You may find the
 [https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
 /submitting-patches/#patch-review-checklist patch review checklist]
 particularly helpful.

-- 
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.de05772c4870a7a8d0d6211f95985d44%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.

2014-06-25 Thread Django

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

Comment (by jooyous):

 Replying to [comment:6 anonymous]:
 > I can't get ugettext to translate "Changed" for some reason, even though
 there are bits of code where it does it successfully and I'm not sure what
 I'm doing wrong.

 Whoops, that was me. Didn't realize I was logged out.

-- 
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.0991b5d256eadc2871c17dae9fb9%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.

2014-06-25 Thread Django

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

Comment (by anonymous):

 I can't get ugettext to translate "Changed" for some reason, even though
 there are bits of code where it does it successfully and I'm not sure what
 I'm doing wrong.

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

Re: [Django] #22734: Move SMTP / email settings to a dictionary

2014-06-25 Thread Django

#22734: Move SMTP / email settings to a dictionary
-+-
 Reporter:  jwa  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Core (Mail)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  settings, email, |  Needs documentation:  0
  mail, smtp |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-

Comment (by timo):

 Thoughts on:
 {{{
 EMAIL = {
 'BACKEND': 'django.core.mail.backends.smtp.EmailBackend',
 'HOST': 'localhost',
 'PORT': 25,
 }
 }}}
 (to allow consolidating more than just the SMTP settings)

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

Re: [Django] #15610: Generic Foreign Keys break when used with multi-db.

2014-06-25 Thread Django

#15610: Generic Foreign Keys break when used with multi-db.
--+
 Reporter:  legutierr |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.contenttypes  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by socketubs):

 If I understand correctly why these patches are not applied, it's just
 because tests are missing ?
 I can help for writing tests but I have never contributed to Django...

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

[Django] #22900: ugettext_lazy with arguments causes RuntimeError

2014-06-25 Thread Django

#22900: ugettext_lazy with arguments causes RuntimeError
---+
 Reporter:  Karmux |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Translations   |Version:  1.7-beta-2
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 If I use arguments with translations I get RuntimeError.

 {{{
 help_text=_('e.g. %(foo)s or %(bar)s') % {
 'foo': 'footxt', 'bar': 'bartxt'})
 }}}

 This code causes following error:

 {{{
 Traceback (most recent call last):
   File "./manage", line 13, in 
 django.setup()
   File "/usr/local/lib/python2.7/dist-packages/django/__init__.py", line
 21, in setup
 apps.populate(settings.INSTALLED_APPS)
   File "/usr/local/lib/python2.7/dist-packages/django/apps/registry.py",
 line 106, in populate
 app_config.import_models(all_models)
   File "/usr/local/lib/python2.7/dist-packages/django/apps/config.py",
 line 190, in import_models
 self.models_module = import_module(models_module_name)
   File "/usr/lib/python2.7/importlib/__init__.py", line 37, in
 import_module
 __import__(name)
   File "/home/karmo/Dev/project/api/models.py", line 205, in 
 class Test(Model):
   File "/home/karmo/Dev/project/api/models.py", line 222, in Test
 'foo': 'footxt', 'bar': 'bartxt'})
   File "/usr/local/lib/python2.7/dist-
 packages/django/utils/functional.py", line 179, in __mod__
 return six.text_type(self) % rhs
   File "/usr/local/lib/python2.7/dist-
 packages/django/utils/functional.py", line 144, in __text_cast
 return func(*self.__args, **self.__kw)
   File "/usr/local/lib/python2.7/dist-
 packages/django/utils/translation/__init__.py", line 83, in ugettext
 return _trans.ugettext(message)
   File "/usr/local/lib/python2.7/dist-
 packages/django/utils/translation/trans_real.py", line 317, in ugettext
 return do_translate(message, 'ugettext')
   File "/usr/local/lib/python2.7/dist-
 packages/django/utils/translation/trans_real.py", line 298, in
 do_translate
 _default = translation(settings.LANGUAGE_CODE)
   File "/usr/local/lib/python2.7/dist-
 packages/django/utils/translation/trans_real.py", line 201, in translation
 default_translation = _fetch(settings.LANGUAGE_CODE)
   File "/usr/local/lib/python2.7/dist-
 packages/django/utils/translation/trans_real.py", line 184, in _fetch
 for app_config in reversed(list(apps.get_app_configs())):
   File "/usr/local/lib/python2.7/dist-packages/django/apps/registry.py",
 line 125, in get_app_configs
 self.check_ready()
   File "/usr/local/lib/python2.7/dist-packages/django/apps/registry.py",
 line 119, in check_ready
 raise RuntimeError("App registry isn't ready yet.")
 RuntimeError: App registry isn't ready yet.
 }}}

 Seems it uses non-lazy ugettext in django/utils/translation/__init__.py.

 If I remove dictionary from the end of _() then this error disappears.

 I'm using Django 1.7b4.

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

Re: [Django] #22895: [PEP8] Acronyms in class names should be uppercase

2014-06-25 Thread Django

#22895: [PEP8] Acronyms in class names should be uppercase
-+-
 Reporter:  bendavis78   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Uncategorized|   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 aaugustin):

 It would have been nice to get this right when we introduced these APIs,
 but now that they exist, changing them is not worth the code churn. -1
 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/068.55f5ff3ae10e10e6eb75a6b72e7ca7ac%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 8dcc78: [1.7.x] Fixed #22814 -- Allowed ISO-8601 [+-]hh ti...

2014-06-25 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 8dcc7810f07e2ce76ebee50c70a5c16f1bc9edec
  
https://github.com/django/django/commit/8dcc7810f07e2ce76ebee50c70a5c16f1bc9edec
  Author: Richard Eames 
  Date:   2014-06-25 (Wed, 25 Jun 2014)

  Changed paths:
M django/utils/dateparse.py
M tests/utils_tests/test_dateparse.py

  Log Message:
  ---
  [1.7.x] Fixed #22814 -- Allowed ISO-8601 [+-]hh timezone format in 
parse_datetime

Backport of 7beaeeed 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/53aa8f397f080_60b2115bd40721254%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22814: parse_datetime can't parse datetimes returned from postgresql

2014-06-25 Thread Django

#22814: parse_datetime can't parse datetimes returned from postgresql
---+-
 Reporter:  Naddiseo   |Owner:  aaugustin
 Type:  Bug|   Status:  closed
Component:  Utilities  |  Version:  1.6
 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 Aymeric Augustin ):

 In [changeset:"8dcc7810f07e2ce76ebee50c70a5c16f1bc9edec"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8dcc7810f07e2ce76ebee50c70a5c16f1bc9edec"
 [1.7.x] Fixed #22814 -- Allowed ISO-8601 [+-]hh timezone format in
 parse_datetime

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

Re: [Django] #22814: parse_datetime can't parse datetimes returned from postgresql

2014-06-25 Thread Django

#22814: parse_datetime can't parse datetimes returned from postgresql
---+-
 Reporter:  Naddiseo   |Owner:  aaugustin
 Type:  Bug|   Status:  closed
Component:  Utilities  |  Version:  1.6
 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):

 I'll do it for 1.7.

 I'd rather not do it in 1.6. I'm wary of making small changes in low level
 utilities in stable versions because people tend to rely on the exact
 behaviour, sometimes after checking the source.

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

Re: [Django] #22898: Specify backend name for custom SQL

2014-06-25 Thread Django

#22898: Specify backend name for custom SQL
-+-
 Reporter:  shaung   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:  custom sql   |  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:   => wontfix


Comment:

 As you can read in the documentation, custom SQL is deprecated.
 https://docs.djangoproject.com/en/dev/howto/initial-data/#providing-
 initial-sql-data

 The recommended path now is to use data migrations, where you should be
 able to consult settings and run (SQL) code accordingly.

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

Re: [Django] #22857: Django 1.7 runserver auto-reload : setting behaviour by extensions

2014-06-25 Thread Django

#22857: Django 1.7 runserver auto-reload : setting behaviour by extensions
-+-
 Reporter:  artscoop |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:
  commands)  |  1.7-beta-2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by artscoop):

 To be done in the next 8 hours, I'll keep you informed.

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

Re: [Django] #22857: Django 1.7 runserver auto-reload : setting behaviour by extensions

2014-06-25 Thread Django

#22857: Django 1.7 runserver auto-reload : setting behaviour by extensions
-+-
 Reporter:  artscoop |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:
  commands)  |  1.7-beta-2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by claudep):

 I'd like at least the reporter to review and check 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/066.18bba4f2d169adc3279bbd8ad8661207%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22734: Move SMTP / email settings to a dictionary

2014-06-25 Thread Django

#22734: Move SMTP / email settings to a dictionary
-+-
 Reporter:  jwa  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Core (Mail)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  settings, email, |  Needs documentation:  0
  mail, smtp |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-

Comment (by claudep):

 Why not, but as you said, it's hard to find real use cases for that
 structure. My current feelings tend to be -0 on that idea.

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

76 matches

Mail list logo