[Pythonmac-SIG] Python on on a second drive

[Jack Jansen]

> I've been working with Python (though not hardly) in a second drive for=
 =

> quite time and never happened something like that. The only strange thi=
ng =

> that happened and happens is that  with my last machine (G4, with MacOS=
 =

> 9.0.4) I've to launch 'Configure Python' each session I want to work wi=
th =

> an app with Python embedded. Otherwise it can't find "PythonCore". This=
 =

> was reported by me (and some other guy) to the list, but we could never=
 =

> have other solution than having 'Configure Python' as a StartUp Item...=


Ah... Now we're getting somewhere! At least: we're getting somewhere with=
 your =

problem. My guess is that because the PythonCore alias points to another =
disk, =

and that disk is not mounted yet when MacOS starts looking for INITs in t=
he =

Extension folder it will somehow break the alias (probably while trying t=
o =

resolve it).

> Now I've tried to set the (finder) flag to "File has no INIT" (with =

> ResEdit), once restarted the same happened, and both flags (No init, an=
d =

> inited) were checked in the alias file. I don't know if this is what yo=
u =

> meant. I'm off of being an expert.

Hmm, yet another good idea out the window.

Does anyone else know of MacOS problems with aliases in the Extensions fo=
lder? =

I do notice that PythonCore is the only alias I have in the extension fol=
der =

on my machine, so maybe it isn't a good idea to have aliases there in the=
 =

first place?
--
Jack Jansen             | ++++ stop the execution of Mumia Abu-Jamal ++++=

Jack.Jansen@oratrix.com | ++++ if you agree copy these lines to your sig =
++++
www.oratrix.nl/~jack    | see http://www.xs4all.nl/~tank/spg-l/sigaction.=
htm =