[Pythonmac-SIG] Python 2.2.2 and Tkinter installation problems on OS X

[Jack Jansen]

On Wednesday, Nov 27, 2002, at 01:08 Europe/Amsterdam, Nicholas Riley 
wrote:

> The second example gave me a clue.  It was a permissions problem;
> struct.so was installed like this:
>
>   -rwx--x--x    1 root     admin         61k Nov 26 12:39 struct.so*
>
> After fixing the permissions, codecs and Tk in pythonw work properly.
> Hooray!
>
> What needs fixing in Python, IMO, is:
>
> - The permissions on installed files in lib/dynload should be properly
>   set.  Perhaps it picked up my umask, which is 077?  But then they'd
>   be rwx------, so I don't know...).  Using the 'install' program to
>   install files is usually the right way to do this, as it uses
>   rwxr-xr-x by default.

Could you check that you can reproduce this (i.e. if umask is 077 you 
get rwx--x--x files and
if umask is, say, 022, you get rwxr-xr-x)? If so, post a sourgeforge 
bug report on this, please.
I'll have to investigate what goes on, and whether it's MacOSX-specific 
and whether we want to fix it.

> - "no module named struct" should be distinguished from "can't access
>   struct module to import it".

That's difficult. After the import failed (due to the file being 
unreadable) import will continue
looking in other sys.path entries, so by the time it gets to the end it 
will have forgotten
about any intermediate errors.

Have you tried what "python -v" and "python -vv" report in this case?
>
> - In the third case of pythonw, the import error was somehow
>   suppressed; it should be displayed.  If it were, the resultant
>   error would not be so cryptic.

Agreed. I'd also be interested in the python -vv output of this.
--
- Jack Jansen        <Jack.Jansen@oratrix.com>        
http://www.cwi.nl/~jack -
- If I can't dance I don't want to be part of your revolution -- Emma 
Goldman -