[Django] #22833: 1.7 migrations can't delete codependent "through" models

[Django]

#22833: 1.7 migrations can't delete codependent "through" models
+
 Reporter:  mozumder@…  |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  1.7-beta-2
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 Hi,

 I'm using Django 1.7b4, and I'm testing the migrations.  I have this
 existing model in the database:


 {{{
 class BlocksList(Named, Ordered):
 blocks_list_assignments = models.ManyToManyField(
   Block,
   through='BlocksListAssignment'
   )
 family = models.ForeignKey(
 BlockFamily,
 verbose_name=_("Family Name"),
 null=True,
 blank=True,
 )
 def __str__(self):  # Python 3: def __str__(self):
 return self.name


 class BlocksListAssignment(Ordered):
 block = models.ForeignKey(Block)
 block_list = models.ForeignKey(BlocksList)
 def __str__(self):  # Python 3: def __str__(self):
 return self.block_list.name + ": %s" % self.block

 }}}

 I'm trying to delete this with the makemigrations/migrate command, with
 this in my migrations file:


 {{{
 migrations.DeleteModel(
 name='BlocksList',
 ),
 migrations.DeleteModel(
 name='BlocksListAssignment',
 ),

 }}}

 It looks like the co-dependencies prevent the migrations from deleting
 both models, because I constantly get:

 {{{

 Running migrations:
   Applying blocks.0014_auto_20140613_2227...Traceback (most recent call
 last):
   File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4
 /site-packages/django/apps/config.py", line 152, in get_model
 return self.models[model_name.lower()]
 KeyError: 'blockslistassignment'

 During handling of the above exception, another exception occurred:

 Traceback (most recent call last):
   File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4
 /site-packages/django/db/migrations/state.py", line 76, in render
 model = self.apps.get_model(lookup_model[0], lookup_model[1])
   File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4
 /site-packages/django/apps/registry.py", line 190, in get_model
 return self.get_app_config(app_label).get_model(model_name.lower())
   File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4
 /site-packages/django/apps/config.py", line 155, in get_model
 "App '%s' doesn't have a '%s' model." % (self.label, model_name))
 LookupError: App 'blocks' doesn't have a 'blockslistassignment' model.

 During handling of the above exception, another exception occurred:

 Traceback (most recent call last):
   File "./manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4
 /site-packages/django/core/management/__init__.py", line 427, in
 execute_from_command_line
 utility.execute()
   File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4
 /site-packages/django/core/management/__init__.py", line 419, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4
 /site-packages/django/core/management/base.py", line 288, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4
 /site-packages/django/core/management/base.py", line 337, in execute
 output = self.handle(*args, **options)
   File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4
 /site-packages/django/core/management/commands/migrate.py", line 146, in
 handle
 executor.migrate(targets, plan, fake=options.get("fake", False))
   File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4
 /site-packages/django/db/migrations/executor.py", line 62, in migrate
 self.apply_migration(migration, fake=fake)
   File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4
 /site-packages/django/db/migrations/executor.py", line 90, in
 apply_migration
 if self.detect_soft_applied(migration):
   File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4
 /site-packages/django/db/migrations/executor.py", line 134, in
 detect_soft_applied
 apps = project_state.render()
   File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4
 /site-packages/django/db/migrations/state.py", line 86, in render
 model=lookup_model,
 ValueError: Lookup failed for model referenced by field
 blocks.BlocksList.blocks_list_assignments: blocks.BlocksListAssignment

 }}}

 Anyways to get around this I have to recreate the database and start from
 fixtures.

 Do let me 

Re: [Django] #20879: BinaryField doesn't work with Oracle on Python3

[Django]

#20879: BinaryField doesn't work with Oracle on Python3
-+-
 Reporter:  slafs|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |  1.6-beta-1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  BinaryField Oracle   | Triage Stage:  Accepted
  Python3|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by shai):

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


Comment:

 Some related fixes were introduced in #22715. The Django test-suite passes
 on 1.7 and master with python3 and cx_Oracle 5.1.3; so I suspect this has
 been solved.

 If this is not the case, please reopen.

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

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

Re: [Django] #13296: order_with_respect_to fails to correctly track _order after deleting entries

[Django]

#13296: order_with_respect_to fails to correctly track _order after deleting
entries
-+-
 Reporter:  krijesta |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.1
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_better_patch:  0 => 1


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

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

Re: [Django] #22371: AttributeError during replaying/loading of migration: 'module' object has no attribute 'RemovedModel'

[Django]

#22371: AttributeError during replaying/loading of migration: 'module' object 
has
no attribute 'RemovedModel'
+--
 Reporter:  blueyed |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7-beta-1
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by timo):

 Loic, any thoughts on if we should do anything here?

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

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

Re: [Django] #21021: Default geom_type attribute for GeometryWidget should be "Geometry", not "Unknown"

[Django]

#21021: Default geom_type attribute for GeometryWidget should be "Geometry", not
"Unknown"
-+-
 Reporter:  leplatrem|Owner:
 Type:   |  EricBoersma
  Cleanup/optimization   |   Status:  assigned
Component:  GIS  |  Version:
 Severity:  Normal   |  1.6-beta-1
 Keywords:  minor|   Resolution:
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  1
 |UI/UX:  0
-+-
Changes (by timo):

 * needs_better_patch:  0 => 1


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

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

Re: [Django] #18654: Support for model properties that are not fields in LayerMapping

[Django]

#18654: Support for model properties that are not fields in LayerMapping
--+
 Reporter:  msopacua  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  GIS   |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  LayerMapping  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timo):

 * needs_better_patch:  0 => 1


Comment:

 Patch no longer applies cleanly.

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

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

Re: [Django] #18100: Deleting model instances with deferred fields don't trigger deletion signals

[Django]

#18100: Deleting model instances with deferred fields don't trigger deletion
signals
-+-
 Reporter:  charettes|Owner:  charettes
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  deferred delete  |  Needs documentation:  0
  signals|  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_better_patch:  0 => 1


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

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

Re: [Django] #22784: Schema migration: rename tables

[Django]

#22784: Schema migration: rename tables
---+--
 Reporter:  maxi   |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Migrations |  Version:  1.7-beta-2
 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 shai):

 Sometimes backends do things that the engine proper doesn't support by
 performing extra work -- the Sqlite backend, as a prime example, recreates
 tables as an implementation of alter-column; the usually-saner Oracle
 backend jumps through hoops to change a column from TextField to CharField
 or vice-versa, which isn't supported by the Oracle database.

 Introducing the flag as requested here means that table-renaming is an
 optional feature of schema editors. That may be acceptable, or not -- I'm
 not even sure what I think of it. I think it may be worth a discussion on
 the DevelopersMailingList.

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

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

Re: [Django] #19137: runserver child started via autoreload won't always exit cleanly

[Django]

#19137: runserver child started via autoreload won't always exit cleanly
-+-
 Reporter:  santtu   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.4
  commands)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

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


