date:20131218

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

2013-12-18 Thread Django

#21142: Cannot run migrations that reference django.contrib.auth.models.User
-+
 Reporter:  mario.pfeifer@…  |Owner:
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  Migration, Auth  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by zxc.spam@…):

 * cc: zxc.spam@… (added)


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

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

Re: [Django] #21639: RenderContext should override getitem

2013-12-18 Thread Django

#21639: RenderContext should override __getitem__
-+--
 Reporter:  alexh|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+--
Changes (by alexh):

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


Comment:

 Patch at https://github.com/django/django/pull/2096

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

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

[Django] #21639: RenderContext should override getitem

2013-12-18 Thread Django

#21639: RenderContext should override __getitem__
-+
 Reporter:  alexh|  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Template system  |Version:  master
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  1
Easy pickings:  1|  UI/UX:  0
-+
 From the comments for RenderContext:


 > Name resolution fails if a variable is not found at the top of the
 RequestContext stack. Thus, variables are local to a specific template and
 don't affect the rendering of other templates as they would if they were
 stored in the normal template context.


 In RenderContext, the methods `__iter__`, `get`, and `has_key` are
 overridden. `has_key` is called internally by `BaseContext.__contains__`,
 so "in" works as expected, but `get` is not similarly called by
 `__getitem__`, so using `get` and using indexing syntax give different
 results. It seems to me that that's an oversight, and to be consistent
 with the intention as stated in the comment, `__getitem__` should be
 overridden too.

 Example of the wrong/inconsistent behaviour:

 {{{
 >>> from django.template.context import RenderContext
 >>> c = RenderContext({'fruit': 'banana'})
 >>> 'fruit' in c
 True
 >>> c.push()
 {}
 >>> 'fruit' in c
 False
 >>> c.get('fruit')
 >>> c['fruit']
 'banana'
 }}}

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

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

Re: [Django] #21638: Infinite migrations when using AUTH_USER_MODEL

2013-12-18 Thread Django

