Re: [Pythoncard-users] Re: Item missing from PythonCard 0.8 install?

[Andy T. <an...@ha...>]

Kevin Altis wrote:
> Thanks for catching this Jim!
> 
> Once again I failed to respect the authority of distutils and ended up  
> getting slapped. I updated the setup.py script but forgot to update the  
> MANIFEST.in file, and I didn't include a sub-package as well, so the  
> templates and templates.dialogs package was missing.
> 
> I guess at this point simply getting verification that anyone is able  
> to install and run everything correctly on each platform would be good  
> just to make sure I haven't blown anything else. One thing that I will  
> mention is that on the Mac (and probably Linux) it is critical that you  
> use sudo to install the package, otherwise distutils doesn't copy all  
> the files for some reason. This is mentioned in the install  
> instructions, but it is worth repeating.
> 
> I went ahead and uploaded new versions of all three files to  
> SourceForge, but didn't change the version number. Here are the new  
> file sizes:
> 
> PythonCard-0.8.zip - 1,361,078 bytes
> PythonCard-0.8.tar.gz - 1,127,311 bytes
> PythonCard-0.8.win32.exe - 1,636,223 bytes
> 
> There is one other bit of weirdness on the Mac that I don't really  
> understand since I don't remember distutils doing this before. It is  
> copying all the package files to /Library/Python2.3/PythonCard and then  
> creating a build directory with lib/PythonCard and scripts-2.3 dirs  
> inside that. Does Linux do that too? Perhaps I need to revise the  
> commands I run and/or setup.py script, but this is clearly wrong,  
> though harmless, except for burning additional disk space. Did I  
> mention that distutils is my nemesis? ;-)
> 
[snip]

Hmm, I think it might just be you Kevin ;-) Downloading the tarball from 
  SourceForge on my linux machine and running 'python setup.py install' 
gives me the build directory under 
/usr/lib/python2.3/site-packages/PythonCard

But, when I do a fresh check out of the PythonCard module and build my 
own tarball (using 'python setup.py sdist --formats=gztar') the problem 
disappears.

When I do the same thing on my Mac I see the same problem that you do. 
Ergo, it's a bug in Python 2.3.0 which was fixed in one of the releases 
up to 2.3.4 (which I'm running on Linux).

Do you want me to build a 0.8 tarball on my machine? Or should we wait 
until a few more fixes are in and include this in 0.8.1?

Regards,
Andy
-- 
--------------------------------------------------------------------------------
 From the desk of Andrew J Todd esq - http://www.halfcooked.com/