date:20160812

Re: [Django] #27054: makemigrations tries to create django_migrations in external database

2016-08-12 Thread Django

#27054: makemigrations tries to create django_migrations in external database
--+
 Reporter:  SydneyUniLibrary-Jim  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Migrations|  Version:  1.10
 Severity:  Release blocker   |   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by SydneyUniLibrary-Jim):

 I've withdrawn the [https://github.com/django/django/pull/7069 pull
 request]. I'll submit a new pull request leaves `MigrationRecorder` as is
 and catches the exception higher up.

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

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

Re: [Django] #27054: makemigrations tries to create django_migrations in external database

2016-08-12 Thread Django

Comment (by SydneyUniLibrary-Jim):

I'm wrong about
`django.core.management.core.management.base.BaseCommand.check_migrations`
not directly or indirectly calling `applied_migrations` in the try suite.

Catching `MigrationSchemaMissing` in `applied_migrations` causes
`admin_scripts.tests.ManageRunserver.test_readonly_database` to fail. This
is because `check_migrations` no longer outputs "Not checking migrations"
and instead outputs the list of missing migrations.

Is this new behaviour of `BaseCommand.check_migrations` better?

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

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

Re: [Django] #27054: makemigrations tries to create django_migrations in external database

2016-08-12 Thread Django

Comment (by SydneyUniLibrary-Jim):

I think I've missed the obvious.

`applied_migrations` is calling `ensure_schema` just to avoid a
`DatabaseError` when it calls `Migration.objects.values_list`. For my the
call to `ensure_schema` has unwanted side-effect and causes a problem.

