-
-
Notifications
You must be signed in to change notification settings - Fork 384
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
field checks done too early causing error #1147
Comments
I concur, see also #1169 (comment) |
@sscherfke transformers are your labor of love – is this realistic without adding a whole abstraction layer over this? |
Not sure what you mean -- why isn't it sufficient to just move the order check after the field transformer has been applied? IIUC, field transformers can already do arbitrary rearranging, as long as the initial field order is valid. That said, why do we need the manual check in the first place? Python already gives us a pretty good exception when attempting to evaluate the incorrect code. Picking up the above example: def order_by_metadata(cls, fields):
fields.sort(key=lambda x: x.metadata["field_order"])
return fields
@define(field_transformer=order_by_metadata)
class A:
x: int = field(metadata={"field_order": 1})
y: int = field(metadata={"field_order": 0}, default=0) This yields the following error: Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/home/me/.local/lib/python3.11/site-packages/attr/_next_gen.py", line 144, in wrap
return do_it(cls, True)
^^^^^^^^^^^^^^^^
File "/home/me/.local/lib/python3.11/site-packages/attr/_next_gen.py", line 90, in do_it
return attrs(
^^^^^^
File "/home/me/.local/lib/python3.11/site-packages/attr/_make.py", line 1715, in attrs
return wrap(maybe_cls)
^^^^^^^^^^^^^^^
File "/home/me/.local/lib/python3.11/site-packages/attr/_make.py", line 1694, in wrap
builder.add_init()
File "/home/me/.local/lib/python3.11/site-packages/attr/_make.py", line 1090, in add_init
_make_init(
File "/home/me/.local/lib/python3.11/site-packages/attr/_make.py", line 2181, in _make_init
init = _make_method(
^^^^^^^^^^^^^
File "/home/me/.local/lib/python3.11/site-packages/attr/_make.py", line 345, in _make_method
_compile_and_eval(script, globs, locs, filename)
File "/home/me/.local/lib/python3.11/site-packages/attr/_make.py", line 317, in _compile_and_eval
bytecode = compile(script, filename, "exec")
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "<attrs generated init __main__.A>", line 1
def __init__(self, y=attr_dict['y'].default, x):
^
SyntaxError: non-default argument follows default argument |
* Perform attr order checks after field transformer. Fixes: #1147 * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci * Fix assert style in test_hooks --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: Hynek Schlawack <[email protected]>
Attrs does some checks on fields like no defaulted fields coming before non-defaulted fields before running custom field transformers. This is a problem when a field transformer intends to modify the fields but gets an error before being able to apply their modification.
For example, this field transformer reorders fields so that in fact the defaulted field
x
comes after the non-defaulted fieldy
. But attrs errors before the transformer is ever called.I think these checks should be done after custom field transformers.
The text was updated successfully, but these errors were encountered: