date:20150618

Re: [Django] #25002: Postgresql migration fails when changing a CharField to a TimeField

2015-06-18 Thread Django

#25002: Postgresql migration fails when changing a CharField to a TimeField
-+-
 Reporter:  dirkcuys |Owner:  charettes
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  migrations   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by MarkusH):

 * version:  1.8 => master


Comment:

 I don't thing this bug justifies for backport to 1.8. It's the same
 behavior on 1.7. Use `AddField`, `RunSQL`/`RunPython`, `RemoveField`,
 `RenameField` for the desired outcome.

 That said, there is/was a ticket for `VARCHAR`/`INTEGER` conversation on a
 PK, I think. Do you mind investing that one too. Maybe they can both be
 closed by 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.277eddbf51831e06e2d2f64bf33accbe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25003: schema.tests.SchemaTests.test_alter_implicit_id_to_explicit fails when run in isolation on MySQL

2015-06-18 Thread Django

#25003: schema.tests.SchemaTests.test_alter_implicit_id_to_explicit fails when 
run
in isolation on MySQL
-+
   Reporter:  charettes  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Testing framework  |Version:  1.8
   Severity:  Normal |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 {{{
 Testing against Django installed in '/usr/src/django/django'
 Creating test database for alias 'default'...
 Creating test database for alias 'other'...
 E
 ==
 ERROR: test_alter_implicit_id_to_explicit (schema.tests.SchemaTests)
 --
 Traceback (most recent call last):
   File "/usr/src/django/tests/schema/tests.py", line 765, in
 test_alter_implicit_id_to_explicit
 Author.objects.create(name='Foo')
   File "/usr/src/django/django/db/models/manager.py", line 125, in
 manager_method
 return getattr(self.get_queryset(), name)(*args, **kwargs)
   File "/usr/src/django/django/db/models/query.py", line 401, in create
 obj.save(force_insert=True, using=self.db)
   File "/usr/src/django/django/db/models/base.py", line 674, in save
 force_update=force_update, update_fields=update_fields)
   File "/usr/src/django/django/db/models/base.py", line 702, in save_base
 updated = self._save_table(raw, cls, force_insert, force_update,
 using, update_fields)
   File "/usr/src/django/django/db/models/base.py", line 786, in
 _save_table
 result = self._do_insert(cls._base_manager, using, fields, update_pk,
 raw)
   File "/usr/src/django/django/db/models/base.py", line 825, in _do_insert
 using=using, raw=raw)
   File "/usr/src/django/django/db/models/manager.py", line 125, in
 manager_method
 return getattr(self.get_queryset(), name)(*args, **kwargs)
   File "/usr/src/django/django/db/models/query.py", line 1028, in _insert
 return query.get_compiler(using=using).execute_sql(return_id)
   File "/usr/src/django/django/db/models/sql/compiler.py", line 980, in
 execute_sql
 cursor.execute(sql, params)
   File "/usr/src/django/django/db/backends/utils.py", line 64, in execute
 return self.cursor.execute(sql, params)
   File "/usr/src/django/django/db/utils.py", line 95, in __exit__
 six.reraise(dj_exc_type, dj_exc_value, traceback)
   File "/usr/src/django/django/db/backends/utils.py", line 64, in execute
 return self.cursor.execute(sql, params)
   File "/usr/src/django/django/db/backends/mysql/base.py", line 112, in
 execute
 return self.cursor.execute(query, args)
   File "/usr/local/lib/python2.7/site-packages/MySQLdb/cursors.py", line
 220, in execute
 self.errorhandler(self, exc, value)
   File "/usr/local/lib/python2.7/site-packages/MySQLdb/connections.py",
 line 36, in defaulterrorhandler
 raise errorvalue
 OperationalError: (1364, "Field 'id' doesn't have a default value")

 --
 Ran 1 test in 0.156s

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

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

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

Re: [Django] #25002: Postgresql migration fails when changing a CharField to a TimeField

2015-06-18 Thread Django

#25002: Postgresql migration fails when changing a CharField to a TimeField
-+-
 Reporter:  dirkcuys |Owner:  charettes
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  migrations   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * has_patch:  0 => 1
 * easy:  1 => 0


Comment:

 Not sure if this is something we want to backport to 1.8.x but the added
 test seems to be passing with the proposed changes.

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

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

Re: [Django] #25002: Postgresql migration fails when changing a CharField to a TimeField

2015-06-18 Thread Django

#25002: Postgresql migration fails when changing a CharField to a TimeField
-+-
 Reporter:  dirkcuys |Owner:  charettes
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  migrations   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by charettes):

 * owner:  nobody => charettes
 * status:  new => assigned
 * easy:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 I'm not sure this qualify as a bug or an enhancement but a simple fix
 would be to set

 `DatabaseSchemaEditor.sql_alter_column_type = "ALTER COLUMN %(column)s
 TYPE %(type)s USING %(column)s::%(type)s"`.

 I'll submit a tentative PR to run the full test suite against CI before
 adding a test.

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

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

