> I am. Unfortunately, I don't even understand the problem you are talking > about, let alone being able to do anything about it. > > Regards, > Martin > > > I'll explain. (Please correct me if I'm making any mistakes here.) > > When you install a Python package in Windows, an .exe file is generated > for every script that your package defines.
How is that generated (i.e. what piece of code specifically generates it)? > What seems right to me is that the MSI installer will figure out where > the Python interpreter is on the end-user's system and then use that in > the shebang line. > > What do you think? That will be difficult. It will require a custom action to be generated when the MSI is produced, and that custom action must be scheduled into the InstallExecute sequence. Regards, Martin _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
