[Django] #23542: Add ability to disable migrations

[Django]

#23542: Add ability to disable migrations
---+
 Reporter:  yuriiz |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.7
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Django 1.7 introduces migrations which are described at:
 https://docs.djangoproject.com/en/1.7/topics/migrations/

 Unfortunately this step is now mandatory which restricts Django 1.7 usage.
 (Otherwise the one get
 "CommandError: App 'sessions' has migrations. Only the sqlmigrate and
 sqlflush commands can be used when an app has migrations." on manage.py
 test immediately).

 There are great number of projects that are established enough to have DB
 schema unmodified for long time already but would benefit from Django 1.7
 securiry/bug fixes. Some projects have third-party migration solutions
 (South is not the only one in the world), some of them could be even non-
 Python. These projects can not upgrade Django from now either or forced to
 make dummy migrations.

 It would be great if Django had settings to disable new Django's built-in
 migrations completely. Like
 ENABLE_MIGRATIONS = default True and False would fallback syncdb to old
 create-table-if-not-exists behaviour and manage.py test could be still
 used for testing applications with no Django migrations created.

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

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

Re: [Django] #17638: Link up topic guides with API reference

[Django]

#17638: Link up topic guides with API reference
--+
 Reporter:  oinopion  |Owner:  duane9
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by duane9):

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

Re: [Django] #23541: RunSQL Bug Django 1.7

[Django]

#23541: RunSQL Bug Django 1.7
-+-
 Reporter:  abhillman|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Migrations   |  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  migrations runsql| Triage Stage:
  postgresql |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by abhillman):

 Okay. I looked into this a bit more. I seemed to be able to resolve my
 issue by escaping the '%' character (i.e. convert all instances of '%%' to
 '%'). Inspecting the stack trace, I am not entirely clear on why this is
 happening. Perhaps this is the correct behavior on django's behalf. Any
 enlightenment on this issue would be much appreciated. In addition, I
 wonder if some warning message or other error message might be appropriate
 or helpful in this sort of situation.

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

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

Re: [Django] #23541: RunSQL Bug Django 1.7

[Django]

#23541: RunSQL Bug Django 1.7
-+-
 Reporter:  abhillman|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Migrations   |  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  migrations runsql| Triage Stage:
  postgresql |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by abhillman:

Old description:

> Django migrations are wonderful, but I believe I have found a bug. The
> essence of what I am trying to do here: rename all tables starting with
> the name "hello" (i.e. hello_1, hello2_, hello_3, ...) to start with the
> name "goodbye (goodbye_1, goodbye_2, goodbye_3, ...), which could be very
> helpful when renaming an application.
>
> Here's how to reproduce (there is probably a more minimal case):
>
> 1. Install this function at a shell for PostgreSQL (very handy for
>
> {{{
> CREATE FUNCTION exec(text) returns text language plpgsql volatile
>   AS $f$
> BEGIN
>   EXECUTE $1;
>   RETURN $1;
> END;
> $f$;
> }}}
>
> source: http://wiki.postgresql.org/wiki/Dynamic_DDL
>
> 2. Write a RunSQL operation to help rename some tables
>
> {{{
> class Migration(migrations.Migration):
> ...
> operations = [
> migrations.RunPython(
> code=x
> ),
> migrations.RunSQL(
> sql="""select exec(format('alter table %I rename to %I',
> tablename, regexp_replace(tablename, '^hello, 'goodbye'))) from pg_tables
> where tablename like 'hello%';"""
> ),
> ]
> ...
> }}}
>
> 3. Run the migration. I got this error:
>
> {{{
> Traceback (most recent call last):
>   File "./manage.py", line 10, in 
> execute_from_command_line(sys.argv)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/core/management/__init__.py", line 385, in
> execute_from_command_line
> utility.execute()
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/core/management/__init__.py", line 377, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/core/management/base.py", line 288, in run_from_argv
> self.execute(*args, **options.__dict__)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/core/management/base.py", line 338, in execute
> output = self.handle(*args, **options)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/core/management/commands/migrate.py", line 160, in handle
> executor.migrate(targets, plan, fake=options.get("fake", False))
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/db/migrations/executor.py", line 63, in migrate
> self.apply_migration(migration, fake=fake)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/db/migrations/executor.py", line 97, in apply_migration
> migration.apply(project_state, schema_editor)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/db/migrations/migration.py", line 107, in apply
> operation.database_forwards(self.app_label, schema_editor,
> project_state, new_state)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/db/migrations/operations/special.py", line 69, in
> database_forwards
> schema_editor.execute(statement)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/db/backends/schema.py", line 98, in execute
> cursor.execute(sql, params)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/db/backends/utils.py", line 81, in execute
> return super(CursorDebugWrapper, self).execute(sql, params)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/db/backends/utils.py", line 65, in execute
> return self.cursor.execute(sql, params)
> IndexError: list index out of range
> }}}
>
> Not sure what's going on here. Could it be the custom PGSQL function?

New description:

 Django migrations are wonderful, but I believe I have found a bug. The
 essence of what I am trying to do here: rename all tables starting with
 the name "hello" (i.e. hello_1, hello2_, hello_3, ...) to start with the
 name "goodbye (goodbye_1, goodbye_2, goodbye_3, ...), which could be very
 helpful when renaming an application.

 Here's how to reproduce (there is probably a more minimal case):

 1. Install this function at a shell for PostgreSQL (very handy for

 {{{
 CREATE FUNCTION exec(text) returns text language plpgsql volatile
   AS 

Re: [Django] #23541: RunSQL Bug Django 1.7

[Django]

#23541: RunSQL Bug Django 1.7
-+-
 Reporter:  abhillman|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Migrations   |  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  migrations runsql| Triage Stage:
  postgresql |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by abhillman:

Old description:

> Django migrations are wonderful, but I have found a bug. Here's how to
> reproduce (there is probably a more minimal case):
>
> 1. Install this function at a shell for PostgreSQL
>
> {{{
> CREATE FUNCTION exec(text) returns text language plpgsql volatile
>   AS $f$
> BEGIN
>   EXECUTE $1;
>   RETURN $1;
> END;
> $f$;
> }}}
>
> source: http://wiki.postgresql.org/wiki/Dynamic_DDL
>
> 2. Write a RunSQL operation to help rename some tables
>
> {{{
> class Migration(migrations.Migration):
> ...
> operations = [
> migrations.RunPython(
> code=x
> ),
> migrations.RunSQL(
> sql="""select exec(format('alter table %I rename to %I',
> tablename, regexp_replace(tablename, '^hello, 'goodbye'))) from pg_tables
> where tablename like 'hello%';"""
> ),
> ]
> ...
> }}}
>
> 3. Run the migration. I got this error:
>
> {{{
> Traceback (most recent call last):
>   File "./manage.py", line 10, in 
> execute_from_command_line(sys.argv)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/core/management/__init__.py", line 385, in
> execute_from_command_line
> utility.execute()
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/core/management/__init__.py", line 377, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/core/management/base.py", line 288, in run_from_argv
> self.execute(*args, **options.__dict__)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/core/management/base.py", line 338, in execute
> output = self.handle(*args, **options)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/core/management/commands/migrate.py", line 160, in handle
> executor.migrate(targets, plan, fake=options.get("fake", False))
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/db/migrations/executor.py", line 63, in migrate
> self.apply_migration(migration, fake=fake)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/db/migrations/executor.py", line 97, in apply_migration
> migration.apply(project_state, schema_editor)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/db/migrations/migration.py", line 107, in apply
> operation.database_forwards(self.app_label, schema_editor,
> project_state, new_state)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/db/migrations/operations/special.py", line 69, in
> database_forwards
> schema_editor.execute(statement)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/db/backends/schema.py", line 98, in execute
> cursor.execute(sql, params)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/db/backends/utils.py", line 81, in execute
> return super(CursorDebugWrapper, self).execute(sql, params)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/db/backends/utils.py", line 65, in execute
> return self.cursor.execute(sql, params)
> IndexError: list index out of range
> }}}
>
> Not sure what's going on here. Could it be the custom PGSQL function?

New description:

 Django migrations are wonderful, but I believe I have found a bug. The
 essence of what I am trying to do here: rename all tables starting with
 the name "hello" (i.e. hello_1, hello2_, hello_3, ...) to start with the
 name "goodbye (goodbye_1, goodbye_2, goodbye_3, ...), which could be very
 helpful when renaming an application.

 Here's how to reproduce (there is probably a more minimal case):

 1. Install this function at a shell for PostgreSQL (very handy for

 {{{
 CREATE FUNCTION exec(text) returns text language plpgsql volatile
   AS $f$
 BEGIN
   EXECUTE $1;
   RETURN $1;
 END;
 $f$;
 }}}

 source: http://wiki.postgresql.org/wiki/Dynamic_DDL

 2. Write a RunSQL operation to help rename some tables

 {{{
 class Migration(migrations.Migration):
 ...
 operations = [
 migrations.RunPython(
   

Re: [Django] #23540: RunSQL Bug Django 1.7

[Django]

#23540: RunSQL Bug Django 1.7
-+-
 Reporter:  abhillman|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Migrations   |  Version:  1.7
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  migrations runsql| Triage Stage:
  postgresql |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by abhillman):

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


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

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

Re: [Django] #23541: RunSQL Bug Django 1.7

[Django]

#23541: RunSQL Bug Django 1.7
-+-
 Reporter:  abhillman|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Migrations   |  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  migrations runsql| Triage Stage:
  postgresql |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by abhillman:

Old description:

> Django migrations are wonderful, but I have found a bug. Here's how to
> reproduce (there is probably a more minimal case):
>
> 1. Install this function at a shell for PostgreSQL
>
> {{{CREATE FUNCTION exec(text) returns text language plpgsql volatile
>   AS $f$
> BEGIN
>   EXECUTE $1;
>   RETURN $1;
> END;
> $f$;}}}
>
> source: http://wiki.postgresql.org/wiki/Dynamic_DDL
>
> 2. Write a RunSQL operation to help rename some tables
>
> {{{class Migration(migrations.Migration):
> ...
> operations = [
> migrations.RunPython(
> code=x
> ),
> migrations.RunSQL(
> sql="""select exec(format('alter table %I rename to %I',
> tablename, regexp_replace(tablename, '^hello, 'goodbye'))) from pg_tables
> where tablename like 'hello%';"""
> ),
> ]
> ...}}}
>
> 3. Run the migration. I got this error:
>
> {{{Traceback (most recent call last):
>   File "./manage.py", line 10, in 
> execute_from_command_line(sys.argv)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/core/management/__init__.py", line 385, in
> execute_from_command_line
> utility.execute()
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/core/management/__init__.py", line 377, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/core/management/base.py", line 288, in run_from_argv
> self.execute(*args, **options.__dict__)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/core/management/base.py", line 338, in execute
> output = self.handle(*args, **options)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/core/management/commands/migrate.py", line 160, in handle
> executor.migrate(targets, plan, fake=options.get("fake", False))
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/db/migrations/executor.py", line 63, in migrate
> self.apply_migration(migration, fake=fake)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/db/migrations/executor.py", line 97, in apply_migration
> migration.apply(project_state, schema_editor)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/db/migrations/migration.py", line 107, in apply
> operation.database_forwards(self.app_label, schema_editor,
> project_state, new_state)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/db/migrations/operations/special.py", line 69, in
> database_forwards
> schema_editor.execute(statement)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/db/backends/schema.py", line 98, in execute
> cursor.execute(sql, params)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/db/backends/utils.py", line 81, in execute
> return super(CursorDebugWrapper, self).execute(sql, params)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/db/backends/utils.py", line 65, in execute
> return self.cursor.execute(sql, params)
> IndexError: list index out of range}}}
>
> Not sure what's going on here. Could it be the custom PGSQL function?

New description:

 Django migrations are wonderful, but I have found a bug. Here's how to
 reproduce (there is probably a more minimal case):

 1. Install this function at a shell for PostgreSQL

 {{{
 CREATE FUNCTION exec(text) returns text language plpgsql volatile
   AS $f$
 BEGIN
   EXECUTE $1;
   RETURN $1;
 END;
 $f$;
 }}}

 source: http://wiki.postgresql.org/wiki/Dynamic_DDL

 2. Write a RunSQL operation to help rename some tables

 {{{
 class Migration(migrations.Migration):
 ...
 operations = [
 migrations.RunPython(
 code=x
 ),
 migrations.RunSQL(
 sql="""select exec(format('alter table %I rename to %I',
 tablename, regexp_replace(tablename, '^hello, 'goodbye'))) from pg_tables
 where tablename like 'hello%';"""
 ),
 ]
 ...
 }}}

 3. Run the migration. I got this error:

 {{{
 

Re: [Django] #23541: RunSQL Bug Django 1.7

[Django]

#23541: RunSQL Bug Django 1.7
-+-
 Reporter:  abhillman|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Migrations   |  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  migrations runsql| Triage Stage:
  postgresql |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by abhillman):

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


Old description:

> Django migrations are wonderful, but I have found a bug. Here's how to
> reproduce (there is probably a more minimal case):
>
> 1. Install this function at a shell for PostgreSQL
>
> ```CREATE FUNCTION exec(text) returns text language plpgsql volatile
>   AS $f$
> BEGIN
>   EXECUTE $1;
>   RETURN $1;
> END;
> $f$;```
>
> source: http://wiki.postgresql.org/wiki/Dynamic_DDL
>
> 2. Write a RunSQL operation to help rename some tables
>
> ```class Migration(migrations.Migration):
> ...
> operations = [
> migrations.RunPython(
> code=x
> ),
> migrations.RunSQL(
> sql="""select exec(format('alter table %I rename to %I',
> tablename, regexp_replace(tablename, '^hello, 'goodbye'))) from pg_tables
> where tablename like 'hello%';"""
> ),
> ]```
>
> 3. Run the migration. I got this error:
>
> ```Traceback (most recent call last):
>   File "./manage.py", line 10, in 
> execute_from_command_line(sys.argv)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/core/management/__init__.py", line 385, in
> execute_from_command_line
> utility.execute()
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/core/management/__init__.py", line 377, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/core/management/base.py", line 288, in run_from_argv
> self.execute(*args, **options.__dict__)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/core/management/base.py", line 338, in execute
> output = self.handle(*args, **options)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/core/management/commands/migrate.py", line 160, in handle
> executor.migrate(targets, plan, fake=options.get("fake", False))
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/db/migrations/executor.py", line 63, in migrate
> self.apply_migration(migration, fake=fake)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/db/migrations/executor.py", line 97, in apply_migration
> migration.apply(project_state, schema_editor)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/db/migrations/migration.py", line 107, in apply
> operation.database_forwards(self.app_label, schema_editor,
> project_state, new_state)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/db/migrations/operations/special.py", line 69, in
> database_forwards
> schema_editor.execute(statement)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/db/backends/schema.py", line 98, in execute
> cursor.execute(sql, params)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/db/backends/utils.py", line 81, in execute
> return super(CursorDebugWrapper, self).execute(sql, params)
>   File "/Users/abhillman/stable_env/lib/python2.7/site-
> packages/django/db/backends/utils.py", line 65, in execute
> return self.cursor.execute(sql, params)
> IndexError: list index out of range```
>
> Not sure what's going on here. Could it be the custom function?

New description:

 Django migrations are wonderful, but I have found a bug. Here's how to
 reproduce (there is probably a more minimal case):

 1. Install this function at a shell for PostgreSQL

 {{{CREATE FUNCTION exec(text) returns text language plpgsql volatile
   AS $f$
 BEGIN
   EXECUTE $1;
   RETURN $1;
 END;
 $f$;}}}

 source: http://wiki.postgresql.org/wiki/Dynamic_DDL

 2. Write a RunSQL operation to help rename some tables

 {{{class Migration(migrations.Migration):
 ...
 operations = [
 migrations.RunPython(
 code=x
 ),
 migrations.RunSQL(
 sql="""select exec(format('alter table %I rename to %I',
 tablename, regexp_replace(tablename, '^hello, 'goodbye'))) from pg_tables
 where tablename like 'hello%';"""
 ),
 ]
 ...}}}

 3. 

[Django] #23541: RunSQL Bug Django 1.7

[Django]

#23541: RunSQL Bug Django 1.7
---+--
 Reporter:  abhillman  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Migrations |Version:  1.7
 Severity:  Normal |   Keywords:  migrations runsql postgresql
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+--
 Django migrations are wonderful, but I have found a bug. Here's how to
 reproduce (there is probably a more minimal case):

 1. Install this function at a shell for PostgreSQL

 ```CREATE FUNCTION exec(text) returns text language plpgsql volatile
   AS $f$
 BEGIN
   EXECUTE $1;
   RETURN $1;
 END;
 $f$;```

 source: http://wiki.postgresql.org/wiki/Dynamic_DDL

 2. Write a RunSQL operation to help rename some tables

 ```class Migration(migrations.Migration):
 ...
 operations = [
 migrations.RunPython(
 code=x
 ),
 migrations.RunSQL(
 sql="""select exec(format('alter table %I rename to %I',
 tablename, regexp_replace(tablename, '^hello, 'goodbye'))) from pg_tables
 where tablename like 'hello%';"""
 ),
 ]```

 3. Run the migration. I got this error:

 ```Traceback (most recent call last):
   File "./manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/Users/abhillman/stable_env/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 385, in
 execute_from_command_line
 utility.execute()
   File "/Users/abhillman/stable_env/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 377, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/Users/abhillman/stable_env/lib/python2.7/site-
 packages/django/core/management/base.py", line 288, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/Users/abhillman/stable_env/lib/python2.7/site-
 packages/django/core/management/base.py", line 338, in execute
 output = self.handle(*args, **options)
   File "/Users/abhillman/stable_env/lib/python2.7/site-
 packages/django/core/management/commands/migrate.py", line 160, in handle
 executor.migrate(targets, plan, fake=options.get("fake", False))
   File "/Users/abhillman/stable_env/lib/python2.7/site-
 packages/django/db/migrations/executor.py", line 63, in migrate
 self.apply_migration(migration, fake=fake)
   File "/Users/abhillman/stable_env/lib/python2.7/site-
 packages/django/db/migrations/executor.py", line 97, in apply_migration
 migration.apply(project_state, schema_editor)
   File "/Users/abhillman/stable_env/lib/python2.7/site-
 packages/django/db/migrations/migration.py", line 107, in apply
 operation.database_forwards(self.app_label, schema_editor,
 project_state, new_state)
   File "/Users/abhillman/stable_env/lib/python2.7/site-
 packages/django/db/migrations/operations/special.py", line 69, in
 database_forwards
 schema_editor.execute(statement)
   File "/Users/abhillman/stable_env/lib/python2.7/site-
 packages/django/db/backends/schema.py", line 98, in execute
 cursor.execute(sql, params)
   File "/Users/abhillman/stable_env/lib/python2.7/site-
 packages/django/db/backends/utils.py", line 81, in execute
 return super(CursorDebugWrapper, self).execute(sql, params)
   File "/Users/abhillman/stable_env/lib/python2.7/site-
 packages/django/db/backends/utils.py", line 65, in execute
 return self.cursor.execute(sql, params)
 IndexError: list index out of range```

 Not sure what's going on here. Could it be the custom function?

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

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

[Django] #23540: RunSQL Bug Django 1.7

[Django]

#23540: RunSQL Bug Django 1.7
---+--
 Reporter:  abhillman  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Migrations |Version:  1.7
 Severity:  Normal |   Keywords:  migrations runsql postgresql
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+--
 Django migrations are wonderful, but I have found a bug. Here's how to
 reproduce (there is probably a more minimal case):

 1. Install this function at a shell for PostgreSQL

 ```CREATE FUNCTION exec(text) returns text language plpgsql volatile
   AS $f$
 BEGIN
   EXECUTE $1;
   RETURN $1;
 END;
 $f$;```

 source: http://wiki.postgresql.org/wiki/Dynamic_DDL

 2. Write a RunSQL operation to help rename some tables

 ```class Migration(migrations.Migration):
 ...
 operations = [
 migrations.RunPython(
 code=x
 ),
 migrations.RunSQL(
 sql="""select exec(format('alter table %I rename to %I',
 tablename, regexp_replace(tablename, '^hello, 'goodbye'))) from pg_tables
 where tablename like 'hello%';"""
 ),
 ]```

 3. Run the migration. I got this error:

 ```Traceback (most recent call last):
   File "./manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/Users/abhillman/stable_env/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 385, in
 execute_from_command_line
 utility.execute()
   File "/Users/abhillman/stable_env/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 377, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/Users/abhillman/stable_env/lib/python2.7/site-
 packages/django/core/management/base.py", line 288, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/Users/abhillman/stable_env/lib/python2.7/site-
 packages/django/core/management/base.py", line 338, in execute
 output = self.handle(*args, **options)
   File "/Users/abhillman/stable_env/lib/python2.7/site-
 packages/django/core/management/commands/migrate.py", line 160, in handle
 executor.migrate(targets, plan, fake=options.get("fake", False))
   File "/Users/abhillman/stable_env/lib/python2.7/site-
 packages/django/db/migrations/executor.py", line 63, in migrate
 self.apply_migration(migration, fake=fake)
   File "/Users/abhillman/stable_env/lib/python2.7/site-
 packages/django/db/migrations/executor.py", line 97, in apply_migration
 migration.apply(project_state, schema_editor)
   File "/Users/abhillman/stable_env/lib/python2.7/site-
 packages/django/db/migrations/migration.py", line 107, in apply
 operation.database_forwards(self.app_label, schema_editor,
 project_state, new_state)
   File "/Users/abhillman/stable_env/lib/python2.7/site-
 packages/django/db/migrations/operations/special.py", line 69, in
 database_forwards
 schema_editor.execute(statement)
   File "/Users/abhillman/stable_env/lib/python2.7/site-
 packages/django/db/backends/schema.py", line 98, in execute
 cursor.execute(sql, params)
   File "/Users/abhillman/stable_env/lib/python2.7/site-
 packages/django/db/backends/utils.py", line 81, in execute
 return super(CursorDebugWrapper, self).execute(sql, params)
   File "/Users/abhillman/stable_env/lib/python2.7/site-
 packages/django/db/backends/utils.py", line 65, in execute
 return self.cursor.execute(sql, params)
 IndexError: list index out of range```

 Not sure what's going on here. Could it be the custom function?

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

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

Re: [Django] #23539: GenericInlineModelAdmin doesn't utilize get_extra (and get_max_num/get_min_num)

[Django]

#23539: GenericInlineModelAdmin doesn't utilize get_extra (and
get_max_num/get_min_num)
--+
 Reporter:  bigjust   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.contenttypes  |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by charettes):

 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #23523: pyinotify yelling no space available

[Django]

#23523: pyinotify yelling no space available
---+--
 Reporter:  MattBlack85|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.7
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by MattBlack85):

 yes, I can increase to a bigger number. But this is not a real solution to
 the problem. I just want to understand if this is a django problem or not.
 If I try to run into a virtual env I don't get the error

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

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

Re: [Django] #23539: GenericInlineModelAdmin doesn't utilize get_extra (and get_max_num/get_min_num)

[Django]

#23539: GenericInlineModelAdmin doesn't utilize get_extra (and
get_max_num/get_min_num)
-+-
 Reporter:  bigjust  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:   |  Version:  1.7
  contrib.contenttypes   |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by bigjust):

 * has_patch:  0 => 1


Old description:

> the helper functions get_extra, get_max_num, and get_min_num were
> introduced in 1.6 as a way of calculating extra, max_num, min_num per
> request.  The GenericInlineModelAdmin has continued using the old
> self.extra, max_num, and min_num values.

New description:

 the helper functions get_extra, get_max_num, and get_min_num were
 introduced in 1.6 as a way of calculating extra, max_num, min_num per
 request.  The GenericInlineModelAdmin has continued using the old
 self.extra, max_num, and min_num values.

--

Comment:

 PR submitted https://github.com/django/django/pull/3263

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

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

Re: [Django] #23539: GenericInlineModelAdmin doesn't utilize get_extra (and get_max_num/get_min_num)

[Django]

#23539: GenericInlineModelAdmin doesn't utilize get_extra (and
get_max_num/get_min_num)
-+-
 Reporter:  bigjust  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:   |  Version:  1.7
  contrib.contenttypes   |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by bigjust):

 * cc: bigjust@… (added)
 * needs_better_patch:   => 0
 * component:  Uncategorized => contrib.contenttypes
 * needs_tests:   => 0
 * needs_docs:   => 0


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

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

[Django] #23539: GenericInlineModelAdmin doesn't utilize get_extra (and get_max_num/get_min_num)

[Django]

#23539: GenericInlineModelAdmin doesn't utilize get_extra (and
get_max_num/get_min_num)
---+
 Reporter:  bigjust|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.7
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 the helper functions get_extra, get_max_num, and get_min_num were
 introduced in 1.6 as a way of calculating extra, max_num, min_num per
 request.  The GenericInlineModelAdmin has continued using the old
 self.extra, max_num, and min_num values.

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

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

[django/django] 7fe554: Merged one_to_one_regress into the one_to_one test...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 7fe554b2a3d72d0142e5c9e97efbd0a672c2d790
  
https://github.com/django/django/commit/7fe554b2a3d72d0142e5c9e97efbd0a672c2d790
  Author: Loic Bistuer 
  Date:   2014-09-23 (Tue, 23 Sep 2014)

  Changed paths:
M tests/one_to_one/models.py
M tests/one_to_one/tests.py
R tests/one_to_one_regress/__init__.py
R tests/one_to_one_regress/models.py
R tests/one_to_one_regress/tests.py

  Log Message:
  ---
  Merged one_to_one_regress into the one_to_one test package.


  Commit: d42a45de407c7d7962aa7a2dd79f7d32b423e600
  
https://github.com/django/django/commit/d42a45de407c7d7962aa7a2dd79f7d32b423e600
  Author: Loic Bistuer 
  Date:   2014-09-23 (Tue, 23 Sep 2014)

  Changed paths:
M tests/custom_columns/models.py
M tests/custom_columns/tests.py
R tests/custom_columns_regress/__init__.py
R tests/custom_columns_regress/models.py
R tests/custom_columns_regress/tests.py

  Log Message:
  ---
  Merged custom_columns_regress into the custom_columns test package.


  Commit: 0dab07e5da43f8965db24adc4363cec01944de4d
  
https://github.com/django/django/commit/0dab07e5da43f8965db24adc4363cec01944de4d
  Author: Loic Bistuer 
  Date:   2014-09-23 (Tue, 23 Sep 2014)

  Changed paths:
M tests/custom_managers/models.py
M tests/custom_managers/tests.py
R tests/custom_managers_regress/__init__.py
R tests/custom_managers_regress/models.py
R tests/custom_managers_regress/tests.py

  Log Message:
  ---
  Merged custom_managers_regress into the custom_managers test package.


Compare: https://github.com/django/django/compare/37b13033c61d...0dab07e5da43

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

[django/django] 37b130: Removed sudo from pip commands in docs.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 37b13033c61d24045b8182944c0964fffc8ff7d0
  
https://github.com/django/django/commit/37b13033c61d24045b8182944c0964fffc8ff7d0
  Author: Corey Farwell 
  Date:   2014-09-22 (Mon, 22 Sep 2014)

  Changed paths:
M docs/README
M docs/howto/deployment/wsgi/gunicorn.txt
M docs/howto/outputting-pdf.txt
M docs/internals/contributing/writing-documentation.txt
M docs/intro/whatsnext.txt
M docs/ref/contrib/gis/install/index.txt
M docs/ref/contrib/gis/install/spatialite.txt
M docs/topics/i18n/timezones.txt

  Log Message:
  ---
  Removed sudo from pip commands in docs.


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

[Django] #23538: MySQL GIS backend missing SchemaEditor

[Django]

#23538: MySQL GIS backend missing SchemaEditor
---+---
   Reporter:  timgraham|  Owner:  timgraham
   Type:  Bug  | Status:  new
  Component:  GIS  |Version:  1.7
   Severity:  Release blocker  |   Keywords:
   Triage Stage:  Accepted |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+---
 I think this results in a missing index for GIS fields on apps that have
 migrations.

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

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

Re: [Django] #23535: Clarify presence of default filter in tutorial 2

[Django]

#23535: Clarify presence of default filter in tutorial 2
--+
 Reporter:  velis74   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:  fixed
 Keywords:  tutorial, templates   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"1c1f418802503a78589171a540a4b795c5f53875"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1c1f418802503a78589171a540a4b795c5f53875"
 [1.7.x] Fixed #23535 -- Updated tutorial to account for default filter
 added in 5ea34f3f86.

 Backport of 24aa85cea9 from master
 }}}

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

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

[django/django] 1c1f41: [1.7.x] Fixed #23535 -- Updated tutorial to accoun...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 1c1f418802503a78589171a540a4b795c5f53875
  
https://github.com/django/django/commit/1c1f418802503a78589171a540a4b795c5f53875
  Author: velis74 
  Date:   2014-09-22 (Mon, 22 Sep 2014)

  Changed paths:
M docs/intro/tutorial02.txt

  Log Message:
  ---
  [1.7.x] Fixed #23535 -- Updated tutorial to account for default filter added 
in 5ea34f3f86.

Backport of 24aa85cea9 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/5420778be09f3_7bcd3ffb50bb92bc5635a%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 24aa85: Fixed #23535 -- Updated tutorial to account for de...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 24aa85cea9d741fcbc288f12f59e22f1d05f79d7
  
https://github.com/django/django/commit/24aa85cea9d741fcbc288f12f59e22f1d05f79d7
  Author: velis74 
  Date:   2014-09-22 (Mon, 22 Sep 2014)

  Changed paths:
M docs/intro/tutorial02.txt

  Log Message:
  ---
  Fixed #23535 -- Updated tutorial to account for default filter added in 
5ea34f3f86.


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

Re: [Django] #23535: Clarify presence of default filter in tutorial 2

[Django]

#23535: Clarify presence of default filter in tutorial 2
--+
 Reporter:  velis74   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:  fixed
 Keywords:  tutorial, templates   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"24aa85cea9d741fcbc288f12f59e22f1d05f79d7"]:
 {{{
 #!CommitTicketReference repository=""
 revision="24aa85cea9d741fcbc288f12f59e22f1d05f79d7"
 Fixed #23535 -- Updated tutorial to account for default filter added in
 5ea34f3f86.
 }}}

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

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

[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
---+
Changes (by tchaumeny):

 * cc: t.chaumeny@… (added)


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

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

Re: [Django] #23338: Warn when unique=True is set on ForeignKey

[Django]

#23338: Warn when unique=True is set on ForeignKey
--+
 Reporter:  funkybob  |Owner:  JLinden
 Type:  New feature   |   Status:  assigned
Component:  Core (System checks)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by diegoguimaraes):

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


Comment:

 New pull request with tests and updated documentation at
 https://github.com/django/django/pull/3262

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

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

Re: [Django] #23504: Oracle GIS test failures

[Django]

#23504: Oracle GIS test failures
---+-
 Reporter:  timgraham  |Owner:  timgraham
 Type:  Bug|   Status:  new
Component:  GIS|  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 claudep):

 For 1., I think we will not avoid using a specific value for Oracle.
 For 2., unless we understand what's happening, it should be marked as an
 expectedFailure on Oracle. Some Oracle lover will hopefully chime in and
 fix 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.23c275045024f800edeaac6fb76b57d1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23504: Oracle GIS test failures

[Django]

#23504: Oracle GIS test failures
---+-
 Reporter:  timgraham  |Owner:  timgraham
 Type:  Bug|   Status:  new
Component:  GIS|  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 timgraham):

 The remaining failures are:

 1. Claude suggested trying a zip with a smaller area, but there are still
 discrepancies between what Oracle and the other DBs calculate.

 {{{
 ==
 FAIL: test06_geography_area
 (django.contrib.gis.tests.geogapp.tests.GeographyTest)
 Testing that Area calculations work on geography columns.
 --
 Traceback (most recent call last):
   File "/home/tim/code/django/django/test/testcases.py", line 968, in
 skip_wrapper
 return test_func(*args, **kwargs)
   File "/home/tim/code/django/django/contrib/gis/tests/geogapp/tests.py",
 line 102, in test06_geography_area
 self.assertAlmostEqual(z.area.sq_m, ref_area, tol)
 AssertionError: 5439100.95415646 != 5439084.70637573 within 5 places
 }}}

 2. Can be made to pass with the diff the follows, but may more
 investigation and/or just skipped on Oracle.

 {{{
 ==
 FAIL: test_unionagg
 (django.contrib.gis.tests.geoapp.tests.GeoQuerySetTest)
 Testing the `unionagg` (aggregate union) GeoQuerySet method.
 --
 Traceback (most recent call last):
   File "/home/tim/code/django/django/test/testcases.py", line 968, in
 skip_wrapper
 return test_func(*args, **kwargs)
   File "/home/tim/code/django/django/contrib/gis/tests/geoapp/tests.py",
 line 751, in test_unionagg
 self.assertEqual(True, union1.equals_exact(u1, tol) or
 union2.equals_exact(u1, tol))
 AssertionError: True != False
 }}}

 {{{
 diff --git a/django/contrib/gis/tests/geoapp/tests.py
 b/django/contrib/gis/tests/geoapp/tests.py
 index f4699ae..306664b 100644
 --- a/django/contrib/gis/tests/geoapp/tests.py
 +++ b/django/contrib/gis/tests/geoapp/tests.py
 @@ -791,6 +791,8 @@ class GeoQuerySetTest(TestCase):
  # Houston, Dallas -- Ordering may differ depending on backend or
 GEOS version.
  union1 = fromstr('MULTIPOINT(-96.801611 32.782057,-95.363151
 29.763374)')
  union2 = fromstr('MULTIPOINT(-95.363151 29.763374,-96.801611
 32.782057)')
 +if oracle:
 +union1 = union2 = fromstr('POINT (-97.52115723
 34.46464178)')
  qs = City.objects.filter(point__within=tx)
  self.assertRaises(TypeError, qs.unionagg, 'name')
  # Using `field_name` keyword argument in one query and specifying
 an
 }}}

 3. Fixed in #23537.

 {{{
 ==
 FAIL: test_add_gis_field
 (django.contrib.gis.tests.gis_migrations.test_operations.OperationTests)
 --
 Traceback (most recent call last):
   File
 
"/home/tim/code/django/django/contrib/gis/tests/gis_migrations/test_operations.py",
 line 73, in test_add_gis_field
 2
 AssertionError: 0 != 2
 }}}

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

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

