Using PyInstaller (or similar) to create an executable

Hi everyone,

I got this run from the pynsist github repository, I got it to work with pynsist, but sadly I need it to work with pyinstaller instead. I have no idea what I am doing but I tried combining the run from pynsist and hmadevs method (excluding --clean), and almost got a working exe file. The only problem is when I open the exe it creates web browser on an infinite loop. Based on what I have gathered it the problem is from the subproces. So can anyone help me figure this out?

from subprocess import Popen, PIPE, STDOUT
import sys
import time
import webbrowser

def main():

# Getting path to python executable (full path of deployed python on Windows)
executable = sys.executable

path_to_main = os.path.join(os.path.dirname(__file__), "")

# Running streamlit server in a subprocess and writing to log file
proc = Popen(
        # The following option appears to be necessary to correctly start the streamlit server,
        # but it should start without it. More investigations should be carried out.

# Force the opening (does not open automatically) of the browser tab after a brief delay to let
# the streamlit server start.

while True:
    s =
    if not s:
    print(s, end="")


if name == “main”:

For some, the following approach may work well:

It can make sharing a streamlit application as simple as emailing a html file.


Hi @SimonBiggs! Do you have any availability for that video call that was discussed a while ago? To use your method for making an executable?

Yup, for sure. Would both you @OneYoungLion, and @AntonisCSt be able to meet together first, compare notes, detail on here what you have tried, and where you have struggled, as well as formulate some clear questions. Then once you both have helped each other as much as you can, let us three (and any others who are interested) jump on a video call to see how I can help.


I believe the question has been discussed enough already. Here, on Github, and in our email correspondence a few months ago. In my opinion, this forum, and this thread, would make a great place for you to share your thoughts and the potential solution with the community. Otherwise, I’ll work around the issue or seek the solution elsewhere. This is for a hobby project and I don’t think I should keep the final step hostage anymore. Thanks.

Fair enough :slight_smile:.

The time goes to unpacking the files, since the exe was created with --onefile.

Hi @AntonisCSt, @OneYoungLion, and others,

As of last week I have successfully bundled a Streamlit application with PyOxidizer and Electron. I have written up the following draft document that details how I achieved it:

If you were interested in taking the approach for a spin I’d be keen for your feedback on the document. Also, for any questions about it, it might be best to create a post over on the PyMedPhys discourse forum:



Hi @SimonBiggs ,

Thanks for writing and sharing this guide (and also for PyMedPhys, neat tool).
However I feel like your guide is for now indeed a draft: the PyMedPhys project is quite big, and following the guide by looking at the codebase while trying to replicate a mininal working example for a small standalone streamlit app is almost impossible. Would you be willing to provide a smaller, self-contained, example app ? I’m willing to help on such a project.


1 Like

Hi @the-dharma-bum,

Yes, I’d be happy to set up a minimal example, and your help would be much appreciated. I was just about to make a standalone repo for one of my products. I’ll set up the repo, send through the link, and get started.

Once we’ve made the minimal example I’ll continue to build on top of the repo, but we can make a branch/release tag that hangs around and is referenced within the docs for those who want to go back to the beginning and see the minimal example.

What do you think about that?


Hi @the-dharma-bum,

So, I have created a “bare bones” example over at:

Let me know if that meets yours and others needs :slight_smile:.


Hi @SimonBiggs,

Wow ! Thank you so much for your quick reply and your work ! It’s exactly what I had in mind.
I think the coolest part of your work is the Electron embedding and the use of Github Actions, allowing for deployment on any OS, so that would be a good thing to add to this minimal example, while still keeping things simple.
I submitted a PR with the code to build the Electron app (which I tested successfully on Debian) which is basically your PyMedPhys code.
I guess there’s only the Github Actions to set up. I think we can continue this discussion on the github repo ?
Anyway, thanks again !


My pleasure, I hope it is helpful :slight_smile:. Let’s make sure to post a link back on this forum to the final pinned branch that we think will be most useful for everyone :slight_smile:.


Hey Simon and @the-dharma-bum,

Mind if I join in on the fun? I’m trying to replicate what you have done Simon, but am running into issues. It probably stems from lack of understanding of pyoxidizer, poetry, node, yarn, essentially everything you have used to create your app.

I guess to start from the top, installation:

  • pyoxidizer
    • Instructions.
    • Ran the following in CMD prompt:
      pip install pyoxidizer
  • poetry
    • Instructions
    • Ran the following in Windows (Powershell):
      (Invoke-WebRequest -Uri -UseBasicParsing).Content | py -
  • Node
    • Instructions
    • Downloaded and installed Node.js 16.17.0 LTS.
    • Funny Story… This also deleted Python from my computer. I clicked the button which said “Automatically install the necessary tools”, which I guess also installs Python. It tried to install Python 3.10, said “Install Fail” and once it finished doing everything else, I tried to use pip and was told told “No Python”.
  • Yarn
    • Instructions
    • Ran the following in CMD prompt:
      • npm install --global yarn
      • npm install -g npm@8.18.0

Once I had everything installed, I began to run down your instructions.

Just as an FYI, I’m not working on github, just my local desktop.

First, it seems like I need to configure my pyoxidizer.bzl config file. I’m looking at the example you provided here, and this is where I start to get lost. Specifically, what do I need to change in here to point to my streamlit application? I’m looking back and forth between what was written for Enopios and the pymedphys .bzl files and am making the best guess and am changing the following to match my .py files:

#python_config.run_module = "pymedphys"
python_config.run_module = "_Introduction_And_Setup"

    #exe = dist.to_python_executable(
        #name = "pymedphys", etc.,

    exe = dist.to_python_executable(
        name = "_Introduction_And_Setup",
        packaging_policy = policy,
        config = python_config,

That’s the only thing I can see to update.

Next, looking at poetry, I’m familiar with virtual environments, but normally use pipenv to manage mine, but I’m willing to give poetry a try. Launching CMD Prompt from the project folder, I used, poetry init and went through the steps to set up the dependencies I use in this project. Looking at the repo posted for Enopios, the readme states I should use the following to create my requirements.txt:
poetry export -f requirements.txt --output requirements.txt

Then I use:

poetry run pyoxidizer build

However, I kept getting the following error:

In --require-hashes mode, all requirements must have their versions pinned with ==. These do not:
setuptools>=18.5 from (from ipython==8.4.0->-r requirements.txt (line 275))

researching the error led me to adding --without-hashes to the end of the command like so:

poetry export -f requirements.txt --output requirements.txt --without-hashes

and then reran the pyoxidizer command. Which is now erroring out on “exe.add_python_resources(exe.pip_install([”.“]))”. and after working on this some this past weekend and all day today, I’ve ran out of ways to troubleshoot this myself and am now asking for help. Thank you!

1 Like

Most certainly :slight_smile:. As a first step in helping you here, would you be able to confirm that the issues you are detailing occur when building off of the minimal example produced over at:

Cheers :slight_smile:,

Hi @CBrown,

This seems to be an issue with pip itself.
Can you share your Python version, your pip version, your poetry version, and your pyproject.toml file ?

As for the NodeJS issue, I think it would be best to install it through Node Version Manager.

I’m making a guide of the whole process for Linux & Windows that will appear on the Enopios repo within the week.

1 Like

None of the issues occur when I use the minimal example build. Is this correct, the total file size is 178mb?

Hehe yup. Other bundler methods (like pyinstaller) attempt to strip out unused components and just deploy that which is utilised. However, this “stripping out” process can often cause weird edge cases that don’t align between normal python and the distributed version. And this… costs a lot of developer time.

…so… here I have made the trade off of developer time being more important than the final distribution size, and, the entire Python distribution, unfettered, is distributed. (Depending on your use case, a different trade-off might be appropriate)

…so… 178mb is just what you get when streamlit installs all of its dependencies + a complete batteries included Python distribution.

Hi Simon,
Thanks for sharing.

After I downloaded your barebone example and tried to execute it in powershell, I got an error like that.

Since I haven’t used poetry before and it’s my first time trying to create an exe file. I have no idea what’s going on there and I guess something is missing (in my computer)? Would you have time to give a glance at this pic and help me out?

Hi @sss163ii,

Welcome to the streamlit community :slight_smile: .

I’m not immediately sure what might be causing your issue. I might get a chance to have a look later on this week. Might you be in a position to raise an issue on the GitHub repo?