Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #20936 > unrolled thread
| Started by | Andrea Crotti <andrea.crotti.0@gmail.com> |
|---|---|
| First post | 2012-02-27 13:57 +0000 |
| Last post | 2012-02-27 13:57 +0000 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
windows executable calling python script Andrea Crotti <andrea.crotti.0@gmail.com> - 2012-02-27 13:57 +0000
| From | Andrea Crotti <andrea.crotti.0@gmail.com> |
|---|---|
| Date | 2012-02-27 13:57 +0000 |
| Subject | windows executable calling python script |
| Message-ID | <mailman.196.1330351081.3037.python-list@python.org> |
I am creating an installer for python projects, using CMake and NSIS. Now my goal is to be able to select at installer time the python executable that will run that project, and then associate them. I saw that setuptools is able to generate exe wrappers, but how does that work exactly? From what I've understood there is some compiled C code that somehow calls the python script, is that correct? Supposing I ship this executable in the same directory of the python script (with a known name), is there a way to make it run the right python interpreter? The best and easiest solution would be to generate the full installer with PyInstaller or similar, but unfortunately that doesn't work yet, and we would still need both approaches anyway.
Back to top | Article view | comp.lang.python
csiph-web