For me, it doesn't deserve it because only sequence.strict are affected which are only used for invoice sequence. Normal usage will require to create such sequence once per year (generally 1 january). So the bug could be managed as any other bugs with the "monthly" bugfix releases.
This is because of the double call to fields_view_get due to the inherit of a view from an other model.
I think we should drop this feature as we don't have anymore "inherits" for which this was implemented.
Meanwhile as every series is affected, I think we could avoid the second call to safe_eval if the attributue contains "__" as it will in any case fail and it also means that it was already encoded.
- All modules installation
- create a fiscalyear
- on Tab Sequences in the field of the first sequence (Post Move Sequence) hit F3 and create first sequence
- go to second field (Customer Invoice Sequence) and hit F3
Traceback (most recent call last):
File "/trytond/protocols/jsonrpc.py", line 150, in _marshaled_dispatch
response['result'] = dispatch_method(method, params)
File "/trytond/protocols/jsonrpc.py", line 179, in _dispatch
res = dispatch(*args)
File "/trytond/protocols/dispatcher.py", line 160, in dispatch
result = rpc.result(meth(*c_args, **c_kwargs))
File "/trytond/model/modelview.py", line 239, in fields_view_get
File "/trytond/model/modelview.py", line 331, in _view_look_dom_arch
File "/trytond/model/modelview.py", line 471, in __view_look_dom
File "/trytond/model/modelview.py", line 431, in __view_look_dom
File "/trytond/tools/misc.py", line 373, in safe_eval
raise ValueError('Double underscores not allowed')
ValueError: Double underscores not allowed