Re: [Django] #24997: Allow bulk_create with proxy inheritance

2015-06-18 Thread Django

#24997: Allow bulk_create with proxy inheritance
-+-
 Reporter:  wkschwartz   |Owner:
 |  wkschwartz
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  proxy, inheritance,  | Triage Stage:  Accepted
  bulk_create, queryset, insert  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by wkschwartz):

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

Re: [Django] #24997: Allow bulk_create with proxy inheritance

2015-06-18 Thread Django

#24997: Allow bulk_create with proxy inheritance
-+-
 Reporter:  wkschwartz   |Owner:
 |  wkschwartz
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  proxy, inheritance,  | Triage Stage:  Accepted
  bulk_create, queryset, insert  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by wkschwartz):

 * has_patch:  0 => 1


Comment:

 Pull request submitted: https://github.com/django/django/pull/4886

 Note I've updated it since @timgraham looked at it this morning. It now
 correctly handles the case where a proxy model inherits from a multi-table
 model.

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

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

Re: [Django] #25002: Postgresql migration fails when changing a CharField to a TimeField

2015-06-18 Thread Django

#25002: Postgresql migration fails when changing a CharField to a TimeField
-+-
 Reporter:  dirkcuys |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  migrations   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by dirkcuys:

Old description:

> The code from the migration is as follows:
>
> {{{#!python
> migrations.AlterField(
> model_name='studygroup',
> name='time',
> field=models.TimeField(),
> ),
> }}}
>
> The field used to be a models.CharField()
>
> The error follows:
>
> {{{
> django.db.utils.ProgrammingError: column "time" cannot be cast
> automatically to type time without time zone
> HINT:  Specify a USING expression to perform the conversion
> }}}
>
> I can manually fix this using SQL:
>
> {{{
> ALTER TABLE "studygroups_studygroup" ALTER COLUMN "time" TYPE time USING
> "time"::time;
> }}}

New description:

 The code from the migration is as follows:

 {{{#!python
 migrations.AlterField(
 model_name='studygroup',
 name='time',
 field=models.TimeField(),
 ),
 }}}

 The field used to be a models.CharField()

 The error follows:

 {{{
 django.db.utils.ProgrammingError: column "time" cannot be cast
 automatically to type time without time zone
 HINT:  Specify a USING expression to perform the conversion
 }}}

 I can manually fix this using SQL:

 {{{
 ALTER TABLE "studygroups_studygroup" ALTER COLUMN "time" TYPE time USING
 "time"::time;
 }}}

 I don't have code with the problem isolated, but this project shows the
 problem when configured to use postgres. http://github.com/p2pu/knight-
 app/.

--

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

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

Re: [Django] #25002: Postgresql migration fails when changing a CharField to a TimeField

2015-06-18 Thread Django

#25002: Postgresql migration fails when changing a CharField to a TimeField
-+-
 Reporter:  dirkcuys |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  migrations   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by dirkcuys):

 * needs_better_patch:   => 0
 * component:  Uncategorized => Database layer (models, ORM)
 * needs_tests:   => 0
 * keywords:   => migrations
 * needs_docs:   => 0
 * type:  Uncategorized => Bug


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

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

[Django] #25002: Postgresql migration fails when changing a CharField to a TimeField

2015-06-18 Thread Django

#25002: Postgresql migration fails when changing a CharField to a TimeField
---+
 Reporter:  dirkcuys   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.8
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 The code from the migration is as follows:

 {{{#!python
 migrations.AlterField(
 model_name='studygroup',
 name='time',
 field=models.TimeField(),
 ),
 }}}

 The field used to be a models.CharField()

 The error follows:

 {{{
 django.db.utils.ProgrammingError: column "time" cannot be cast
 automatically to type time without time zone
 HINT:  Specify a USING expression to perform the conversion
 }}}

 I can manually fix this using SQL:

 {{{
 ALTER TABLE "studygroups_studygroup" ALTER COLUMN "time" TYPE time USING
 "time"::time;
 }}}

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

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

[Django] #25001: collectstatic does not correctly handle uninstallation of apps which write the same file as remaining apps.

