date:20131017

Re: [Django] #21268: pep8 cleanup: too many blank lines

2013-10-17 Thread Django

#21268: pep8 cleanup: too many blank lines
--+
 Reporter:  timo  |Owner:  alasdair
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Alex Gaynor ):

 In [changeset:"65750b83523870851008e804364121f8c458fc2d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="65750b83523870851008e804364121f8c458fc2d"
 Merge pull request #1768 from alasdairnicol/ticket_21268

 Fixed #21268 -- Fixed E303 pep8 warnings
 }}}

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

Re: [Django] #21268: pep8 cleanup: too many blank lines

2013-10-17 Thread Django

#21268: pep8 cleanup: too many blank lines
--+
 Reporter:  timo  |Owner:  alasdair
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Alasdair Nicol ):

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


Comment:

 In [changeset:"bab9123daa5d05150951f74183906a76d2b0cf27"]:
 {{{
 #!CommitTicketReference repository=""
 revision="bab9123daa5d05150951f74183906a76d2b0cf27"
 Fixed #21268 -- Fixed E303 pep8 warnings
 }}}

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

[django/django] bab912: Fixed #21268 -- Fixed E303 pep8 warnings

2013-10-17 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: bab9123daa5d05150951f74183906a76d2b0cf27
  
https://github.com/django/django/commit/bab9123daa5d05150951f74183906a76d2b0cf27
  Author: Alasdair Nicol 
  Date:   2013-10-17 (Thu, 17 Oct 2013)

  Changed paths:
M django/contrib/admin/templatetags/admin_list.py
M django/contrib/auth/tests/test_auth_backends.py
M django/contrib/auth/tests/test_views.py
M django/contrib/contenttypes/tests.py
M django/contrib/formtools/preview.py
M django/contrib/formtools/tests/tests.py
M django/contrib/gis/geos/tests/test_mutable_list.py
M django/contrib/gis/tests/test_measure.py
M django/contrib/sessions/tests.py
M django/contrib/sitemaps/tests/test_http.py
M django/core/handlers/base.py
M django/core/urlresolvers.py
M django/forms/models.py
M django/test/runner.py
M django/utils/six.py
M setup.cfg
M tests/admin_changelist/tests.py
M tests/admin_inlines/tests.py
M tests/admin_scripts/management/commands/noargs_command.py
M tests/admin_validation/tests.py
M tests/admin_widgets/tests.py
M tests/app_loading/tests.py
M tests/cache/tests.py
M tests/custom_managers/tests.py
M tests/defaultfilters/tests.py
M tests/delete_regress/tests.py
M tests/files/tests.py
M tests/fixtures_model_package/tests.py
M tests/fixtures_regress/tests.py
M tests/forms_tests/tests/test_extra.py
M tests/forms_tests/tests/test_fields.py
M tests/forms_tests/tests/test_forms.py
M tests/forms_tests/tests/test_formsets.py
M tests/generic_relations/tests.py
M tests/generic_views/test_dates.py
M tests/generic_views/test_edit.py
M tests/http_utils/tests.py
M tests/i18n/tests.py
M tests/m2m_through/tests.py
M tests/middleware/tests.py
M tests/model_forms/tests.py
M tests/model_forms_regress/tests.py
M tests/multiple_database/tests.py
M tests/nested_foreign_keys/tests.py
M tests/or_lookups/tests.py
M tests/prefetch_related/tests.py
M tests/queries/tests.py
M tests/requests/tests.py
M tests/select_related_regress/tests.py
M tests/template_tests/test_response.py
M tests/template_tests/tests.py
M tests/transactions/tests.py
M tests/wsgi/tests.py

  Log Message:
  ---
  Fixed #21268 -- Fixed E303 pep8 warnings


  Commit: 65750b83523870851008e804364121f8c458fc2d
  
https://github.com/django/django/commit/65750b83523870851008e804364121f8c458fc2d
  Author: Alex Gaynor 
  Date:   2013-10-17 (Thu, 17 Oct 2013)

  Changed paths:
M django/contrib/admin/templatetags/admin_list.py
M django/contrib/auth/tests/test_auth_backends.py
M django/contrib/auth/tests/test_views.py
M django/contrib/contenttypes/tests.py
M django/contrib/formtools/preview.py
M django/contrib/formtools/tests/tests.py
M django/contrib/gis/geos/tests/test_mutable_list.py
M django/contrib/gis/tests/test_measure.py
M django/contrib/sessions/tests.py
M django/contrib/sitemaps/tests/test_http.py
M django/core/handlers/base.py
M django/core/urlresolvers.py
M django/forms/models.py
M django/test/runner.py
M django/utils/six.py
M setup.cfg
M tests/admin_changelist/tests.py
M tests/admin_inlines/tests.py
M tests/admin_scripts/management/commands/noargs_command.py
M tests/admin_validation/tests.py
M tests/admin_widgets/tests.py
M tests/app_loading/tests.py
M tests/cache/tests.py
M tests/custom_managers/tests.py
M tests/defaultfilters/tests.py
M tests/delete_regress/tests.py
M tests/files/tests.py
M tests/fixtures_model_package/tests.py
M tests/fixtures_regress/tests.py
M tests/forms_tests/tests/test_extra.py
M tests/forms_tests/tests/test_fields.py
M tests/forms_tests/tests/test_forms.py
M tests/forms_tests/tests/test_formsets.py
M tests/generic_relations/tests.py
M tests/generic_views/test_dates.py
M tests/generic_views/test_edit.py
M tests/http_utils/tests.py
M tests/i18n/tests.py
M tests/m2m_through/tests.py
M tests/middleware/tests.py
M tests/model_forms/tests.py
M tests/model_forms_regress/tests.py
M tests/multiple_database/tests.py
M tests/nested_foreign_keys/tests.py
M tests/or_lookups/tests.py
M tests/prefetch_related/tests.py
M tests/queries/tests.py
M tests/requests/tests.py
M tests/select_related_regress/tests.py
M tests/template_tests/test_response.py
M tests/template_tests/tests.py
M tests/transactions/tests.py
M tests/wsgi/tests.py

  Log Message:
  ---
  Merge pull request #1768 from alasdairnicol/ticket_21268

Fixed #21268 -- Fixed E303 pep8 warnings


Compare: https://github.com/django/django/compare/65d1d65d52a8...65750b835238

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To