Comment:

 I think we should focus on gunicorn integration (#21978) rather than what
 seems to be an obscure issue.

 Actually, I think this may be fixed by #21773.

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

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

Re: [Django] #20725: Oracle+Python3: Django test suite segfaults

[Django]

#20725: Oracle+Python3: Django test suite segfaults
-+-
 Reporter:  shai |Owner:  shai
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |  1.6-beta-1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  oracle python3   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 This is fixed with cx_Oracle 5.1.3 per [https://groups.google.com/d/topic
 /django-developers/6FLjKkVRx2Y/discussion Shai]. I have also been able to
 run the tests on Oracle with 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/062.a72ffe1f4fc655de9c6aa3bb7fd3d108%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22389: contrib.formtools show errors while running test suite on windows

[Django]

#22389: contrib.formtools show errors while running test suite on windows
---+-
 Reporter:  anubhav9042|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.formtools  |  Version:  master
 Severity:  Normal |   Resolution:  duplicate
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by timo):

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


Comment:

 Duplicate of #22772 which has been 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/069.6c272dc050d59365f28cf45f091b6c40%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22395: Deleting a model and fields that relate to it results in ValueError: Related model '.' cannot be resolved

[Django]

#22395: Deleting a model and fields that relate to it results in ValueError:
Related model '.' cannot be resolved
+--
 Reporter:  melinath|Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.7-beta-1
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by timo):

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

Re: [Django] #18501: Custom fields as foreign keys fix

[Django]

#18501: Custom fields as foreign keys fix
-+-
 Reporter:  msopacua |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  RelatedField |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

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

Re: [Django] #19396: Allow customized ModelState classes

[Django]

#19396: Allow customized ModelState classes
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_better_patch:  0 => 1


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

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

Re: [Django] #18148: django.contrib.sites.managers.CurrentSiteManager should be able to span multiple models

[Django]

#18148: django.contrib.sites.managers.CurrentSiteManager should be able to span
multiple models
---+
 Reporter:  rgeoghegan |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.sites  |  Version:  1.4
 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 timo):

 * needs_better_patch:  0 => 1


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

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

Re: [Django] #10944: Site app should be able to make absolute URLs.

[Django]

#10944: Site app should be able to make absolute URLs.
---+--
 Reporter:  jdunck |Owner:  krzysiumed
 Type:  New feature|   Status:  assigned
Component:  contrib.sites  |  Version:  1.0
 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 timo):

 * needs_better_patch:  0 => 1


Comment:

 Patch no longer applies cleanly.

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

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

Re: [Django] #17133: get_script_name goofs when there is Apache URL rewriting

[Django]

#17133: get_script_name goofs when there is Apache URL rewriting
--+
 Reporter:  gjanee@…  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  HTTP handling |  Version:  1.3
 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 timo):

 * needs_tests:  0 => 1


Comment:

 Is there any way to add a test?

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

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

Re: [Django] #15279: Inheritance of fields from a single abstract base class through multiple abstract classes causes errors.

[Django]

#15279: Inheritance of fields from a single abstract base class through multiple
abstract classes causes errors.
-+-
 Reporter:  melinath |Owner:  melinath
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  abstract |  Needs documentation:  0
  inheritance|  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_better_patch:  0 => 1


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

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

Re: [Django] #19625: mysql 5.1 large decimalfield lookups return too few results

[Django]

#19625: mysql 5.1 large decimalfield lookups return too few results
-+-
 Reporter:  wdoekes  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

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


Comment:

 As MySQL 5.1 is End of life as of December 31, 2013, I think we should
 close 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/065.511f78ea13ff914c2a45805be7000615%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #11458: Add GPolylineOptions and GPolygonOptions to django.contrib.gis.maps.google.overlays

[Django]

#11458: Add GPolylineOptions and GPolygonOptions to
django.contrib.gis.maps.google.overlays
-+-
 Reporter:  tomchuk  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  GOverlay GoogleMap   | Triage Stage:  Accepted
  GPolylineOptions GPolygonOptions   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

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

Re: [Django] #12410: add support for St_Line_Locate_Point to geodjango postgis backend

[Django]

#12410: add support for St_Line_Locate_Point to geodjango postgis backend
--+
 Reporter:  IanWard   |Owner:  jbronn
 Type:  New feature   |   Status:  assigned
Component:  GIS   |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  St_Line_Locate_Point  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timo):

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

Re: [Django] #7857: manage.py shell, dbshell funtionality

[Django]

#7857: manage.py shell, dbshell funtionality
-+-
 Reporter:  Sanha|Owner:  marclurr
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  manage.py,   |  Needs documentation:  0
  testserver, shell, dbshell |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

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


Comment:

 I agree with Aymeric (aaugustin), that this doesn't seem very necessary.
 Please use the snippet if you need it.

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

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

[django/django] 79956d: Fixed #22440 -- Updated ConditionalGetMiddleware t...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 79956d06946c881cb71958f27a12f62b9cab8de5
  
https://github.com/django/django/commit/79956d06946c881cb71958f27a12f62b9cab8de5
  Author: Mark Lavin 
  Date:   2014-06-13 (Fri, 13 Jun 2014)

  Changed paths:
M django/middleware/http.py
M tests/middleware/tests.py

  Log Message:
  ---
  Fixed #22440 -- Updated ConditionalGetMiddleware to comply with RFC 2616.


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

Re: [Django] #22440: Incorrect Behavior of ConditionalGetMiddleware

[Django]

#22440: Incorrect Behavior of ConditionalGetMiddleware
---+
 Reporter:  mlavin |Owner:  mlavin
 Type:  Bug|   Status:  closed
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"79956d06946c881cb71958f27a12f62b9cab8de5"]:
 {{{
 #!CommitTicketReference repository=""
 revision="79956d06946c881cb71958f27a12f62b9cab8de5"
 Fixed #22440 -- Updated ConditionalGetMiddleware to comply with RFC 2616.
 }}}

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

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

Re: [Django] #19126: Allow runserver to bypass model validation

[Django]

#19126: Allow runserver to bypass model validation
-+-
 Reporter:  direvus  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

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


Comment:

 The system check framework's `SILENCED_SYSTEM_CHECKS` setting allows you
 to ignore model validation errors and allow `runserver` to proceed.

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

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

Re: [Django] #14722: @last_modified should ignore lack of etag method when USE_ETAGS is enabled

[Django]

#14722: @last_modified should ignore lack of etag method when USE_ETAGS is 
enabled
---+
 Reporter:  lamby  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  HTTP handling  |  Version:  1.2
 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 timo):

 * needs_better_patch:  0 => 1


Comment:

 Patch needs to be updated.

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

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

Re: [Django] #9071: Can't disable "add" popup links in the admin

[Django]

#9071: Can't disable "add" popup links in the admin
---+
 Reporter:  jacob  |Owner:  burzak
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  1.0
 Severity:  Normal |   Resolution:
 Keywords:  pyconuk| Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  1
---+
Changes (by timo):

 * needs_better_patch:  0 => 1


Comment:

 Needs a patch that applies cleanly.

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

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

Re: [Django] #13794: Django does not respect to_field's model on an inline model admin

[Django]

#13794: Django does not respect to_field's model on an inline model admin
-+-
 Reporter:  sebastien@…  |Owner:  gautier
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin inline | Triage Stage:  Accepted
  to_field formset   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_better_patch:  0 => 1


Comment:

 The latest version of of the patch doesn't include the test from the
 earlier version. Please uncheck "Patch needs improvement" if someone can
 update it. 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/079.d2af8d8901cdffa6f1cde282040d3dc5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #18620: Prefer current Site when checking M2M in "shortcut"/"view_on_site" redirect

[Django]

