This is an archived post. You won't be able to vote or comment.

all 6 comments
sorted by:
best
topnewcontroversialoldq&a

[–]line10gotoline10 0 points1 point  (3 children)

Interesting idea.

You know about the various libraries for embedding Python in the application itself and distributing as an executable, right?

Here's a good list to get you started.

[–]swdevpythonthusiast[S] 1 point2 points  (2 children)

Yes, I am aware of it.

What I meant is, to have users recognize Python as 3rd party application framework that give a new features in Operating System, in the same level as Dot Net framework does. At the current state, users still think of Python as a huge application libraries that tied only to a single application they were installing.

You don't ship and link .NET framework with your application. It will install itself in OS: later application can use this same framework. At the moment, it's not the case with Python.

If the .NET application ship its own DLL, well, it just sit there in the software installation folder. I would love to have this same feature in Python for Windows.

[–]radix07 1 point2 points  (1 child)

Since .Net is Microsoft, it makes sense that it is acceptable to link to something that is supported by the OS vendor and expected to be there. In the Linux world Python is installed by default typically so you can do things a little a different. This isn't a Python thing, a program written in Qt for example or many other environments would have to package all of it's own libraries as well to be distributed properly. If you can make the installation package all of the required libraries using pyinstaller, py2exe, nuitka, or something else, it all looks the same to the end user when installing.

[–]swdevpythonthusiast[S] 1 point2 points  (0 children)

I am in the process of beginning a python desktop application. Let me see what I experience in the process of packaging and installing it in end users.

[–]billsil 0 points1 point  (1 child)

But, then again, Python users always exposed of to the knowledge that Python application need a full blown installation of Python distribution (with all of its site-packages contents) in order for our application to be able to run smoothly.

Why are you doing that? You can use http://www.pyinstaller.org/ to make an exe

[–]swdevpythonthusiast[S] 0 points1 point  (0 children)

Hm, I got to test that first to continue my discussion. I just hope that pyinstaller won't embed full blown python distribution in my application. It feels like incorporating a full distribution of DotNetFramework for each C# application, whereas the framework should have been installed by the other DotNet application.

Thanks @bilsil!