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):

 just don't worry about that !

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

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

Re: [Django] #22479: Support byte range requests in django.views.static.serve

[Django]

#22479: Support byte range requests in django.views.static.serve
---+
 Reporter:  slurms |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by slurms):

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


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

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

[Django] #22479: Support byte range requests in django.views.static.serve

[Django]

#22479: Support byte range requests in django.views.static.serve
---+
 Reporter:  slurms |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  HTTP handling  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 As supported by this google groups discussions:
 https://groups.google.com/d/msg/django-developers/NZ1qTkZ6vok/fhdz7rTtL1EJ

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.a4000c626746e1b4c5761a7c68ea93b1%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):

 It's a hack (`sys.argv` parsing, private APIs) but if like me you have a
 large test suite and really need a stopgap solution you may find this
 helpful:

 {{{
 import sys

 from django.apps import AppConfig
 from django.utils.module_loading import import_module,
 module_has_submodule


 TEST_MODELS_MODULE_NAME = 'tests'


 class AppConfigWithTestModels(AppConfig):
 def import_models(self, *args, **kwargs):
 super(AppConfigWithTestModels, self).import_models(*args,
 **kwargs)

 if len(sys.argv) >= 2 and sys.argv[1] == 'test':
 if module_has_submodule(self.module, TEST_MODELS_MODULE_NAME):
 models_module_name = '%s.%s' % (self.name,
 TEST_MODELS_MODULE_NAME)
 models_module = import_module(models_module_name)
 if self.models_module is None:
 self.models_module = models_module
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.28da3ddc412e9621415bd9a60eae3b80%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #16735: Queryset values should be aliasable

[Django]

#16735: Queryset values should be aliasable
-+-
 Reporter:  alex.latchford@… |Owner:  nate_b
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  queryset, alias, |  Needs documentation:  0
  values |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by charettes):

 Unfortunately this feature didn't make it to the 1.7.x branch before it
 was feature frozen.

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

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

Re: [Django] #16735: Queryset values should be aliasable

[Django]

#16735: Queryset values should be aliasable
-+-
 Reporter:  alex.latchford@… |Owner:  nate_b
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  queryset, alias, |  Needs documentation:  0
  values |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by paveluc.alexandr@…):

 Will this patch be included in next Django release?

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

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

Re: [Django] #22478: Wrong module name used in build_test

[Django]

#22478: Wrong module name used in build_test
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.7-beta-1
 Severity:  Normal |   Resolution:
 Keywords:  tests, test suite  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by prestontimmons):

 Replying to [comment:2 yakky]:
 > Test attached

 yakky, it would help if you submitted this as a single patch.

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

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

Re: [Django] #22478: Wrong module name used in build_test

[Django]

#22478: Wrong module name used in build_test
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.7-beta-1
 Severity:  Normal |   Resolution:
 Keywords:  tests, test suite  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by prestontimmons):

 The issue wasn't clear to me based on the report. It boiled down to this:

 If you define a test in `tests/__init__.py`, and use the old test runner,
 a test label like myapp.TestCase fails to resolve to the test case.
 Instead, a ValueError is raised:

 {{{
 ValueError: Test label 'testapp.MyTest' does not refer to a test
 }}}

 From my testing, this works in the 1.6.x branch but fails in 1.7.x. I
 didn't track down the commit that caused the regression.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.feedfa83e095afe157bbf8c3b68c164b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22478: Wrong module name used in build_test

[Django]

#22478: Wrong module name used in build_test
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.7-beta-1
 Severity:  Normal |   Resolution:
 Keywords:  tests, test suite  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by rtnpro):

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


Comment:

 I am able to reproduce the reported bug. I have also reviewed the patches
 and tested it on my local codebase of Django running tag 1.7b1. The
 patches seem to be working, however, they are not PEP8 compliant.

 {{{
 $ pep8 tests/test_suite_override/sample_app/
 tests/test_suite_override/sample_app/__init__.py:1:24: W292 no newline at
 end of file
 tests/test_suite_override/sample_app/models.py:4:1: E302 expected 2 blank
 lines, found 1
 tests/test_suite_override/sample_app/tests/__init__.py:2:27: W292 no
 newline at end of file
 }}}

 So, I'd suggest yakky to make the change PEP8 compliant and submit an
 incremental patch.

 I will mark this ticket as accepted. If someone has any point to add,
 please feel free to share your opinion.

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

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

Re: [Django] #22478: Wrong module name used in build_test

[Django]

#22478: Wrong module name used in build_test
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.7-beta-1
 Severity:  Normal |   Resolution:
 Keywords:  tests, test suite  | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by rtnpro):

 * component:  Uncategorized => Testing framework


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

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

Re: [Django] #22125: Unnecessary creation of index for ManyToManyField

[Django]

#22125: Unnecessary creation of index for ManyToManyField
-+-
 Reporter:  tbhtan3@…|Owner:  bwreilly
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.6
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by bwreilly):

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

Re: [Django] #22478: Wrong module name used in build_test

[Django]

#22478: Wrong module name used in build_test
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  1.7-beta-1
 Severity:  Normal |   Resolution:
 Keywords:  tests, test suite  | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by rtnpro):

 * cc: rtnpro (added)


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

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

Re: [Django] #22478: Wrong module name used in build_test

[Django]

