Re: [Django] #24080: Sqlite segmentation fault regression when running tests (since 1.7.2)

[Django]

#24080: Sqlite segmentation fault regression when running tests (since 1.7.2)
---+
 Reporter:  stevejalim |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  sqlite | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by tricoder42):

 It's probably related only to Python 2.7.6. In Python 3.4.1 the test case
 runs fine.

 Unfortunately I haven't found the cause of segmentation fault. Here is the
 traceback (begins with the last test case):

 {{{
 SAVEPOINT "s140735267844864_x61"
 test_use_explicit_o2o_to_parent_from_abstract_model
 (model_inheritance_regress.tests.ModelInheritanceTest) ... ok
 ROLLBACK TO SAVEPOINT "s140735267844864_x61"
 Fatal Python error: Segmentation fault

 Current thread 0x7fff7ba5b300 (most recent call first):
   File
 "/Users/tricoder/Projects/django/django/db/backends/sqlite3/base.py", line
 317 in execute
   File "/Users/tricoder/Projects/django/django/db/backends/utils.py", line
 63 in execute
   File "/Users/tricoder/Projects/django/django/db/backends/base/base.py",
 line 215 in _savepoint_rollback
   File "/Users/tricoder/Projects/django/django/db/backends/base/base.py",
 line 255 in savepoint_rollback
   File "/Users/tricoder/Projects/django/django/db/transaction.py", line
 252 in __exit__
   File "/Users/tricoder/Projects/django/django/test/testcases.py", line
 932 in _rollback_atomics
   File "/Users/tricoder/Projects/django/django/test/testcases.py", line
 988 in _fixture_teardown
   File "/Users/tricoder/Projects/django/django/test/testcases.py", line
 844 in _post_teardown
   File "/Users/tricoder/Projects/django/django/test/testcases.py", line
 184 in __call__
   File
 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/suite.py",
 line 108 in run
   File
 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/suite.py",
 line 70 in __call__
   File
 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/runner.py",
 line 151 in run
   File "/Users/tricoder/Projects/django/django/test/runner.py", line 178
 in run_suite
   File "/Users/tricoder/Projects/django/django/test/runner.py", line 211
 in run_tests
   File "./tests/runtests.py", line 236 in django_tests
   File "./tests/runtests.py", line 414 in 
 [1]38431 segmentation fault  ./tests/runtests.py -v3
 model_inheritance_regress
 }}}

 Some clues:
 - Good library for catching tracebacks on segfault is `faulthandler`
 http://faulthandler.readthedocs.org/
 - Some failing test suites are `model_inheritance_regress` (with traceback
 above) and `admin_views`
 - It always crashes on "ROLLBACK TO SAVEPOINT", even in different tests
 (admin_views for example).
 - It doesn't depend on how many savepoints is created and released
 (`admin_views` tests create about 350 savepoints, while
 `model_inheritance_regress` creates about 60 savepoints)

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

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

[Django] #24275: Migration files should comply with PEP8

[Django]

#24275: Migration files should comply with PEP8
--+-
 Reporter:  darkryder |  Owner:  f.ssat95@…
 Type:  Cleanup/optimization  | Status:  new
Component:  Migrations|Version:  master
 Severity:  Normal|   Keywords:  Migration, PEP8
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+-
 The migration statements generated by the
 
[https://github.com/django/django/blob/master/django/db/migrations/writer.py#L123
 MigrationWriter] should preferably be PEP8 compatible. This would ensure
 that when people run flake8 on their apps, they do not stumble
 unnecessarily due to warnings generated in the migration files. [[BR]]
 In order to correct this, I've aimed to create a new class
 
