Re: [Pythoncard-users] Python distribution problems

[Kevin A. <al...@se...>]

On Apr 4, 2005, at 10:03 AM, Alex Tweedly wrote:

> Schollnick, Benjamin wrote:
>
>>
>> I am unclear on what you are suggesting they are basing their 
>> decisions
>> on?  (The quote does not include it)  Presumably on the fact that they
>> need to instead Python, WxPython, and PythonCard?  Windows programmers
>> are fully aware of dependencies...  .Net anyone?
> True - they are aware of them - but that doesn't mean they like them. 
> I think it would be pretty cool to have the *option* of a single 
> download and install to do Python, wxPython and Pythoncard in one easy 
> operation. I have no idea how easy it would be to create that - but I 
> suspect it would overcome some people's concerns about the complexity 
> of getting started with Pythoncard.
>

First of all, I just want to make sure everyone actually found the 
install instructions at:

http://pythoncard.sourceforge.net/installation.html

Those are step by step and are supposed to be bullet proof. If there is 
a problem with them, like needing more images, more explanation at a 
particular step, please provide specifics on the needed changes.

Secondly, once we have a viable 1.x release, I would like to have a 
single installer option for Python, wxPython, and PythonCard on the 
Windows platform; Robin Dunn and I talked about doing this almost four 
years ago, but it doesn't make any sense until the parts of the big 
package are at a stable point like the combo of Python 2.3.5, wxPython 
2.6, PythonCard 1.0, etc. On the Mac, it will just be wxPython and 
PythonCard, since Macs already include Python. Given the various 
versions and combinations of Python and wxPython, the single installer 
will only support one combination. If possible, we'll do the same for 
Linux.

The installer scripts for py2exe (Windows) and py2app (Mac) are almost 
identical, in fact, Bob Ippolito sent me a script variation to deal 
with both in a single script. So, once the new standaloneBuilder tool 
is updated to support py2exe and py2app creating PythonCard standalones 
should be relatively painless. At Pycon, Bob fixed an earlier problem 
with how py2app renames the startup module, so people that have had 
problems with py2app should find that the latest version in cvs works 
correctly now with PythonCard; I don't know if/when he will have a new 
release of that outside of cvs.

ka