Re: [Django] #22452: VIEW PERMISSIONS

[Django]

#22452: VIEW PERMISSIONS
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.6
 Severity:  Normal |   Resolution:  duplicate
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by anonymous):

 Replying to [comment:8 timo]:
 > Please use our support channels for usage questions.

 Yes i posted question and no one reply there . my question
 https://groups.google.com/forum/#!topic/django-users/6QZdC1sgwqw

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

Re: [Django] #22448: django test command runs wrong tests if test module has no tests

[Django]

#22448: django test command runs wrong tests if test module has no tests
-+-
 Reporter:  cjerdonek|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  test discovery,test  | Triage Stage:  Accepted
  runner,test command,test label |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by prestontimmons):

 After some further testing I realized this is fixed in 1.7. That's because
 we now only run discovery if the test label is a module or 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/067.0c22edb72e8fe04f60b7cf52d83e7f41%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22448: django test command runs wrong tests if test module has no tests

[Django]

#22448: django test command runs wrong tests if test module has no tests
-+-
 Reporter:  cjerdonek|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  test discovery,test  | Triage Stage:  Accepted
  runner,test command,test label |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by prestontimmons):

 * stage:  Unreviewed => Accepted


Comment:

 Yes, I can reproduce this now. That explains why the existing test reports
 back without error as well.

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

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

Re: [Django] #22459: Creating model classes for test purposes breaks migrations

[Django]

#22459: Creating model classes for test purposes breaks migrations
---+--
 Reporter:  pgcd   |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Migrations |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by loic84):

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


Comment:

 Hi @pgcd, do you have the admin (`django.contrib.admin`) in your
 `INSTALLED_APPS`? If so, could you try commenting it out before running
 `django-admin.py sqlflush`?

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

Re: [Django] #22462: Loading issue of models declared in tests.py due to a combination of AdminConfig, System checks, and Model._meta caching.

[Django]

#22462: Loading issue of models declared in tests.py due to a combination of
AdminConfig, System checks, and Model._meta caching.
-+
 Reporter:  loic84   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by loic84):

 @charettes hard to tell for #22459, I'm gonna ask the OP to try commenting
 out the admin from `INSTALLED_APPS`.

 I believe the `select_related` issue is tracked at #10414.

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

Re: [Django] #12531: Model field name 'hiding' should not be permitted when field is defined in one of the parent models

[Django]

#12531: Model field name 'hiding' should not be permitted when field is defined 
in
one of the parent models
-+-
 Reporter:  parxier  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.1
  (models, ORM)  |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

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


Comment:

 Duplicate of #17673

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

Re: [Django] #22401: SQL Function initial SQL data does not work.

[Django]

#22401: SQL Function initial SQL data does not work.
-+-
 Reporter:  pouete   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"47927eb786f432cb069f0b00fd810c465a78fd71"]:
 {{{
 #!CommitTicketReference repository=""
 revision="47927eb786f432cb069f0b00fd810c465a78fd71"
 Revert "Fixed #22401 -- Deprecated regular expression parsing of initial
 SQL in favor of installing sqlparse."

 This reverts commit 071c9337750b296d198cced56f3ffad0e176afb6.

 This introduced a regression on MySQL and custom SQL is deprecated.
 }}}

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

[django/django] 47927e: Revert "Fixed #22401 -- Deprecated regular express...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 47927eb786f432cb069f0b00fd810c465a78fd71
  
https://github.com/django/django/commit/47927eb786f432cb069f0b00fd810c465a78fd71
  Author: Tim Graham 
  Date:   2014-04-16 (Wed, 16 Apr 2014)

  Changed paths:
M django/core/management/sql.py
M docs/howto/initial-data.txt
M docs/internals/contributing/writing-code/unit-tests.txt
M docs/internals/deprecation.txt
M docs/releases/1.8.txt
M tests/requirements/base.txt

  Log Message:
  ---
  Revert "Fixed #22401 -- Deprecated regular expression parsing of initial SQL 
in favor of installing sqlparse."

This reverts commit 071c9337750b296d198cced56f3ffad0e176afb6.

This introduced a regression on MySQL and custom SQL is deprecated.


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

Re: [Django] #22463: Inconsistent code style in HTML, JavaScript, and CSS files

[Django]

#22463: Inconsistent code style in HTML, JavaScript, and CSS files
-+-
 Reporter:  treyhunner   |Owner:
 Type:   |  treyhunner
  Cleanup/optimization   |   Status:  assigned
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
-+-
Changes (by russellm):

 * stage:  Unreviewed => Accepted


Comment:

 Accepted on the principle that we Flake8 our Python code; linting our
 JavaScript would also seem prudent. The only decision is the choice of
 linter. [https://groups.google.com/d/msgid/django-
 
developers/CACuWcAwrCq_q4%2BFkKOVU5nqokSSgM7wqzXPbo%2BKJh0U%3DY1ecVA%40mail.gmail.com?utm_medium=email&utm_source=footer
 See this django-dev thread for 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/068.802b2e2c162abd9aff366bda08bef132%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #15419: initial sql files need better warnings

[Django]

#15419: initial sql files need better warnings
-+-
 Reporter:  joel3000 |Owner:
 Type:  Bug  |  marcosmoyano
Component:  Database layer   |   Status:  closed
  (models, ORM)  |  Version:  1.2
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  initial sql  | 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):

 * status:  assigned => closed
 * needs_better_patch:  0 => 1
 * resolution:   => wontfix


Comment:

 Now that we have migrations, initial SQL is deprecated.

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

Re: [Django] #22378: \d in urls examples in documentation is missleading.

[Django]

#22378: \d in urls examples in documentation is missleading.
-+-
 Reporter:  tomwys   |Owner:
 Type:   |  chriscauley
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"66ec9ee441618894c1ccebdcdd5eb4d7fbf4a6d3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="66ec9ee441618894c1ccebdcdd5eb4d7fbf4a6d3"
 Fixed #22378 -- Updated \d to [0-9]+ in urlpatterns of docs and tests.

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

[django/django] 66ec9e: Fixed #22378 -- Updated \d to [0-9]+ in urlpattern...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 66ec9ee441618894c1ccebdcdd5eb4d7fbf4a6d3
  
https://github.com/django/django/commit/66ec9ee441618894c1ccebdcdd5eb4d7fbf4a6d3
  Author: chriscauley 
  Date:   2014-04-16 (Wed, 16 Apr 2014)

  Changed paths:
M docs/intro/overview.txt
M docs/intro/tutorial03.txt
M docs/intro/tutorial04.txt
M docs/ref/class-based-views/base.txt
M docs/ref/class-based-views/generic-date-based.txt
M docs/ref/contrib/syndication.txt
M docs/ref/forms/fields.txt
M docs/ref/models/instances.txt
M docs/ref/templates/builtins.txt
M docs/ref/urls.txt
M docs/topics/cache.txt
M docs/topics/class-based-views/generic-display.txt
M docs/topics/class-based-views/generic-editing.txt
M docs/topics/class-based-views/mixins.txt
M docs/topics/http/urls.txt
M tests/contenttypes_tests/urls.py
M tests/fixtures_regress/tests.py
M tests/forms_tests/tests/test_error_messages.py
M tests/forms_tests/tests/test_fields.py
M tests/forms_tests/tests/test_forms.py
M tests/forms_tests/urls.py
M tests/generic_views/urls.py
M tests/model_formsets/tests.py
M tests/template_tests/urls.py
M tests/test_utils/urls.py
M tests/urlpatterns_reverse/extra_urls.py
M tests/urlpatterns_reverse/included_named_urls.py
M tests/urlpatterns_reverse/included_named_urls2.py
M tests/urlpatterns_reverse/included_namespace_urls.py
M tests/urlpatterns_reverse/included_no_kwargs_urls.py
M tests/urlpatterns_reverse/included_urls.py
M tests/urlpatterns_reverse/named_urls.py
M tests/urlpatterns_reverse/namespace_urls.py
M tests/urlpatterns_reverse/urls.py
M tests/utils_tests/test_jslex.py
M tests/version/tests.py
M tests/view_tests/tests/test_debug.py
M tests/view_tests/urls.py

  Log Message:
  ---
  Fixed #22378 -- Updated \d to [0-9]+ in urlpatterns of docs and tests.

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

