From: normanwinn <nor...@on...> - 2005-07-23 07:53:24
|
Thank you for the replies. I am not going to deal with each comment on the difficulty of upgrading in the Python world but give my further thoughts. What I think is needed when upgrading is the offer to take the simple path. That is to get rid of the old and install the new. In the world of Basic (that is what we all want to replace, isn't it?) I would be offered such a choice. OK, I may not get offered an upgrade path from version 1 but would be from 2.3 to 2.4, say. I know that it is a lot of tedious work to analyse each bit of user code to test where it will break under a new version and offer to convert. But if the FOSS world really believes that is can carry the average user then this work will need to be done. If that is not what people want to do then they should say so. In the case of PythonCard itself it seemed reasonable to believe that if, when I invoke Python, I get 2.4 then after running 'python setup.py install' in the PythonCard directory that all would be well. I looked in the 'tools\codeEditor' folder and there is no setup.py there. It is possible that the problems are mine. In truth, the only time I have felt I really understood what is going on in computing is when I programmed in assembler (and in C), either on various computers or micro-controllers. There, one has to understand what is happening everywhere, in memory, in registers et al. I seem incapable of 'knowing' when I can't see the whole picture. No doubt it is laziness that has stopped me from getting the whole Python picture. Once again, thank you for your replies, but I think I think I give this a miss for now. Life is too short, Norman -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.9.4/57 - Release Date: 22/07/2005 |