[Django] #21287: pep8 cleanup: closing bracket does not match indentation of opening bracket's line

2013-10-17 Thread Django

#21287: pep8 cleanup: closing bracket does not match indentation of opening
bracket's line
+
   Reporter:  timo  |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Core (Other)  |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  1
  UI/UX:  0 |
+
 To find errors, ensure you have an up-to-date master with the flake8
 config in setup.cfg, then remove E123 from the ignore list there. You can
 then run `flake8` from the directory with setup.cfg in it to list all
 errors - there should be about 150.

 Attaching an example patch to get you started.

 Apply it, if you'd like:

 `patch -p1 -i E123.diff`

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

Re: [Django] #21268: pep8 cleanup: too many blank lines

2013-10-17 Thread Django

#21268: pep8 cleanup: too many blank lines
--+
 Reporter:  timo  |Owner:  alasdair
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by alasdair):

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


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

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

[django/django] 65d1d6: Fixed #21267 -- Fixed E502 pep8 warnings

2013-10-17 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 65d1d65d52a87bba22845bcb7c3c921a8789ec19
  
https://github.com/django/django/commit/65d1d65d52a87bba22845bcb7c3c921a8789ec19
  Author: Alasdair Nicol 
  Date:   2013-10-17 (Thu, 17 Oct 2013)

  Changed paths:
M django/contrib/messages/tests/test_cookie.py
M django/contrib/sites/managers.py
M django/core/management/__init__.py
M django/core/management/commands/createcachetable.py
M django/core/management/commands/dbshell.py
M django/core/serializers/xml_serializer.py
M setup.cfg
M tests/admin_changelist/tests.py
M tests/admin_widgets/tests.py
M tests/defaultfilters/tests.py
M tests/distinct_on_fields/tests.py

  Log Message:
  ---
  Fixed #21267 -- Fixed E502 pep8 warnings



-- 
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/5260828aa9081_7552ecdd58140916%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21267: pep8 cleanup: the backslash is redundant between brackets

2013-10-17 Thread Django

#21267: pep8 cleanup: the backslash is redundant between brackets
--+
 Reporter:  timo  |Owner:  alasdair
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Alasdair Nicol ):

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


Comment:

 In [changeset:"65d1d65d52a87bba22845bcb7c3c921a8789ec19"]:
 {{{
 #!CommitTicketReference repository=""
 revision="65d1d65d52a87bba22845bcb7c3c921a8789ec19"
 Fixed #21267 -- Fixed E502 pep8 warnings
 }}}

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

Re: [Django] #21267: pep8 cleanup: the backslash is redundant between brackets

2013-10-17 Thread Django

#21267: pep8 cleanup: the backslash is redundant between brackets
--+
 Reporter:  timo  |Owner:  alasdair
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by alasdair):

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


Comment:

 Pull request https://github.com/django/django/pull/1767

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

[django/django] dfb4cb: Fixed #21285 -- Fixed E121,E122 pep8 warnings

2013-10-17 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: dfb4cb9970f86487f0aaa88c5dfcfafa31e4f430
  
https://github.com/django/django/commit/dfb4cb9970f86487f0aaa88c5dfcfafa31e4f430
  Author: Alasdair Nicol 
  Date:   2013-10-17 (Thu, 17 Oct 2013)

  Changed paths:
M django/conf/global_settings.py
M django/contrib/admin/filters.py
M django/contrib/admin/options.py
M django/contrib/admin/views/main.py
M django/contrib/auth/tests/test_forms.py
M django/contrib/auth/tests/test_management.py
M django/contrib/formtools/tests/wizard/wizardtests/urls.py
M django/contrib/gis/admin/widgets.py
M django/contrib/gis/db/models/__init__.py
M django/contrib/gis/forms/widgets.py
M django/contrib/messages/storage/base.py
M django/contrib/messages/tests/base.py
M django/core/management/validation.py
M django/db/backends/creation.py
M django/db/models/base.py
M django/db/models/fields/__init__.py
M django/db/models/fields/related.py
M django/template/base.py
M django/test/testcases.py
M django/utils/jslex.py
M django/views/decorators/debug.py
M docs/conf.py
M setup.cfg
M tests/bulk_create/tests.py
M tests/cache/tests.py
M tests/extra_regress/tests.py
M tests/forms_tests/tests/test_media.py
M tests/model_regress/tests.py
M tests/prefetch_related/tests.py
M tests/serializers/tests.py
M tests/serializers_regress/tests.py
M tests/signals_regress/tests.py
M tests/template_tests/filters.py
M tests/test_utils/tests.py

  Log Message:
  ---
  Fixed #21285 -- Fixed E121,E122 pep8 warnings



-- 
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/52607f0b42a5e_79054fdd50125649%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21285: pep8 cleanup: continuation line indentation

2013-10-17 Thread Django

#21285: pep8 cleanup: continuation line indentation
--+
 Reporter:  timo  |Owner:  alasdair
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"dfb4cb9970f86487f0aaa88c5dfcfafa31e4f430"]:
 {{{
 #!CommitTicketReference repository=""
 revision="dfb4cb9970f86487f0aaa88c5dfcfafa31e4f430"
 Fixed #21285 -- Fixed E121,E122 pep8 warnings
 }}}

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

[Django] #21286: Fix commented out tests in serializers_regress

2013-10-17 Thread Django

#21286: Fix commented out tests in serializers_regress
+
   Reporter:  timo  |  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  Core (Serialization)  |Version:  master
   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 |
+
 `tests/serializers_regress/tests.py` contains some commented out items in
 the `test_data` list. I think it may be because not all serializers
 support those items. If this is the case, we should make appropriate
 modifications so the tests are run where they are supported and skipped
 where not.

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

Re: [Django] #21283: Migrations created in wrong directory for models defined in model package

2013-10-17 Thread Django

#21283: Migrations created in wrong directory for models defined in model 
package
+
 Reporter:  anonymous   |Owner:  MarkusH
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by timo):

 That would be `get_app_path()` introduced in
 31c13a99bb9ebdaf12ccab4e880c5da930d86e79, I think.

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

Re: [Django] #21285: pep8 cleanup: continuation line indentation

2013-10-17 Thread Django

#21285: pep8 cleanup: continuation line indentation
--+
 Reporter:  timo  |Owner:  alasdair
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by alasdair):

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


Comment:

 Pull request https://github.com/django/django/pull/1766

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