Re: [Django] #22220: reverse() documentation

[Django]

#0: reverse() documentation
-+-
 Reporter:  EvilDMP  |Owner:
 Type:   |  bendavis78
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"e0930608230fc7e1f1a68d51296661200857658a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e0930608230fc7e1f1a68d51296661200857658a"
 [1.6.x] Fixed #0 -- Added more examples to reverse() documention.

 Thanks EvilDMP for the suggestions.

 Backport of 030dd4f72c 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/065.f280989b790972828093b54495c80886%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 8c1d8a: [1.7.x] Fixed #22220 -- Added more examples to rev...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 8c1d8a6215b123f2d0981f926db1f0405392ae5f
  
https://github.com/django/django/commit/8c1d8a6215b123f2d0981f926db1f0405392ae5f
  Author: Ben Davis 
  Date:   2014-04-16 (Wed, 16 Apr 2014)

  Changed paths:
M docs/ref/urlresolvers.txt

  Log Message:
  ---
  [1.7.x] Fixed #0 -- Added more examples to reverse() documention.

Thanks EvilDMP for the suggestions.

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

Re: [Django] #22220: reverse() documentation

[Django]

#0: reverse() documentation
-+-
 Reporter:  EvilDMP  |Owner:
 Type:   |  bendavis78
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"8c1d8a6215b123f2d0981f926db1f0405392ae5f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8c1d8a6215b123f2d0981f926db1f0405392ae5f"
 [1.7.x] Fixed #0 -- Added more examples to reverse() documention.

 Thanks EvilDMP for the suggestions.

 Backport of 030dd4f72c 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/065.bd3dfdca3c0259d8ead6d0529888dfe0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] e09306: [1.6.x] Fixed #22220 -- Added more examples to rev...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: e0930608230fc7e1f1a68d51296661200857658a
  
https://github.com/django/django/commit/e0930608230fc7e1f1a68d51296661200857658a
  Author: Ben Davis 
  Date:   2014-04-16 (Wed, 16 Apr 2014)

  Changed paths:
M docs/ref/urlresolvers.txt

  Log Message:
  ---
  [1.6.x] Fixed #0 -- Added more examples to reverse() documention.

Thanks EvilDMP for the suggestions.

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

[django/django] 030dd4: Fixed #22220 -- Added more examples to reverse() d...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 030dd4f72ca4d84c0a5e09ee625123d03651fdd1
  
https://github.com/django/django/commit/030dd4f72ca4d84c0a5e09ee625123d03651fdd1
  Author: Ben Davis 
  Date:   2014-04-16 (Wed, 16 Apr 2014)

  Changed paths:
M docs/ref/urlresolvers.txt

  Log Message:
  ---
  Fixed #0 -- Added more examples to reverse() documention.

Thanks EvilDMP for the suggestions.


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

Re: [Django] #22220: reverse() documentation

[Django]

#0: reverse() documentation
-+-
 Reporter:  EvilDMP  |Owner:
 Type:   |  bendavis78
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"030dd4f72ca4d84c0a5e09ee625123d03651fdd1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="030dd4f72ca4d84c0a5e09ee625123d03651fdd1"
 Fixed #0 -- Added more examples to reverse() documention.

 Thanks EvilDMP for the suggestions.
 }}}

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

Re: [Django] #21644: FormWizard needs confirmation step logic

[Django]

#21644: FormWizard needs confirmation step logic
---+
 Reporter:  nickname123|Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Generic views  |  Version:  1.6
 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 nickname123):

 Replying to [comment:10 Fabio Caritas Barrionuevo da Luz ]:
 > nickname123 you have a test project that uses its implementation on
 github? If not, you could create it? I would test it

 I will have some time in two weeks to put a demo together.  I do not have
 anything together in a shareable state at this time.

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

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

Re: [Django] #22454: Confusing message id=1_6.W001

[Django]

#22454: Confusing message id=1_6.W001
--+
 Reporter:  pgcd  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (System checks)  |  Version:  1.6
 Severity:  Release blocker   |   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 russellm):

 * severity:  Normal => Release blocker
 * needs_better_patch:   => 0
 * component:  Documentation => Core (System checks)
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 Fair point - The message doesn't mention the TEST_RUNNER setting, and the
 link provided in the message points at the release note describing the new
 feature, rather than the backwards compatibility guide saying how to
 compensate for the problem. There's a link from the release note _to_ the
 backwards compatibility guide, but that's a step that a user shouldn't
 have to make.

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

Re: [Django] #22090: ModelAdmin list_filter field member values are serialized using __str__ and not __repr__

[Django]

#22090: ModelAdmin list_filter field member values are serialized using __str__ 
and
not __repr__
-+-
 Reporter:  sam@…|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.6
Component:  contrib.admin|   Resolution:  needsinfo
 Severity:  Normal   | Triage Stage:
 Keywords:  admin, list_filter   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by bmispelon):

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


Comment:

 I've also tried and failed to reproduce the problem described in this
 ticket.

 Can you provide some code example that demonstrate your issue?

 Thanks.

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

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

Re: [Django] #21227: Selenium tests terminate with [Errno 10054]

[Django]

#21227: Selenium tests terminate with [Errno 10054]
---+
 Reporter:  marfire|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  selenium   | 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):

 For anyone looking to repro this, here's a single test case that shows the
 error:

 python runtests.py --selenium
 admin_widgets.tests.DateTimePickerSeleniumFirefoxTests

 be aware that if this PR on logging gets accepted
 