#21638: Infinite migrations when using AUTH_USER_MODEL
+--
 Reporter:  patrick@…   |Owner:
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:
 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 jess@…):

 * cc: jess@… (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


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

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

[Django] #21638: Infinite migrations when using AUTH_USER_MODEL

2013-12-18 Thread Django

#21638: Infinite migrations when using AUTH_USER_MODEL
+-
 Reporter:  patrick@…   |  Owner:
 Type:  Bug | Status:  new
Component:  Migrations  |Version:
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+-
 When using a custom class with AUTH_USER_MODEL, syncdb thinks that the
 "username" field in that class has changed. Every time you run
 {{{
 python manage.py makemigrations
 }}}
 it generates a new migration file, even though that model has no changes.
 If you run that migration, and call makemigrations again, it still thinks
 the field has changed and will make even more migration files.

 For example, my models.py:

 {{{
 from django.db import models
 from django.contrib.auth.models import AbstractUser
 # Create your models here.

 class Person(AbstractUser):
 favorite_color = models.CharField(max_length=64)

 }}}

 0001_initial.py created by "python manage.py makemigrations myapp"

 {{{
 # encoding: utf8
 from django.db import models, migrations
 import django.utils.timezone
 import django.core.validators


 class Migration(migrations.Migration):

 dependencies = []

 operations = [
 migrations.CreateModel(
 fields = [('id', models.AutoField(serialize=False,
 primary_key=True, verbose_name='ID', auto_created=True),), ('password',
 models.CharField(max_length=128, verbose_name='password'),),
 ('last_login', models.DateTimeField(default=django.utils.timezone.now,
 verbose_name='last login'),), ('is_superuser',
 models.BooleanField(default=False, verbose_name='superuser status',
 help_text='Designates that this user has all permissions without
 explicitly assigning them.'),), ('username',
 models.CharField(max_length=30, help_text='Required. 30 characters or
 fewer. Letters, digits and @/./+/-/_ only.', unique=True,
 verbose_name='username',
 validators=[django.core.validators.RegexValidator('^[\\w.@+-]+$', 'Enter a
 valid username.', 'invalid')]),), ('first_name',
 models.CharField(max_length=30, verbose_name='first name', blank=True),),
 ('last_name', models.CharField(max_length=30, verbose_name='last name',
 blank=True),), ('email', models.EmailField(max_length=75,
 verbose_name='email address', blank=True),), ('is_staff',
 models.BooleanField(default=False, verbose_name='staff status',
 help_text='Designates whether the user can log into this admin site.'),),
 ('is_active', models.BooleanField(default=True, verbose_name='active',
 help_text='Designates whether this user should be treated as active.
 Unselect this instead of deleting accounts.'),), ('date_joined',
 models.DateTimeField(default=django.utils.timezone.now, verbose_name='date
 joined'),), ('favorite_color', models.CharField(max_length=64),),
 ('groups', models.ManyToManyField(to='auth.Group', verbose_name='groups',
 blank=True),), ('user_permissions',
 models.ManyToManyField(to='auth.Permission', verbose_name='user
 permissions', blank=True),)],
 options = {'abstract': False, 'verbose_name': 'user',
 'verbose_name_plural': 'users'},
 bases = (models.Model,),
 name = 'Person',
 ),
 ]
 }}}
 I'm suspicious of the "bases = (models.Model,)" instead of
 "bases=(models.AbstractUser,)" but I don't know if that has any
 significance.


 And every time I run makemigrations after this, it creates a new migration
 like the following (the field order changes, but the content is always the
 same). If you run makemigrations ten times without changing your model,
 you get ten new scripts that all look like this:
 {{{
 # encoding: utf8
 from django.db import models, migrations
 import django.core.validators


 class Migration(migrations.Migration):

 dependencies = [('myapp', '0001_initial')]

 operations = [
 migrations.AlterField(
 name = 'username',
 model_name = 'person',
 field =
 
models.CharField(validators=[django.core.validators.RegexValidator('^[\\w.@+-]+$',
 'Enter a valid username.', 'invalid')], verbose_name='username',
 max_length=30, help_text='Required. 30 characters or fewer. Letters,
 digits and @/./+/-/_ only.', unique=True),
 ),
 ]
 }}}



 Discovered using Python 3.3.3, and Django 1.7 (alpha) commit
 23d9f517dc3ca31816bb8596f5a59f1ae44304ee

 Note: I double checked this occurred with a fresh database after reading
 the warning
 [https://docs.djangoproject.com/en/dev/topics/auth/customizing/#substituting-a
 -custom-user-model here], and confirmed that AUTH_USER_MODEL was set
 before any tables were made.

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

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

[django/django] 438f9e: [1.6.x] Fixed #21585 -- Updated some links to 3rd ...

2013-12-18 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 438f9edff6e53815c8223ec9e04740facad83a26
  
https://github.com/django/django/commit/438f9edff6e53815c8223ec9e04740facad83a26
  Author: Tim Graham 
  Date:   2013-12-18 (Wed, 18 Dec 2013)

  Changed paths:
M docs/ref/databases.txt
M docs/topics/install.txt

  Log Message:
  ---
  [1.6.x] Fixed #21585 -- Updated some links to 3rd party database projects.

Thanks graeme.perrow at sap.com for the original report.

Backport of 23d9f517dc 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/52b2350cc0f64_145a64dd541210d6%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21585: SQL Anywhere driver project has moved

2013-12-18 Thread Django

#21585: SQL Anywhere driver project has moved
--+
 Reporter:  graeme.perrow@…   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"23d9f517dc3ca31816bb8596f5a59f1ae44304ee"]:
 {{{
 #!CommitTicketReference repository=""
 revision="23d9f517dc3ca31816bb8596f5a59f1ae44304ee"
 Fixed #21585 -- Updated some links to 3rd party database projects.

 Thanks graeme.perrow at sap.com for the original report.
 }}}

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

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

[django/django] 23d9f5: Fixed #21585 -- Updated some links to 3rd party da...

2013-12-18 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 23d9f517dc3ca31816bb8596f5a59f1ae44304ee
  
https://github.com/django/django/commit/23d9f517dc3ca31816bb8596f5a59f1ae44304ee
  Author: Tim Graham 
  Date:   2013-12-18 (Wed, 18 Dec 2013)

  Changed paths:
M docs/ref/databases.txt
M docs/topics/install.txt

  Log Message:
  ---
  Fixed #21585 -- Updated some links to 3rd party database projects.

Thanks graeme.perrow at sap.com for the original report.


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

[django/django] cc2d96: Fixed #21613 -- Removed a hardcoded input id from ...

2013-12-18 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: cc2d9602746395d5f406632139378d469ca6301b
  
https://github.com/django/django/commit/cc2d9602746395d5f406632139378d469ca6301b
  Author: Tim Graham 
  Date:   2013-12-18 (Wed, 18 Dec 2013)

  Changed paths:
M docs/intro/tutorial04.txt

  Log Message:
  ---
  Fixed #21613 -- Removed a hardcoded input id from the tutorial.

Thanks Bruno Brouard for the report.


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

[django/django] 07d3d5: [1.6.x] Fixed #21613 -- Removed a hardcoded input ...

2013-12-18 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 07d3d57dedbc2baf8d704d32f3d48523d2991b9e
  
https://github.com/django/django/commit/07d3d57dedbc2baf8d704d32f3d48523d2991b9e
  Author: Tim Graham 
  Date:   2013-12-18 (Wed, 18 Dec 2013)

  Changed paths:
M docs/intro/tutorial04.txt

  Log Message:
  ---
  [1.6.x] Fixed #21613 -- Removed a hardcoded input id from the tutorial.

Thanks Bruno Brouard for the report.

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

[django/django] 698005: [1.5.x] Fixed #21613 -- Removed a hardcoded input ...

2013-12-18 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 6980059af2835ed3d15b4a59e16321bc8d828c0e
  
https://github.com/django/django/commit/6980059af2835ed3d15b4a59e16321bc8d828c0e
  Author: Tim Graham 
  Date:   2013-12-18 (Wed, 18 Dec 2013)

  Changed paths:
M docs/intro/tutorial04.txt

  Log Message:
  ---
  [1.5.x] Fixed #21613 -- Removed a hardcoded input id from the tutorial.

Thanks Bruno Brouard for the report.

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

Re: [Django] #21613: Misleading hardcoded input id in tutorial

2013-12-18 Thread Django

#21613: Misleading hardcoded input id in tutorial
-+-
 Reporter:  claudep  |Owner:
 Type:   |  AnneTheAgile
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"07d3d57dedbc2baf8d704d32f3d48523d2991b9e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="07d3d57dedbc2baf8d704d32f3d48523d2991b9e"
 [1.6.x] Fixed #21613 -- Removed a hardcoded input id from the tutorial.

 Thanks Bruno Brouard for the report.

 Backport of cc2d960274 from master
 }}}

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

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

Re: [Django] #21613: Misleading hardcoded input id in tutorial

2013-12-18 Thread Django

#21613: Misleading hardcoded input id in tutorial
-+-
 Reporter:  claudep  |Owner:
 Type:   |  AnneTheAgile
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"6980059af2835ed3d15b4a59e16321bc8d828c0e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6980059af2835ed3d15b4a59e16321bc8d828c0e"
 [1.5.x] Fixed #21613 -- Removed a hardcoded input id from the tutorial.

 Thanks Bruno Brouard for the report.

 Backport of cc2d960274 from master
 }}}

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

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

Re: [Django] #21613: Misleading hardcoded input id in tutorial

2013-12-18 Thread Django

#21613: Misleading hardcoded input id in tutorial
-+-
 Reporter:  claudep  |Owner:
 Type:   |  AnneTheAgile
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"cc2d9602746395d5f406632139378d469ca6301b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cc2d9602746395d5f406632139378d469ca6301b"
 Fixed #21613 -- Removed a hardcoded input id from the tutorial.

 Thanks Bruno Brouard for the report.
 }}}

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

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

[django/django] 4ac5de: Simplied some code in django.conf.init.

2013-12-18 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4ac5def4a27802fb16a8941195bc0d98b9e2e35c
  
https://github.com/django/django/commit/4ac5def4a27802fb16a8941195bc0d98b9e2e35c
  Author: Ondrej Sika 
  Date:   2013-12-18 (Wed, 18 Dec 2013)

  Changed paths:
M django/conf/__init__.py

  Log Message:
  ---
  Simplied some code in django.conf.__init__.


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

Re: [Django] #21478: Documentation of field.db_type() wrong

2013-12-18 Thread Django

#21478: Documentation of field.db_type() wrong
--+
 Reporter:  akaariai  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timo):

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


Comment:

 Don't forget to set the trac flags appropriate to put the ticket in the
 review queue. I've marked "Has patch" and also "Patch needs improvement"
 per my comments on the PR. Thanks!

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

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

Re: [Django] #21592: formset.ordered_forms should try to return ordered forms if is_valid() is false

2013-12-18 Thread Django

#21592: formset.ordered_forms should try to return ordered forms if is_valid() 
is
false
---+-
 Reporter:  nickname123|Owner:  pjrharley
 Type:  Uncategorized  |   Status:  assigned
Component:  Forms  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+-

Comment (by nickname123):

 I think the patch needs to do just a little more.  If the form isn't valid
 then cleaned_data will raise an exception won't it?  Unless that changed
 in more recent versions of django.  I'm stuck on an older version with the
 project I am currently working with.

 I got around this by falling back to using form.data.  See line 33 of the
 file I attached.  This still doesn't work for forms without data.  It
 makes sense to me for initial forms to have an ordering as well as it
 might be nice for ordered forms to return all forms that aren't deleted
 for easy rendering in templates.

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

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

Re: [Django] #21478: Documentation of field.db_type() wrong

2013-12-18 Thread Django

#21478: Documentation of field.db_type() wrong
--+
 Reporter:  akaariai  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by anubhav9042):

 Please see the pull request:
 https://github.com/django/django/pull/2094

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

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

