Re: how do "real" python programmers work?

"Tim Golden" <[EMAIL PROTECTED]> wrote: > Tyrrell, Wendy wrote: > > (Well, nothing) > 8<-- > Your organisation seems to deal with partnerships between > business and education; are you looking to promote the use > of programming in schools? Or is there something else you

Re: how do "real" python programmers work?

Tyrrell, Wendy wrote: (Well, nothing) Was that all your question, Wendy, or did you accidentally hit the Send button too soon? You're welcome to ask here or on the tutor list http://mail.python.org/mailman/listinfo/tutor if you want to find out about Python. Or just look at the website: http

how do "real" python programmers work?

_ Wendy Tyrrell WRL Adviser Camden Education Business Partnership Children, Schools and Families London Borough of Camden The Medburn Centre 136 Chalton Street NW1 1RX Streetmap: http://www.streetmap.co.uk/streetmap.dll?G2M?X=529491&Y=183342&A=Y&Z=1 Phone: 020 7974 8249

Re: how do "real" python programmers work?

bblais wrote: > Hello, > > Let me start by saying that I am coming from a background using Matlab > (or Octave), and C++. I am going to outline the basic nuts-and-bolts > of how I work in these languages, and ask for some help to find out how > the same thing is done in Python. I am not sure wh

Re: how do "real" python programmers work?

I might be a little late to the party but my comments may still be valuable. I write Python code in emacs. Emacs has an great python-mode. The code I write can range from a GUI apps to server side code and emacs works just as well in all cases. Some of the features that make emacs a good Python ed

Re: how do "real" python programmers work?

I have a python file type setup in Vim. When I hit F9, it saves the file and executes it in a python shell. My _vimrc: filetype on autocmd FileType python call FileType_Python() " Python coding function! TryPython() :w! :!python % endfunction function! FileType_Python() map :ca

Re: how do "real" python programmers work?

Travis E. Oliphant wrote: >bblais wrote: > > >>In Python, there seems to be a couple ways of doing things. I could >>write it in one window, and from a Unix shell call >> python myscript.py >>and be like C++, but then I lose the interactiveness which makes >>prototypi

Re: how do "real" python programmers work?

Scott David Daniels <[EMAIL PROTECTED]> wrote: > bblais wrote: > > How do experienced python programmers usually do it? Is there a > > "usually" about it, or is it up to personal taste? Are there any > > convenient ways of doing these things? > There are a lot of us who use a test-first process:

Re: how do "real" python programmers work?

Love it. -- fynali -- http://mail.python.org/mailman/listinfo/python-list

Re: how do "real" python programmers work?

Tom Anderson <[EMAIL PROTECTED]> writes: > On Thu, 12 Jan 2006, Mike Meyer wrote: >> well, we need a term for development environment built out of Unix >> tools > Disintegrated development environment? Differentiated development > environment? How about just a development environment? I'd like

Re: how do "real" python programmers work?

Roy Smith <[EMAIL PROTECTED]> writes: > Mike Meyer <[EMAIL PROTECTED]> wrote: >> we need a term for development environment built out of Unix tools > We already have one. The term is "emacs". So people using a development environment built around vim's pyhon mode are using emacs?

Re: how do "real" python programmers work?

On Fri, 13 Jan 2006 17:09:13 +, Tom Anderson <[EMAIL PROTECTED]> wrote: > Ah, of course - to an true believer, emacs *is* the unix toolset. > :) To the true believer, unix runs under emacs. Regards, Dan -- Dan Sommers -- http://mail.python.org/mailman/

Re: how do "real" python programmers work?

On Fri, 13 Jan 2006, Roy Smith wrote: > Mike Meyer <[EMAIL PROTECTED]> wrote: > >> we need a term for development environment built out of Unix tools > > We already have one. The term is "emacs". Emacs isn't built out of unix tools - it's a standalone program. Ah, of course - to an true bel

Re: how do "real" python programmers work?

On Thu, 12 Jan 2006, Mike Meyer wrote: > well, we need a term for development environment built out of Unix > tools Disintegrated development environment? Differentiated development environment? How about just a development environment? tom -- NOW ALL ASS-KICKING UNTIL THE END -- http:/

Re: how do "real" python programmers work?

Mike Meyer <[EMAIL PROTECTED]> wrote: > we need a term for development environment built out of Unix tools We already have one. The term is "emacs". -- http://mail.python.org/mailman/listinfo/python-list

Re: how do "real" python programmers work?

Scott David Daniels wrote: > bblais wrote: > >>How do experienced python programmers usually do it? Is there a >>"usually" about it, or is it up to personal taste? Are there any >>convenient ways of doing these things? > > There are a lot of us who use a test-first process: > Write a unit t

Re: how do "real" python programmers work?

bblais wrote: [snip..] > In Python, there seems to be a couple ways of doing things. I could > write it in one window, and from a Unix shell call >python myscript.py > and be like C++, but then I lose the interactiveness which makes > prototyping easier. If I use the