(https://github.com/jmbowman/django/commit/c34c5860d4e842e62574657ec61a125bc91b6c0f)
 then the error will no longer be visible on stdout.  If I get time I'll
 try and build some kind of specific failing test for just 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/065.b1093f733de065c7a1395f1aa5112215%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22434: Ordering is cleared in Subqueries with limits

[Django]

#22434: Ordering is cleared in Subqueries with limits
-+-
 Reporter:  maciej.pawlisz@… |Owner:
 Type:  Bug  |  justhamade
Component:  Database layer   |   Status:  closed
  (models, ORM)  |  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
-+-

Comment (by Simon Charette ):

 In [changeset:"7f8bd1a4b39ed834dffa0adc8fa19ef6b807f45d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7f8bd1a4b39ed834dffa0adc8fa19ef6b807f45d"
 [1.7.x] Fixed #22434 -- Retain ordering on related sliced subqueries.

 Thanks maciej.pawlisz for the report, and charettes for the review.

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

[django/django] 7f8bd1: [1.7.x] Fixed #22434 -- Retain ordering on related...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 7f8bd1a4b39ed834dffa0adc8fa19ef6b807f45d
  
https://github.com/django/django/commit/7f8bd1a4b39ed834dffa0adc8fa19ef6b807f45d
  Author: Justin Hamade 
  Date:   2014-04-16 (Wed, 16 Apr 2014)

  Changed paths:
M django/db/models/sql/where.py
M tests/queries/tests.py

  Log Message:
  ---
  [1.7.x] Fixed #22434 -- Retain ordering on related sliced subqueries.

Thanks maciej.pawlisz for the report, and charettes for the review.

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

[django/django] a13df6: Fixed #22434 -- Retain ordering on related sliced ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a13df671a5a5b867397ce05f73a59a3f4504868a
  
https://github.com/django/django/commit/a13df671a5a5b867397ce05f73a59a3f4504868a
  Author: Justin Hamade 
  Date:   2014-04-16 (Wed, 16 Apr 2014)

  Changed paths:
M django/db/models/sql/where.py
M tests/queries/tests.py

  Log Message:
  ---
  Fixed #22434 -- Retain ordering on related sliced subqueries.

Thanks maciej.pawlisz for the report, and charettes 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/534efccf8020a_55416a9d34929c8%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22434: Ordering is cleared in Subqueries with limits

[Django]

#22434: Ordering is cleared in Subqueries with limits
-+-
 Reporter:  maciej.pawlisz@… |Owner:
 Type:  Bug  |  justhamade
Component:  Database layer   |   Status:  closed
  (models, ORM)  |  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 Simon Charette ):

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


Comment:

 In [changeset:"a13df671a5a5b867397ce05f73a59a3f4504868a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a13df671a5a5b867397ce05f73a59a3f4504868a"
 Fixed #22434 -- Retain ordering on related sliced subqueries.

 Thanks maciej.pawlisz for the report, and charettes 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/083.42e8ae03faa025d2b46e619888e6dd02%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22455: send_mail/send_messages do not document the return value

[Django]

#22455: send_mail/send_messages do not document the return value
--+
 Reporter:  mark0978  |Owner:  mrezk
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Baptiste Mispelon ):

 In [changeset:"841e21a85c17c87f8b7b41b5cbb5eae15888f9b7"]:
 {{{
 #!CommitTicketReference repository=""
 revision="841e21a85c17c87f8b7b41b5cbb5eae15888f9b7"
 [1.7.x] Fixed #22455 -- Documented return values for send_mail and
 send_mass_mail

 Backport of 7cd74fc96ee982acfed7a98e76d4623eabde146d from master.
 }}}

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

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

[django/django] 841e21: [1.7.x] Fixed #22455 -- Documented return values f...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 841e21a85c17c87f8b7b41b5cbb5eae15888f9b7
  
https://github.com/django/django/commit/841e21a85c17c87f8b7b41b5cbb5eae15888f9b7
  Author: Mariano Rezk 
  Date:   2014-04-16 (Wed, 16 Apr 2014)

  Changed paths:
M docs/topics/email.txt

  Log Message:
  ---
  [1.7.x] Fixed #22455 -- Documented return values for send_mail and 
send_mass_mail

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

Re: [Django] #22455: send_mail/send_messages do not document the return value

[Django]

#22455: send_mail/send_messages do not document the return value
--+
 Reporter:  mark0978  |Owner:  mrezk
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Baptiste Mispelon ):

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


Comment:

 In [changeset:"7cd74fc96ee982acfed7a98e76d4623eabde146d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7cd74fc96ee982acfed7a98e76d4623eabde146d"
 Fixed #22455 -- Documented return values for send_mail and send_mass_mail
 }}}

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

[django/django] 7cd74f: Fixed #22455 -- Documented return values for send_...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 7cd74fc96ee982acfed7a98e76d4623eabde146d
  
https://github.com/django/django/commit/7cd74fc96ee982acfed7a98e76d4623eabde146d
  Author: Mariano Rezk 
  Date:   2014-04-16 (Wed, 16 Apr 2014)

  Changed paths:
M docs/topics/email.txt

  Log Message:
  ---
  Fixed #22455 -- Documented return values for send_mail and send_mass_mail


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

Re: [Django] #22455: send_mail/send_messages do not document the return value

[Django]

#22455: send_mail/send_messages do not document the return value
--+
 Reporter:  mark0978  |Owner:  mrezk
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by mrezk):

 Pull request updated.

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

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

Re: [Django] #22463: Inconsistent code style in HTML, JavaScript, and CSS files

[Django]

#22463: Inconsistent code style in HTML, JavaScript, and CSS files
-+-
 Reporter:  treyhunner   |Owner:
 Type:   |  treyhunner
  Cleanup/optimization   |   Status:  assigned
Component:  Uncategorized|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by treyhunner):

 I added a (nearly empty) .jshintrc file to the pull request.  The
 preferred code style should be decided (I prefer the default JSHint style)
 and the existing code should be modified to adhere to the style.

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

Re: [Django] #22455: send_mail/send_messages do not document the return value

[Django]

#22455: send_mail/send_messages do not document the return value
--+
 Reporter:  mark0978  |Owner:  mrezk
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by mrezk):

 Pull request updated. Please feel free to make any subtle comments about
 style!

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

Re: [Django] #22351: New django migrations and places where lambdas are supposed

[Django]

#22351: New django migrations and places where lambdas are supposed
--+
 Reporter:  dimyur27@…|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  migrations lambdas| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by chriscauley):

 I thought you specifically were having a problem with `limit_choices_to`.
 That makes more sense. `upload_to` is addressed in #22436 where
 `SomeClass.some_method` breaks in the same way. The solution there will
 fix lambdas as well.

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

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

Re: [Django] #22455: send_mail/send_messages do not document the return value

[Django]

#22455: send_mail/send_messages do not document the return value
--+
 Reporter:  mark0978  |Owner:  mrezk
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by mrezk):

 * needs_better_patch:  1 => 0


Comment:

 Pull request updated.

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

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

Re: [Django] #22462: Loading issue of models declared in tests.py due to a combination of AdminConfig, System checks, and Model._meta caching.

[Django]

#22462: Loading issue of models declared in tests.py due to a combination of
AdminConfig, System checks, and Model._meta caching.
-+
 Reporter:  loic84   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by charettes):

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


Comment:

 Well there's definitely something to fix here, do you think this could be
 related to #22459?

 What about starting by making `select_related` complain when a non-
 existing field is referenced?

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

[django/django] 79f056: Fixed flake8 warnings introduced in recent commits...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 79f05616fbf48cf7c205ef17666af0c3d47b3c1e
  
https://github.com/django/django/commit/79f05616fbf48cf7c205ef17666af0c3d47b3c1e
  Author: Simon Charette 
  Date:   2014-04-16 (Wed, 16 Apr 2014)

  Changed paths:
M django/db/backends/postgresql_psycopg2/base.py
M tests/get_or_create/tests.py
M tests/prefetch_related/tests.py
M tests/test_discovery_sample/doctests.py
M tests/test_runner/test_discover_runner.py

  Log Message:
  ---
  Fixed flake8 warnings introduced in recent commits.


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

Re: [Django] #22463: Inconsistent code style in HTML, JavaScript, and CSS files

[Django]