Re: [Django] #21454: Ignoring certain fields on INSERT and UPDATE queries

2013-12-18 Thread Django

#21454: Ignoring certain fields on INSERT and UPDATE queries
-+-
 Reporter:  mpessas  |Owner:  mpessas
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  oracle   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by shai):

 * cc: shai (added)
 * keywords:   => oracle


Comment:

 @mpessas: With all things Oracle, you can always bug me. I only had time
 to glimpse at your patch now, but I will happily work with you to make
 sure that, by the time it is committed, Oracle is not broken.

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

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

Re: [Django] #21454: Ignoring certain fields on INSERT and UPDATE queries

2013-12-18 Thread Django

#21454: Ignoring certain fields on INSERT and UPDATE queries
-+-
 Reporter:  mpessas  |Owner:  mpessas
 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:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by manfre):

 * cc: mmanfre@… (added)


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

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

Re: [Django] #21635: "manage.py test" ignore --settings option

2013-12-18 Thread Django

#21635: "manage.py test" ignore --settings option
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.6
 Severity:  Normal |   Resolution:  needsinfo
 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 claudep):

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


Comment:

 I am not able to reproduce, maybe provide us a sample project?

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

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

Re: [Django] #21592: formset.ordered_forms should try to return ordered forms if is_valid() is false

2013-12-18 Thread Django

#21592: formset.ordered_forms should try to return ordered forms if is_valid() 
is
false
---+-
 Reporter:  nickname123|Owner:  pjrharley
 Type:  Uncategorized  |   Status:  assigned
Component:  Forms  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+-
Changes (by pjrharley):

 * status:  new => assigned
 * owner:  nobody => pjrharley
 * has_patch:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 PR here https://github.com/django/django/pull/2093

 I tried doing the same for deleted forms but it broke a whole load of
 other tests that were expecting an empty list. It would be really easy to
 just fix the tests but it makes me wonder if anyone is relying on that
 behaviour? I'd guess not, so if it is ok to change I'll submit that too.

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

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

Re: [Django] #21627: changepassword command fails with unicode characters

2013-12-18 Thread Django

#21627: changepassword command fails with unicode characters
-+
 Reporter:  jonklo   |Owner:  jonklo
 Type:  Bug  |   Status:  assigned
Component:  contrib.auth |  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 jonklo):

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


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

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

Re: [Django] #21454: Ignoring certain fields on INSERT and UPDATE queries

2013-12-18 Thread Django

#21454: Ignoring certain fields on INSERT and UPDATE queries
-+-
 Reporter:  mpessas  |Owner:  mpessas
 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:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by manfre):

 This ticket seems to only address fields that are '''ALWAYS''' updated by
 a trigger, but not fields that '''MAY''' be updated by a trigger (or
 something else working in/against the database), but doesn't necessarily
 require blocking changes on either insert or update.

 This scenario seems like it should be covered by this ticket too. If so,
 another field argument {{{always_refresh}}} could handle that. When
 {{{always_refresh=True}}}, it would instruct the ORM to fetch the field
 after an insert or update with either use of a {{{RETURNING}}} clause or a
 separate fetch. When {{{always_refresh=False}}}, it would have no action,
 unless {{{use_on_insert=False}}} or {{{use_on_update=False}}}.

 A third field argument feels excessive, especially since you'd need to
 define all three for the common case of a read-only field. The
 {{{use_on_insert}}} and {{{use_on_update}}} arguments could get merged in
 to an {{{edit_behavior}}} argument (probably needs a better name) that
 expects one of the following constant values:

 DEFAULT - {{{use_on_insert == True and use_on_update == True}}}
 CREATE_ONLY - {{{use_on_insert == True and use_on_update == False}}}
 UPDATE_ONLY - {{{use_on_insert == False and use_on_update == True}}}
 READ_ONLY - {{{use_on_insert == False and use_on_update == False}}}

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

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

Re: [Django] #21627: changepassword command fails with unicode characters

2013-12-18 Thread Django

Comment (by jonklo):

It looks like I encountered this error with a custom user model that
displayed the first and last name from the
{{{__unicode__}}} method on the custom User object. So this would not
occur with a vanilla Django User object, since it's {{{__str__}}} method
outputs the username, and the username is validated for ASCII only.

I still think this should be fixed though, since the changepassword
command can be utilized with custom User models and it worked in Django
1.5.

Looks like the change happened in commit
70a0de37d132e5f1514fb939875f69649f103124, where the username is no longer
explicitly used for the output to stdout.

Is it OK to use a Unicode character in the username for the regression
test?

I've committed the fix, a test case and a note in the 1.6.2 release notes,
let me know if there's anything else:
https://github.com/funkbit/django/tree/ticket_21627

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

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

Re: [Django] #21637: Defining objects of models having custom field without any parameter.

2013-12-18 Thread Django

#21637: Defining objects of models having custom field without any parameter.
-+-
 Reporter:  anubhav9042  |Owner:
 Type:  Bug  |  anubhav9042
Component:  Database layer   |   Status:  closed
  (models, ORM)  |  Version:  1.6
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 The `to_python` method must handle empty values (string/None) as
 documented here:
 https://docs.djangoproject.com/en/1.6/howto/custom-model-
 fields/#django.db.models.Field.to_python

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

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

Re: [Django] #21386: admindocs 'views' section depends on SITE_ID setting

2013-12-18 Thread Django

#21386: admindocs 'views' section depends on SITE_ID setting
--+
 Reporter:  ramiro|Owner:  bouke
 Type:  Cleanup/optimization  |   Status:  closed
Component:  contrib.admindocs |  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 claudep):

 * type:  Uncategorized => Cleanup/optimization


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

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

Re: [Django] #21386: admindocs 'views' section depends on SITE_ID setting

2013-12-18 Thread Django

#21386: admindocs 'views' section depends on SITE_ID setting
---+
 Reporter:  ramiro |Owner:  bouke
 Type:  Uncategorized  |   Status:  closed
Component:  contrib.admindocs  |  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 Claude Paroz ):

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


Comment:

 In [changeset:"a39d672ec7d53637805a61b45a51bc0e7d297a36"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a39d672ec7d53637805a61b45a51bc0e7d297a36"
 Fixed #21386 -- Removed admindocs dependence on sites framework

 * Removed ADMIN_FOR setting and warn warning
 * Group view functions by namespace instead of site
 * Added a test verifying namespaces are listed

 Thanks to Claude Paroz for reviewing and ideas for improvement.
 }}}

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

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

