date:20140619

Re: [Django] #13711: Very long field names on models cause problems

2014-06-19 Thread Django

#13711: Very long field names on models cause problems
-+-
 Reporter:  russellm |Owner:
 Type:  Bug  |  anubhav9042
Component:  Database layer   |   Status:  closed
  (models, ORM)  |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by anubhav9042):

 I have made a patch for what I suggested:
 https://github.com/coder9042/django/compare/gsoc_13711
 IMO this is the right way for this issue and also now the check runs for
 all backends rather than only for the one with minimum allowed length.
 Also the backends with the `connection.feature.supports_auto_truncation`
 set to  `True` are skipped.

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

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

Re: [Django] #22791: makemigrations interactive questioner ignores app labels

2014-06-19 Thread Django

#22791: makemigrations interactive questioner ignores app labels
--+
 Reporter:  bendavis78|Owner:  whoshuu
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Migrations|  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by whoshuu):

 * has_patch:  0 => 1


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

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

Re: [Django] #22791: makemigrations interactive questioner ignores app labels

2014-06-19 Thread Django

#22791: makemigrations interactive questioner ignores app labels
--+
 Reporter:  bendavis78|Owner:  whoshuu
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Migrations|  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 whoshuu):

 Made a quick change in `makemigrations` using approach 1.

 PR sent: https://github.com/django/django/pull/2834

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

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

Re: [Django] #22862: makemigrations --merge broken because --noinput isn't registered

2014-06-19 Thread Django

#22862: makemigrations --merge broken because --noinput isn't registered
-+--
 Reporter:  art@…|Owner:  whoshuu
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by whoshuu):

 * has_patch:  0 => 1


Comment:

 PR sent: https://github.com/django/django/pull/2833

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

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

Re: [Django] #22862: makemigrations --merge broken because --noinput isn't registered

2014-06-19 Thread Django

#22862: makemigrations --merge broken because --noinput isn't registered
-+--
 Reporter:  art@…|Owner:  whoshuu
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-beta-2
 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 whoshuu):

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


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

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

Re: [Django] #22836: Issue on the code in the documentation

2014-06-19 Thread Django

#22836: Issue on the code in the documentation
--+
 Reporter:  anonymous |Owner:  maxocub
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by maxocub):

 * has_patch:  0 => 1


Comment:

 Here's my [https://github.com/django/django/pull/2832 PR].

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

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

Re: [Django] #21113: django_admin_log table stores messages in different languages depending on which language was active while editing.

2014-06-19 Thread Django

#21113: django_admin_log table stores messages in different languages depending 
on
which language was active while editing.
-+
 Reporter:  dimyur27@…   |Owner:  jooyous
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin logs i18n  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by jooyous):

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


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

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

Re: [Django] #13163: Display link to change-form on inlines where model is registered in admin site

2014-06-19 Thread Django

#13163: Display link to change-form on inlines where model is registered in 
admin
site
---+
 Reporter:  DrMeers|Owner:  DrMeers
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  inline link| Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  1
---+

