[issue5956] test_distutils fails for Python 3.1b1 on MacOS X

Ned Deily added the comment: Another good reason not to install Stuffit or Stuffit Expander. These days OS X expands the standard open formats (i.e. .gz, .zip, .tar, etc) all by itself, and there are the standard command line tools as well. If you need Stuffit for actual stuffit archives, I

[issue5956] test_distutils fails for Python 3.1b1 on MacOS X

Jean Brouwers added the comment: Possible, I do not know and had never seen this before. Also, I just installed the latest (free) version 13.0.3 (Intel Build 165) of Stuffit Expander and the problem does *not* occur. But the older Stuffit 11.0.2 (Intel Build 627) still creates 2 files for

[issue5956] test_distutils fails for Python 3.1b1 on MacOS X

Antoine Pitrou added the comment: Ok, I was fearing some MacOS X-specific "feature" à la application bundles. Thanks for reporting the problem anyway :) -- resolution: -> invalid status: open -> closed ___ Python tracker

[issue5956] test_distutils fails for Python 3.1b1 on MacOS X

Amaury Forgeot d'Arc added the comment: Is it possible that Stuffit tries to unpack every compressed file found inside the tar file? the wininst*.exe files are templates for installers. They likely contain part of the signature of a ZIP file, and Stuffit would handle them as an archive to un

[issue5956] test_distutils fails for Python 3.1b1 on MacOS X

Jean Brouwers added the comment: Here are the answers to your questions. % python Python 2.6.2 (r262:71600, Apr 16 2009, 09:17:39) [GCC 4.0.1 (Apple Computer, Inc. build 5250)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> f = open('Lib/distutils/command/

[issue5956] test_distutils fails for Python 3.1b1 on MacOS X

Antoine Pitrou added the comment: Where does wininst-6.0.1.exe come from? I don't see it on a fresh checkout (there's only wininst-6.0.exe (without the ".1")). Does MacOS X create these "aliases" automatically? Did you install Python 3.1 or are your running directly from the source tree? -

[issue5956] test_distutils fails for Python 3.1b1 on MacOS X

Changes by Antoine Pitrou : -- components: +IO ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue5956] test_distutils fails for Python 3.1b1 on MacOS X

Antoine Pitrou added the comment: Ouch! Could you try to simply open() an exe file in the interactive interpreter? What does os.stat() give on this exe file? What does os.stat() give on a "real" directory? If some files are also directories under MacOS X, perhaps we must reconsider the director

[issue5956] test_distutils fails for Python 3.1b1 on MacOS X

Jean Brouwers added the comment: Another attempt to attach the image. -- Added file: http://bugs.python.org/file13979/Issue5956.jpg ___ Python tracker ___ ___

[issue5956] test_distutils fails for Python 3.1b1 on MacOS X

Jean Brouwers added the comment: Indeed, this is Python 3.1b1 built from source on MacOS X 10.4.1 Tiger (Intel). MacOS considers some of these win*.exe files directories. See the attached picture and below. % ls -l Python-3.1b1/Lib/distutils/command/win* -rw-r--r-- 1 jean jean 61440 Ju

[issue5956] test_distutils fails for Python 3.1b1 on MacOS X

Amaury Forgeot d'Arc added the comment: "Is a directory"? I suppose you are trying to install from a source tar ball? What happens when you try to "ls" this file? -- nosy: +amaury.forgeotdarc ___ Python tracker ___

[issue5956] test_distutils fails for Python 3.1b1 on MacOS X

New submission from Jean Brouwers : % make test test_distutils test test_distutils failed -- Traceback (most recent call last): File "../Python-3.1b1/Lib/distutils/tests/test_bdist_wininst.py", line 23, in test_get_exe_bytes exe_file = cmd.get_exe_bytes() File "../Python-3.1b1/Lib/d