[django/django] 59d369: [1.6.x] Skipped some broken tests on Oracle GIS; r...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 59d369db7854b55f22ff75da92971dcd0ab4322f
  
https://github.com/django/django/commit/59d369db7854b55f22ff75da92971dcd0ab4322f
  Author: Tim Graham 
  Date:   2014-09-22 (Mon, 22 Sep 2014)

  Changed paths:
M django/contrib/gis/tests/geoapp/test_regress.py
M django/contrib/gis/tests/relatedapp/tests.py

  Log Message:
  ---
  [1.6.x] Skipped some broken tests on Oracle GIS; refs #23504.

Backport of 7fce7f51ef from master


  Commit: 8cee5875a65d6b736c3cbafa774abdc62336ed08
  
https://github.com/django/django/commit/8cee5875a65d6b736c3cbafa774abdc62336ed08
  Author: Tim Graham 
  Date:   2014-09-22 (Mon, 22 Sep 2014)

  Changed paths:
M django/contrib/gis/tests/layermap/tests.py

  Log Message:
  ---
  [1.6.x] Removed unnecessary order_by() from a GIS test that crashed Oracle.

Oracle cannot order_by() a TextField; refs #23504.

Backport of 7fc13178d6 from master


  Commit: 2376319ce089cb3d5484fc1d9861f81a80d6abc4
  