#18620: Prefer current Site when checking M2M in "shortcut"/"view_on_site" 
redirect
--+
 Reporter:  mtigas|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.contenttypes  |  Version:  1.4
 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 timo):

 * needs_better_patch:  0 => 1


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

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

Re: [Django] #22795: Iterating all object fields in template

[Django]

#22795: Iterating all object fields in template
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.6
Component:  Database layer   |   Resolution:  wontfix
  (models, ORM)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

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


Comment:

 I suspect exact needs will be project specific so it's not something that
 needs to live in core.

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

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

Re: [Django] #22816: Oracle test failure: Inspecting NullBooleanField

[Django]

#22816: Oracle test failure: Inspecting NullBooleanField
-+-
 Reporter:  shai |Owner:  shai
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |  1.7-beta-2
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  oracle   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Shai Berger ):

 In [changeset:"4b922b809413eb9e9d59be0c3b41d0cedefbeb29"]:
 {{{
 #!CommitTicketReference repository=""
 revision="4b922b809413eb9e9d59be0c3b41d0cedefbeb29"
 [1.7.x] Fixed #22816 -- Corrected Oracle feature flag and fixed
 introspection test

 Backport of 6122904 from master
 }}}

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

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

[django/django] 4b922b: [1.7.x] Fixed #22816 -- Corrected Oracle feature f...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 4b922b809413eb9e9d59be0c3b41d0cedefbeb29
  
https://github.com/django/django/commit/4b922b809413eb9e9d59be0c3b41d0cedefbeb29
  Author: Shai Berger 
  Date:   2014-06-14 (Sat, 14 Jun 2014)

  Changed paths:
M django/db/backends/__init__.py
M django/db/backends/oracle/base.py
M tests/introspection/tests.py

  Log Message:
  ---
  [1.7.x] Fixed #22816 -- Corrected Oracle feature flag and fixed introspection 
test

Backport of 6122904 from master


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

Re: [Django] #22816: Oracle test failure: Inspecting NullBooleanField

[Django]

#22816: Oracle test failure: Inspecting NullBooleanField
-+-
 Reporter:  shai |Owner:  shai
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |  1.7-beta-2
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  oracle   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Shai Berger ):

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


Comment:

 In [changeset:"612290400f79fb2293a6a0b0cfa5743ab0cef6b1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="612290400f79fb2293a6a0b0cfa5743ab0cef6b1"
 Fixed #22816 -- Corrected Oracle feature flag and fixed introspection test
 }}}

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

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

[django/django] 612290: Fixed #22816 -- Corrected Oracle feature flag and ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 612290400f79fb2293a6a0b0cfa5743ab0cef6b1
  
https://github.com/django/django/commit/612290400f79fb2293a6a0b0cfa5743ab0cef6b1
  Author: Shai Berger 
  Date:   2014-06-14 (Sat, 14 Jun 2014)

  Changed paths:
M django/db/backends/__init__.py
M django/db/backends/oracle/base.py
M tests/introspection/tests.py

  Log Message:
  ---
  Fixed #22816 -- Corrected Oracle feature flag and fixed introspection test


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

Re: [Django] #22816: Oracle test failure: Inspecting NullBooleanField

[Django]

#22816: Oracle test failure: Inspecting NullBooleanField
-+-
 Reporter:  shai |Owner:  shai
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |  1.7-beta-2
 Severity:  Release blocker  |   Resolution:
 Keywords:  oracle   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by shai):

 @aaugustin and @manfre have [https://groups.google.com/forum/#!msg/django-
 developers/wGjBCWsWKZQ/ARuP0R7ecAMJ confirmed] that the flag is needed by
 django-pymssql, a 3rd-party backend. So, I'm just fixing the Oracle issue.

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

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

Re: [Django] #18174: Model inheritance pointers doesn't refer to parent to refer to grandparents

[Django]

#18174: Model inheritance pointers doesn't refer to parent to refer to 
grandparents
-+-
 Reporter:  phowe|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_better_patch:  0 => 1


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

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

Re: [Django] #13559: Need a contextprocessor for current site

[Django]

#13559: Need a contextprocessor for current site
---+
 Reporter:  tonnzor|Owner:  chrismedrela
 Type:  New feature|   Status:  assigned
Component:  contrib.sites  |  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 timo):

 * needs_better_patch:  0 => 1


Comment:

 I left comments for improvement on PR. Please uncheck "Patch needs
 improvement" when you update it, thanks.

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

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

Re: [Django] #15184: Error when subclassing models.ForeignKey field

[Django]

#15184: Error when subclassing models.ForeignKey field
-+-
 Reporter:  rupa108  |Owner:
 Type:  Bug  |  furious_luke
Component:  Database layer   |   Status:  new
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  ForeignKey, models,  | Triage Stage:  Accepted
  subclassing|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_better_patch:  0 => 1


Comment:

 Patch needs to be updated to apply cleanly.

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

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

Re: [Django] #19973: Management commands migration to argparse

[Django]

#19973: Management commands migration to argparse
-+-
 Reporter:  jose |Owner:  jose
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Core (Management |   Resolution:
  commands)  | Triage Stage:  Ready for
 Severity:  Normal   |  checkin
 Keywords:  optparse, argparse,  |  Needs documentation:  0
  basecommand|  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by timo):

 Claude, do you know if this will obsolete #11407?

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

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

Re: [Django] #18105: Investigate possible misuse of Context

[Django]

#18105: Investigate possible misuse of Context
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Template system   |  Version:  1.4
 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 timo):

 * needs_better_patch:  0 => 1


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

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

Re: [Django] #22832: admin.autodiscover() missing

[Django]

#22832: admin.autodiscover() missing
---+--
 Reporter:  Matej  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.6
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by valberg):

 Due to the new app loading mechanism introduced in 1.7, django will do the
 autodiscover automatically.

 See https://docs.djangoproject.com/en/1.7/ref/applications/ for more about
 the app loading process.

 And the release notes https://docs.djangoproject.com/en/1.7/releases/1.7
 /#app-loading-refactor for information on what effects this new mechanism
 has.

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

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

Re: [Django] #22832: admin.autodiscover() missing

[Django]

#22832: admin.autodiscover() missing
---+--
 Reporter:  Matej  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.6
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timo):

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


Comment:

 Please ​https://docs.djangoproject.com/en/1.6/ref/contrib/gis/tutorial/ if
 you are using Django 1.6. That line is no longer necessary 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/063.cb0da4bd3a53e28e7d37f8b9c1762401%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22794: Using WizardForm with only one model

[Django]

#22794: Using WizardForm with only one model
--+--
 Reporter:  sofi.vasserman@…  |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  Uncategorized |  Version:  1.6
 Severity:  Normal|   Resolution:  wontfix
 Keywords:  WizardForm| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by timo):

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


Comment:

 I'm not sure an implementation of this is going to be sufficiently simple
 and general enough for inclusion in Django itself. It you could provide
 some working code for idea, perhaps we could consider it.

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

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

[Django] #22832: admin.autodiscover() missing

[Django]

#22832: admin.autodiscover() missing
---+
 Reporter:  Matej  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Hi,
 in the geoDjango tutorial:
 https://docs.djangoproject.com/en/dev/ref/contrib/gis/tutorial/
 close to the bottom of the page there is this block of code:

 from django.conf.urls import url, include
 from django.contrib.gis import admin

 urlpatterns = [
 url(r'^admin/', include(admin.site.urls)),
 ]

 that should have also included the following line:
 admin.autodiscover()

 otherwise, the admin page says: you don't have permission to edit
 anything.

 Matej

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

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