Re: [OT] how do "real" python programmers work?

Mike Meyer wrote: (snip) > Maybe > some of the people who IDEs (instead of - well, we need a term for > development environment built out of Unix tools) "Extegrated Development environment" ?-) -- bruno desthuilliers python -c "print '@'.join(['.'.join([w[::-1] for w in p.split('.')]) for p

Re: how do "real" python programmers work?

bblais wrote: > Hello, > (snip) > > In C++, I open up an editor in one window, a Unix shell in another. (snip) > In Matlab, I do much the same thing, except there is no compile phase. (snip) > In Python, there seems to be a couple ways of doing things. I could > write it in one window, and fro

Re: how do "real" python programmers work?

As many others, I use emacs for programming and ipython for interactive experiments. Michele Simionato -- http://mail.python.org/mailman/listinfo/python-list

Re: how do "real" python programmers work?

bblais wrote: > In Python, there seems to be a couple ways of doing things. I could > write it in one window, and from a Unix shell call >python myscript.py > and be like C++, but then I lose the interactiveness which makes > prototyping easier. If I use the python s

Re: how do "real" python programmers work?

On Thu, 12 Jan 2006, bblais wrote: > In Matlab, I do much the same thing, except there is no compile phase. I > have the editor on one window, the Matlab interactive shell in the > other. I often make a bunch of small scripts for exploration of a > problem, before writing any larger apps. I g

Re: how do "real" python programmers work?

bblais wrote: > In Python, there seems to be a couple ways of doing things. I could > write it in one window, and from a Unix shell call >python myscript.py > and be like C++, but then I lose the interactiveness which makes > prototyping easier. If I use the python sh

Re: how do "real" python programmers work?

bblais wrote: > How do experienced python programmers usually do it? Is there a > "usually" about it, or is it up to personal taste? Are there any > convenient ways of doing these things? There are a lot of us who use a test-first process: Write a unit test, watch it fail, fix the code til th

Re: how do "real" python programmers work?

"bblais" <[EMAIL PROTECTED]> writes: > In Python, there seems to be a couple ways of doing things. I could > write it in one window, and from a Unix shell call >python myscript.py > and be like C++, but then I lose the interactiveness which makes > prototyping easier.

Re: how do "real" python programmers work?

Scott David Daniels <[EMAIL PROTECTED]> writes: > bblais wrote: >> How do experienced python programmers usually do it? Is there a >> "usually" about it, or is it up to personal taste? Are there any >> convenient ways of doing these things? > There are a lot of us who use a test-first process: >

Re: how do "real" python programmers work?

On 12 Jan 2006 12:20:50 -0800 "bblais" <[EMAIL PROTECTED]> wrote: > Hello, > > Let me start by saying that I am coming from a background using Matlab > (or Octave), and C++. I am going to outline the basic nuts-and-bolts > of how I work in these languages, and ask for some help to find out > how

Re: how do "real" python programmers work?

Barbier de Reuille Pierre wrote: > On 12 Jan 2006 12:20:50 -0800 > "bblais" <[EMAIL PROTECTED]> wrote: > > >>Hello, >> (snip) > > > Well, I think it will depend on your project ... > If you're developing GUI application, you will have trouble using the > python shell. At least you will need a s

Re: how do "real" python programmers work?

Hi Brian, I'm sure I don't qualify as an "experienced Python programmer", but I write lots of code usually for statistical analysis (via numarray) or for GUI work. The way I work is to use an editor and Idle for interactive testing of small routines. My choice of editor is SciTE. I'll have diffe

Re: how do "real" python programmers work?

bblais wrote: > In Python, there seems to be a couple ways of doing things. I could > write it in one window, and from a Unix shell call >python myscript.py > and be like C++, but then I lose the interactiveness which makes > prototyping easier. If I use the python sh

Re: how do "real" python programmers work?

I'm not an experienced python programmer, but I come from a C++ background as well. I like to code in Komodo ($29 for the personal edition) and that lets me have multiple python files opened in tabs, and multiple interpreters opened below, since the interpreter is command based, it doesn't have to

Re: how do "real" python programmers work?

On 12 Jan 2006 12:20:50 -0800 in comp.lang.python, "bblais" <[EMAIL PROTECTED]> wrote: >Hello, > >Let me start by saying that I am coming from a background using Matlab >(or Octave), and C++. I am going to outline the basic nuts-and-bolts I generally write C code for embedded controllers. >of h

how do "real" python programmers work?

Hello, Let me start by saying that I am coming from a background using Matlab (or Octave), and C++. I am going to outline the basic nuts-and-bolts of how I work in these languages, and ask for some help to find out how the same thing is done in Python. I am not sure what the standard is. In C++

Re: how do "real" python programmers work?

bblais wrote: > In Python, there seems to be a couple ways of doing things. I could > write it in one window, and from a Unix shell call >python myscript.py > and be like C++, but then I lose the interactiveness which makes > prototyping easier. If I use the python sh