Re: [Django] #21231: Limiting the number of variables and files that a POST request can contain

2013-10-17 Thread Django

#21231: Limiting the number of variables and files that a POST request can 
contain
---+--
 Reporter:  epandurski@…   |Owner:  nobody
 Type:  New feature|   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 epandurski@…):

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


Comment:

 I think I have a nicely working patch for this issue. Here it is:

 
https://github.com/epandurski/django/commit/9ae456e4280843e87a24e508131dfd9919b20db7

 What do you think?

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

Re: [Django] #21283: Migrations created in wrong directory for models defined in model package

2013-10-17 Thread Django

#21283: Migrations created in wrong directory for models defined in model 
package
+
 Reporter:  anonymous   |Owner:  MarkusH
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by loic84):

 @timo, shouldn't this use the app cache methods that you reworked at some
 point to better deal with models in exotic locations?

 As for testing, dunno if this is going to play nice with
 `MIGRATION_MODULES` that we need to use in tests.

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

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

Re: [Django] #21142: Cannot run migrations that reference django.contrib.auth.models.User

2013-10-17 Thread Django

#21142: Cannot run migrations that reference django.contrib.auth.models.User
-+
 Reporter:  mario.pfeifer@…  |Owner:
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  Migration, Auth  | 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):

 Yes, migrations is still under active development. It was merged well
 before it was feature complete because reconciling changes on master with
 the external branch was a challenge. We will definitely review all
 migrations tickets before releasing 1.7.

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

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

[django/django] 37afcb: [1.6.x] Removed 1.6 release note text regarding pa...

2013-10-17 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 37afcbeb92cd556ff1081c9db5a4a320efd5b7a3
  
https://github.com/django/django/commit/37afcbeb92cd556ff1081c9db5a4a320efd5b7a3
  Author: Tim Graham 
  Date:   2013-10-17 (Thu, 17 Oct 2013)

  Changed paths:
M docs/releases/1.6.txt

  Log Message:
  ---
  [1.6.x] Removed 1.6 release note text regarding password limit length.

This changed was reverted in 5d74853e156105ea02a41f4731346dbe272c2412.

Backport of d97bec5ee3 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/52606bff5d46a_57b79d1d54945cd%40hookshot-fe6-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] d97bec: Removed 1.6 release note text regarding password l...

2013-10-17 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d97bec5ee3a6284d30b613c9070588a60358e7ec
  
https://github.com/django/django/commit/d97bec5ee3a6284d30b613c9070588a60358e7ec
  Author: Tim Graham 
  Date:   2013-10-17 (Thu, 17 Oct 2013)

  Changed paths:
M docs/releases/1.6.txt

  Log Message:
  ---
  Removed 1.6 release note text regarding password limit length.

This changed was reverted in 5d74853e156105ea02a41f4731346dbe272c2412.



-- 
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/52606beb17b0a_760e863d50157189%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21142: Cannot run migrations that reference django.contrib.auth.models.User

2013-10-17 Thread Django

Comment (by OBu):

...and to add to the list of problems: There is no migration `__first__`as
well.
Removing the dependencies does not help since migrate is checking all
foreign keys and it does not find information about foreign keys pointing
to `Users`.

Since tried to add a `--fake` migration since in my current application I
wanted to add just a boolean, but this still did not help since migrate
traverses through all models fields.

To sum it up: No work arounds found, switching back to south :-(...

I don't have too much experience with django core development, but I would
rate this bug a "release blocker"...

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

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

Re: [Django] #20346: cache middleware should vary on full URL

2013-10-17 Thread Django

#20346: cache middleware should vary on full URL
-+
 Reporter:  jamey|Owner:
 Type:  Bug  |   Status:  new
Component:  Core (Cache system)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+

Comment (by ijl):

 I've documented the changes in the 1.7 release notes. I'm at a loss for
 backwards-compatible changes using the keys, given that existing cache
 keys use a hash.

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

[django/django] 7e5d7a: Fixed #21259 -- Fixed formstools wizard for Inline...

2013-10-17 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 7e5d7a76bf60564d39d25a101380e47da7f1e2f6
  
https://github.com/django/django/commit/7e5d7a76bf60564d39d25a101380e47da7f1e2f6
  Author: Kathryn Killebrew 
  Date:   2013-10-17 (Thu, 17 Oct 2013)

  Changed paths:
A django/contrib/formtools/tests/models.py
M django/contrib/formtools/tests/wizard/wizardtests/tests.py
M django/contrib/formtools/wizard/views.py

  Log Message:
  ---
  Fixed #21259 -- Fixed formstools wizard for InlineFormSet.



-- 
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/526025f271b41_57d4126bd48577e5%40hookshot-fe6-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21259: Wizard sets queryset instead of instance on InlineFormset

2013-10-17 Thread Django

#21259: Wizard sets queryset instead of instance on InlineFormset
-+-
 Reporter:  banderkat@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.formtools|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  wizard,  | Triage Stage:  Accepted
  InlineFormSet  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"7e5d7a76bf60564d39d25a101380e47da7f1e2f6"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7e5d7a76bf60564d39d25a101380e47da7f1e2f6"
 Fixed #21259 -- Fixed formstools wizard for InlineFormSet.
 }}}

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

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

[django/django] 9833b9: Removed importing formtools tests in init.py

2013-10-17 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 9833b931b78ab3fac33b55873d13769f6dcdb41e
  
https://github.com/django/django/commit/9833b931b78ab3fac33b55873d13769f6dcdb41e
  Author: Tim Graham 
  Date:   2013-10-17 (Thu, 17 Oct 2013)

  Changed paths:
M django/contrib/formtools/tests/wizard/__init__.py

  Log Message:
  ---
  Removed importing formtools tests in __init__.py

Unnecessary since introduction of DiscoveryTestRunner in 9012833af8.



-- 
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/526023ecacffe_52cd59d5056675%40hookshot-fe5-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 3514bc: Fixed #21284 -- Prevented KeyError swallowing in f...

2013-10-17 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3514bcb251fb623dbd07911e53d417d55934ffa5
  
https://github.com/django/django/commit/3514bcb251fb623dbd07911e53d417d55934ffa5
  Author: Claude Paroz 
  Date:   2013-10-17 (Thu, 17 Oct 2013)

  Changed paths:
M django/core/management/__init__.py
M tests/admin_scripts/tests.py

  Log Message:
  ---
  Fixed #21284 -- Prevented KeyError swallowing in fetch_command

Thanks wildfire for the report.



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

Re: [Django] #21284: Errors in the settings.py file result in misleading messages

2013-10-17 Thread Django

#21284: Errors in the settings.py file result in misleading messages
-+-
 Reporter:  wildfire |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:
  commands)  |  1.6-beta-1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"3514bcb251fb623dbd07911e53d417d55934ffa5"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3514bcb251fb623dbd07911e53d417d55934ffa5"
 Fixed #21284 -- Prevented KeyError swallowing in fetch_command

 Thanks wildfire for the report.
 }}}

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

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

[django/django] b2f9c7: [1.6.x] Fixed #21282 -- Made HttpResponse.serializ...

2013-10-17 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: b2f9c74ed1cd246022ab52d239eeb33f950dcc70
  
https://github.com/django/django/commit/b2f9c74ed1cd246022ab52d239eeb33f950dcc70
  Author: Claude Paroz 
  Date:   2013-10-17 (Thu, 17 Oct 2013)

  Changed paths:
M django/http/response.py
M tests/httpwrappers/tests.py

  Log Message:
  ---
  [1.6.x] Fixed #21282 -- Made HttpResponse.serialize_headers accept latin-1

Thanks Raphaël Barrois for the report and the initial patch and
Aymeric Augustin for the review.

Backport of a14f087233 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/52600d64b6653_70131219d5446537%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21282: The serialize_headers method of HttpResponse fails to handle latin1-compatible values

2013-10-17 Thread Django

#21282: The serialize_headers method of HttpResponse fails to handle
latin1-compatible values
--+
 Reporter:  xelnor|Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  HTTP handling |  Version:  1.4
 Severity:  Normal|   Resolution:  fixed
 Keywords:  http header encoding  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Claude Paroz ):

 In [changeset:"b2f9c74ed1cd246022ab52d239eeb33f950dcc70"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b2f9c74ed1cd246022ab52d239eeb33f950dcc70"
 [1.6.x] Fixed #21282 -- Made HttpResponse.serialize_headers accept latin-1

 Thanks Raphaël Barrois for the report and the initial patch and
 Aymeric Augustin for the review.

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

[django/django] a14f08: Fixed #21282 -- Made HttpResponse.serialize_header...

2013-10-17 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a14f08723304be27e851c753a68c8200473a9ca1
  
https://github.com/django/django/commit/a14f08723304be27e851c753a68c8200473a9ca1
  Author: Claude Paroz 
  Date:   2013-10-17 (Thu, 17 Oct 2013)

  Changed paths:
M django/http/response.py
M tests/httpwrappers/tests.py

  Log Message:
  ---
  Fixed #21282 -- Made HttpResponse.serialize_headers accept latin-1

Thanks Raphaël Barrois for the report and the initial patch and
Aymeric Augustin for the review.



-- 
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/52600d07b7c7_62891105d5098862%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21282: The serialize_headers method of HttpResponse fails to handle latin1-compatible values

2013-10-17 Thread Django

#21282: The serialize_headers method of HttpResponse fails to handle
latin1-compatible values
--+
 Reporter:  xelnor|Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  HTTP handling |  Version:  1.4
 Severity:  Normal|   Resolution:  fixed
 Keywords:  http header encoding  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"a14f08723304be27e851c753a68c8200473a9ca1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a14f08723304be27e851c753a68c8200473a9ca1"
 Fixed #21282 -- Made HttpResponse.serialize_headers accept latin-1

 Thanks Raphaël Barrois for the report and the initial patch and
 Aymeric Augustin for the review.
 }}}

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

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

[django/django] 500870: Added test for a921f06 - refs #21280.

2013-10-17 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 50087063450b3134461f2c4c5a36c3dd8ec1980c
  
https://github.com/django/django/commit/50087063450b3134461f2c4c5a36c3dd8ec1980c
  Author: Loic Bistuer 
  Date:   2013-10-17 (Thu, 17 Oct 2013)

  Changed paths:
M tests/migrations/models.py
M tests/migrations/test_commands.py

  Log Message:
  ---
  Added test for a921f06 - refs #21280.

This commit also lays the groundwork for future tests for the
makemigrations command.



-- 
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/52600ccdd2eed_563b5e5d5813403e%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21280: Avoid generating empty migrations on serialization failures

2013-10-17 Thread Django

#21280: Avoid generating empty migrations on serialization failures
-+-
 Reporter:  timo |Owner:  Tim
 Type:  Bug  |  Graham 
Component:  Migrations   |   Status:  closed
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:  fixed
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"50087063450b3134461f2c4c5a36c3dd8ec1980c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="50087063450b3134461f2c4c5a36c3dd8ec1980c"
 Added test for a921f06 - refs #21280.

 This commit also lays the groundwork for future tests for the
 makemigrations command.
 }}}

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

Re: [Django] #21284: Errors in the settings.py file result in misleading messages

2013-10-17 Thread Django

#21284: Errors in the settings.py file result in misleading messages
-+-
 Reporter:  wildfire |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:
  commands)  |  1.6-beta-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by claudep):

 * component:  Uncategorized => Core (Management commands)
 * easy:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 That issue is specific to `KeyError`, which is swallowed in
 `fetch_command`. But the workaround is trivial (separate `get_commands()`
 from getting the index).

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

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

Re: [Django] #21279: Field content not escaped in admin filter

2013-10-17 Thread Django

#21279: Field content not escaped in admin filter
-+-
 Reporter:  cam.w.lee@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.4
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  javascript escape| Triage Stage:
  admin filter   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by cam.w.lee@…):

 Replying to [comment:7 timo]:
 > By the way, you should report security issues like this privately.  For
 Django, see djangoproject.com/security


 Ok. I'll do that in the future. For this ticket though, is there any way
 to delete 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/077.ddb2d54b8aa6274fba9e9c65f3c91327%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21282: The serialize_headers method of HttpResponse fails to handle latin1-compatible values

2013-10-17 Thread Django

#21282: The serialize_headers method of HttpResponse fails to handle
latin1-compatible values
--+
 Reporter:  xelnor|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  HTTP handling |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:  http header encoding  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by claudep):

 I've attached a slightly different patch, Python 3 compatible. Aymeric's
 review mandatory!

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

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