[django/django] a39d67: Fixed #21386 -- Removed admindocs dependence on si...

2013-12-18 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a39d672ec7d53637805a61b45a51bc0e7d297a36
  
https://github.com/django/django/commit/a39d672ec7d53637805a61b45a51bc0e7d297a36
  Author: Bouke Haarsma 
  Date:   2013-12-18 (Wed, 18 Dec 2013)

  Changed paths:
M django/contrib/admindocs/templates/admin_doc/template_detail.html
M django/contrib/admindocs/templates/admin_doc/view_index.html
M django/contrib/admindocs/views.py
M docs/ref/contrib/admin/admindocs.txt
M docs/ref/settings.txt
M docs/releases/1.7.txt
M tests/admin_docs/tests.py
M tests/admin_docs/urls.py

  Log Message:
  ---
  Fixed #21386 -- Removed admindocs dependence on sites framework

* Removed ADMIN_FOR setting and warn warning
* Group view functions by namespace instead of site
* Added a test verifying namespaces are listed

Thanks to Claude Paroz for reviewing and ideas for improvement.


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

Re: [Django] #21454: Ignoring certain fields on INSERT and UPDATE queries

2013-12-18 Thread Django

#21454: Ignoring certain fields on INSERT and UPDATE queries
-+-
 Reporter:  mpessas  |Owner:  mpessas
 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:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by manfre):

 Replying to [comment:4 mpessas]:
 >
 > Check commit
 
https://github.com/mpessas/django/commit/dac93937c66040cb901e5e48bd6deba5ce51de9e.
 If the backend supports the RETURNING clause, we use that to fetch the
 values the database has given to the db-default fields. Otherwise, an
 extra SELECT query is issued. If the user does not want this overhead, he
 can set `force_fetch=False` (which is the default).
 >
 > There are two main issues here: I have not checked yet how this works,
 when Model inheritance is used and the Oracle backend is broken.
 >
 > Regarding the latter, I have not found any helpful docs about the
 RETURNING clause and I cannot test it either. Is there someone I could ask
 or should I contact the cx_oracle developers directly?
 .

 It's possible that a database backend is capable of returning the IDs from
 an insert without supporting the {{{RETURNING}}} clause. Those should be
 separate features. I previously injected a select statement to return the
 inserted ID without needing a second round trip to the MSSQL server. It's
 also possible that certain database drivers may return newly inserted IDs
 without SQL.

 MSSQL supports the {{{OUTPUT}}} clause, which is similar to
 {{{RETURNING}}}, but not exactly the same. Once I add Django 1.7 support
 to django-mssql, I'll test out your branch. The primary database I develop
 django-mssql against is a heavy user of readonly fields (computed fields,
 populated with triggers/SSIS, etc). We've made due with a Manager that
 lets me define the readonly fields and having to manually refresh the
 instance after certain inserts.

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

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

Re: [Django] #21637: Defining objects of models having custom field without any parameter.

2013-12-18 Thread Django

#21637: Defining objects of models having custom field without any parameter.
-+-
 Reporter:  anubhav9042  |Owner:
 Type:  Bug  |  anubhav9042
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by anubhav9042):

 C:\Python27\lib\site-packages\django\db\models\base.pyc in __init__(self,
 *args, **kwargs)
 403 setattr(self, field.name, rel_obj)
 404 else:
 --> 405 setattr(self, field.attname, val)
 406
 407 if kwargs:

 C:\Python27\lib\site-packages\django\db\models\fields\subclassing.py in
 __set__
 self, obj, value)
  33
  34 def __set__(self, obj, value):
 ---> 35 obj.__dict__[self.field.name] =
 self.field.to_python(value)
  36
  37 def make_contrib(superclass, func=None):

 C:\anubhav_imp\django_projects\dev\test1\models.pyc in to_python(self,
 value)
   6 return 'longtext'
   7 def to_python(self, value):
 > 8 return long(value)
   9
  10 class Person(models.Model):

 ValueError: invalid literal for long() with base 10: ''

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

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

Re: [Django] #21637: Defining objects of models having custom field without any parameter.

2013-12-18 Thread Django

#21637: Defining objects of models having custom field without any parameter.
-+-
 Reporter:  anubhav9042  |Owner:
 Type:  Bug  |  anubhav9042
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Description changed by timo:

Old description:

> When we define any model, then we can create its object as
> obj=ModelClassName(). But when we define custom fields we just cannot do
> the same always. If we are using to_python() method, then it shows up
> error.
>

> If a define my model as:
>
> from django.db import models
>
> class LField(models.Field):
> __metaclass__ = models.SubfieldBase
> def db_type(self, connection):
> return 'longtext'
> def to_python(self, value):
> return long(value)
>
> class Person(models.Model):
> name = models.CharField(max_length=80, blank=True, null=True)
> something_else = LField()
> class Person2(models.Model):
> name = models.CharField(max_length=80, blank=True, null=True)
> ph = models.CharField(max_length=80, blank=True, null=True)
>

> Then it is not possible to define an object of Person type without giving
> parameters.
> i.e.
> p=Person() raises ValueError
> p=Person2() works fine as it should like in case of any other class.

New description:

 When we define any model, then we can create its object as
 obj=ModelClassName(). But when we define custom fields we just cannot do
 the same always. If we are using to_python() method, then it shows up
 error.

 If a define my model as:
 {{{
 from django.db import models

 class LField(models.Field):
 __metaclass__ = models.SubfieldBase
 def db_type(self, connection):
 return 'longtext'
 def to_python(self, value):
 return long(value)

 class Person(models.Model):
 name = models.CharField(max_length=80, blank=True, null=True)
 something_else = LField()
 class Person2(models.Model):
 name = models.CharField(max_length=80, blank=True, null=True)
 ph = models.CharField(max_length=80, blank=True, null=True)
 }}}

 Then it is not possible to define an object of Person type without giving
 parameters.
 i.e.
 p=Person() raises ValueError
 p=Person2() works fine as it should like in case of any other class.

--

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

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

Re: [Django] #21637: Defining objects of models having custom field without any parameter.

2013-12-18 Thread Django

#21637: Defining objects of models having custom field without any parameter.
-+-
 Reporter:  anubhav9042  |Owner:
 Type:  Bug  |  anubhav9042
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by anubhav9042):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * owner:  nobody => anubhav9042
 * 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/069.0f8c04ef1da47f8e31b9129e031abc50%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21637: Defining objects of models having custom field without any parameter.

2013-12-18 Thread Django

