Re: [Django] #32556: assertHTMLEqual gives a confusing error message with empty attributes

[Django]

#32556: assertHTMLEqual gives a confusing error message with empty attributes
-+-
 Reporter:  Baptiste Mispelon|Owner:  Baptiste
 |  Mispelon
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  dev
 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 Mariusz Felisiak ):

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


Comment:

 In [changeset:"41e6b2a3c5e723256506b9ff49437d52a1f3bf43" 41e6b2a3]:
 {{{
 #!CommitTicketReference repository=""
 revision="41e6b2a3c5e723256506b9ff49437d52a1f3bf43"
 Fixed #32556 -- Fixed handling empty string as non-boolean attributes
 value by assertHTMLEqual().
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.070d84b88335e2e3dcdc6f85b73e8d73%40djangoproject.com.

Re: [Django] #32556: assertHTMLEqual gives a confusing error message with empty attributes

[Django]

#32556: assertHTMLEqual gives a confusing error message with empty attributes
-+-
 Reporter:  Baptiste Mispelon|Owner:  Baptiste
 |  Mispelon
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  Version:  dev
 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
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"98abf80cde0a7b6846f2612ee8ec9189adccdc3c" 98abf80c]:
 {{{
 #!CommitTicketReference repository=""
 revision="98abf80cde0a7b6846f2612ee8ec9189adccdc3c"
 Refs #32556 -- Added django.test.html.normalize_attributes().
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.bc1b2fa9f5fe4b31de2d9cbe439584c6%40djangoproject.com.

Re: [Django] #32559: Add attribute 'step' to FloatField.

[Django]

#32559: Add attribute 'step' to FloatField.
-+-
 Reporter:  Jacob Rief   |Owner:  Kapil
 |  Bansal
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  FloatField,  | Triage Stage:  Accepted
  NumberInput, step  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by Mariusz Felisiak:

Old description:

> If someone wants to use the `step` attribute as provided by the HTML
> field
> `` , she/he has to specify that using for
> instance
> `FloatField(widget=NumberInput(attrs={'step': 0.5}))`.
>
> Since the HTML standard offers a `step` attribute on input fields of
> `type="number"`,
> this feature shall be reflected by Django's `FloatField` and  optionally
> `DecimalField`,
> rather than having to parametrize the widget.
>
> Min- and max-values are already supported by the `FloatField`, so the
> step-value
> would make sense here as well. It furthermore would require to revalidate
> the
> step-value by Django's Form validation, rather than by HTML alone.
>
> Patch: https://github.com/django/django/pull/14162

New description:

 If someone wants to use the `step` attribute as provided by the HTML field
 `` , she/he has to specify that using for
 instance
 `FloatField(widget=NumberInput(attrs={'step': 0.5}))`.

 Since the HTML standard offers a `step` attribute on input fields of
 `type="number"`,
 this feature shall be reflected by Django's `FloatField` and  optionally
 `DecimalField`,
 rather than having to parametrize the widget.

 Min- and max-values are already supported by the `FloatField`, so the
 step-value
 would make sense here as well. It furthermore would require to revalidate
 the
 step-value by Django's Form validation, rather than by HTML alone.

--

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.2247af197449260b557a5f7f4a6df397%40djangoproject.com.

Re: [Django] #32559: Add attribute 'step' to FloatField. (was: Add attribute 'step' to FloatField and DecimalField)

[Django]

#32559: Add attribute 'step' to FloatField.
-+-
 Reporter:  Jacob Rief   |Owner:  Kapil
 |  Bansal
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  FloatField,  | Triage Stage:  Accepted
  NumberInput, step  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.d59da81774983d5dee79ea7f03866ca4%40djangoproject.com.

Re: [Django] #18096: Overiding delete permissions in the Admin

[Django]

#18096: Overiding delete permissions in the Admin
---+
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Mariusz Felisiak):

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


Comment:

 Agreed, thanks for checking. Fixed in
 3eb9127678e292ef2645b632199f3e9c876ad999.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.780135445d807d571188a93f58d465c1%40djangoproject.com.

Re: [Django] #32559: Add attribute 'step' to FloatField and DecimalField

[Django]

#32559: Add attribute 'step' to FloatField and DecimalField
-+-
 Reporter:  Jacob Rief   |Owner:  Kapil
 |  Bansal
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  FloatField,  | Triage Stage:  Accepted
  NumberInput, step  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Kapil Bansal):

 * has_patch:  0 => 1


Old description:

> If someone wants to use the `step` attribute as provided by the HTML
> field
> `` , she/he has to specify that using for
> instance
> `FloatField(widget=NumberInput(attrs={'step': 0.5}))`.
>
> Since the HTML standard offers a `step` attribute on input fields of
> `type="number"`,
> this feature shall be reflected by Django's `FloatField` and  optionally
> `DecimalField`,
> rather than having to parametrize the widget.
>
> Min- and max-values are already supported by the `FloatField`, so the
> step-value
> would make sense here as well. It furthermore would require to revalidate
> the
> step-value by Django's Form validation, rather than by HTML alone.

New description:

 If someone wants to use the `step` attribute as provided by the HTML field
 `` , she/he has to specify that using for
 instance
 `FloatField(widget=NumberInput(attrs={'step': 0.5}))`.

 Since the HTML standard offers a `step` attribute on input fields of
 `type="number"`,
 this feature shall be reflected by Django's `FloatField` and  optionally
 `DecimalField`,
 rather than having to parametrize the widget.

 Min- and max-values are already supported by the `FloatField`, so the
 step-value
 would make sense here as well. It furthermore would require to revalidate
 the
 step-value by Django's Form validation, rather than by HTML alone.

 Patch: https://github.com/django/django/pull/14162

--

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.d6db51875af7c34a0f05c354887153c0%40djangoproject.com.

Re: [Django] #18096: Overiding delete permissions in the Admin

[Django]

#18096: Overiding delete permissions in the Admin
---+
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Tim McCurrach):

 I think this can now be closed. It looks like this issue was fixed in
 https://github.com/django/django/commit/3eb9127678e

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.05d3f9097cf3bcce35e7c2ce7012c3dc%40djangoproject.com.

Re: [Django] #32576: Correct documentation for dumpdata --exclude

[Django]

#32576: Correct documentation for dumpdata --exclude
-+-
 Reporter:  Tim McCurrach|Owner:  Tim
 Type:   |  McCurrach
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  3.1
 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 Mariusz Felisiak):

 * stage:  Unreviewed => Accepted


Comment:

 Good catch.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.dbd3a112a5ef8d545a2d8bb9b6b8293d%40djangoproject.com.

Re: [Django] #32559: Add attribute 'step' to FloatField and DecimalField

[Django]

#32559: Add attribute 'step' to FloatField and DecimalField
-+-
 Reporter:  Jacob Rief   |Owner:
 |  devkapilbansal
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  FloatField,  | Triage Stage:  Accepted
  NumberInput, step  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by devkapilbansal):

 * owner:  nobody => devkapilbansal
 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.03636969522f15117cc0fdf5df21e932%40djangoproject.com.