2015-06-18 Thread Django

#25001: collectstatic does not correctly handle uninstallation of apps which 
write
the same file as remaining apps.
-+
 Reporter:  JulianAndrews|  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  contrib.staticfiles  |Version:  1.8
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 Steps to reproduce:

 1. Create a project with two apps which write the same static file.
 2. Run `python manage.py collectstatic`.
 3. Uninstall the first app.
 4. Re-run `python manage.py collectstatic`.

 Expected behavior:
 The file from the second (still installed) app should be installed.

 Observed Behavior:
 The file from the first (now uninstalled) app remains installed.

 See [https://github.com/fusionbox/collectstatic_bug] for a demonstration
 of the bug.

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

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

Re: [Django] #24834: Optional port in Host request header breaks get_current_site()

2015-06-18 Thread Django

#24834: Optional port in Host request header breaks get_current_site()
-+-
 Reporter:  ngnpope  |Owner:  ngnpope
 Type:  Bug  |   Status:  closed
Component:  contrib.sites|  Version:  1.5
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"0d97e73d95379722b8044fa09b1c1c4ee4c0a486" 0d97e73d]:
 {{{
 #!CommitTicketReference repository=""
 revision="0d97e73d95379722b8044fa09b1c1c4ee4c0a486"
 Fixed reverse sites_tests failures introduced in refs #24834.
 }}}

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

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

Re: [Django] #24940: unhashable type: 'RelatedManager' when deleting a model using django admin that has GenericRelation and related_query_name

2015-06-18 Thread Django

#24940: unhashable type: 'RelatedManager' when deleting a model using django 
admin
that has GenericRelation and related_query_name
-+-
 Reporter:  jmfederico   |Owner:  MarkusH
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  1.8
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #24962: Objects with primary keys containing newlines do not get links to being edited in the admin list view

2015-06-18 Thread Django

#24962: Objects with primary keys containing newlines do not get links to being
edited in the admin list view
---+
 Reporter:  alito  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  1
---+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"20c6ba6ffa9d68cad21fcfbdcb1a7d72eaee143c" 20c6ba6f]:
 {{{
 #!CommitTicketReference repository=""
 revision="20c6ba6ffa9d68cad21fcfbdcb1a7d72eaee143c"
 Fixed #24962 -- Added newline to characters escaped by
 contrib.admin.utils.quote()

 Thanks alito for the report and patch.
 }}}

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

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

Re: [Django] #24865: Add a feature to programmatically remove stale content types

2015-06-18 Thread Django

#24865: Add a feature to programmatically remove stale content types
--+
 Reporter:  Protosac  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.contenttypes  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  stale contenttypes| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by MarkusH):

 Tim, neither patch is guaranteed to work when a user has not applied all
 `contenttypes` migrations, as the model used inside the
 `update_contenttypes` is from the global apps, not from the latest applied
 migration state (see #24100 for that).

 Anyway, I'm ok with making it a public API if we put a `.. warning::` box
 around the docs and state the potential data loss due to cascading.

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

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

Re: [Django] #24940: unhashable type: 'RelatedManager' when deleting a model using django admin that has GenericRelation and related_query_name

2015-06-18 Thread Django

#24940: unhashable type: 'RelatedManager' when deleting a model using django 
admin
that has GenericRelation and related_query_name
-+
 Reporter:  jmfederico   |Owner:  MarkusH
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  1.8
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by MarkusH):

 * status:  new => assigned
 * owner:  nobody => MarkusH
 * has_patch:  0 => 1


Comment:

 PR: https://github.com/django/django/pull/4885

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

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

Re: [Django] #23658: Provide the password to PostgreSQL from "dbshell" command

2015-06-18 Thread Django

#23658: Provide the password to PostgreSQL from "dbshell" command
-+-
 Reporter:  etanol   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  postgresql dbshell   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


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

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

Re: [Django] #24873: Error while using Prefech on more than two levels

2015-06-18 Thread Django

#24873: Error while using Prefech on more than two levels
-+-
 Reporter:  Gagaro   |Owner:  Gagaro
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  Prefetch | Triage Stage:  Ready for
  prefetch_related   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"74261bc593bcf9411e7e25a4731dd9471499819e" 74261bc5]:
 {{{
 #!CommitTicketReference repository=""
 revision="74261bc593bcf9411e7e25a4731dd9471499819e"
 Fixed #24873 -- Prevented nested Prefetch objects from being overwritten.
 }}}

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

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

Re: [Django] #25000: Implement default str and similar for lazy() objects

2015-06-18 Thread Django