https://github.com/django/django/commit/2376319ce089cb3d5484fc1d9861f81a80d6abc4
  Author: Tim Graham 
  Date:   2014-09-22 (Mon, 22 Sep 2014)

  Changed paths:
M django/contrib/gis/tests/relatedapp/tests.py

  Log Message:
  ---
  [1.6.x] Skipped a broken GIS test on Oracle; refs #23504.

Backport of 828edc5ba9 from master


  Commit: dd7346ed1daf30ee37517057b58900bd10ba978b
  
https://github.com/django/django/commit/dd7346ed1daf30ee37517057b58900bd10ba978b
  Author: Tim Graham 
  Date:   2014-09-22 (Mon, 22 Sep 2014)

  Changed paths:
M django/contrib/gis/tests/geoapp/tests.py

  Log Message:
  ---
  [1.6.x] Made a GIS test work on Oracle.

Thanks Josh Smeaton and Claude Paroz for advice.

Backport of 7add30df01 from master


Compare: https://github.com/django/django/compare/a6c294a5a293...dd7346ed1daf

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

Re: [Django] #23504: Oracle GIS test failures

[Django]

#23504: Oracle GIS test failures
---+-
 Reporter:  timgraham  |Owner:  timgraham
 Type:  Bug|   Status:  new
Component:  GIS|  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by Tim Graham ):

 In [changeset:"59d369db7854b55f22ff75da92971dcd0ab4322f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="59d369db7854b55f22ff75da92971dcd0ab4322f"
 [1.6.x] Skipped some broken tests on Oracle GIS; refs #23504.

 Backport of 7fce7f51ef from master
 }}}

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

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