#21637: Defining objects of models having custom field without any parameter.
--+
 Reporter:  anubhav9042   |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.6
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 When we define any model, then we can create its object as
 obj=ModelClassName(). But when we define custom fields we just cannot do
 the same always. If we are using to_python() method, then it shows up
 error.


 If a define my model as:

 from django.db import models

 class LField(models.Field):
 __metaclass__ = models.SubfieldBase
 def db_type(self, connection):
 return 'longtext'
 def to_python(self, value):
 return long(value)

 class Person(models.Model):
 name = models.CharField(max_length=80, blank=True, null=True)
 something_else = LField()
 class Person2(models.Model):
 name = models.CharField(max_length=80, blank=True, null=True)
 ph = models.CharField(max_length=80, blank=True, null=True)


 Then it is not possible to define an object of Person type without giving
 parameters.
 i.e.
 p=Person() raises ValueError
 p=Person2() works fine as it should like in case of any other class.

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

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

Re: [Django] #21628: Stop using the `imp` module

2013-12-18 Thread Django

#21628: Stop using the `imp` module
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by merb):

 * cc: merb (added)


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

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

Re: [Django] #11629: Deprecate callable QuerySet filter arguments

2013-12-18 Thread Django

#11629: Deprecate callable QuerySet filter arguments
-+-
 Reporter:  harrym   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:  fixed
  (models, ORM)  | Triage Stage:  Ready for
 Severity:  Normal   |  checkin
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Baptiste Mispelon ):

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


Comment:

 In [changeset:"f1b3ab9c2158f5a7da113aef4158499ce2d42ee2"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f1b3ab9c2158f5a7da113aef4158499ce2d42ee2"
 Fixed #11629 -- Deprecated callable arguments to queryset methods.

 Callable arguments were an untested and undocumented feature.
 }}}

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

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

[django/django] f1b3ab: Fixed #11629 -- Deprecated callable arguments to q...

2013-12-18 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: f1b3ab9c2158f5a7da113aef4158499ce2d42ee2
  
https://github.com/django/django/commit/f1b3ab9c2158f5a7da113aef4158499ce2d42ee2
  Author: Baptiste Mispelon 
  Date:   2013-12-18 (Wed, 18 Dec 2013)

  Changed paths:
M django/db/models/sql/query.py
M docs/internals/deprecation.txt
M docs/releases/1.7.txt
M tests/queries/tests.py

  Log Message:
  ---
  Fixed #11629 -- Deprecated callable arguments to queryset methods.

Callable arguments were an untested and undocumented feature.


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

Re: [Django] #21597: (2006, 'MySQL server has gone away') in django1.6 when wait_timeout passed

2013-12-18 Thread Django

Comment (by aigarius):

Could this actually be a failure to re-establish a connection to MySQL
after receiving the 2006 error? I get the same symptoms in production now
when a MySQL server is restarted - all workers start getting 2006 errors
and do not recover. Only gunicorn restart helps then. You could reproduce
it locally by calling "print
list(django.contrib.auth.models.User.objects.all())" every second and then
restarting MySQL server. The connection does not recover even after the
server is back up and accepting connections. This was tested with
CONN_MAX_AGE > 0 but lower than wait_timeout on the MySQL server.

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

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

Re: [Django] #21632: Docs: Unsupported example with a callable as a query parameter

2013-12-18 Thread Django

#21632: Docs: Unsupported example with a callable as a query parameter
---+
 Reporter:  marfire|Owner:  marfire
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by timo):

 For the record, bmispelon and I chatted about his comment above. He said
 he may have read the patch too quickly and missed that the note does
 mention ModelForm.

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

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

[django/django] 683377: [1.5.x] Fixed #21632 -- Docs: Removed example with...

2013-12-18 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 6833773775fe135c38768418d31ec3f789d8f06f
  
https://github.com/django/django/commit/6833773775fe135c38768418d31ec3f789d8f06f
  Author: Kevin Christopher Henry 
  Date:   2013-12-18 (Wed, 18 Dec 2013)

  Changed paths:
M docs/ref/models/fields.txt

  Log Message:
  ---
  [1.5.x] Fixed #21632 -- Docs: Removed example with callable as query parameter

Using callables as query parameters is undocumented and not working,
so this changes an example from the ForeignKey.limit_choices_to
documentation that uses it.

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

[django/django] dd7e29: [1.6.x] Fixed #21632 -- Docs: Removed example with...

2013-12-18 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: dd7e2925dd63700a70f04a1e4c0df837acbdd55c
  
https://github.com/django/django/commit/dd7e2925dd63700a70f04a1e4c0df837acbdd55c
  Author: Kevin Christopher Henry 
  Date:   2013-12-18 (Wed, 18 Dec 2013)

  Changed paths:
M docs/ref/models/fields.txt

  Log Message:
  ---
  [1.6.x] Fixed #21632 -- Docs: Removed example with callable as query parameter

Using callables as query parameters is undocumented and not working,
so this changes an example from the ForeignKey.limit_choices_to
documentation that uses it.

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

[django/django] d34c8c: Fixed #21632 -- Docs: Removed example with callabl...

2013-12-18 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d34c8c338a843df2a540f19d15efc1ff12e3119c
  
https://github.com/django/django/commit/d34c8c338a843df2a540f19d15efc1ff12e3119c
  Author: Kevin Christopher Henry 
  Date:   2013-12-18 (Wed, 18 Dec 2013)

  Changed paths:
M docs/ref/models/fields.txt

  Log Message:
  ---
  Fixed #21632 -- Docs: Removed example with callable as query parameter

Using callables as query parameters is undocumented and not working,
so this changes an example from the ForeignKey.limit_choices_to
documentation that uses it.


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

Re: [Django] #21632: Docs: Unsupported example with a callable as a query parameter

2013-12-18 Thread Django

#21632: Docs: Unsupported example with a callable as a query parameter
---+
 Reporter:  marfire|Owner:  marfire
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Tim Graham ):

 In [changeset:"6833773775fe135c38768418d31ec3f789d8f06f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6833773775fe135c38768418d31ec3f789d8f06f"
 [1.5.x] Fixed #21632 -- Docs: Removed example with callable as query
 parameter

 Using callables as query parameters is undocumented and not working,
 so this changes an example from the ForeignKey.limit_choices_to
 documentation that uses it.

 Backport of d34c8c338a from master
 }}}

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

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

Re: [Django] #21632: Docs: Unsupported example with a callable as a query parameter

2013-12-18 Thread Django

#21632: Docs: Unsupported example with a callable as a query parameter
---+
 Reporter:  marfire|Owner:  marfire
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Tim Graham ):

 In [changeset:"dd7e2925dd63700a70f04a1e4c0df837acbdd55c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="dd7e2925dd63700a70f04a1e4c0df837acbdd55c"
 [1.6.x] Fixed #21632 -- Docs: Removed example with callable as query
 parameter

 Using callables as query parameters is undocumented and not working,
 so this changes an example from the ForeignKey.limit_choices_to
 documentation that uses it.

 Backport of d34c8c338a from master
 }}}

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

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

Re: [Django] #21632: Docs: Unsupported example with a callable as a query parameter