#25000: Implement default __str__ and similar for lazy() objects
---+
 Reporter:  knbk   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Utilities  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timgraham):

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


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

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

Re: [Django] #24994: Document/check that settings.SECRET_KEY should be a valid unicode string

2015-06-18 Thread Django

#24994: Document/check that settings.SECRET_KEY should be a valid unicode string
--+
 Reporter:  bmispelon |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (System checks)  |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #24958: Inline admins broken with UUID parent key and AutoField child key

2015-06-18 Thread Django

#24958: Inline admins broken with UUID parent key and AutoField child key
-+
 Reporter:  jhoos|Owner:  jhoos
 Type:  Bug  |   Status:  assigned
Component:  Forms|  Version:  1.8
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by timgraham):

 * needs_better_patch:  0 => 1


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

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

Re: [Django] #24998: ManyToManyField generating wrong query

2015-06-18 Thread Django

#24998: ManyToManyField generating wrong query
-+-
 Reporter:  arthurio |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  ManyToManyField, | Triage Stage:
  bad query  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by arthurio):

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


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

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

Re: [Django] #24998: ManyToManyField generating wrong query

2015-06-18 Thread Django

#24998: ManyToManyField generating wrong query
-+-
 Reporter:  arthurio |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ManyToManyField, | Triage Stage:
  bad query  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by arthurio):

 If you define the related_name with a unique name, the bug goes away.
 There is probably something going on when setting the _hints of the
 related field.

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

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

Re: [Django] #15760: Feature: JS Hooks for Dynamic Inlines

2015-06-18 Thread Django

#15760: Feature: JS Hooks for Dynamic Inlines
-+-
 Reporter:  mlavin   |Owner:
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  inlines jquery   | Triage Stage:  Accepted
  callback   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-
Changes (by RamezIssac):

 * cc: RamezIssac (added)


Comment:

 PR created [https://github.com/django/django/pull/4883 4883]

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

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

Re: [Django] #24997: Allow bulk_create with proxy inheritance

2015-06-18 Thread Django

#24997: Allow bulk_create with proxy inheritance
-+-
 Reporter:  wkschwartz   |Owner:
 |  wkschwartz
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  proxy, inheritance,  | Triage Stage:  Accepted
  bulk_create, queryset, insert  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 Per our [https://docs.djangoproject.com/en/dev/internals/release-process
 /#supported-versions supported version policy], I don't think this would
 qualify for a backport to 1.8. I'd suggest to take a look at our
 [https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
 /submitting-patches/#patch-review-checklist patch review checklist] before
 you submit the PR, but generally the patch looks okay.

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

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

Re: [Django] #24997: Allow bulk_create with proxy inheritance

2015-06-18 Thread Django

Comment (by wkschwartz):

I have also created a forward port for Django 1.9 (based on the master
branch) at https://github.com/wkschwartz/django/tree/ticket_24997_19.
(It's simply a cherry-pick from the other branch.) The documentation in
this version of the patch still shows the bug being fixed in Django 1.8.3.
The purpose of this version of the patch is merely to make it easy to
forward-port the fix.

I've created another "practice" pull request at
https://github.com/wkschwartz/django/pull/2.

All commits are now squashed.

Tests pass on Sqlite and Postgresql.

Unless someone says otherwise beforehand, I'll submit both pull requests
tomorrow morning.

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

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

Re: [Django] #12952: Models history doesn't use verbose names

2015-06-18 Thread Django

#12952: Models history doesn't use verbose names
--+
 Reporter:  acangiano |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  1
--+

Comment (by timgraham):

 It seems to me that the verbose name is a safer choice to account for the
 fact that you might have several different editing forms each with a
 different label.

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

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

Re: [Django] #20203: Impossible to have a descriptor named `objects` on an abstract model

2015-06-18 Thread Django

#20203: Impossible to have a descriptor named `objects` on an abstract model
-+-
 Reporter:  Alex |Owner:  coldmind
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by coldmind):

 * has_patch:  0 => 1


Comment:

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

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

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

Re: [Django] #24964: Infinite migrations with empty help_text via ugettext_lazy

2015-06-18 Thread Django

#24964: Infinite migrations with empty help_text via ugettext_lazy
-+-
 Reporter:  gimbo|Owner:  coldmind
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.8
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations,  | Triage Stage:  Accepted
  internationalisation   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by coldmind):

 Replying to [comment:7 knbk]:
 > Replying to [comment:5 coldmind]:
 > > Or, the question is more why
 > >
 > > {{{
 > > ipdb> old_field.help_text
 > > u''
 > > ipdb> new_field.help_text
 > > 
 > > }}}
 >
 > `__repr__` is not in any way set on `__proxy__`, so it inherits the
 default behaviour from `object`, which is what you're seeing. If you use
 `str(new_field.help_text)`, you should see `u''`.

 I described problem in
 https://code.djangoproject.com/ticket/24964#comment:6, this is not related
 to actual problem

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

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

Re: [Django] #24964: Infinite migrations with empty help_text via ugettext_lazy

2015-06-18 Thread Django

#24964: Infinite migrations with empty help_text via ugettext_lazy
-+-
 Reporter:  gimbo|Owner:  coldmind
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.8
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations,  | Triage Stage:  Accepted
  internationalisation   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by knbk):

 Replying to [comment:5 coldmind]:
 > Or, the question is more why
 >
 > {{{
 > ipdb> old_field.help_text
 > u''
 > ipdb> new_field.help_text
 > 
 > }}}

 `__repr__` is not in any way set on `__proxy__`, so it inherits the
 default behaviour from `object`, which is what you're seeing. If you use
 `str(new_field.help_text)`, you should see `u''`.

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

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

Re: [Django] #24881: order_with_respect_to needs better docs

2015-06-18 Thread Django

#24881: order_with_respect_to needs better docs
-+-
 Reporter:  karyon   |Owner:  karyon
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timgraham):

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


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

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