[https://github.com/darkryder/django/commit/405413a94571e52f20841f15480ee6fa0d35b06a
 #diff-7d0e679c6018bf032defd15cf12a2520R41 CleanWriter] that
 MigrationWriter can inherit from, and can use its
 
[https://github.com/darkryder/django/commit/405413a94571e52f20841f15480ee6fa0d35b06a
 #diff-7d0e679c6018bf032defd15cf12a2520R111 clean] function before finally
 preparing the migration file. For lines which still can't be fixed, a `#
 NOQA` comment should be appended.[[BR]]
 Currently there are a couple of bugs in the CleanWriter class, which if
 this ticket gets accepted, I'll fix and then create a PR.

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

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

Re: [Django] #24274: migrations break fixtures

[Django]

#24274: migrations break fixtures
---+--
 Reporter:  yuriiz |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.7
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timgraham):

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


Comment:

 Apps with migrations [https://docs.djangoproject.com/en/1.7/howto/initial-
 data/#automatically-loading-initial-data-fixtures don't support
 initial_data], so you'll need to find a different solution like using a
 data migration.

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

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

Re: [Django] #24274: migrations break fixtures

[Django]

#24274: migrations break fixtures
---+--
 Reporter:  yuriiz |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.7
 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 yuriiz):

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


Comment:

 Currently the only way to workaround this is to delete third-party
 application migrations like this:
 rm -rfv local/lib/python2.7/site-
 packages/allauth/socialaccount/migrations/

 Than manage.py migrate and manage.py test will work again.

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

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

[Django] #24274: migrations break fixtures

[Django]

#24274: migrations break fixtures
---+
 Reporter:  yuriiz |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.7
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Since Django 1.7 syncdb does not work if there are fixtures including
 objects from apps having migrations because currently syncdb/migrate does
 following:
 1. Create tables for unmigrated apps
 2. Load initial_data.json
 3. Apply migrations
 If one would like to have instances of models from app having migration in
 initial_data.json syncdb will break with smth like this:
 {{{
 Operations to perform:
   Synchronize unmigrated apps: google, allauth, widget_tweaks, flatpages,
 facebook
   Apply all migrations: account, sessions, admin, sites, auth,
 contenttypes, socialaccount
 Synchronizing apps without migrations:
   Creating tables...
 Creating table django_flatpage_sites
 Creating table django_flatpage
   Installing custom SQL...
   Installing indexes...
 Traceback (most recent call last):
   File "manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/home/user/myproject/local/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 385, in
 execute_from_command_line
 utility.execute()
   File "/home/user/myproject/local/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 377, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/user/myproject/local/lib/python2.7/site-
 packages/django/core/management/base.py", line 288, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/home/user/myproject/local/lib/python2.7/site-
 packages/django/core/management/base.py", line 338, in execute
 output = self.handle(*args, **options)
   File "/home/user/myproject/local/lib/python2.7/site-
 packages/django/core/management/base.py", line 533, in handle
 return self.handle_noargs(**options)
   File "/home/user/myproject/local/lib/python2.7/site-
 packages/django/core/management/commands/syncdb.py", line 27, in
 handle_noargs
 call_command("migrate", **options)
   File "/home/user/myproject/local/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 115, in call_command
 return klass.execute(*args, **defaults)
   File "/home/user/myproject/local/lib/python2.7/site-
 packages/django/core/management/base.py", line 338, in execute
 output = self.handle(*args, **options)
   File "/home/user/myproject/local/lib/python2.7/site-
 packages/django/core/management/commands/migrate.py", line 128, in handle
 created_models = self.sync_apps(connection,
 executor.loader.unmigrated_apps)
   File "/home/user/myproject/local/lib/python2.7/site-
 packages/django/core/management/commands/migrate.py", line 298, in
 sync_apps
 call_command('loaddata', 'initial_data', verbosity=self.verbosity,
 database=connection.alias, skip_validation=True, app_label=app_label,
 hide_empty=True)
   File "/home/user/myproject/local/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 115, in call_command
 return klass.execute(*args, **defaults)
   File "/home/user/myproject/local/lib/python2.7/site-
 packages/django/core/management/base.py", line 338, in execute
 output = self.handle(*args, **options)
   File "/home/user/myproject/local/lib/python2.7/site-
 packages/django/core/management/commands/loaddata.py", line 61, in handle
 self.loaddata(fixture_labels)
   File "/home/user/myproject/local/lib/python2.7/site-
 packages/django/core/management/commands/loaddata.py", line 91, in
 loaddata
 self.load_label(fixture_label)
   File "/home/user/myproject/local/lib/python2.7/site-
 packages/django/core/management/commands/loaddata.py", line 148, in
 load_label
 obj.save(using=self.using)
   File "/home/user/myproject/local/lib/python2.7/site-
 packages/django/core/serializers/base.py", line 173, in save
 models.Model.save_base(self.object, using=using, raw=True)
   File "/home/user/myproject/local/lib/python2.7/site-
 packages/django/db/models/base.py", line 617, in save_base
 updated = self._save_table(raw, cls, force_insert, force_update,
 using, update_fields)
   File "/home/user/myproject/local/lib/python2.7/site-
 packages/django/db/models/base.py", line 679, in _save_table
 forced_update)
   File "/home/user/myproject/local/lib/python2.7/site-
 packages/django/db/models/base.py", line 723, in _do_update
 return filtered._update(values) > 0
   File "/home/user/myproject/local/lib/python2.7/site-
 packages/django/db/models/query.py", line 600, in _update
 return query.get_compiler(self.db).execute_sql(CURSOR)
   File "/home/user/myproject/local/lib/python2.7/site-
 

Re: [Django] #24146: (admin.E116) The value of 'list_filter[0]' refers to 'through__field', which does not refer to a Field.

[Django]

#24146: (admin.E116) The value of 'list_filter[0]' refers to 'through__field',
which does not refer to a Field.
-+-
 Reporter:  collinanderson   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.8alpha1
 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 pirosb3):

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

Re: [Django] #24271: Error message for fields.E005 does not specify that both 'actual value', 'human readable name' must be strings/'Actual Value should be able to be a non-string

[Django]

#24271: Error message for fields.E005 does not specify that both 'actual value',
'human readable name' must be strings/'Actual Value should be able to be a
non-string
--+--
 Reporter:  AncientSwordRage  |Owner:  mbasanta
 Type:  Bug   |   Status:  closed
Component:  Core (Other)  |  Version:  1.7
 Severity:  Normal|   Resolution:  invalid
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+--
Changes (by knbk):

 * resolution:  fixed => invalid


Comment:

 Whoops, I mean 'invalid', not 'fixed'. (I can't edit that, can I?)

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

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

Re: [Django] #24271: Error message for fields.E005 does not specify that both 'actual value', 'human readable name' must be strings/'Actual Value should be able to be a non-string

[Django]

#24271: Error message for fields.E005 does not specify that both 'actual value',
'human readable name' must be strings/'Actual Value should be able to be a
non-string
--+--
 Reporter:  AncientSwordRage  |Owner:  mbasanta
 Type:  Bug   |   Status:  closed
Component:  Core (Other)  |  Version:  1.7
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+--
Changes (by knbk):

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


Comment:

 Turns out to be a bug in the user's code, not in Django:
 http://stackoverflow.com/questions/28304776/are-numerically-keyed-choices-
 no-longer-possible-in-django-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/074.8e33ca318b876db072c220e82bb8ca95%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #15321: Models._get_unique_checks() does not return grandparents' unique checks

[Django]

#15321: Models._get_unique_checks() does not return grandparents' unique checks
-+-
 Reporter:  jku  |Owner:  aron45
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  models, unique   | Triage Stage:  Ready for
  checks |  checkin
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:"fc49e736484892eaa516826d93660c7ab53a6c3e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="fc49e736484892eaa516826d93660c7ab53a6c3e"
 [1.8.x] Fixed #15321 -- Honored ancestors unique checks.

 Thanks to Tim for the review.

 Backport of 79f27f2b61aeac763ae048416ef8a97c2b639ae8 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/061.b197cf7dbeadeff9047723ac9b6b790c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #15321: Models._get_unique_checks() does not return grandparents' unique checks

[Django]

#15321: Models._get_unique_checks() does not return grandparents' unique checks
-+-
 Reporter:  jku  |Owner:  aron45
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  models, unique   | Triage Stage:  Ready for
  checks |  checkin
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:"79f27f2b61aeac763ae048416ef8a97c2b639ae8"]:
 {{{
 #!CommitTicketReference repository=""
 revision="79f27f2b61aeac763ae048416ef8a97c2b639ae8"
 Fixed #15321 -- Honored ancestors unique checks.

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

Re: [Django] #23763: Python 3.5 compatibility

[Django]

#23763: Python 3.5 compatibility
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"3e24ab6f4ca6632c910c684fda3d0f937fade52a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3e24ab6f4ca6632c910c684fda3d0f937fade52a"
 [1.8.x] Refactored tests that rely on an ImportError for Python 3.5
 compatibility

 A change in Python test discovery [1] causes the old packages that raised
 an error to be discovered; now we use a common directory that's
 ignored during discovery. Refs #23763.

 [1] http://bugs.python.org/issue7559

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

Re: [Django] #23763: Python 3.5 compatibility

[Django]

#23763: Python 3.5 compatibility
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"c0cc8f69e7abfa8578729031f97ae4b96c5cdafe"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c0cc8f69e7abfa8578729031f97ae4b96c5cdafe"
 Refactored tests that rely on an ImportError for Python 3.5 compatibility

 A change in Python test discovery [1] causes the old packages that raised
 an error to be discovered; now we use a common directory that's
 ignored during discovery. Refs #23763.

 [1] http://bugs.python.org/issue7559
 }}}

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

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

Re: [Django] #24241: state.clone doesn't copy Django models

[Django]

#24241: state.clone doesn't copy Django models
-+-
 Reporter:  claudep  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.8alpha1
 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 coldmind):

 More reliable to copy class, but still no ideal


 {{{
 dict_copy = SomeDjangoModel.__dict__.copy()
 del dict_copy[‘_meta’]
 type(SomeDjangoModel.__name__, SomeDjangoModel.__bases__, dict_copy)
 }}}

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

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

Re: [Django] #24273: AttributeError: _processors_index on nested inclusion_tag

[Django]

#24273: AttributeError: _processors_index on nested inclusion_tag
-+--
 Reporter:  collinanderson   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.8alpha1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by collinanderson):

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


Comment:

 bisected to
 
https://github.com/django/django/commit/e53495ba3352c2c0fdb6178f2b333c30cb6b5d46

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

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

[Django] #24273: AttributeError: _processors_index on nested inclusion_tag

[Django]

#24273: AttributeError: _processors_index on nested inclusion_tag
-+---
 Reporter:  collinanderson   |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Template system  |Version:  1.8alpha1
 Severity:  Release blocker  |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+---
 Testcase here:
 
https://github.com/collinanderson/doubleinclusion/commit/10d56afa7ae086f0bb460ad0c3cee0dcfb67a8ef

 To reproduce:

 git clone https://github.com/collinanderson/doubleinclusion
 python manage.py runserver
 # go to homepage

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

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

Re: [Django] #24235: Deprecate is_usable attribute on template loaders?

[Django]

#24235: Deprecate is_usable attribute on template loaders?
--+
 Reporter:  prestontimmons|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Template system   |  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 prestontimmons):

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

Re: [Django] #24235: Deprecate is_usable attribute on template loaders?

[Django]

#24235: Deprecate is_usable attribute on template loaders?
--+
 Reporter:  prestontimmons|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Template system   |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by prestontimmons):

 I added a pull request here:

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

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

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

Re: [Django] #15321: Models._get_unique_checks() does not return grandparents' unique checks

[Django]

#15321: Models._get_unique_checks() does not return grandparents' unique checks
-+-
 Reporter:  jku  |Owner:  aron45
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  models, unique   | Triage Stage:  Ready for
  checks |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:  1 => 0
 * needs_tests:  1 => 0
 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #14497: ModelAdmin.readonly_fields isn't graceful with filefields.

[Django]

#14497: ModelAdmin.readonly_fields isn't graceful with filefields.
-+-
 Reporter:  Keryn Knight |Owner:
    |  paulcollins
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  1.2
 Severity:  Normal   |   Resolution:
 Keywords:  feature admin| Triage Stage:  Ready for
  readonly filefield |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by collinanderson):

 * stage:  Accepted => Ready for checkin


Comment:

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

Re: [Django] #24266: Change `get_parent_list` to return a list of parents ordered by __mro__ instead of a set

[Django]

#24266: Change `get_parent_list` to return a list of parents ordered by __mro__
instead of a set
-+-
 Reporter:  charettes|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette ):

 In [changeset:"cbcf92e95f8a6d275b55069de3c57835814b502f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cbcf92e95f8a6d275b55069de3c57835814b502f"
 [1.8.x] Fixed #24266 -- Changed get_parent_list to return a list ordered
 by MRO.

 Thanks to Aron Podrigal for the initial patch and Tim for the review.

 Backport of 65e005f8cd9c656e558e53e6c8b890cd0fcc9e74 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/067.8ae8755bbba5d54f9901ab934c504f98%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24271: Error message for fields.E005 does not specify that both 'actual value', 'human readable name' must be strings/'Actual Value should be able to be a non-string

[Django]

#24271: Error message for fields.E005 does not specify that both 'actual value',
'human readable name' must be strings/'Actual Value should be able to be a
non-string
--+--
 Reporter:  AncientSwordRage  |Owner:  mbasanta
 Type:  Bug   |   Status:  assigned
Component:  Core (Other)  |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+--
Changes (by mbasanta):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * owner:  nobody => mbasanta
 * 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.07faa1bc364b3f73ed10816cdaea8558%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24266: Change `get_parent_list` to return a list of parents ordered by __mro__ instead of a set

[Django]

#24266: Change `get_parent_list` to return a list of parents ordered by __mro__
instead of a set
-+-
 Reporter:  charettes|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette ):

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


Comment:

 In [changeset:"65e005f8cd9c656e558e53e6c8b890cd0fcc9e74"]:
 {{{
 #!CommitTicketReference repository=""
 revision="65e005f8cd9c656e558e53e6c8b890cd0fcc9e74"
 Fixed #24266 -- Changed get_parent_list to return a list ordered by MRO.

 Thanks to Aron Podrigal for the initial patch and Tim 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/067.9a6f571cae56b1ca0130bfd40efe7d06%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24266: Change `get_parent_list` to return a list of parents ordered by __mro__ instead of a set

[Django]

#24266: Change `get_parent_list` to return a list of parents ordered by __mro__
instead of a set
-+-
 Reporter:  charettes|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #24146: (admin.E116) The value of 'list_filter[0]' refers to 'through__field', which does not refer to a Field.

[Django]

#24146: (admin.E116) The value of 'list_filter[0]' refers to 'through__field',
which does not refer to a Field.
-+-
 Reporter:  collinanderson   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.8alpha1
 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 timgraham):

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


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

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

Re: [Django] #24146: (admin.E116) The value of 'list_filter[0]' refers to 'through__field', which does not refer to a Field.

[Django]

#24146: (admin.E116) The value of 'list_filter[0]' refers to 'through__field',
which does not refer to a Field.
-+-
 Reporter:  collinanderson   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.8alpha1
 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 timgraham):

 * has_patch:  1 => 0
 * version:  master => 1.8alpha1
 * stage:  Ready for checkin => 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/072.0bde37148c43b76f42fb647c53dc06bc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24146: (admin.E116) The value of 'list_filter[0]' refers to 'through__field', which does not refer to a Field.

[Django]

#24146: (admin.E116) The value of 'list_filter[0]' refers to 'through__field',
which does not refer to a Field.
-+-
 Reporter:  collinanderson   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"92d5bedc56155e4c91c7644200415b3e42cdd31f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="92d5bedc56155e4c91c7644200415b3e42cdd31f"
 [1.8.x] Reverted "Fixed #24146 -- Fixed a missing fields regression in
 admin checks."

 This reverts commit e8171daf0cd7f0e070395cb4c850c17fea32f11d.

 A new solution is forthcoming.

 Backport of 0e489c19f1554ecfd9825daacfbac73be8ce723e 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/072.a8387ff9ede01c8d9a9ac29d5affd882%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24146: (admin.E116) The value of 'list_filter[0]' refers to 'through__field', which does not refer to a Field.

[Django]

#24146: (admin.E116) The value of 'list_filter[0]' refers to 'through__field',
which does not refer to a Field.
-+-
 Reporter:  collinanderson   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"0e489c19f1554ecfd9825daacfbac73be8ce723e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="0e489c19f1554ecfd9825daacfbac73be8ce723e"
 Reverted "Fixed #24146 -- Fixed a missing fields regression in admin
 checks."

 This reverts commit e8171daf0cd7f0e070395cb4c850c17fea32f11d.

 A new solution is forthcoming.
 }}}

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

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

Re: [Django] #24266: Change `get_parent_list` to return a list of parents ordered by __mro__ instead of a set

[Django]

#24266: Change `get_parent_list` to return a list of parents ordered by __mro__
instead of a set
-+-
 Reporter:  charettes|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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):

 * has_patch:  0 => 1


Comment:

 Created a [https://github.com/django/django/pull/4043 PR].

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

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

Re: [Django] #24242: compress_sequence creates a larger content than no compression

[Django]

#24242: compress_sequence creates a larger content than no compression
--+
 Reporter:  dracos|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  HTTP handling |  Version:  1.7
 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 timgraham):

 * needs_better_patch:  0 => 1


Comment:

 Test doesn't pass on Python 3.

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

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

Re: [Django] #24149: Normalize settings to be lists rather than tuples

[Django]

#24149: Normalize settings to be lists rather than tuples
-+-
 Reporter:  aaugustin|Owner:  darkryder
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Core (Other) |  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 Tim Graham ):

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


Comment:

 In [changeset:"9ec8aa5e5d42ac4529846f7eae6bf4982800abff"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9ec8aa5e5d42ac4529846f7eae6bf4982800abff"
 Fixed #24149 -- Normalized tuple settings to lists.
 }}}

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

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

Re: [Django] #24231: Regression in availability of `_meta.get_field()` before app registry is fully populated

[Django]

#24231: Regression in availability of `_meta.get_field()` before app registry is
fully populated
---+-
 Reporter:  carljm |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.8alpha1
 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 carljm):

 * version:  1.7 => 1.8alpha1


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

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

Re: [Django] #24266: Change `get_parent_list` to return a list of parents ordered by __mro__ instead of a set (was: Deprecate `Options.get_parent_list` in favor of a new `get_ancestors` one.)

[Django]

#24266: Change `get_parent_list` to return a list of parents ordered by __mro__
instead of a set
-+-
 Reporter:  charettes|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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
-+-

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

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

Re: [Django] #24146: (admin.E116) The value of 'list_filter[0]' refers to 'through__field', which does not refer to a Field.

[Django]

#24146: (admin.E116) The value of 'list_filter[0]' refers to 'through__field',
which does not refer to a Field.
-+-
 Reporter:  collinanderson   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by carljm):

 I don't have time in the next couple days, but towards the end of this
 week I can put together an alternative PR that maintains deterministic
 behavior but uses `models_ready` instead of `ready`. I think I'd feel
 better if the existing commit were rolled back sooner so we don't get
 anything else that depends on the non-deterministic early calling of
 `get_field()`, but I can also just roll it back in my alternate PR.

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

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

Re: [Django] #24146: (admin.E116) The value of 'list_filter[0]' refers to 'through__field', which does not refer to a Field.

[Django]

#24146: (admin.E116) The value of 'list_filter[0]' refers to 'through__field',
which does not refer to a Field.
-+-
 Reporter:  collinanderson   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by collinanderson):

 We're kind of repeating the discussion on the PR. :)
 https://github.com/django/django/pull/3912

 In my head I though Daniel was opposed to it, but apparently on the PR he
 said "I think models_ready is a good place.".

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

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

Re: [Django] #24146: (admin.E116) The value of 'list_filter[0]' refers to 'through__field', which does not refer to a Field.

[Django]

#24146: (admin.E116) The value of 'list_filter[0]' refers to 'through__field',
which does not refer to a Field.
-+-
 Reporter:  collinanderson   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by collinanderson):

 Anyway, I'm not attached to any particular solution, as long as it works
 :)

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

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

Re: [Django] #24146: (admin.E116) The value of 'list_filter[0]' refers to 'through__field', which does not refer to a Field.

[Django]

#24146: (admin.E116) The value of 'list_filter[0]' refers to 'through__field',
which does not refer to a Field.
-+-
 Reporter:  collinanderson   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by carljm):

 It seems we already have two stages of app-registry "readyness" -- there's
 `models_ready`, which is set to `True` before the app-config `ready()`
 methods run, and then there's `ready`, which isn't set until afterwards.
 It seems to me that it's really `models_ready` which should be the basis
 for the meta API deciding that the model graph is ready for use; in
 general, app-config `ready()` methods should be able to introspect models
 in a deterministic way.

 So I don't think we should introduce the possibility of non-deterministic
 introspection into the core of the meta API, as this commit does. Instead,
 we should switch the meta API to require `models_ready` rather than
 require `ready` before it caches the full model graph.

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

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

Re: [Django] #24146: (admin.E116) The value of 'list_filter[0]' refers to 'through__field', which does not refer to a Field.

[Django]

#24146: (admin.E116) The value of 'list_filter[0]' refers to 'through__field',
which does not refer to a Field.
-+-
 Reporter:  collinanderson   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by collinanderson):

 The admin checks run in `ready()`, and `apps.ready` isn't `True` until all
 `ready()`s are done.

 
https://github.com/django/django/blob/570912a97d5051fa3aeacd9d16c3be9afcf92198/django/apps/registry.py#L111-L114

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

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

Re: [Django] #24146: (admin.E116) The value of 'list_filter[0]' refers to 'through__field', which does not refer to a Field.

[Django]

#24146: (admin.E116) The value of 'list_filter[0]' refers to 'through__field',
which does not refer to a Field.
-+-
 Reporter:  collinanderson   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by carljm):

 I'm not convinced this is the right fix. Exposing reverse fields before
 the app-cache is ready is a recipe for unpredictable behavior, which is
 exactly what app-loading and the meta-refactor were supposed to fix. Why
 do admin checks run before the app cache is ready? That seems wrong -
 can't we fix that 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/072.a0d91f7c28340ebc679ddefe685c6726%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24197: contrib.staticfiles does not respect override_settings

[Django]

#24197: contrib.staticfiles does not respect override_settings
-+-
 Reporter:  mlavin   |Owner:  mlavin
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  contrib.staticfiles  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #24176: Incorrect SQL text when searching in SQLite for datetime values with milliseconds

[Django]

#24176: Incorrect SQL text when searching in SQLite for datetime values with
milliseconds
-+-
 Reporter:  me21 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |
 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 timgraham):

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

Re: [Django] #24266: Deprecate `Options.get_parent_list` in favor of a new `get_ancestors` one.

[Django]

#24266: Deprecate `Options.get_parent_list` in favor of a new `get_ancestors` 
one.
-+-
 Reporter:  charettes|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 timgraham):

 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #24242: compress_sequence creates a larger content than no compression

[Django]

#24242: compress_sequence creates a larger content than no compression
--+
 Reporter:  dracos|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  HTTP handling |  Version:  1.7
 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 timgraham):

 * type:  Uncategorized => Cleanup/optimization
 * component:  Uncategorized => HTTP handling
 * 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.b315e5c98c24ac127c051eab793270e9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24141: contains() method for QuerySets

[Django]

#24141: contains() method for QuerySets
-+-
 Reporter:  gormster |Owner:
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 I guess a discussion on the DevelopersMailingList needs to happen in order
 to move this forward. Closing until that discussion happens and there's
 agreement to add this.

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

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

Re: [Django] #24272: prefetch_related GenericRelation via related_query_name

[Django]

#24272: prefetch_related GenericRelation via related_query_name
-+-
 Reporter:  asdator  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  prefetch_related,| Triage Stage:
  GenericRelation,   |  Unreviewed
  related_query_name |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 I don't think what you have asked for can be implemented, but I'll leave
 this open for confirmation by an ORM expert. See #21422 which is to
 document the limitation.

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

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

Re: [Django] #24270: Wheel package does not contain 'extras' directory

[Django]

#24270: Wheel package does not contain 'extras' directory
---+
 Reporter:  mblayman   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Packaging  |  Version:  1.7
 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 timgraham):

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


Comment:

 This is related to #21511. It seems to me the solution would be to require
 installing the `extras` directory (not sure it can be done without turning
 it into a Python package, and not sure we want to do that). Unless an
 alternative is proposed, the best route might be to clarify the
 documentation to say that the script is included in the "source
 distribution" and not the wheel.

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

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

Re: [Django] #14497: ModelAdmin.readonly_fields isn't graceful with filefields.

[Django]

#14497: ModelAdmin.readonly_fields isn't graceful with filefields.
-+-
 Reporter:  Keryn Knight |Owner:
    |  paulcollins
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  1.2
 Severity:  Normal   |   Resolution:
 Keywords:  feature admin| Triage Stage:  Accepted
  readonly filefield |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by collinanderson):

 * cc: cmawebsite@… (added)


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

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

Re: [Django] #24267: Simplify Query.build_filter()

[Django]

#24267: Simplify Query.build_filter()
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 timgraham):

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


Comment:

 [https://github.com/django/django/pull/4036 PR] (currently has a test
 failure)

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

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

[Django] #24272: prefetch_related GenericRelation via related_query_name

[Django]

#24272: prefetch_related GenericRelation via related_query_name
-+-
 Reporter:  asdator  |  Owner:  nobody
 Type:  New feature  | Status:  new
Component:  Database layer   |Version:  1.7
  (models, ORM)  |   Keywords:  prefetch_related,
 Severity:  Normal   |  GenericRelation, related_query_name
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 Consider the following model structure:


 {{{#!python
 from django.db import models
 from django.contrib.contenttypes.fields import GenericForeignKey,
 GenericRelation
 from django.contrib.contenttypes.models import ContentType


 class TaggedItem(models.Model):
 tag = models.SlugField()
 content_type = models.ForeignKey(ContentType)
 object_id = models.PositiveIntegerField()
 content_object = GenericForeignKey('content_type', 'object_id')

 def __unicode__(self):
 return self.tag


 class Director(models.Model):
 name = models.CharField(max_length=100)

 def __unicode__(self):
 return self.name


 class Movie(models.Model):
 name = models.CharField(max_length=100)
 director = models.ForeignKey(Director)
 tags = GenericRelation(TaggedItem, related_query_name='movies')

 def __unicode__(self):
 return self.name


 class Author(models.Model):
 name = models.CharField(max_length=100)

 def __unicode__(self):
 return self.name


 class Book(models.Model):
 name = models.CharField(max_length=100)
 author = models.ForeignKey(Author)
 tags = GenericRelation(TaggedItem, related_query_name='books')

 def __unicode__(self):
 return self.name
 }}}

 And some initial data:



 {{{#!python
 >>> a = Author.objects.create(name='E L James')
 >>> b1 = Book.objects.create(name='Fifty Shades of Grey', author=a)
 >>> b2 = Book.objects.create(name='Fifty Shades Darker', author=a)
 >>> b3 = Book.objects.create(name='Fifty Shades Freed', author=a)
 >>> d = Director.objects.create(name='James Gunn')
 >>> m1 = Movie.objects.create(name='Guardians of the Galaxy', director=d)
 >>> t1 = TaggedItem.objects.create(content_object=b1, tag='roman')
 >>> t2 = TaggedItem.objects.create(content_object=b2, tag='roman')
 >>> t3 = TaggedItem.objects.create(content_object=b3, tag='roman')
 >>> t4 = TaggedItem.objects.create(content_object=m1, tag='action movie')
 }}}

 Now using the `GenericForeignKey` we are able to:
 1. `prefetch` only one level deep from `querysets` containing different
 type of `content_object`
 {{{#!python
 >>> TaggedItem.objects.all().prefetch_related('content_object')
 [, , ,
 ]
 }}}
 2. `prefetch` many levels but from `querysets` containing only one type of
 `content_object`.
 {{{#!python
 >>> TaggedItem.objects.filter(books__author__name='E L
 James').prefetch_related('content_object__author')
 [, , ]
 }}}
 But we can't do 1) and 2) together (//`prefetch` many levels from
 `querysets` containing different types of `content_objects`//)
 {{{#!python
 >>> TaggedItem.objects.all().prefetch_related('content_object__author')
 Traceback (most recent call last):
   ...
 AttributeError: 'Movie' object has no attribute 'author_id'
 }}}
 For such tasks this API is inconvenient and became unconvincing in more
 complex examples. For example if we want all `TaggedItems` with
 `prefetched` `movies` with their `directors` and `prefetched` `books` with
 their `author`.
 One silly attempt would look like this:
 {{{#!python
 >>> TaggedItem.objects.all().prefetch_related(
 ... 'content_object__author',
 ... 'content_object__director',
 ... )
 Traceback (most recent call last):
   ...
 AttributeError: 'Movie' object has no attribute 'author_id'
 }}}
 Or like this:
 {{{#!python
 >>> TaggedItem.objects.all().prefetch_related(
 ... Prefetch('content_object',
 queryset=Book.objects.all().select_related('author')),
 ... Prefetch('content_object',
 queryset=Movie.objects.all().select_related('director')),
 ... )
 Traceback (most recent call last):
   ...
 ValueError: Custom queryset can't be used for this lookup.
 }}}

 What I suggest is to use the API which we used to filter `TaggedItems` by
 their `book` `author`. This is not working right now.
 {{{#!python
 >>> TaggedItem.objects.filter(books__author__name='E L
 James').prefetch_related('books')
 Traceback (most recent call last):
   ...
 AttributeError: 'Book' object has no attribute 'object_id'
 }}}
 This way we would have and a nice solution for the more complex example
 mentioned above:
 {{{#!python
 >>> TaggedItem.objects.all().prefetch_related(
 ... 'books__author',
 ... 'movies__director',
 ... )
 Traceback (most recent call last):
   ...
 AttributeError: 'Book' object has no attribute 'object_id'
 }}}
 Or like this:
 

Re: [Django] #24080: Sqlite segmentation fault regression when running tests (since 1.7.2)

[Django]

#24080: Sqlite segmentation fault regression when running tests (since 1.7.2)
---+
 Reporter:  stevejalim |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  sqlite | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by tricoder42):

 I see. It works for `stable/1.7.x` and `1.7.2` for me though...

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

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

Re: [Django] #24268: Remove Query.having

[Django]

#24268: Remove Query.having
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 timgraham):

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


Comment:

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

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

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

Re: [Django] #24265: jinja2 template backend results in KeyError

[Django]

#24265: jinja2 template backend results in KeyError
-+-
 Reporter:  robhudson|Owner:  aaugustin
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  1.8alpha1
 Severity:  Normal   |   Resolution:
 Keywords:  multiple-template-   | Triage Stage:  Accepted
  engines 1.8-beta   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * keywords:  multiple-template-engines => multiple-template-engines
   1.8-beta
 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #24269: Explain why translations in Django repository are not synchronized with transifex (was: Django repository not synchronized with transifex)

[Django]

#24269: Explain why translations in Django repository are not synchronized with
transifex
---+-
 Reporter:  TheProdigyFilippo  |Owner:  timgraham
 Type:  New feature|   Status:  assigned
Component:  Documentation  |  Version:  1.7
 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 timgraham):

 * status:  new => assigned
 * component:  Internationalization => Documentation
 * owner:  nobody => timgraham
 * type:  Bug => New feature
 * 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/075.054768f3c60dcc622085b466810f2dde%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24080: Sqlite segmentation fault regression when running tests (since 1.7.2)

[Django]

#24080: Sqlite segmentation fault regression when running tests (since 1.7.2)
---+
 Reporter:  stevejalim |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  sqlite | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by timgraham):

 The original report is against Django 1.7.2 -- the change for the linked
 ticket is only present on 1.8+.

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

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

Re: [Django] #24252: reverse_lazy representation

[Django]

#24252: reverse_lazy representation
-+-
 Reporter:  Starou   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (URLs)  |  Version:  1.8alpha1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  reverse_lazy | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"ea3e40c278eb27fb3c8362d9e8cd67f957bf4f57"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ea3e40c278eb27fb3c8362d9e8cd67f957bf4f57"
 [1.8.x] Fixed #24252 -- Forced lazy __str__ to utf-8 on Python 2

 Thanks Stanislas Guerra for the report and Tomas Ehrlich for
 the review.
 Backport of cd0ceaa102 from master.
 }}}

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

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

Re: [Django] #24252: reverse_lazy representation

[Django]

#24252: reverse_lazy representation
-+-
 Reporter:  Starou   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (URLs)  |  Version:  1.8alpha1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  reverse_lazy | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"cd0ceaa102c1e12b016432db4d180bee7906131f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cd0ceaa102c1e12b016432db4d180bee7906131f"
 Fixed #24252 -- Forced lazy __str__ to utf-8 on Python 2

 Thanks Stanislas Guerra for the report and Tomas Ehrlich for
 the review.
 }}}

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

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

Re: [Django] #24240: Setting Content-Encoding on a non-ASCII StreamingHttpResponse raises UnicodeEncodeError

[Django]

#24240: Setting Content-Encoding on a non-ASCII StreamingHttpResponse raises
UnicodeEncodeError
-+-
 Reporter:  dracos   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  Version:  1.7
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"d88c24f436ae23ff5aec4ea06c0c27499a71e074"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d88c24f436ae23ff5aec4ea06c0c27499a71e074"
 [1.8.x] Fixed #24240 -- Allowed GZipping a Unicode StreamingHttpResponse

 make_bytes() assumed that if the Content-Encoding header is set, then
 everything had already been dealt with bytes-wise, but in a streaming
 situation this was not necessarily the case.

 make_bytes() is only called when necessary when working with a
 StreamingHttpResponse iterable, but by that point the middleware has
 added the Content-Encoding header and thus make_bytes() tried to call
 bytes(value) (and dies). If it had been a normal HttpResponse,
 make_bytes() would have been called when the content was set, well
 before the middleware set the Content-Encoding header.

 This commit removes the special casing when Content-Encoding is set,
 allowing unicode strings to be encoded during the iteration before they
 are e.g. gzipped. This behaviour was added a long time ago for #4969 and
 it doesn't appear to be necessary any more, as everything is correctly
 made into bytes at the appropriate places.

 Two new tests, to show that supplying non-ASCII characters to a
 StreamingHttpResponse works fine normally, and when passed through the
 GZip middleware (the latter dies without the change to make_bytes()).
 Removes the test with a nonsense Content-Encoding and Unicode input - if
 this were to happen, it can still be encoded as bytes fine.

 Backport of 250aa7c39b from master.
 }}}

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

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

Re: [Django] #24240: Setting Content-Encoding on a non-ASCII StreamingHttpResponse raises UnicodeEncodeError

[Django]

#24240: Setting Content-Encoding on a non-ASCII StreamingHttpResponse raises
UnicodeEncodeError
-+-
 Reporter:  dracos   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  Version:  1.7
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"250aa7c39b0025ef3ae508884fda8d6e43c9518f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="250aa7c39b0025ef3ae508884fda8d6e43c9518f"
 Fixed #24240 -- Allowed GZipping a Unicode StreamingHttpResponse

 make_bytes() assumed that if the Content-Encoding header is set, then
 everything had already been dealt with bytes-wise, but in a streaming
 situation this was not necessarily the case.

 make_bytes() is only called when necessary when working with a
 StreamingHttpResponse iterable, but by that point the middleware has
 added the Content-Encoding header and thus make_bytes() tried to call
 bytes(value) (and dies). If it had been a normal HttpResponse,
 make_bytes() would have been called when the content was set, well
 before the middleware set the Content-Encoding header.

 This commit removes the special casing when Content-Encoding is set,
 allowing unicode strings to be encoded during the iteration before they
 are e.g. gzipped. This behaviour was added a long time ago for #4969 and
 it doesn't appear to be necessary any more, as everything is correctly
 made into bytes at the appropriate places.

 Two new tests, to show that supplying non-ASCII characters to a
 StreamingHttpResponse works fine normally, and when passed through the
 GZip middleware (the latter dies without the change to make_bytes()).
 Removes the test with a nonsense Content-Encoding and Unicode input - if
 this were to happen, it can still be encoded as bytes fine.
 }}}

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

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

Re: [Django] #24080: Sqlite segmentation fault regression when running tests (since 1.7.2)

[Django]

#24080: Sqlite segmentation fault regression when running tests (since 1.7.2)
---+
 Reporter:  stevejalim |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  sqlite | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by tricoder42):

 * version:  1.7 => master
 * type:  Uncategorized => Bug


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

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

Re: [Django] #24080: Sqlite segmentation fault regression when running tests (since 1.7.2)

[Django]

#24080: Sqlite segmentation fault regression when running tests (since 1.7.2)
---+
 Reporter:  stevejalim |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Testing framework  |  Version:  1.7
 Severity:  Normal |   Resolution:
 Keywords:  sqlite | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by tricoder42):

 * status:  closed => new
 * cc: tomas.ehrlich@… (added)
 * component:  Uncategorized => Testing framework
 * resolution:  needsinfo =>
 * stage:  Unreviewed => Accepted


Comment:

 This regression is caused by #20392. In the ticket there's a mention about
 sqlite:

 > I also ran into some weird threading issues with sqlite that was causing
 a segmentation fault.

 For me it happens in OS X 10.10.2, Python 2.7.6 and latest master branch.

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

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

Re: [Django] #24112: Inconsistency in TestCase.assertInHTML

[Django]

#24112: Inconsistency in TestCase.assertInHTML
---+
 Reporter:  plumdog|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.7
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by claudep):

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

[Django] #24271: Error message for fields.E005 does not specify that both 'actual value', 'human readable name' must be strings/'Actual Value should be able to be a non-string

[Django]

#24271: Error message for fields.E005 does not specify that both 'actual value',
'human readable name' must be strings/'Actual Value should be able to be a
non-string
--+
 Reporter:  AncientSwordRage  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Core (Other)  |Version:  1.7
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 There is some
 
[https://github.com/django/django/blob/master/django/db/models/fields/__init__.py#L254
 code] that checks your choice of choices is valid. At one point it checks
 this:

 {{{ isinstance(choice, six.string_types)}}}

 Which checks that BOTH parts of the 2-tuple are strings (e.g. human
 readable). But the error message just says:

 "'choices' must be an iterable containing (actual value, human
 readable name) tuples."

 Which does not specify type in anyway, (e.g it doesn't say they must be
 some kind of string).

 Either the error should say that both parts must be strings (and thus
 block some fields from using  them e.g. integer fields), or only the
 second element should be checked, thusly:

 {{{
 >>> choices = (
 ... (1, 'Primary'), (2, 'Secondary'), (3, 'Tertiary')
 ... )
 >>> any(isinstance(choice, six.string_types) for choice in choices)
 False
 >>> any(isinstance(choice[1], six.string_types) for choice in choices)
 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/059.aec4b7c10164e7723d6565fce74159ca%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24269: Django repository not synchronized with transifex

[Django]

#24269: Django repository not synchronized with transifex
-+-
 Reporter:  TheProdigyFilippo|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  1.7
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by claudep):

 Here's what we could add at the bottom of
 
https://docs.djangoproject.com/en/1.7/internals/contributing/localizing/#translations
 :
 {{{
 Beware that translations from Transifex are only integrated into Django's
 source
 code at the time of new major releases. We try to update them a second
 time
 during one of the first minor releases, but that depends on the
 translation
 manager's availability. So don't miss the string freeze period (between
 the
 release candidate and the first major release) to take the opportunity to
 complete and fix the translations for your language!
 }}}

 I'll let you rephrase it in better English!

 About documenting the integration process, it's both simple and
 complicated. Simple because theoretically, it's a simple command (`python
 scripts/manage_translations fetch`), providing you have an account on
 Transifex, and then commit the changed/added files (both .po and .mo).
 Complicated because there are often validation errors for which you have
 to debug the causes and sometimes contact translators. I trust you about
 writing something based on the information 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/075.87407b42e8b94e2967e0dc29cfdc1b27%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #18651: Assignment tags should allow optional assignments

[Django]

#18651: Assignment tags should allow optional assignments
-+-
 Reporter:  mitar|Owner:  Tim
 |  Graham 
 Type:  New feature  |   Status:  closed
Component:  Template system  |  Version:  1.4
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"cd4282816db9164791cd0ac97a3dc329ad92c522"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cd4282816db9164791cd0ac97a3dc329ad92c522"
 Fixed #18651 -- Enabled optional assignments for simple_tag().
 }}}

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

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

Re: [Django] #24112: Inconsistency in TestCase.assertInHTML

[Django]

#24112: Inconsistency in TestCase.assertInHTML
---+
 Reporter:  plumdog|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.7
 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 plumdog):

 Pull Request created:

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

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

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

Re: [Django] #24080: Sqlite segmentation fault regression when running tests (since 1.7.2)

[Django]

#24080: Sqlite segmentation fault regression when running tests (since 1.7.2)
---+--
 Reporter:  stevejalim |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.7
 Severity:  Normal |   Resolution:  needsinfo
 Keywords:  sqlite | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by stevejalim):

 Just as an update for the future: I 'solved' this by throwing more RAM at
 it. Haven't seen it happen since.

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

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

Re: [Django] #23932: Document how to set a unique value for new fields using migrations

[Django]

#23932: Document how to set a unique value for new fields using migrations
--+
 Reporter:  michaeljohnbarr   |Owner:  akulakov
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  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 timgraham):

 * needs_better_patch:  0 => 1


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

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

Re: [Django] #14497: ModelAdmin.readonly_fields isn't graceful with filefields.

[Django]

#14497: ModelAdmin.readonly_fields isn't graceful with filefields.
-+-
 Reporter:  Keryn Knight |Owner:
    |  paulcollins
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  1.2
 Severity:  Normal   |   Resolution:
 Keywords:  feature admin| Triage Stage:  Accepted
  readonly filefield |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-

Comment (by rm_):

 Opened pull request:
 https://github.com/django/django/pull/4040

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

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

Re: [Django] #23617: The new UUID field does not allow to automatically generate a UUID on save

[Django]

#23617: The new UUID field does not allow to automatically generate a UUID on 
save
-+-
 Reporter:  thedrow  |Owner:  zedr
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  1.8-beta | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"43b0131fb5724cb92716eedfe35a6b2b4d84e1e5"]:
 {{{
 #!CommitTicketReference repository=""
 revision="43b0131fb5724cb92716eedfe35a6b2b4d84e1e5"
 [1.8.x] Fixed #23617 -- Added get_pk_value_on_save()

 The method is mainly intended for use with UUIDField. For UUIDField we
 want to call the field's default even when primary key value is
 explicitly set to None to match the behavior of AutoField.

 Thanks to Marc Tamlyn and Tim Graham for review.

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

Re: [Django] #14497: ModelAdmin.readonly_fields isn't graceful with filefields.

[Django]

#14497: ModelAdmin.readonly_fields isn't graceful with filefields.
-+-
 Reporter:  Keryn Knight |Owner:
    |  paulcollins
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  1.2
 Severity:  Normal   |   Resolution:
 Keywords:  feature admin| Triage Stage:  Accepted
  readonly filefield |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by rm_):

 * needs_better_patch:  1 => 0


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

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

Re: [Django] #23617: The new UUID field does not allow to automatically generate a UUID on save

[Django]

#23617: The new UUID field does not allow to automatically generate a UUID on 
save
-+-
 Reporter:  thedrow  |Owner:  zedr
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  1.8-beta | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"8adc59038cdc6ce4f9170e4de2d716d940e136b3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8adc59038cdc6ce4f9170e4de2d716d940e136b3"
 Fixed #23617 -- Added get_pk_value_on_save()

 The method is mainly intended for use with UUIDField. For UUIDField we
 want to call the field's default even when primary key value is
 explicitly set to None to match the behavior of AutoField.

 Thanks to Marc Tamlyn and Tim Graham for 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/065.7ffb0c5ad4341ec03249b74bd8c3d995%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24263: Optimization: django.views.generic.dates.BaseDateDetailView

[Django]

#24263: Optimization: django.views.generic.dates.BaseDateDetailView
-+-
 Reporter:  jekka-ua |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Generic views|  Version:  1.7
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  Optimization | Triage Stage:  Ready for
  BaseDateDetailView |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"9ffe013caa9360183cdb948b8e03c9c2a0da5417"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9ffe013caa9360183cdb948b8e03c9c2a0da5417"
 [1.8.x] Fixed #24263 -- Prevented extra queries on BaseDateDetailView with
 a custom queryset.

 Thanks jekka-ua for the report and patch.

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

Re: [Django] #24263: Optimization: django.views.generic.dates.BaseDateDetailView

[Django]

#24263: Optimization: django.views.generic.dates.BaseDateDetailView
-+-
 Reporter:  jekka-ua |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Generic views|  Version:  1.7
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  Optimization | Triage Stage:  Ready for
  BaseDateDetailView |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"118b11221f7f632b4d0e6e976c87f563746ec211"]:
 {{{
 #!CommitTicketReference repository=""
 revision="118b11221f7f632b4d0e6e976c87f563746ec211"
 Fixed #24263 -- Prevented extra queries on BaseDateDetailView with a
 custom queryset.

 Thanks jekka-ua for the report and patch.
 }}}

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

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

Re: [Django] #24250: Class FormMixin does not provide "form" variable in centext.

[Django]

#24250: Class FormMixin does not provide "form" variable in centext.
-+-
 Reporter:  4544fa8d |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  FormMixin form   | Triage Stage:  Ready for
  context|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"5fdd74f4be4aa6ce54021492e1b05ebf3770463d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5fdd74f4be4aa6ce54021492e1b05ebf3770463d"
 [1.8.x] Fixed broken links in class based views flattend index; refs
 #24250.

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

Re: [Django] #24250: Class FormMixin does not provide "form" variable in centext.

[Django]

#24250: Class FormMixin does not provide "form" variable in centext.
-+-
 Reporter:  4544fa8d |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  FormMixin form   | Triage Stage:  Ready for
  context|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"5104d935045c85d6e3a7354dcb74b5009e5794f2"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5104d935045c85d6e3a7354dcb74b5009e5794f2"
 [1.6.x] Fixed broken links in class based views flattend index; refs
 #24250.

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

Re: [Django] #24250: Class FormMixin does not provide "form" variable in centext.

[Django]

#24250: Class FormMixin does not provide "form" variable in centext.
-+-
 Reporter:  4544fa8d |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  FormMixin form   | Triage Stage:  Ready for
  context|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"346451164e56b01d8174bb21e3354f47db2764ae"]:
 {{{
 #!CommitTicketReference repository=""
 revision="346451164e56b01d8174bb21e3354f47db2764ae"
 [1.7.x] Fixed broken links in class based views flattend index; refs
 #24250.

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

Re: [Django] #24250: Class FormMixin does not provide "form" variable in centext.

[Django]

#24250: Class FormMixin does not provide "form" variable in centext.
-+-
 Reporter:  4544fa8d |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  FormMixin form   | Triage Stage:  Ready for
  context|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"9a391fbd6102176d576aa96ed3aeee9e9661b455"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9a391fbd6102176d576aa96ed3aeee9e9661b455"
 Fixed broken links in class based views flattend index; refs #24250.
 }}}

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

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

Re: [Django] #23932: Document how to set a unique value for new fields using migrations

[Django]

#23932: Document how to set a unique value for new fields using migrations
--+
 Reporter:  michaeljohnbarr   |Owner:  akulakov
 Type:  Cleanup/optimization  |   Status:  assigned
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:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * has_patch:  0 => 1


Comment:

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

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

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

Re: [Django] #24263: Optimization: django.views.generic.dates.BaseDateDetailView

[Django]

#24263: Optimization: django.views.generic.dates.BaseDateDetailView
-+-
 Reporter:  jekka-ua |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Generic views|  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  Optimization | Triage Stage:  Ready for
  BaseDateDetailView |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Ready for checkin


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

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

Re: [Django] #24250: Class FormMixin does not provide "form" variable in centext.

[Django]

#24250: Class FormMixin does not provide "form" variable in centext.
-+-
 Reporter:  4544fa8d |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  FormMixin form   | Triage Stage:  Ready for
  context|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"9c456ea8ff49eb8323f0b776935444197b6d75f2"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9c456ea8ff49eb8323f0b776935444197b6d75f2"
 [1.7.x] Fixed #24250 -- Corrected mistakes in FormMixin docs.

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

Re: [Django] #24250: Class FormMixin does not provide "form" variable in centext.

[Django]

#24250: Class FormMixin does not provide "form" variable in centext.
-+-
 Reporter:  4544fa8d |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  FormMixin form   | Triage Stage:  Ready for
  context|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"9316a04a9cb8e2f57068c1655c18510f943120e4"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9316a04a9cb8e2f57068c1655c18510f943120e4"
 [1.6.x] Fixed #24250 -- Corrected mistakes in FormMixin docs.

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

Re: [Django] #24250: Class FormMixin does not provide "form" variable in centext.

[Django]

#24250: Class FormMixin does not provide "form" variable in centext.
-+-
 Reporter:  4544fa8d |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  FormMixin form   | Triage Stage:  Ready for
  context|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"6454716264163b4693c03168ec56ea894ea511f2"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6454716264163b4693c03168ec56ea894ea511f2"
 [1.8.x] Fixed #24250 -- Corrected mistakes in FormMixin docs.

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

Re: [Django] #24250: Class FormMixin does not provide "form" variable in centext.

[Django]

#24250: Class FormMixin does not provide "form" variable in centext.
-+-
 Reporter:  4544fa8d |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  FormMixin form   | Triage Stage:  Ready for
  context|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"5d193d042a3cc49033f0e8b5125913650d779496"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5d193d042a3cc49033f0e8b5125913650d779496"
 Fixed #24250 -- Corrected mistakes in FormMixin docs.
 }}}

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

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

Re: [Django] #24250: Class FormMixin does not provide "form" variable in centext.

[Django]

#24250: Class FormMixin does not provide "form" variable in centext.
-+-
 Reporter:  4544fa8d |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  FormMixin form   | Triage Stage:  Ready for
  context|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Accepted => Ready for checkin


Comment:

 Yes, I'll add that. Thanks 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/066.d237fe6bffce77636205b599909c8701%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24269: Django repository not synchronized with transifex

[Django]

#24269: Django repository not synchronized with transifex
-+-
 Reporter:  TheProdigyFilippo|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  1.7
  Internationalization   |
 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 timgraham):

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


Comment:

 Claude, on a related note, it would be great to document the process of
 how to integrate translations from Transifex as well as the schedule for
 doing so (e.g. a checklist item on `docs/internals/howto-release-
 django.txt` for a new major release). Then we'll have something to point
 to that explains why translations on master are "outdated" like this.

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

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

Re: [Django] #24168: TemplateResponse and TemplateView cannot select a specific template engine

[Django]

#24168: TemplateResponse and TemplateView cannot select a specific template 
engine
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  multiple-template-   | Triage Stage:  Ready for
  engines 1.8|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"c65c8f5696eeac056260a0850525d5266dcf8353"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c65c8f5696eeac056260a0850525d5266dcf8353"
 [1.8.x] Skipped tests from refs #24168 on Python 3.2.
 }}}

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

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

[Django] #24270: Wheel package does not contain 'extras' directory

[Django]

#24270: Wheel package does not contain 'extras' directory
+
 Reporter:  mblayman|  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Packaging   |Version:  1.7
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 I installed Django from pip and it installs the whl package file by
 default. While looking for the django_bash_completion script, I discovered
 that the whl does not include the 'extras' directory.

 Since the 'extras' directory is referenced in the documentation
 (https://docs.djangoproject.com/en/1.7/ref/django-admin/#bash-completion),
 it seems appropriate to include 'extras' in the whl package.

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

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

[Django] #24269: Django repository not synchronized with transifex

[Django]

#24269: Django repository not synchronized with transifex
--+
 Reporter:  TheProdigyFilippo |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Internationalization  |Version:  1.7
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Django repository has not actual translations.  It looks like it's not
 synchronized with transifex in any manner. For example this .po file:
 
https://github.com/django/django/blob/master/django/contrib/auth/locale/pl/LC_MESSAGES/django.po
 was last updated almost a half year ago and it gives bad translation. In
 transifex some sentences are translated correctly.

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

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

Re: [Django] #16508: Provide real support for virtual fields

[Django]

#16508: Provide real support for virtual fields
-+-
 Reporter:  vzima|Owner:  pirosb3
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 pirosb3):

 Thanks akaariai,

 If you need any help on my side (given the work I did on Meta) please let
 me know.

 Daniel

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

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

Re: [Django] #24263: Optimization: django.views.generic.dates.BaseDateDetailView

[Django]

#24263: Optimization: django.views.generic.dates.BaseDateDetailView
-+-
 Reporter:  jekka-ua |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Generic views|  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  Optimization | Triage Stage:
  BaseDateDetailView |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jekka-ua):

 It looks like you can use this patch for different versions of 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/066.4d1696a13cf31537a710aaf18db2d1ee%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #24268: Remove Query.having

[Django]

#24268: Remove Query.having
-+-
   Reporter:  akaariai   |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |
  Component:  Database   |Version:  master
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  1
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Instead of Query.having and Query.where we could instead use Query.where
 only, and then split that to where and having parts in the compiler.

 The main reason for doing the split in compiler is that we gain a bit
 simpler Query class without any significant complications to the where
 class.

 There are other cases, too, where such a split would be needed. For
 example, window aggregates can't be filtered on the same query level. So,
 `qs.filter(row_num__lte=10)` would need to be splitted into an outer
 query's where clause.

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

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

Re: [Django] #24265: jinja2 template backend results in KeyError

[Django]

#24265: jinja2 template backend results in KeyError
-+-
 Reporter:  robhudson|Owner:  aaugustin
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  1.8alpha1
 Severity:  Normal   |   Resolution:
 Keywords:  multiple-template-   | Triage Stage:
  engines|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * owner:  nobody => aaugustin
 * keywords:   => multiple-template-engines
 * needs_docs:   => 0


Comment:

 I thought I had taken care of copying before mutating... I'll take care of
 this.

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

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

Re: [Django] #16870: CSRF too strict when no referer is present

[Django]

#16870: CSRF too strict when no referer is present
+--
 Reporter:  rtux|Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  CSRF|  Version:  master
 Severity:  Normal  |   Resolution:  wontfix
 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 aaugustin):

 Perhaps we should document that Django's CSRF protection is incompatible
 with `` and requires at least the
 origin for same-site requests (in which case there are no privacy
 concerns).

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

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

Re: [Django] #16508: Provide real support for virtual fields

[Django]

#16508: Provide real support for virtual fields
-+-
 Reporter:  vzima|Owner:  pirosb3
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 akaariai):

 I'm planning on tackling this issue. The initial plan is to:
   - Change ForeignObjectRel subclasses to real field instances. (For
 example, ForeignKey generates a ManyToOneRel in the related model). The
 Rel instances are already returned from get_field(), but they aren't yet
 field subclasses.
   - Allow direct usage of ForeignObjectRel subclasses. In certain cases it
 can be advantageous to be able to define reverse relations directly. For
 example, see https://github.com/akaariai/django-reverse-unique.
   - Partition ForeignKey to virtual relation field, and concrete data
 field. The former is the model.author, the latter model.author_id's
 backing implementation.
   - Consider other cases where true virtual fields are needed.

 My initial try will be a class structure like:
 {{{
 Field
 RelationField (base class for ForeignKey, ManyToOneRel, maybe also
 ManyToManyField)
 ConcreteField (base class for concrete data fields, for example
 IntegerField, ...)
 }}}

 I expect this to cause a good amount of breakage in 3rd party apps. I'm
 going to use the old good "lets first break things, then fix those cases
 that are complained about".

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

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

Re: [Django] #16870: CSRF too strict when no referer is present

[Django]

#16870: CSRF too strict when no referer is present
+--
 Reporter:  rtux|Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  CSRF|  Version:  master
 Severity:  Normal  |   Resolution:  wontfix
 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 raulcd):

 As per policy! Close ticket :)

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

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

Re: [Django] #16870: CSRF too strict when no referer is present

[Django]

#16870: CSRF too strict when no referer is present
+--
 Reporter:  rtux|Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  CSRF|  Version:  master
 Severity:  Normal  |   Resolution:  wontfix
 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 ubernostrum):

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


Comment:

 Per the ticket/triaging documentation, do not re-open a ticket which has
 been closed "wontfix" by a member of the Django core team:

 https://docs.djangoproject.com/en/1.7/internals/contributing/triaging-
 tickets/#closing-tickets

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

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

Re: [Django] #16870: CSRF too strict when no referer is present

[Django]

#16870: CSRF too strict when no referer is present
+--
 Reporter:  rtux|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  CSRF|  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 raulcd):

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


Comment:

 Reopen bug so we take a look. I also think that things have changed since
 the bug was open and due to new implementation of browsers the % of users
 that may want to not send their HTTP_REFERER header may increase.

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

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

Re: [Django] #24250: Class FormMixin does not provide "form" variable in centext.

[Django]

#24250: Class FormMixin does not provide "form" variable in centext.
-+-
 Reporter:  4544fa8d |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  FormMixin form   | Triage Stage:  Accepted
  context|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by claudep):

 `get_context_data()` is inherited from `ContextMixin` (which only adds the
 view in the context). Does this warrants its presence in `FormMixin` docs?

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

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

[Django] #24267: Simplify Query.build_filter()

[Django]

#24267: Simplify Query.build_filter()
-+-
   Reporter:  akaariai   |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |
  Component:  Database   |Version:  master
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Now that the old way of building lookups isn't supported any more, we
 could restructure build_filter(). Steps included:
   - Remove related field's get_lookup_constraint(), instead write proper
 lookups for relational fields, too.
   - Do not use lookup_name in build_filter(), instead use Lookup flags
 where needed.
   - Ultimate goal could be usage of resolve_ref() in build_filter()
 instead of direct use of setup_joins(). In this case build_filter() would
 be simplified a lot. It is uncertain if this goal is achievable.

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

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