Re: [Django] #11385: DateTimeField doesn't accept ISO 8601 formatted date string

[Django]

#11385: DateTimeField doesn't accept ISO 8601 formatted date string
-+
 Reporter:  jtiai|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  datetime orm format  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by charettes):

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


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

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

Re: [Django] #11385: DateTimeField doesn't accept ISO 8601 formatted date string

[Django]

#11385: DateTimeField doesn't accept ISO 8601 formatted date string
-+
 Reporter:  jtiai|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  datetime orm format  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by bronger):

 * cc: bronger@… (added)


Comment:

 Note that this is not yet really reopened.  An oversight?

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

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

Re: [Django] #26536: Stack overflow in template rendering when using django.template.loaders.cached.Loader

[Django]

#26536: Stack overflow in template rendering when using
django.template.loaders.cached.Loader
-+-
 Reporter:  andersroos   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.9
 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 Simon Charette ):

 In [changeset:"a06fa6e7d35b408264ee0c2e19d2040ef54c5b4d" a06fa6e7]:
 {{{
 #!CommitTicketReference repository=""
 revision="a06fa6e7d35b408264ee0c2e19d2040ef54c5b4d"
 [1.9.x] Fixed #26536 -- Preserved leading dashes of the cached template
 loader keys.

 Thanks Anders Roos for the report.

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

Re: [Django] #26536: Stack overflow in template rendering when using django.template.loaders.cached.Loader

[Django]

#26536: Stack overflow in template rendering when using
django.template.loaders.cached.Loader
-+-
 Reporter:  andersroos   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.9
 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 Simon Charette ):

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


Comment:

 In [changeset:"bd145e7209a0e628cced10384bd6f62d65c0f211" bd145e7]:
 {{{
 #!CommitTicketReference repository=""
 revision="bd145e7209a0e628cced10384bd6f62d65c0f211"
 Fixed #26536 -- Preserved leading dashes of the cached template loader
 keys.

 Thanks Anders Roos for the report.
 }}}

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

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

Re: [Django] #26052: Consider removing conditional_content_removal

[Django]

#26052: Consider removing conditional_content_removal
--+
 Reporter:  aaugustin |Owner:  susan
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  HTTP handling |  Version:  1.9
 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):

 * needs_better_patch:  1 => 0


Comment:

 Okay, here's a [https://github.com/django/django/pull/6505 PR] based on
 that suggestion.

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

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

Re: [Django] #19513: update() after annotate(val=Sum(...)) crashes on PostgreSQL & Oracle

[Django]

#19513: update() after annotate(val=Sum(...)) crashes on PostgreSQL & Oracle
-+-
 Reporter:  mengzhuo1203@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (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
-+-

Comment (by dsanders11):

 Opened a [https://github.com/django/django/pull/6504 PR request] with a
 regression test as requested. The PR should also fix #18580 which is the
 same underlying issue as this 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/080.214e62d0ae38f03693a4c4ed5414d489%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26539: Using Annotation As Update Parameter Generates Invalid SQL

[Django]

#26539: Using Annotation As Update Parameter Generates Invalid SQL
--+
 Reporter:  dsanders11|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 If you try to use an annotation which spans tables in an update,
 everything will resolve and attempt to execute but the SQL will fail
 because for MySQL the query is broken into a `SELECT` and then an
 `UPDATE`, but the necessary info is not available in the UPDATE. On
 sqlite3 it generates an `UPDATE` that looks similar but with the `SELECT`
 as a subquery.

 Example:

 {{{
 class Bar(models.Model):
 name = models.CharField(max_length=32)

 class Foo(models.Model):
 related_bar = models.ForeignKey(Bar)
 bar_name = models.CharField(max_length=32)

 
Foo.objects.annotate(bar_name=F('related_bar__name')).update(name=F('bar_name'))
 }}}

 On MySQL produces:

 {{{
 SELECT `test_foo`.`id`, `test_bar`.`name` AS `bar_name` FROM `test_foo`
 LEFT OUTER JOIN `test_bar` ON ( `test_foo`.`related_bar` = `test_bar`.`id`
 );

 UPDATE `test_foo` SET `bar_name` = `test_bar`.`name` WHERE `test_foo`.`id`
 IN (1);
 }}}

 I don't think there's a trivial fix for this. Doing an `UPDATE` with a
 `JOIN` appears to have different syntax in the various implementations and
 isn't possible at all on sqlite3, so it would need to be multiple queries.

 Seems that until it can be made to work correctly an error should occur if
 attempted, similar to the
 
[https://github.com/django/django/blob/master/django/db/models/sql/compiler.py#L1098
 error for aggregates] in an `UPDATE`.

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

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

Re: [Django] #26536: Stack overflow in template rendering when using django.template.loaders.cached.Loader

[Django]

#26536: Stack overflow in template rendering when using
django.template.loaders.cached.Loader
-+-
 Reporter:  andersroos   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.9
 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 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/068.572f82e88e6ebaa1de94020b9486ddc1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26052: Consider removing conditional_content_removal

[Django]

#26052: Consider removing conditional_content_removal
--+
 Reporter:  aaugustin |Owner:  susan
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  HTTP handling |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by claudep):

 I tested the HEAD behaviour of mod_wsgi without
 `conditional_content_removal` and confirms it strips the content.

 If it's not too hard to simulate this behavior in the test client, I think
 we should do it at that level.

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

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

Re: [Django] #26538: BaseInlineFormSet Has Inconsistent Fields For Forms

[Django]

#26538: BaseInlineFormSet Has Inconsistent Fields For Forms
+--
 Reporter:  dsanders11  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Forms   |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by dsanders11):

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

Re: [Django] #26537: BaseInlineFormSet Adds N Entries to form._meta.fields For FK

[Django]

#26537: BaseInlineFormSet Adds N Entries to form._meta.fields For FK
+--
 Reporter:  dsanders11  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Forms   |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by dsanders11):

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