Comment (by blueyed):

 @smcoll:

 It looks like there is a wrong `if` in your patch: `{% if
 inline_admin_form.original %}`. It should check for the new
 `show_edit_link` option probably.

 I assume that it won't work for many2many inlines, where you have `model =
 Foo.bars.through`?

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

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

Re: [Django] #22836: Issue on the code in the documentation

2014-06-19 Thread Django

#22836: Issue on the code in the documentation
--+
 Reporter:  anonymous |Owner:  maxocub
 Type:  Cleanup/optimization  |   Status:  assigned
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:  1 |UI/UX:  0
--+
Changes (by maxocub):

 * owner:  nobody => maxocub
 * status:  new => assigned
 * version:  1.6 => master


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

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

Re: [Django] #22874: Swappable dependency breaks if swappable model not in first migration of its app

2014-06-19 Thread Django

#22874: Swappable dependency breaks if swappable model not in first migration of
its app
-+
 Reporter:  melinath |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by SmileyChris):

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


Comment:

 This is a valid bug, not sure if it's considered release blocker - will
 bump up and let andrew decide.

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

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

Re: [Django] #22874: Swappable dependency breaks if swappable model not in first migration of its app

2014-06-19 Thread Django

#22874: Swappable dependency breaks if swappable model not in first migration of
its app
+--
 Reporter:  melinath|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by SmileyChris):

 Reverse dependencies are possible, just not documented - use `run_before`
 in the same way you use the `dependencies` attribute.

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

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

Re: [Django] #22874: Swappable dependency breaks if swappable model not in first migration of its app

2014-06-19 Thread Django

#22874: Swappable dependency breaks if swappable model not in first migration of
its app
+--
 Reporter:  melinath|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by SmileyChris):

 * version:  1.7-beta-2 => master


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

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

Re: [Django] #22875: "ValueError: Lookup failed for model referenced by field app.Model.m2mfield: app.ThroghModel" in simple-self contained M2M setup

2014-06-19 Thread Django

#22875: "ValueError: Lookup failed for model referenced by field
app.Model.m2mfield: app.ThroghModel" in simple-self contained M2M setup
+--
 Reporter:  ramiro  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7-beta-2
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Description changed by ramiro:

Old description:

> In a simple `ManyToManyField` with intermediate model setup involving
> three models in the same application:
>
> {{{
> # app_b/models.py
> from django.db import models
>
> class Employee(models.Model):
> name = models.CharField(max_length=30)
>
> class Employer(models.Model):
> name = models.CharField(max_length=30)
> employees = models.ManyToManyField(Employee, through='Employment')
>
> class Employment(models.Model):
> employee = models.ForeignKey(Employee)
> employer = models.ForeignKey(Employer)
> recruiting_date = models.DateField()
> }}}
>
> I'm seeing the following traceback when running `migrate` after the
> initial migration has been created for the app:
>
> {{{
> ~/dtest/dtest002$ rm -rf db.sqlite3 app_b/migrations
>
> ~/dtest/dtest002$ PYTHONPATH=~/django/upstream python ./manage.py
> makemigrations
> No changes detected
>
> ramiro@serverid:~/dtest/dtest002$ PYTHONPATH=~/django/upstream python
> ./manage.py makemigrations app_b
> Migrations for 'app_b':
>   0001_initial.py:
> - Create model Employee
> - Create model Employer
> - Create model Employment
>
> ~/dtest/dtest002$ PYTHONPATH=~/django/upstream python ./manage.py migrate
> Operations to perform:
>   Synchronize unmigrated apps: (none)
>   Apply all migrations: admin, contenttypes, app_b, auth, sessions
> Synchronizing apps without migrations:
>   Creating tables...
>   Installing custom SQL...
>   Installing indexes...
> Running migrations:
>   Applying contenttypes.0001_initial... OK
>   Applying auth.0001_initial... OK
>   Applying admin.0001_initial... OK
>   Applying app_b.0001_initial...Traceback (most recent call last):
>   File "./manage.py", line 10, in 
> execute_from_command_line(sys.argv)
>   File "/home/xxx/django/upstream/django/core/management/__init__.py",
> line 385, in execute_from_command_line
> utility.execute()
>   File "/home/xxx/django/upstream/django/core/management/__init__.py",
> line 377, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "/home/xxx/django/upstream/django/core/management/base.py", line
> 288, in run_from_argv
> self.execute(*args, **options.__dict__)
>   File "/home/xxx/django/upstream/django/core/management/base.py", line
> 337, in execute
> output = self.handle(*args, **options)
>   File
> "/home/xxx/django/upstream/django/core/management/commands/migrate.py",
> line 146, in handle
> executor.migrate(targets, plan, fake=options.get("fake", False))
>   File "/home/xxx/django/upstream/django/db/migrations/executor.py", line
> 62, in migrate
> self.apply_migration(migration, fake=fake)
>   File "/home/xxx/django/upstream/django/db/migrations/executor.py", line
> 96, in apply_migration
> migration.apply(project_state, schema_editor)
>   File "/home/xxx/django/upstream/django/db/migrations/migration.py",
> line 107, in apply
> operation.database_forwards(self.app_label, schema_editor,
> project_state, new_state)
>   File
> "/home/xxx/django/upstream/django/db/migrations/operations/models.py",
> line 33, in database_forwards
> apps = to_state.render()
>   File "/home/xxx/django/upstream/django/db/migrations/state.py", line
> 89, in render
> model=lookup_model,
> ValueError: Lookup failed for model referenced by field
> app_b.Employer.employees: app_b.Employment
> }}}
>
> I'm selecting '1.7/beta-2' as Version but I'm running the latest
> `stable/1.7.x` code:
>
> {{{
> ~/django/upstream$ git log  -1
> commit 30d8b95139a1fa3070f3b112115e624ffcf8e555
> Author: Tim Graham 
> Date:   Thu Jun 19 11:02:53 2014 -0400
>
> [1.7.x] Added feature for implied null (needed for Firebird backend)
>
> Backport of 1b07781292 from master
> }}}
>
> Initially Employee didn't exist and the m2m relationship was against a
> custom User model.
>
> After that trying to create a minimal setup that reproduces the issue,
> usage of the swappable user model feature was removed and the m2m field
> was re-pointed to standard auth.User, and finally to a local Employee
> model.

New description:

 In a simple `ManyToManyField` with intermediate model setup involving
 three models in the same

Re: [Django] #22873: Allow disabling debug cursor when DEBUG=True

2014-06-19 Thread Django

Comment (by john@…):

This was added way back in 2010 in [5506653] by Alex Gaynor to support
tests for `assertNumQueries`, fixing #5416. Previously, the code directly
looked at `settings.DEBUG`. It may have been the intention to allow more
control over the new debug cursor, but the most direct reason was to
support the new assertion without forcing the test to run with
`DEBUG=True`. `assertNumQueries` might now be broken when queries pass
9000, but that's probably rare and silly.

If `use_debug_cursor` it could initialized to `settings.DEBUG` in the
`__init__` method, then it could be set or cleared by code as needed. I'm
not familiar with early settings loading, so it is possible that settings
isn't initialized at this point.

If the current behavior is retained, `force_debug_cursor` is a better
name, making it clearer that this is a private hook for testing.

If this undocumented API goes away, I could instead fail the management
command when `DEBUG=True`.

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

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

Re: [Django] #22872: Backwards incompatible change: Can't proxy User model: RuntimeError: App registry isn't ready yet.

2014-06-19 Thread Django

#22872: Backwards incompatible change: Can't proxy User model: RuntimeError: App
registry isn't ready yet.
---+--
 Reporter:  jdufresne  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  1.7-beta-2
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by jdufresne):

 Replying to [comment:1 aaugustin]:
 > The best idea I have is to create an AppConfig for your app and create
 the model in its ready() method, then add it to the module.

 How would one go about importing this model for use elsewhere (other
 models, forms, views, etc.)? These references are often used at compile
 time such as model forms and generic views. It seems, importing the proxy
 model would never work at compile time. Every function that referenced the
 proxy model directly would need to import it at the top of the function so
 as to delay the import. Or, I guess, implement another `get_user_model()`
 style function and sprinkle it all over.

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

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

[Django] #22875: "ValueError: Lookup failed for model referenced by field app.Model.m2mfield: app.ThroghModel" in simple-self contained M2M setup

2014-06-19 Thread Django

#22875: "ValueError: Lookup failed for model referenced by field
app.Model.m2mfield: app.ThroghModel" in simple-self contained M2M setup
--+
   Reporter:  ramiro  |  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  Migrations  |Version:  1.7-beta-2
   Severity:  Normal  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+
 In a simple `ManyToManyField` with intermediate model setup involving
 three models in the same application:

 {{{
 # app_b/models.py
 from django.db import models

 class Employee(models.Model):
 name = models.CharField(max_length=30)

 class Employer(models.Model):
 name = models.CharField(max_length=30)
 employees = models.ManyToManyField(Employee, through='Employment')

 class Employment(models.Model):
 employee = models.ForeignKey(Employee)
 employer = models.ForeignKey(Employer)
 recruiting_date = models.DateField()
 }}}

 I'm seeing the following traceback when running `migrate` after the
 initial migration has been created for the app:

 {{{
 ~/dtest/dtest002$ rm -rf db.sqlite3 app_b/migrations

 ~/dtest/dtest002$ PYTHONPATH=~/django/upstream python ./manage.py
 makemigrations
 No changes detected

 ramiro@serverid:~/dtest/dtest002$ PYTHONPATH=~/django/upstream python
 ./manage.py makemigrations app_b
 Migrations for 'app_b':
   0001_initial.py:
 - Create model Employee
 - Create model Employer
 - Create model Employment

 ~/dtest/dtest002$ PYTHONPATH=~/django/upstream python ./manage.py migrate
 Operations to perform:
   Synchronize unmigrated apps: (none)
   Apply all migrations: admin, contenttypes, app_b, auth, sessions
 Synchronizing apps without migrations:
   Creating tables...
   Installing custom SQL...
   Installing indexes...
 Running migrations:
   Applying contenttypes.0001_initial... OK
   Applying auth.0001_initial... OK
   Applying admin.0001_initial... OK
   Applying app_b.0001_initial...Traceback (most recent call last):
   File "./manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/home/xxx/django/upstream/django/core/management/__init__.py",
 line 385, in execute_from_command_line
 utility.execute()
   File "/home/xxx/django/upstream/django/core/management/__init__.py",
 line 377, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/xxx/django/upstream/django/core/management/base.py", line
 288, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/home/xxx/django/upstream/django/core/management/base.py", line
 337, in execute
 output = self.handle(*args, **options)
   File
 "/home/xxx/django/upstream/django/core/management/commands/migrate.py",
 line 146, in handle
 executor.migrate(targets, plan, fake=options.get("fake", False))
   File "/home/xxx/django/upstream/django/db/migrations/executor.py", line
 62, in migrate
 self.apply_migration(migration, fake=fake)
   File "/home/xxx/django/upstream/django/db/migrations/executor.py", line
 96, in apply_migration
 migration.apply(project_state, schema_editor)
   File "/home/xxx/django/upstream/django/db/migrations/migration.py", line
 107, in apply
 operation.database_forwards(self.app_label, schema_editor,
 project_state, new_state)
   File
 "/home/xxx/django/upstream/django/db/migrations/operations/models.py",
 line 33, in database_forwards
 apps = to_state.render()
   File "/home/xxx/django/upstream/django/db/migrations/state.py", line 89,
 in render
 model=lookup_model,
 ValueError: Lookup failed for model referenced by field
 app_b.Employer.employees: app_b.Employment
 }}}

 I'm selecting '1.7/beta-2' as Version but I'm running the latest
 `stable/1.7.x` code:

 {{{
 ~/django/upstream$ git log  -1
 commit 30d8b95139a1fa3070f3b112115e624ffcf8e555
 Author: Tim Graham 
 Date:   Thu Jun 19 11:02:53 2014 -0400

 [1.7.x] Added feature for implied null (needed for Firebird backend)

 Backport of 1b07781292 from master
 }}}

 Initially Employee didn't exist and the m2m relationship was against a
 custom User model.

 After that trying to create a minimal setup that reproduces the issue,
 usage of the swappable user model feature was removed and the m2m field
 was re-pointed to standard auth.User, and finally to a local Employee
 model.

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

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

Re: [Django] #8408: Add a new meta option: don't do count(*) in admin

2014-06-19 Thread Django

#8408: Add a new meta option: don't do count(*) in admin
---+
 Reporter:  lidaobing  |Owner:  oinopion
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Cerin):

 See here for some interesting workarounds of Django's inefficient result
 count mechanism: http://craiglabenz.me/2013/06/12/how-i-made-django-admin-
 scale/

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

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

Re: [Django] #13711: Very long field names on models cause problems

2014-06-19 Thread Django

#13711: Very long field names on models cause problems
-+-
 Reporter:  russellm |Owner:
 Type:  Bug  |  anubhav9042
Component:  Database layer   |   Status:  closed
  (models, ORM)  |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by anubhav9042):

 If we can make a decision then I will make a patch for this.

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

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

Re: [Django] #8408: Add a new meta option: don't do count(*) in admin

2014-06-19 Thread Django

Comment (by Cerin):

+1 for this feature. I have a few databases with tables containing tens of
millions of records, and browsing them in Django is painfully slow, even
with caching and extensive indexing. These sections of admin takes
*minutes* to load, and DDT is telling me that around 90% of the load time
is just from a single "SELECT COUNT(*) ..." to display the total result
count, which I don't care about.

Yes, both PostgreSQL and MySQL have tricks for approximate counts, but
only for total tables sizes, which doesn't help once you begin filtering.

And can confirm that using InfinitePaginator from django-pagination and
specifying a custom paginator=InfinitePaginator in your modeladmin does
not work because admin still expects to receive a valid count, which
causes InfinitePaginator to throw NotImplementedError exceptions.

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

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

Re: [Django] #13711: Very long field names on models cause problems

2014-06-19 Thread Django

#13711: Very long field names on models cause problems
-+-
 Reporter:  russellm |Owner:
 Type:  Bug  |  anubhav9042
Component:  Database layer   |   Status:  closed
  (models, ORM)  |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by anubhav9042):

 One approach:

 Adding a setting which tells whether `truncate_name` is called or not,
 like `connection.support_auto_truncation` and then running the model check
 only for those dbs which have this set to 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/066.cab9d24c9cf94292e935ff0ebff95c42%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22796: "Working with forms" docs need improving

2014-06-19 Thread Django

#22796: "Working with forms" docs need improving
--+
 Reporter:  EvilDMP   |Owner:  EvilDMP
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timo):

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


Comment:

 Some more comments have been left on the PR.

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

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

Re: [Django] #13711: Very long field names on models cause problems

2014-06-19 Thread Django

#13711: Very long field names on models cause problems
-+-
 Reporter:  russellm |Owner:
 Type:  Bug  |  anubhav9042
Component:  Database layer   |   Status:  closed
  (models, ORM)  |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timo):

 As discussed with Shai on IRC, column names are auto-truncated in Oracle
 so the model check isn't needed so much there, or at least the errors
 should be reduced to warnings. 3rd-party backends may implemented similar
 behavior so we should keep that in mind when deciding on a solution.

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

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

Re: [Django] #16335: Document why you cannot iterate defaultdict in templates (was: Cannot iterate defaultdict in template)

2014-06-19 Thread Django

#16335: Document why you cannot iterate defaultdict in templates
-+-
 Reporter:  jacob.ninja.dev@…|Owner:
 Type:  Bug  |  bluejeansummer
Component:  Documentation|   Status:  closed
 Severity:  Normal   |  Version:  1.3
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  1|  Needs documentation:  0
 |  Patch needs improvement:  1
 |UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 The documentation that was added as part of the ticket
 [d171b3cc0b32374fd5891254b04693e9ec8ed946] explains why it doesn't work.

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

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

Re: [Django] #22791: makemigrations interactive questioner ignores app labels

2014-06-19 Thread Django

Comment (by whoshuu):

I'd actually change this ticket to, "makemigrations ignores app labels for
conflicts". From the looks of it, there are three issues I would classify
as improper behavior:

1. (Original ticket) Interactive questioner will ask a "y/N" question for
an app that was not specified.
2. An outstanding conflict in an unspecified app will throw a
`CommandErorr` if `merge` is set to `False`.
3. An outstanding conflict in an unspecified app **will** create a
migration file if `merge` is set to `True` and `interactive` is left as
`False`.

The expected behavior is to ignore apps that have not been specified when
at least one app has been specified. There are two ways of going about
eliminating these behaviors:

1. Filter out `conflicts` from `loader.detect_conflicts` in the
`makemigrations` module by `app_labels`. This localizes the required
changes but may be inefficient as conflicts will be scanned for
unspecified apps.
2. Pass in `app_labels` to `loader.detect_conflicts()` and only scan for
conflicts in the apps that have been specified. This is more efficient but
touches more code.

I'd like to hear what people have to say about this. If necessary, I can
create the tickets for issues 2 and 3 if merging them all into this one is
inappropriate.

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

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

Re: [Django] #22874: Swappable dependency breaks if swappable model not in first migration of its app (was: Swappable dependency not working)

2014-06-19 Thread Django

Comment (by melinath):

It seems like this wasn't working because swappable dependency
automatically goes to the first migration in the swapped model's app - and
if the swappable model isn't migrated into existence in the first
migration, the swappable model dependency breaks.

I don't think this would be a serious problem in the future - brambling
has some slightly older 1.7 migrations, from back when it would generate a
million of them. I believe it's now consolidated down to one initial
migration, so most people probably won't run into this.

Workaround was to add a dependency to the last migration in the swappable
model's app. Would that work for the swappable model dependency behavior?
(I could also imagine situations where a swappable model is switched out
for a different one over the course of the app.)

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

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

Re: [Django] #22874: Swappable dependency not working (was: Need a way to declare a dependency for AUTH_USER_MODEL.)

2014-06-19 Thread Django

#22874: Swappable dependency not working
+--
 Reporter:  melinath|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7-beta-2
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by melinath):

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


Comment:

 ... wait, swappable dependencies are totally a thing. Okay. So why isn't
 this working?

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

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

[Django] #22874: Need a way to declare a dependency for AUTH_USER_MODEL.

2014-06-19 Thread Django

#22874: Need a way to declare a dependency for AUTH_USER_MODEL.
+
Reporter: melinath| Owner: nobody
Type: Bug | Status: new
Component: Migrations |Version: 1.7-beta-2
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
+
Right now, it's impossible to declare a dependency to/from
AUTH_USER_MODEL.

Here's the error I'm getting:

{{{
ValueError: Lookup failed for model referenced by field
feedback.FeedbackItem.user: brambling.Person
}}}

This is bad on two fronts:

1. From the "brambling" side - the side declaring/using an AUTH_USER_MODEL
- I can't use the "feedback" module because it doesn't declare a
dependency on my model - and django doesn't currently support reverse
dependencies (unless they're undocumented.)

2. From the "feedback" side - the side with migrations and a swappable FK
- the app can't be used by anyone who actually has a swappable model,
because there's no way to declare a correct migration dependency.

I feel like the correct fix here would be to have a 'swappable
dependency'.

This is on stable/1.7.x

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

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

Re: [Django] #22873: Allow disabling debug cursor when DEBUG=True

2014-06-19 Thread Django

#22873: Allow disabling debug cursor when DEBUG=True
-+-
 Reporter:  john@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 Indeed, `use_debug_cursor` was a tri-valued boolean. That ranks quite high
 on my scale of programming anti-patterns. Furthermore, one of the three
 values was never used by Django.

 So I changed it to a regular boolean. The new logic is:

 * If db.connection.use_debug_cursor is a true-ish value, use a debug
 cursor;
 * If db.connection.use_debug_cursor is a false-ish value, defer to
 `settings.DEBUG`.

 `None` is just a false-ish value among others.

 I should have changed the name to something like `force_debug_cursor` but
 I didn't find a short and explicit name so I left it as is. Suggestions?

 I don't think the tri-valued boolean behaviour was introduced on purpose
 because it wasn't documented. It was a private API with no guarantee that
 its behaviour will be preserved across versions.

 Accepting to fix this ticket would mean turning `use_debug_cursor` into a
 public API with its previous three-valued behaviour. I'm very close to -1
 on this, but I'll let someone else confirm in case that behaviour was
 there for a good reason. If it was, it must be documented.

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

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

Re: [Django] #22872: Backwards incompatible change: Can't proxy User model: RuntimeError: App registry isn't ready yet.

2014-06-19 Thread Django

#22872: Backwards incompatible change: Can't proxy User model: RuntimeError: App
registry isn't ready yet.
---+--
Reporter: jdufresne |Owner: nobody
Type: Bug| Status: new
Component: Uncategorized | Version: 1.7-beta-2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 |UI/UX: 0
---+--
Changes (by aaugustin):

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

Comment:

As part of the app-loading refactor, it's expected that calling
get_user_model() at compile-time fail with this message.

The best idea I have is to create an AppConfig for your app and create the
model in its ready() method, then add it to the module.

I suspect that many non-declarative models will require this pattern.

I'm leaving the ticket open for now in case someone has other ideas which
may involve changes in Django.

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

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

Re: [Django] #22058: Consider a more general method to replace handlerXXX

2014-06-19 Thread Django

#22058: Consider a more general method to replace handlerXXX
-+---
 Reporter:  debanshuk|Owner:  anubhav9042
 Type:  New feature  |   Status:  assigned
Component:  Core (URLs)  |  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 anubhav9042):

 * has_patch:  0 => 1


Comment:

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

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

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

Re: [Django] #12663: Information provided by Model._meta should be documented in /models/options/

2014-06-19 Thread Django

#12663: Information provided by Model._meta should be documented in
/models/options/
-+-
 Reporter:  MadeR|Owner:  pirosb3
 Type:  New feature  |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  Model Meta   | Triage Stage:  Accepted
  Documentation  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"d862fae5bbfb52ab7aeaad5a59b3d8b27b30c8f9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d862fae5bbfb52ab7aeaad5a59b3d8b27b30c8f9"
 Refs #12663 -- Added tests for methods in db.models.options.

 Thanks Russell Keith-Magee and Tim Graham for reviews.
 }}}

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

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

[django/django] d862fa: Refs #12663 -- Added tests for methods in db.model...

2014-06-19 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d862fae5bbfb52ab7aeaad5a59b3d8b27b30c8f9
  
https://github.com/django/django/commit/d862fae5bbfb52ab7aeaad5a59b3d8b27b30c8f9
  Author: Daniel Pyrathon 
  Date:   2014-06-19 (Thu, 19 Jun 2014)

  Changed paths:
M AUTHORS
A tests/model_meta/__init__.py
A tests/model_meta/models.py
A tests/model_meta/test.py

  Log Message:
  ---
  Refs #12663 -- Added tests for methods in db.models.options.

Thanks Russell Keith-Magee and Tim Graham for reviews.


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

[Django] #22873: Allow disabling debug cursor when DEBUG=True

2014-06-19 Thread Django

#22873: Allow disabling debug cursor when DEBUG=True
--+
 Reporter:  john@…|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  1 |  UI/UX:  0
--+
 In Django 1.6, the logic for using the CursorDebugWrapper was:

 * If db.connection.use_debug_cursor is True, use it
 * If db.connection.use_debug_cursor is None, defer to settings.DEBUG
 * if db.connection.use_debug_cursor is False, don't use it.

 This was changed in the fix for #20420.  Commit [127218b92bb8] changed the
 logic to:

 * If db.connection.use_debug_cursor is True, use it
 * If db.connection.use_debug_cursor is False or None, defer to
 settings.DEBUG

 I am using a management command to load lots of data into the database,
 and I was setting use_debug_cursor to False to disable query logging
 before my lengthy import.  I'd rather not have to remember to set
 DEBUG=False every time I run a management command on my dev box.  I'd like
 the 1.6 trinary behavior, as well as the better queries_logged property
 introduced in [40bfd8561d016]

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

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

[Django] #22872: Backwards incompatible change: Can't proxy User model: RuntimeError: App registry isn't ready yet.

2014-06-19 Thread Django

#22872: Backwards incompatible change: Can't proxy User model: RuntimeError: App
registry isn't ready yet.
---+
 Reporter:  jdufresne  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  1.7-beta-2
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 My application creates proxies of the user model to add custom methods
 that are useful in certain contexts. There is an attempt to do this in a
 `AUTH_USER_MODEL` agnostic way. This fails with the latest beta version of
 1.7.

 Starting from a fresh install and project I created the following files in
 directory `myapp`.

 `myapp/models.py`

 {{{
 from django.contrib.auth import get_user_model


 class MyUser(get_user_model()):
 def my_method(self):
 return 'foo'

 class Meta:
 proxy = True
 }}}

 `myapp/tests.py`

 {{{
 from django.test import TestCase
 from myapp.models import MyUser


 class MyTestCase(TestCase):
 def test_my_user(self):
 user = MyUser()
 self.assertTrue(user)
 }}}


 Django 1.7 beta 2
 {{{
 $ python manage.py test
 Traceback (most recent call last):
   File "manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/home/jon/djtest/venv/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 427, in
 execute_from_command_line
 utility.execute()
   File "/home/jon/djtest/venv/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 391, in execute
 django.setup()
   File "/home/jon/djtest/venv/lib/python2.7/site-
 packages/django/__init__.py", line 21, in setup
 apps.populate(settings.INSTALLED_APPS)
   File "/home/jon/djtest/venv/lib/python2.7/site-
 packages/django/apps/registry.py", line 106, in populate
 app_config.import_models(all_models)
   File "/home/jon/djtest/venv/lib/python2.7/site-
 packages/django/apps/config.py", line 190, in import_models
 self.models_module = import_module(models_module_name)
   File "/usr/lib64/python2.7/importlib/__init__.py", line 37, in
 import_module
 __import__(name)
   File "/home/jon/djtest/djtest/myapp/models.py", line 4, in 
 class MyUser(get_user_model()):
   File "/home/jon/djtest/venv/lib/python2.7/site-
 packages/django/contrib/auth/__init__.py", line 136, in get_user_model
 return django_apps.get_model(settings.AUTH_USER_MODEL)
   File "/home/jon/djtest/venv/lib/python2.7/site-
 packages/django/apps/registry.py", line 187, in get_model
 self.check_ready()
   File "/home/jon/djtest/venv/lib/python2.7/site-
 packages/django/apps/registry.py", line 119, in check_ready
 raise RuntimeError("App registry isn't ready yet.")
 RuntimeError: App registry isn't ready yet.
 }}}

 Django 1.6.5

 {{{
 $ python manage.py test
 Creating test database for alias 'default'...
 .
 --
 Ran 1 test in 0.001s

 OK
 Destroying test database for alias 'default'...
 }}}

 If there is a better (or forward compatible) way proxy an unknown `User`
 model, I'd be happy to hear about it.

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

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

Re: [Django] #22867: Pickling models is slow in alpha versions

2014-06-19 Thread Django

#22867: Pickling models is slow in alpha versions
--+
 Reporter:  Suor  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Utilities |  Version:  master
 Severity:  Release blocker   |   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+

Comment (by loic84):

 Upgrading Python 2.6 which is EOL and recommitting this fix is the ideal
 course of action.

 However if we don't manage to do so within a few of days, I'd suggest we
 go with a stopgap solution like
 https://gist.github.com/313430836d20006916c4f.

 The regression could be quite severe to anyone caching large querysets
 since we'd be starting a process for each model.

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

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

Re: [Django] #22791: makemigrations interactive questioner ignores app labels

2014-06-19 Thread Django

#22791: makemigrations interactive questioner ignores app labels
--+
 Reporter:  bendavis78|Owner:  whoshuu
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Migrations|  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 whoshuu):

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


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

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

Re: [Django] #22871: All links returned by search engines don't work anymore!

2014-06-19 Thread Django

#22871: All links returned by search engines don't work anymore!
-+-
 Reporter:  davide.guerri@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  *.djangoproject.com  |  Version:
 Severity:  Normal   |   Resolution:  fixed
 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 anonymous):

 Wow, thank you for the quick response!

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

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

Re: [Django] #22867: Pickling models is slow in alpha versions

2014-06-19 Thread Django

#22867: Pickling models is slow in alpha versions
--+
 Reporter:  Suor  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Utilities |  Version:  master
 Severity:  Release blocker   |   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 aaugustin):

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


Comment:

 While this commit was correct, I had to revert it because it broke the
 docs builds, which are still running on Python 2.6.

 We need to upgrade the djangoproject.com server before we can push this
 change. Sorry for the inconvenience.

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

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

Re: [Django] #22869: broken link

2014-06-19 Thread Django

#22869: broken link
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.6
 Severity:  Normal |   Resolution:  fixed
 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 aaugustin):

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

Re: [Django] #22870: Broken release notes links in dev documentation

2014-06-19 Thread Django

#22870: Broken release notes links in dev documentation
-+-
 Reporter:  makmanalp|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  docs,links,broken| Triage Stage:
  link   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 This was a problem on the server. The docs are currently rebuilding and
 should be up within a few minutes. Thanks 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/067.1ea4ebe225b8bc82a439a88c1b9d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22871: All links returned by search engines don't work anymore!

2014-06-19 Thread Django

#22871: All links returned by search engines don't work anymore!
-+-
 Reporter:  davide.guerri@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  *.djangoproject.com  |  Version:
 Severity:  Normal   |   Resolution:  fixed
 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 aaugustin):

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


Comment:

 The docs are currently rebuilding and should be up within a few minutes.
 Thanks 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/081.2a3f830e166df6ace04f097f00d65b99%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22867: Pickling models is slow in alpha versions

2014-06-19 Thread Django

#22867: Pickling models is slow in alpha versions
--+
 Reporter:  Suor  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Utilities |  Version:  master
 Severity:  Release blocker   |   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 Aymeric Augustin ):

 In [changeset:"01399fa0aaa817281c77bbb4b7d82c6c8487c916"]:
 {{{
 #!CommitTicketReference repository=""
 revision="01399fa0aaa817281c77bbb4b7d82c6c8487c916"
 Revert "Fixed #22867 -- Memoized
 django.utils.version.get_git_changeset()."

 This reverts commit 80f4487 temporarily, because that commit prevented
 the djangoproject.com server from building the docs, because it still
 uses Python 2.6.
 }}}

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

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

[django/django] 01399f: Revert "Fixed #22867 -- Memoized django.utils.vers...

2014-06-19 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 01399fa0aaa817281c77bbb4b7d82c6c8487c916
  
https://github.com/django/django/commit/01399fa0aaa817281c77bbb4b7d82c6c8487c916
  Author: Aymeric Augustin 
  Date:   2014-06-19 (Thu, 19 Jun 2014)

  Changed paths:
M django/utils/version.py

  Log Message:
  ---
  Revert "Fixed #22867 -- Memoized django.utils.version.get_git_changeset()."

This reverts commit 80f4487 temporarily, because that commit prevented
the djangoproject.com server from building the docs, because it still
uses Python 2.6.


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

Re: [Django] #22869: broken link

2014-06-19 Thread Django

#22869: broken link
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  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
---+--

Comment (by aaugustin):

 Correct. We noticed shortly after I answered your ticket. We're looking
 into it. Thanks 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/067.2e75475a6a6b11b9cb942ed8ca2d665f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22871: All links returned by search engines don't work anymore!

2014-06-19 Thread Django

#22871: All links returned by search engines don't work anymore!
-+-
 Reporter:  davide.guerri@…  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  *.djangoproject.com  |  Version:
 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 Deacalion):

 * needs_better_patch:   => 0
 * component:  Uncategorized => *.djangoproject.com
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 The dev version of the docs isn't working:
 https://docs.djangoproject.com/en/dev

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

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

Re: [Django] #22865: Testing framework: ValueError: Cannot create form field for 'user' yet, because its related model 'myauth.User' has not been loaded yet

2014-06-19 Thread Django

#22865: Testing framework: ValueError: Cannot create form field for 'user' yet,
because its related model 'myauth.User' has not been loaded yet
---+--
 Reporter:  jdufresne  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.6
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by renatooliveira):

 Ok, thanks!

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

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

[Django] #22871: All links returned by search engines don't work anymore!

2014-06-19 Thread Django

#22871: All links returned by search engines don't work anymore!
-+
 Reporter:  davide.guerri@…  |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Uncategorized|Version:
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 All links returned by search engines don't work anymore!

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

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

Re: [Django] #22869: broken link

2014-06-19 Thread Django

#22869: broken link
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  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
---+--

Comment (by anonymous):

 The dev version of the documentation is not being published,

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

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

Re: [Django] #22869: broken link

2014-06-19 Thread Django

#22869: broken link
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  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 aaugustin):

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


Comment:

 Can you clarify which link doesn't work, and on which page you found that
 link?

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

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

Re: [Django] #22865: Testing framework: ValueError: Cannot create form field for 'user' yet, because its related model 'myauth.User' has not been loaded yet

2014-06-19 Thread Django

#22865: Testing framework: ValueError: Cannot create form field for 'user' yet,
because its related model 'myauth.User' has not been loaded yet
---+--
 Reporter:  jdufresne  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.6
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by aaugustin):

 Unfortunately, the "fix" involves some major backwards-incompatibilities,
 and thus cannot be backported to a future 1.6.x release.

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

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

[Django] #22870: Broken release notes links in dev documentation

2014-06-19 Thread Django

#22870: Broken release notes links in dev documentation
---+
 Reporter:  makmanalp  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  master
 Severity:  Normal |   Keywords:  docs,links,broken link
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Examples:
 https://docs.djangoproject.com/en/dev/releases/1.4/
 https://docs.djangoproject.com/en/dev/internals/deprecation/

 But changing /dev/ to /1.6/ works, for example.

 I'm guessing this is partially intentional (maybe a file move?) but most
 of these links are on the top of google search results like "django
 release notes" and "django deprecation timeline". Maybe having the docs
 404 page show you pages from previous doc versions could be handy? In any
 case, just thought it might be handy to know.

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

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

[Django] #22869: broken link

2014-06-19 Thread Django

#22869: broken link
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 testing links from google, dont work

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

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

[django/django] 30d8b9: [1.7.x] Added feature for implied null (needed for...

2014-06-19 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 30d8b95139a1fa3070f3b112115e624ffcf8e555
  
https://github.com/django/django/commit/30d8b95139a1fa3070f3b112115e624ffcf8e555
  Author: Tim Graham 
  Date:   2014-06-19 (Thu, 19 Jun 2014)

  Changed paths:
M django/db/backends/__init__.py
M django/db/backends/schema.py

  Log Message:
  ---
  [1.7.x] Added feature for implied null (needed for Firebird backend)

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

Re: [Django] #13711: Very long field names on models cause problems

2014-06-19 Thread Django

#13711: Very long field names on models cause problems
-+-
 Reporter:  russellm |Owner:
 Type:  Bug  |  anubhav9042
Component:  Database layer   |   Status:  closed
  (models, ORM)  |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

 * cc: shai (added)
 * has_patch:  1 => 0
 * severity:  Normal => Release blocker
 * stage:  Ready for checkin => Accepted


Comment:

 Reopening as these changes prevent the Oracle tests from running:
 {{{
 ERRORS:
 backends.VeryLongModelNameZZ:
 (models.E018) Autogenerated column name too long for field
 "charfield_is_quite_long_zzz". Maximum
 length is "30" for database "default".
 HINT: Set the column name manually using 'db_column'.
 backends.VeryLongModelNameZZ:
 (models.E018) Autogenerated column name too long for field
 "primary_key_is_quite_long_z". Maximum
 length is "30" for database "default".
 HINT: Set the column name manually using 'db_column'.
 backends.VeryLongModelNameZZ:
 (models.E019) Autogenerated column name too long for M2M field
 "verylongmodelnamezz_id". Maximum
 length is "30" for database "default".
 HINT: Use 'through' to create a separate model for M2M and then
 set column_name using 'db_column'.
 sites_framework.CustomArticle: (models.E018) Autogenerated column name too
 long for field "places_this_article_should_appear_id". Maximum length is
 "30" for database "default".
 HINT: Set the column name manually using 'db_column'.
 }}}

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

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

Re: [Django] #22865: Testing framework: ValueError: Cannot create form field for 'user' yet, because its related model 'myauth.User' has not been loaded yet

2014-06-19 Thread Django

#22865: Testing framework: ValueError: Cannot create form field for 'user' yet,
because its related model 'myauth.User' has not been loaded yet
---+--
 Reporter:  jdufresne  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.6
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by renatooliveira):

 Repltying to [comment:8 aaugustin]

 > that Django 1.7 will warn that django.contrib.auth should be in
 INSTALLED_APPS, and that Django 1.9 will require it.

 If you see ticket:22866 you'll see that this behavior isn't only in
 {{{django.contrib.auth}}}

 However it's fixed in 1.7. Are there plans to fix it in Django 1.6?

 thanks!

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

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

Re: [Django] #21430: Raise Warning when unpickling Models and QuerySet from different version

2014-06-19 Thread Django

#21430: Raise Warning when unpickling Models and QuerySet from different version
-+-
 Reporter:  FunkyBob |Owner:
 Type:  New feature  |  anubhav9042
Component:  Database layer   |   Status:  closed
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"80f4487d17a0040e9be35e7ee6ac478bafe6504a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="80f4487d17a0040e9be35e7ee6ac478bafe6504a"
 Fixed #22867 -- Memoized django.utils.version.get_git_changeset().

 This improves pickling speed in prelease versions of Django; refs #21430.
 }}}

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

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

Re: [Django] #22867: Pickling models is slow in alpha versions

2014-06-19 Thread Django

#22867: Pickling models is slow in alpha versions
--+
 Reporter:  Suor  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Utilities |  Version:  master
 Severity:  Release blocker   |   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 Tim Graham ):

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


Comment:

 In [changeset:"80f4487d17a0040e9be35e7ee6ac478bafe6504a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="80f4487d17a0040e9be35e7ee6ac478bafe6504a"
 Fixed #22867 -- Memoized django.utils.version.get_git_changeset().

 This improves pickling speed in prelease versions of Django; refs #21430.
 }}}

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

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

[django/django] 80f448: Fixed #22867 -- Memoized django.utils.version.get_...

2014-06-19 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 80f4487d17a0040e9be35e7ee6ac478bafe6504a
  
https://github.com/django/django/commit/80f4487d17a0040e9be35e7ee6ac478bafe6504a
  Author: Alexander Schepanovski 
  Date:   2014-06-19 (Thu, 19 Jun 2014)

  Changed paths:
M django/utils/version.py

  Log Message:
  ---
  Fixed #22867 -- Memoized django.utils.version.get_git_changeset().

This improves pickling speed in prelease versions of Django; refs #21430.


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

Re: [Django] #14030: Use F() objects in aggregates(), annotates() and values()

2014-06-19 Thread Django

#14030: Use F() objects in aggregates(), annotates() and values()
-+-
 Reporter:  delfick  |Owner:  smeatonj
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  aggregate, annotate  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by manfre):

 * cc: mmanfre@… (added)
 * needs_better_patch:  0 => 1


Comment:

 Patch introduces a field alignment issue for resolve_columns. This is
 similar to #21126 and #21203.

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

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

[Django] #22868: Activated language not respected in post_save signal called during custom management command

2014-06-19 Thread Django

#22868: Activated language not respected in post_save signal called during 
custom
management command
---+
 Reporter:  stodge |  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
---+
 This one is a little tricky to explain. My problem seems to be this:

  * run custom management command
  * activate language from settings, which is "en-gb"
  * dynamically import module for a Django app and invoke custom bootstrap
 function
  * calling get_language() in bootstrap function returns "en-gb"
  * bootstrap function calls loaddata management command (using
 management.call_command)
  * data created in DB, which triggers a post_save signal
  * get_language() in post_save signal always returns "en-us"

 I don't know if the signal is invoked in a separate thread but I would
 expect get_language to return the newly activated language when called in
 a post_save signal. Or am I missing something? 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/049.ebb4cfadcaaf2de265fd32b8965acca1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #16335: Cannot iterate defaultdict in template

2014-06-19 Thread Django

#16335: Cannot iterate defaultdict in template
-+-
 Reporter:  jacob.ninja.dev@…|Owner:
 Type:  Bug  |  bluejeansummer
Component:  Documentation|   Status:  new
 Severity:  Normal   |  Version:  1.3
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  1|  Needs documentation:  0
 |  Patch needs improvement:  1
 |UI/UX:  0
-+-
Changes (by anonymous):

 * status:  closed => new


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

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

Re: [Django] #14932: Tests failing with SQLite3 on Linux systems; Sites object causing failures.

2014-06-19 Thread Django

#14932: Tests failing with SQLite3 on Linux systems; Sites object causing 
failures.
-+-
 Reporter:  bart.ciszk@… |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Uncategorized|  Version:  1.2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  sqlite3 app-loading  | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 It isn't clear which conditions triggered this bug, but it cannot happen
 anymore in Django 1.7+, thanks to the app-loading refactor. Now it's
 explicitly forbidden to import models in `__init__.py` at the root of an
 application.

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

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

Re: [Django] #22865: Testing framework: ValueError: Cannot create form field for 'user' yet, because its related model 'myauth.User' has not been loaded yet

2014-06-19 Thread Django

#22865: Testing framework: ValueError: Cannot create form field for 'user' yet,
because its related model 'myauth.User' has not been loaded yet
---+--
 Reporter:  jdufresne  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.6
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by anonymous):

 Replying to [comment:6 timo]:
 > I suspect this has been resolved the app loading refactor in 1.7, can
 you test there?

 Confirmed. Fixed for me with 1.7. Thanks.

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

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

Re: [Django] #14932: Tests failing with SQLite3 on Linux systems; Sites object causing failures.

2014-06-19 Thread Django

#14932: Tests failing with SQLite3 on Linux systems; Sites object causing 
failures.
---+--
 Reporter:  bart.ciszk@…   |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.2
 Severity:  Normal |   Resolution:
 Keywords:  sqlite3| Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by anonymous):

 * status:  closed => new
 * severity:   => Normal
 * resolution:  worksforme =>
 * easy:   => 0
 * ui_ux:   => 0
 * type:   => Uncategorized


Comment:

 Just happened to me - reproducing:
 use a model import in __ini__ of an app

 from configuration.models import myModel

 run the testing suite with sqlite db


 get:

 django.db.utils.OperationalError: no such table: configuration_myModel

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

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

Re: [Django] #22812: Reformat and restructure lookup API documentation

2014-06-19 Thread Django

#22812: Reformat and restructure lookup API documentation
-+-
 Reporter:  jorgecarleitao   |Owner:
 Type:   |  jorgecarleitao
  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:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timo):

 * needs_better_patch:  0 => 1


Comment:

 I think it would be better not to move the built-in lookups for the reason
 you mentioned.

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

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

Re: [Django] #22835: Deprecate NoArgsCommand

2014-06-19 Thread Django

#22835: Deprecate NoArgsCommand
-+-
 Reporter:  claudep  |Owner:  maxocub
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Core (Management |   Resolution:  fixed
  commands)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by maxocub):

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

Re: [Django] #22867: Pickling models is slow in alpha versions

2014-06-19 Thread Django

#22867: Pickling models is slow in alpha versions
--+
 Reporter:  Suor  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Utilities |  Version:  master
 Severity:  Release blocker   |   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+

Comment (by anonymous):

 Moved `@lru_cache()` to `get_git_changeset()`.

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

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

[django/django] 999615: Fixed #22835 -- Deprecated NoArgsCommand.

2014-06-19 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 9996158db467f9bef8243fcc36dc3602570e3613
  
https://github.com/django/django/commit/9996158db467f9bef8243fcc36dc3602570e3613
  Author: Maxime Turcotte 
  Date:   2014-06-19 (Thu, 19 Jun 2014)

  Changed paths:
M django/contrib/sessions/management/commands/clearsessions.py
M django/contrib/staticfiles/management/commands/collectstatic.py
M django/core/management/base.py
M django/core/management/commands/diffsettings.py
M django/core/management/commands/flush.py
M django/core/management/commands/inspectdb.py
M django/core/management/commands/makemessages.py
M django/core/management/commands/shell.py
M django/core/management/commands/sqlflush.py
M django/core/management/commands/syncdb.py
M django/core/management/commands/validate.py
M docs/howto/custom-management-commands.txt
M docs/internals/deprecation.txt
M docs/releases/1.8.txt
M tests/admin_scripts/complex_app/management/commands/duplicate.py
M tests/admin_scripts/management/commands/color_command.py
M tests/admin_scripts/management/commands/noargs_command.py
M tests/admin_scripts/management/commands/validation_command.py
M tests/admin_scripts/simple_app/management/commands/duplicate.py
M tests/admin_scripts/tests.py

  Log Message:
  ---
  Fixed #22835 -- Deprecated NoArgsCommand.


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

Re: [Django] #22835: Deprecate NoArgsCommand

2014-06-19 Thread Django

#22835: Deprecate NoArgsCommand
-+-
 Reporter:  claudep  |Owner:  maxocub
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Core (Management |   Resolution:  fixed
  commands)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"9996158db467f9bef8243fcc36dc3602570e3613"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9996158db467f9bef8243fcc36dc3602570e3613"
 Fixed #22835 -- Deprecated NoArgsCommand.
 }}}

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

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

Re: [Django] #22867: Pickling models is slow in alpha versions

2014-06-19 Thread Django

#22867: Pickling models is slow in alpha versions
--+
 Reporter:  Suor  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Utilities |  Version:  master
 Severity:  Release blocker   |   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 loic84):

 * cc: loic84 (added)
 * needs_better_patch:  0 => 1
 * severity:  Normal => Release blocker
 * stage:  Unreviewed => Accepted


Comment:

 +1 although I'd only wrap `get_git_changeset` with `lru_cache`.

 Marking as a release blocker for 1.8 since this is a regression from
 #21430.

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

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

Re: [Django] #22865: Testing framework: ValueError: Cannot create form field for 'user' yet, because its related model 'myauth.User' has not been loaded yet

2014-06-19 Thread Django

#22865: Testing framework: ValueError: Cannot create form field for 'user' yet,
because its related model 'myauth.User' has not been loaded yet
---+--
 Reporter:  jdufresne  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.6
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timo):

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

Re: [Django] #22867: Pickling models is slow in alpha versions

2014-06-19 Thread Django

#22867: Pickling models is slow in alpha versions
-+-
 Reporter:  Suor |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Utilities|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Suor):

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


Comment:

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

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

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

[Django] #22867: Pickling models is slow in alpha versions

2014-06-19 Thread Django

#22867: Pickling models is slow in alpha versions
--+
 Reporter:  Suor  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Utilities |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  1 |  UI/UX:  0
--+
 When pickling Django models in alpha version `get_version()` creates a git
 subprocess, which is very slow. I suggest memoizing `get_version()`.

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

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

Re: [Django] #22756: Technical 404 could say which view was run, if any.

2014-06-19 Thread Django

#22756: Technical 404 could say which view was run, if any.
-+-
 Reporter:  Keryn Knight |Owner:  jooyous
   |   Status:  assigned
 Type:  New feature  |  Version:  master
Component:  Core (URLs)  |   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 jooyous):

 * has_patch:  0 => 1


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

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

Re: [Django] #22865: Testing framework: ValueError: Cannot create form field for 'user' yet, because its related model 'myauth.User' has not been loaded yet

2014-06-19 Thread Django

#22865: Testing framework: ValueError: Cannot create form field for 'user' yet,
because its related model 'myauth.User' has not been loaded yet
---+--
 Reporter:  jdufresne  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by aaugustin):

 I can confirm that app-loading is the fix, that Django 1.7 will warn that
 django.contrib.auth should be in INSTALLED_APPS, and that Django 1.9 will
 require 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/067.419a4c96fd1ea79bc6f6543371fe12ab%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

75 matches

Mail list logo