[Pythonmac-SIG] Re: Python on Mac OS X w/shared modules

Steven D. Majewski sdm7g@virginia.edu
Thu, 5 Oct 2000 16:06:17 -0400 (EDT)

On Thu, 5 Oct 2000, Martin v. Loewis wrote:

> >  I moved the fcntlmodule line in Modules/Setup above the '*shared*'
> > marker, and it seems to manage to import both, as long as I got rid
> > of the fcntlmodule.so from the previous build. ( Is this what you
> > were saying all along ? If it is, it wasn't clear until I actually
> > tried poking it myself. ) 
> That would certainly solve the problem for fcntl. It would still be
> good if the general problem is solved. Please note that DOS/Win raises
> an exception if the case on disk doesn't match the case in the import
> statement - that's still better than crashing, I guess.

Yeah -- I agree a better general and permanent solution would be nice!
And the Mac OS<9 version also raises an exception. It's probably all
in code that's disabled for unix, so it may just be a matter of 
figuring out how to turn it back on in the compile. 

But I think the main priority is to get a stable and installable 
version (with dylib) out there so folks can start porting all the 
Carbon (old Mac), Cocoa (next NextStep) and X11 libs. 

I'm sure none of that porting work will be able to make it in time
for Python 2.0 release, but maybe some of the build fixes can make
the cut. Do you know when they will stop taking bug fixes ? 

---|  Steven D. Majewski   (804-982-0831)  <sdm7g@Virginia.EDU>  |---
---|  Department of Molecular Physiology and Biological Physics  |---
---|  University of Virginia             Health Sciences Center  |---
---|  P.O. Box 10011            Charlottesville, VA  22906-0011  |---
		"All operating systems want to be unix, 
		 All programming languages want to be lisp."