Re: [Django] #26537: BaseInlineFormSet Adds N Entries to form._meta.fields For FK

[Django]

#26537: BaseInlineFormSet Adds N Entries to form._meta.fields For FK
---+--
 Reporter:  dsanders11 |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Forms  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by dsanders11):

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


Comment:

 Submitted [https://github.com/django/django/pull/6503 PR #6503].

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

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

Re: [Django] #26538: BaseInlineFormSet Has Inconsistent Fields For Forms

[Django]

#26538: BaseInlineFormSet Has Inconsistent Fields For Forms
---+--
 Reporter:  dsanders11 |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Forms  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by dsanders11):

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


Comment:

 Submitted [https://github.com/django/django/pull/6503 PR #6503].

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

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

[Django] #26538: BaseInlineFormSet Has Inconsistent Fields For Forms

[Django]

#26538: BaseInlineFormSet Has Inconsistent Fields For Forms
---+
 Reporter:  dsanders11 |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Forms  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  0  |  UI/UX:  0
---+
 Currently `BaseInlineFormSet` appends the FK name for the formset to the
 fields for the form `Meta` every time `add_fields` runs, so the first form
 in the formset does not see the FK as a field on the form when it is
 instantiated. Subsequent forms in the formset will see the field since it
 is added to the form `Meta` after `add_fields` runs.

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

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

[Django] #26537: BaseInlineFormSet Adds N Entries to form._meta.fields For FK

[Django]

#26537: BaseInlineFormSet Adds N Entries to form._meta.fields For FK
---+
 Reporter:  dsanders11 |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Forms  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  0  |  UI/UX:  0
---+
 Currently `BaseInlineFormSet` appends the FK name for the formset to the
 fields for the form `Meta` every time `add_fields` runs, so with you end
 up with N fields where N - 1 are duplicates. As each form is instantiated
 it'll see a different version of the list.

 Example based on `tests/inline_formsets/tests.py`:

 {{{
 >>> poet = Poet.objects.create(name='test')
 >>> poet.poem_set.create(name='first test poem')
 >>> poet.poem_set.create(name='second test poem')
 >>> poet.poem_set.create(name='third test poem')
 >>> PoemFormSet = inlineformset_factory(Poet, Poem, fields=('name',),
 extra=0)
 >>> formset = PoemFormSet(None, instance=poet)
 >>> PoemFormSet.form._meta.fields
 ['name', 'poet', 'poet', 'poet']
 }}}

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

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

Re: [Django] #26536: Stack overflow in template rendering when using django.template.loaders.cached.Loader

[Django]

#26536: Stack overflow in template rendering when using
django.template.loaders.cached.Loader
-+
 Reporter:  andersroos   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.9
 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 charettes):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/6502 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.de374b71cd5344a91e5fbe035bc8529e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26534: has_changed For BooleanField and NullBooelanField always returns True with HiddenInput

[Django]

#26534: has_changed For BooleanField and NullBooelanField always returns True 
with
HiddenInput
-+-
 Reporter:  dsanders11   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  has_changed  | Triage Stage:  Ready for
  BooleanField   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette ):

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