#22463: Inconsistent code style in HTML, JavaScript, and CSS files
-+-
 Reporter:  treyhunner   |Owner:
 Type:   |  treyhunner
  Cleanup/optimization   |   Status:  assigned
Component:  Uncategorized|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by treyhunner):

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

[django/django] 71c8ae: [1.7.x] Fixed #22460 -- Explicity remove constrain...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 71c8ae543ffec847ec275859bc406202f5029604
  
https://github.com/django/django/commit/71c8ae543ffec847ec275859bc406202f5029604
  Author: Motiejus Jakštys 
  Date:   2014-04-16 (Wed, 16 Apr 2014)

  Changed paths:
M django/db/backends/schema.py
M tests/migrations/test_operations.py

  Log Message:
  ---
  [1.7.x] Fixed #22460 -- Explicity remove constraints when dropping a related 
field.

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

Re: [Django] #22460: Fix of removal of a ForeignKey field in a migration in MySQL

[Django]

#22460: Fix of removal of a ForeignKey field in a migration in MySQL
+
 Reporter:  motiejus|Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by Simon Charette ):

 In [changeset:"71c8ae543ffec847ec275859bc406202f5029604"]:
 {{{
 #!CommitTicketReference repository=""
 revision="71c8ae543ffec847ec275859bc406202f5029604"
 [1.7.x] Fixed #22460 -- Explicity remove constraints when dropping a
 related field.

 Backport of 0e45669fa9 from master
 }}}

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

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

Re: [Django] #22448: django test command runs wrong tests if test module has no tests

[Django]

#22448: django test command runs wrong tests if test module has no tests
-+-
 Reporter:  cjerdonek|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  test discovery,test  | Triage Stage:
  runner,test command,test label |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by cjerdonek):

 Thanks for putting the test case together!  I ran it and got 0 tests, too.
 But then I realized it's not discovering tests because the filenames don't
 match the default test pattern.  When I renamed the files to `test_bar.py`
 and `test_car.py`, I was able to reproduce the problem.  (Sorry, I
 probably should have said `foo.test_bar` in my original test above.)

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

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

Re: [Django] #22463: Inconsistent code style in HTML, JavaScript, and CSS files

[Django]

#22463: Inconsistent code style in HTML, JavaScript, and CSS files
-+-
 Reporter:  treyhunner   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Uncategorized|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by treyhunner):

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


Comment:

 I started a pull request for this ticket here:
 https://github.com/django/django/pull/2577

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

Re: [Django] #22464: 1.7b1 tarball missing contrib/gis/static

[Django]

#22464: 1.7b1 tarball missing contrib/gis/static
-+--
 Reporter:  michael@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Packaging|  Version:  1.7-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by bmispelon):

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


Comment:

 Hi,

 I have no idea why that's happening, but we should definitely fix this for
 the final release.

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

Re: [Django] #22455: send_mail/send_messages do not document the return value

[Django]

#22455: send_mail/send_messages do not document the return value
--+
 Reporter:  mark0978  |Owner:  mrezk
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+

Comment (by mrezk):

 I thought that since I've never seen an example of `send_mail` which takes
 in account the return value, it may be nice to clarify this.

 If you don't think that it may be misleading that none of the examples
 checks the return value, then it is OK for me to take it away =)

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

Re: [Django] #22455: send_mail/send_messages do not document the return value

[Django]

#22455: send_mail/send_messages do not document the return value
--+
 Reporter:  mark0978  |Owner:  mrezk
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+

Comment (by bmispelon):

 You're absolutely right (I got too far down the rabbit hole of figuring
 out what the return value was and forgot it was `send_message` we were
 documenting).

 Do we really need the "though generally ignored..." bit?

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

[Django] #22464: 1.7b1 tarball missing contrib/gis/static

[Django]

#22464: 1.7b1 tarball missing contrib/gis/static
+
 Reporter:  michael@…   |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Packaging   |Version:  1.7-beta-1
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 The tar download at https://www.djangoproject.com/download/1.7b1/tarball/
 does not contain a django/contrib/gis/static directory.

 This is present in the source:
 
https://github.com/django/django/tree/stable/1.7.x/django/contrib/gis/static/gis/js

 Without the JS file contained here, OLMapWidget.js, geospatial fields do
 not appear in the admin.

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

Re: [Django] #22455: send_mail/send_messages do not document the return value

[Django]

#22455: send_mail/send_messages do not document the return value
--+
 Reporter:  mark0978  |Owner:  mrezk
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+

Comment (by mrezk):

 Hi,

 That is true, but I am actually documenting `send_mail`. As far as I know,
 you can only send 0 or 1 emails with that method, is there a way to send
 more than 1 email with that method?

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

Re: [Django] #22455: send_mail/send_messages do not document the return value

[Django]

#22455: send_mail/send_messages do not document the return value
--+
 Reporter:  mark0978  |Owner:  mrezk
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by bmispelon):

 * needs_better_patch:  0 => 1


Comment:

 Hi,

 The sentence you added is incorrect: `send_messages` returns the number of
 emails sent (which is potentially 0).

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

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

Re: [Django] #22460: Fix of removal of a ForeignKey field in a migration in MySQL

[Django]

#22460: Fix of removal of a ForeignKey field in a migration in MySQL
+
 Reporter:  motiejus|Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by Simon Charette ):

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


Comment:

 In [changeset:"0e45669fa9eb82c6de8e226c6da53ab5e88575f5"]:
 {{{
 #!CommitTicketReference repository=""
 revision="0e45669fa9eb82c6de8e226c6da53ab5e88575f5"
 Fixed #22460 -- Explicity remove constraints when dropping a related
 field.
 }}}

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

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

[django/django] 0e4566: Fixed #22460 -- Explicity remove constraints when ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 0e45669fa9eb82c6de8e226c6da53ab5e88575f5
  
https://github.com/django/django/commit/0e45669fa9eb82c6de8e226c6da53ab5e88575f5
  Author: Motiejus Jakštys 
  Date:   2014-04-16 (Wed, 16 Apr 2014)

  Changed paths:
M django/db/backends/schema.py
M tests/migrations/test_operations.py

  Log Message:
  ---
  Fixed #22460 -- Explicity remove constraints when dropping a related field.


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

[Django] #22463: Inconsistent code style in HTML, JavaScript, and CSS files

[Django]

#22463: Inconsistent code style in HTML, JavaScript, and CSS files
--+
 Reporter:  treyhunner|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Uncategorized |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 There are multiple inconsistent code styles used throughout the Django
 project.

 It appears that the overall preferred style for HTML is 2 spaces,
 JavaScript is 2 or 4 spaces (and sometimes tabs) and CSS is 4 spaces.

 It seems that all files should have newlines at the end and whitespace
 should be trimmed from the end of each line.

 I am currently working on discovering the existing code style, fixing
 obvious unintended inconsistencies, and creating a .editorconfig file to
 document the expectations for future code changes.

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

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

Re: [Django] #22455: send_mail/send_messages do not document the return value

[Django]

#22455: send_mail/send_messages do not document the return value
--+
 Reporter:  mark0978  |Owner:  mrezk
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by mrezk):

 * has_patch:  0 => 1


Comment:

 Pull request created: https://github.com/django/django/pull/2576

 I found out that actually `send_messages` is documented on this section:
 https://docs.djangoproject.com/en/dev/topics/email/#defining-a-custom-
 email-backend, do you think we should add more information somewhere else?

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