Re: [Django] #18510: Options._fill_related_objects_cache should assert for app_cache_ready() or deal with app_cache_ready() == False

[Django]

#18510: Options._fill_related_objects_cache should assert for app_cache_ready() 
or
deal with app_cache_ready() == False
-+-
 Reporter:  vanschelven  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  app-loading  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * keywords:   => app-loading
 * status:  new => closed
 * resolution:   => fixed


Comment:

 This is "fixed" by the app-loading refactor, in the sense that Django now
 throws an explicit exception.

 '''stable/1.6.x -- obscure test failure'''

 {{{
 Creating test database for alias 'default'...
 E
 ==
 ERROR: test_get_field_by_name (testapp.tests.SimpleTest)
 --
 Traceback (most recent call last):
   File "~/django/django/db/models/options.py", line 371, in
 get_field_by_name
 return self._name_map[name]
 KeyError: 'userprofile'

 During handling of the above exception, another exception occurred:

 Traceback (most recent call last):
   File "~/django/t18510/testapp/tests.py", line 10, in
 test_get_field_by_name
 User._meta.get_field_by_name('userprofile')
   File "~/django/django/db/models/options.py", line 377, in
 get_field_by_name
 % (self.object_name, name))
 django.db.models.fields.FieldDoesNotExist: User has no field named
 'userprofile'

 --
 Ran 1 test in 0.002s

 FAILED (errors=1)
 Destroying test database for alias 'default'...
 }}}

 '''stable/1.7.x -- explicit exception'''

 {{{
 Traceback (most recent call last):
   File "~/django/django/db/models/options.py", line 414, in
 get_field_by_name
 return self._name_map[name]
 AttributeError: 'Options' object has no attribute '_name_map'

 During handling of the above exception, another exception occurred:

 Traceback (most recent call last):
   File "~/django/django/db/models/options.py", line 559, in
 get_all_related_m2m_objects_with_model
 cache = self._related_many_to_many_cache
 AttributeError: 'Options' object has no attribute
 '_related_many_to_many_cache'

 During handling of the above exception, another exception occurred:

 Traceback (most recent call last):
   File "./manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "~/django/django/core/management/__init__.py", line 385, in
 execute_from_command_line
 utility.execute()
   File "~/django/django/core/management/__init__.py", line 354, in execute
 django.setup()
   File "~/django/django/__init__.py", line 21, in setup
 apps.populate(settings.INSTALLED_APPS)
   File "~/django/django/apps/registry.py", line 106, in populate
 app_config.import_models(all_models)
   File "~/django/django/apps/config.py", line 190, in import_models
 self.models_module = import_module(models_module_name)
   File "~/.virtualenvs/django/lib/python3.4/importlib/__init__.py", line
 104, in import_module
 return _bootstrap._gcd_import(name[level:], package, level)
   File "", line 2231, in _gcd_import
   File "", line 2214, in _find_and_load
   File "", line 2203, in
 _find_and_load_unlocked
   File "", line 1200, in _load_unlocked
   File "", line 1129, in _exec
   File "", line 1448, in exec_module
   File "", line 321, in
 _call_with_frames_removed
   File "~/django/t18510/testapp/models.py", line 5, in 
 User._meta.get_field_by_name('username')
   File "~/django/django/db/models/options.py", line 416, in
 get_field_by_name
 cache = self.init_name_map()
   File "~/django/django/db/models/options.py", line 445, in init_name_map
 for f, model in self.get_all_related_m2m_objects_with_model():
   File "~/django/django/db/models/options.py", line 561, in
 get_all_related_m2m_objects_with_model
 cache = self._fill_related_many_to_many_cache()
   File "~/django/django/db/models/options.py", line 575, in
 _fill_related_many_to_many_cache
 for klass in self.apps.get_models():
   File "~/.virtualenvs/django/lib/python3.4/functools.py", line 428, in
 wrapper
 result = user_function(*args, **kwds)
   File "~/django/django/apps/registry.py", line 156, in get_models
 self.check_ready()
   File "~/django/django/apps/registry.py", line 119, in check_ready
 raise RuntimeError("App registry isn't ready yet.")
 RuntimeError: App registry isn't 

Re: [Django] #18603: Adding support for PEP 302 importers

[Django]

#18603: Adding support for PEP 302 importers
--+
 Reporter:  bhuztez   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:
 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 timo):

 * needs_better_patch:  0 => 1


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

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

[Django] #22831: Migrations should provide a way to 'upgrade' from south via loaddata

[Django]

#22831: Migrations should provide a way to 'upgrade' from south via loaddata
---+
 Reporter:  gcbirzan   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Migrations |Version:  1.7-beta-2
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 People with existing south migrations that contain any kind of data
 migrations will need to dump their initial data in a fixture and re-create
 it with 1.7 migrations. This is impossible in the current state unless a)
 there's an undocumented way to do it, b) one uses mock (or monkey patches
 by hand) to change django.core.serializers.python._get_model to the one
 from the migration.

 The reason that b is needed is because if you modify the model afterwards,
 loaddata will explode since the model is different.

 Additionally, since migrations are now almost 10 times slower than with
 south, nobody will want to create proper data migrations, so this is
 really the best way to 'upgrade' from south.

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

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

Re: [Django] #12509: Feature: Selector Inlines

[Django]

#12509: Feature: Selector Inlines
-+-
 Reporter:  zain |Owner:  zain
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  soc2009
 Severity:  Normal   |  /admin-ui
 Keywords:  design_ux|   Resolution:
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  1
 |UI/UX:  1
-+-
Changes (by timo):

 * needs_better_patch:  0 => 1


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

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

Re: [Django] #18332: No generic way to get database backend version

[Django]

#18332: No generic way to get database backend version
-+-
 Reporter:  apollovy@…   |Owner:
 Type:  Bug  |  vanessagomes
Component:  Database layer   |   Status:  new
  (models, ORM)  |  Version:  1.3
 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 timo):

 * needs_better_patch:  0 => 1


Comment:

 Patch needs to be updated to apply cleanly.

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

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

Re: [Django] #7930: FORCE_SCRIPT_NAME does not work with dev server

[Django]

#7930: FORCE_SCRIPT_NAME does not work with dev server
---+
 Reporter:  ElliottM   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:  wontfix
 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 timo):

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


Comment:

 Given the last comment, I'm going to close this as "won't fix."

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

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

Re: [Django] #22550: QuerySet last() and reverse() confusing when used with ordered slices

[Django]

#22550: QuerySet last() and reverse() confusing when used with ordered slices
-+-
 Reporter:  jdufresne|Owner:  merll
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_better_patch:  0 => 1


Comment:

 I left comments for improvement on PR. Please uncheck "Patch needs
 improvement" when you update it, thanks.

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

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

Re: [Django] #18081: Proxy model foreign keys not created properly by syncdb

[Django]

#18081: Proxy model foreign keys not created properly by syncdb
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_better_patch:  0 => 1


Comment:

 Two years later, I guess the branch probably doesn't merge cleanly.

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

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

Re: [Django] #18088: Add a "supports_foreign_key" database feature to ease testing