2013-12-18 Thread Django

#21632: Docs: Unsupported example with a callable as a query parameter
---+
 Reporter:  marfire|Owner:  marfire
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"d34c8c338a843df2a540f19d15efc1ff12e3119c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d34c8c338a843df2a540f19d15efc1ff12e3119c"
 Fixed #21632 -- Docs: Removed example with callable as query parameter

 Using callables as query parameters is undocumented and not working,
 so this changes an example from the ForeignKey.limit_choices_to
 documentation that uses 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/065.ed76f8ab0cfeea38db8346b142da1b04%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20241: QuerySets with callable filter args have said args evaluated only once

2013-12-18 Thread Django

#20241: QuerySets with callable filter args have said args evaluated only once
-+-
 Reporter:   |Owner:  nobody
  christopher.m.pike@…   |   Status:  closed
 Type:  Bug  |  Version:  1.5
Component:  Database layer   |   Resolution:  duplicate
  (models, ORM)  | 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):

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


Comment:

 We're going to deprecate callable queryset filter arguments -- see #11629.

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

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

Re: [Django] #21454: Ignoring certain fields on INSERT and UPDATE queries

2013-12-18 Thread Django

#21454: Ignoring certain fields on INSERT and UPDATE queries
-+-
 Reporter:  mpessas  |Owner:  mpessas
 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:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by mpessas):

 Replying to [comment:3 mpessas]:
 > Replying to [comment:2 akaariai]:
 > > It would be really useful to do autorefresh after save. Access to
 database set values could also be done with RETURNING, but for first
 implementation just executing a query from .save() would be enough.
 >
 > I would rather avoid the extra query to re-read the db-default values;
 it would have a significant impact on performance, when one of the goals
 was to improve performance in the first place.
 >
 > Regarding the `RETURNING` clause, it is not part of the SQL standard
 AFAIK (see http://www.postgresql.org/docs/9.1/static/sql-
 update.html#AEN76402) and that's the reason I avoided it. That said, can
 we have backend-specific codepaths in Django? That is, use the `RETURNING`
 clause, when available, and fallback to a re-read query otherwise.
 >
 > In any case, I suppose we should allow the developer to skip the re-read
 query, if using the `RETURNING` clause is not possible. How does that
 sound?
 >

 Check commit
 
https://github.com/mpessas/django/commit/dac93937c66040cb901e5e48bd6deba5ce51de9e.
 If the backend supports the RETURNING clause, we use that to fetch the
 values the database has given to the db-default fields. Otherwise, an
 extra SELECT query is issued. If the user does not want this overhead, he
 can set `force_fetch=False` (which is the default).

 There are two main issues here: I have not checked yet how this works,
 when Model inheritance is used and the Oracle backend is broken.

 Regarding the latter, I have not found any helpful docs about the
 RETURNING clause and I cannot test it either. Is there someone I could ask
 or should I contact the cx_oracle developers directly?

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

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

Re: [Django] #11629: Deprecate callable QuerySet filter arguments (was: Callable QuerySet filter arguments not mentioned in documentation)

2013-12-18 Thread Django

#11629: Deprecate callable QuerySet filter arguments
-+-
 Reporter:  harrym   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Ready for
 Severity:  Normal   |  checkin
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * stage:  Accepted => Ready for checkin
 * component:  Documentation => Database layer (models, ORM)


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

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

Re: [Django] #11629: Callable QuerySet filter arguments not mentioned in documentation

2013-12-18 Thread Django

#11629: Callable QuerySet filter arguments not mentioned in documentation
--+
Reporter: harrym|Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: master
Severity: Normal| Resolution:
Keywords:| Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 |UI/UX: 0
--+
Changes (by bmispelon):

* has_patch: 0 => 1

Comment:

On top of being undocumented, that feature is also untested (full test
suite still passed after removing the two lines that call the value if
it's callable).

Plus, as mentionned on #20241, this feature is going to be tricky to
implement in a useful way.

Consequently, I propose to remove the feature altogether (going through
the usual deprecation path).

Here's a PR with docs and some tests:
https://github.com/django/django/pull/2091

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

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

Re: [Django] #21636: distinct_on_fields tests require DatabaseFeature.ignores_nulls_in_unique_constraints

2013-12-18 Thread Django

#21636: distinct_on_fields tests require
DatabaseFeature.ignores_nulls_in_unique_constraints
---+--
 Reporter:  manfre |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.6
 Severity:  Normal |   Resolution:  wontfix
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by manfre):

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


Comment:

 PR was accidentally made against 1.6.x. This is likely a non-issue with
 master because the '''can_distinct_on_fields''' check was bumped up to the
 class, instead of on each of the tests. None of the known database
 backends support '''can_distinct_on_fields''', but not
 '''ignores_nulls_in_unique_constraints''' in such a way that causes an
 error during setUp.

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

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

Re: [Django] #21636: distinct_on_fields tests require DatabaseFeature.ignores_nulls_in_unique_constraints

2013-12-18 Thread Django

#21636: distinct_on_fields tests require
DatabaseFeature.ignores_nulls_in_unique_constraints
---+--
 Reporter:  manfre |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by anonymous):

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


Comment:

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

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

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

[Django] #21636: distinct_on_fields tests require DatabaseFeature.ignores_nulls_in_unique_constraints

2013-12-18 Thread Django

#21636: distinct_on_fields tests require
DatabaseFeature.ignores_nulls_in_unique_constraints
---+
 Reporter:  manfre |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Testing framework  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  1  |  UI/UX:  0
---+
 {{{DistinctOnTests.setUp()}}} requires
 '''DatabaseFeature.ignores_nulls_in_unique_constraints'''.

 Django-mssql would skip all of theses tests due to
 {{{can_distinct_on_fields = False}}}, but it throws a database exception
 during setUp when it tries to insert multiple NULLs for the
 '''greatest_fan''', nullable, unique field.

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

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

Re: [Django] #21206: Misleading Exception on empty test class: ImportError: Start directory is not importable (was: Misleading Exception on emty test class: ImportError: Start directory is not importa

2013-12-18 Thread Django

#21206: Misleading Exception on empty test class: ImportError: Start directory 
is
not importable
---+--
 Reporter:  thepapermen|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.6-beta-1
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by prestontimmons):

 * needs_better_patch:  1 => 0


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

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

Re: [Django] #21552: Cannot use None as a query value for iexact lookup

2013-12-18 Thread Django

#21552: Cannot use None as a query value for iexact lookup
-+-
 Reporter:  denya|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"d4e578d0f64971483ded49f9cae460ea174b5138"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d4e578d0f64971483ded49f9cae460ea174b5138"
 Fixed #21552 -- Allowed the use of None for the iexact lookup.

 Thanks Anubhav Joshi for the documentation.
 }}}

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

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

[django/django] d4e578: Fixed #21552 -- Allowed the use of None for the ie...

