Kay Hayen

This is now on the develop and the commercial staging branch and part of the latest pre-release, will be part of the 2.1 release that will eventually follow.

This is part of the 2.1 release I just made. For some reason, Linux and macOS trigger assertions when loading a DLL, this is apparently not covered yet.

Am I seriously to guess to OS here, because the issue template cannot be filled, missing requested --version output?

From the looks of it, this is purely a single extension module. I took note of a `py.typed` data file, that is a kind of type that should never be...

Oh my goodness, looking at the C code, the extension overloads `__getattr__` like all the cool kids now, to deliver attributes of `apsw` from `apsw.shell` because why not.

I thought it was delegating more stuff, but it still adds a hidden dependency I guess: ``` static PyObject * apsw_getattr(PyObject *module, PyObject *name) { PyObject *shellmodule = NULL, *res...

I used `--python-flag=-v` and found no imports that it attempts at all. It seems the module should only ever remain empty if `init_exceptions` fails. But then it also returns NULL,...

Yes, I understand that is unrelated, although a problem for some uses by itself. But I don't know why that happens at all. I would have to debug the C...

Unfortunately I do not think I can afford the time to debug this outside of Nuitka commercial, somebody else needs to build this and single step/trace the extension module C...

Typical reasons why extension modules do not work a) Nuitka doesn't include all of stdlib by default. Module code attempts import, and handles lack of module more or less clearly....