Re: [Django] #22397: Issues removing M2M field with explicit through model

[Django]

#22397: Issues removing M2M field with explicit through model
-+
 Reporter:  melinath |Owner:  andrewsg
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by andrewsg):

 Fix submitted as https://github.com/django/django/pull/2575

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

Re: [Django] #9894: Give the FileField 'upload_to' callable access to an UploadedFile's contents.

[Django]

#9894: Give the FileField 'upload_to' callable access to an UploadedFile's
contents.
-+-
 Reporter:  Pyth |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  File |  Version:  1.0
  uploads/storage|   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  feature upload_to|  Needs documentation:  1
  FileField  |  Patch needs improvement:  1
Has patch:  0|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-

Comment (by dmckeone):

 To avoid the issue with potentially discarding a valid TypeError here this
 implementation could potentially be used in conjunction with a change of
 the generate_filename signature to include a content= keyword argument:

 {{{
 #!python
 def save(self, name, content, save=True):
 try:
 inspect.getcallargs(self.field.generate_filename,
 self.instance, name, content=content)
 except TypeError:
 # Possibly make some kind of Deprecation Warning
 name = self.field.generate_filename(self.instance, name)
 else:
 name = self.field.generate_filename(self.instance, name,
 content=content)
 }}}

 The benefit of this implementation is that an old version of the
 `upload_to=` callback will continue to function as it had in the past, but
 Django can now emit a deprecation warning of some kind (deferring an
 eventual API change).  Using `inspect.getcallargs` works in both Python 2
 and 3, and it only tests the binding of the arguments to the function,
 without actually calling the function.

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

Re: [Django] #22460: Fix of removal of a ForeignKey field in a migration in MySQL

[Django]

#22460: Fix of removal of a ForeignKey field in a migration in MySQL
+
 Reporter:  motiejus|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by charettes):

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

Re: [Django] #22452: VIEW PERMISSIONS

[Django]

#22452: VIEW PERMISSIONS
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.6
 Severity:  Normal |   Resolution:  duplicate
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by timo):

 Please use our support channels for usage questions.

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

Re: [Django] #22444: conflicting docs regarding initial_data loading

[Django]

#22444: conflicting docs regarding initial_data loading
-+--
 Reporter:  kmtracey |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  1.7-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+--

Comment (by timo):

 I believe "Providing initial SQL data" should also be marked as deprecated
 for the same reasons.

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

Re: [Django] #22401: SQL Function initial SQL data does not work.

[Django]

#22401: SQL Function initial SQL data does not work.
-+-
 Reporter:  pouete   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * status:  closed => new
 * severity:  Normal => Release blocker
 * needs_better_patch:  1 => 0
 * version:  1.6 => master
 * has_patch:  1 => 0
 * resolution:  fixed =>


Comment:

 There's a regression here because `sqlparse` does not strip trailing
 comments the way the regex does (see #4680 for when this behavior was
 added). `tests/initial_sql_regress/sql/simple.sql` contains a trailing
 comment on line 2 and this causes MySQL to error out with "Commands out of
 sync; you can't run this command now". Jenkins doesn't have `sqlparse`
 installed, so it's still using the regex logic.

 You can reproduce this behavior with the following code:
 {{{
 >>> from django.db import connection
 >>> cursor = connection.cursor()
 >>> cursor.execute("SELECT 1; --")
 >>> cursor.execute("SELECT 2;")
 Traceback ...
 django.db.utils.ProgrammingError: (2014, "Commands out of sync; you can't
 run this command now")
 }}}

 I've realized that initial SQL data is deprecated (pending confirmation
 from Andrew Godwin in #22444) so I'm inclined just to revert this and mark
 it "won't fix".

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

[Django] #22462: Loading issue of models declared in tests.py due to a combination of AdminConfig, System checks, and Model._meta caching.

[Django]

#22462: Loading issue of models declared in tests.py due to a combination of
AdminConfig, System checks, and Model._meta caching.
-+
 Reporter:  loic84   |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Core (Other) |Version:  master
 Severity:  Release blocker  |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 I just had a very weird problem with my test suite, where calls to
 `select_related` didn't seem to work and busted every `assertNumQueries`
 while still returning correct values. This only happened for models
 defined in `tests.py` which inherited from models from another app's
 `models.py`.

 {{{
 app:
 models.py
 class A(models.Model):
 pass
 admin.py
 @admin.register(A)
 class AAdmin(admin.ModelAdmin):
 list_filters = 'id',
 app2:
 tests.py
 class B(A):
 pass
 }}}

 The problem turned out to be that the various caches in `A._meta` were
 wrong (those used by `get_field_by_name()` and friends). Calls to
 `select_related('b')` were silently ignored (because that's what
 `select_related` do for non-existing relations) but calls to
 `filter(b=something)` would have failed with a `FieldError ` despite `A`
 having the `A.b` descriptor.

 Here is how the cache got to hold the wrong values:

 - `Apps.populate()` calls `AdminConfig.ready()`.
 - `AdminConfig.ready()` calls `autodiscover()`.
 - `autodiscover()` causes `AAdmin` to register, which in turn triggers
 `ModelAdmin.check()`.
 - `ModelAdmin.check()` inspects the model fields and fills up the caches
 in `_meta` by doing so.
 - `app2.tests.B` is loaded but it's already too late.

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

Re: [Django] #22447: Migrations have bases=(NewBase, ) for models with custom metaclass

[Django]

#22447: Migrations have bases=(NewBase,) for models with custom metaclass
-+--
 Reporter:  cdestigter   |Owner:  charettes
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by charettes):

 It doesn't work in the `mttp` case because they skip `ModelBase.__new__`
 [https://github.com/django-mptt/django-
 mptt/blob/master/mptt/models.py#L217-L218 here], it would work if they
 called `super(MPTTModelBase, cls).__new__` instead.

 Unsure how to deal correctly with this.
 [https://bitbucket.org/gutworth/six/issue/66/replace-the-implementation-of
 I've proposed] `six` to replace their `with_metaclass` implementation with
 
[https://github.com/mitsuhiko/flask/blob/6ec83e18dca497a8fbfca6caca584bd32f2e/flask/_compat.py#L56-L73
 the one Flask uses] in order to prevent those `NewBase` artifacts. I ran
 the full test suite with this modified version and it fully passed.

 Fixing the issue at this level makes more sense me than trying to work
 around it by `__mro__` and `__dict__` checks.

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

Re: [Django] #21587: Make generic RedirectView default to permanent=False

[Django]

#21587: Make generic RedirectView default to permanent=False
--+
 Reporter:  wraus@…   |Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Generic views |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:  redirect, view| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by gregloy):

 * status:  assigned => new
 * owner:  gregloy =>


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

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

Re: [Django] #22461: condition decorator: support fo if-unmodified-since and updating etags

[Django]

#22461: condition decorator: support fo if-unmodified-since and updating etags
---+--
 Reporter:  tanner |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by tanner):

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


Comment:

 pull request https://github.com/django/django/pull/2573

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

Re: [Django] #22423: Geodjango spatial functions should leverage mysql 5.6 spatial functions.

[Django]

#22423: Geodjango spatial functions should leverage mysql 5.6 spatial functions.
-+
 Reporter:  visu |Owner:  visu
 Type:  New feature  |   Status:  new
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  gis, mysql,  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by visu):

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