Maybe it would better to not call `ensure_schema` at all, but instead
catch the `DatabaseError` that is going to happen if there is no ``` table
and then return an empty set.

`MigrationRecorder.record_applied` and
`MigrationRecorder.record_unapplied` both call `ensure_schema` themselves.
This would mean that the `django_migrations` table would be created at the
point when a migration is actually to being applied. At that point, if the
`django_migrations` table cannot be created, that is an exceptional
circumstance.

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

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

Re: [Django] #27054: makemigrations tries to create django_migrations in external database

2016-08-12 Thread Django

Comment (by SydneyUniLibrary-Jim):

For each connection: `loader.check_consistent_history` calls
`recorder.MigrationRecorder.applied_migrations` to get the set of
migrations that have already been applied to the database on the other end
of the connection. `MigrationRecorder.applied_migrations` calls
`MigrationRecorder.ensure_schema` so that it can query the table
underlying `MigrationRecorder.Migration`.

Conceptually `MigrationRecorder.applied_migrations` is a read-only
operation with respect to the database, but nevertheless it does attempt
write operations as an implementation side-effect.

I'm inexperienced in Django's code, so I'll lift catch the exception
higher up the call stack if you think that's best.

My thoughts at catching the `MigrationSchemaMissing` exception within
`applied_migrations` was along the following lines.

The existing usages of `applied_migrations` are:
*
`django.db.migrations.executor.MigrationsExecutor.check_replacements(self)`:
doesn't handle `MigrationSchemaMissing`, copes with `applied_migrations`
returning an empty set
* `django.db.migrations.loader.MigrationLoader.build_graph(self)`: this
code explicitly treats no connection as being equivalent to
`applied_migrations` returning an empty set
*
`django.db.migrations.loader.MigrationLoader.check_consistent_history(self,
connection)`: uses the result of `applied_migrations` in a for loop, so
copes with `applied_migrations` returning an empty set

`MigrationSchemaMissing` is only raised in
`MigrationRecorder.ensure_schema`.

`MigrationSchemaMissing` is only handled in
`django.core.management.core.management.base.BaseCommand.check_migrations`,
where it logs a message to stdout and then skips checking the migrations.
However `check_migrations` doesn't directly or indirectly call
`applied_migrations` in the try suite.

`MigrationSchemaMissing` is a subclass of `DatabaseError`, which has too
many usages to consider.

Considering the existing usages above, and possible future usages, my
thinking for catching `MigrationSchemaMissing` inside `applied_migrations`
is:
* not being able to create `django_migrations` is not exceptional. I think
my use-case and `BaseCommand.check_migrations` proves that
* `MigrationSchemaMissing` is indirectly raised in `applied_migrations`
because of the implementation side-effect, not because of the semantics of
`applied_migrations`. I think it is leaking an exception in a non-
exceptional circumstance.
* I don't think a callee would usefully want to distinguish between a
database with no migrations, where empty set returned, from a sitatuation
of the `django_migrations` table failed to be created, where
`MigrationSchemaMissing` is raised.
* requiring a callee to have to consider `MigrationSchemaMissing` being
raise is onerous, when returning an empty set would most likely have the
same effect in the callee's code.

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

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

Re: [Django] #27008: Add manage.py test --debug option

2016-08-12 Thread Django

#27008: Add manage.py test --debug option
---+-
 Reporter:  cjerdonek  |Owner:  cjerdonek
 Type:  New feature|   Status:  closed
Component:  Testing framework  |  Version:  1.10
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"5890b1613c0a348750a11239ab73a9f0075314ee" 5890b16]:
 {{{
 #!CommitTicketReference repository=""
 revision="5890b1613c0a348750a11239ab73a9f0075314ee"
 Fixed #27008 -- Added --debug-mode option to DiscoverRunner.
 }}}

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

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

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2016-08-12 Thread Django

#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  akaariai |Owner:
 Type:   |   Status:  new
  Cleanup/optimization   |
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:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timgraham):

 * owner:  ketanbhatt =>
 * status:  assigned => new


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

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

Re: [Django] #19222: Clarify that custom managers don't apply to intermediate joins

2016-08-12 Thread Django

#19222: Clarify that custom managers don't apply to intermediate joins
-+-
 Reporter:  andrewbadr   |Owner:
 Type:   |  yanikkoval
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * easy:  1 => 0


Comment:

 I felt the existing proposal is more verbose than needed, so I created an
 alternate [https://github.com/django/django/pull/7074 PR].

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

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

Re: [Django] #27048: Document that refresh_from_db() doesn't clear @cached_properties

2016-08-12 Thread Django

#27048: Document that refresh_from_db() doesn't clear @cached_properties
-+-
 Reporter:  jarekwg  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  cached_property  | Triage Stage:  Ready for
  refresh_from_db|  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:"eea74edc7068a9c75f0f7b09ae59bfdcacc35195" eea74ed]:
 {{{
 #!CommitTicketReference repository=""
 revision="eea74edc7068a9c75f0f7b09ae59bfdcacc35195"
 [1.10.x] Fixed #27048 -- Documented that refresh_from_db() doesn't reload
 @cached_properties.

 Backport of 9556005425ca3d1c8c2a0e8b48e228e63a0bdd32 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.15d48ca697db93f9b018df53b4deb461%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27048: Document that refresh_from_db() doesn't clear @cached_properties

2016-08-12 Thread Django

#27048: Document that refresh_from_db() doesn't clear @cached_properties
-+-
 Reporter:  jarekwg  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  cached_property  | Triage Stage:  Ready for
  refresh_from_db|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by GitHub ):

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


Comment:

 In [changeset:"9556005425ca3d1c8c2a0e8b48e228e63a0bdd32" 95560054]:
 {{{
 #!CommitTicketReference repository=""
 revision="9556005425ca3d1c8c2a0e8b48e228e63a0bdd32"
 Fixed #27048 -- Documented that refresh_from_db() doesn't reload
 @cached_properties.
 }}}

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

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

Re: [Django] #27030: Add support for GIN indexes

2016-08-12 Thread Django

#27030: Add support for GIN indexes
--+
 Reporter:  akki  |Owner:  akki
 Type:  New feature   |   Status:  assigned
Component:  contrib.postgres  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  db-indexes| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"236baa0f0ec31422bc8c36b24e41112f7a564532" 236baa0]:
 {{{
 #!CommitTicketReference repository=""
 revision="236baa0f0ec31422bc8c36b24e41112f7a564532"
 Refs #27030 -- Added BtreeGinExtension operation.
 }}}

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

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

Re: [Django] #27030: Add support for GIN indexes

2016-08-12 Thread Django

#27030: Add support for GIN indexes
--+
 Reporter:  akki  |Owner:  akki
 Type:  New feature   |   Status:  closed
Component:  contrib.postgres  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  db-indexes| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"6e07ec3f655073bebdf1b1dfd2303e91202e14e1" 6e07ec3]:
 {{{
 #!CommitTicketReference repository=""
 revision="6e07ec3f655073bebdf1b1dfd2303e91202e14e1"
 Fixed #27030 -- Added contrib.postgres.indexes.GinIndex.
 }}}

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

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

Re: [Django] #27030: Add support for GIN indexes

2016-08-12 Thread Django

#27030: Add support for GIN indexes
--+
 Reporter:  akki  |Owner:  akki
 Type:  New feature   |   Status:  assigned
Component:  contrib.postgres  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  db-indexes| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"2f19306a125a9253d99b35b276d932e8e24d4e6f" 2f19306a]:
 {{{
 #!CommitTicketReference repository=""
 revision="2f19306a125a9253d99b35b276d932e8e24d4e6f"
 Refs #27030 -- Added index type introspection on PostgreSQL.
 }}}

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

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

Re: [Django] #27048: Document that refresh_from_db() doesn't clear @cached_properties

2016-08-12 Thread Django

#27048: Document that refresh_from_db() doesn't clear @cached_properties
-+-
 Reporter:  jarekwg  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  cached_property  | Triage Stage:  Ready for
  refresh_from_db|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

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

Re: [Django] #26866: Lazy variant of string format

2016-08-12 Thread Django

#26866: Lazy variant of string format
--+
 Reporter:  lovmat|Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Internationalization  |  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):

 Looks promising, tests are still missing.

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

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

Re: [Django] #27007: Handle non-UTF-8 bytes objects for text/* attachments

2016-08-12 Thread Django

#27007: Handle non-UTF-8 bytes objects for text/* attachments
-+-
 Reporter:  Feuermurmel  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Core (Mail)  |  Version:  master
 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:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"72d541b61cd7b0a14f70242e2207fdb3f600c4d5" 72d541b]:
 {{{
 #!CommitTicketReference repository=""
 revision="72d541b61cd7b0a14f70242e2207fdb3f600c4d5"
 Fixed #27007 -- Handled non-UTF-8 bytes objects for text/* attachments.

 The fallback logic which allows non-UTF-8 encoded files to be passed to
 attach_file() even when a `text/*` mime type has been specified is
 moved to attach(). Both functions now fall back to a content type of
 `application/octet-stream`.

 A side effect is that a file's content is decoded in memory instead of
 opening it in text mode and reading it into a string.

 Some mimetype-related logic in _create_attachment() has become
 obsolete as the code moved from attach_file() to attach() already
 handles this.
 }}}

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

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

Re: [Django] #20888: Index ordering in index_together

2016-08-12 Thread Django

#20888: Index ordering in index_together
-+-
 Reporter:  anonymous|Owner:  akki
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  index, order, db-| Triage Stage:  Accepted
  indexes|
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:"311a8e8d505049ff5644a94e16c00246c8a43a18" 311a8e8]:
 {{{
 #!CommitTicketReference repository=""
 revision="311a8e8d505049ff5644a94e16c00246c8a43a18"
 Fixed #20888 -- Added support for column order in class-based indexes.
 }}}

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

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

Re: [Django] #27029: invalid email addresses input django validate_email

2016-08-12 Thread Django

#27029: invalid email addresses input django validate_email
-+-
 Reporter:  RaminFP  |Owner:  Ramin
 |  Farajpour Cami
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   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/065.e37412ac9b6b4749b11888c23d0ed473%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26866: Lazy variant of string format

2016-08-12 Thread Django

#26866: Lazy variant of string format
--+
 Reporter:  lovmat|Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Internationalization  |  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 lovmat):

 Forked and created a ticket_26866 branch:
 https://github.com/lovmat/django/tree/ticket_26866

 What do you think?

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

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

Re: [Django] #22669: bulk_create with empty model fields fails on oracle

2016-08-12 Thread Django

#22669: bulk_create with empty model fields fails on oracle
-+-
 Reporter:  sns1081@…|Owner:  mnach
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  QuerySet.bulk_create   |
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


Comment:

 Tests are passing now and the patch is ready for some feedback from Oracle
 users.

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

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

Re: [Django] #26998: admin.E013 check false positive on django-taggit

2016-08-12 Thread Django

#26998: admin.E013 check false positive on django-taggit
---+
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.10
 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


Comment:

 I don't mind, feel free to submit a 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/067.17614e514c554427f2de30f9f6d4cf68%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26993: Increase the length of the User model's last_name field to 100 characters

2016-08-12 Thread Django

#26993: Increase the length of the User model's last_name field to 100 
characters
--+
 Reporter:  mbox  |Owner:  an0o0nym
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  contrib.auth  |  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 an0o0nym):

 I rushed a little bit. I can see that. My mistake.

 I was going to ask about the docs, whether to reference new commit to this
 one, or make it in the same one.

 Will keep an eye on the discussion and update docs together with db
 migrations (if nescessary new `models.py` file)once the discussion reaches
 the consensus.

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

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

Re: [Django] #26993: Increase the length of the User model's last_name field to 100 characters

2016-08-12 Thread Django

#26993: Increase the length of the User model's last_name field to 100 
characters
--+
 Reporter:  mbox  |Owner:  an0o0nym
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  contrib.auth  |  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):

 This should include docs and a database migration as in
 15ef1dd478c5b6f005e5f782b7619f718ed55e84. Also, the discussion continues
 about 100 vs. 150 characters.

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

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

Re: [Django] #26998: admin.E013 check false positive on django-taggit

2016-08-12 Thread Django

* status: closed => new
* cc: cmawebsite@… (added)
* resolution: duplicate =>

Comment:

Hi All, Sorry I'm late to respond on this.

I encouraged the 983c158da7723eb00a376bd31db76709da4d0260 change in hopes
of being more liberal in what django _accepts_, but I see now that the
many cases the change made django more liberal in what it flags as a
problem.

Yes, #12203 is a good new behavior that would solve this problem, but I'd
consider the 983c158da7723eb00a376bd31db76709da4d0260 to be a regression,
because it breaks things that work fine in 1.9. (Though, yes, you could
argue, private APIs, etc.)

I think we should revert the entire checks.py file changes except for
admin.E003 and admin.E020. (I think the "must be m2m" checks should allow
all many_to_many, and the "can't be m2m" checks should only check
ManyToManyField.). That way django allows more custom fields.

(I'm re-opening so this comment doesn't get lost. Feel free to wontfix if
we don't want to revert the check.py 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/067.48a6b6d7c25a69534d8c4479dba8ffa9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26993: Increase the length of the User model's last_name field to 100 characters

2016-08-12 Thread Django

#26993: Increase the length of the User model's last_name field to 100 
characters
--+
 Reporter:  mbox  |Owner:  an0o0nym
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  contrib.auth  |  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 an0o0nym):

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

Re: [Django] #25995: Add more sophisticated serialization support to JSONField

2016-08-12 Thread Django

#25995: Add more sophisticated serialization support to JSONField
--+
 Reporter:  jimgraham |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.postgres  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  JSONB | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

 * has_patch:  0 => 1


Comment:

 This [https://github.com/django/django/pull/7071 PR] adds custom encoding
 support.

 The decoding part is another story. The patch currently recommends using
 `from_db`/`from_db_value` hooks. If anyone can come with a concrete
 proposal with another method, please propose 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.bde7d81764ddaf5ef1d01ab723ab8c64%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27018: Admin views in admindocs crash with AttributeError

2016-08-12 Thread Django

#27018: Admin views in admindocs crash with AttributeError
---+
 Reporter:  MarkusH|Owner:  helenst
 Type:  Bug|   Status:  assigned
Component:  contrib.admindocs  |  Version:  1.10
 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 helenst):

 I'm working on branch https://github.com/helenst/django/tree/ticket_27018

 Have written tests for the detail and index views.

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

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

Re: [Django] #27037: 'required' attribute on prefilled ClearableFileInput prevents valid form submissions

2016-08-12 Thread Django

#27037: 'required' attribute on prefilled ClearableFileInput prevents valid form
submissions
-+-
 Reporter:  gasman   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.10
 Severity:  Release blocker  |   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:"d8cda352b11ece1070f4aaf4b7a9894908a6160c" d8cda35]:
 {{{
 #!CommitTicketReference repository=""
 revision="d8cda352b11ece1070f4aaf4b7a9894908a6160c"
 [1.10.x] Fixed #27037 -- Prevented required attribute on
 ClearableFileInput when initial data exists.

 Backport of fab46ce6f5a0a58c4e5e39c9e5e412702beb4a64 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/064.fc2449f38ca6c030a8337dbef0df0370%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27037: 'required' attribute on prefilled ClearableFileInput prevents valid form submissions

2016-08-12 Thread Django

#27037: 'required' attribute on prefilled ClearableFileInput prevents valid form
submissions
-+-
 Reporter:  gasman   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.10
 Severity:  Release blocker  |   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:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"fab46ce6f5a0a58c4e5e39c9e5e412702beb4a64" fab46ce6]:
 {{{
 #!CommitTicketReference repository=""
 revision="fab46ce6f5a0a58c4e5e39c9e5e412702beb4a64"
 Fixed #27037 -- Prevented required attribute on ClearableFileInput when
 initial data exists.
 }}}

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

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

Re: [Django] #27029: invalid email addresses input django validate_email

2016-08-12 Thread Django

#27029: invalid email addresses input django validate_email
-+-
 Reporter:  RaminFP  |Owner:  Ramin
 |  Farajpour Cami
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by RaminFP):

 Replying to [comment:2 claudep]:
 > Reopening as I have a patch which targets this specific issue.


 Hi,

 Thanks a lot,

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

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

Re: [Django] #27056: changing dim property for gemotries does not generate correct migration

2016-08-12 Thread Django

#27056: changing dim property for gemotries does not generate correct migration
-+-
 Reporter:  billyburly   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  geodjango postgres   | Triage Stage:  Accepted
  postgis|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * needs_better_patch:   => 0
 * component:  Uncategorized => Migrations
 * needs_tests:   => 0
 * version:  1.9 => master
 * needs_docs:   => 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/068.f2740dd59d384b310a5795b6b75797b2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20888: Index ordering in index_together

2016-08-12 Thread Django

#20888: Index ordering in index_together
-+-
 Reporter:  anonymous|Owner:  akki
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  index, order, db-| Triage Stage:  Accepted
  indexes|
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:"f842d1011c1195aa26071a6ab6f96e0b8d907343" f842d10]:
 {{{
 #!CommitTicketReference repository=""
 revision="f842d1011c1195aa26071a6ab6f96e0b8d907343"
 Refs #20888 -- Added index order introspection.
 }}}

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

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

[Django] #27056: changing dim property for gemotries does not generate correct migration

2016-08-12 Thread Django

#27056: changing dim property for gemotries does not generate correct migration
---+
 Reporter:  billyburly |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  1.9
 Severity:  Normal |   Keywords:  geodjango postgres postgis
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Changing the dim property for a geometry field does not generate a
 migration that changes the number of dimensions a geometry in the DB has.

 Changing a field in a model from {{{models.LineStringField(null=True)}}}
 to {{{models.LineStringField(null=True, dim=3)}}} creates the following
 migration and sql:

 {{{
 # -*- coding: utf-8 -*-
 # Generated by Django 1.9.8 on 2016-08-12 15:28
 from __future__ import unicode_literals

 import django.contrib.gis.db.models.fields
 from django.db import migrations


 class Migration(migrations.Migration):

 dependencies = [
 ('rivermap', '0026_auto_20160624_1827'),
 ]

 operations = [
 migrations.AlterField(
 model_name='sectionextra',
 name='streamPath',
 field=django.contrib.gis.db.models.fields.LineStringField(dim=3,
 null=True, srid=4326),
 ),
 ]
 }}}
 {{{
 BEGIN;
 --
 -- Alter field streamPath on sectionextra
 --
 ALTER TABLE "rivermap_sectionextra" ALTER COLUMN "streamPath" TYPE
 geometry(LINESTRINGZ,4326) USING "streamPath"::geometry(LINESTRINGZ,4326);

 COMMIT;
 }}}
 This causes an exception during migration because PostGIS returned the
 following error
 {{{
 Column has Z dimension but geometry does not
 }}}

 According to http://gis.stackexchange.com/questions/109410/postgis-column-
 has-z-dimension-but-geometry-does-not the {{{ST_Force3D}}} function needs
 to be used for the USING clause.

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

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

Re: [Django] #27029: invalid email addresses input django validate_email

2016-08-12 Thread Django

#27029: invalid email addresses input django validate_email
-+-
 Reporter:  RaminFP  |Owner:  Ramin
 |  Farajpour Cami
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

 * status:  closed => new
 * has_patch:  0 => 1
 * version:  1.10 => master
 * resolution:  duplicate =>
 * stage:  Unreviewed => Accepted


Comment:

 Reopening as I have a patch which targets this specific 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/065.f1ea8b94f0a6c75dafd795a3684a7c3f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26423: Make EmailValidator use HTML5 validation rather than more complicated regular expressions

2016-08-12 Thread Django

#26423: Make EmailValidator use HTML5 validation rather than more complicated
regular expressions
--+
 Reporter:  timgraham |Owner:  cjbcross
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

 * has_patch:  1 => 0


Comment:

 My patch was moved to #27029.

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

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

Re: [Django] #27054: makemigrations tries to create django_migrations in external database

2016-08-12 Thread Django

#27054: makemigrations tries to create django_migrations in external database
--+
 Reporter:  SydneyUniLibrary-Jim  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Migrations|  Version:  1.10
 Severity:  Release blocker   |   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by timgraham):

 I'm not sure if the fix is at the appropriate level. Catching the
 exception in `recorder.py` might hide it too much. It might be more
 appropriate to catch the exception in `makemigrations.py`. Is the
 exception coming from `loader.check_consistent_history(connection)` there?

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

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

Re: [Django] #27039: ModelFields with 'default' value set and 'required'=False in form does not use default value

2016-08-12 Thread Django

#27039: ModelFields with 'default' value set and 'required'=False in form does 
not
use default value
-+-
 Reporter:  devbis   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.10
 Severity:  Release blocker  |   Resolution:
 Keywords:  default non- | Triage Stage:  Accepted
  required modelform |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 I asked on [https://groups.google.com/d/topic/django-
 developers/lpfM6QPILoQ/discussion django-developers] to try to get a
 consensus on how to proceed.

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

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

Re: [Django] #27055: Model form with geometry widgets has invalid html (was: Model form for MultiPolygonField has invalid html)

2016-08-12 Thread Django

#27055: Model form with geometry widgets has invalid html
+
 Reporter:  aptiko  |Owner:  nobody
 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
+
Changes (by claudep):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * version:  1.10 => master
 * needs_docs:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 To fix this and remove the

Re: [Django] #26971: UnicodeDecodeError with non-ASCII string in quoted URL

2016-08-12 Thread Django

#26971: UnicodeDecodeError with non-ASCII string in quoted URL
-+-
 Reporter:  Oleg78   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  HTTP handling|  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  UnicodeDecodeError   | Triage Stage:  Accepted
  UTF-8 windows-1251 URL wsgi|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

 * has_patch:  0 => 1


Comment:

 Suggested fix in that [https://github.com/django/django/pull/7070 PR].

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

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

[Django] #27055: Model form for MultiPolygonField has invalid html

2016-08-12 Thread Django

#27055: Model form for MultiPolygonField has invalid html + Reporter: aptiko | Owner: nobody Type: Bug | Status: new Component: GIS |Version: 1.10 Severity: Normal | Keywords: Triage Stage: Unreviewed | Has patch: 0 Easy pickings: 0 | UI/UX: 0 + == Synopsis == I have a model with a `MultiPolygonField`. I have Django automatically create a form for it (using a `CreateView`). I show the form on a template with `{{ form.as_p}}`. The result is invalid HTML; it has `` inside a `

`. The reason for this is that the MultiPolygonField is rendered with a `django.contrib.gis.forms.widgets.OpenLayersWidget`, which uses `django/contrib/gis/templates/gis/openlayers.html`. This template contains a `