2013-12-18 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d4e578d0f64971483ded49f9cae460ea174b5138
  
https://github.com/django/django/commit/d4e578d0f64971483ded49f9cae460ea174b5138
  Author: Denis Moskalets 
  Date:   2013-12-18 (Wed, 18 Dec 2013)

  Changed paths:
M django/db/models/sql/query.py
M docs/ref/models/querysets.txt
M docs/releases/1.7.txt
M tests/null_queries/tests.py

  Log Message:
  ---
  Fixed #21552 -- Allowed the use of None for the iexact lookup.

Thanks Anubhav Joshi for the documentation.


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

[django/django] 2fd7fc: Refs #17413 -- Added isinstance backward compatibi...

2013-12-18 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2fd7fc134cf0c0685ceac22fd858509aa43f819f
  
https://github.com/django/django/commit/2fd7fc134cf0c0685ceac22fd858509aa43f819f
  Author: Loic Bistuer 
  Date:   2013-12-18 (Wed, 18 Dec 2013)

  Changed paths:
M django/forms/utils.py
M tests/forms_tests/tests/test_forms.py

  Log Message:
  ---
  Refs #17413 -- Added isinstance backward compatibility on ErrorList.


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

Re: [Django] #17413: Serialization or getting non-HTML version of form errors is not easy

2013-12-18 Thread Django

#17413: Serialization or getting non-HTML version of form errors is not easy
-+-
 Reporter:  kmike|Owner:  loic84
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  form errors  | Triage Stage:  Ready for
  serialization  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"2fd7fc134cf0c0685ceac22fd858509aa43f819f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2fd7fc134cf0c0685ceac22fd858509aa43f819f"
 Refs #17413 -- Added isinstance backward compatibility on ErrorList.
 }}}

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

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

Re: [Django] #21625: DiscoverRunner.build_suite docs are incorrect

2013-12-18 Thread Django

#21625: DiscoverRunner.build_suite docs are incorrect
---+
 Reporter:  bradleyayers   |Owner:  tianyi
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.6
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  1  |UI/UX:  0
---+

Comment (by Baptiste Mispelon ):

 In [changeset:"60517c9c09daffee678fd4337687185ce38ed35b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="60517c9c09daffee678fd4337687185ce38ed35b"
 [1.6.x] Fixed #21625 -- incorrect documentation for
 DiscoverRunner.build_suite

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

[django/django] 60517c: [1.6.x] Fixed #21625 -- incorrect documentation fo...

2013-12-18 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 60517c9c09daffee678fd4337687185ce38ed35b
  
https://github.com/django/django/commit/60517c9c09daffee678fd4337687185ce38ed35b
  Author: Tianyi Wang 
  Date:   2013-12-18 (Wed, 18 Dec 2013)

  Changed paths:
M docs/topics/testing/advanced.txt

  Log Message:
  ---
  [1.6.x] Fixed #21625 -- incorrect documentation for DiscoverRunner.build_suite

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

Re: [Django] #21630: Simplify find_management_module

2013-12-18 Thread Django

#21630: Simplify find_management_module
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Core (Management |   Resolution:
  commands)  | 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|
-+-

Comment (by mjtamlyn):

 I think we've had the new layout long enough - other things which tried to
 do clever stuff around this have been removed from what I remember. +1 to
 removing this.

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

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

Re: [Django] #21625: DiscoverRunner.build_suite docs are incorrect

2013-12-18 Thread Django

#21625: DiscoverRunner.build_suite docs are incorrect
---+
 Reporter:  bradleyayers   |Owner:  tianyi
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.6
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  1  |UI/UX:  0
---+
Changes (by Baptiste Mispelon ):

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


Comment:

 In [changeset:"b62031441b2e1cb1eeb7e1d6f254c553643add96"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b62031441b2e1cb1eeb7e1d6f254c553643add96"
 Fixed #21625 -- incorrect documentation for DiscoverRunner.build_suite
 }}}

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

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

[django/django] b62031: Fixed #21625 -- incorrect documentation for Discov...

2013-12-18 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b62031441b2e1cb1eeb7e1d6f254c553643add96
  
https://github.com/django/django/commit/b62031441b2e1cb1eeb7e1d6f254c553643add96
  Author: Tianyi Wang 
  Date:   2013-12-18 (Wed, 18 Dec 2013)

  Changed paths:
M docs/topics/testing/advanced.txt

  Log Message:
  ---
  Fixed #21625 -- incorrect documentation for DiscoverRunner.build_suite


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

Re: [Django] #21630: Simplify find_management_module

2013-12-18 Thread Django

#21630: Simplify find_management_module
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Core (Management |   Resolution:
  commands)  | 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|
-+-

Comment (by ramiro):

 Thought the same when trying to work on #15084 and reviewing that code.

 But, shouldn't that code remain as is to stay compatible with existing
 project that use old the layout? Or this isn't a supported scenario?

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

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

Re: [Django] #11629: Callable QuerySet filter arguments not mentioned in documentation

2013-12-18 Thread Django

#11629: Callable QuerySet filter arguments not mentioned in documentation
--+
 Reporter:  harrym|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  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 bmispelon):

 Another ticket linked with this issue: #21632.

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

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

Re: [Django] #21632: Docs: Unsupported example with a callable as a query parameter

2013-12-18 Thread Django

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

Comment:

Hi,

From my limited testing, using callable values in `limit_choices_to` is
only half-broken:

* It works when doing model validation (the callable is evaluated every
time you call `model.full_clean()`)
* Ir works in the admin if you let the admin generate a modelform for you
(the callable is evaluated for every request).
* It's broken for modelforms (the callable is evaluated only when the
`ModelForm` is declared, not when instanciated).

Consequently, I think it makes sense to remove it from the documentation,
at least while we sort out #11629 and #20241.

However, your patch makes it seem like `limit_choices_to` is only useful
in the admin but that's not the case: it's a property that affects the
generation of `ModelForms` (both its rendering and its validation) and
it's also used when doing model validation.

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

Re: [Django] #21628: Stop using the `imp` module

2013-12-18 Thread Django

#21628: Stop using the `imp` module
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by merb):

 @aaugustin i think we could just ignore this issue.

 Currently I tried:
 https://code.djangoproject.com/attachment/ticket/18251/threading_lock.tar.gz
 On Python 2.7.5+ and on Python 3.3.2+ the issue never occured. Without
 calling {{{imp.acquire_lock()}}} or {{{imp.release_lock()}}}

 Maybe the "test" itself is somehow not correct anymore.

 But I think its due to the fact that we now (since the last commit
 https://github.com/django/django/compare/fe1389e911b0...4a56a93cc458) use
 https://pypi.python.org/pypi/importlib a backport of importlib for python
 2.7 due to the fact that the next django version won't be compatible to
 python 2.6. So just remove imp and we are fine.

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

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

Re: [Django] #16380: admin_list_filter should pass the spec to the template

2013-12-18 Thread Django

#16380: admin_list_filter should pass the spec to the template
---+
 Reporter:  hvdklauw   |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by bruno@…):

 @bmispelon: ok will do next time.

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

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

