[Django] #22977: No validation error when ForeignKey related_name clashes with manager name.

[Django]

#22977: No validation error when ForeignKey related_name clashes with manager 
name.
+
   Reporter:  russellm  |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Core (System checks)  |Version:  1.6
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 Consider the following model definition:
 {{{
 class Author(models.Model):
 authors = models.Manager()

 name = models.CharField(max_length=100)

 mentor = models.ForeignKey('self', related_name='authors')
 }}}

 The related name on the the foreign key clashes with the manager, so when
 you try to issue a query:
 {{{
 Author.authors.filter(name__startswith='Douglas')
 }}}

 you get an error because "Author.authors has no attribute 'filter'".

 The problem is order dependent; if you define the manager *after* the
 foreign key, you get different errors.

 I haven't checked what errors you get if you just have the default
 Manager, and a related_name of 'objects'.

 There may also be problems if you have a field named 'objects'.

 I suspect this class of problem could be picked up by the system check
 framework.

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

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

Re: [Django] #22969: Forms show_hidden_initial not is_valid() and fix => lost changes in valid fields

[Django]

#22969: Forms show_hidden_initial not is_valid() and fix => lost changes in 
valid
fields
-+-
 Reporter:  dibrovsd@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  Form | Triage Stage:
  show_hidden_initial changed_data   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by dibrovsd@…):

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


Comment:

 Other example

 view
 {{{
 def test(request):
 u""" for debug and test's """

 from django.forms import Form, CharField

 class MyForm(Form):

 req_field = CharField(show_hidden_initial=True, required=True)
 notreq_field = CharField(show_hidden_initial=True, required=False)

 if request.method == 'POST':
 form = MyForm(data=request.POST)
 if form.is_valid():
 for field_name in form.changed_data:
 print field_name
 else:
 form = MyForm()

 return render(request, 'test.html', {'form': form})

 }}}

 template
 {{{
 
 {% csrf_token %}
 {{form.as_p}}
 
 
 }}}

 script:
 1. Load page, set notreq_field = '12' and submit form
 2. Fix error (set req_field = '12') and submit form
 3. console print is "req_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/076.231380c79284081c743f2190e4cb933f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22280: "Conflicting models in application" RuntimeError for same model with different paths

[Django]

#22280: "Conflicting models in application" RuntimeError for same model with
different paths
---+
 Reporter:  blueyed|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by blueyed):

 Thanks for your time, investigation and explanations.

 Just to clarify:

 > For example, why on Earth would you import a model in `manage.py`? I
 don't think it's relevant here, but seriously, I wasted a lot of time just
 to find that out...

 Sorry, that was meant to simulate loading it early, similar to how e.g.
 autocomplete_light's discovery (might) work(s), and I've thought it would
 be necessary to trigger it.

 But just having it in INSTALLED_APPS (and removing it from manage.py) also
 triggers this issue. I have updated the test project accordingly, which is
 now only weird in the regard that it has a `__init__.py` next to
 manage.py.

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

[django/django] 131825: [1.7.x] Renamed an admin_views test to fix orderin...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 1318254669d1b7f8b09c2558e4f187fa1ee2884c
  
https://github.com/django/django/commit/1318254669d1b7f8b09c2558e4f187fa1ee2884c
  Author: Tim Graham 
  Date:   2014-07-07 (Mon, 07 Jul 2014)

  Changed paths:
M tests/admin_views/tests.py

  Log Message:
  ---
  [1.7.x] Renamed an admin_views test to fix ordering issue.

test_i18n_language_non_english_fallback fails if run after
test_L10N_deactivated; the tests can be run in any order after
a5f6cbce07b5f3ab48d931e3fd1883c757fb9b45 but this commit is not
in stable/1.7.x.


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

[django/django] 1326cd: [1.7.x] Removed unnecessary directory in dispatch ...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 1326cd28d09f4e657c6ed3af9a23ea6a356d0708
  
https://github.com/django/django/commit/1326cd28d09f4e657c6ed3af9a23ea6a356d0708
  Author: Tim Graham 
  Date:   2014-07-07 (Mon, 07 Jul 2014)

  Changed paths:
A tests/dispatch/tests.py
R tests/dispatch/tests/__init__.py
R tests/dispatch/tests/test_dispatcher.py

  Log Message:
  ---
  [1.7.x] Removed unnecessary directory in dispatch tests.

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

[django/django] 136a3f: Removed unnecessary directory in dispatch tests.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 136a3ffe21988d49e443867d129cc01fb62b34cd
  
https://github.com/django/django/commit/136a3ffe21988d49e443867d129cc01fb62b34cd
  Author: Tim Graham 
  Date:   2014-07-07 (Mon, 07 Jul 2014)

  Changed paths:
A tests/dispatch/tests.py
R tests/dispatch/tests/__init__.py
R tests/dispatch/tests/test_dispatcher.py

  Log Message:
  ---
  Removed unnecessary directory in dispatch tests.


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

[django/django] fddd95: Fixed flake8 errors.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: fddd95254e3ccd8c6836e56b8f5481a0a13568bd
  
https://github.com/django/django/commit/fddd95254e3ccd8c6836e56b8f5481a0a13568bd
  Author: Tim Graham 
  Date:   2014-07-07 (Mon, 07 Jul 2014)

  Changed paths:
M django/utils/autoreload.py
M tests/utils_tests/test_autoreload.py

  Log Message:
  ---
  Fixed flake8 errors.


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

[django/django] 0100af: [1.7.x] Fixed flake8 errors.

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 0100afb01399e4605a68daec0e7b447e163e0b1d
  
https://github.com/django/django/commit/0100afb01399e4605a68daec0e7b447e163e0b1d
  Author: Tim Graham 
  Date:   2014-07-07 (Mon, 07 Jul 2014)

  Changed paths:
M django/utils/autoreload.py
M tests/utils_tests/test_autoreload.py

  Log Message:
  ---
  [1.7.x] Fixed flake8 errors.

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

Re: [Django] #22909: Fix camelCase test names

[Django]