[Django] #21285: pep8 cleanup: continuation line indentation

2013-10-17 Thread Django

#21285: pep8 cleanup: continuation line indentation
+
   Reporter:  timo  |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Core (Other)  |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  1
  UI/UX:  0 |
+
 Includes two errors:
 * E21 continuation line indentation is not a multiple of four
 * E122 continuation line missing indentation or outdented

 To find errors, ensure you have an up-to-date master with the flake8
 config in setup.cfg, then remove E121,E122 from the ignore list there. You
 can then run `flake8` from the directory with setup.cfg in it to list all
 errors - there should be about 115.

 Attaching an example patch to get you started.

 Apply it, if you'd like:

 `patch -p1 -i E121.diff`

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

Re: [Django] #20346: cache middleware should vary on full URL

2013-10-17 Thread Django

* needs_better_patch: 0 => 1
* version: 1.3 => master
* needs_tests: 1 => 0
* needs_docs: 0 => 1

Comment:

Here's an [https://code.djangoproject.com/ticket/20346 updated PR] with
tests. I left some minor comments for improvement.

One concern is that upgrading Django will change cache keys for all the
existing pages now that the domain name is part of the key. At a minimum,
this needs to be documented in the release notes. Ideas for how we might
be able to do this in a backwards compatible fashion would also be
welcome.

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

Re: [Django] #21282: The serialize_headers method of HttpResponse fails to handle latin1-compatible values

2013-10-17 Thread Django

#21282: The serialize_headers method of HttpResponse fails to handle
latin1-compatible values
--+
 Reporter:  xelnor|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  HTTP handling |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:  http header encoding  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

 * stage:  Unreviewed => Accepted


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

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

[django/django] 3a6603: Removed F.deepcopy()

2013-10-17 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3a66035107a640c4905f0a5f247a45f32dbe16d7
  
https://github.com/django/django/commit/3a66035107a640c4905f0a5f247a45f32dbe16d7
  Author: Anssi Kääriäinen 
  Date:   2013-10-17 (Thu, 17 Oct 2013)

  Changed paths:
M django/db/models/expressions.py

  Log Message:
  ---
  Removed F.__deepcopy__()

The method didn't change standard __deepcopy__ in any way.



-- 
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/525ff891ce719_63027b7d489564f%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20834: Document how user permission caching works

2013-10-17 Thread Django

#20834: Document how user permission caching works
--+
 Reporter:  Giggaflop |Owner:  Jennifer
 Type:  New feature   |   Status:  assigned
Component:  Documentation |  Version:
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timo):

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


Comment:

 I left some comments for improvement on the pull request.

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

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

Re: [Django] #21283: Migrations created in wrong directory for models defined in model package

2013-10-17 Thread Django

#21283: Migrations created in wrong directory for models defined in model 
package
+
 Reporter:  anonymous   |Owner:  MarkusH
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by timo):

 Could you make a separate test app like "migrations_model_package" and
 make sure migrations are properly generated there?

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

[django/django] 2fb5a5: Fixed #18659 -- Deprecated request.REQUEST and Mer...

2013-10-17 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2fb5a51fa3ac276efc7121ec9de91f092a986104
  
https://github.com/django/django/commit/2fb5a51fa3ac276efc7121ec9de91f092a986104
  Author: Bouke Haarsma 
  Date:   2013-10-17 (Thu, 17 Oct 2013)

  Changed paths:
M django/contrib/admin/options.py
M django/contrib/auth/admin.py
M django/contrib/auth/tests/test_views.py
M django/contrib/auth/views.py
M django/core/handlers/wsgi.py
M django/utils/datastructures.py
M django/views/i18n.py
M docs/internals/deprecation.txt
M docs/ref/request-response.txt
M docs/releases/1.7.txt
M tests/deprecation/tests.py
M tests/forms_tests/tests/test_forms.py
M tests/test_client_regress/views.py
M tests/utils_tests/test_datastructures.py

  Log Message:
  ---
  Fixed #18659 -- Deprecated request.REQUEST and MergeDict

Thanks Aymeric Augustin 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/525fed4753a3a_573157bd54103968%40hookshot-fe6-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18659: Remove `request.REQUEST`

2013-10-17 Thread Django

#18659: Remove `request.REQUEST`
--+
 Reporter:  aaugustin |Owner:  bouke
 Type:  Cleanup/optimization  |   Status:  closed
Component:  HTTP handling |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"2fb5a51fa3ac276efc7121ec9de91f092a986104"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2fb5a51fa3ac276efc7121ec9de91f092a986104"
 Fixed #18659 -- Deprecated request.REQUEST and MergeDict

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

Re: [Django] #18549: Admin should not use verbose_name_plural for OneToOne field

2013-10-17 Thread Django

#18549: Admin should not use verbose_name_plural for OneToOne field
---+
 Reporter:  RoySmith   |Owner:  vanessagomes
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timo):

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


Comment:

 This needs tests, ideally adding `max_num=1` to an existing tabular and
 stacked inline and verifying the  text. The existing patch also causes
 some test failures due to the added whitespace.

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

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

Re: [Django] #21284: Errors in the settings.py file result in misleading messages

2013-10-17 Thread Django

#21284: Errors in the settings.py file result in misleading messages
---+--
 Reporter:  wildfire   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  1.6-beta-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
---+--
Changes (by aaugustin):

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


Comment:

 Does this only happen with `KeyError`, or also with other exceptions? For
 instance what happens if you put `1/0` in your settings file?

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

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

Re: [Django] #21283: Migrations created in wrong directory for models defined in model package

2013-10-17 Thread Django

#21283: Migrations created in wrong directory for models defined in model 
package
+
 Reporter:  anonymous   |Owner:  MarkusH
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by MarkusH):

 * cc: info@… (added)
 * owner:  anonymous => MarkusH


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

Re: [Django] #21283: Migrations created in wrong directory for models defined in model package

2013-10-17 Thread Django

#21283: Migrations created in wrong directory for models defined in model 
package
+-
 Reporter:  anonymous   |Owner:  anonymous
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+-
Changes (by Markus Holtermann ):

 * owner:  MarkusH => anonymous
 * status:  new => assigned
 * has_patch:  0 => 1
 * needs_tests:  0 => 1


Comment:

 The pull request is at https://github.com/django/django/pull/1763

 Right know I don't have a clue how to write a test case for this issue.

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

