| 5 | | The two parsing statements are different though. Empty strings are allowed for `set_resolution`: `set_resolution = , fixed,` is parsed to `['', 'fixed', '']`. Not for `set_owner` though: `set_owner = , user1, , user2` is parsed to `['user1', 'user2']`. I suspect that was not intentional so I'm not planning to preserve the behaviour unless someone has an argument for keeping it. |
| | 5 | The two parsing statements are different though. ~~Empty strings are allowed for `set_resolution`: `set_resolution = , fixed,` is parsed to `['', 'fixed', '']`. Not for `set_owner` though: `set_owner = , user1, , user2` is parsed to `['user1', 'user2']`.~~ |
| | 6 | |
| | 7 | Leading and trailing empty string are stripped from `set_owner` but not from `set_resolution`. |
| | 8 | * `set_resolution = , fixed, , ` -> `[u'', u'fixed', u'', u'']` |
| | 9 | * `set_owner = , user1, , ` -> `[u'user1', u'']` |
| | 10 | |
| | 11 | I suspect that particular behavior was not intentional so I'm not planning to preserve the behavior unless someone has an argument for keeping it. It seems better to just strip all empty strings. |
| | 12 | |
| | 13 | Parsing the string using `as_list`, the values would be `['fixed']` and `['user']`: [browser:/trunk/trac/ticket/default_workflow.py@13313:63-65#L40] |