#22909: Fix camelCase test names
--+
 Reporter:  timo  |Owner:  brylie
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Uncategorized |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"28962c57f3f2b4543cd67d55ca635e9198f585dd"]:
 {{{
 #!CommitTicketReference repository=""
 revision="28962c57f3f2b4543cd67d55ca635e9198f585dd"
 [1.7.x] Fixed #22909 -- Removed camelCasing in some tests.

 Thanks brylie.

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

Re: [Django] #22909: Fix camelCase test names

[Django]

#22909: Fix camelCase test names
--+
 Reporter:  timo  |Owner:  brylie
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Uncategorized |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"89b9e6e5d68297e7fe10baea6abcd96e24de0e09"]:
 {{{
 #!CommitTicketReference repository=""
 revision="89b9e6e5d68297e7fe10baea6abcd96e24de0e09"
 Fixed #22909 -- Removed camelCasing in some tests.

 Thanks brylie.
 }}}

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

[django/django] 89b9e6: Fixed #22909 -- Removed camelCasing in some tests.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 89b9e6e5d68297e7fe10baea6abcd96e24de0e09
  
https://github.com/django/django/commit/89b9e6e5d68297e7fe10baea6abcd96e24de0e09
  Author: Tim Graham 
  Date:   2014-07-07 (Mon, 07 Jul 2014)

  Changed paths:
M tests/admin_custom_urls/tests.py
M tests/admin_views/tests.py
M tests/admin_widgets/tests.py
M tests/bug639/tests.py
M tests/conditional_processing/tests.py
M tests/dispatch/tests/test_dispatcher.py
M tests/generic_inline_admin/tests.py
M tests/nested_foreign_keys/tests.py
M tests/raw_query/tests.py
M tests/utils_tests/test_http.py
M tests/view_tests/tests/test_i18n.py

  Log Message:
  ---
  Fixed #22909 -- Removed camelCasing in some tests.

Thanks brylie.


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

[django/django] 28962c: [1.7.x] Fixed #22909 -- Removed camelCasing in som...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 28962c57f3f2b4543cd67d55ca635e9198f585dd
  
https://github.com/django/django/commit/28962c57f3f2b4543cd67d55ca635e9198f585dd
  Author: Tim Graham 
  Date:   2014-07-07 (Mon, 07 Jul 2014)

  Changed paths:
M tests/admin_custom_urls/tests.py
M tests/admin_views/tests.py
M tests/admin_widgets/tests.py
M tests/bug639/tests.py
M tests/conditional_processing/tests.py
M tests/dispatch/tests/test_dispatcher.py
M tests/generic_inline_admin/tests.py
M tests/nested_foreign_keys/tests.py
M tests/raw_query/tests.py
M tests/utils_tests/test_http.py
M tests/view_tests/tests/test_i18n.py

  Log Message:
  ---
  [1.7.x] Fixed #22909 -- Removed camelCasing in some tests.

Thanks brylie.

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

Re: [Django] #22821: DjangoJSONEncoder no longer supports simplejson

[Django]

#22821: DjangoJSONEncoder no longer supports simplejson
-+-
 Reporter:  Keryn Knight |Owner:  nobody
   |   Status:  closed
 Type:  New feature  |  Version:  master
Component:  Core |   Resolution:  wontfix
  (Serialization)| Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

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

[django/django] c379fc: [1.7.x] Fixed #22942 -- Noted that __init__.py fil...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: c379fc4eec885101ac30e0505f967048c869e630
  
https://github.com/django/django/commit/c379fc4eec885101ac30e0505f967048c869e630
  Author: Tim Graham 
  Date:   2014-07-07 (Mon, 07 Jul 2014)

  Changed paths:
M docs/howto/custom-management-commands.txt

  Log Message:
  ---
  [1.7.x] Fixed #22942 -- Noted that __init__.py files are required for 
management command detection.

Thanks Diego Cerdán for the suggestion.

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

Re: [Django] #22942: Custom django-admin commands - __init__.py in directories

[Django]

#22942: Custom django-admin commands - __init__.py in directories
-+-
 Reporter:  Diego Cerdán |Owner:  nobody
  |   Status:  closed
 Type:   |  Version:  master
  Cleanup/optimization   |   Resolution:  fixed
Component:  Documentation| Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"837cad0f6242f5292b8a4811fc48fbfbefe92a47"]:
 {{{
 #!CommitTicketReference repository=""
 revision="837cad0f6242f5292b8a4811fc48fbfbefe92a47"
 [1.6.x] Fixed #22942 -- Noted that __init__.py files are required for
 management command detection.

 Thanks Diego Cerdán for the suggestion.

 Backport of 54546cee88 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/093.d4beb481e204c760ed2e9c120fe802d6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 837cad: [1.6.x] Fixed #22942 -- Noted that __init__.py fil...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 837cad0f6242f5292b8a4811fc48fbfbefe92a47
  
https://github.com/django/django/commit/837cad0f6242f5292b8a4811fc48fbfbefe92a47
  Author: Tim Graham 
  Date:   2014-07-07 (Mon, 07 Jul 2014)

  Changed paths:
M docs/howto/custom-management-commands.txt

  Log Message:
  ---
  [1.6.x] Fixed #22942 -- Noted that __init__.py files are required for 
management command detection.

Thanks Diego Cerdán for the suggestion.

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

Re: [Django] #22942: Custom django-admin commands - __init__.py in directories

[Django]

#22942: Custom django-admin commands - __init__.py in directories
-+-
 Reporter:  Diego Cerdán |Owner:  nobody
  |   Status:  closed
 Type:   |  Version:  master
  Cleanup/optimization   |   Resolution:  fixed
Component:  Documentation| Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"c379fc4eec885101ac30e0505f967048c869e630"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c379fc4eec885101ac30e0505f967048c869e630"
 [1.7.x] Fixed #22942 -- Noted that __init__.py files are required for
 management command detection.

 Thanks Diego Cerdán for the suggestion.

 Backport of 54546cee88 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/093.bb743f47fd491cb9a6bad24224c44724%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22942: Custom django-admin commands - __init__.py in directories

[Django]

#22942: Custom django-admin commands - __init__.py in directories
-+-
 Reporter:  Diego Cerdán |Owner:  nobody
  |   Status:  closed
 Type:   |  Version:  master
  Cleanup/optimization   |   Resolution:  fixed
Component:  Documentation| Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:   |  Needs documentation:  0
Has patch:  0|  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:"54546cee88f1db4e7e0ad75ebb9672c118b2236c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="54546cee88f1db4e7e0ad75ebb9672c118b2236c"
 Fixed #22942 -- Noted that __init__.py files are required for management
 command detection.

 Thanks Diego Cerdán for the suggestion.
 }}}

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

[django/django] 54546c: Fixed #22942 -- Noted that __init__.py files are r...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 54546cee88f1db4e7e0ad75ebb9672c118b2236c
  
https://github.com/django/django/commit/54546cee88f1db4e7e0ad75ebb9672c118b2236c
  Author: Tim Graham 
  Date:   2014-07-07 (Mon, 07 Jul 2014)

  Changed paths:
M docs/howto/custom-management-commands.txt

  Log Message:
  ---
  Fixed #22942 -- Noted that __init__.py files are required for management 
command detection.

Thanks Diego Cerdán for the suggestion.


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

Re: [Django] #22942: Custom django-admin commands - __init__.py in directories

[Django]

#22942: Custom django-admin commands - __init__.py in directories
-+-
 Reporter:  Diego Cerdán |Owner:  nobody
  |   Status:  new
 Type:   |  Version:  master
  Cleanup/optimization   |   Resolution:
Component:  Documentation| Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

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


Comment:

 Reported again in #22974 so I'm going to add some emphasis about this.

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

Re: [Django] #22974: howto-custom-management-commands: manage.py is completely changed

[Django]

#22974: howto-custom-management-commands: manage.py is completely changed
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.6
 Severity:  Normal |   Resolution:  duplicate
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timo):

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


Comment:

 Duplicate of #22942.

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

Re: [Django] #22976: EmailField: Maximum RFC-compliant length should be 320 characters

[Django]

