Alex Railean

The test on *Python 2.7.12* was successful, I reloaded the module a couple of times via `.reload ` and the behaviour was as expected. This was very satisfying, I must...

`distribute 0.6.24` Something like this in `setup.py` would do the trick: ``` if sys.version_info[0] < 3: requires.append('backports.ssl_match_hostname') # remove entries with adnotations that are not supported by older versions #...

What prevents this update from being part of the current release? Is there something I could to do make it happen? The tests above were successful and I would love...

This is what the output looks like: ``` ``` And this is output from a clean virtualenv of Python 3.9, which produces a working binary ``` ```

Yes, the action happens on the same computer.

Here are the paths for the working binary: ``` ['/home/alex/projects/nuitkatest', '/usr/local/lib/python39.zip', '/usr/local/lib/python3.9', '/usr/local/lib/python3.9/lib-dynload', '/home/alex/projects/nuitkatest/venv39/lib/python3.9/site-packages'] ``` And the associated report ``` ``` Here are the paths for the failing attempt: ```...

> I understand however, that in your case, in the non-working environment, it's not there. Hmm, now I get it - the environment was indeed not activated. I mistakenly thought...

And what's the error message? In what way does it not work? Give us the details, otherwise we cannot help.

It is possible that the way the obfuscator works makes it non-obvious that the file is imported, so Nuitka isn't aware of this dependency. Try to explicitly add `import pytransform`...

Update: after another cycle, I stopped at the next thing: `FATAL: Error, error exit from AppImage because fuse kernel module was not loaded`. The same rationale applies here, it would...