Re: [Django] #16380: admin_list_filter should pass the spec to the template

2013-12-18 Thread Django

#16380: admin_list_filter should pass the spec to the template
---+
 Reporter:  hvdklauw   |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by bmispelon):

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


Comment:

 Hi,

 Thanks for digging up these old out-of-date tickets
 FYI, you don't need special permmissions to close a ticket here and you
 can do so yourself.

 Putting the commit id in the comment when you close a ticket will help us
 double check.

 In this case, this issue appears to have been fixed in
 4dbeb4bca4638ff851a2f4844d262dbe1652f7b5.

 Thanks.

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

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

[Django] #21635: "manage.py test" ignore --settings option

2013-12-18 Thread Django

#21635: "manage.py test" ignore --settings option
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I just bumped into this:
 http://stackoverflow.com/questions/7529666/django-test-runner-ignoring-
 the-settings-option

 Note that "./manage.py runserver --settings=foo" works fine.
 When it comes to "./manage.py test --settings=foo" the "foo" module is not
 even imported.

 I'm using Django 1.6.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/052.6deeebe24cefe2fa389ea9dbc737ea23%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16380: admin_list_filter should pass the spec to the template

2013-12-18 Thread Django

#16380: admin_list_filter should pass the spec to the template
---+
 Reporter:  hvdklauw   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by bruno@…):

 * cc: bruno@… (added)


Comment:

 This ticket could be closed, `admin_list_filter` is now (in v1.6 at least)
 a `simple_tag` that uses the spec's template AND pass the spec to the
 template (cf
 
https://github.com/django/django/blob/master/django/contrib/admin/templatetags/admin_list.py
 line 409).

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

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

Re: [Django] #21634: Lis of installed apps set to empty when ImproperlyConfigured exception is raised

2013-12-18 Thread Django

* stage: Unreviewed => Accepted

Comment:

As you can read in the comment, the purpose is to allow to run some
commands even when settings are not yet properly configured. It's obvious
that when you run `django-admin.py startproject`, no suitable settings
will be available.

In [a098bee1b9fa4df] (#19724), we already improved the message for the
`help` command in the case `ImproperlyConfigured` exception is raised. So
I suggest to extend a similar handling for all commands.

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

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

Re: [Django] #6159: Reusable templatetags for admin list

2013-12-18 Thread Django

#6159: Reusable templatetags for admin list
-+-
 Reporter:  Petr Marhoun |Owner:  nobody
     |   Status:  closed
 Type:  New feature  |  Version:  newforms-
Component:  contrib.admin|  admin
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  nfa-someday  | Triage Stage:
Has patch:  1|  Someday/Maybe
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by claudep):

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

Re: [Django] #21628: Stop using the `imp` module

2013-12-18 Thread Django

Comment (by loic84):

As @aaugustin pointed in a github comment, these functions used to be
implemented as normal reentrant threads and that caused deadlocks
(#18251).

It seems the behavior of those functions changed in 3.3 as well, dunno if
the change affected us:

"Changed in version 3.3: The locking scheme has changed to per-module
locks for the most part. A global import lock is kept for some critical
tasks, such as initializing the per-module locks."

FWIW the python bug where the deprecation was discussed:
http://bugs.python.org/issue17177.

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

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

Re: [Django] #21634: Lis of installed apps set to empty when ImproperlyConfigured exception is raised

2013-12-18 Thread Django

#21634: Lis of installed apps set to empty when ImproperlyConfigured exception 
is
raised
-+-
 Reporter:  nikolay.v.golub@…|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.6
Component:  Core (Management |   Resolution:
  commands)  | 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 nikolay.v.golub@…):

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


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

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

[Django] #21634: Lis of installed apps set to empty when ImproperlyConfigured exception is raised

2013-12-18 Thread Django

#21634: Lis of installed apps set to empty when ImproperlyConfigured exception 
is
raised
+
 Reporter:  nikolay.v.golub@…   |  Owner:  nobody
 Type:  Cleanup/optimization| Status:  new
Component:  Core (Management commands)  |Version:  1.6
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 This code in django.core.management. !__init!__.py at line 104
 {{{
 #!div style="font-size: 80%"
 Code highlighting:
   {{{#!python
 # Find the installed apps
 from django.conf import settings
 try:
 apps = settings.INSTALLED_APPS
 except ImproperlyConfigured:
 # Still useful for commands that do not require functional
 settings,
 # like startproject or help
 apps = []
}}}
 }}}
 Says, that  apps will be set to [] if ImproperlyConfigured exception is
 raised. This leads to misunderstanding, when error raised for wrong
 configuration of 3rd-party application.

 Also this code contradicts PEP-20:
 * Explicit is better than implicit
 * Errors should never pass silently

 For example if you use South, and have any 3rd party app, that can raise
 ImproperlyConfigured exception you will get following error when you'll
 try to migrate apps db schema:
 {{{
 Unknown command: 'migrate'
 Type 'manage.py help' for usage.
 }}}
 What purpose of this catching? If something is improperly configured,
 maybe user should know about it?

 Please, review this ticket and remove this catching.

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

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

Re: [Django] #6159: Reusable templatetags for admin list

2013-12-18 Thread Django

#6159: Reusable templatetags for admin list
-+-
 Reporter:  Petr Marhoun |Owner:  nobody
     |   Status:  new
 Type:  New feature  |  Version:  newforms-
Component:  contrib.admin|  admin
 Severity:  Normal   |   Resolution:
 Keywords:  nfa-someday  | Triage Stage:
Has patch:  1|  Someday/Maybe
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by bruno@…):

 * cc: bruno@… (added)


Comment:

 This ticket could be closed as fixed by now - the proposed changes have
 been applied.

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

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

Re: [Django] #21633: django.utils.functional.update_wrapper is missing

2013-12-18 Thread Django

#21633: django.utils.functional.update_wrapper is missing
-+--
 Reporter:  mbertheau@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Utilities|  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:  1|UI/UX:  0
-+--
Changes (by aaugustin):

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


Comment:

 It's available in the standard library, there's no point in importing it
 from django.utils.functional, is there?

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

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

[Django] #21633: django.utils.functional.update_wrapper is missing

2013-12-18 Thread Django

#21633: django.utils.functional.update_wrapper is missing
-+
 Reporter:  mbertheau@…  |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Utilities|Version:  1.6
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  1|  UI/UX:  0
-+
 It was removed, afaict accidentally, in
 https://github.com/django/django/commit/876fc391

 Please add it back as it breaks backwards compatibility.

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

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

78 matches

Mail list logo