#22976: EmailField: Maximum RFC-compliant length should be 320 characters
+--
 Reporter:  a.lloyd.flanagan@…  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Documentation   |  Version:  master
 Severity:  Normal  |   Resolution:  invalid
 Keywords:  email limit | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--

Comment (by a.lloyd.flanagan@…):

 Whoops, my mistake for not checking the errata closely. Thanks for the
 info.

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

Re: [Django] #22976: EmailField: Maximum RFC-compliant length should be 320 characters

[Django]

#22976: EmailField: Maximum RFC-compliant length should be 320 characters
+--
 Reporter:  a.lloyd.flanagan@…  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Documentation   |  Version:  master
 Severity:  Normal  |   Resolution:  invalid
 Keywords:  email limit | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--
Changes (by timo):

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


Comment:

 Yes, it was initially 320, but subsequently revised. Please see
 [http://www.rfc-editor.org/errata_search.php?rfc=3696&eid=1690 this
 errata].

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

[Django] #22976: EmailField: Maximum RFC-compliant length should be 320 characters

[Django]

#22976: EmailField: Maximum RFC-compliant length should be 320 characters
+-
 Reporter:  a.lloyd.flanagan@…  |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Documentation   |Version:  master
 Severity:  Normal  |   Keywords:  email limit
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  1   |  UI/UX:  0
+-
 The documentation for model.EmailField states

 Incompliance to RFCs

 The default 75 character max_length is not capable of storing all
 possible RFC3696/5321-compliant
 email addresses. In order to store all possible valid email addresses,
 a max_length of 254 is
 required.

 In fact, however, RFC3696 states of email address maximum length:

 That limit is a maximum of 64 characters (octets)
 in the "local part" (before the "@") and a maximum of 255 characters
 (octets) in the domain part (after the "@") for a total length of 320
 characters.

 I note the same statement regarding the 254-character limit in the Release
 Notes document for version 1.8.

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

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

Re: [Django] #22974: howto-custom-management-commands: manage.py is completely changed

[Django]

#22974: howto-custom-management-commands: manage.py is completely changed
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  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 anonymous):

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


Comment:

 Replying to [ticket:22974 anonymous]:
 > I don't know how to add a custom command based on all docs from 1.6 to
 present.   manage.py looks completely different and does not display the
 command created under /management/commands
 >
 > https://docs.djangoproject.com/en/1.6/howto/custom-management-commands
 /#howto-custom-management-commands

 I found the solution: there must be __init__.py files (empty) in both
 management and commands directories.  The documents could state this
 better.  Thanks

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

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

[Django] #22975: Cannot rename model keeping db table name

[Django]

#22975: Cannot rename model keeping db table name
+
 Reporter:  rhcarvalho  |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  1.7-rc-1
 Severity:  Normal  |   Keywords:  migrations
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 Django migrations do not work when you rename a model keeping the db table
 name. For instance:

 # -- models.py --
 class Book(models.Model):
 name = models.CharField()
 class Meta:
 db_table = "books"


 # -- models.py  after renaming model --
 class AwesomeBook(models.Model):
 name = models.CharField()
 class Meta:
 db_table = "books"


 The migration system ends up making an operational error by trying to
 rename the table from `books` to `books`, when the rename is unnecessary.

 
https://github.com/django/django/commit/fddc5957c53bd654312c4a238a8cdcfe5f4ef4cc#commitcomment-6916125

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

[Django] #22974: howto-custom-management-commands: manage.py is completely changed

[Django]

#22974: howto-custom-management-commands: manage.py is completely changed
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I don't know how to add a custom command based on all docs from 1.6 to
 present.   manage.py looks completely different and does not display the
 command created under /management/commands

 https://docs.djangoproject.com/en/1.6/howto/custom-management-commands
 /#howto-custom-management-commands

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

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

[Django] #22973: cannot get SQL code of empty queryset

[Django]

#22973: cannot get SQL code of empty queryset
--+
 Reporter:  emanuele.paolini@…|  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.5
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Suppose you have defined any Model class.

 The code:
 {{{
 str(Model.objects.filter(id__in=[]).query)

 }}}

 raises an exception:


 {{{
 Traceback (most recent call last):
   File "", line 1, in 
   File "/usr/local/lib/python2.7/dist-
 packages/django/db/models/sql/query.py", line 174, in __str__
 sql, params = self.sql_with_params()
   File "/usr/local/lib/python2.7/dist-
 packages/django/db/models/sql/query.py", line 182, in sql_with_params
 return self.get_compiler(DEFAULT_DB_ALIAS).as_sql()
   File "/usr/local/lib/python2.7/dist-
 packages/django/db/models/sql/compiler.py", line 85, in as_sql
 where, w_params = self.query.where.as_sql(qn=qn,
 connection=self.connection)
   File "/usr/local/lib/python2.7/dist-
 packages/django/db/models/sql/where.py", line 126, in as_sql
 raise EmptyResultSet
 EmptyResultSet

 }}}

 instead this works fine:

 {{{
 str(Model.objects.none().query)
 }}}

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

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

Re: [Django] #22972: HashedFilesMixin.patterns should limit URL matches to their respective filetypes

[Django]

#22972: HashedFilesMixin.patterns should limit URL matches to their respective
filetypes
-+-
 Reporter:  alex.ehlke@… |Owner:  aehlke
 Type:  Uncategorized|   Status:  assigned
Component:  contrib.staticfiles  |  Version:  1.7-rc-1
 Severity:  Normal   |   Resolution:
 Keywords:  HashedFilesMixin | Triage Stage:
  CachedFilesMixin staticfiles   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aehlke):

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


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

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

Re: [Django] #22972: HashedFilesMixin.patterns should limit URL matches to their respective filetypes

[Django]

#22972: HashedFilesMixin.patterns should limit URL matches to their respective
filetypes
-+-
 Reporter:  alex.ehlke@… |Owner:  aehlke
 Type:  Uncategorized|   Status:  assigned
Component:  contrib.staticfiles  |  Version:  1.7-rc-1
 Severity:  Normal   |   Resolution:
 Keywords:  HashedFilesMixin | Triage Stage:
  CachedFilesMixin staticfiles   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aehlke):

 I'm preparing a test case and patch.

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

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

Re: [Django] #22922: Add a better error messsage or an FAQ entry for InvalidBasesError

[Django]

#22922: Add a better error messsage or an FAQ entry for InvalidBasesError
--+
 Reporter:  bufke |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  1.7-rc-1
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by CollinAnderson):

 * cc: cmawebsite@… (added)


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

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

Re: [Django] #22966: Documentation on upgrading Django to a newer version should link to all release notes regardless of what version of the docs you view

[Django]