Re: [Django] #19898: Document why/when of class-based views

2013-10-17 Thread Django

#19898: Document why/when of class-based views
-+--
 Reporter:  estebistec   |Owner:  estebistec
 Type:  New feature  |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  docs sprint2013  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+--
Changes (by timo):

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


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

[Django] #21284: Errors in the settings.py file result in misleading messages

2013-10-17 Thread Django

#21284: Errors in the settings.py file result in misleading messages
---+
 Reporter:  wildfire   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  1.6-beta-1
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 If you have an error in your settings.py, Django 1.6 will give an error
 indicating that whatever command you are attempting to run does not exist.

 $ django-admin.py startproject djtest .
 $ python manage.py validate
 0 errors found

 Now edit djtest/settings.py and put the following in the file:

 diff -u djtest.orig/settings.py djtest/settings.py
 --- djtest.orig/settings.py 2013-10-17 14:18:51.348674346 +0100
 +++ djtest/settings.py  2013-10-17 14:20:07.773667472 +0100
 @@ -26,6 +26,7 @@

  ALLOWED_HOSTS = []

 +ENV_FACTOR_STUFF = os.environ['ENV_FACTOR_STUFF']

  # Application definition

 # (i.e. attempt to get something from the environment)

 $ python manage.py validate
 Unknown command: 'validate'
 Type 'manage.py help' for usage.

 $ python manage.py runserver
 Unknown command: 'runserver'
 Type 'manage.py help' for usage.


 etc.

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

Re: [Django] #12090: Show admin actions on the edit pages too

2013-10-17 Thread Django

#12090: Show admin actions on the edit pages too
---+
 Reporter:  apollo13   |Owner:  jgmize
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  1
---+
Changes (by timo):

 * needs_better_patch:  0 => 1


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

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

Re: [Django] #21283: Migrations created in wrong directory for models defined in model package

2013-10-17 Thread Django

#21283: Migrations created in wrong directory for models defined in model 
package
+
 Reporter:  anonymous   |Owner:  MarkusH
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by timo):

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


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

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

[Django] #21283: Migrations created in wrong directory for models defined in model package

2013-10-17 Thread Django

#21283: Migrations created in wrong directory for models defined in model 
package
+-
 Reporter:  anonymous   |  Owner:  MarkusH
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  master
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+-
 Django supports to split a bunch of models into a separate Python modules
 which are placed in a models Python package. However the
 `django.db.migrations.writer.MigrationWriter` does not reflect this fact
 in its `path` property.

 The solution is easy:

 If `myapp.models` is a Python `app_module` (currently line 61) has a
 `__path__` attribute. If it is a Python module there is no such attribute.

 I'm going to write a patch and open a pull request for further discussion.

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

Re: [Django] #21281: trying to override settings in test case setUpClass

2013-10-17 Thread Django

#21281: trying to override settings in test case setUpClass
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Testing framework  |  Version:  1.5
 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 alasdair):

 * cc: alasdair (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


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

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

[django/django] 98788d: Remove some unnecesary uses of bool

2013-10-17 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 98788d3c3af9f6cce2b94c276d17726f46608b08
  
https://github.com/django/django/commit/98788d3c3af9f6cce2b94c276d17726f46608b08
  Author: Alex Gaynor 
  Date:   2013-10-17 (Thu, 17 Oct 2013)

  Changed paths:
M django/contrib/gis/gdal/datasource.py
M django/contrib/gis/gdal/geometries.py
M django/contrib/gis/gdal/prototypes/errcheck.py
M django/contrib/gis/geoip/prototypes.py
M django/contrib/gis/geos/geometry.py
M django/contrib/gis/geos/prototypes/io.py
M django/db/backends/mysql/introspection.py

  Log Message:
  ---
  Remove some unnecesary uses of bool



-- 
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/525fd7b9da232_6e6fac9d4c917b1%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] a921f0: Fixed #21280 -- Don't generate empty migration fil...

2013-10-17 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a921f0634583e2f87475e802e2674e7159b4f25b
  
https://github.com/django/django/commit/a921f0634583e2f87475e802e2674e7159b4f25b
  Author: Javed Khan 
  Date:   2013-10-17 (Thu, 17 Oct 2013)

  Changed paths:
M django/core/management/commands/makemigrations.py

  Log Message:
  ---
  Fixed #21280 -- Don't generate empty migration files



-- 
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/525fd64bd0990_6e6fac9d4c91174%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21280: Avoid generating empty migrations on serialization failures

2013-10-17 Thread Django

#21280: Avoid generating empty migrations on serialization failures
-+-
 Reporter:  timo |Owner:  Tim
 Type:  Bug  |  Graham 
Component:  Migrations   |   Status:  closed
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:  fixed
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Tim Graham ):

 * owner:   => Tim Graham 
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"a921f0634583e2f87475e802e2674e7159b4f25b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a921f0634583e2f87475e802e2674e7159b4f25b"
 Fixed #21280 -- Don't generate empty migration 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/062.cb42bec9f0cd435f5cfef4008ffe13fa%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 7f508a: Removed some dead code and simplified some other o...

2013-10-17 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 7f508a36731660c8cd2659f23098f1379eaa8fb5
  
https://github.com/django/django/commit/7f508a36731660c8cd2659f23098f1379eaa8fb5
  Author: Alex Gaynor 
  Date:   2013-10-17 (Thu, 17 Oct 2013)

  Changed paths:
M django/contrib/gis/gdal/prototypes/errcheck.py
M django/contrib/gis/gdal/prototypes/geom.py
M django/contrib/gis/geos/tests/test_geos_mutation.py

  Log Message:
  ---
  Removed some dead code and simplified some other ocde



-- 
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/525fd4d027391_57b79d1d5459188%40hookshot-fe6-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21270: pep8 cleanup: multiple statements on one line (colon)

2013-10-17 Thread Django

#21270: pep8 cleanup: multiple statements on one line (colon)
--+
 Reporter:  timo  |Owner:  alasdair
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Alex Gaynor ):

 In [changeset:"cce42d4cf2d6820ce04e71b7c1a785ec0d19538f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cce42d4cf2d6820ce04e71b7c1a785ec0d19538f"
 Merge pull request #1762 from alasdairnicol/ticket_21270

 Fixed #21270 -- Fixed E701 pep8 warnings
 }}}

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

Re: [Django] #21270: pep8 cleanup: multiple statements on one line (colon)