Re: [Django] #24995: MySQL error when renaming a primary key

2015-06-18 Thread Django

#24995: MySQL error when renaming a primary key
+
 Reporter:  EikeDehling |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.8
 Severity:  Normal  |   Resolution:
 Keywords:  rename mysql error  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by EikeDehling):

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

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

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

Re: [Django] #24997: Allow bulk_create with proxy inheritance

2015-06-18 Thread Django

#24997: Allow bulk_create with proxy inheritance
-+-
 Reporter:  wkschwartz   |Owner:
 |  wkschwartz
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  proxy, inheritance,  | Triage Stage:  Accepted
  bulk_create, queryset, insert  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by wkschwartz):

 Work ongoing at https://github.com/wkschwartz/django/tree/ticket_24997.

 I've created a "practice" pull request at
 https://github.com/wkschwartz/django/pull/1. Before submitting a real pull
 request to Django, I'll squash my commits.

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

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

Re: [Django] #24995: MySQL error when renaming a primary key

2015-06-18 Thread Django

#24995: MySQL error when renaming a primary key
+
 Reporter:  EikeDehling |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.8
 Severity:  Normal  |   Resolution:
 Keywords:  rename mysql error  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by EikeDehling):

 Thanks, testing with settings for mysql indeed shows the issue

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

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

Re: [Django] #24999: manage dbshell with mysql give the password on the command line, visible system wide

2015-06-18 Thread Django

#24999: manage dbshell with mysql give the password on the command line, visible
system wide
-+-
 Reporter:  nirgal   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


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

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

Re: [Django] #24834: Optional port in Host request header breaks get_current_site()

2015-06-18 Thread Django

#24834: Optional port in Host request header breaks get_current_site()
-+-
 Reporter:  ngnpope  |Owner:  ngnpope
 Type:  Bug  |   Status:  closed
Component:  contrib.sites|  Version:  1.5
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"b3d5dc6932bf896a909e9871d508654494b34563" b3d5dc69]:
 {{{
 #!CommitTicketReference repository=""
 revision="b3d5dc6932bf896a909e9871d508654494b34563"
 Fixed #24834 -- Fixed get_current_site() when Host header contains port.

 When the Host header contains a port, looking up the Site record fails
 as the host will never match the domain.
 }}}

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

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

[Django] #25000: Implement default str and similar for lazy() objects

2015-06-18 Thread Django

#25000: Implement default __str__ and similar for lazy() objects
+
 Reporter:  knbk|  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Utilities   |Version:  master
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 Currently `__str__`  returns the string representation of the proxied
 object only if one of the resultclasses is a string-like object.
 Otherwise, it returns the pretty much useless
 ``.

 `str(lazy_object)` should return the same as `str(non_lazy_object)`. This
 is easily achievable by providing a default `__str__()` method on
 `__proxy__`:

 {{{
 class __proxy__(Promise):
 def __str__(self):
 return str(self.__cast())
 }}}

 This behaviour would still be overridden for string-like lazy objects. The
 same could be implemented for `bytes()` and `unicode()`.

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

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

[Django] #24999: manage dbshell with mysql give the password on the command line, visible system wide

2015-06-18 Thread Django