Comment:

 In [changeset:"218175b09d244b9c7c84c2f2d5f478297251bbe9" 218175b0]:
 {{{
 #!CommitTicketReference repository=""
 revision="218175b09d244b9c7c84c2f2d5f478297251bbe9"
 Fixed #26534 -- Fixed boolean form fields has_changed() with hidden input.
 }}}

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

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

Re: [Django] #26534: has_changed For BooleanField and NullBooelanField always returns True with HiddenInput

[Django]

#26534: has_changed For BooleanField and NullBooelanField always returns True 
with
HiddenInput
-+-
 Reporter:  dsanders11   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  has_changed  | Triage Stage:  Ready for
  BooleanField   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

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

Re: [Django] #26536: Stack overflow in template rendering when using django.template.loaders.cached.Loader

[Django]

#26536: Stack overflow in template rendering when using
django.template.loaders.cached.Loader
-+
 Reporter:  andersroos   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.9
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by charettes):

 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * severity:  Normal => Release blocker
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 This is a regression introduced by
 fc2147152637e21bc73f991b50fa06254af02739.

 Using `'-'.join(filter(bool, [template_name, skip_prefix, dirs_prefix]))`
 instead should fix 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/068.bf742908640bdd7b6d93429bb845c618%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26524: Change foreign key id list_display reference to display only the id

[Django]

#26524: Change foreign key id list_display reference to display only the id
-+-
 Reporter:  cristianocca |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  admin list_display   | Triage Stage:  Accepted
  changelist |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by zachborboa):

 * cc: zachborboa@… (added)


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

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

[Django] #26536: Stack overflow in template rendering when using django.template.loaders.cached.Loader

[Django]

#26536: Stack overflow in template rendering when using
django.template.loaders.cached.Loader
-+
 Reporter:  andersroos   |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Template system  |Version:  1.9
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 If you have two template files with the same name except one is prefixed
 with a dash '-' where one is including the other, you will get a stack
 overflow.

 For example if the main template named {{{example.html}}} looks like this:
 {{{
 {% include '-example.html' %}
 }}}

 This bug is in django.template.loaders.cached.Loader and only happens if
 it is used.

 I believe the bug is caused by the strip('-') when building the cache key
 at {{{django/template/loaders/cached.py:103}}} (in
 {{{Loader.cache_key}}}):
 {{{
 return ("%s-%s-%s" % (template_name, skip_prefix,
 dirs_prefix)).strip('-')
 }}}

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

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

[Django] #26535: Possible bug - when migrating and removing unique constraint.

[Django]

#26535: Possible bug - when migrating and removing unique constraint.
---+
 Reporter:  jenlu  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Migrations |Version:  1.9
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Possible bug - when migrating and removing unique constraint.

 Postgres 9.4.1 / 9.5.7 + Django 1.9.5 + psycopg 2.6.1

 ——

 My setup is models/database representing sports events, and with
 competitors in different events.

 Each competitor in different sports has for their model/class:

class Meta:
unique_together = ('event', 'number')

 i.e. ensure a unique starting number in an event, now we are relaxing
 (removing this constraint)
 this but having issues when migrating.

 The above is represented in postgress as a UNIQUE constraint
 and in all models.py the above constraint is as-above — but in pg it is
 represented as

 (i) UNIQUE (event_id, number)

 and sometimes as...

 (ii) UNIQUE (number, event_id)

 …and now when doing migration - for all tables where it is represented as
 (i) everything
 goes well, but in tables where (ii) the following error:

  File "/Users/XXX/.virtualenvs/ssi195_2711/lib/python2.7/site-
 packages/django/db/migrations/migration.py", line 123, in apply
operation.database_forwards(self.app_label, schema_editor, old_state,
 project_state)
  File "/Users/XXX/.virtualenvs/ssi195_2711/lib/python2.7/site-
 packages/django/db/migrations/operations/models.py", line 359, in
 database_forwards
getattr(new_model._meta, self.option_name, set()),
  File "/Users/XXX/.virtualenvs/ssi195_2711/lib/python2.7/site-
 packages/django/db/backends/base/schema.py", line 318, in
 alter_unique_together
self._delete_composed_index(model, fields, {'unique': True},
 self.sql_delete_unique)
  File "/Users/XXX/.virtualenvs/ssi195_2711/lib/python2.7/site-
 packages/django/db/backends/base/schema.py", line 347, in
 _delete_composed_index
", ".join(columns),
 ValueError: Found wrong number (0) of constraints for
 match_ppc_ppccompetitor(event_id, number)

 So seems to need to do some migrations manually and no biggie - but yet
 strange and unsure if Django or pg issue….

 / Jens

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

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