[Django]

#18088: Add a "supports_foreign_key" database feature to ease testing
--+
 Reporter:  akaariai  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  Version:  1.4
 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 timo):

 * needs_better_patch:  0 => 1


Comment:

 Patch no longer applies cleanly.

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

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

Re: [Django] #17522: ModelAdmin.ordering validation too strict

[Django]

#17522: ModelAdmin.ordering validation too strict
-+-
 Reporter:  sebastian|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin, validation,   | Triage Stage:  Accepted
  ordering, strict   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_better_patch:  0 => 1


Comment:

 Patch no longer applies cleanly.

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

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

Re: [Django] #8122: Better way of testing for cookies

[Django]

#8122: Better way of testing for cookies
--+
 Reporter:  jcassee   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.sessions  |  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 timo):

 * needs_better_patch:  0 => 1


Comment:

 Patch no longer applies cleanly.

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

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

Re: [Django] #17761: save_base() does not properly detect when MTI parent key is unset

[Django]

#17761: save_base() does not properly detect when MTI parent key is unset
-+-
 Reporter:  agriffis |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_better_patch:  0 => 1


Comment:

 I haven't verified if this is still an issue, but the patch no longer
 applies cleanly.

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

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

[Django] #22830: GeoDjango dwithin errors when using django.contrib.gis.measure.D

[Django]

#22830: GeoDjango dwithin errors when using django.contrib.gis.measure.D
+
 Reporter:  django@…|  Owner:  nobody
 Type:  Bug | Status:  new
Component:  GIS |Version:  1.6
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 First off, I started a StackOverflow thread
 [http://stackoverflow.com/questions/24194710/geodjango-dwithin-error-
 argument-of-type-geoqueryset-is-not-iterable here] but haven't come up
 with an answer yet. I think there may be a bug in Django somewhere.

 Versions: Python 2.7.6, Django 1.6.5, Postgres 9.3.4, PostGIS 2.1.3,
 psycopg2 2.5.3 on RHEL 6.5

 Here's the model I'm using:

 {{{
 #!python
 class Location(models.Model):
 name = models.CharField(max_length=255)
 geometry = models.MultiPolygonField(blank=True, default=None,
 null=True)
 objects = models.GeoManager()  # override the default manager with a
 GeoManager instance
 parent = models.ForeignKey('self', blank=True, default=None,
 null=True)

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

 This query should work
 [https://docs.djangoproject.com/en/1.6/ref/contrib/gis/geoquerysets/#std
 :fieldlookup-dwithin according to the docs]:

 {{{
 #!python
 touching_locations =
 Location.objects.filter(geometry__dwithin=(location.geometry, D(km=5)))
 logging.debug(type(touching_locations))
 logging.debug(len(touching_locations))
 }}}

 But it doesn't. The first debug call works, but the second throws a
 `ValueError`:

 {{{
 
 ValueError: Only numeric values of degree units are allowed on geographic
 DWithin queries.
 }}}

 If I make a small change by changing `D(km=5)` to `5`:

 {{{
 #!python
 touching_locations =
 Location.objects.filter(geometry__dwithin=(location.geometry, 5))
 logging.debug(type(touching_locations))
 logging.debug(len(touching_locations))
 }}}

 All of a sudden it works. The output I get is this:

 {{{
 
 54
 }}}

 Is there a bug somewhere in Django? Am I misunderstanding how to use `D`?
 Are the Django docs incorrect? Is something else going on here? I
 appreciate any help I can get. 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/064.4fa2f190eff13fe5715fd102517e0e40%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22715: Failing tests on Oracle/Python 3

[Django]

#22715: Failing tests on Oracle/Python 3
-+--
 Reporter:  timo |Owner:  shai
 Type:  Bug  |   Status:  closed
Component:  Python 3 |  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by Tim Graham ):

 In [changeset:"1cb5dfe05f4e8363a7cf39d400e328f4b1c33366"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1cb5dfe05f4e8363a7cf39d400e328f4b1c33366"
 [1.7.x] Added django.utils.six.buffer_types

 and used it in the Oracle SchemaEditor. Refs #22715.

 Backport of 06c0e740a4 from master
 }}}

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

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

[django/django] 1cb5df: [1.7.x] Added django.utils.six.buffer_types

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 1cb5dfe05f4e8363a7cf39d400e328f4b1c33366
  
https://github.com/django/django/commit/1cb5dfe05f4e8363a7cf39d400e328f4b1c33366
  Author: Shai Berger 
  Date:   2014-06-13 (Fri, 13 Jun 2014)

  Changed paths:
M django/db/backends/oracle/schema.py
M django/utils/six.py

  Log Message:
  ---
  [1.7.x] Added django.utils.six.buffer_types

and used it in the Oracle SchemaEditor. Refs #22715.

Backport of 06c0e740a4 from master


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

Re: [Django] #22715: Failing tests on Oracle/Python 3

[Django]

#22715: Failing tests on Oracle/Python 3
-+--
 Reporter:  timo |Owner:  shai
 Type:  Bug  |   Status:  closed
Component:  Python 3 |  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by Tim Graham ):

 In [changeset:"06c0e740a41f64a49a11569e76edee7be04770e0"]:
 {{{
 #!CommitTicketReference repository=""
 revision="06c0e740a41f64a49a11569e76edee7be04770e0"
 Added django.utils.six.buffer_types

 and used it in the Oracle SchemaEditor. Refs #22715.
 }}}

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

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

[django/django] 06c0e7: Added django.utils.six.buffer_types

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 06c0e740a41f64a49a11569e76edee7be04770e0
  
https://github.com/django/django/commit/06c0e740a41f64a49a11569e76edee7be04770e0
  Author: Shai Berger 
  Date:   2014-06-13 (Fri, 13 Jun 2014)

  Changed paths:
M django/db/backends/oracle/schema.py
M django/utils/six.py

  Log Message:
  ---
  Added django.utils.six.buffer_types

and used it in the Oracle SchemaEditor. Refs #22715.


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

Re: [Django] #22771: TestCase.client.logout fails when using custom authentication backend not based on AUTH_USER_MODEL

[Django]

#22771: TestCase.client.logout fails when using custom authentication backend 
not
based on AUTH_USER_MODEL
-+-
 Reporter:  xafer|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Testing framework|  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  logout test  | Triage Stage:
  AUTH_USER_MODEL|  Unreviewed
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:"50b9313e0a0739dfe1ac699449b66ed3e62add51"]:
 {{{
 #!CommitTicketReference repository=""
 revision="50b9313e0a0739dfe1ac699449b66ed3e62add51"
 Fixed #22771 -- Fixed test.Client.logout when using custom auth backend.
 }}}

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

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

[django/django] 50b931: Fixed #22771 -- Fixed test.Client.logout when usin...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 50b9313e0a0739dfe1ac699449b66ed3e62add51
  
https://github.com/django/django/commit/50b9313e0a0739dfe1ac699449b66ed3e62add51
  Author: Xavier Fernandez 
  Date:   2014-06-13 (Fri, 13 Jun 2014)

  Changed paths:
M django/test/client.py
A tests/test_client_regress/auth_backends.py
M tests/test_client_regress/tests.py

  Log Message:
  ---
  Fixed #22771 -- Fixed test.Client.logout when using custom auth backend.


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

