Thanks for your answer. Despite numerous tries, the intricacies of pythons packages and modules, and the various packaging possibilities are still very blurry for me… I’ll try to correct my project structure as you suggest (I will keep the src-layout though because I saw it suggested on numerous places, like https://packaging.python.org/en/latest/discussions/src-layout-vs-flat-layout/) and I’ll come back here to give the result. I don’t understand though, why it works locally installed under Linux and Windows and with pip on Linux and Windows, and also with the pyinstaller+inno-setup installer made locally, but not with the pyinstaller+inno setup installer made on github actions.
Gaël Le vendredi 23 août 2024 à 21:59:28 UTC+2, bwoodsend a écrit : > Your project structure is somewhat defunct. Those `src/__init__.py` and > `src/__main__.py` files imply that `src` is a package and `yaas.py` is the > submodule `src.yaas`. That's reflected in the wheels on PyPI which are > installing `__init__.py` et al directly into `site-packages`. > > I'm guessing you really want a package called `yaas` in which case you'd > insert a `yaas` directory (e.g. `src/yaas/__init__.py`) (personally I'd > ditch the `src` and just use `yaas/__init__.py`) then adjust all the > internal imports to use `from yaas import worker` instead of `import > worker`. > > Once you've made that change and dealt with all the collateral damage that > the refactor causes, PyInstaller should stop objecting to your modules not > being where they're supposed to be. > -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/pyinstaller/f16ea1c5-55bb-4ea9-9d46-3fcb9d97f8b1n%40googlegroups.com.