#24999: manage dbshell with mysql give the password on the command line, visible
system wide
+
 Reporter:  nirgal  |  Owner:  nobody
 Type:  Uncategorized   | Status:  new
Component:  Core (Management commands)  |Version:  master
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 Hi

 When using mysql backend, when one runs the dbshell command,
 subprocess.call() uses the mysql command line argument --password. This is
 insecure on multi-users systems, since anyone who can do "ps" is able to
 see the password.

 I believe it would be much better to write the password in the temporary
 configuration file whose name is given using --defaults-extra-
 file=file_name, in a way similar to
 https://github.com/django/django/pull/4392

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

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

Re: [Django] #24997: Allow bulk_create with proxy inheritance

2015-06-18 Thread Django

#24997: Allow bulk_create with proxy inheritance
-+-
 Reporter:  wkschwartz   |Owner:
 |  wkschwartz
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  proxy, inheritance,  | Triage Stage:  Accepted
  bulk_create, queryset, insert  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by wkschwartz):

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

Re: [Django] #24997: Allow bulk_create with proxy inheritance

2015-06-18 Thread Django

Comment (by wkschwartz):

I think that as a user, I would be surprised if `bulk_create` did not
execute in single (or very small number of, depending on `batch_size`)
INSERTs. I can imagine stackoverflow threads asking "How to force
bulk_create to use single insert," with answers to the effect of, "Back in
the day, it always executed in a single INSERT but now it's a bit of a
guessing game". I'm not saying that it would be a guessing game, I'm just
saying that having `bulk_create` decide what to do will feel opaque to
users. The current way it works has the advantage of being fully explicit.

Further, I'm not sure I see such an expansion of `bulk_create`'s duties as
being germane to allowing proxy models to use the method, except if your
goal is also to allow multi-table models to use it. But the latter
consideration seems like it should be a separate 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/068.0f65b24d5161d987052bd33bee43b3ef%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24944: Have password_reset pass extra_context to the email template rendering as well

2015-06-18 Thread Django

#24944: Have password_reset pass extra_context to the email template rendering 
as
well
--+---
 Reporter:  twelveeighty  |Owner:  SujaySKumar
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+---

Comment (by timgraham):

 The password reset function is documented in
 `docs/topics/auth/default.txt`.

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

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

Re: [Django] #24944: Have password_reset pass extra_context to the email template rendering as well

2015-06-18 Thread Django

Comment (by SujaySKumar):