Re: [Django] #22477: Remove contrib middleware from MIDDLEWARE_CLASSES global defaults

[Django]

#22477: Remove contrib middleware from MIDDLEWARE_CLASSES global defaults
-+-
 Reporter:  mlavin   |Owner:  mlavin
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Core (Other) |  1.7-beta-2
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"4696cd9671243958fd4a596631d75b3cbca325c3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="4696cd9671243958fd4a596631d75b3cbca325c3"
 Fixed #22477 -- Removed contrib middleware from the global settings
 defaults.

 Also added a compatibility check for changed middleware defaults.

 Forwardport of d94de802d3 from stable/1.7.x
 }}}

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

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

[django/django] 4696cd: Fixed #22477 -- Removed contrib middleware from th...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4696cd9671243958fd4a596631d75b3cbca325c3
  
https://github.com/django/django/commit/4696cd9671243958fd4a596631d75b3cbca325c3
  Author: mlavin 
  Date:   2014-06-13 (Fri, 13 Jun 2014)

  Changed paths:
M django/conf/global_settings.py
M django/contrib/auth/tests/test_context_processors.py
M django/core/checks/__init__.py
A django/core/checks/compatibility/django_1_7_0.py
M docs/ref/settings.txt
M docs/releases/1.7.txt
M tests/admin_scripts/tests.py
M tests/check_framework/tests.py
M tests/runtests.py

  Log Message:
  ---
  Fixed #22477 -- Removed contrib middleware from the global settings defaults.

Also added a compatibility check for changed middleware defaults.

Forwardport of d94de802d3 from stable/1.7.x


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

Re: [Django] #19973: Management commands migration to argparse

[Django]

#19973: Management commands migration to argparse
-+-
 Reporter:  jose |Owner:  jose
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Core (Management |   Resolution:
  commands)  | Triage Stage:  Ready for
 Severity:  Normal   |  checkin
 Keywords:  optparse, argparse,  |  Needs documentation:  0
  basecommand|  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

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

Re: [Django] #17903: `ModelBackend.get_all_permissions` returns permissions for inactive users

[Django]

#17903: `ModelBackend.get_all_permissions` returns permissions for inactive 
users
--+--
 Reporter:  SmileyChris   |Owner:  jorgecarleitao
 Type:  Bug   |   Status:  assigned
Component:  contrib.auth  |  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 timo):

 * needs_better_patch:  0 => 1


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

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

Re: [Django] #22778: Specify default value for a Model's RelatedFields related_name.

[Django]

#22778: Specify default value for a Model's RelatedFields related_name.
-+-
 Reporter:  renaud.parent@…  |Owner:  anonymous
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

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

Re: [Django] #22477: Remove contrib middleware from MIDDLEWARE_CLASSES global defaults

[Django]

#22477: Remove contrib middleware from MIDDLEWARE_CLASSES global defaults
-+-
 Reporter:  mlavin   |Owner:  mlavin
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Core (Other) |  1.7-beta-2
 Severity:  Release blocker  |   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:"d94de802d34c858805a01d3c699799aebc247ec3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d94de802d34c858805a01d3c699799aebc247ec3"
 [1.7.x] Fixed #22477 -- Removed contrib middleware from the global
 settings defaults.

 Also added a compatibility check for changed middleware defaults.
 }}}

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

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

[django/django] d94de8: [1.7.x] Fixed #22477 -- Removed contrib middleware...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: d94de802d34c858805a01d3c699799aebc247ec3
  
https://github.com/django/django/commit/d94de802d34c858805a01d3c699799aebc247ec3
  Author: mlavin 
  Date:   2014-06-13 (Fri, 13 Jun 2014)

  Changed paths:
M django/conf/global_settings.py
M django/contrib/auth/tests/test_context_processors.py
M django/core/checks/__init__.py
A django/core/checks/compatibility/django_1_7_0.py
M docs/ref/settings.txt
M docs/releases/1.7.txt
M tests/admin_scripts/tests.py
M tests/check_framework/tests.py
M tests/runtests.py

  Log Message:
  ---
  [1.7.x] Fixed #22477 -- Removed contrib middleware from the global settings 
defaults.

Also added a compatibility check for changed middleware defaults.


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

Re: [Django] #22829: URLValidator doesn't allow underscored in host part

[Django]

#22829: URLValidator doesn't allow underscored in host part
--+--
 Reporter:  anonymous |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Core (Other)  |  Version:  1.6
 Severity:  Normal|   Resolution:  duplicate
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by timo):

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


Comment:

 Duplicate of #20264

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

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

Re: [Django] #22829: URLValidator doesn't allow underscored in host part

[Django]

#22829: URLValidator doesn't allow underscored in host part
--+--
 Reporter:  anonymous |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by aaugustin):

 I'm pretty sure we did the opposite change in the past.

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

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

Re: [Django] #22829: URLValidator doesn't allow underscored in host part

[Django]

#22829: URLValidator doesn't allow underscored in host part
--+--
 Reporter:  anonymous |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by anonymous):

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


Comment:

 A bit of a clarification, it's not technically valid - rather it is used
 in the wild anyway. For example http://www.mattmorones_broker-
 beta.homesconnect.com

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

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

[Django] #22829: URLValidator doesn't allow underscored in host part

[Django]

#22829: URLValidator doesn't allow underscored in host part
--+
 Reporter:  anonymous |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Core (Other)  |Version:  1.6
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 URLValidator doesn't allow underscored in host part of URL which seems to
 be perfectly valid:

 http://stackoverflow.com/questions/2180465/can-someone-have-a-subdomain-
 hostname-with-an-underscore-in-it

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

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

Re: [Django] #15610: Generic Foreign Keys break when used with multi-db.

[Django]

#15610: Generic Foreign Keys break when used with multi-db.
--+
 Reporter:  legutierr |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.contenttypes  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by claudep):

 Thanks, but tests are still missing...

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

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

Re: [Django] #21584: prefetch_related child queryset does not update on create

[Django]

#21584: prefetch_related child queryset does not update on create
-+-
 Reporter:  lucaswiman   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by lukeplant):

 Sorry, that's just how the ORM works. Objects that represent collections
 do not keep track of their elements, because they represent querysets i.e.
 queries that may or may not yet have been evaluated, not actual
 collections of objects. If you have:

 {{{
 #!python
 my_objects = Foo.objects.all().filter(bar=1)
 list(my_objects) # evaluate query
 my_objects.update(bar=2)
 }}}

 then you will find that the 'update' has not affected anything in
 `my_objects` - either by changing the instances, or by removing them from
 the collection (since they no longer match the requirement `bar=1`).

 In the same way, `p.child_set` does not keep track of elements that are
 referred to. When you call `all()`, it executes a query every time,
 (rather than tracking creates/adds/deletes etc.). If you have used
 `prefetch_related`, however, it never executes a query when you just do
 `all()` because it has been prefetched. This is exactly what
 `prefetch_related` is supposed to do - the `all()` will not return data to
 reflect what is in the DB at that moment in time, but what was in the DB
 when the query was first evaluated.

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

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

Re: [Django] #7599: add get_user_permissions method to ModelBackend

[Django]

#7599: add get_user_permissions method to ModelBackend
--+--
 Reporter:  gwilson   |Owner:  jorgecarleitao
 Type:  New feature   |   Status:  closed
