On Saturday, September 21, 2013 2:43:13 PM UTC-7, Peter Cacioppi wrote:
> This is an idea brought over from another post.
>
>
>
> When I write Python code I generally have 2 or 3 windows open simultaneously.
>
>
>
> 1) An editor for the actual code.
>
> 2) The interactive interpreter.
>
> 3
On 23 September 2013 10:35, rusi wrote:
>> Then, I launch iPython, which can intellisense launch 3 easily. Then I make
>> whatever changes I need to 1-3 to make a baby step forward, close iPython,
>> and repeat.
>
> Hardly looks very ergonomic to me
I'm not quite sure what's meant by intellisense
On Monday, September 23, 2013 2:01:00 PM UTC+5:30, Peter Cacioppi wrote:
> One thing re: editors and interactive environments. I'm not a huge emacs fan
> (ducking) and I really like iPython.
Heh! Yeah we are an endangered species
G enerally
N ot
U sed
E ditor for
M iddle
A ged
C omputer
S cientis
On Saturday, September 21, 2013 2:43:13 PM UTC-7, Peter Cacioppi wrote:
> This is an idea brought over from another post.
>
>
>
> When I write Python code I generally have 2 or 3 windows open simultaneously.
>
>
>
> 1) An editor for the actual code.
>
> 2) The interactive interpreter.
>
> 3
On Sunday, September 22, 2013 3:13:13 AM UTC+5:30, Peter Cacioppi wrote:
> This is an idea brought over from another post.
>
> When I write Python code I generally have 2 or 3 windows open simultaneously.
>
>
> 1) An editor for the actual code.
> 2) The interactive interpreter.
> 3) An editor fo
On Saturday, September 21, 2013 2:43:13 PM UTC-7, Peter Cacioppi wrote:
> This is an idea brought over from another post.
>
>
>
> When I write Python code I generally have 2 or 3 windows open simultaneously.
>
>
>
> 1) An editor for the actual code.
>
> 2) The interactive interpreter.
>
> 3
On 9/21/2013 5:43 PM, Peter Cacioppi wrote:
This is an idea brought over from another post.
When I write Python code I generally have 2 or 3 windows open simultaneously.
1) An editor for the actual code.
2) The interactive interpreter.
3) An editor for the unit tests. (Sometimes skipped for qui
This is an idea brought over from another post.
When I write Python code I generally have 2 or 3 windows open simultaneously.
1) An editor for the actual code.
2) The interactive interpreter.
3) An editor for the unit tests. (Sometimes skipped for quick one-off scripts)
My work flow tends to inv