Comment:

 Hi,

 I sent a pull request.  Please review and let me know.
 I attached a unit test in the pull request as well.

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

 thanks,
 Visu M

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

Re: [Django] #22452: VIEW PERMISSIONS

[Django]

#22452: VIEW PERMISSIONS
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.6
 Severity:  Normal |   Resolution:  duplicate
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by anonymous):

 Replying to [comment:5 timo]:
 > As a feature request, this is a duplicate of #820 and #8936.

 timo thank you for quick response :) ... one more thing i want to ask..
 see there is django databrowse and what i want is to ad view permission
 for all models in admin panel, so by simply selecting user and assigning
 him a view request he will be able to login and to view all admin section
 without adding, creating and deleting any thing. Django Databrowse has
 this same functionality?
 '''UPDATE TO ABOVE COMMENT :'''

 i want to make all login and performed transactions visible to users
 having view permission. can databrowse do this thing?

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

Re: [Django] #22452: VIEW PERMISSIONS

[Django]

#22452: VIEW PERMISSIONS
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.6
 Severity:  Normal |   Resolution:  duplicate
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by anonymous):

 Replying to [comment:5 timo]:
 > As a feature request, this is a duplicate of #820 and #8936.



 timo thank you for quick response :) ... one more thing i want to ask..
 see there is django databrowse and what i want is to ad view permission
 for all models in admin panel, so by simply selecting user and assigning
 him a view request he will be able to login and to view all admin section
 without adding, creating and deleting any thing. Django Databrowse has
 this same functionality?

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

[Django] #22461: condition decorator: support fo if-unmodified-since and updating etags

[Django]

#22461: condition decorator: support fo if-unmodified-since and updating etags
---+
 Reporter:  tanner |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  HTTP handling  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  0  |  UI/UX:  0
---+
 I have implemented support for the If-Unmodified-Since header
 http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.28
 in the condition decorator and added an parameter to support updating
 of the etags for write operations
 http://tools.ietf.org/id/draft-reschke-http-etag-on-write-09.txt

 tests are included

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

Re: [Django] #21936: Add delete message mixin

[Django]

#21936: Add delete message mixin
-+-
 Reporter:  david.fischer.ch@…   |Owner:
 Type:  New feature  |  CarolineSimpson
Component:  contrib.messages |   Status:  assigned
 Severity:  Normal   |  Version:  master
 Keywords:  mixin|   Resolution:
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  1|  Needs documentation:  1
Easy pickings:  0|  Patch needs improvement:  1
 |UI/UX:  0
-+-
Changes (by CarolineSimpson):

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

Re: [Django] #22455: send_mail/send_messages do not document the return value

[Django]

#22455: send_mail/send_messages do not document the return value
--+
 Reporter:  mark0978  |Owner:  mrezk
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.6
 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 mrezk):

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


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

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

Re: [Django] #22351: New django migrations and places where lambdas are supposed

[Django]

#22351: New django migrations and places where lambdas are supposed
--+
 Reporter:  dimyur27@…|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  migrations lambdas| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by dimyur27@…):

 When instead of get_user_picture_path there was a lambda, it refused to do
 "makemigrations".
 {{{
 class MyModel(models.Model):

 picture = models.ImageField(
 upload_to=get_user_picture_path,
 blank=True,
 )

 }}}

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

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

Re: [Django] #21587: Make generic RedirectView default to permanent=False

[Django]

#21587: Make generic RedirectView default to permanent=False
--+
 Reporter:  wraus@…   |Owner:  gregloy
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Generic views |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:  redirect, view| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by bmispelon):

 * needs_better_patch:  0 => 1
 * easy:  1 => 0


Comment:

 As noted in the comment on the PR, the current approach would still raise
 a warning in this case:
 {{{#!python
 class CustomRedirectView(RedirectView):
 permanent = False
 }}}

 I think we could fix this with this approach:
 {{{#!python
 _sentinel = object()

 class RedirectView(View):
 permanent = _sentinel  # empty objects evaluate to True
 ...
 def __init__(self, **kwargs):
 if 'permanent' not in kwargs and self.permanent is _sentinel:
 # raise deprecation warning
 ...
 }}}

 The tricky part then becomes writing a check for this (which is necessary
 at this point since we're making a subtle change to a default behavior)
 and I'm not sure exactly how to approach this.

 In any case, I'm removing the `easy pickings` flag.

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

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

Re: [Django] #22336: Impossible to exclude specific subdirectories with makemessages

[Django]

#22336: Impossible to exclude specific subdirectories with makemessages
-+-
 Reporter:  infraredgirl |Owner:
 Type:  Bug  |  justhamade
Component:  Core (Management |   Status:  assigned
  commands)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by justhamade):

 Created pull request https://github.com/django/django/pull/2572

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

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

Re: [Django] #22336: Impossible to exclude specific subdirectories with makemessages

[Django]

#22336: Impossible to exclude specific subdirectories with makemessages
-+-
 Reporter:  infraredgirl |Owner:
 Type:  Bug  |  justhamade
Component:  Core (Management |   Status:  assigned
  commands)  |  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 justhamade):

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

[Django] #22460: Fix of removal of a ForeignKey field in a migration in MySQL

[Django]

#22460: Fix of removal of a ForeignKey field in a migration in MySQL
+
 Reporter:  motiejus|  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  master
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  1
Easy pickings:  0   |  UI/UX:  0
+
 Consider the following:

 1. A model has a ForeignKey() field.
 2. Migration tries to remove it.
 3. BAM! in MySQL:

 {{{
 OperationalError: (1025, "Error on rename of './test_myapp/test_rfk_rider'
 to './test_myapp/#sql2-3398-2e8' (errno: 152)")
 }}}

 Here is a patch with a regression test:
 https://github.com/django/django/pull/2571

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

[Django] #22459: Creating model classes for test purposes breaks migrations

[Django]

#22459: Creating model classes for test purposes breaks migrations
---+
 Reporter:  pgcd   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Migrations |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Defining a model class in a test file like this:

 {{{
 class BasicModel(models.Model):
 title = models.CharField(max_length=255)
 }}}

 results in the test breaking immediately with a CommandError:

 {{{
 CommandError: Database test_db couldn't be flushed. Possible reasons:
   * The database isn't running or isn't configured correctly.
   * At least one of the expected database tables doesn't exist.
   * The SQL was invalid.
 Hint: Look at the output of 'django-admin.py sqlflush'. That's the SQL
 this command wasn't able to run.
 The full error: relation "appname_basicmodel" does not exist
 }}}

 Since it is no longer possible to disable migrations for testing, a
 possible solution would be either allowing specific models to be marked as
 non-migrated, or avoiding flushing of non-existing tables.

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

Re: [Django] #22458: MySQL notes recommend legacy utf8_general_ci unicode collation

[Django]

#22458: MySQL notes recommend legacy utf8_general_ci unicode collation
-+-
 Reporter:  tobami@… |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.7-beta-1
 Severity:  Normal   |   Resolution:
 Keywords:  unicode  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by aaugustin):

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

Re: [Django] #20916: Provide a "simple_login" feature for the test client

[Django]

#20916: Provide a "simple_login" feature for the test client
---+
 Reporter:  mjtamlyn   |Owner:  alasdair
 Type:  New feature|   Status:  assigned
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  auth   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by alasdair):

 jfilipes approach looks promising, so I have unassigned the ticket from
 myself.

 > Also, the term "simple" seems a little vague to me. Something like
 `force_login(user)`, or `login(user, force=True)` would seem more
 explicit.

 Adding `force=True` to the login method would be backwards incompatible.
 As mjtamlyn says earlier in the comments, login currently takes `**kwargs`
 which get passed to the auth backend.

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