Re: [Django] #23504: Oracle GIS test failures

[Django]

#23504: Oracle GIS test failures
---+-
 Reporter:  timgraham  |Owner:  timgraham
 Type:  Bug|   Status:  new
Component:  GIS|  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by Tim Graham ):

 In [changeset:"2376319ce089cb3d5484fc1d9861f81a80d6abc4"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2376319ce089cb3d5484fc1d9861f81a80d6abc4"
 [1.6.x] Skipped a broken GIS test on Oracle; refs #23504.

 Backport of 828edc5ba9 from master
 }}}

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

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

Re: [Django] #23504: Oracle GIS test failures

[Django]

#23504: Oracle GIS test failures
---+-
 Reporter:  timgraham  |Owner:  timgraham
 Type:  Bug|   Status:  new
Component:  GIS|  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by Tim Graham ):

 In [changeset:"8cee5875a65d6b736c3cbafa774abdc62336ed08"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8cee5875a65d6b736c3cbafa774abdc62336ed08"
 [1.6.x] Removed unnecessary order_by() from a GIS test that crashed
 Oracle.

 Oracle cannot order_by() a TextField; refs #23504.

 Backport of 7fc13178d6 from master
 }}}

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

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

[Django] #23537: Oracle GIS backend missing SchemaEditor

[Django]

#23537: Oracle GIS backend missing SchemaEditor
---+
   Reporter:  timgraham|  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  GIS  |Version:  1.7
   Severity:  Release blocker  |   Keywords:
   Triage Stage:  Accepted |  Has patch:  1
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 I think this results in missing indexes and metadata for GIS fields.

 There is one test failure that will be fixed by this:

 {{{
 ==
 FAIL: test_add_gis_field
 (django.contrib.gis.tests.gis_migrations.test_operations.OperationTests)
 --
 Traceback (most recent call last):
   File
 
"/home/tim/code/django/django/contrib/gis/tests/gis_migrations/test_operations.py",
 line 77, in test_add_gis_field
 2
 AssertionError: 0 != 2
 }}}

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

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

Re: [Django] #23529: Template docs shouldn't use comments as an example

[Django]

#23529: Template docs shouldn't use comments as an example
-+-
 Reporter:  aaugustin|Owner:
 Type:   |  olasitarska
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by varun):

 Replying to [comment:3 aaugustin]:
 > Yes, that's a good choice. Would you like to write a patch?
 Yes, I would love to but I didn't know things move that fast in here :)

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

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

Re: [Django] #23536: BinaryField on mysql gets retrieved as 'str', not as 'bytes'

[Django]

#23536: BinaryField on mysql gets retrieved as 'str', not as 'bytes'
---+--
 Reporter:  fbrau  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Uncategorized  |  Version:  1.6
 Severity:  Normal |   Resolution:  invalid
 Keywords:  mysql BinaryField  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by claudep):

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


Comment:

 This is a known limitation, documented in the third note here:
 https://docs.djangoproject.com/en/dev/ref/databases/#id8

 Now there's hope with a new fork of MySQLdb that we plan to promote
 (#23446), https://pypi.python.org/pypi/mysqlclient/
 If you make positive experiments with that driver, might be nice to
 comment on that ticket.

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

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

Re: [Django] #21272: Oracle doesn't return views in introspection

[Django]

#21272: Oracle doesn't return views in introspection
-+-
 Reporter:  claudep  |Owner:  smeatonj
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  oracle   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

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


Comment:

 This will be fixed along with #18782.

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

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

Re: [Django] #23532: Macedonian locale (mk_MK) date format has an extra dot

[Django]

#23532: Macedonian locale (mk_MK) date format has an extra dot
-+-
 Reporter:  dekomote |Owner:  dekomote
 Type:  Bug  |   Status:  closed
Component:   |  Version:  1.7
  Internationalization   |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"f1d7fffc95fa60488db29a48f38c571978bdc608"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f1d7fffc95fa60488db29a48f38c571978bdc608"
 [1.7.x] Fixed #23532 -- Fixed Macedonian locale date formats

 Backport of 903d144d85 from master.
 }}}

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

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

[django/django] f1d7ff: [1.7.x] Fixed #23532 -- Fixed Macedonian locale da...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: f1d7fffc95fa60488db29a48f38c571978bdc608
  
https://github.com/django/django/commit/f1d7fffc95fa60488db29a48f38c571978bdc608
  Author: Dejan Noveski 
  Date:   2014-09-22 (Mon, 22 Sep 2014)

  Changed paths:
M django/conf/locale/mk/formats.py
M docs/releases/1.7.1.txt

  Log Message:
  ---
  [1.7.x] Fixed #23532 -- Fixed Macedonian locale date formats

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

Re: [Django] #23532: Macedonian locale (mk_MK) date format has an extra dot

[Django]

#23532: Macedonian locale (mk_MK) date format has an extra dot
-+-
 Reporter:  dekomote |Owner:  dekomote
 Type:  Bug  |   Status:  closed
Component:   |  Version:  1.7
  Internationalization   |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"903d144d85f5d25c4968dc41bd5a5ea9434a9703"]:
 {{{
 #!CommitTicketReference repository=""
 revision="903d144d85f5d25c4968dc41bd5a5ea9434a9703"
 Fixed #23532 -- Fixed Macedonian locale date formats
 }}}

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

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

[django/django] 903d14: Fixed #23532 -- Fixed Macedonian locale date forma...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 903d144d85f5d25c4968dc41bd5a5ea9434a9703
  