2013-10-17 Thread Django

#21270: pep8 cleanup: multiple statements on one line (colon)
--+
 Reporter:  timo  |Owner:  alasdair
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Alasdair Nicol ):

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


Comment:

 In [changeset:"eb214452c3b1dc399b629aabea926e27b5538c52"]:
 {{{
 #!CommitTicketReference repository=""
 revision="eb214452c3b1dc399b629aabea926e27b5538c52"
 Fixed #21270 -- Fixed E701 pep8 warnings
 }}}

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

[django/django] eb2144: Fixed #21270 -- Fixed E701 pep8 warnings

2013-10-17 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: eb214452c3b1dc399b629aabea926e27b5538c52
  
https://github.com/django/django/commit/eb214452c3b1dc399b629aabea926e27b5538c52
  Author: Alasdair Nicol 
  Date:   2013-10-17 (Thu, 17 Oct 2013)

  Changed paths:
M django/contrib/admin/views/main.py
M django/contrib/admindocs/utils.py
M django/contrib/gis/admin/options.py
M django/contrib/gis/admin/widgets.py
M django/contrib/gis/db/backends/base.py
M django/contrib/gis/db/backends/postgis/introspection.py
M django/contrib/gis/db/backends/postgis/operations.py
M django/contrib/gis/db/backends/spatialite/operations.py
M django/contrib/gis/db/models/proxy.py
M django/contrib/gis/db/models/query.py
M django/contrib/gis/db/models/sql/compiler.py
M django/contrib/gis/db/models/sql/query.py
M django/contrib/gis/feeds.py
M django/contrib/gis/gdal/base.py
M django/contrib/gis/gdal/datasource.py
M django/contrib/gis/gdal/driver.py
M django/contrib/gis/gdal/error.py
M django/contrib/gis/gdal/feature.py
M django/contrib/gis/gdal/field.py
M django/contrib/gis/gdal/geometries.py
M django/contrib/gis/gdal/geomtype.py
M django/contrib/gis/gdal/layer.py
M django/contrib/gis/gdal/libgdal.py
M django/contrib/gis/gdal/prototypes/errcheck.py
M django/contrib/gis/gdal/prototypes/generation.py
M django/contrib/gis/gdal/srs.py
M django/contrib/gis/gdal/tests/test_ds.py
M django/contrib/gis/gdal/tests/test_geom.py
M django/contrib/gis/geoip/base.py
M django/contrib/gis/geoip/libgeoip.py
M django/contrib/gis/geoip/prototypes.py
M django/contrib/gis/geos/base.py
M django/contrib/gis/geos/collections.py
M django/contrib/gis/geos/coordseq.py
M django/contrib/gis/geos/geometry.py
M django/contrib/gis/geos/libgeos.py
M django/contrib/gis/geos/linestring.py
M django/contrib/gis/geos/mutable_list.py
M django/contrib/gis/geos/point.py
M django/contrib/gis/geos/polygon.py
M django/contrib/gis/geos/prepared.py
M django/contrib/gis/geos/prototypes/errcheck.py
M django/contrib/gis/geos/prototypes/geom.py
M django/contrib/gis/geos/prototypes/io.py
M django/contrib/gis/geos/prototypes/predicates.py
M django/contrib/gis/geos/prototypes/threadsafe.py
M django/contrib/gis/geos/prototypes/topology.py
M django/contrib/gis/geos/tests/test_geos.py
M django/contrib/gis/geos/tests/test_geos_mutation.py
M django/contrib/gis/geos/tests/test_mutable_list.py
M django/contrib/gis/maps/google/gmap.py
M django/contrib/gis/maps/google/overlays.py
M django/contrib/gis/measure.py
M django/contrib/gis/sitemaps/georss.py
M django/contrib/gis/sitemaps/kml.py
M django/contrib/gis/tests/distapp/models.py
M django/contrib/gis/tests/distapp/tests.py
M django/contrib/gis/tests/geoadmin/models.py
M django/contrib/gis/tests/geoapp/models.py
M django/contrib/gis/tests/geoapp/tests.py
M django/contrib/gis/tests/geogapp/models.py
M django/contrib/gis/tests/layermap/tests.py
M django/contrib/gis/tests/relatedapp/models.py
M django/contrib/gis/tests/relatedapp/tests.py
M django/contrib/gis/tests/utils.py
M django/contrib/gis/utils/layermapping.py
M django/contrib/gis/utils/ogrinspect.py
M django/core/management/color.py
M django/forms/utils.py
M django/forms/widgets.py
M django/utils/text.py
M django/utils/translation/trans_null.py
M django/utils/xmlutils.py
M setup.cfg
M tests/decorators/tests.py
M tests/forms_tests/tests/test_error_messages.py
M tests/forms_tests/tests/test_extra.py
M tests/forms_tests/tests/test_util.py

  Log Message:
  ---
  Fixed #21270 -- Fixed E701 pep8 warnings


  Commit: cce42d4cf2d6820ce04e71b7c1a785ec0d19538f
  
https://github.com/django/django/commit/cce42d4cf2d6820ce04e71b7c1a785ec0d19538f
  Author: Alex Gaynor 
  Date:   2013-10-17 (Thu, 17 Oct 2013)

  Changed paths:
M django/contrib/admin/views/main.py
M django/contrib/admindocs/utils.py
M django/contrib/gis/admin/options.py
M django/contrib/gis/admin/widgets.py
M django/contrib/gis/db/backends/base.py
M django/contrib/gis/db/backends/postgis/introspection.py
M django/contrib/gis/db/backends/postgis/operations.py
M django/contrib/gis/db/backends/spatialite/operations.py
M django/contrib/gis/db/models/proxy.py
M django/contrib/gis/db/models/query.py
M django/contrib/gis/db/models/sql/compiler.py
M django/contrib/gis/db/models/sql/query.py
M django/contrib/gis/feeds.py
M django/contrib/gis/gdal/base.py
M django/contrib/gis/gdal/datasource.py
M django/contrib/gis/gdal/driver.py
M django/contrib/gis/gdal/error.py
M django/contrib/gis/gdal/feature.py
M django/contrib/gis/gdal/field.py
M django/contrib/gis/gdal/geometries.py

Re: [Django] #21270: pep8 cleanup: multiple statements on one line (colon)

2013-10-17 Thread Django