#22966: Documentation on upgrading Django to a newer version should link to all
release notes regardless of what version of the docs you view
-+-
 Reporter:  haimunt@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  documentation,   | Triage Stage:  Accepted
  release notes, confusing   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by Tim Graham ):

 In [changeset:"cf9e33f930be9032f68e12301e6d1f9f9d139f3c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cf9e33f930be9032f68e12301e6d1f9f9d139f3c"
 [1.7.x] Fixed #22966 -- Clarified which release notes appear for each doc
 version.

 Thanks haimunt at yahoo.com for the suggestion.

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

[django/django] cf9e33: [1.7.x] Fixed #22966 -- Clarified which release no...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: cf9e33f930be9032f68e12301e6d1f9f9d139f3c
  
https://github.com/django/django/commit/cf9e33f930be9032f68e12301e6d1f9f9d139f3c
  Author: Tim Graham 
  Date:   2014-07-07 (Mon, 07 Jul 2014)

  Changed paths:
M docs/releases/index.txt

  Log Message:
  ---
  [1.7.x] Fixed #22966 -- Clarified which release notes appear for each doc 
version.

Thanks haimunt at yahoo.com for the suggestion.

Backport of e6b3d6c22f from master


  Commit: 5acb0a913997aea83dbbf272bcc97f67a25a32c4
  
https://github.com/django/django/commit/5acb0a913997aea83dbbf272bcc97f67a25a32c4
  Author: Collin Anderson 
  Date:   2014-07-07 (Mon, 07 Jul 2014)

  Changed paths:
M docs/ref/settings.txt

  Log Message:
  ---
  [1.7.x] Fixed a few PEP8 errors in settings doc.

Backport of 2c1384fbac from master


Compare: https://github.com/django/django/compare/1bb8ccdb9e70...5acb0a913997

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

Re: [Django] #22966: Documentation on upgrading Django to a newer version should link to all release notes regardless of what version of the docs you view

[Django]

#22966: Documentation on upgrading Django to a newer version should link to all
release notes regardless of what version of the docs you view
-+-
 Reporter:  haimunt@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  documentation,   | Triage Stage:  Accepted
  release notes, confusing   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by Tim Graham ):

 In [changeset:"85f9745807ea0042225aaf4472fb63a00f3e2bcc"]:
 {{{
 #!CommitTicketReference repository=""
 revision="85f9745807ea0042225aaf4472fb63a00f3e2bcc"
 [1.6.x] Fixed #22966 -- Clarified which release notes appear for each doc
 version.

 Thanks haimunt at yahoo.com for the suggestion.

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

Re: [Django] #22966: Documentation on upgrading Django to a newer version should link to all release notes regardless of what version of the docs you view

[Django]

#22966: Documentation on upgrading Django to a newer version should link to all
release notes regardless of what version of the docs you view
-+-
 Reporter:  haimunt@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  documentation,   | Triage Stage:  Accepted
  release notes, confusing   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by Tim Graham ):

 In [changeset:"ddc715edd3e473a995f7f8a1b8277be33324641f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ddc715edd3e473a995f7f8a1b8277be33324641f"
 [1.5.x] Fixed #22966 -- Clarified which release notes appear for each doc
 version.

 Thanks haimunt at yahoo.com for the suggestion.

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

[django/django] ddc715: [1.5.x] Fixed #22966 -- Clarified which release no...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: ddc715edd3e473a995f7f8a1b8277be33324641f
  
https://github.com/django/django/commit/ddc715edd3e473a995f7f8a1b8277be33324641f
  Author: Tim Graham 
  Date:   2014-07-07 (Mon, 07 Jul 2014)

  Changed paths:
M docs/releases/index.txt

  Log Message:
  ---
  [1.5.x] Fixed #22966 -- Clarified which release notes appear for each doc 
version.

Thanks haimunt at yahoo.com for the suggestion.

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

[django/django] 85f974: [1.6.x] Fixed #22966 -- Clarified which release no...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 85f9745807ea0042225aaf4472fb63a00f3e2bcc
  
https://github.com/django/django/commit/85f9745807ea0042225aaf4472fb63a00f3e2bcc
  Author: Tim Graham 
  Date:   2014-07-07 (Mon, 07 Jul 2014)

  Changed paths:
M docs/releases/index.txt

  Log Message:
  ---
  [1.6.x] Fixed #22966 -- Clarified which release notes appear for each doc 
version.

Thanks haimunt at yahoo.com for the suggestion.

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

Re: [Django] #22966: Documentation on upgrading Django to a newer version should link to all release notes regardless of what version of the docs you view

[Django]

#22966: Documentation on upgrading Django to a newer version should link to all
release notes regardless of what version of the docs you view
-+-
 Reporter:  haimunt@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  documentation,   | Triage Stage:  Accepted
  release notes, confusing   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"e6b3d6c22f5c638b08f653bada4d51b47174852c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e6b3d6c22f5c638b08f653bada4d51b47174852c"
 Fixed #22966 -- Clarified which release notes appear for each doc version.

 Thanks haimunt at yahoo.com for the suggestion.
 }}}

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

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

[django/django] e6b3d6: Fixed #22966 -- Clarified which release notes appe...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e6b3d6c22f5c638b08f653bada4d51b47174852c
  
https://github.com/django/django/commit/e6b3d6c22f5c638b08f653bada4d51b47174852c
  Author: Tim Graham 
  Date:   2014-07-07 (Mon, 07 Jul 2014)

  Changed paths:
M docs/releases/index.txt

  Log Message:
  ---
  Fixed #22966 -- Clarified which release notes appear for each doc version.

Thanks haimunt at yahoo.com for the suggestion.


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

[django/django] 2c1384: Fixed a few PEP8 errors in settings doc.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2c1384fbacfdea78b5acc3e652c7bd6422fea1ef
  
https://github.com/django/django/commit/2c1384fbacfdea78b5acc3e652c7bd6422fea1ef
  Author: Collin Anderson 
  Date:   2014-07-06 (Sun, 06 Jul 2014)

  Changed paths:
M docs/ref/settings.txt

  Log Message:
  ---
  Fixed a few PEP8 errors in settings 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/53baf4eb71c02_3d30775d44504b8%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #9104: FieldDoesNotExist is defined in "confusing" place.

[Django]

#9104: FieldDoesNotExist is defined in "confusing" place.
-+-
 Reporter:  telenieko|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Core (Other) |   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:   |  decision needed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by wraus):

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


Comment:

 I'd like to reopen this just to hopefully have this oddity resolved.

 One of the comments was talking about use cases, and I wanted to give the
 use case that I'm using for it to hopefully sway opinion a bit on making
 this simple change.

 I'm working on a template tag that will allow me to iterate over a list of
 a model's fields / attributes and output it as a table. I want to grab the
 verbose_name of the field, given the field's name, and to do so, I get
 obj._meta.get_field(field_name). However, I also want the option to
 reference class attributes and functions, and obviously if I reference a
 function or attribute, there is no matching field. Thus, I need to call
 get_field, and catch FieldDoesNotExist to handle it as a function /
 attribute and get a separate label.

 There doesn't seem to be a more "obvious" way to do this, and I ran into
 the issue of trying to find this oddly placed exception. I understand that
 moving the exception would be a serious change, but hopefully making it
 importable via django.core.exceptions will resolve this inconvenience.

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

Re: [Django] #14787: Upload handler should pass errors on to forms.FileField

[Django]