https://github.com/django/django/commit/903d144d85f5d25c4968dc41bd5a5ea9434a9703
  Author: Dejan Noveski 
  Date:   2014-09-22 (Mon, 22 Sep 2014)

  Changed paths:
M django/conf/locale/mk/formats.py
M docs/releases/1.7.1.txt

  Log Message:
  ---
  Fixed #23532 -- Fixed Macedonian locale date formats


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

[Django] #23536: BinaryField on mysql gets retrieved as 'str', not as 'bytes'

[Django]

#23536: BinaryField on mysql gets retrieved as 'str', not as 'bytes'
---+---
 Reporter:  fbrau  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:  mysql BinaryField
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+---
 I have a project that uses BinaryFields to pickle dynamic data.

 Last week when migrating from sqlite to mysql
 using MySQL-for-Python-3 the BinaryField now gets
 retrieved as 'str'.

 Reading the docs about BinaryField it says it is stored as 'bytes'.

 I know mysql stores blobs
 as text (right?) but in that case the problem is django's
 documentation.

 In this particular case:
 the attribute mymodel.myblob looked like: b'dadadadaa'
 but type(mymodel.myblob) said it was a 'str'
 (I'm bit outdated about latest python changes in strings, bytes
  and unicode)

 Anyways I had to bypass this different behaviour to act just
 like the embedded sqlite driver. My 'solution' is not nice:
 * I had to reparse the string to make it a 'bytes':
>>> self._tags = eval('b"'+self.tags[2:-1]+'"')
 * And add proxy points to get and set the blob

 The code is located at:
 [https://code.google.com/p/tidy-django-
 
models/source/diff?spec=svn2dd52f4b6600c58b9a970cdcebfaf0b725cd0961=2dd52f4b6600c58b9a970cdcebfaf0b725cd0961=side=/tdmodels/tagged.py]

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

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

Re: [Django] #23532: Macedonian locale (mk_MK) date format has an extra dot

[Django]

#23532: Macedonian locale (mk_MK) date format has an extra dot
-+-
 Reporter:  dekomote |Owner:  dekomote
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  1.7
  Internationalization   |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by vasiliyeah):

 * stage:  Accepted => Ready for checkin


Comment:

 True, please checking this patch.

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

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

Re: [Django] #23535: Clarify presence of default filter in tutorial 2

[Django]

#23535: Clarify presence of default filter in tutorial 2
--+
 Reporter:  velis74   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:  tutorial, templates   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by velis74):

 I created a pull request 3258.
 https://github.com/django/django/pull/3258

 It contains modification for docs only as proposed in the original ticket.

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

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

Re: [Django] #23535: Clarify presence of default filter in tutorial 2 (was: A bit vague instructions about modifying templates in tutorial 2)

[Django]

#23535: Clarify presence of default filter in tutorial 2
--+
 Reporter:  velis74   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:  tutorial, templates   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timgraham):

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


Comment:

 You can use git blame to find the commit that added the `default` filter
 to the template ([5ea34f3f]). It should stay, but a documentation update
 for the second issue would be welcome.

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

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

Re: [Django] #18586: Rewrite unit tests migrated from doctests

[Django]

#18586: Rewrite unit tests migrated from doctests
-+-
 Reporter:  konk |Owner:
 Type:   |  ChillarAnand
  Cleanup/optimization   |   Status:  assigned
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  unit tests   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by davide-ceretti):

 I am going to start working on M2mThroughTests

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

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

[Django] #23535: A bit vague instructions about modifying templates in tutorial 2

[Django]

#23535: A bit vague instructions about modifying templates in tutorial 2
--+-
 Reporter:  velis74   |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.7
 Severity:  Normal|   Keywords:  tutorial, templates
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+-
 I'm running through tutorials @ django sprint PyConUK and I just had a bit
 of a problem with the section "Customize the admin look and feel"
 (https://docs.djangoproject.com/en/1.7/intro/tutorial02/).

 In the tutorial, it says: "Then, just edit the file and replace ''{{
 site_header }}'' with your own site’s name as you see fit."

 There are two issues with this:
 1. the tag in base_site.html itself is actually ''{{
 site_header|default:_('Django administration') }}''
 2. changing the default part (''default:_('Django administration')'')
 doesn't work since the ''site_header'' variable is actually defined.

 The documentation mentions the ''site_header'' variable location in the
 same paragraph, but for a new user (such as myself) it is not immediately
 obvious what the entire thing means.

 I would like to discuss two issues regarding this:
 1. The necessity of the ''default:'' specification in the template itself
 (Daniele Procida's suggestion)
 2. Appropriate change in the documentation where the text would be more
 specific about what to change

 Argumentation for issue 1:
 The ''default:'' specification may not even be necessary since the
 site_header variable is declared by default and automatically works.
 Setting it to ''None'' or even ''del''eting it seems like a pretty stupid
 idea, so I would argue that the ''default:'' spec in the template might be
 redundant. I have not tested how the framework reacts to the variable not
 being defined or ''None'' though.

 I propose to fix this by editing the template to remove the ''default:''
 specifications both for ''site_title'' and ''site_header'' variables.

 Argumentation for issue 2:
 I propose to change the text of this paragraph to:
 Then, just edit the file and replace ''{{ site_header }}'' tag with your
 own site’s name as you see fit. Note that in the template, the tag itself
 also contains a ''default'' specification for when the ''site_header''
 variable wouldn't be defined. Since the variable IS defined, you have to
 replace the entire tag text with your own, to e.g. ''{{_('Polls
 administration') }}''
 '''Note:''' We use this approach to teach you how to override templates.
 In an actual project, you would probably use the
 django.contrib.admin.AdminSite.site_header attribute to more easily make
 this particular customization.

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

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

Re: [Django] #23532: Macedonian locale (mk_MK) date format has an extra dot

[Django]

#23532: Macedonian locale (mk_MK) date format has an extra dot
--+
 Reporter:  dekomote  |Owner:  dekomote
 Type:  Bug   |   Status:  assigned
Component:  Internationalization  |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by claudep):

 Great, if he could confirm and mark the ticket as RFC, would be nice!

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

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

Re: [Django] #23534: Docs aren't clear if you can use certain template tags inside blocktrans

[Django]

#23534: Docs aren't clear if you can use certain template tags inside blocktrans
--+
 Reporter:  edu2004eu |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by evildmp):

 * keywords:   => afraid-to-commit


Comment:

 I've marked this ticket as especially suitable for people following the
 ​'''Don't be afraid to commit tutorial''' at the PyCon UK 2014 sprints. If
 you're tackling this ticket, please don't hesitate to ask me for guidance
 if you'd like any, either here or on the Django IRC channels, where I can
 be found as ''EvilDMP''.

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

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

Re: [Django] #18757: Examine ways to get rid of DB backend convert_values()

[Django]

#18757: Examine ways to get rid of DB backend convert_values()
-+-
 Reporter:  akaariai |Owner:  mjtamlyn
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:  fixed
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by Marc Tamlyn ):

 In [changeset:"c6fd1e904cb15da1a627843c79b89b19beabe2a1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c6fd1e904cb15da1a627843c79b89b19beabe2a1"
 Fixed Oracle GIS gml() test failure introduced by e910340; refs #18757.
 }}}

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

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

