On Fri, 2005-07-22 at 10:55 +0200, normanwinn wrote:
> I am trying to get going again with PythonCard. Since last using it I
> have installed Python 2.4 and wxPython 2.6.1 (unicode).
> I have a copy of PythonCard 0.8 in site-packages in the Python 2.4 folder.
> I have run setup.py in this PythonCard folder.
> When I start the Code Editor and run a script it still used Python 2.3.
> Could you tell me why?
That's because the start menu entry for the code editor launches it with
i.e, it explicitly runs it using Python 2.3, which is fine, since that's
what you had installed when you first installed PythonCard.
> The Sample Launcher opens a shell and then dies.
The start menu entry for the samples launcher is set up as:
So this relies on the Windows file association for a '.py' file in order
to determine how to run it. The Python 2.4 installer changes the
assocation for .py files so that they get opened using Python 2.4
instead of Python 2.3. You haven't added PythonCard to your Python 2.4
installation, therefore it breaks as soon as it sees the line:
from PythonCard import about, dialog, model
In the samples.py code.
What I'd suggest you do is simply re-run the PythonCard installer but
this time select 'C:\Python24' as the directory to install in, and
change the name of the program group to something like 'PythonCard
(py2.4)'. Then check and edit the shortcuts in each program group so
that they use the correct Python version.
> Without wishing to moan, why does it take so much knowledge to upgrade
> things in the python world? Why, when I install 2.4, am I not asked if I
> want to convert/upgrade all my python stuff to use 2.4?
Well, moaning is a perfectly valid emotional outlet, so don't feel bad
about it. A problem shared, and all that. :-)
It's quite okay to have multiple Python installations if that's what you
want to do. The problem is that it's not what *most* people want to do.
Democracy's only a good thing if you agree with the policies!
Every time a new version of Python was released, the team would have to
write code to upgrade installations under previous versions. This code
would have to be able to cope with all the possible combinations of
upgrade paths across multiple versions, i.e py1.5 to 2.4, 1.6 to 2.4,
2.0 to 2.4, etc, etc. It would be a nightmare to write, let alone
Personally, I quite like the fact that Python doesn't try to force a
particular way of working on you. I find it more irritating when
software I install makes completely unjustified assumptions about what I
want to do with it - I'm a responsible adult, I'd much prefer to be left
alone to make my own decisions, thank you very much. :-)
Hope this helps, Norman, good luck.