[Pythonmac-SIG] IDLE and MacPython 2.5

[David Worrall]

There was a time a while ago when IDLE was a pain/unstable etc etc on  
intel OSX
and I guess I just gave up. I used to use it all the time.
Perhaps it works ok these days.
Stopping to sharpen one's axe is ok as long as one doesn't get bogged  
down in the process.
Now, where was that nifty little chain-saw I had yesterday?.. :-)

David.

On 27/10/2006, at 3:40 PM, Ronald Oussoren wrote:

> Why does everyone seem to want to push people away from IDLE? IDLE  
> isn't award-winning material, but it does work properly as a simple  
> python environment.
>
> In a way it is better than most programmers text editors because  
> although it is missing some of the advanced editor features these  
> offer it does come with an embedded python interpreter and debugger.
>
> Ronald
>
> On Oct 27, 2006, at 4:26 AM, David Worrall wrote:
>
>> no need for a file? then enjoy the delights of the interpreter.  just
>> $ /usr/bin/python (at the prompt)
>>
>> will get you the interpreter at which you can play around.
>> sometimes I do that whilst I'm trying to work out what I want
>> (by looking at the results of various processes)
>> and then drag/copy and past into a text edit doco when it's right,
>> and sometimes the reverse, especially for looping structures.
>>
>> That afterall is one of the beauties of interpreted languages ...
>> you don't need to know what you want until you see the it ..
>> This means that it is a tool for thought rather than just a tool for
>> executing a known idea.
>>
>> All the best w. python. I've programmed in everything from
>> fortran II , pascal, snobol, apl, forth, c, assemblers etc etc
>> and python for 7 years on all sorts of platforms. These days
>>   there has to be a pretty convincing argument  for me to use
>> anything else.
>>
>> ---David
>>
>> On 26/10/2006, at 7:28 PM, Rodney Somerstein wrote:
>>
>>> Thanks Chris and David for the suggestions. I'm already aware of
>>> other editors. But, as I mentioned, I'm currently learning Python  
>>> and
>>> an environment that actually lets me execute python code without
>>> having to first create and save a file is superior for that purpose,
>>> in my opinion.
>>>
>>> I already own BBEdit and have for many years. So, when I start
>>> actually writing real code, I will likely use that.
>>>
>>>> For what it' worth, perhaps to save you some time, I recently spent
>>>> a  day evaluating
>>>> these tools. Horses for courses, but for me:
>>>> TextWrangler is a freebie BBEditLite - a very nice word-processor
>>>> which is keyword aware;
>>>> SPE is a full-blown development environment which includes wxglade
>>>> interface to wxwindows
>>>> I found it difficult to 'grock' quickly but it could be good
>>>> ScrIDE is 1/2 way between.
>>>>
>>>> David
>>>>
>>>> On 26/10/2006, at 2:13 AM, Christopher Barker wrote:
>>>>
>>>>> While we're at it, if all you want is a Python-aware editor --  
>>>>> then
>>>>> there area a lot of other (better?) options. Scan the archives of
>>>>> this
>>>>> list for suggestions. A few:
>>>>>
>>>>> BBEdit (TextWrangler?)
>>>>> Eclipse
>>>>> SPE
>>>>> Jedit
>>>>> ScrIDE
>>>>>
>>>>>
>>>>> Assorted *nix editors: emaca, VIm, etc, etc.
>>>>>
>>>>> or look here:
>>>>>
>>>>> http://wiki.python.org/moin/PythonEditors
>>>>>
>>>>> -Chris
>>>
>>>
>>> -- 
>>>
>>> Rodney Somerstein            Always remember that you are unique...
>>> rodneys at io.com               just like everyone else.
>>> _______________________________________________
>>> Pythonmac-SIG maillist  -  Pythonmac-SIG at python.org
>>> http://mail.python.org/mailman/listinfo/pythonmac-sig
>>>
>>
>> _______________________________________
>> experimental polymedia:	www.avatar.com.au
>> Sonic Communications Research Group,
>> University of Canberra:	 www.canberra.edu.au
>>
>>
>>
>>
>> _______________________________________________
>> Pythonmac-SIG maillist  -  Pythonmac-SIG at python.org
>> http://mail.python.org/mailman/listinfo/pythonmac-sig
>

_______________________________________
experimental polymedia:	www.avatar.com.au
Sonic Communications Research Group,
University of Canberra:	 www.canberra.edu.au