[django/django] c6fd1e: Fixed Oracle GIS gml() test failure introduced by ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c6fd1e904cb15da1a627843c79b89b19beabe2a1
  
https://github.com/django/django/commit/c6fd1e904cb15da1a627843c79b89b19beabe2a1
  Author: Marc Tamlyn 
  Date:   2014-09-22 (Mon, 22 Sep 2014)

  Changed paths:
M django/contrib/gis/db/backends/oracle/operations.py
M django/contrib/gis/db/models/query.py
M django/contrib/gis/db/models/sql/__init__.py
M django/contrib/gis/db/models/sql/conversion.py

  Log Message:
  ---
  Fixed Oracle GIS gml() test failure introduced by e910340; refs #18757.


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

Re: [Django] #22310: Document exact usage of and consequences of rotating SECRET_KEY

[Django]

#22310: Document exact usage of and consequences of rotating SECRET_KEY
-+-
 Reporter:  erikr|Owner:  erikr
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #23532: Macedonian locale (mk_MK) date format has an extra dot

[Django]

#23532: Macedonian locale (mk_MK) date format has an extra dot
--+
 Reporter:  dekomote  |Owner:  dekomote
 Type:  Bug   |   Status:  assigned
Component:  Internationalization  |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by dekomote):

 Replying to [comment:2 claudep]:
 > The current version of formats.py was contributed by trac user
 vasiliyeah in ticket #15553. Do you know him? Would it be possible to
 contact him about this fix?

 He is a close friend of mine. He is aware of the issue and the fix.

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

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

Re: [Django] #23532: Macedonian locale (mk_MK) date format has an extra dot

[Django]

#23532: Macedonian locale (mk_MK) date format has an extra dot
--+
 Reporter:  dekomote  |Owner:  dekomote
 Type:  Bug   |   Status:  assigned
Component:  Internationalization  |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Description changed by dekomote:

Old description:

> The Macedonian locale (mk_MK) date format currently has an extra dot
> after the year. The date shouldn't end with a dot.
>
> Correct format: '%d.%m.%Y %H:%M:%S' 25.10.2006 14:30:59
> Current format: '%d.%m.%Y. %H:%M:%S' 25.10.2006. 14:30:59
>
> Pull request here - https://github.com/django/django/pull/3255

New description:

 The Macedonian locale (mk_MK) date format currently has an extra dot after
 the year. The date shouldn't end with a dot.

 Correct format: '%d.%m.%Y %H:%M:%S' 25.10.2006 14:30:59
 Current format: '%d.%m.%Y. %H:%M:%S' 25.10.2006. 14:30:59

--

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

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

[django/django] c9a530: Generate GeoManager from GeoQuerySet. Refs #20625.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c9a53035d61588bc7c76eb38db74b774d64b5c1c
  
https://github.com/django/django/commit/c9a53035d61588bc7c76eb38db74b774d64b5c1c
  Author: Loic Bistuer 
  Date:   2014-09-22 (Mon, 22 Sep 2014)

  Changed paths:
M django/contrib/gis/db/models/manager.py

  Log Message:
  ---
  Generate GeoManager from GeoQuerySet. Refs #20625.

This cleanup lays the groundwork for #23533 and also addresses
the issue that GeoManager.get_queryset() failed to pass the
database router hints to the QuerySet constructor.

Thanks Anssi Kääriäinen for the review.


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

Re: [Django] #20625: Custom Chainable QuerySets

[Django]

#20625: Custom Chainable QuerySets
-+-
 Reporter:  danols   |Owner:  loic84
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  QuerySet,|  Needs documentation:  0
  models.Manager, chainable  |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by Loic Bistuer ):

 In [changeset:"c9a53035d61588bc7c76eb38db74b774d64b5c1c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c9a53035d61588bc7c76eb38db74b774d64b5c1c"
 Generate GeoManager from GeoQuerySet. Refs #20625.

 This cleanup lays the groundwork for #23533 and also addresses
 the issue that GeoManager.get_queryset() failed to pass the
 database router hints to the QuerySet constructor.

 Thanks Anssi Kääriäinen for the review.
 }}}

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

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

Re: [Django] #23534: Docs aren't clear if you can use certain template tags inside blocktrans

[Django]

#23534: Docs aren't clear if you can use certain template tags inside blocktrans
--+
 Reporter:  edu2004eu |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by bmispelon):

 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * type:  Bug => Cleanup/optimization
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 Hi,

 That's a good idea, 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.84a16efe21a07063b3ef0fbfea93d2bf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23534: Docs aren't clear if you can use certain template tags inside blocktrans

[Django]

#23534: Docs aren't clear if you can use certain template tags inside blocktrans
---+
 Reporter:  edu2004eu  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  1.7
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 There isn't any reference in the
 [https://docs.djangoproject.com/en/1.7/topics/i18n/translation/#std
 :templatetag-blocktrans docs] about whether you can use `{% if %}` or `{%
 for %}` inside `{% blocktrans %}` blocks.

 There should be a note stating whether such template tags are allowed.

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

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

Re: [Django] #23532: Macedonian locale (mk_MK) date format has an extra dot

[Django]

#23532: Macedonian locale (mk_MK) date format has an extra dot
--+
 Reporter:  dekomote  |Owner:  dekomote
 Type:  Bug   |   Status:  assigned
Component:  Internationalization  |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by claudep):

 * stage:  Unreviewed => Accepted


Comment:

 The current version of formats.py was contributed by trac user vasiliyeah
 in ticket #15553. Do you know him? Would it be possible to contact him
 about this fix?

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

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

Re: [Django] #23533: Hook for default QuerySet filtering defined on the QuerySet itself.

[Django]

#23533: Hook for default QuerySet filtering defined on the QuerySet itself.
-+-
 Reporter:  loic |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by loic):

 It's worth noting that `QuerySet.__init__()` can't be used for providing
 such initialization/customization:
 - QuerySet are often cloned, and the customization should only ever apply
 once.
 - QuerySet methods return a cloned QuerySet instance and `__init__` can't
 return a different instance.

 So far the best option I can think of is a hook called externally by the
 manager.

 POC with a `QuerySet.get_initial_queryset()` method
 https://github.com/loic/django/compare/ticket23533

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

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

[Django] #23533: Hook for default QuerySet filtering defined on the QuerySet itself.

[Django]

#23533: Hook for default QuerySet filtering defined on the QuerySet itself.
-+-
   Reporter:  loic   |  Owner:  nobody
   Type:  New| Status:  new
  feature|Version:  master
  Component:  Database   |   Keywords:
  layer (models, ORM)|  Has patch:  0
   Severity:  Normal |Needs tests:  0
   Triage Stage: |  Easy pickings:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 Django 1.7 brought managers automatically created from `QuerySet` which
 replaces defining a custom manager for the purpose of defining reusable
 methods. Refs #20625.

 One use-case remains inelegant: using a custom `QuerySet` with default
 `QuerySet` customization/filtering:

 {{{
 BaseCustomManager = Manager.from_queryset(CustomQueryset)

 class CustomManager (BaseCustomManager ):
 def get_queryset(self):
 queryset = super(Manager, self).get_queryset()
 return queryset.filter(...)
 }}}

 This ticket proposes adding a hook on `QuerySet` to enable this without
 requiring a custom `Manager`.

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

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