[Pythonmac-SIG] Python on on a second drive

JoanCarles p Casasín joanca@typerware.com
Fri, 13 Oct 2000 14:06:04 +0200


At 12/10/00 22:27 Jack Jansen wrote:

>There's a bug report on the sourceforge site that having Python on a
>second drive causes problems with warm restarts (they don't proceed
>past the happy mac state). Actually the problem may be only with
>removable drives, the bug report isn't very clear, and it is anonymous 
>so I can't ask the original submitter.
>
>The submitter seems to think that the problem is with PythonCore being
>an alias to an external drive. I can hardly imagine this, but I can't
>test it as I don't have a second drive.If someone could give this a
>try that would be helpful. Also, if it indeed turns out to be a
>problem i think a workaround may be to set the "File has no INIT"
>flags on the alias file, so if  that could be tested too I'd be very
>happy... 

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 thing 
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 with 
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...

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, and 
inited) were checked in the alias file. I don't know if this is what you 
meant. I'm off of being an expert.

But *never* had the problem with the "happy mac" locked and always (as 
far as I remember) had Python in a second drive.

Hope this helps, at least a bit.

Cheers,

-> jc, tw®