Re: [Django] #20916: Provide a "simple_login" feature for the test client

[Django]

#20916: Provide a "simple_login" feature for the test client
---+
 Reporter:  mjtamlyn   |Owner:  alasdair
 Type:  New feature|   Status:  assigned
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  auth   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by jfilipe):

 PR against Django's repo has been created:
 https://github.com/django/django/pull/2570.

 That's a valid point, Exposing `SimpleLoginBackend` in the `auth` contrib
 package could open it up to be abused by others.

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

Re: [Django] #22448: django test command runs wrong tests if test module has no tests

[Django]

#22448: django test command runs wrong tests if test module has no tests
-+-
 Reporter:  cjerdonek|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  test discovery,test  | Triage Stage:
  runner,test command,test label |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by prestontimmons):

 Although we added the test case in the 1.7 cycle, this wasn't a bug in 1.6
 that I'm aware of. That's the version I'm using to try to reproduce what
 you're seeing.

 I'm using the following layout to test:

 {{{
 foo/
   __init__.py
   bar.py
   car.py
 }}}

 The bar.py file is empty and car.py has:

 {{{
 import unittest

 from django.test import TestCase


 class SampleTest(unittest.TestCase):

 def test_one(self):
 assert True


 class DjangoTest(TestCase):

 def test_one(self):
 assert True
 }}}

 Running python manage.py test foo.bar returns:

 {{{
 --
 Ran 0 tests in 0.000s

 OK
 }}}

 Is this a correct interpretation of the scenario your describing?

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

Re: [Django] #22373: Django Migrations keeps detecting changes to FileField using custom storage

[Django]

#22373: Django Migrations keeps detecting changes to FileField using custom 
storage
-+-
 Reporter:  Matthias Pronk   |Owner:
   |   Status:  new
 Type:  Bug  |  Version:  master
Component:  Migrations   |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by chriscauley):

 You should also consider just removing the storage kwarg in
 `FileField.deconstruct()`. Since it's an optional argument this may make
 more sense. `upload_to` is required this is not an option in the other
 tickets. Then again, if a migration somehow touches a storage it may be
 better to raise `NotImplementedError`.

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

[Django] #22458: MySQL notes recommend legacy utf8_general_ci unicode collation

[Django]

#22458: MySQL notes recommend legacy utf8_general_ci unicode collation
--+
 Reporter:  tobami@…  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.7-beta-1
 Severity:  Normal|   Keywords:  unicode
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 The documentation section "MySQL notes" recommends the obsolete
 utf8_general_ci collation settings:
 "By default, with a UTF-8 database, MySQL will use the utf8_general_ci
 collation." [0]
 and
 "... you should still use utf8_general_ci (the default) collation for the
 django.contrib.sessions.models.Session table"

 While it may still be the default depending on your MySQL version, MySQL
 itself recommends utf8_unicode_ci instead of utf8_general_ci, as the later
 can be incorrect for some characters and languages and its performance
 benefits are no longer relevant. From the MySQL docs themselves:
 "utf8_general_ci is a legacy collation that does not support expansions,
 contractions, or ignorable characters." [1]

 Using utf8_general_ci can be the cause of difficult to debug text issues.
 IMO Django should update its MySQL collation recommendation to
 utf8_unicode_ci.

 [0] https://docs.djangoproject.com/en/dev/ref/databases/#collation-
 settings
 [1] http://dev.mysql.com/doc/refman/5.5/en/charset-unicode-sets.html

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

Re: [Django] #5863: list_display does not allow functions of referenced objects

[Django]

#5863: list_display does not allow functions of referenced objects
-+-
 Reporter:  Beat Bolli   |Owner:  nobody
|   Status:  closed
 Type:  Uncategorized|  Version:  master
Component:  contrib.admin|   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:  Design
 Keywords:  list_display |  decision needed
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-

Comment (by petr.dlouhy@…):

 I remade the Snippet 2996 in form of an application (for anyone interested
 in working around this issue): https://github.com/PetrDlouhy/django-
 related-admin

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

Re: [Django] #22449: Colorize output of test results

[Django]

#22449: Colorize output of test results
-+-
 Reporter:  jrothenbuhler|Owner:
 Type:  New feature  |  jrothenbuhler
Component:  Core (Management |   Status:  assigned
  commands)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by bmispelon):

 * needs_better_patch:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 I think this would be a useful feature.

 The patch looks good overall but I left a few comments on the pull
 request.
 Once those are fixed, you can remove the `patch needs improvement` flag.

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

Re: [Django] #20916: Provide a "simple_login" feature for the test client

[Django]

#20916: Provide a "simple_login" feature for the test client
---+
 Reporter:  mjtamlyn   |Owner:  alasdair
 Type:  New feature|   Status:  assigned
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  auth   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by julien):

 Thank you for your work on this ticket.

 I feel a bit uncomfortable adding an inherently insecure authenticate
 backend to core. This feature only really makes sense for testing, so I'd
 personally prefer to add it directly to the test client.

 Also, the term "simple" seems a little vague to me. Something like
 ``force_login(user)``, or ``login(user, force=True)`` would seem more
 explicit.

 I'd appreciate getting another core dev's opinion about the above.

 By the way, could you re-create the PR against the official Django
 repository on github (instead of your own fork)?

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

Re: [Django] #22353: CachedStaticFilesMixin lags in updating hashed names of other static files referenced in CSS

[Django]

#22353: CachedStaticFilesMixin lags in updating hashed names of other static 
files
referenced in CSS
-+
 Reporter:  woodlee  |Owner:  frog32
 Type:  Bug  |   Status:  assigned
Component:  contrib.staticfiles  |  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by frog32):

 * has_patch:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 Opened a pull request https://github.com/django/django/pull/2569

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

Re: [Django] #22325: Defining a custom user model in an app and having relations between it and other models in the app causes circular dependencies

[Django]

#22325: Defining a custom user model in an app and having relations between it 
and
other models in the app causes circular dependencies
+--
 Reporter:  melinath|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7-beta-1
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by bmispelon):

 * stage:  Unreviewed => Accepted


Comment:

 Triaging this per the previous comment

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

Re: [Django] #22444: conflicting docs regarding initial_data loading

[Django]

#22444: conflicting docs regarding initial_data loading
-+--
 Reporter:  kmtracey |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  1.7-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+--
Changes (by timo):

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

Re: [Django] #22386: squashmigrations needs documentation

[Django]

#22386: squashmigrations needs documentation
-+--
 Reporter:  kmtracey@…   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7-beta-1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by timo):

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


Comment:

 In 09af48c70fb5cc652ea109487015472e9ef984df:

 Improve migrations/schema docs

 Backported to 1.7x in a195ec847e44e8ec6f688dfed55b37eb8ec144cf.

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

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

[django/django] 828036: [1.6.x] Fixed #22457 -- Fixed contributing guide w...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 82803611eb1ca2ec8f4ea8569d4bf4abbd91cdb2
  
https://github.com/django/django/commit/82803611eb1ca2ec8f4ea8569d4bf4abbd91cdb2
  Author: Jordi Yeh 
  Date:   2014-04-16 (Wed, 16 Apr 2014)

  Changed paths:
M docs/internals/contributing/writing-code/unit-tests.txt

  Log Message:
  ---
  [1.6.x] Fixed #22457 -- Fixed contributing guide w/o github set-up

The published commnand was not working when the user did not have
the git client set-up with the public-key. Changed the contributing
guide to clone it from https instead.

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

Re: [Django] #22457: Quickstart git command Error Without git Setup

[Django]

#22457: Quickstart git command Error Without git Setup
---+
 Reporter:  jyeh   |Owner:  jyeh
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by Baptiste Mispelon ):

 In [changeset:"ec2d456df8a56a3000b991adcd5ce3aede974492"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ec2d456df8a56a3000b991adcd5ce3aede974492"
 [1.5.x] Fixed #22457 -- Fixed contributing guide w/o github set-up

 The published commnand was not working when the user did not have
 the git client set-up with the public-key. Changed the contributing
 guide to clone it from https instead.

 Backport of 28102991172ab931d030412275f926c1b05c688d from master
 }}}

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

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

Re: [Django] #22457: Quickstart git command Error Without git Setup

[Django]

#22457: Quickstart git command Error Without git Setup
---+
 Reporter:  jyeh   |Owner:  jyeh
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by Baptiste Mispelon ):

 In [changeset:"fcbcdf72d60ccfd808187c3322457decc927712c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="fcbcdf72d60ccfd808187c3322457decc927712c"
 [1.7.x] Fixed #22457 -- Fixed contributing guide w/o github set-up

 The published commnand was not working when the user did not have
 the git client set-up with the public-key. Changed the contributing
 guide to clone it from https instead.

 Backport of 28102991172ab931d030412275f926c1b05c688d from master.
 }}}

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

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

Re: [Django] #22457: Quickstart git command Error Without git Setup

[Django]

#22457: Quickstart git command Error Without git Setup
---+
 Reporter:  jyeh   |Owner:  jyeh
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by Baptiste Mispelon ):

 In [changeset:"82803611eb1ca2ec8f4ea8569d4bf4abbd91cdb2"]:
 {{{
 #!CommitTicketReference repository=""
 revision="82803611eb1ca2ec8f4ea8569d4bf4abbd91cdb2"
 [1.6.x] Fixed #22457 -- Fixed contributing guide w/o github set-up

 The published commnand was not working when the user did not have
 the git client set-up with the public-key. Changed the contributing
 guide to clone it from https instead.

 Backport of 28102991172ab931d030412275f926c1b05c688d from master.
 }}}

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

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

[django/django] ec2d45: [1.5.x] Fixed #22457 -- Fixed contributing guide w...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: ec2d456df8a56a3000b991adcd5ce3aede974492
  
https://github.com/django/django/commit/ec2d456df8a56a3000b991adcd5ce3aede974492
  Author: Jordi Yeh 
  Date:   2014-04-16 (Wed, 16 Apr 2014)

  Changed paths:
M docs/internals/contributing/writing-code/unit-tests.txt

  Log Message:
  ---
  [1.5.x] Fixed #22457 -- Fixed contributing guide w/o github set-up

The published commnand was not working when the user did not have
the git client set-up with the public-key. Changed the contributing
guide to clone it from https instead.

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

[django/django] fcbcdf: [1.7.x] Fixed #22457 -- Fixed contributing guide w...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: fcbcdf72d60ccfd808187c3322457decc927712c
  
https://github.com/django/django/commit/fcbcdf72d60ccfd808187c3322457decc927712c
  Author: Jordi Yeh 
  Date:   2014-04-16 (Wed, 16 Apr 2014)

  Changed paths:
M docs/internals/contributing/writing-code/unit-tests.txt

  Log Message:
  ---
  [1.7.x] Fixed #22457 -- Fixed contributing guide w/o github set-up

The published commnand was not working when the user did not have
the git client set-up with the public-key. Changed the contributing
guide to clone it from https instead.

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

[django/django] c06497: [1.7.x] Fixed spelling errors in documentation.

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: c064971e6bd1906c3665b25e0d659c0e47bb4a00
  
https://github.com/django/django/commit/c064971e6bd1906c3665b25e0d659c0e47bb4a00
  Author: Tim Graham 
  Date:   2014-04-16 (Wed, 16 Apr 2014)

  Changed paths:
M docs/ref/django-admin.txt
M docs/spelling_wordlist
M docs/topics/migrations.txt
M docs/topics/testing/tools.txt

  Log Message:
  ---
  [1.7.x] Fixed spelling errors in documentation.

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

[django/django] b5ce21: Fixed spelling errors in documentation.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b5ce21accb57a5b70420574647d56eb837eb7722
  
https://github.com/django/django/commit/b5ce21accb57a5b70420574647d56eb837eb7722
  Author: Tim Graham 
  Date:   2014-04-16 (Wed, 16 Apr 2014)

  Changed paths:
M docs/ref/django-admin.txt
M docs/spelling_wordlist
M docs/topics/migrations.txt
M docs/topics/testing/tools.txt

  Log Message:
  ---
  Fixed spelling errors in documentation.


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

Re: [Django] #22457: Quickstart git command Error Without git Setup

[Django]

#22457: Quickstart git command Error Without git Setup
---+
 Reporter:  jyeh   |Owner:  jyeh
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by Baptiste Mispelon ):

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


Comment:

 In [changeset:"28102991172ab931d030412275f926c1b05c688d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="28102991172ab931d030412275f926c1b05c688d"
 Fixed #22457 -- Fixed contributing guide w/o github set-up

 The published commnand was not working when the user did not have
 the git client set-up with the public-key. Changed the contributing
 guide to clone it from https instead.
 }}}

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

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

[django/django] 281029: Fixed #22457 -- Fixed contributing guide w/o githu...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 28102991172ab931d030412275f926c1b05c688d
  
https://github.com/django/django/commit/28102991172ab931d030412275f926c1b05c688d
  Author: Jordi Yeh 
  Date:   2014-04-16 (Wed, 16 Apr 2014)

  Changed paths:
M docs/internals/contributing/writing-code/unit-tests.txt

  Log Message:
  ---
  Fixed #22457 -- Fixed contributing guide w/o github set-up

The published commnand was not working when the user did not have
the git client set-up with the public-key. Changed the contributing
guide to clone it from https instead.


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

Re: [Django] #22457: Quickstart git command Error Without git Setup

[Django]

#22457: Quickstart git command Error Without git Setup
---+
 Reporter:  jyeh   |Owner:  jyeh
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by jyeh):

 * has_patch:  0 => 1


Comment:

 Pull request available at https://github.com/django/django/pull/2568

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

Re: [Django] #22446: Add tox support

[Django]

#22446: Add tox support
-+-
 Reporter:  jmbowman |Owner:  jmbowman
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Testing framework|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

 * easy:  1 => 0


Comment:

 I'm in favor of recommending the [https://github.com/jphalip/djangocore-
 box djangocore-box], but tox could probably be leveraged there as well.

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

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

Re: [Django] #20916: Provide a "simple_login" feature for the test client

[Django]

#20916: Provide a "simple_login" feature for the test client
---+
 Reporter:  mjtamlyn   |Owner:  alasdair
 Type:  New feature|   Status:  assigned
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  auth   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by jfilipe):

 Technically it's not setting it as the default, it's just adding it as
 another backend the auth system will try and use.

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