Use most recent Python Syntax in .pyi files

[JonathanPlasse]

In .pyi files, the most recent syntax of python can be used, as it is only used for static analysis.

Therefore, these changes can be made:

• Remove all quotes (future annotation)
• Use | instead of Optional and Union (PEP 604) (Use modern Python 3.10 syntax #207)
• Use type Parameter Syntax (PEP 695)
• Use list, dict, … instead of typing.List, typing.Dict, … (PEP 585)
  • builtin (Use modern Python 3.10 syntax #207)
  • collections.abc (Replace deprecated aliases to ABCs in collections.abc #223)
• Use Self (PEP 673)
• Add Ruff and enable linter rules to avoid regression we encountered (c.f. Fix typing.Tuple syntax reintroduced in mod file #222, Fix: Use | None instead of typing.Optional #224)

I could work on this, to familiarize myself with the codebase.

[nutti]

@JonathanPlasse

Yes, go ahead.
Currently, we use Python 3.9 for the generation which does not support these syntax.
You many need to change Python version as well.

fake-bpy-module/.github/workflows/fake-bpy-module-ci.yml

Line 69 in 97f5da9

python-version: "3.9"

[JonathanPlasse]

Ok, I will start working on it.

[nutti]

@JonathanPlasse

#207 is merged now.
Will you also tackle the remain (PEP695) as wall?

[JonathanPlasse]

I will.

[Road-hog123]

Can I suggest PEP 673's Self type as a related change?

Presently ID.evaluated_get() returns ID, but if this were changed to Self then I believe Object.evaluated_get() would correctly return Object instead of ID.

Unfortunately the documentation just lists the return type as ID, so I don't know if there's anything for the generation code to detect to make this change automatically.

[JonathanPlasse]

To avoid regression, we should use the plugin flake-pyi available in Ruff to check we use the modern syntax in the generated code.

[nutti]

@JonathanPlasse

Should this issue be still opened?
I think some features have already merged.

[JonathanPlasse]

Can I suggest PEP 673's Self type as a related change?

Presently ID.evaluated_get() returns ID, but if this were changed to Self then I believe Object.evaluated_get() would correctly return Object instead of ID.

Unfortunately the documentation just lists the return type as ID, so I don't know if there's anything for the generation code to detect to make this change automatically.

This one would be interesting.

To avoid regression, we should use the plugin flake-pyi available in Ruff to check we use the modern syntax in the generated code.

This one would be cool to have.

Is it a problem for you if the issue remains open?
Should we open a specific issue for each remaining point instead?

[nutti]

No, I just would like to know the current status and the future plan.
We welcome your contribution.

[JonathanPlasse]

I updated the initial comment.

[nutti]

@JonathanPlasse

Ruff linter is now merged to the master branch.
You can tackle the remaining task now.

[nutti]

@JonathanPlasse

Can I suggest PEP 673's Self type as a related change?

Presently ID.evaluated_get() returns ID, but if this were changed to Self then I believe Object.evaluated_get() would correctly return Object instead of ID.

Unfortunately the documentation just lists the return type as ID, so I don't know if there's anything for the generation code to detect to make this change automatically.

By solving this feature, I solved below item.

• Use Self (PEP 673)

[nutti]

@JonathanPlasse

I think below item seems to have already been resolved by the ruff linter introduced.

• Add Ruff and enable linter rules to avoid regression we encountered

How do you think about it?

[JonathanPlasse]

Does it check that the generated code passes the rules of flake8-pyi?