Rok Mandeljc

> It was verified that the script file runs well on Jupiter, and later.I converted the py file into an exe file using pyinstaller, but the following code appears when...

Yeah, symlinked executable is definitely not resolved to its original path on Windows at the moment, so that failure is not unexpected.

> Hey @rokm any recommended options to work around this problem? Unfortunately not. The Windows codepath in bootloader was not written with symlinks in mind.

> Are there any workarounds? Nope. We'll have to add an option to disable splash screen via environment variable to the bootloader. And then have the main process set that...

@ughstudios Would you be able to provide a minimum example that exhibits this behavior? I tried to reproduce it locally with a simple program that uses `multiprocessing` (`multiprocessing.Process`), but it...

> if splash is used together with [gooey](https://github.com/chriskiehl/Gooey), then will show again after click the start in gooey GUI. It can be reproduced by a very basic gooey example. @rokm...

> > if splash is used together with [gooey](https://github.com/chriskiehl/Gooey), then will show again after click the start in gooey GUI. It can be reproduced by a very basic gooey example....

> Is the fix already developed and launched? I am still facing this issue. > > ``` > if __name__ == '__main__': > from multiprocessing import freeze_support > freeze_support() >...

> I was trying to look into this issue, but I am having trouble finding out where `_PYIBoot_SPLASH` is defined in the [bootloader sources](https://github.com/paulmueller/pyinstaller/tree/splash_disable_on_subprocess/bootloader/src). Is there some magic happening that...

> That's not logging though – it's just a print statement. > > Since it doesn't do any logging, I don't think it makes sense for `pyi-makespec` to accept a...