#14787: Upload handler should pass errors on to forms.FileField
-+-
 Reporter:  intgr|Owner:
 Type:  New feature  |  anubhav9042
Component:  File |   Status:  assigned
  uploads/storage|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by anubhav9042):

 OK. So we are down to that maximum size issue itself.
 Can you please post your replies on both the points on ML, so that when
 someone sees he knows about these things as well.

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

Re: [Django] #14787: Upload handler should pass errors on to forms.FileField

[Django]

#14787: Upload handler should pass errors on to forms.FileField
-+-
 Reporter:  intgr|Owner:
 Type:  New feature  |  anubhav9042
Component:  File |   Status:  assigned
  uploads/storage|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timo):

 It's a server configuration issue that should be fixed by the person
 deploying the site, not something an end user should get an error about.

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

Re: [Django] #14787: Upload handler should pass errors on to forms.FileField

[Django]

#14787: Upload handler should pass errors on to forms.FileField
-+-
 Reporter:  intgr|Owner:
 Type:  New feature  |  anubhav9042
Component:  File |   Status:  assigned
  uploads/storage|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by anubhav9042):

 What I wanted to say is we can inform the user about the problem in a
 better way than just adding in the docs by raising a proper error in
 `to_python()` itself as we have file_name there so we could check the
 encoding.

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

Re: [Django] #22972: HashedFilesMixin.patterns should limit URL matches to their respective filetypes (was: HashedFilesMixin)

[Django]

#22972: HashedFilesMixin.patterns should limit URL matches to their respective
filetypes
-+-
 Reporter:  alex.ehlke@… |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  contrib.staticfiles  |  Version:  1.7-rc-1
 Severity:  Normal   |   Resolution:
 Keywords:  HashedFilesMixin | Triage Stage:
  CachedFilesMixin staticfiles   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by anonymous):

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

Re: [Django] #14787: Upload handler should pass errors on to forms.FileField

[Django]

#14787: Upload handler should pass errors on to forms.FileField
-+-
 Reporter:  intgr|Owner:
 Type:  New feature  |  anubhav9042
Component:  File |   Status:  assigned
  uploads/storage|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timo):

 What's the file name encoding issue you mentioned in the mailing list
 post? Is it different from #17686?

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

[Django] #22972: HashedFilesMixin

[Django]

#22972: HashedFilesMixin
-+-
 Reporter:   |  Owner:  nobody
  alex.ehlke@…   | Status:  new
 Type:   |Version:  1.7-rc-1
  Uncategorized  |   Keywords:  HashedFilesMixin CachedFilesMixin
Component:   |  staticfiles
  contrib.staticfiles|  Has patch:  0
 Severity:  Normal   |  UI/UX:  0
 Triage Stage:   |
  Unreviewed |
Easy pickings:  0|
-+-
 {{{HashedFilesMixin}}} contains a {{{patterns}}} property which maps file
 extensions to regex patterns. This works great for the default case that
 Django ships with  {{{"*.css"}}} as the only filetype, but results in
 surprising behavior once extended with multiple filetypes. I would expect
 the regex patterns to only apply to the filetype they're categorized
 under, but once I added {{{"*.js"}}} to {{{patterns}}} (via subclassing),
 the CSS rules also applied to my JS files.

 My use-case of extending this is to add URL rewriting to JS source map
 references, e.g. {{{//# sourceMappingURL=foo.js.map }}} which can appear
 at the end of JS files. I need to be able to rewrite these URLs in the
 same way that Django's staticfiles can rewrite URLs in CSS, for e.g.
 adding hashes to filenames.

 Once I tried extending {{{patterns}}} with this:
 {{{
 patterns = HashedFilesMixin.patterns + (
 ("*.js", (
 (r"""(//# sourceMappingURL=(\s*))""", """//#
 sourceMappingURL=%s"""),
 )),
 )
 }}}
 The surprising and broken behavior was that Django tried to rewrite "URLs"
 for this JS (from Backbone.js): {{{this.loadUrl(window.location.hash)}}},
 which matched the CSS pattern for rewriting {{{url(foo)}}} because the
 regex patterns are case-insensitive.

 This also applies to the previous {{{CachedFilesMixin}}} from before 1.7.

 Please let me know if a fix for this would be accepted, and I'll put
 together a test case and patch.

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

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

Re: [Django] #2445: [patch] allow callable values for limit_choices_to

[Django]

#2445: [patch] allow callable values for limit_choices_to
-+-
 Reporter:  michael@…|Owner:  Tim
 Type:  New feature  |  Graham 
Component:  Core (Other) |   Status:  closed
 Severity:  Normal   |  Version:  master
 Keywords:  sprint2013   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by timo):

 Not really, the `request` is generally not available in a form.

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

Re: [Django] #2445: [patch] allow callable values for limit_choices_to

[Django]

#2445: [patch] allow callable values for limit_choices_to
-+-
 Reporter:  michael@…|Owner:  Tim
 Type:  New feature  |  Graham 
Component:  Core (Other) |   Status:  closed
 Severity:  Normal   |  Version:  master
 Keywords:  sprint2013   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by blueyed):

 Thanks! This looks very useful.

 I wonder if it could be changed to pass along any `request` object to the
 callback, which would allow to look at `request.user` and then limit the
 choices to objects that the current user owns?

 From what I understand the `request` object may not be available, e.g.
 when used via management commands, where `None` would be passed to the
 callback then.

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

Re: [Django] #14787: Upload handler should pass errors on to forms.FileField

[Django]

#14787: Upload handler should pass errors on to forms.FileField
-+-
 Reporter:  intgr|Owner:
 Type:  New feature  |  anubhav9042
Component:  File |   Status:  assigned
  uploads/storage|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by anubhav9042):

 I did mention what I want to do, i.e. including the new attribute
 `max_size`, though I will pay more attention to the subject from next time
 onwards.
 Thanks.

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

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

Re: [Django] #22971: Can't receive file with non-ascii filename according to rfc2388

[Django]

#22971: Can't receive file with non-ascii filename according to rfc2388
---+--
 Reporter:  homm   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  HTTP handling  |  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 homm):

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


Comment:

 Related requests ticket:
 https://github.com/kennethreitz/requests/issues/2117

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

[Django] #22971: Can't receive file with non-ascii filename according to rfc2388

[Django]

#22971: Can't receive file with non-ascii filename according to rfc2388
---+
 Reporter:  homm   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  HTTP handling  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Requests, popular Python library, starting from version 2.0 sends files
 with non-ascii characters in filename in full compliance with rfc2388:

 The original local file name may be supplied as well, either as a
 "filename" parameter either of the "content-disposition: form-data"
 header or, in the case of multiple files, in a "content-disposition:
 file" header of the subpart. The sending application MAY supply a
 file name; if the file name of the sender's operating system is not
 in US-ASCII, the file name might be approximated, or encoded using
 the method of RFC 2231.

 Where RFC 2231 defines attributes with * char. And requests uses such
 attribute name to send non-ascii file names.

 {{{
 # requests 1.2.3
 >>> requests.post('http://ya.ru', files={'file': (u'файл',
 '123')}).request.body
 --cb90e5c32429403b99966534716cda56
 Content-Disposition: form-data; name="file"; filename="файл"
 Content-Type: application/octet-stream

 123
 --cb90e5c32429403b99966534716cda56--


 # requests 2.0
 >>> requests.post('http://ya.ru', files={'file': (u'файл',
 '123')}).request.body
 --40f2f1873ec843598773fe150b4f783a
 Content-Disposition: form-data; name="file";
 filename*=utf-8''%D1%84%D0%B0%D0%B9%D0%BB

 123
 --40f2f1873ec843598773fe150b4f783a--
 }}}

 But Django doesn't recognize such files and puts raw files content in
 `request.POST` instead of population `request.FILES`.

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

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

