Changes between Initial Version and Version 5 of Ticket #17229


Ignore:
Timestamp:
11/14/2011 10:32:46 PM (3 years ago)
Author:
lukeplant
Comment:

Your initial example only did a comparison to True, and didn't mention any comparison to None. I am not a mind reader!

The ticket has now changed in scope to the feature addition "Allow 'True', 'False' and 'None' to resolve to corresponding Python objects".

I can see why this would be useful, but I'm not entirely convinced, given that we've survived without these for a long time. Therefore marking DDN.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #17229

    • Property Status changed from new to reopened
    • Property Patch needs improvement unset
    • Property Needs tests unset
    • Property Summary changed from Invalid '==' expression silently ignored leading to invalid result to Allow 'True', 'False' and 'None' to resolve to corresponding Python objects
    • Property Type changed from Bug to New feature
    • Property Needs documentation unset
    • Property UI/UX unset
    • Property Triage Stage changed from Unreviewed to Design decision needed
  • Ticket #17229 – Description

    initial v5  
     1[Original bug title: Invalid '==' expression silently ignored leading to invalid result]
     2
    13Let me clarify the title - I am not sure the expression below is invalid. It is the expression I intuitively expect to work. But perhaps Django it is a specifics of template language. In any case it should either complain or produce expected output, which it doesn't.
    24
Back to Top