import behaviour on Mac and Unix

[Steven D. Majewski]

On 8 Aug 2000, Igor V. Rafienko wrote:

 
> However, on Mac, the *exactly* same file (except perhaps for
> tranformation of Unix style newlines into Mac style newlines) can be
> imported, *but* module bar contains nothing but __doc__, __file__ and
> __builtins__. There is *no* reference to foo.


Are you SURE that the Mac file doesn't in fact have Unix newlines ? 
You would see that behaviour in that case. 


> In both cases, it's a standard Python-1.5.2 distribution. Furthermore,
> just to underline -- import does not fail on Mac, it simply does not
> fetch function/class names from the imported module. 

It should probably be considered a bug that we get this silent failure
for the wrong line endings. I would expect that it would fail, but 
I haven't looked at why it gets thru without an error. 


---|  Steven D. Majewski   (804-982-0831)  <sdm7g at Virginia.EDU>  |---
---|  Department of Molecular Physiology and Biological Physics  |---
---|  University of Virginia             Health Sciences Center  |---
---|  P.O. Box 10011            Charlottesville, VA  22906-0011  |---

"There's a new programming language called C+++. It's 50% better than C++, 
         but every time you compile, your modem hangs up."