Replying to [comment:4 timgraham]:
> A ticket isn't marked fixed until the patch is committed to Django. Also
your patch is missing tests and documentation as outlined in our
[https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
/submitting-patches/#patch-review-checklist patch review checklist]. Also
your patch has a problem if someone is using `extra_context` with a key
that clashes with one in `opts` as I mentioned in comment 1.
I am new to contributing to open source. I am not able to understand where
to put the documentation for this new feature. I would be grateful if you
could point to the file in which I should add the documentation.

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

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

Re: [Django] #24944: Have password_reset pass extra_context to the email template rendering as well

2015-06-18 Thread Django

#24944: Have password_reset pass extra_context to the email template rendering 
as
well
--+---
 Reporter:  twelveeighty  |Owner:  SujaySKumar
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+---
Changes (by SujaySKumar):

 * needs_tests:  0 => 1


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

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

Re: [Django] #24944: Have password_reset pass extra_context to the email template rendering as well

2015-06-18 Thread Django

#24944: Have password_reset pass extra_context to the email template rendering
as
well
--+---
Reporter: twelveeighty |Owner: SujaySKumar
Type: New feature | Status: new
Component: contrib.auth | Version: 1.8
Severity: Normal| Resolution:
Keywords:| Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 1 |UI/UX: 0
--+---
Changes (by timgraham):

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

Comment:

A ticket isn't marked fixed until the patch is committed to Django. Also
your patch is missing tests and documentation as outlined in our
[https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
/submitting-patches/#patch-review-checklist patch review checklist]. Also
your patch has a problem if someone is using `extra_context` with a key
that clashes with one in `opts` as I mentioned in comment 1.

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

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

Re: [Django] #24424: Removing a model's last field results in SQL syntax error on SQLite

2015-06-18 Thread Django

Comment (by adnam):

I notice this bug is still open after 4 months. My feeling is that
reproducing it by creating a rather convoluted series of migrations is
rather the wrong way to go about it. The error is quite simple as I
[[https://github.com/django/django/pull/4325#issuecomment-85060638|explained
earlier]], and the fix is just a
[[https://github.com/django/django/pull/4325/files#diff-
0c8f495bfee773ab7b5409533bd6d7efL142|2-line change in
db/backends/sqlite3/schema.py]]. The bug only affects the sqlite schema
editor as it uniquely deletes then re-creates tables upon migrations.
Reproducing the error via migrations is rather like eating sushi with 10m-
long chopsticks, since the bug is several layers down the internal API.
Just my tuppence worth.

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

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

Re: [Django] #24944: Have password_reset pass extra_context to the email template rendering as well

2015-06-18 Thread Django

#24944: Have password_reset pass extra_context to the email template rendering 
as
well
--+---
 Reporter:  twelveeighty  |Owner:  SujaySKumar
 Type:  New feature   |   Status:  closed
Component:  contrib.auth  |  Version:  1.8
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+---
Changes (by SujaySKumar):

 * status:  assigned => closed
 * needs_docs:  0 => 1
 * has_patch:  0 => 1
 * resolution:   => fixed
 * needs_better_patch:  0 => 1


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

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

Re: [Django] #15760: Feature: JS Hooks for Dynamic Inlines

2015-06-18 Thread Django

#15760: Feature: JS Hooks for Dynamic Inlines
-+-
 Reporter:  mlavin   |Owner:
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  inlines jquery   | Triage Stage:  Accepted
  callback   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-

Comment (by RamezIssac):

 Adding a formset defaults in the document_ready block is too late for the
 defaults to get picked up.
 The plugin is Initiated by the edit_inline/tabular.html (or stacked) , at
 the end of inline_field_sets block

 The other option i see is on the extrahead block

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

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

Re: [Django] #24998: ManyToManyField generating wrong query

2015-06-18 Thread Django

#24998: ManyToManyField generating wrong query
-+-
 Reporter:  arthurio |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ManyToManyField, | Triage Stage:
  bad query  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 This looks like it might be a duplicate of #24505 (fixed in master, but
 not 1.8). Can you reproduce the issue against 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.96973e33045dd34b5820e81a55c02ee3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24995: MySQL error when renaming a primary key

2015-06-18 Thread Django

#24995: MySQL error when renaming a primary key
+
 Reporter:  EikeDehling |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.8
 Severity:  Normal  |   Resolution:
 Keywords:  rename mysql error  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by timgraham):

 You need to [https://docs.djangoproject.com/en/dev/internals/contributing
 /writing-code/unit-tests/#using-another-settings-module create another
 settings file] in order to run the tests with a different database. Please
 send a pull request with the fix and test.

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

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

Re: [Django] #24865: Add a feature to programmatically remove stale content types

2015-06-18 Thread Django

#24865: Add a feature to programmatically remove stale content types
--+
 Reporter:  Protosac  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.contenttypes  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  stale contenttypes| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by timgraham):

 Markus, can you elaborate on the data loss concerns? I guess it's about
 the possibility of delete cascades which is why interactive prompts were
 originally added in #12339. I don't think there's much value in completing
 this ticket if it isn't a public API. I'd think documentation that
 explains the data-loss considerations would do more to educate users than
 keeping the function private would. If you have another idea on how to
 address the use case in #24820 I'm open to alternatives.

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

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

Re: [Django] #24944: Have password_reset pass extra_context to the email template rendering as well

2015-06-18 Thread Django

#24944: Have password_reset pass extra_context to the email template rendering 
as
well
--+---
 Reporter:  twelveeighty  |Owner:  SujaySKumar
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  1.8
 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 SujaySKumar):

 * status:  new => assigned
 * cc: sujay.skumar141295@… (added)
 * owner:  nobody => SujaySKumar


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

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

Re: [Django] #20203: Impossible to have a descriptor named `objects` on an abstract model

2015-06-18 Thread Django

#20203: Impossible to have a descriptor named `objects` on an abstract model
-+-
 Reporter:  Alex |Owner:  coldmind
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by coldmind):

 * owner:   => coldmind
 * cc: me@… (added)
 * version:  1.5 => master
 * status:  new => assigned


Comment:

 I'm working on this issue

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

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

Re: [Django] #24865: Add a feature to programmatically remove stale content types

2015-06-18 Thread Django

#24865: Add a feature to programmatically remove stale content types
--+
 Reporter:  Protosac  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.contenttypes  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  stale contenttypes| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by MarkusH):

 * needs_better_patch:  0 => 1


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

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

Re: [Django] #24865: Add a feature to programmatically remove stale content types

2015-06-18 Thread Django

