Compatibility with python 3.9

[colormotor]

Hello, thanks for the great lib! I recently moved from pyimgui to slimgui, but found that I could not use slimgui with Python 3.9, which is required for ROS1 to function with RoboStack (RoboStack/ros-noetic#489).
Would you consider relaxing the requirement in future releases?
I was able to get slimgui to run by removing code that is incompatible with 3.9, specifically calls to match and the use of | as opposed to Optional. Happy to do a pull request if useful.

[nurpax]

This would require switching docs generation pipeline to support multiple versions of Python static type syntax. It may be possible but it may also need more than simple mechanical changes.

I'd very much like the .pyi files to be correct even on Python 3.9. This should be mostly possible because Nanobind does support Python 3.9 and it will generate the .pyi files for that Python version.

If you're willing to dig into it, I may be open to a PR that supports this, but it should be done by starting with this file full_build.sh which is what drives the full Slimgui build.

The reason why I have not supported earlier version of Python is because this script is kind of hardcoded to run on Python 3.12. This way the output .pyi files will be for that version and won't work on earlier versions. But this way I was also able to more easily write all the other scripts using Python 3.12/13 without worrying about what runs in GitHub Actions.

You'll notice that I also check in the generated .pyi files. An alternative would be to rebuild the package in CI for each Python version and not used checked in .pyi's. I'm not sure what's the best approach here.

Do you think that Python 3.9 typing hints can express all the types that are used in the pyi files?

[colormotor]

Probably needs more testing but I got it to work with some modifs to the gen code and integrations. But I installed with full_build.sh and I'm not sure how easy it is to migrate to your build system for pip. You can check here:
main...colormotor:slimgui:py39-test
Ended up also adding a script that does the conversion automatically (with some LLM help:)

[nurpax]

Sorry, but I'm going to push back on lowering the minimum required Python version to 3.9. I have so many scripts that are written for Python 3.10 and I write all my new code using Python 3.13. I'd prefer not to have the friction of having to deal with old Python 3.9 type annotations.

Are the RoboStack people not willing to upgrade to later version of Python? F.ex. Python 3.10 was already released in Oct 2021, so it's not really that new.

Here's a rough estimate of what each file requires:

3.10    check_min_python.py
  - 3.6: f-strings (line 17)
  - 3.9: PEP 585 built-in generics (`list[str]` style) (line 48)
  - 3.10: PEP 604 union types (`A | B`) in annotations (line 24)
3.6     example/app.py
  - 3.6: f-strings (line 110)
3.0     example/demo_window/__init__.py
3.9     example/demo_window/demo.py
  - 3.6: f-strings (line 128)
  - 3.9: PEP 585 built-in generics (`list[str]` style) (line 15)
3.6     example/demo_window/layout.py
  - 3.6: f-strings (line 27)
3.6     example/demo_window/property_editor.py
  - 3.6: f-strings (line 19)
3.9     example/demo_window/shapes.py
  - 3.9: PEP 585 built-in generics (`list[str]` style) (line 18)
3.0     example/demo_window/types.py
3.0     example/demo_window/utils.py
3.6     example/demo_window/widgets.py
  - 3.6: f-strings (line 108)
3.8     example/demo_window/widgets2.py
  - 3.6: f-strings (line 119)
  - 3.8: walrus operator (`:=`) (line 128)
3.0     example/doc_examples/__init__.py
3.0     example/doc_examples/buttons.py
3.6     example/doc_examples/layout.py
  - 3.6: f-strings (line 20)
3.10    example/doc_examples/meta.py
  - 3.9: PEP 585 built-in generics (`list[str]` style) (line 12)
  - 3.10: PEP 604 union types (`A | B`) in annotations (line 12)
3.0     example/implot_demo_window/__init__.py
3.10    example/implot_demo_window/implot.py
  - 3.6: f-strings (line 285)
  - 3.9: PEP 585 built-in generics (`list[str]` style) (line 13)
  - 3.10: structural pattern matching (`match`/`case`) (line 206)
3.10    example/run_examples.py
  - 3.6: f-strings (line 23)
  - 3.8: walrus operator (`:=`) (line 178)
  - 3.9: PEP 585 built-in generics (`list[str]` style) (line 45)
  - 3.10: PEP 604 union types (`A | B`) in annotations (line 58)
3.6     example/standalone_glfw.py
  - 3.6: f-strings (line 10)
3.6     example/standalone_pyglet.py
  - 3.6: f-strings (line 147)
3.0     example/util/gl_utils.py
3.10    example/util/imgui_window.py
  - 3.10: PEP 604 union types (`A | B`) in annotations (line 180)
3.8     gen/amend_func_docs.py
  - 3.6: f-strings (line 72)
  - 3.8: walrus operator (`:=`) (line 22)
3.9     gen/checklist.py
  - 3.6: f-strings (line 131)
  - 3.9: PEP 585 built-in generics (`list[str]` style) (line 35)
3.10    gen/expand_apiref_md.py
  - 3.6: f-strings (line 44)
  - 3.8: walrus operator (`:=`) (line 154)
  - 3.9: PEP 585 built-in generics (`list[str]` style) (line 15)
  - 3.10: PEP 604 union types (`A | B`) in annotations (line 16)
3.10    gen/gen_nb_enums.py
  - 3.6: f-strings (line 45)
  - 3.8: walrus operator (`:=`) (line 79)
  - 3.9: PEP 585 built-in generics (`list[str]` style) (line 14)
  - 3.10: PEP 604 union types (`A | B`) in annotations (line 48)
3.10    gen/gen_nb_funcs.py
  - 3.6: f-strings (line 227)
  - 3.9: PEP 585 built-in generics (`list[str]` style) (line 22)
  - 3.10: PEP 604 union types (`A | B`) in annotations (line 23)
  - 3.10: structural pattern matching (`match`/`case`) (line 280)
3.10    gen/gen_utils.py
  - 3.6: f-strings (line 180)
  - 3.8: walrus operator (`:=`) (line 204)
  - 3.9: PEP 585 built-in generics (`list[str]` style) (line 131)
  - 3.10: PEP 604 union types (`A | B`) in annotations (line 144)
  - 3.10: structural pattern matching (`match`/`case`) (line 190)
3.10    gen/imgui_vendor.py
  - 3.6: f-strings (line 15)
  - 3.10: PEP 604 union types (`A | B`) in annotations (line 24)
3.0     gen/recipes/__init__.py
3.9     gen/recipes/build_recipes.py
  - 3.6: f-strings (line 84)
  - 3.9: PEP 585 built-in generics (`list[str]` style) (line 16)
3.10    gen/recipes/examples.py
  - 3.9: PEP 585 built-in generics (`list[str]` style) (line 31)
  - 3.10: PEP 604 union types (`A | B`) in annotations (line 27)
3.10    gen/recipes/make_recipes_md.py
  - 3.6: f-strings (line 28)
  - 3.9: PEP 585 built-in generics (`list[str]` style) (line 28)
  - 3.10: PEP 604 union types (`A | B`) in annotations (line 26)
3.10    gen/recipes/screenshot_render.py
  - 3.6: f-strings (line 27)
  - 3.9: PEP 585 built-in generics (`list[str]` style) (line 50)
  - 3.10: PEP 604 union types (`A | B`) in annotations (line 83)
3.0     gen/stubfixer.py
3.0     gen/test_gen_utils.py
3.6     src/c/imgui/misc/debuggers/imgui_lldb.py
  - 3.6: f-strings (line 58)
3.0     src/slimgui/__init__.py
3.10    src/slimgui/imgui/__init__.py
  - 3.9: PEP 585 built-in generics (`list[str]` style) (line 47)
  - 3.10: PEP 604 union types (`A | B`) in annotations (line 67)
3.10    src/slimgui/implot/__init__.py
  - 3.10: PEP 604 union types (`A | B`) in annotations (line 15)
3.0     src/slimgui/integrations/__init__.py
3.0     src/slimgui/integrations/base.py
3.10    src/slimgui/integrations/glfw.py
  - 3.9: PEP 585 built-in generics (`list[str]` style) (line 50)
  - 3.10: PEP 604 union types (`A | B`) in annotations (line 14)
3.0     src/slimgui/integrations/null.py
3.10    src/slimgui/integrations/opengl.py
  - 3.10: structural pattern matching (`match`/`case`) (line 272)
3.0     tests/test_implot.py
3.10    tests/test_simple.py
  - 3.10: PEP 604 union types (`A | B`) in annotations (line 195)
  - 3.10: structural pattern matching (`match`/`case`) (line 223)

[colormotor]

Thanks for checking, I understand and it makes sense. Unfortunately ROS is a complicated beast and it is made to run on Linux, so it already seems like a miracle that the RoboStack people managed to package a version that runs on MacOS. From the issue I linked above it seems that it is a no go, but for my use case I can stick with my locally installed/patched version of slimgui and I might eventually switch to a newer version of ROS as also the version I am using (Noetic) is from 2020.