Component:  contrib.auth  |  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:"cc35bd461d35da2b03c0a1a8ff92123d716db9a9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cc35bd461d35da2b03c0a1a8ff92123d716db9a9"
 Fixed #7599 -- Added get_user_permissions to ModelBackend.

 Thanks to @gdub for the report and intial patch and
 @charettes and @timgraham 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/065.f54dd75019fba5bbd9f79e383d4d67a4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] cc35bd: Fixed #7599 -- Added get_user_permissions to Model...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: cc35bd461d35da2b03c0a1a8ff92123d716db9a9
  
https://github.com/django/django/commit/cc35bd461d35da2b03c0a1a8ff92123d716db9a9
  Author: Jorge C. Leitão 
  Date:   2014-06-13 (Fri, 13 Jun 2014)

  Changed paths:
M django/contrib/auth/backends.py
M docs/ref/contrib/auth.txt

  Log Message:
  ---
  Fixed #7599 -- Added get_user_permissions to ModelBackend.

Thanks to @gdub for the report and intial patch and
@charettes and @timgraham for the review.


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

Re: [Django] #6327: Add has_module_permission to ModelAdmin

[Django]

#6327: Add has_module_permission to ModelAdmin
---+
 Reporter:  chrj   |Owner:  maxocub
 Type:  New feature|   Status:  closed
Component:  contrib.admin  |  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:"504c89e8008c557a1e83c45535b549f77a3503b2"]:
 {{{
 #!CommitTicketReference repository=""
 revision="504c89e8008c557a1e83c45535b549f77a3503b2"
 Fixed #6327 -- Added has_module_permission method to BaseModelAdmin

 Thanks chrj for the suggestion.
 }}}

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

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

[django/django] 504c89: Fixed #6327 -- Added has_module_permission method ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 504c89e8008c557a1e83c45535b549f77a3503b2
  
https://github.com/django/django/commit/504c89e8008c557a1e83c45535b549f77a3503b2
  Author: Maxime Turcotte 
  Date:   2014-06-13 (Fri, 13 Jun 2014)

  Changed paths:
M django/contrib/admin/options.py
M django/contrib/admin/sites.py
M docs/ref/contrib/admin/index.txt
M docs/releases/1.8.txt
M tests/admin_ordering/tests.py
M tests/admin_views/admin.py
M tests/admin_views/tests.py
M tests/admin_views/urls.py
M tests/modeladmin/tests.py

  Log Message:
  ---
  Fixed #6327 -- Added has_module_permission method to BaseModelAdmin

Thanks chrj for the suggestion.


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

Re: [Django] #22817: Missing custom methods on EmptyQuerySet

[Django]

#22817: Missing custom methods on EmptyQuerySet
-+-
 Reporter:  benjaoming   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by benjaoming):

 Ah okay so this is the problem:

 {{{
 >>> from testapp import models
 >>> from django.db.models.manager import EmptyManager
 >>> emp=EmptyManager(models.MyModel)
 >>> emp.all()
 []
 >>> emp.custom_method()
 Traceback (most recent call last):
   File "", line 1, in 
 AttributeError: 'EmptyManager' object has no attribute 'custom_method'

 }}}

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

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

Re: [Django] #16087: Add ResolverMatch object to test client responses.

[Django]

#16087: Add ResolverMatch object to test client responses.
-+-
 Reporter:  mrmachine|Owner:  gchp
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  1.3
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  test client view | Triage Stage:  Accepted
  url resolve reverse|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"bf743a4d571bbb7da276bc21c61f6ada5d26942c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="bf743a4d571bbb7da276bc21c61f6ada5d26942c"
 Fixed #16087 -- Added ResolverMatch instance to test client response.

 Thanks mrmachine for the suggestion.
 }}}

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

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

[django/django] bf743a: Fixed #16087 -- Added ResolverMatch instance to te...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: bf743a4d571bbb7da276bc21c61f6ada5d26942c
  
https://github.com/django/django/commit/bf743a4d571bbb7da276bc21c61f6ada5d26942c
  Author: Greg Chapple 
  Date:   2014-06-13 (Fri, 13 Jun 2014)

  Changed paths:
M django/test/client.py
M docs/releases/1.8.txt
M docs/topics/testing/tools.txt
M tests/test_client/tests.py
M tests/test_client/urls.py

  Log Message:
  ---
  Fixed #16087 -- Added ResolverMatch instance to test client response.

Thanks mrmachine for the suggestion.


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

[Django] #22828: Model admins should return copies of its attributes

[Django]

#22828: Model admins should return copies of its attributes
---+
 Reporter:  vzima  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.admin  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I found out there is hidden problem in `ModelAdmin`s. Getters returns
 directly attributes and not their copies. This has a hidden danger in
 cases when you override the getters. You can easily change the
 configuration of the model admin.

 Example:
 {{{
 #!python
 from django.contrib.admin.options import BaseModelAdmin
 class MyAdmin(BaseModelAdmin):
 readonly_fields = ['foo', ]

 admin = MyAdmin()
 rf = admin.get_readonly_fields(None)
 # For example, but it can very easily happen in the method override.
 rf.append('bar')
 MyAdmin.readonly_fields #>>> ['foo', 'bar']
 }}}

 === Affected attributes ===
  * fieldsets
  * fileds
  * ordering
  * readonly_fields
  * prepopulated_fields
  * list_display
  * list_display_links
  * list_filter
  * search_fields


 Django should return copies in getters of these attributes to avoid
 unwanted changes of the `ModelAdmin` at runtime.

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

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

Re: [Django] #22817: Missing custom methods on EmptyQuerySet

[Django]

#22817: Missing custom methods on EmptyQuerySet
-+-
 Reporter:  benjaoming   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by benjaoming):

 I'm going to mark this as invalid very shortly because I cannot recreate
 the bug.

 Django 1.7 style Manager...

 {{{
 from django.db import models
 from django.db.models.query import QuerySet


 class MyQuerySet(QuerySet):
 def custom_method(self):
 return self.filter(my_field=True)


 class MyModel(models.Model):
 objects = MyQuerySet.as_manager()
 my_field = models.BooleanField(default=False)

 }}}

 Output:

 {{{
 >>> models.MyModel.objects.custom_method()
 []

 >>> models.MyModel.objects.none().custom_method()
 []
 }}}

 This part works.

 Also works with Django <=1.6 style managers:


 {{{
 from django.db import models
 from django.db.models.query import QuerySet


 class MyManager(models.Manager):
 def get_empty_query_set(self):
 return MyEmptyQuerySet(model=self.model)

 def get_query_set(self):
 return MyQuerySet(self.model, using=self._db)

 def custom_method(self):
 return self.filter(my_field=True)


 class MyQuerySet(QuerySet):
 def custom_method(self):
 return self.filter(my_field=True)


 class MyEmptyQuerySet(QuerySet):
 def custom_method(self):
 return self


 class MyModel(models.Model):
 objects = MyManager()
 my_field = models.BooleanField(default=False)

 }}}


 Running on Django 1.7, the above code works:

 {{{
 >> from testapp import models
 >>> models.MyModel.objects.none().custom_method()
 []
 >>> models.MyModel.objects.custom_method()
 []
 >>> models.MyModel.objects.all().none().custom_method()
 []
 }}}

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

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

Re: [Django] #22817: Missing custom methods on EmptyQuerySet

[Django]

#22817: Missing custom methods on EmptyQuerySet
-+-
 Reporter:  benjaoming   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * type:  Uncategorized => Bug
 * component:  Uncategorized => Database layer (models, ORM)
 * severity:  Normal => Release blocker
 * 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/068.d3c52e712402b41afe4602ccd0398b3a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #18229: Improving the AJAX Error text version to include the contextual code and variables

[Django]

#18229: Improving the AJAX Error text version to include the contextual code and
variables
+---
 Reporter:  davehughes05@…  |Owner:  anubhav9042
 Type:  New feature |   Status:  assigned
Component:  Core (Other)|  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+---

Comment (by timo):

 As a possible starting point, I've used
 [https://djangosnippets.org/snippets/650/ this middleware] before to make
 it easier to read AJAX exceptions.

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

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

Re: [Django] #22817: Missing custom methods on EmptyQuerySet

[Django]

#22817: Missing custom methods on EmptyQuerySet
---+--
 Reporter:  benjaoming |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by benjaoming):

 * severity:  Release blocker => Normal
 * stage:  Accepted => Unreviewed


Comment:

 Thanks. I will provide a running example, the AttributeError in the above
 is due to an embarrassing typo and not actually a missing method --
 however, the point remains the same.

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

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

Re: [Django] #22817: Missing custom methods on EmptyQuerySet

[Django]

#22817: Missing custom methods on EmptyQuerySet
-+
 Reporter:  benjaoming   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Uncategorized|  Version:  1.6
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by akaariai):

 * severity:  Normal => Release blocker
 * stage:  Unreviewed => Accepted


Comment:

 OK, the problem is that EmptyManager is subclass of Manager. Due to that,
 it doesn't have same methods as the real Manager. I'll set this as release
 blocker.

 One solution is to create dynamically a subclass of the real manager for
 EmptyManager. I don't like how much dynamic class creation we have now for
 querysets and managers, I have a feeling we will need to revisit this
 design again later on...

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

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

Re: [Django] #22827: Per-site cache docs vague about which middleware sets headers

[Django]

#22827: Per-site cache docs vague about which middleware sets headers
-+-
 Reporter:  Keryn Knight |Owner:  nobody
   |   Status:  new
 Type:   |  Version:  master
  Cleanup/optimization   |   Resolution:
Component:  Documentation| Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

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


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

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

Re: [Django] #22740: Model gets Meta from abstract ancestor class in MTI

[Django]

#22740: Model gets Meta from abstract ancestor class in MTI
-+-
 Reporter:  Kronuz   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 Your proposal would break code that relies on the currently documented
 behaviour: https://docs.djangoproject.com/en/dev/topics/db/models/#meta-
 inheritance

 We can have a discussion on the django-developers mailing-list about the
 advantages and drawbacks of inheriting Meta from abstract parents.

 But we can't accept such a backwards-incompatible change without
 discussion.

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

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

[Django] #22827: Per-site cache docs vague about which middleware sets headers

[Django]

#22827: Per-site cache docs vague about which middleware sets headers
-+
 Reporter:  Keryn Knight   |  Owner:  nobody
 Type:  Cleanup/optimization | Status:  new
Component:  Documentation|Version:  master
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 The [https://docs.djangoproject.com/en/dev/topics/cache/#the-per-site-
 cache docs] currently say:

 > Additionally, the cache middleware automatically sets a few headers in
 each HttpResponse:
 >
 > Sets the Last-Modified header to the current date/time when a fresh (not
 cached) version of the page is requested.
 > Sets the Expires header to the current date/time plus the defined
 CACHE_MIDDLEWARE_SECONDS.
 > Sets the Cache-Control header to give a max age for the page – again,
 from the CACHE_MIDDLEWARE_SECONDS setting.

 It's no longer clear ''which'' middleware does that, because these days
 what was once `CacheMiddleware` is now recommended as two separate
 components, `UpdateCacheMiddleware` and `FetchFromCacheMiddleware`. It is
 the
 
[https://github.com/django/django/blob/c083e3815aec23b99833da710eea574e6f2e8566/django/middleware/cache.py#L99
 UpdateCacheMiddleware] that is responsible for modifying the Response's
 headers.

 And, if being really picky:

 > The cache middleware caches GET and HEAD responses with status 200,
 where the request and response headers allow

 This is dictated by the
 
[https://github.com/django/django/blob/c083e3815aec23b99833da710eea574e6f2e8566/django/middleware/cache.py#L129
 FetchFromCacheMiddleware] at the beginning of the request

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

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

Re: [Django] #18229: Improving the AJAX Error text version to include the contextual code and variables (was: Allow configuration of debug response format for AJAX errors)

[Django]

#18229: Improving the AJAX Error text version to include the contextual code and
variables
+---
 Reporter:  davehughes05@…  |Owner:  anubhav9042
 Type:  New feature |   Status:  assigned
Component:  Core (Other)|  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+---
Changes (by anubhav9042):

 * status:  new => assigned
 * owner:  nobody => anubhav9042
 * version:  1.4 => 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/080.a8bb0a893c1e02a7a8064a68cabef8a8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22740: Model gets Meta from abstract ancestor class in MTI (was: Multi-table inheritance gets Meta from abstract ancestor model class)

[Django]

#22740: Model gets Meta from abstract ancestor class in MTI
-+-
 Reporter:  Kronuz   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by anubhav9042):

 * cc: anubhav9042@… (added)
 * component:  Uncategorized => Database layer (models, ORM)
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Comment:

 I am marking it as 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.2f256e3d316095f81177bf325dd96bf2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22740: Multi-table inheritance gets Meta from abstract ancestor model class

[Django]

#22740: Multi-table inheritance gets Meta from abstract ancestor model class
---+--
 Reporter:  Kronuz |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by anubhav9042):

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


Comment:

 I think that this a issue that must be corrected. To me even the fix seems
 good and simple enough. Though you may want to wait until you hear from a
 core-dev.

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

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

[Django] #22826: Simplify Query.setup_joins

[Django]

#22826: Simplify Query.setup_joins
--+
 Reporter:  jorgecarleitao|  Owner:  jorgecarleitao
 Type:  Cleanup/optimization  | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Currently, not all arguments returned by Query.setup_joins are being used
 all the times.

 On the other hand, some arguments are systematically being used in common
 things (e.g. join_list[-1])

 I propose to have a minor cleanup on these as part of an effort to
 simplify the entanglement between
 Query, SQLCompiler, and SQLEvalutor.

 This is a minor simplification and doesn't affect any public API.

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

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

Re: [Django] #7599: add get_user_permissions method to ModelBackend

[Django]

#7599: add get_user_permissions method to ModelBackend
--+--
 Reporter:  gwilson   |Owner:  jorgecarleitao
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  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 jorgecarleitao):

 * needs_better_patch:  1 => 0


Comment:

 See
 
https://github.com/jorgecarleitao/django/commit/ac217515b5290b6bab8a7a78d38bf309e063b3f6

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

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

Re: [Django] #17903: `ModelBackend.get_all_permissions` returns permissions for inactive users

[Django]

#17903: `ModelBackend.get_all_permissions` returns permissions for inactive 
users
--+--
 Reporter:  SmileyChris   |Owner:  jorgecarleitao
 Type:  Bug   |   Status:  assigned
Component:  contrib.auth  |  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 jorgecarleitao):

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