Different approach to wrapping

[SageCreations]

@AlbertShown , I just noticed you updated the wrapper. Thanks for that as I'm trying to push for it's use in a project at my work. I've forked the project and was experimenting with a different approach that might be easier for maintainability if you want to take a look. I was targeting 2.5.0.beta-2 of the C version and heavily documenting it all so that IDE's can explain functions better.

my fork

I've separated all the c-python in one file, and left only the python wrapper functions/classes in the webui.py file. The library loading functions is in its own script and is only used in the c-python file. This makes most of the wrapper functions just a couple or even single lines long.

[AlbertShown]

I like your fork, and yes, feel free to merge your fork into the python-webui repo.
I just created a PR in your fork with some minor changes.

PR: SageCreations#2

[SageCreations]

Just merged, not sure how the PyPi publish system works but that still needs to be ran so that that users can actually install using the pip install command.

[AlbertShown]

I have the private key (shared by the original project creator).
I guess we can create an auto PyPi updater (will securely read private key) like we did for the auto website uploader (securely reads the FTP password). However, I will try to add a new secure variable that have the PyPi private key.

[AlbertShown]

FTP uploader: https://github.com/webui-dev/website/blob/main/.github/workflows/ftp.yml

[SageCreations]

I'll get started on the documentation examples needed for the website docs in the meantime.