No actual examples of packaging an application as a standalone single *.exe file?

[James Adams]

I would like to use PyOxidizer to create a distributable application built for Windows, MacOS, and Linux.

I primarily develop my Python application on Linux (Ubuntu 18.04).

The examples in the documentation don't appear to be relevant to my use case, although it may be that I'm just not understanding the gist.

My Python application utilizes OpenCV for reading image frames from a video stream and performs object detection and facial recognition on the images using TensorFlow, Keras, and Caffe models. I want to create an executable that can be used to launch the application by users who are not familiar with Python and who most likely won't/can't install the application into a Python environment. According to this article this is possible (and is the marquee feature of PyOxidizer), but the examples in the documentation all show example usage of "pyoxidizer run" rather than launching a *.exe file. What am I missing here? Is there an example of creating a single .exe for an application using PyInstaller that I've just not discovered yet?

Thanks in advance for any comments or suggestions.

[gnp...@gmail.com]

On Tuesday, July 2, 2019 at 12:40:17 PM UTC-7, James Adams wrote:

I want to create an executable that can be used to launch the application by users who are not familiar with Python and who most likely won't/can't install the application into a Python environment. According to this article this is possible (and is the marquee feature of PyOxidizer), but the examples in the documentation all show example usage of "pyoxidizer run" rather than launching a *.exe file. What am I missing here? Is there an example of creating a single .exe for an application using PyInstaller that I've just not discovered yet?

The "pyoxidizer run" command actually does exactly this -- it creates that single executable file, and then just runs it. The getting-started doc alludes to this:

> The default project created by `pyoxidizer init` will produce an executable that embeds Python and starts a Python REPL by default

but isn't super explicit about it and doesn't demonstrate with an example. I agree it'd be helpful for that doc to be a lot more explicit about showing how to get your hands on the actual executable file.

There's a much more specific discussion in the more detailed "managing projects" page which that getting-started section links to. It tells you exactly where to find the executable file. If you use the `pyoxidizer build` command, it also prints a handy hint at the very end of its output.

(BTW I'm not an expert -- just another interested potential user.)

Cheers,

Greg

[James Adams]

Thanks, this was helpful, and provided an impetus for me to try again.

I've still not managed to make everything work as expected, but I feel like I'm getting closer. My current issue is described here: https://github.com/indygreg/PyOxidizer/issues/99

[Greg Price]

Glad to hear it! I think that GitHub thread is a good place for the detailed troubleshooting discussion, too.

Greg

--
You received this message because you are subscribed to a topic in the Google Groups "pyoxidizer-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pyoxidizer-users/rUyM3iTpZq0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pyoxidizer-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pyoxidizer-users/f63d4992-7ea9-4df5-8cbf-1d1d8f62ae8b%40googlegroups.com.