Re: [Django] #22280: "Conflicting models in application" RuntimeError for same model with different paths

[Django]

#22280: "Conflicting models in application" RuntimeError for same model with
different paths
---+
 Reporter:  blueyed|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by aaugustin):

 * keywords:  app-loading =>
 * component:  Core (Other) => Testing framework
 * stage:  Unreviewed => Accepted


Comment:

 Thanks for the example project. I ran it and reproduced the error:

 {{{
 RuntimeError: Conflicting 'model' models in application 'app':  and .
 }}}

 It's pretty clear in this error that the same `Model` class was imported
 through two different Python paths: `app.models` and `proot.app.models`.
 That is always an error and it's purposefully forbidden in Django 1.7.
 However, the reasons why this happens aren't obvious.

 If you aren't convinced that it's always an error, learn about [http
 ://python-
 notes.curiousefficiency.org/en/latest/python_concepts/import_traps.html
 #the-double-import-trap the double import trap] and come back.

 With `python -Wall` I got this warning:

 {{{
 test-django-issue-22280/proot/app/models.py:3: RemovedInDjango19Warning:
 Model class app.models.Model doesn't declare an explicit app_label and
 either isn't in an application in INSTALLED_APPS or else was imported
 before its application was loaded. This will no longer be supported in
 Django 1.9.
 }}}

 It's referring to `app.models.Model` which is the expected path. So I went
 ahead and added `'app'` to `INSTALLED_APPS`.

 Then I got this warning:

 {{{
 test-django-issue-22280/proot/app/models.py:3: RemovedInDjango19Warning:
 Model class proot.app.models.Model doesn't declare an explicit app_label
 and either isn't in an application in INSTALLED_APPS or else was imported
 before its application was loaded. This will no longer be supported in
 Django 1.9.
 }}}

 Note that it's referring to `proot.app.models.Model` now which is
 unexpected.

 To debug this further, I added `from pprint import pprint; import sys;
 pprint(sys.path)` in `app/models.py`.

 As expected, that shows that the module is imported twice. The first time,
 `sys.path` contains `test-django-issue-22280/proot`, and then venv and
 system stuff. The second time, it contains `test-django-issue-22280`,
 `test-django-issue-22280/proot`, and the same venv and system stuff.

 That's where the `__init__.py` begins to make a difference. Once `test-
 django-issue-22280` is added to `sys.path`, the `__init__.py` makes in
 possible to import Python objects as `proot.xxx`, and the double import
 trap appears.

 So the question becomes -- what added `test-django-issue-22280` on
 `sys.path`? I think it happens somewhere in `DiscoverRunner.build_suite`.
 I don't understand that code very well.

 I'm going to stop there for now because I don't think it's an app-loading
 regression. App-loading just raised an error, as intended, in one of the
 situations it was designed to prevent.

 Considering that you're the only person to have complained about this, and
 that your example contains fairly weird stuff, I'm not marking this as a
 release blocker. For example, why on Earth would you import a model in
 `manage.py`? I don't think it's relevant here, but seriously, I wasted a
 lot of time just to find that 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/065.03115cd31a3fc8a680ab32f9d475a545%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #14787: Upload handler should pass errors on to forms.FileField

[Django]

#14787: Upload handler should pass errors on to forms.FileField
-+-
 Reporter:  intgr|Owner:
 Type:  New feature  |  anubhav9042
Component:  File |   Status:  assigned
  uploads/storage|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timo):

 A couple comments on the post:

 1. It's better to make a proposal than ask "what to do" or "how to solve a
 ticket." What do you think should be done? If you don't care, then find
 I'd find something else to work on.

 2. A subject that includes a description of the item instead of "Decision
 for ticket #14787" is more likely to get interested people to read 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/063.d074a114e9662205d4be49218dba8a40%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22928: Provide a option to generate the full settings.py instead of the short, minimal one

[Django]

#22928: Provide a option to generate the full settings.py instead of the short,
minimal one
-+--
 Reporter:  guruprasad   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Uncategorized|  Version:  1.6
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  django-admin.py  | 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:   => wontfix


Comment:

 Yes, please use the mailing list. I see other core devs referenced in the
 commit message for 3f1c7b70537330435e2ec2fca9550f7b7fa4372e where this
 change was made, so at least a couple other people thought it was a good
 thing to do.

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

Re: [Django] #22280: "Conflicting models in application" RuntimeError for same model with different paths

[Django]

#22280: "Conflicting models in application" RuntimeError for same model with
different paths
--+--
 Reporter:  blueyed   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  master
 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 blueyed):

 > Your examples look like the directory containing the outer "project" or
 "proot" directory is on PYTHONPATH.

 No. This is a new shell, and I have created the virtualenv with
 `virtualenv venv` explicitly.

 > The __init__.py is a red herring. It just makes the error more
 confusing.

 No, with __init__.py the tests fail, and removing it make them run -
 because then `/tmp/test-django-issue-22280` gets not added to sys.path and
 the model/app gets not imported with different paths.

 I have added a Makefile to the test repo. You should be able to reproduce
 it with:
 {{{
 1. git clone https://github.com/blueyed/test-django-issue-22280
 2. cd test-django-issue-22280
 3. make test
 }}}

 It uses the `1.7c1` tarball. You may want to use a local checkout instead.

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

Re: [Django] #14787: Upload handler should pass errors on to forms.FileField

[Django]

#14787: Upload handler should pass errors on to forms.FileField
-+-
 Reporter:  intgr|Owner:
 Type:  New feature  |  anubhav9042
Component:  File |   Status:  assigned
  uploads/storage|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by anubhav9042):

 Here: https://groups.google.com/forum/#!topic/django-
 developers/4fbcsPhuuR8

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

Re: [Django] #22966: Documentation on upgrading Django to a newer version should link to all release notes regardless of what version of the docs you view

[Django]

#22966: Documentation on upgrading Django to a newer version should link to all
release notes regardless of what version of the docs you view
-+-
 Reporter:  haimunt@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  documentation,   | Triage Stage:  Accepted
  release notes, confusing   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by timo):

 I can backport it to older release, I just wanted to upload a patch first
 to make sure it looked okay to you.

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

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

Re: [Django] #22966: Documentation on upgrading Django to a newer version should link to all release notes regardless of what version of the docs you view

[Django]

#22966: Documentation on upgrading Django to a newer version should link to all
release notes regardless of what version of the docs you view
-+-
 Reporter:  haimunt@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  documentation,   | Triage Stage:  Accepted
  release notes, confusing   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by anonymous):

 Thanks. Does that note appear in all older versions of the docs or just
 the latest?

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

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

Re: [Django] #22966: Documentation on upgrading Django to a newer version should link to all release notes regardless of what version of the docs you view

[Django]

#22966: Documentation on upgrading Django to a newer version should link to all
release notes regardless of what version of the docs you view
-+-
 Reporter:  haimunt@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  documentation,   | Triage Stage:  Accepted
  release notes, confusing   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by timo):

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


Comment:

 Linking to the development version of the docs would require an external
 link which isn't ideal when building a local version of the docs, for
 example, so I opted for a note.

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

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

Re: [Django] #14787: Upload handler should pass errors on to forms.FileField

[Django]

#14787: Upload handler should pass errors on to forms.FileField
-+-
 Reporter:  intgr|Owner:
 Type:  New feature  |  anubhav9042
Component:  File |   Status:  assigned
  uploads/storage|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timo):

 Although the scope of this ticket isn't well defined, I think what you've
 implemented is somewhat tangential to what the summary describes "Upload
 handler should pass errors on to forms.FileField" -- although, I'm not
 sure how/if file size limit errors would be part of the upload handler.
 Btw, `max_upload_size` already exists as a third party package:
 [https://pypi.python.org/pypi/django-validated-file/2.0 django-validated-
 file]. We'd probably want a mailing list thread to figure out if we'd want
 to bring it into core. I don't feel strongly either way on doing so.

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

Re: [Django] #22944: Migrate doesn't like ForeignKey being reassigned to a different app's model

[Django]

#22944: Migrate doesn't like ForeignKey being reassigned to a different app's 
model
+--
 Reporter:  mozumder@…  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7-rc-1
 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 timo):

 Possibly related/duplicate of #22970.

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

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

Re: [Django] #22970: Migration dependencies not correctly calculated

[Django]

#22970: Migration dependencies not correctly calculated
-+--
 Reporter:  dekkers  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-rc-1
 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 timo):

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


Comment:

 Possibly related/duplicate of #22944.

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

[Django] #22970: Migration dependencies not correctly calculated

[Django]

#22970: Migration dependencies not correctly calculated
-+--
 Reporter:  dekkers  |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Migrations   |Version:  1.7-rc-1
 Severity:  Release blocker  |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+--
 When working with the new migrations I hit a bug that dependencies between
 migrations aren't correctly calculated. Migrations that add a ForeignKey
 to a model in another app that was created in the second or later
 migrations of that other app have a depenency on the first migration
 instead of the later migration. Steps to reproduce:

 * Start a new project and create two apps myapp1 and myapp2
 * Add a model named Model1 to myapp1
 * Run makemigrations, resulting in 0001_initial.py that creates Model1
 * Add a model named Model2 to myapp1
 * Run makemigrations, resulting in 0002_model2.py that creates Model2
 * Add a model named Model3 with a !ForeignKey to 'myapp1.Model2' to myapp2
 * Run makemigrations, resulting in 0001_initial.py that creates Model3

 The 0001_initial.py of myapp2 will then have `('myapp1', '__first__')` as
 dependency while Model2 is created in the second migration.

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

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

Re: [Django] #22965: InvalidBasesError for unmigrated apps subclassing contrib

[Django]

#22965: InvalidBasesError for unmigrated apps subclassing contrib
-+
 Reporter:  CollinAnderson   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-rc-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by timo):

 * stage:  Unreviewed => Accepted


Comment:

 The same issue was also reporeted in #22922. I changed the summary there
 to "Add a better error messsage or an FAQ entry for InvalidBasesError" so
 if there's no code changes we can make here, this would be a duplicate of
 that.

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

Re: [Django] #22965: InvalidBasesError for unmigrated apps subclassing contrib

[Django]

#22965: InvalidBasesError for unmigrated apps subclassing contrib
-+--
 Reporter:  CollinAnderson   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-rc-1
 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
-+--

Comment (by CollinAnderson):

 Or, I'm a little naive here, wouldn't it be saner to migrate first and
 syncdb second? It would mean you can't use migrations until your
 dependencies use migrations which seems fine to me (though could be a
 problem for non-migrated custom user models).

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

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

Re: [Django] #22965: InvalidBasesError for unmigrated apps subclassing contrib

[Django]

#22965: InvalidBasesError for unmigrated apps subclassing contrib
-+--
 Reporter:  CollinAnderson   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-rc-1
 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
-+--

Comment (by CollinAnderson):

 The issue is that non migrated apps are synced before migrations happen.
 Could we detect the dependency and run just those migrations first? Or
 syncdb any depended base models and then fake their initial migrations
 later.

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

Re: [Django] #22928: Provide a option to generate the full settings.py instead of the short, minimal one

[Django]

#22928: Provide a option to generate the full settings.py instead of the short,
minimal one
-+--
 Reporter:  guruprasad   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Uncategorized|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  django-admin.py  | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by guruprasad):

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

Re: [Django] #22708: InvalidBasesError when running manage.py migrate

[Django]

#22708: InvalidBasesError when running manage.py migrate
---+--
 Reporter:  strelnikovdmitrij  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Migrations |  Version:  1.7-beta-2
 Severity:  Release blocker|   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by CollinAnderson):

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


Comment:

 It's a separate issue. #22965

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

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

Re: [Django] #22965: InvalidBasesError for unmigrated apps subclassing contrib (was: better error message for unmigrated apps depending on migrated apps.)

[Django]

#22965: InvalidBasesError for unmigrated apps subclassing contrib
-+--
 Reporter:  CollinAnderson   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-rc-1
 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 CollinAnderson):

 * severity:  Normal => Release blocker


Comment:

 Marking as release blocker because someone else ran into it.
 https://code.djangoproject.com/ticket/22708#comment:16

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

[Django] #22969: Forms show_hidden_initial not is_valid() and fix => lost changes in valid fields

[Django]

#22969: Forms show_hidden_initial not is_valid() and fix => lost changes in 
valid
fields
-+-
 Reporter:   |  Owner:  nobody
  dibrovsd@… | Status:  new
 Type:  Bug  |Version:  1.6
Component:  Forms|   Keywords:  Form show_hidden_initial
 Severity:  Normal   |  changed_data
 Triage Stage:   |  Has patch:  0
  Unreviewed |  UI/UX:  0
Easy pickings:  0|
-+-
 if use show_hidden_initial as initial and have some error fields
 form.is_valid() == False
 django set initial other (valid) fields from data
 and in next step (user fix form errors) django lost changed valid fields
 from changed_data


 {{{
 from django.forms import Form, CharField

 class MyForm(Form):

 req_field = CharField(show_hidden_initial=True, required=True)
 notreq_field = CharField(show_hidden_initial=True)

 data = {
 'req_field': '', 'initial-req_field': '',
 'notreq_field': '12', 'initial-notreq_field': '',
 }

 # i can't use initial from database.
 # other user can change some field and django revert unchange field back
 # user 1: open form (field_1 is "1")
 # user 2: change field_1 to "2"
 # user 1 change field_2 to "" and
 # user 1 send unchange (field_1 is "1") initial value field_1 == "2" (user
 2 change it)
 # django mark field_1 as change from 2 to 1 back

 form = MyForm(data=data)
 assert(form.is_valid(), False)  # req_field error

 # show invalid form and set: initial-notreq_field = 12 (why???)
 # in next send form this field not in changed_data
 for field in form.visible_fields():
 print field
 # django action: set initial-notreq_field = 12
 data['initial-notreq_field'] = '12'  #

 # user action: fix error
 data['req_field'] = '12'
 form = MyForm(data=data)
 print form.is_valid()

 for change_field in form.changed_data:
 print 'change', change_field, form.cleaned_data[change_field]
 # oops! lost change in notreq_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/061.aeb3f838824e78f0ae09d73eff87bd34%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22708: InvalidBasesError when running manage.py migrate

[Django]

#22708: InvalidBasesError when running manage.py migrate
---+--
 Reporter:  strelnikovdmitrij  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Migrations |  Version:  1.7-beta-2
 Severity:  Release blocker|   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by stanislas.guerra@…):

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


Comment:

 Hi there,

 Same problem here with a fresh checkout of stable/1.7.x when running my
 tests (which used to works a few weeks ago):


 {{{
 Creating test database for alias 'default'...
 Traceback (most recent call last):
   File "manage.py", line 9, in 
 execute_from_command_line(sys.argv)
   File "/Users/stan/src/venv_dj_1_7/lib/python2.7/site-
 packages/Django-1.7c1-py2.7.egg/django/core/management/__init__.py", line
 385, in execute_from_command_line
 utility.execute()
   File "/Users/stan/src/venv_dj_1_7/lib/python2.7/site-
 packages/Django-1.7c1-py2.7.egg/django/core/management/__init__.py", line
 377, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/Users/stan/src/venv_dj_1_7/lib/python2.7/site-
 packages/Django-1.7c1-py2.7.egg/django/core/management/commands/test.py",
 line 50, in run_from_argv
 super(Command, self).run_from_argv(argv)
   File "/Users/stan/src/venv_dj_1_7/lib/python2.7/site-
 packages/Django-1.7c1-py2.7.egg/django/core/management/base.py", line 288,
 in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/Users/stan/src/venv_dj_1_7/lib/python2.7/site-
 packages/Django-1.7c1-py2.7.egg/django/core/management/commands/test.py",
 line 71, in execute
 super(Command, self).execute(*args, **options)
   File "/Users/stan/src/venv_dj_1_7/lib/python2.7/site-
 packages/Django-1.7c1-py2.7.egg/django/core/management/base.py", line 337,
 in execute
 output = self.handle(*args, **options)
   File "/Users/stan/src/venv_dj_1_7/lib/python2.7/site-
 packages/Django-1.7c1-py2.7.egg/django/core/management/commands/test.py",
 line 88, in handle
 failures = test_runner.run_tests(test_labels)
   File "/Users/stan/src/venv_dj_1_7/lib/python2.7/site-
 packages/Django-1.7c1-py2.7.egg/django/test/runner.py", line 147, in
 run_tests
 old_config = self.setup_databases()
   File "/Users/stan/src/venv_dj_1_7/lib/python2.7/site-
 packages/Django-1.7c1-py2.7.egg/django/test/runner.py", line 109, in
 setup_databases
 return setup_databases(self.verbosity, self.interactive, **kwargs)
   File "/Users/stan/src/venv_dj_1_7/lib/python2.7/site-
 packages/Django-1.7c1-py2.7.egg/django/test/runner.py", line 299, in
 setup_databases
 serialize=connection.settings_dict.get("TEST_SERIALIZE", True),
   File "/Users/stan/src/venv_dj_1_7/lib/python2.7/site-
 packages/Django-1.7c1-py2.7.egg/django/db/backends/creation.py", line 374,
 in create_test_db
 test_flush=True,
   File "/Users/stan/src/venv_dj_1_7/lib/python2.7/site-
 packages/Django-1.7c1-py2.7.egg/django/core/management/__init__.py", line
 115, in call_command
 return klass.execute(*args, **defaults)
   File "/Users/stan/src/venv_dj_1_7/lib/python2.7/site-
 packages/Django-1.7c1-py2.7.egg/django/core/management/base.py", line 337,
 in execute
 output = self.handle(*args, **options)
   File "/Users/stan/src/venv_dj_1_7/lib/python2.7/site-
 packages/Django-1.7c1-py2.7.egg/django/core/management/commands/migrate.py",
 line 160, in handle
 executor.migrate(targets, plan, fake=options.get("fake", False))
   File "/Users/stan/src/venv_dj_1_7/lib/python2.7/site-
 packages/Django-1.7c1-py2.7.egg/django/db/migrations/executor.py", line
 62, in migrate
 self.apply_migration(migration, fake=fake)
   File "/Users/stan/src/venv_dj_1_7/lib/python2.7/site-
 packages/Django-1.7c1-py2.7.egg/django/db/migrations/executor.py", line
 90, in apply_migration
 if self.detect_soft_applied(migration):
   File "/Users/stan/src/venv_dj_1_7/lib/python2.7/site-
 packages/Django-1.7c1-py2.7.egg/django/db/migrations/executor.py", line
 134, in detect_soft_applied
 apps = project_state.render()
   File "/Users/stan/src/venv_dj_1_7/lib/python2.7/site-
 packages/Django-1.7c1-py2.7.egg/django/db/migrations/state.py", line 71,
 in render
 raise InvalidBasesError("Cannot resolve bases for %r" %
 new_unrendered_models)
 InvalidBasesError: Cannot resolve bases for [, ,
 , , ]
 make: *** [test] Error 1

 }}}

 I am not using migrations.

 Here my models.py:


 {{{

 from django.contrib.sites.models import Site
 from django.contrib.auth.models import User


 cla

Re: [Django] #22939: admin_static templatetag is not using the staticfiles' storage

[Django]

#22939: admin_static templatetag is not using the staticfiles' storage
-+-
 Reporter:  generalov|Owner:  aaugustin
 Type:  Bug  |   Status:  assigned
Component:  Core (Other) |  Version:  1.7-rc-1
 Severity:  Release blocker  |   Resolution:
 Keywords:  admin_static admin   | Triage Stage:  Accepted
  app-loading|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

 * has_patch:  0 => 1


Comment:

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

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

Re: [Django] #22957: Humanize - polish translation

[Django]

#22957: Humanize - polish translation
--+--
 Reporter:  efrinut@… |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Translations  |  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
--+--

Comment (by claudep):

 Try to write to his/her email directly: angular.circle at gmail.com

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

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

Re: [Django] #22957: Humanize - polish translation

[Django]

#22957: Humanize - polish translation
--+--
 Reporter:  efrinut@… |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Translations  |  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
--+--

Comment (by anonymous):

 I need to be in translation team. I've applied and haven't been accepted
 yet. Is there anything else I can do?

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

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