#24865: Add a feature to programmatically remove stale content types
--+
 Reporter:  Protosac  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.contenttypes  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  stale contenttypes| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by MarkusH):

 I think `remove_contenttypes()` should remain private as well. It's way
 too easy to loose data when using that function. I'd put the respective
 documentation for that method into the function's docstring.

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

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

Re: [Django] #24960: Blank pages due to {{ block.super }}

2015-06-18 Thread Django

#24960: Blank pages due to {{ block.super }}
-+-
 Reporter:  srkunze  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  block.super blank| Triage Stage:
  pages  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by srkunze):

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


Comment:

 We further investigated the issue. We found that with an upgrade to 1.8,
 we might resolve the issue of empty {{ block.super }}.

 However, we might consider opening another issue for the inconsistencies
 of variable resolution. We still would prefer a check-if-possible approach
 instead of try-and-fail.

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

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

Re: [Django] #24998: ManyToManyField generating wrong query

2015-06-18 Thread Django

#24998: ManyToManyField generating wrong query
-+-
 Reporter:  arthurio |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ManyToManyField, | Triage Stage:
  bad query  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by arthurio):

 * Attachment "manytomanybug-1.1.zip" added.

 Django project containing the test

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

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

Re: [Django] #24995: MySQL error when renaming a primary key

2015-06-18 Thread Django

#24995: MySQL error when renaming a primary key
+
 Reporter:  EikeDehling |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.8
 Severity:  Normal  |   Resolution:
 Keywords:  rename mysql error  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by EikeDehling):

 Commit with test here:
 
https://github.com/EikeDehling/django/commit/72aa1b92551137da69104ab917079ea7e3ac8854

 This would only fail on mysql though, which the test-framework does not
 use i think?

 So the test also passes without my patch.

 Suggestions?

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

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

[Django] #24998: ManyToManyField generating wrong query

2015-06-18 Thread Django

#24998: ManyToManyField generating wrong query
-+-
Reporter: arthurio | Owner: nobody
Type: Bug | Status: new
Component: Database layer |Version: master
(models, ORM) | Keywords: ManyToManyField, bad
Severity: Normal | query
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0| UI/UX: 0
-+-
If two models have a ManyToManyField pointing to the same model, the query
generate for the lookup is incorrect. I have created a repo on github with
a simple test
(https://github.com/arthurio/manytomanybug/releases/tag/v1.0) and you can
also find the code enclosed as a .zip file.

There are 3 models:
- Upload: that will be common to several other models.
- FormA with a ManyToManyField to the Upload model.
- FormB with a ManyToManyField to the Upload model.

When trying to do formAinstance.signature.all(), the query generated is
using the FormB table to do the join instead of the FormA table.

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

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

Re: [Django] #24998: ManyToManyField generating wrong query

2015-06-18 Thread Django

#24998: ManyToManyField generating wrong query
--+
 Reporter:  arthurio  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal| Resolution:
 Keywords:  ManyToManyField, bad query|   Triage Stage:  Unreviewed
Has patch:  0 |  Easy pickings:  0
UI/UX:  0 |
--+
Changes (by arthurio):

 * Attachment "manytomanybug-1.0.zip" added.

 Django project containing the test

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

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

Re: [Django] #24998: ManyToManyField generating wrong query

2015-06-18 Thread Django

#24998: ManyToManyField generating wrong query
-+-
 Reporter:  arthurio |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ManyToManyField, | Triage Stage:
  bad query  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by arthurio):

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


Old description:

> If two models have a ManyToManyField pointing to the same model, the
> query generate for the lookup is incorrect. I have created a repo on
> github with a simple test
> (https://github.com/arthurio/manytomanybug/releases/tag/v1.0) and you can
> also find the code enclosed as a .zip file.
>
> There are 3 models:
> - Upload: that will be common to several other models.
> - FormA with a ManyToManyField to the Upload model.
> - FormB with a ManyToManyField to the Upload model.
>
> When trying to do formAinstance.signature.all(), the query generated is
> using the FormB table to do the join instead of the FormA table.

New description:

 If two models have a ManyToManyField pointing to the same model, the query
 generated for the lookup is incorrect. I have created a repo on github
 with a simple test
 (https://github.com/arthurio/manytomanybug/releases/tag/v1.0) and you can
 also find the code enclosed as a .zip file.

 There are 3 models:
 - Upload: that will be common to several other models.
 - FormA with a ManyToManyField to the Upload model.
 - FormB with a ManyToManyField to the Upload model.

 When trying to do formAinstance.signature.all(), the query generated is
 using the FormB table to do the join instead of the FormA table.

--

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

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

59 matches

Mail list logo