Python Frameworks need testing

[Rainer Müller]

Bryan Blackburn wrote:
> A few initial notes, nothing major as yet:
> 
> - any reason you switched to tgz from the tar.bz2 (since that means  
> another download of the basic same file)?

I just wanted to use the same file type for all python ports. I could 
have switched all to bzip2 as well...

> - this may not affect anything at all, but most frameworks I've seen  
> have the Headers, Resources, and main library symlinked at the base of  
> the framework directory (and that CodeResources is new, so not sure  
> about that):
> 
> $ ls -l /System/Library/Frameworks/Python.framework/
> total 32
> lrwxr-xr-x  1 root  wheel   26 Mar 12 14:59 CodeResources@ -> Versions/ 
> 2.5/CodeResources
> lrwxr-xr-x  1 root  wheel   24 Mar 12 18:07 Headers@ -> Versions/ 
> Current/Headers
> lrwxr-xr-x  1 root  wheel   23 Mar 12 14:59 Python@ -> Versions/ 
> Current/Python
> lrwxr-xr-x  1 root  wheel   26 Mar 12 14:59 Resources@ -> Versions/ 
> Current/Resources
> drwxr-xr-x  5 root  wheel  170 Mar 12 15:00 Versions/
> 
> yours only has Versions...again, may have no negative effects at all,  
> but there's always the possibility someone, somewhere may be looking  
> for the base one.

Yes, I know that these symlinks should be there. But those symlinks are 
shared amongst all python ports and cannot be owned by a specific python 
port. The problem is, if the files are owned by one port and you 
uninstall it, those files will be gone as well.

So these symlinks will be created by python_select.

> - for some odd reason, ${prefix}/lib/libpython2.5.dylib built fully  
> universal (32 and 64 bit) whereas everything else is just i386:
> [...]

Interesting. I have no idea though why libpython gets build as 4-way 
universal. The build target is 'all libpython2.5.dylib' so this gets I 
doubt it somehow, but maybe because the Makefile is explicitly running 
/usr/bin/libtool? I didn't anything else special.

> Wait, the current non-framework python25 port does the same thing  
> (though obviously without Library/Frameworks.../Python), so it didn't  
> come in with the framework stuff.

Okay, so we should treat this as separate issue.

Rainer