RE: [Distutils] more clashes between 'build' and 'bdist_wininst'

From: Stefan Seefeld [mailto:seefeld@sympatico.ca]
I would thus expect the installer to do the same trick again, i.e. modifying the first line of my scripts to point to the right interpreter, not the one used during the build.
Am I missing something ? Is this a bug ?
The #! line is not relevant on Windows, and so its contents don't really matter. Paul.

Moore, Paul wrote:
From: Stefan Seefeld [mailto:seefeld@sympatico.ca]
I would thus expect the installer to do the same trick again, i.e. modifying the first line of my scripts to point to the right interpreter, not the one used during the build.
Am I missing something ? Is this a bug ?
The #! line is not relevant on Windows, and so its contents don't really matter.
Hmm, I was confused, sorry. I'm trying to run the script from within cygwin, so it *does* matter. However, I can't run the script from cygwin as is anyways, as the very mechanism of finding the interpreter, and passing it the file name, doesn't work because the file name would need to be translated via 'cygpath' first anyways. It seems I need a wrapper script in any case. Thanks, Stefan

I'm new to the list, but I would argue that if the line doesn't functionally matter then the next important point is user/developer expectation (ie, I *expect* that line to point to something relevant, or it shouldn't be there). Therefore, I'd propose the behavior change on windows to either: 1) point to the correct python, or 2) be removed so it's not confusing. --Ivan
-----Original Message----- From: distutils-sig-bounces@python.org [mailto:distutils-sig-bounces@python.org] On Behalf Of Moore, Paul Sent: Wednesday, September 17, 2003 9:02 AM To: Stefan Seefeld; Distutils-Sig@Python.Org Subject: RE: [Distutils] more clashes between 'build' and 'bdist_wininst'
From: Stefan Seefeld [mailto:seefeld@sympatico.ca]
I would thus expect the installer to do the same trick again, i.e. modifying the first line of my scripts to point to the right interpreter, not the one used during the build.
Am I missing something ? Is this a bug ?
The #! line is not relevant on Windows, and so its contents don't really matter.
Paul.
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distut> ils-sig

"Ivan R. Judson" <judson@mcs.anl.gov> writes:
I'm new to the list, but I would argue that if the line doesn't functionally matter then the next important point is user/developer expectation (ie, I *expect* that line to point to something relevant, or it shouldn't be there). Therefore, I'd propose the behavior change on windows to either:
1) point to the correct python, or 2) be removed so it's not confusing.
Sounds sensible. Does anyone care enough to write a patch? Thomas
participants (4)
-
Ivan R. Judson
-
Moore, Paul
-
Stefan Seefeld
-
Thomas Heller