#21270: pep8 cleanup: multiple statements on one line (colon)
--+
 Reporter:  timo  |Owner:  alasdair
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by alasdair):

 Pull request: https://github.com/django/django/pull/1762

 The test suite passes with the changes, but I need to configure my setup
 so that I can run the tests which are skipping.

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

Re: [Django] #21280: Avoid generating empty migrations on serialization failures

2013-10-17 Thread Django

#21280: Avoid generating empty migrations on serialization failures
+
 Reporter:  timo|Owner:
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by tuxcanfly):

 Submitted a simple fix: https://github.com/django/django/pull/1761

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

Re: [Django] #21257: ForeignKey on_delete functionality should traverse (cascade, ha ha) to the DB backend

2013-10-17 Thread Django

#21257: ForeignKey on_delete functionality should traverse (cascade, ha ha) to 
the
DB backend
---+
 Reporter:  gcbirzan   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Uncategorized  |  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 anonymous):

 I think the URL should be https://groups.google.com/forum/#!topic/django-
 developers/FJMoGgtYIX4

 Anyway, it is, but this doesn't involve any default behaviour change, so
 it should be way easier.

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

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

Re: [Django] #21282: The serialize_headers method of HttpResponse fails to handle latin1-compatible values

2013-10-17 Thread Django

#21282: The serialize_headers method of HttpResponse fails to handle
latin1-compatible values
-+-
 Reporter:  xelnor   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  HTTP handling|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  http header  | Triage Stage:
  encoding   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by xelnor):

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


Comment:

 The test suite passes with the proposed patch:
 {{{
 Ran 5906 tests in 201.214s

 OK (skipped=348, expected failures=11)
 }}}

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

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

[Django] #21282: The serialize_headers method of HttpResponse fails to handle latin1-compatible values

2013-10-17 Thread Django

#21282: The serialize_headers method of HttpResponse fails to handle
latin1-compatible values
---+--
 Reporter:  xelnor |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  HTTP handling  |Version:  1.4
 Severity:  Normal |   Keywords:  http header encoding
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  0  |  UI/UX:  0
---+--
 If a header value (passed as unicode) contains only ascii data,
 `serialize_headers()` doesn't fail
 If it contains characters that can't be encoded in latin1,
 `serialize_headers()` doesn't fail
 If it contains only characters valid in latin1, including some outside the
 ascii range, `serialize_headers()` fails with a `UnicodeDecodeError`.

 The culprit seems to lie on line 132 of `django/http/response.py`: that
 line calls `('%s: %s' % (key, value)).encode('us-ascii')`, but at this
 point, key is ascii bytes and value is a bytes array containing either
 latin1-encoded text or mime-encoded utf8 text.

 Since we're using `unicode_literals`, Python tries
 `value.decode('ascii')`, which fails if, and only if, value contains
 latin1 characters outside the ascii range.

 I have attached a patch containing both a test exhibiting the issue and a
 patch fixing it (no test failure).

 Note: This is not a release blocker, since the `serialize_headers()` and
 its callers (`serialize()` and `__str__()`) aren't used while answering
 requests.

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

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

Re: [Django] #7018: Make ModelForm multiple inheritance possible

2013-10-17 Thread Django

#7018: Make ModelForm multiple inheritance possible
-+
 Reporter:  bear330  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  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 mjtamlyn):

 Sounds like you want something along the lines of
 https://github.com/bmispelon/django-multiform


 You'd nerd to write the connection logic yourself each time but I think
 that's fine. Personally I'm not convinced this is code which needs to live
 in core. Baptiste may have a different opinion.

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

Re: [Django] #7018: Make ModelForm multiple inheritance possible

2013-10-17 Thread Django

Comment (by anonymous):

Replying to [comment:20 mjtamlyn]:
> Worth noting here that you can now combine Form and ModelForm together.
Combining the multiple models is a much more complex issue, and one I'm
personally not convinced should be included. This has implications on
validation and saving which could have a myriad of edge cases. Personally
I think some code which renders and validates two forms would be superior,
handled effectively as a nonhomogeneous Form set.
This is closer to what I want to do (combine multiple model forms in one
form)
Where can I find info on this ?
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/065.002916615a33947f02b2c1cb4bcd53fe%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #7018: Make ModelForm multiple inheritance possible

2013-10-17 Thread Django

#7018: Make ModelForm multiple inheritance possible
-+
 Reporter:  bear330  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  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 mjtamlyn):

 Worth noting here that you can now combine Form and ModelForm together.
 Combining the multiple models is a much more complex issue, and one I'm
 personally not convinced should be included. This has implications on
 validation and saving which could have a myriad of edge cases. Personally
 I think some code which renders and validates two forms would be superior,
 handled effectively as a nonhomogeneous Form set.

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

Re: [Django] #21275: Cannot use migrations if model field specifies validators

2013-10-17 Thread Django

#21275: Cannot use migrations if model field specifies validators
+--
 Reporter:  timo|Owner:
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by loic84):

 Another POC around the concept of a `deconstructible` decorator.

 https://github.com/loic/django/tree/ticket21275_take2.

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

Re: [Django] #13008: @never_cache decorator should add 'no-cache' & 'no-store'

2013-10-17 Thread Django

#13008: @never_cache decorator should add  'no-cache' & 'no-store'
-+
 Reporter:  harm |Owner:  susan
 Type:  Bug  |   Status:  assigned
Component:  Core (Cache system)  |  Version:  1.2-beta
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by susan):

 Where should I write a test? Should it be in `cache/tests.py`? The
 function `add_never_cache_headers` is never tested in the`tests/`
 directory.

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

Re: [Django] #7018: Make ModelForm multiple inheritance possible

2013-10-17 Thread Django

#7018: Make ModelForm multiple inheritance possible
-+
 Reporter:  bear330  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  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 maa@…):

 * cc: maa@… (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/065.9ef281339f5d50cd42326beb2a13e30e%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13008: @never_cache decorator should add 'no-cache' & 'no-store' (was: @never_cache decorator should add 'no-cache' & 'must-revalidate')

2013-10-17 Thread Django

#13008: @never_cache decorator should add  'no-cache' & 'no-store'
-+
 Reporter:  harm |Owner:  susan
 Type:  Bug  |   Status:  assigned
Component:  Core (Cache system)  |  Version:  1.2-beta
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by susan):

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


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

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

71 matches

Mail list logo