Does not work with Nuitka

[txtsd]

Nuitka creates a single executable out of your python code.

I've used platformdirs in a project of mine called mcrpc. The code itself runs fine, but the executable created with Nuitka spits out this error:

λ ./mcrpc-linux                                                                  
Traceback (most recent call last):
  File "/tmp/.mount_mcrpc-h4h3HH/mcrpc.py", line 14, in <module>
  File "/tmp/.mount_mcrpc-h4h3HH/platformdirs/__init__.py", line 33, in <module platformdirs>
  File "/tmp/.mount_mcrpc-h4h3HH/platformdirs/__init__.py", line 29, in _set_platform_dir_class
  File "importlib.py", line 127, in import_module
ModuleNotFoundError: No module named 'platformdirs.unix'

It spits out a similar error on windows:
ModuleNotFoundError: No module named 'platformdirs.windows'

Is there anything that can be done on platformdirs' side to help it work well with Nuitka? You can try using the executables from v1.2.

[gaborbernat]

PRs welcome, but I'm not a Nuitka expert to tell 🤔

[txtsd]

Tried it with appdirs instead of platformdirs, and there is no such error in the binary.

[gaborbernat]

Not sure how that's relevant here.

[txtsd]

platformdirs is a fork of appdirs. Whatever's causing the problem was introduced within this fork.

[gaborbernat]

A lot of things changed, so I don't think that helps in any shape or form. And while it started as a fork, today is more like a complete reimagination of it with just the API being similar. And likely that information will be completely useless to track down and fix the issue. Just to spell out, a PR would be welcome on this, but don't expect the maintainers to act on this otherwise.

[txtsd]

Fair enough. Thanks for the explanation.

[ofek]

The issue is the dynamic imports https://github.com/platformdirs/platformdirs/blob/2.4.1/src/platformdirs/__init__.py#L20-L33

Changing to actual import statements and executing the logic outside of that function should fix it.

[ofek]

@txtsd Can you try?

[Clouder0]

For Nuitka you can specify --include-package=platformdirs and everything will be fine.

From my personal perspective, I don't think it makes sense to use dynamic importing for several fixed platforms. Kind of overkill I suppose.

[Julian]

If there's an option in nuitka to make things work, I'd vote for closing personally. Things which do "odd" packaging things (or users of them) are responsible for making things work, so long as we are doing "normal" python things. Overkill or not, what's here is perfectly well specified Python behavior.

[txtsd]

@gaborbernat GLORIOUS!