Georgios Papadoulis

> PyQt is incompatible and won't be supported. Had no idea. The first three commits are fixes so that Ryven works with both PySide2 and PySide6. They also include a...

The changes were minor, so I believe they should be noted here instead of having to re-arrange the whole PR. I can edit the PR description to include what needed...

How should we proceed? As is and mention pyside changes in the description or remove all the other stuff and include them in a new PR?

Happy new year! > I can try to cherry-pick relevant changes here to initiate another PR. I'd suggest you keep all the changes, most of them were replacing deprecated qt...

These are the only two changes that have nothing to do with pyside6. Feel free to remove them if you deem it necessary, I have all my changes saved in...

> Just to clarify, I am using Python 3.11.4 I've been testing on 3.10 so I could test pyside2 and pyside6 as well. I think what's important here is checking...

> Interesting, did you profile it? What part of loading is causing this, is it the actual inspect.getsource() call? I did profile it. Here's a snapshot of importing the build_in...

> Could you show a flame graph of the whole process of importing a package using a profiler? Currently I don't have time for this and I don't know if...

I added the GUI part of this in the StartUpDialog in the open PR. I believe that the option should start as enabled. We want the users to start with...

Had this problem as well. You just saved me the trouble of searching where the issue is. I think a better approach would be to let the user initialize the...