#22478: Wrong module name used in build_test
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  1.7-beta-1
 Severity:  Normal |   Resolution:
 Keywords:  tests, test suite  | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by yakky):

 * cc: yakky (added)
 * keywords:   => tests, test suite


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.86f5a489df72a5c13287c369424ecf6e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22478: Wrong module name used in build_test

[Django]

#22478: Wrong module name used in build_test
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  1.7-beta-1
 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 yakky):

 * needs_tests:  1 => 0


Comment:

 Test attached

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.d3a5fd030787f1e6014b75bd2ae26405%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22342: Changing a model to an abstract model caused "ValueError: Related model 'app.Model' cannot be resolved"

[Django]

#22342: Changing a model to an abstract model caused "ValueError: Related model
'app.Model' cannot be resolved"
+--
 Reporter:  blueyed |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:  worksforme
 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 blueyed):

 Thanks for looking into this.

 I have came across a code comment, where I've linked to this ticket, but
 the code itself changed quite a lot already.

 IIRC your basic test case was what I was doing.

 Feel free to close this ticket because of lacking information, and because
 it has been fixed in the meantime already or was specific to some certain
 local-only change at that 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/065.3734b4db25c4a587fb5f1964a1b456f3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22478: Wrong module name used in build_test

[Django]

#22478: Wrong module name used in build_test
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  1.7-beta-1
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by yakky):

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


Comment:

 Tests still needed

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.bbc658389d859dabd948ddf90fcf876c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22478: Wrong module name used in build_test

[Django]

#22478: Wrong module name used in build_test
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  1.7-beta-1
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 TestClass loading in django.test.simple.build_test cycle through
 discovered modules in application, but iterated modules are not used in
 the for cycle.

 See
 https://github.com/django/django/blob/stable/1.7.x/django/test/simple.py#L183

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

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

[django/django] 9e86c3: [1.7.x] Fixed flake8 errors.

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 9e86c3f0a62a33a541b0ccf7d86a3db87e8e8705
  
https://github.com/django/django/commit/9e86c3f0a62a33a541b0ccf7d86a3db87e8e8705
  Author: Tim Graham 
  Date:   2014-04-20 (Sun, 20 Apr 2014)

  Changed paths:
M django/db/migrations/migration.py
M tests/migrations/test_autodetector.py
M tests/migrations/test_state.py

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

Backport of 471fb04a30 from master


  Commit: 33d1dc2eeb5db83f07b6b7fbf3b10ef01b74702b
  
https://github.com/django/django/commit/33d1dc2eeb5db83f07b6b7fbf3b10ef01b74702b
  Author: Simon Charette 
  Date:   2014-04-20 (Sun, 20 Apr 2014)

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

  Log Message:
  ---
  [1.7.x] Fixed flake8 warnings introduced in recent commits.

Backport of 79f05616fbf48cf7c205ef17666af0c3d47b3c1e from master


Compare: https://github.com/django/django/compare/0086c9eb4810...33d1dc2eeb5d

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

[django/django] 471fb0: Fixed flake8 errors.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 471fb04a307870794e3cefb1177405b506ee1a0a
  
https://github.com/django/django/commit/471fb04a307870794e3cefb1177405b506ee1a0a
  Author: Tim Graham 
  Date:   2014-04-20 (Sun, 20 Apr 2014)

  Changed paths:
M django/db/migrations/migration.py
M tests/migrations/test_autodetector.py
M tests/migrations/test_state.py

  Log Message:
  ---
  Fixed flake8 errors.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/5353ff05ec60f_4319f0fd3496996%40hookshot-fe1-cp1-prd.iad.github.net.mail.
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 aaugustin):

 Replying to [comment:10 prestontimmons]:
 > aaugustin: Declaring models in tests.py still works in 1.6.

 It still works in 1.7 too, for some value of works ;-) More accurately,
 the set of cases where it doesn't work seems to have increased a bit in
 1.6 and again in 1.7.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.fe007c9b48a8b80fe5fe2eb926c9043d%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 prestontimmons):

 loic: You're not crazy. It's just that this feature is pseudo-documented.

 aaugustin: Declaring models in tests.py still works in 1.6.

 Custom user model tests depend on it and recommend this as part of the 1.6
 upgrade path:

 https://docs.djangoproject.com/en/dev/releases/1.6/#custom-user-models-in-
 tests
 https://docs.djangoproject.com/en/dev/topics/auth/customizing/#custom-
 users-and-testing-fixtures

 What changed with discover runner is that it now requires an expicit
 import of `django.contrib.auth.tests.custom_user.CustomUser` in tests.py.
 Unlike the old test runner, the discover runner doesn't always import
 every test file. Hence, the supplied CustomUser model wouldn't be
 registered.

 Additional discussion is in #21164.

 https://code.djangoproject.com/ticket/21164#comment:9 Starting here is
 discussion on how much this behavior should be solidified in Django

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

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

Re: [Django] #22477: Incompatible Global Settings

[Django]

#22477: Incompatible Global Settings
---+--
 Reporter:  mlavin |Owner:  mlavin
 Type:  Uncategorized  |   Status:  assigned
Component:  Uncategorized  |  Version:  master
 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 mlavin):

 * has_patch:  0 => 1


Comment:

 Added a PR against 1.7.x https://github.com/django/django/pull/2591. If
 you feel like this shouldn't be back-ported I'll fix to submit vs master.

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

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