Re: What text editor is everyone using for Python
On May 26, 3:35 am, LittleGrasshopper wrote: > With so many choices, I was wondering what editor is the one you > prefer when coding Python, The Zeus for Windows IDE is Python aware: http://www.zeusedit.com/python.html > and why. It does syntax highlighting, smart indenting, code folding etc etc You can write Zeus scripts in Python. Zeus also creates Python tag informatuion (via ctags.exe) and this information is used to populate the class/code browser. It is also possible to hook in the Python documentation so the help can be searched and accessed from within the editor: http://www.zeusedit.com/forum/viewtopic.php?t=8 Jussi Jumppanen Author: Zeus for Windows IDE NOTE: Zeus is shareware -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On May 31, 12:42 am, edexter wrote: On the Windows platform the Zeus editor has Python language support: http://www.zeusedit.com > I will sometimes use word pad but i perfer syntax > highlighting.. The syntax highlighter is fully configurable. > I would be after is to be able to define my syntax file, the > ability to use code snippits, It has a code template feature. > the ability to add tools and compilers... and it also has these features. If also does Python code folding and is scriptable in Python. Jussi Jumppanen Author: Zeus for Windows -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On May 25, 10:35 am, LittleGrasshopper wrote: > With so many choices, I was wondering what editor is the one you > prefer when coding Python, and why. I normally use vi, and just got > into Python, so I am looking for suitable syntax files for it, and > extra utilities. I dabbled with emacs at some point, but couldn't get > through the key bindings for commands. I've never tried emacs with vi > keybindings (I forgot the name of it) but I've been tempted. > > So what do you guys use, and why? Hopefully we can keep this civil. I use emacs. If you never tried emacs, you might check out: • Xah's Emacs Tutorial http://xahlee.org/emacs/emacs.html • Xah's Emacs Lisp Tutorial http://xahlee.org/emacs/elisp.html you can use python to write emacs commands: • Elisp Wrapper For Perl Scripts http://xahlee.org/emacs/elisp_perl_wrapper.html Emacs keyboard shortcuts is problematic indeed. See: • Why Emacs's Keyboard Shortcuts Are Painful http://xahlee.org/emacs/emacs_kb_shortcuts_pain.html However, you can completely fix that. See: • Ergoemacs Keybindings http://xahlee.org/emacs/ergonomic_emacs_keybinding.html Xah ∑ http://xahlee.org/ ☄ -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
Ben Finney wrote: > Emile van Sebille writes: > > > On 6/4/2009 3:19 PM Lawrence D'Oliveiro said... > > > In message , Nick Craig- > > > Wood wrote: > > > > > >> You quit emacs with Ctrl-X Ctrl-C. > > > > > > That's "save-buffers-kill-emacs". If you don't want to save buffers, > > > the exit sequence is alt-tilde, f, e. > > This is an invocation of the menu system, driven by the keyboard. (Also, > it's not Alt+tilde (which would be Alt+Shift+`), it's Alt+` i.e. no > Shift.) It's an alternate command, and IMO is just adding confusion to > the discussion. Also, according to my emacs e==>Exit Emacs (C-x C-c) so Alt-` f e is exactly the same as Ctrl-x Ctrl-c anyway! If the OP really want to quit emacs without being prompted to save any buffes then run the 'kill-emacs' command which isn't bound to a key by default. You would do this with Alt-X kill-emacs But the fact that it isn't bound to a key by default means that it isn't recommended (and I've never used it in 10 years of using emacs!) - just use Ctrl-X Ctrl-C as Richard Stallman intended ;-) -- Nick Craig-Wood -- http://www.craig-wood.com/nick -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
Albert van der Horst wrote: Memories of Atari 260/520/1040 that had a keyboard with a key actually marked ... HELP. Modern day Mac keyboards have one of those, too. -- Greg -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
Emile van Sebille writes: > On 6/4/2009 3:19 PM Lawrence D'Oliveiro said... > > In message , Nick Craig- > > Wood wrote: > > > >> You quit emacs with Ctrl-X Ctrl-C. > > > > That's "save-buffers-kill-emacs". If you don't want to save buffers, > > the exit sequence is alt-tilde, f, e. This is an invocation of the menu system, driven by the keyboard. (Also, it's not Alt+tilde (which would be Alt+Shift+`), it's Alt+` i.e. no Shift.) It's an alternate command, and IMO is just adding confusion to the discussion. > Ha ha ha ha ha! > > No -- really? Not really. If you don't want to save buffers, you just answer “No” when prompted by ‘save-buffers-kill-emacs’, so Ctrl+X Ctrl+C is all you need to know to exit Emacs. -- \“Consider the daffodil. And while you're doing that, I'll be | `\ over here, looking through your stuff.” —Jack Handey | _o__) | Ben Finney -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On 6/4/2009 3:19 PM Lawrence D'Oliveiro said... In message , Nick Craig- Wood wrote: You quit emacs with Ctrl-X Ctrl-C. That's "save-buffers-kill-emacs". If you don't want to save buffers, the exit sequence is alt-tilde, f, e. Ha ha ha ha ha! No -- really? Emile -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
In message , Albert van der Horst wrote: > Memories of Atari 260/520/1040 that had a keyboard with a key actually > marked ... HELP. And the OLPC machines have a key marked "reveal source". -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
In message , Nick Craig- Wood wrote: > You quit emacs with Ctrl-X Ctrl-C. That's "save-buffers-kill-emacs". If you don't want to save buffers, the exit sequence is alt-tilde, f, e. -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
Steven D'Aprano wrote: > On Tue, 02 Jun 2009 10:54:48 +1200, Lawrence D'Oliveiro wrote: > > > In message , Albert van der Horst wrote: > > > >> An indication of how one can see one is in emacs is also appreciated. > > > > How about, hit CTRL/G and see if the word "Quit" appears somewhere. > > Ah, one has to love user interfaces designed with mnemonic keyboard > commands so as to minimize the burden of rote learning on the user. > Presumably it is G for "Get me the frack outta here!". > > Having noted that the word "Quit" does appear, how do you then *actually* > Quit? Apart from taunting the user, what is it that Ctrl-G is actually > doing when it displays the word "Quit" in what seems to be some sort of > status bar? I love the idea of emacs taunting the user - it is like all that lisp code suddenly became self aware and decided to join in ;-) Ctrl-G is the emacs interrupt sequence. It cancels what you are doing. Kind of like Ctrl-C in the shell. You quit emacs with Ctrl-X Ctrl-C. Save a document with Ctrl-X Ctrl-S that that is probably enough for the emacs survival guide! If you run emacs in a windowing environment (eg X-Windows or Windows) you actually get menus you can choose save and quit off! Anyway, wrenching the thread back on topic - I use emacs for all my python editing needs (on linux, windows and mac) with pymacs or python-mode (depending on distro). I use the subversion integration extensively. The interactive features of emacs are really useful for testing python code - even more useful than the python interactive prompt for bits of code longer than a line or too. (Open a new window in python mode, type stuff, press Ctrl-C Ctrl-C and have the output shown in a different window. If you messed up, clicking on the error will put the cursor in the right place in the code). -- Nick Craig-Wood -- http://www.craig-wood.com/nick -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
In article , Emile van Sebille wrote: >On 6/1/2009 4:57 PM Steven D'Aprano said... >> Having noted that the word "Quit" does appear, how do you then *actually* >> Quit? Apart from taunting the user, what is it that Ctrl-G is actually >> doing when it displays the word "Quit" in what seems to be some sort of >> status bar? > >Ahhh.. memories of discovering that F7 gets you out of WordPerfect... Memories of Atari 260/520/1040 that had a keyboard with a key actually marked ... HELP. (Sometimes hitting it provided you with help...) > >Emile > Groetjes Albert -- -- Albert van der Horst, UTRECHT,THE NETHERLANDS Economic growth -- like all pyramid schemes -- ultimately falters. alb...@spe&ar&c.xs4all.nl &=n http://home.hccnet.nl/a.w.m.van.der.horst -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On May 25, 1:35 pm, LittleGrasshopper wrote: > With so many choices, I was wondering what editor is the one you > prefer when coding Python, and why. I normally use vi, and just got > into Python, so I am looking for suitable syntax files for it, and > extra utilities. I dabbled with emacs at some point, but couldn't get > through the key bindings for commands. I've never tried emacs with vi > keybindings (I forgot the name of it) but I've been tempted. > > So what do you guys use, and why? Hopefully we can keep this civil. I use Eclipse with PyDev for serious projects. However, when that is too heavy or not available I use: 1) nano over ssh with syntax highlighting for python turned on 2) notepad++ on standalone Windows systems where I need to do quick edits or fixes. I used to use Crimson Editor, but it is not being developed anymore, and notepad++ does everything crimson used to do and more. -={C}=- -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
Emile van Sebille wrote: On 6/1/2009 4:57 PM Steven D'Aprano said... Having noted that the word "Quit" does appear, how do you then *actually* Quit? Apart from taunting the user, what is it that Ctrl-G is actually doing when it displays the word "Quit" in what seems to be some sort of status bar? Ahhh.. memories of discovering that F7 gets you out of WordPerfect... And if you need help, just press F1, uh, I mean F3... :-) -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On 6/1/2009 4:57 PM Steven D'Aprano said... Having noted that the word "Quit" does appear, how do you then *actually* Quit? Apart from taunting the user, what is it that Ctrl-G is actually doing when it displays the word "Quit" in what seems to be some sort of status bar? Ahhh.. memories of discovering that F7 gets you out of WordPerfect... Emile -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On Tue, 02 Jun 2009 10:54:48 +1200, Lawrence D'Oliveiro wrote: > In message , Albert van der Horst wrote: > >> An indication of how one can see one is in emacs is also appreciated. > > How about, hit CTRL/G and see if the word "Quit" appears somewhere. Ah, one has to love user interfaces designed with mnemonic keyboard commands so as to minimize the burden of rote learning on the user. Presumably it is G for "Get me the frack outta here!". Having noted that the word "Quit" does appear, how do you then *actually* Quit? Apart from taunting the user, what is it that Ctrl-G is actually doing when it displays the word "Quit" in what seems to be some sort of status bar? -- Steven -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
In message , Albert van der Horst wrote: > An indication of how one can see one is in emacs is also appreciated. How about, hit CTRL/G and see if the word "Quit" appears somewhere. -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
In message , Albert van der Horst wrote: > You can carry vim (or Edwin's editor for that matter) on a FAT > [USB] stick. > (As they say: "Speak softly, and carry a large stick.") I like that. :) -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
In article , Lawrence D'Oliveiro wrote: >In message , Lie Ryan wrote: > >> norseman wrote: >> >>> Suggestion: >>> Take a look at the top two most used OS you use and learn the default >>> (most often available) text editors that come with them. >> >> Which means Notepad on Windows? > >Or you could take a Linux preinstallation on a Live CD/DVD or USB stick. >There's no Windows system so brain-dead it can't be fixed with a simple >ctrl-alt-del. :) > You can carry vim (or Edwin's editor for that matter) on a FAT stick. (As they say: "Speak softly, and carry a large stick.") Groetjes Albert -- -- Albert van der Horst, UTRECHT,THE NETHERLANDS Economic growth -- like all pyramid schemes -- ultimately falters. alb...@spe&ar&c.xs4all.nl &=n http://home.hccnet.nl/a.w.m.van.der.horst -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
In article , Roy Smith wrote: >In article , > Bar Shirtcliff wrote: > >> I can't say a thing about other editors, except that when some shell >> script perversely dumped me into vi a month ago, I felt as horrified >> as if some actually living bugs had crawled out of my own reflection >> on the computer screen and fallen, clicking and scraping, onto the >> keyboard. That's a personal reaction - totally irrelevant, of course. > > : q ! Make that : q ! >All the vi you ever need to know :-) Now some kind soul give a similar sequence for emacs. > >The real problem is when you get dumped into some editor other than you one >you expected and don't realize it for a while. It's really amazing how >much damage you can do to a file by typing (for example) emacs commands at >vi. Especially if you accidentally stumble upon the sequence for "save >file". Exactly. An indication of how one can see one is in emacs is also appreciated. [Especially insidious is helpful help that lands you in emacs-ing help file for powerful searching (not!).] Groetjes Albert -- -- Albert van der Horst, UTRECHT,THE NETHERLANDS Economic growth -- like all pyramid schemes -- ultimately falters. alb...@spe&ar&c.xs4all.nl &=n http://home.hccnet.nl/a.w.m.van.der.horst -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
In message , Lie Ryan wrote: > norseman wrote: > >> Suggestion: >> Take a look at the top two most used OS you use and learn the default >> (most often available) text editors that come with them. > > Which means Notepad on Windows? Or you could take a Linux preinstallation on a Live CD/DVD or USB stick. There's no Windows system so brain-dead it can't be fixed with a simple ctrl-alt-del. :) -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On May 30, 6:28 am, "Hendrik van Rooyen" wrote: > "Lie Ryan" wrote: > > norseman wrote: > > > Suggestion: > > > Take a look at the top two most used OS you use and learn the default > > > (most often available) text editors that come with them. > > > Which means Notepad on Windows? > > you could live dangerously and use WordPad... > > - Hendrik I will sometimes use word pad but i perfer syntax highlighting.. I have been tempted to fork out some cash what I would be after is to be able to define my syntax file, the ability to use code snippits, the ability to add tools and compilers... until then I use spe, vim, emacs, boa constructor, I had a couple of other ones but I probily won't miss them that much.. The python to c compiler coming of age is something I am looking foward to and is something I would like to have supported in my editor (shedskin it is all coming back to me now). -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
"Lie Ryan" wrote: > norseman wrote: > > Suggestion: > > Take a look at the top two most used OS you use and learn the default > > (most often available) text editors that come with them. > > Which means Notepad on Windows? you could live dangerously and use WordPad... - Hendrik -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
I am a long time VIM user, and I likely will not change that. The speed, ease of use and functionality, for me, is worth the time spent learning how to use it. My secondary editor on the desktop is UltraEdit, which does a fine job as a text editor and has all the same functionality of VIM - yet despite 2 years on it (they won't allow me GVIM at work), I can't get to the same level of productivity with it as I can with VIM. Ditto Eclipse... I spent more time figuring out how to get a program to run properly than coding. The limited autocomplete and function jump-list were not worth the pain of getting it working, IMO. On May 29, 2:01 am, Steven D'Aprano wrote: > (1) Closed source editors have the same functional requirements as open > source editors. > > (2) If you're waiting for perfection, you'll be waiting forever. > > (3) Why independent of the OS? When is the last time you've used a system > without an OS? Forth programmers in the 1970s used an editor that was OS > independent -- it managed files using its own unique file structure, > managed memory itself, etc. Why do you want to go back there? As to your points, Steven: 1) I would agree with this point. VI and it's children were written to a different interpretation of said rules, however. They were built around the speed at which a human can use a keyboard with natural finger movements, at the expense of discoverability and intuitiveness. 2) VIM may not be perfect, but it's really darned close. ;-) 3) OS independence, IMO, is related more to the ability to use the tool on every OS, rather than on the lack of an OS. -- http://mail.python.org/mailman/listinfo/python-list
Syntax highlighting, round 42 (was Re: What text editor is everyone using for Python)
In article , Lawrence D'Oliveiro wrote: >In message , Steven >D'Aprano wrote: >> On Tue, 26 May 2009 18:31:56 +1200, Lawrence D'Oliveiro wrote: >>> In message >> b201-4b2445732...@v35g2000pro.googlegroups.com>, LittleGrasshopper >>> wrote: ... I am looking for suitable syntax files for [editor of choice] ... >>> >>> I don't understand why people need "syntax files" to use a text editor. >> >> Do you want syntax highlighting? > >Why? Didn't we have this discussion just a few weeks ago, when I said that highlighting made my eyes bleed? [] Oh, Gooja sez that we did it at the beginning of February, so almost four months. -- Aahz (a...@pythoncraft.com) <*> http://www.pythoncraft.com/ my-python-code-runs-5x-faster-this-month-thanks-to-dumping-$2K- on-a-new-machine-ly y'rs - tim -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
In message <003b3d8c$0$9673$c3e8...@news.astraweb.com>, Steven D'Aprano wrote: > On Fri, 29 May 2009 14:00:19 +1200, Lawrence D'Oliveiro wrote: > >> In message <003af57e$0$9673$c3e8...@news.astraweb.com>, Steven D'Aprano >> wrote: >> >>> On Fri, 29 May 2009 09:04:39 +1200, Lawrence D'Oliveiro wrote: >>> In message <003a5518$0$9673$c3e8...@news.astraweb.com>, Steven D'Aprano wrote: > On Thu, 28 May 2009 20:58:07 +1200, Lawrence D'Oliveiro wrote: > >> In message <0039e83c$0$9673$c3e8...@news.astraweb.com>, Steven >> D'Aprano wrote: >> >>> A good UI standard should mean that: >>> >>> * all functionality should be discoverable without reading the >>> manual; >> >> Which means no scripting languages are allowed? > > "Should", not "must". If you meant "may or may not", why don't you say "may or may not"? >>> >>> "Should" does not mean "may or may not". >> >> I'm not sure how there is supposed to be a difference in this context. >> "All people should fly by flapping their arms, except where this is >> physically impossible". You're asking for something that is infeasible >> with most current editors, if not all of them. > > On the remote chance that you're not trolling, I deny that > discoverablity is "infeasible" ... On the remote chance you're not trolling, let me point out politely that it is for scriptability. -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
norseman wrote: > jeffFromOz wrote: >> On May 26, 10:07 pm, Lacrima wrote: >>> I am new to python. >>> And now I am using trial version of Wing IDE. >>> But nobody mentioned it as a favourite editor. >>> So should I buy it when trial is expired or there are better choices? >> >> No one mentioned textmate either . a brilliant text editor with >> python templates, and bundles, syntax highlighting, etc. We use >> wingIDE for debugging and it seems fine, except for the weird way it >> corrupts the displayed text. > === > > BOTTOM LINES: > > Whatever they learned on. > Whatever they are trying out at the moment (for the adventurous types) > > > Suggestion: > Take a look at the top two most used OS you use and learn the default > (most often available) text editors that come with them. Which means Notepad on Windows? -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On Fri, 29 May 2009 08:57:18 +0200, Gabor Urban wrote: > In one the last postings about this topic Steven D'Aprano has written: > "As a general rule, menus are discoverable, while keyboard commands > aren't. There's nothing inherent to text editing functions which makes > then inherently undiscoverable, and KDE apps like kate and kwrite do a > reasonable job of making them so." > > I agree with this assumption if, and only if we are speaking about > outsider users. It's not an assumption, it's a conclusion. My assumption is that everybody, no matter how experienced they are, will *at some time* be looking for some editor functionality without knowing whether or not it exists. I've never needed to (say) strip out all comments from a document, but if I ever do, if the editor makes functions discoverable, I've got a better chance of finding the command I need, rather than wasting my time programming something that's been done before. We all know of experienced system admins who have built-up an amazingly detailed amount of knowledge about the systems they've used. They can tell you about the most obscure features and functions of a system. But put them in a system which is *not quite the same* (say, Ubuntu instead of Redhat, or FreeBSD instead of Linux), and they often flounder. All the functions they're used to are in a different place, so to speak. And there's no easy way to learn that command ABC on one system is precisely the same as command XYZ on another. Only two sorts of people don't benefit from ease of discoverablity: those who know everything, and those who never do anything new. > This is a Python mailing list, which supposed to be a forum of people > using the Python programming language. So Python source is a plain text, > so Python interpreter should be a command-driven application. With no > other UI than the plain old Command Line Intreface. That Python is command-driven doesn't have *any* implications for the editor you use to write Python code. Photo-editing software is mouse- driven. That doesn't mean that you should be forced to write photo- editing programs by point-and-click. > MOre than that, all we are supposed to be techmen, who does acknowledge > and appreciate the conceot of wrtitten User Manual or Reference. All we > have learned Python from tutorials and not from the menues. We're probably better at reading manuals than average people, but that doesn't mean we *like* it. That's one of the reasons we use Python: nearly everything is discoverable from inside the Python runtime environment. We have a wealth of tools for inspecting objects. If you want to know what methods an object has, you don't have to look it up in the manual, you can inspect it with dir(). Besides, once you've been in the tech industry for long enough, you'll learn that the Python documentation is *remarkably* good compared to the average technical documentation. > As a summary, any open source editor should be perfect, which is > extensible, optionally language-sensitive, portable, basically > independent of any OS features. THat cuts the list drammatically. (1) Closed source editors have the same functional requirements as open source editors. (2) If you're waiting for perfection, you'll be waiting forever. (3) Why independent of the OS? When is the last time you've used a system without an OS? Forth programmers in the 1970s used an editor that was OS independent -- it managed files using its own unique file structure, managed memory itself, etc. Why do you want to go back there? -- Steven -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
Gabor Urban writes: > This is a Python mailing list, which supposed to be a forum of people > using the Python programming language. Agreed so far. > As a summary, any open source editor should be perfect, which is > extensible, optionally language-sensitive, portable, basically > independent of any OS features. THat cuts the list drammatically. With this paragraph I can agree. > So Python source is a plain text, so Python interpreter should be a > command-driven application. Huh? The Python interpreter should be a command-line application, true. But the fact that Python source code is text has nothing to do with that. > With no other UI than the plain old Command Line Intreface. This doesn't follow at all. I am convinced that I'm far more productive in my full-window editing environment over needing to use a command-line to do everything. Where does “should” come into that, and why is a full-window environment excluded? If, instead of “command-line”, you actually mean “text-mode full-window console”, I'm still calling you on your non sequitur. There's nothing about editing text that excludes using a graphical interface rendered in pixels instead of text characters. The closest I get to agreement with any of the above is that a full-window text editing environment should never *require* any graphical pixellated interface. But to *exclude* it is too much. > MOre than that, all we are supposed to be techmen, who does > acknowledge and appreciate the conceot of wrtitten User Manual or > Reference. All we have learned Python from tutorials and not from the > menues. You seem to have a rather exclusionist idea of the Python community, that does not match my experience at all. Python programmers are women as well as men. Many Python programmers would not describe themselves as “technical” people. And I know for a fact many of the good ones learned by example, not from tutorials. -- \ “Courage is resistance to fear, mastery of fear — not absence | `\of fear. —Mark Twain, _Pudd'n'head Wilson_ | _o__) | Ben Finney -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
Hi guys, I would like to reflect this issue for the last time, though I found this thread to be quite inspiring. In one the last postings about this topic Steven D'Aprano has written: "As a general rule, menus are discoverable, while keyboard commands aren't. There's nothing inherent to text editing functions which makes then inherently undiscoverable, and KDE apps like kate and kwrite do a reasonable job of making them so." I agree with this assumption if, and only if we are speaking about outsider users. This is a Python mailing list, which supposed to be a forum of people using the Python programming language. So Python source is a plain text, so Python interpreter should be a command-driven application. With no other UI than the plain old Command Line Intreface. MOre than that, all we are supposed to be techmen, who does acknowledge and appreciate the conceot of wrtitten User Manual or Reference. All we have learned Python from tutorials and not from the menues. As a summary, any open source editor should be perfect, which is extensible, optionally language-sensitive, portable, basically independent of any OS features. THat cuts the list drammatically. Gabor -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On Fri, 29 May 2009 14:00:19 +1200, Lawrence D'Oliveiro wrote: > In message <003af57e$0$9673$c3e8...@news.astraweb.com>, Steven D'Aprano > wrote: > >> On Fri, 29 May 2009 09:04:39 +1200, Lawrence D'Oliveiro wrote: >> >>> In message <003a5518$0$9673$c3e8...@news.astraweb.com>, Steven >>> D'Aprano wrote: >>> On Thu, 28 May 2009 20:58:07 +1200, Lawrence D'Oliveiro wrote: > In message <0039e83c$0$9673$c3e8...@news.astraweb.com>, Steven > D'Aprano wrote: > >> A good UI standard should mean that: >> >> * all functionality should be discoverable without reading the >> manual; > > Which means no scripting languages are allowed? "Should", not "must". >>> >>> If you meant "may or may not", why don't you say "may or may not"? >> >> "Should" does not mean "may or may not". > > I'm not sure how there is supposed to be a difference in this context. > "All people should fly by flapping their arms, except where this is > physically impossible". You're asking for something that is infeasible > with most current editors, if not all of them. On the remote chance that you're not trolling, I deny that discoverablity is "infeasible", for editors or other applications. Making a UI discoverable is not a hard problem that is difficult to solve. Discoverablity isn't radical new concept in UI design, it has been around since the 1970s, at least. The concept is simple: e.g. in the editor I'm using to compose this message, I have a toolbar which includes a button "Wrap Text". That's discoverable, because even if I didn't know the command existed, I could discover it by looking at the toolbar. There's a keyboard command to do the same thing: Alt-E-W. Without reading the manual, I'm unlikely to discover that command. Here's a couple of screenshots of Wordstar: http://www.kantl.be/ctb/vanhoutte/teach/slides/graphics/wstar.gif http://www.iee.et.tu-dresden.de/~kc-club/08/PCX/WORDSTAR.GIF Wordstar's commands are discoverable, because they are listed in a menu you can choose from. Wordstar dates back to 1978, so this isn't precisely the cutting edge of UI design. As a general rule, menus are discoverable, while keyboard commands aren't. There's nothing inherent to text editing functions which makes then inherently undiscoverable, and KDE apps like kate and kwrite do a reasonable job of making them so. -- Steven -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
In message <003af57e$0$9673$c3e8...@news.astraweb.com>, Steven D'Aprano wrote: > On Fri, 29 May 2009 09:04:39 +1200, Lawrence D'Oliveiro wrote: > >> In message <003a5518$0$9673$c3e8...@news.astraweb.com>, Steven D'Aprano >> wrote: >> >>> On Thu, 28 May 2009 20:58:07 +1200, Lawrence D'Oliveiro wrote: >>> In message <0039e83c$0$9673$c3e8...@news.astraweb.com>, Steven D'Aprano wrote: > A good UI standard should mean that: > > * all functionality should be discoverable without reading the > manual; Which means no scripting languages are allowed? >>> >>> "Should", not "must". >> >> If you meant "may or may not", why don't you say "may or may not"? > > "Should" does not mean "may or may not". I'm not sure how there is supposed to be a difference in this context. "All people should fly by flapping their arms, except where this is physically impossible". You're asking for something that is infeasible with most current editors, if not all of them. -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On Fri, 29 May 2009 09:04:39 +1200, Lawrence D'Oliveiro wrote: > In message <003a5518$0$9673$c3e8...@news.astraweb.com>, Steven D'Aprano > wrote: > >> On Thu, 28 May 2009 20:58:07 +1200, Lawrence D'Oliveiro wrote: >> >>> In message <0039e83c$0$9673$c3e8...@news.astraweb.com>, Steven >>> D'Aprano wrote: >>> A good UI standard should mean that: * all functionality should be discoverable without reading the manual; >>> >>> Which means no scripting languages are allowed? >> >> "Should", not "must". > > If you meant "may or may not", why don't you say "may or may not"? Are you a native English speaker? "Should" does not mean "may or may not". There is an enormous difference in meaning between e.g. "I should feed the dog" and "I may or may not feed the dog". The first case means that you have a need to feed the dog, but you are not obliged to, while the second case means you are indifferent to whether or not you will feed the dog. (Strictly speaking, "may or may not" is redundant, although often used to emphasise the indifference. If you may do something, then by definition you also may not do it.) The distinction between "may", "should" and "must" is also very common in RFCs. As a tech, I would have expected you to have been aware of that. For example, picking one at random, RFC 1866 (literally the first one I looked up!): may A document or user interface is conforming whether this statement applies or not. must Documents or user agents in conflict with this statement are not conforming. should If a document or user agent conflicts with this statement, undesirable results may occur in practice even though it conforms to this specification. http://www.faqs.org/rfcs/rfc1866.html To put it another way: "may" is optional, "should" is recommended, and "must" is compulsory. -- Steven -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
jeffFromOz wrote: On May 26, 10:07 pm, Lacrima wrote: I am new to python. And now I am using trial version of Wing IDE. But nobody mentioned it as a favourite editor. So should I buy it when trial is expired or there are better choices? No one mentioned textmate either . a brilliant text editor with python templates, and bundles, syntax highlighting, etc. We use wingIDE for debugging and it seems fine, except for the weird way it corrupts the displayed text. === BOTTOM LINES: Whatever they learned on. Whatever they are trying out at the moment (for the adventurous types) Suggestion: Take a look at the top two most used OS you use and learn the default (most often available) text editors that come with them. The deep quiet voice of experience yells: Specialty items are seldom there when you need them! Steve -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On May 26, 10:07 pm, Lacrima wrote: > I am new to python. > And now I am using trial version of Wing IDE. > But nobody mentioned it as a favourite editor. > So should I buy it when trial is expired or there are better choices? No one mentioned textmate either . a brilliant text editor with python templates, and bundles, syntax highlighting, etc. We use wingIDE for debugging and it seems fine, except for the weird way it corrupts the displayed text. -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
In message <003a5518$0$9673$c3e8...@news.astraweb.com>, Steven D'Aprano wrote: > On Thu, 28 May 2009 20:58:07 +1200, Lawrence D'Oliveiro wrote: > >> In message <0039e83c$0$9673$c3e8...@news.astraweb.com>, Steven D'Aprano >> wrote: >> >>> A good UI standard should mean that: >>> >>> * all functionality should be discoverable without reading the manual; >> >> Which means no scripting languages are allowed? > > "Should", not "must". If you meant "may or may not", why don't you say "may or may not"? -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
Hendrik van Rooyen wrote: > When ssh- ing I have been using vim, painfully. Must look at nano - sounds > good. > I really miss Brief. Or try 'joe'. -- JanC -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
I use Emacs, as for the other editing activities. I like it for it is very powerfull. -- Linux: Choice of a GNU Generation -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
Or you can try pyscripter http://code.google.com/p/pyscripter/ Very fast, lightwieght and powerfull python editor. -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
I use Eclipse (www.eclipse.org) with the PyDev plugin (pydev.sourceforge.net). -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
Andreas Roehler wrote: Esmail wrote: LittleGrasshopper wrote: So what do you guys use, and why? Hopefully we can keep this civil. I use Emacs, just because I have been using this editor for all sorts of things in the last 20+ years. I haven't been able to get the python mode to work for Windows A bug-report would be fine... :) In case you use python-mode.el, please refer to https://launchpad.net/python-mode Hi, This got me to waste a bunch of time first with (add-to-list) unsuccessfully before I checked to see if there was an update to emacs distribution/bundle I use under Windows, which is http://vgoulet.act.ulaval.ca/en/ressources/emacs/windows Using its default .emacs I was able to get the python mode to work fine. (I suspect there was something off in my ancient .emacs file which I had been porting from system to system in the last 10 years or so). Glad this thread motivated me to upgrade/check on this. Regards, Esmail -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On Thu, 28 May 2009 06:24:56 +0100, Paul Rudin wrote: "Rhodri James" writes: The feature that caused me to uninstall python-mode.el was its bloody-minded determination to regard '_' as a word character, something which caused me more typing that it ever saved. Probably you could have changed this in a few minutes. Or does fiddling with emacs lisp invalidate your python programmer's licence? ;-) I probably could, but uninstalling didn't even require that much brain-power, and as I said I only missed one feature (and that not much). -- Rhodri James *-* Wildebeeste Herder to the Masses -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On Thu, May 28, 2009 at 07:38:33AM EDT, Steven D'Aprano wrote: > Your point is? notepad, otoh.. > *ducks and runs* .. likewise. -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On Thu, May 28, 2009 at 7:09 AM, Andreas Roehler wrote: > Rhodri James wrote: >> and I'll get over that. The feature that caused me to uninstall >> python-mode.el was its bloody-minded determination to regard '_' as a word >> character, something which caused me more typing that it ever saved. > > Its just one line to comment in python-mode.el, like this: > > ;; (modify-syntax-entry ?\_ "w" py-mode-syntax-table) > Not really a good idea to make minor changes to distributed elisp. You'll have to keep redoing the change every time a new version comes out. Better to put something like this in your .emacs file. (eval-after-load "python-mode" '(modify-syntax-entry ?\_ " " py-mode-syntax-table)) -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On Thu, 28 May 2009 20:58:07 +1200, Lawrence D'Oliveiro wrote: > In message <0039e83c$0$9673$c3e8...@news.astraweb.com>, Steven D'Aprano > wrote: > >> A good UI standard should mean that: >> >> * all functionality should be discoverable without reading the manual; > > Which means no scripting languages are allowed? "Should", not "must". In any case, once you've scripted some particular piece of functionality, the application should allow you to discover the existence of that script. Does the application have a "Scripts" or "Plugins" menu (or equivalent)? Or do you have to rummage around in the file system, looking for secret scripts in undocumented locations? -- Steven -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On Thu, 28 May 2009 11:08:08 +0100, Paul Rudin wrote: > Steven D'Aprano writes: > > >> * if possible, all functionality should be capable of being performed >> by either the mouse or keyboard. > > I'd imagine that the requirement that *all* functionality can be > performed with the mouse rules out many text editors. Almost the > defining feature of a text editor is the ability to type text... which > mostly happens with a keyboard. Likewise graphics editors -- it's difficult if not impossible to edit an image pixel by pixel using the keyboard. Hence the "if possible". (Aside: It's really discouraging that, even on a technical newsgroup where most of the people are relatively intelligent, the provisos and qualifications I give seem to be ignored in favour of an unrealistically extreme interpretation.) I do recall once in the mid 1980s, using a Macintosh with a broken keyboard. I was actually able to get useful work done by clicking letters on a virtual keyboard (the "Keyboard" desk accessory for those who remember it) and copying and pasting the text into the editor. -- Steven -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On Thu, 28 May 2009 05:44:07 -0400, Chris Jones wrote: >> * if possible, all functionality should be capable of being performed >> by either the mouse or keyboard. > > All valid points on the face of it, but doesn't the above rule out both > vim and emacs? Your point is? *ducks and runs* -- Steven -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
Rhodri James wrote: > On Wed, 27 May 2009 16:56:12 +0100, Bruno Desthuilliers > wrote: > >> Rhodri James a écrit : >>> On Tue, 26 May 2009 14:22:29 +0100, Roy Smith wrote: >>> My pet peeve is syntax-aware editors which get things wrong. For example, the version of emacs I'm using now doesn't parse this properly: '''A triple-quoted string. Some editors won't get this right''' The solution is to change the outer quotes to double-quotes, but it annoys me when I have to change my code to appease a tool. >>> It's the separate python-mode that gets this (and much else) wrong. >>> The Python mode that Ubuntu packages with emacs 22.2.1 works just >>> fine. >> >> On this point, indeed. But it also lacks almost every nice feature of >> the One True python-mode (or at least did last time I had to update >> this ... ubuntu box at work). > > That rather depends on your definition of "nice". The only feature of > python-mode.el that I miss in python.el is the ability to run pylint from > the menu, Thanks mentioning it, I'll cc this to python-m...@python.org and I'll get over that. The feature that caused me to uninstall > python-mode.el was its bloody-minded determination to regard '_' as a word > character, something which caused me more typing that it ever saved. > Its just one line to comment in python-mode.el, like this: ;; (modify-syntax-entry ?\_ "w" py-mode-syntax-table) -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
Rhodri James wrote: > On Tue, 26 May 2009 14:22:29 +0100, Roy Smith wrote: > >> My pet peeve is syntax-aware editors which get things wrong. For >> example, >> the version of emacs I'm using now doesn't parse this properly: >> >> '''A triple-quoted string. Some editors won't get this right''' >> >> The solution is to change the outer quotes to double-quotes, but it >> annoys me when I have to change my code to appease a tool. > > It's the separate python-mode that gets this (and much else) wrong. > The Python mode that Ubuntu packages with emacs 22.2.1 works just > fine. > As it should do python-mode.el from https://launchpad.net/python-mode -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
Esmail wrote: > LittleGrasshopper wrote: >> >> So what do you guys use, and why? Hopefully we can keep this civil. > > I use Emacs, just because I have been using this editor for > all sorts of things in the last 20+ years. > > I haven't been able to get the python mode to work for Windows A bug-report would be fine... :) In case you use python-mode.el, please refer to https://launchpad.net/python-mode Thanks Andreas Röhler -- https://code.launchpad.net/s-x-emacs-werkstatt/ > (do most of my work under Linux anyway), but other than that I'm > pretty happy with it :-) > > HTH, > Esmail > -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
Steven D'Aprano writes: > * if possible, all functionality should be capable of being performed by > either the mouse or keyboard. I'd imagine that the requirement that *all* functionality can be performed with the mouse rules out many text editors. Almost the defining feature of a text editor is the ability to type text... which mostly happens with a keyboard. -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On Thu, May 28, 2009 at 12:06:25AM EDT, Steven D'Aprano wrote: > On Wed, 27 May 2009 22:34:45 -0400, Chris Jones wrote: > > I'm unsure about a python editor for everyone but since acquiring > > habits takes time, I'm in favor of sticking to one editor for > > everything. > > Or use an editor which follows user interface standards, rather than > invents its own conventions for everything. That way you can trivially > swap from one compliant application to another compliant application. > > A good UI standard should mean that: > > * common tasks should use the same interface in any application that > supports that task; > > * all functionality should be discoverable without reading the manual; > > * the most common functions should be _trivially_ discoverable; > > * don't penalise the user for mistakes: as few actions as possible > should be irreversible, and those which are irreversible should > _effectively_ warn the user that they are irreversible; > > * simple interfaces are better than complicated interfaces (easy tasks > should be easy to perform); > > * but dumbing-down is not the same as simplifying (complicated tasks > should be possible); > > * if possible, all functionality should be capable of being performed > by either the mouse or keyboard. All valid points on the face of it, but doesn't the above rule out both vim and emacs? CJ -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On May 26, 9:07 am, Lacrima wrote: > I am new to python. > And now I am using trial version of Wing IDE. > But nobody mentioned it as a favourite editor. > So should I buy it when trial is expired or there are better choices? I use nothing but Wing. Their support is great as well. -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
In message <0039e83c$0$9673$c3e8...@news.astraweb.com>, Steven D'Aprano wrote: > A good UI standard should mean that: > > * all functionality should be discoverable without reading the manual; Which means no scripting languages are allowed? -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
"Rhodri James" writes: > The feature that caused me to uninstall python-mode.el was its > bloody-minded determination to regard '_' as a word character, > something which caused me more typing that it ever saved. Probably you could have changed this in a few minutes. Or does fiddling with emacs lisp invalidate your python programmer's licence? ;-) -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On Wed, 27 May 2009 22:34:45 -0400, Chris Jones wrote: > I'm unsure about a python editor for everyone but since acquiring habits > takes time, I'm in favor of sticking to one editor for everything. Or use an editor which follows user interface standards, rather than invents its own conventions for everything. That way you can trivially swap from one compliant application to another compliant application. A good UI standard should mean that: * common tasks should use the same interface in any application that supports that task; * all functionality should be discoverable without reading the manual; * the most common functions should be _trivially_ discoverable; * don't penalise the user for mistakes: as few actions as possible should be irreversible, and those which are irreversible should _effectively_ warn the user that they are irreversible; * simple interfaces are better than complicated interfaces (easy tasks should be easy to perform); * but dumbing-down is not the same as simplifying (complicated tasks should be possible); * if possible, all functionality should be capable of being performed by either the mouse or keyboard. -- Steven -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
I'm unsure about a python editor for everyone but since acquiring habits takes time, I'm in favor of sticking to one editor for everything. CJ -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On May 27, 2:09 pm, Stef Mientki wrote: > John Yeung wrote: > > > I kind of marvel at how few people complain about [SciTE's] > > Python indentation. (I'd like to think it's because anyone > > who edits Python code in SciTE has downloaded my patch, but > > I am confident that is not the case.) > > What's not correct about the Python indentation ? > Where can we find the patch ? If you have used SciTE for Python and haven't been frustrated by the autoindentation, then I don't think there is much reason for you to bother with a patch. By autoindentation, I mean automatically adding a level when a new block starts, not merely maintaining indentation level (which virtually every editor does, and some even call this their "autoindentation" feature). The problem with SciTE's autoindentation for Python is that you can only choose from the following three behaviors: 1. Add a level if you press Enter on a line containing a "live" colon (that is, one that's not in a string or comment). [Try not to use slices except on the same line as a block-initiating 'for', 'if', etc.] 2. Add a level if you press Enter on a line containing selected keywords like 'if', 'for', 'while', 'def', etc. [Avoid list comprehensions and generator expressions. You can do everything with map, filter, and lambda, right?] 3. Don't autoindent at all (maintain the current indentation only). It boggles the mind that there is no way to tell SciTE "only pay attention to the colon if it's at the end of the line" other than by modifying the source code, but there you have it. (It's not like choice 3 is actually that bad. I imagine that is what SciTE's author uses for Python.) My patch (which also fixes a couple of other indentation-related things that were driving me crazy) is here: http://groups.google.com/group/scite-interest/files in the file called Python_AutoIndent.cxx. John -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On Wed, 27 May 2009 16:56:12 +0100, Bruno Desthuilliers wrote: Rhodri James a écrit : On Tue, 26 May 2009 14:22:29 +0100, Roy Smith wrote: My pet peeve is syntax-aware editors which get things wrong. For example, the version of emacs I'm using now doesn't parse this properly: '''A triple-quoted string. Some editors won't get this right''' The solution is to change the outer quotes to double-quotes, but it annoys me when I have to change my code to appease a tool. It's the separate python-mode that gets this (and much else) wrong. The Python mode that Ubuntu packages with emacs 22.2.1 works just fine. On this point, indeed. But it also lacks almost every nice feature of the One True python-mode (or at least did last time I had to update this ... ubuntu box at work). That rather depends on your definition of "nice". The only feature of python-mode.el that I miss in python.el is the ability to run pylint from the menu, and I'll get over that. The feature that caused me to uninstall python-mode.el was its bloody-minded determination to regard '_' as a word character, something which caused me more typing that it ever saved. -- Rhodri James *-* Wildebeeste Herder to the Masses -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
John Yeung wrote: On May 26, 9:43 am, Mel wrote: SciTE I like one big uncomplicated window, tabbed file panes, syntax coloring and help with indentation. There's nothing to it I hate. It would be nice if customization were easier. This is a decent summary of SciTE, but I kind of marvel at how few people complain about its Python indentation. (I'd like to think it's because anyone who edits Python code in SciTE has downloaded my patch, but I am confident that is not the case.) What's not correct about the Python indentation ? Where can we find the patch ? cheers, Stef John -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
> This, ladies and gentlemen of the jury, points > up the essential difference between a modal and > a non-modal way of doing things. That is one reason I love emacs... I not only get a selection of several "major modes", I can also have multiple "minor modes" active at the same time! And I can extend it with a pure language like LISP rather than something like Vim which tends to prefer Python for extension. -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On May 26, 5:07 am, Lacrima wrote: > I am new to python. > And now I am using trial version of Wing IDE. > But nobody mentioned it as a favourite editor. > So should I buy it when trial is expired or there are better choices? First read this and think about where you want to invest your time, IDE or text: http://osteele.com/archives/2004/11/ides After working in a large IDE at first, I am glad I invested time into learning a powerful console-based text editor (VIM). Now my entire dev environment is accessible from any networked computer, and I can do everything without touching that horrible mouse contraption. Bryan -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
Rhodri James a écrit : On Tue, 26 May 2009 14:22:29 +0100, Roy Smith wrote: My pet peeve is syntax-aware editors which get things wrong. For example, the version of emacs I'm using now doesn't parse this properly: '''A triple-quoted string. Some editors won't get this right''' The solution is to change the outer quotes to double-quotes, but it annoys me when I have to change my code to appease a tool. It's the separate python-mode that gets this (and much else) wrong. The Python mode that Ubuntu packages with emacs 22.2.1 works just fine. On this point, indeed. But it also lacks almost every nice feature of the One True python-mode (or at least did last time I had to update this ... ubuntu box at work). -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On May 26, 7:07 pm, Lacrima wrote: > I am new to python. > And now I am using trial version of Wing IDE. > But nobody mentioned it as a favourite editor. > So should I buy it when trial is expired or there are better choices? Hello, I too new to Python. I tried several IDEs and ended up with Wing IDE. I used the trial version till it expired. Then found out that Wing team has a scaled down version of Wing IDE called 'Wing IDE 101'. http://www.wingware.com/downloads/wingide-101 Give it a try. It just lags few functions than Wing IDE. But its really simple and light. -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
I dont think Ive seen it said on this thread (if yes sorry for missing it) If you use emacs 1. DONT use the python.el that comes with emacs but use python-mode.el that comes from python 2. Use python as an interpreter ie not as you would use C or Java or ... which is to say 2.1 Start python as an interpreter under emacs ... which (assuming emacs is set up properly) means 2.1.1 M-x py-shell or 2.1.2 From a python source file C-c C-c 2.2 Dont (PLEASE) start a shell and start python in that; start a genuine 'inferior' python under emacs (yes emacs-speak is a bit weird but once you get used to it it has no replacement) 3. The most useful paradigm of noob hacking of python in emacs is to split the window into 2, keep your python file in one and the inferior python interpreter in the other. 4. After you've graduated out of noob status you may like to look at 4.1 pdb (Ive not managed to get this to run on windows) 4.2 doctest mode 4.3 rope 4.4 ipython -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On 27 Mag, 08:44, Ben Finney wrote: > Lacrima writes: > > I am new to python. > > And now I am using trial version of Wing IDE. > > But nobody mentioned it as a favourite editor. > > So should I buy it when trial is expired or there are better choices? > > I think your time will be better spent learning a powerful, mature, > well-supported, free-software, programmable editor with support for an > enormous range of text processing tasks. > > Either of Vim or Emacs qualify. Language-specific IDEs do not. > > -- > \ “Ladies are requested not to have children in the bar.” | > `\ —cocktail lounge, Norway | > _o__) | > Ben Finney I like using VIM. At this page http://blog.dispatched.ch/2009/05/24/vim-as-python-ide/ you can find some hints about how to setup some nice plugin that ease python (and others) development. -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On Wed, May 27, 2009 at 6:29 AM, Teguh Iskanto wrote: > > > BTW: "screen" does split screen too :) > > HTH > > Unfortunately, screen only does horizontal splitting. (I heard that vertical splitting is supposed to be in the next version of it, and is in the dev trunk, but I don't know). That said, screen is possibly the second most useful tool in my toolbox, right behind emacs. If you need to interact with different machines, it's a lifesaver. Actually, even if you don't, but you find yourself with a bunch of terminals open (whether you're in X or not), it's still incredibly useful. I know this is supposed to be a discussion about text editors, but I think that screen does deserve a mention as being very complementary to a good text editor if you're a programmer. -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
Lacrima writes: > I am new to python. > And now I am using trial version of Wing IDE. > But nobody mentioned it as a favourite editor. > So should I buy it when trial is expired or there are better choices? I think your time will be better spent learning a powerful, mature, well-supported, free-software, programmable editor with support for an enormous range of text processing tasks. Either of Vim or Emacs qualify. Language-specific IDEs do not. -- \ “Ladies are requested not to have children in the bar.” | `\ —cocktail lounge, Norway | _o__) | Ben Finney -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
Steven D'Aprano writes: > nano is basically an updated (forked?) version of pico. Re-implemented http://www.nano-editor.org/dist/v1.2/faq.html#6>. Pico was under a non-free license, so Nano was written to be a feature-compatible free-software clone. -- \ “If you ever catch on fire, try to avoid seeing yourself in the | `\mirror, because I bet that's what REALLY throws you into a | _o__) panic.” —Jack Handey | Ben Finney -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
Lawrence D'Oliveiro writes: > In message , Jean-Michel > Pichavant wrote: > >> Why buy an IDE when you just need a text editor ? > > Because all the cool kids have one. If you want to be different and > individual like them, you have to have what they have. Of course it's not always clear what the difference is in any case. Emacs, for example, has most of the features of many IDEs (not to mention many features that they lack). -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
In message , Teguh Iskanto wrote: > Have you tried vim ? it has got tons of tons of features ... So has everything else these days. > for example: you're working in the office and connected to your remote > CVS server ... Wouldn't it be easier to use a distributed VCS? -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
Have you tried vim ? it has got tons of tons of features, like ( just to name a few) : file manager, color syntax, tab screen, command/syntax completion (cache only) , vertical split, horizontal split, colorful diffing, create a patch, etc .. you name it !! . There's also plugins / script that people share @ http://www.vim.org/scripts/index.php. Also Vim comes in Windows/Unix version :) IMO, you don't even need an IDE, if you combined vim + "screen" ( man screen ) as both are really powerful tools for example: you're working in the office and connected to your remote CVS server, with "screen" you can lock the screen with password & detach it. once you're @ home and want to continue to work , you just need to log in to that cvs server again and do "screen -r" and voila your session is still there :) BTW: "screen" does split screen too :) HTH On Wed, May 27, 2009 at 2:56 PM, Ankit wrote: > On May 26, 6:04 pm, J Kenneth King wrote: >> Lacrima writes: >> > I am new to python. >> > And now I am using trial version of Wing IDE. >> > But nobody mentioned it as a favourite editor. >> > So should I buy it when trial is expired or there are better choices? >> > > I will suggest u to use TEXTPAD 4 on windows and > Emacs or Vi or RocketEdit on your Linux machine > > -- > http://mail.python.org/mailman/listinfo/python-list > -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On May 26, 6:04 pm, J Kenneth King wrote: > Lacrima writes: > > I am new to python. > > And now I am using trial version of Wing IDE. > > But nobody mentioned it as a favourite editor. > > So should I buy it when trial is expired or there are better choices? > I will suggest u to use TEXTPAD 4 on windows and Emacs or Vi or RocketEdit on your Linux machine -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On May 26, 9:43 am, Mel wrote: > SciTE > I like one big uncomplicated window, tabbed file panes, > syntax coloring and help with indentation. There's > nothing to it I hate. It would be nice if > customization were easier. This is a decent summary of SciTE, but I kind of marvel at how few people complain about its Python indentation. (I'd like to think it's because anyone who edits Python code in SciTE has downloaded my patch, but I am confident that is not the case.) John -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
In message , Roy Smith wrote: > The real problem is when you get dumped into some editor other than you > one you expected and don't realize it for a while. It's really amazing > how much damage you can do to a file by typing (for example) emacs > commands at vi. Doesn't work the other way round, though. All you'll likely succeed in doing is putting the vi commands into the file. This, ladies and gentlemen of the jury, points up the essential difference between a modal and a non-modal way of doing things. -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
In message , Jean-Michel Pichavant wrote: > Why buy an IDE when you just need a text editor ? Because all the cool kids have one. If you want to be different and individual like them, you have to have what they have. -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
In message , Arnaud Delobelle wrote: > That's why I use ed. After 20 years of suffering with vi, I finally decided to switch to Emacs. Yes, it has lots of fancy features and "modes" and things, but it wasn't hard to figure out how to turn the intrusive stuff off, and still leave a very powerful and useful editor. -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
In article , "Rhodri James" wrote: > On Tue, 26 May 2009 14:22:29 +0100, Roy Smith wrote: > > > My pet peeve is syntax-aware editors which get things wrong. For > > example, > > the version of emacs I'm using now doesn't parse this properly: > > > > '''A triple-quoted string. Some editors won't get this right''' > > > > The solution is to change the outer quotes to double-quotes, but it > > annoys me when I have to change my code to appease a tool. > > It's the separate python-mode that gets this (and much else) wrong. > The Python mode that Ubuntu packages with emacs 22.2.1 works just > fine. Cool. I'll see if I can snarf that and use it instead. -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On Tue, 26 May 2009 14:22:29 +0100, Roy Smith wrote: My pet peeve is syntax-aware editors which get things wrong. For example, the version of emacs I'm using now doesn't parse this properly: '''A triple-quoted string. Some editors won't get this right''' The solution is to change the outer quotes to double-quotes, but it annoys me when I have to change my code to appease a tool. It's the separate python-mode that gets this (and much else) wrong. The Python mode that Ubuntu packages with emacs 22.2.1 works just fine. -- Rhodri James *-* Wildebeeste Herder to the Masses -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
In article , Bar Shirtcliff wrote: > I can't say a thing about other editors, except that when some shell > script perversely dumped me into vi a month ago, I felt as horrified > as if some actually living bugs had crawled out of my own reflection > on the computer screen and fallen, clicking and scraping, onto the > keyboard. That's a personal reaction - totally irrelevant, of course. : q ! All the vi you ever need to know :-) The real problem is when you get dumped into some editor other than you one you expected and don't realize it for a while. It's really amazing how much damage you can do to a file by typing (for example) emacs commands at vi. Especially if you accidentally stumble upon the sequence for "save file". -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
In article , Arnaud Delobelle wrote: > That's why I use ed. Ed is the standard text editor [1]. Ed is open > source [2]. I still use ed sometimes. If I'm on a box which doesn't have emacs installed (or using something whose terminal emulation is totally broken), it lets me get work done. -- http://mail.python.org/mailman/listinfo/python-list
RE: What text editor is everyone using for Python
I use Textmate (with vim keybindings) on OS X or just vim on the others OS's. I still can't decide on which IDE between Wing, PyDev and Netbeans. Ben Racine -Original Message- From: python-list-bounces+bjracine=glosten@python.org [mailto:python-list-bounces+bjracine=glosten@python.org] On Behalf Of Dave Angel Sent: Tuesday, May 26, 2009 2:36 PM Cc: python-list@python.org; Lacrima Subject: Re: What text editor is everyone using for Python Lacrima wrote: >> I am new to python. >> And now I am using trial version of Wing IDE. >> But nobody mentioned it as a favourite editor. >> So should I buy it when trial is expired or there are better choices? > I'm a little surprised nobody has explicitly mentioned Komodo IDE (the full version). Although it's not free, it has plenty of useful features, is very configurable, supports Python and a host of other languages, and is a full IDE with an out-of-process debugger. This means you can step through GUI code, without it interfering with the debugger's event loop. You can customize it in four ways: 1) through Edit->Preferences 2) through recorded macros 3) through macros written in Javascript 4) through macros written in Python A subset of Komodo IDE is available as Komodo Edit, which is open source. Apparently Komodo is developed from some of the same code base as Firefox, so they can be integrated more tightly when debugging internet stuff. I haven't tried anything of the sort, so I can't say how well this works, and for what. -- http://mail.python.org/mailman/listinfo/python-list -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
Lacrima wrote: I am new to python. And now I am using trial version of Wing IDE. But nobody mentioned it as a favourite editor. So should I buy it when trial is expired or there are better choices? I'm a little surprised nobody has explicitly mentioned Komodo IDE (the full version). Although it's not free, it has plenty of useful features, is very configurable, supports Python and a host of other languages, and is a full IDE with an out-of-process debugger. This means you can step through GUI code, without it interfering with the debugger's event loop. You can customize it in four ways: 1) through Edit->Preferences 2) through recorded macros 3) through macros written in Javascript 4) through macros written in Python A subset of Komodo IDE is available as Komodo Edit, which is open source. Apparently Komodo is developed from some of the same code base as Firefox, so they can be integrated more tightly when debugging internet stuff. I haven't tried anything of the sort, so I can't say how well this works, and for what. -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On May 26, 2009, at 8:07 , Lacrima wrote: I am new to python. And now I am using trial version of Wing IDE. But nobody mentioned it as a favourite editor. So should I buy it when trial is expired or there are better choices? I have found that the appreciation of a text editor varies greatly across different people. What one person swears by, feels clunky to another. On the Mac, I like TextMate because I find it pretty clean and fast. On Windows I've used Notepad++, Emacs, Crimson, and possibly a few others. What I recommend is to try out some of the editors in: http://wiki.python.org/moin/PythonEditors and see how it works for you. Depending on what you need, and how they "feel", you may find what you want with a free editor. bb -- Brian Blais bbl...@bryant.edu http://web.bryant.edu/~bblais -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On May 26, 2009, at 11:17 , Ken Seehart wrote: Lacrima wrote: I am new to python. And now I am using trial version of Wing IDE. But nobody mentioned it as a favourite editor. So should I buy it when trial is expired or there are better choices? Jean-Michel Pichavant wrote: Why buy an IDE when you just need a text editor ? I don't get it. Anyway gvim (aka vim aka vi) and emacs are the most powerful editors for years. Both have Windows and Linux version and most important, they both are very effective at editing any file type (python, C, latex, love letters...) Emacs is more accessible to the newby but requires time to master its complex features. Gvim may be complex for the newby due to its command/insertion mode constant switch, but is as powerful as emacs can be. Being a gvim adept, I should stat that gvim is far better but it would only feed the neverending war. Jean-Michel I've heard notepad is pretty good. http://www.notepad.org/ I'm sorry, but ed is the standard editor[1]. :) bb [1] http://en.wikipedia.org/wiki/Ed_(text_editor) -- Brian Blais bbl...@bryant.edu http://web.bryant.edu/~bblais -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
Zamnedix wrote: So what do you guys use, and why? Hopefully we can keep this civil. Nano! Nano! Nano Revolution!!! Thank you, Mork[1] :) -tkc (who uses Vim for Python coding, and on rare occasions, Notepad or ed) [1] http://en.wikipedia.org/wiki/Mork_%26_Mindy -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
Ken Seehart writes: | | Lacrima wrote: | > I am new to python. | > And now I am using trial version of Wing IDE. | > But nobody mentioned it as a favourite editor. | > So should I buy it when trial is expired or there are better choices? | > | | I've heard notepad is pretty good. http://www.notepad.org/ | | :-) Ken | Seriously. I actually know a programmer who does all of his work in notepad: no macros, syntax-highlighting, or any other robust features, plus that horrible font. I use emacs. No alternative presentation rivals, for me, the ability to program your editor while you use it. Never having to reach for the mouse in emacs is a terrific (and optional) bonus. I guess it depends on how you work. If you're willing to invest a fair amount of time in your editor and you like the idea of being able to drastically modify your editor while you use it, you should consider emacs. Emacs has a good on-line help system, including a friendly emacs lisp introduction. If you're using a Mac, check out Aquamacs Emacs. I can't say a thing about other editors, except that when some shell script perversely dumped me into vi a month ago, I felt as horrified as if some actually living bugs had crawled out of my own reflection on the computer screen and fallen, clicking and scraping, onto the keyboard. That's a personal reaction - totally irrelevant, of course. Bar -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On Tue, May 26, 2009 at 8:07 AM, Lacrima wrote: > I am new to python. > And now I am using trial version of Wing IDE. > But nobody mentioned it as a favourite editor. > So should I buy it when trial is expired or there are better choices? We're mostly talking about text editors, not full-fledged IDEs. Those are actually 3 different pieces of flame bait right there: favorite text editor, favorite IDE, and text editors vs. IDEs. > > -- > http://mail.python.org/mailman/listinfo/python-list > -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
Lacrima wrote: I am new to python. And now I am using trial version of Wing IDE. But nobody mentioned it as a favourite editor. So should I buy it when trial is expired or there are better choices? Jean-Michel Pichavant wrote: Why buy an IDE when you just need a text editor ? I don't get it. Anyway gvim (aka vim aka vi) and emacs are the most powerful editors for years. Both have Windows and Linux version and most important, they both are very effective at editing any file type (python, C, latex, love letters...) Emacs is more accessible to the newby but requires time to master its complex features. Gvim may be complex for the newby due to its command/insertion mode constant switch, but is as powerful as emacs can be. Being a gvim adept, I should stat that gvim is far better but it would only feed the neverending war. Jean-Michel I've heard notepad is pretty good. http://www.notepad.org/ :-) Ken -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On May 25, 10:35 am, LittleGrasshopper wrote: > With so many choices, I was wondering what editor is the one you > prefer when coding Python, and why. I normally use vi, and just got > into Python, so I am looking for suitable syntax files for it, and > extra utilities. I dabbled with emacs at some point, but couldn't get > through the key bindings for commands. I've never tried emacs with vi > keybindings (I forgot the name of it) but I've been tempted. > > So what do you guys use, and why? Hopefully we can keep this civil. Nano! Nano! Nano Revolution!!! -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
Lacrima wrote: > I am new to python. > And now I am using trial version of Wing IDE. > But nobody mentioned it as a favourite editor. > So should I buy it when trial is expired or there are better choices? I use Wing IDE and like it. It very nicely enforces consistent space indentations and other Python basics that might fall through the cracks when writing. I'm not too hot on the auto-suggest, but I haven't seen any other IDE do better. --David -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
On Tue, May 26, 2009 at 11:17 AM, Ken Seehart wrote: > > Lacrima wrote: > >> I am new to python. >> And now I am using trial version of Wing IDE. >> But nobody mentioned it as a favourite editor. >> So should I buy it when trial is expired or there are better choices? >> >> > > Jean-Michel Pichavant wrote: > >> Why buy an IDE when you just need a text editor ? I don't get it. >> Anyway gvim (aka vim aka vi) and emacs are the most powerful editors for >> years. Both have Windows and Linux version and most important, they both are >> very effective at editing any file type (python, C, latex, love letters...) >> Emacs is more accessible to the newby but requires time to master its >> complex features. >> Gvim may be complex for the newby due to its command/insertion mode >> constant switch, but is as powerful as emacs can be. Being a gvim adept, I >> should stat that gvim is far better but it would only feed the neverending >> war. >> >> Jean-Michel >> >> I've heard notepad is pretty good. http://www.notepad.org/ > But it's not available on any *real* OS. XP > > :-) Ken > > > -- > http://mail.python.org/mailman/listinfo/python-list > -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
Lawrence D'Oliveiro writes: > In message , Hendrik van > Rooyen wrote: > >> "Lawrence D'Oliveiro" wrote: >>> >>> Why [do you want syntax highlighting]? >> >> It makes your screen look more busy as you type - for instance, if you >> type a " or a ' then it treats the rest of the file from that point on as >> belonging to the same string you are about to start typing, and colours it >> all using the colour you have selected for displaying string literals. >> This is basically to make you seasick and to force you to type the closing >> quote immediately and then to back arrow to inside the string again to >> finish typing the string, thereby making sure that firstly you type more >> keystrokes, which will look good on your productivity summary, and >> secondly to save the Python parser the hassle of dealing with a string >> that has no end quote. > > Yeah, that's about what I figured. I think I first came across it 15 years > ago in Metrowerks CodeWarrior. I tried it for a while, but it didn't really > help with any of my program bugs, so I turned it off. It's a bit like the colour-coding of electrical cables - distracting more than anything else! And don't start me on traffic lights... They nearly give me an epileptic fit each time. That's why I use ed. Ed is the standard text editor [1]. Ed is open source [2]. [1] http://www.gnu.org/fun/jokes/ed.msg [2] http://www.gnu.org/fun/jokes/ed -- Arnaud -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
LittleGrasshopper wrote: > With so many choices, I was wondering what editor is the one you > prefer when coding Python, and why. I normally use vi, and just got > into Python, so I am looking for suitable syntax files for it, and > extra utilities. I dabbled with emacs at some point, but couldn't get > through the key bindings for commands. I've never tried emacs with vi > keybindings (I forgot the name of it) but I've been tempted. > > So what do you guys use, and why? Hopefully we can keep this civil. SciTE I like one big uncomplicated window, tabbed file panes, syntax coloring and help with indentation. There's nothing to it I hate. It would be nice if customization were easier. Mel. -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
Lacrima wrote: I am new to python. And now I am using trial version of Wing IDE. But nobody mentioned it as a favourite editor. So should I buy it when trial is expired or there are better choices? It's my favorite. Buy it. I'm not aware of any better choices. If you can afford the Pro version buy that, especially if you are planning any large projects. But take a peek at the feature list before making that decision: http://www.wingware.com/wingide/features . Some of my favorite Pro features are test suite support, advanced debugging, and code folding. The debugger is way more powerful in the Pro version. Of course, favorites are ultimately determined by religious preference. Ken -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
In article , "Hendrik van Rooyen" wrote: > [syntax coloring] makes your screen look more busy as you type - for > instance, if you > type a " or a ' then it treats the rest of the file from that point on as > belonging to the same string you are about to start typing, and colours it > all using the colour you have selected for displaying string literals. > This is basically to make you seasick and to force you to type the closing > quote immediately Good syntax coloring implementations have some hysteresis built in, to prevent transient things (like strings you haven't closed yet) from changing the entire file. If you stop typing for a while, it then does a full update. This avoids the problem above. That being said, syntax coloring is like any other tool. It's worth trying, but if you find it hinders you more than it helps, turn it off. Different strokes for different folks. My pet peeve is syntax-aware editors which get things wrong. For example, the version of emacs I'm using now doesn't parse this properly: '''A triple-quoted string. Some editors won't get this right''' The solution is to change the outer quotes to double-quotes, but it annoys me when I have to change my code to appease a tool. -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
Why buy an IDE when you just need a text editor ? I don't get it. Anyway gvim (aka vim aka vi) and emacs are the most powerful editors for years. Both have Windows and Linux version and most important, they both are very effective at editing any file type (python, C, latex, love letters...) Emacs is more accessible to the newby but requires time to master its complex features. Gvim may be complex for the newby due to its command/insertion mode constant switch, but is as powerful as emacs can be. Being a gvim adept, I should stat that gvim is far better but it would only feed the neverending war. Jean-Michel Lacrima wrote: I am new to python. And now I am using trial version of Wing IDE. But nobody mentioned it as a favourite editor. So should I buy it when trial is expired or there are better choices? -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
Lacrima writes: > I am new to python. > And now I am using trial version of Wing IDE. > But nobody mentioned it as a favourite editor. > So should I buy it when trial is expired or there are better choices? That is a slightly better question. Try some of the free alternatives. I do happen to use emacs. It took me quite a lot of adjusting to get used to it after being a vim user for almost ten years. Doesn't cost anything to give one a shot and see if it works for you. The choice of editor is a personal one (hence the reluctance to answer your original question). -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
I am new to python. And now I am using trial version of Wing IDE. But nobody mentioned it as a favourite editor. So should I buy it when trial is expired or there are better choices? -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
In message , Hendrik van Rooyen wrote: > "Lawrence D'Oliveiro" wrote: >> >> Why [do you want syntax highlighting]? > > It makes your screen look more busy as you type - for instance, if you > type a " or a ' then it treats the rest of the file from that point on as > belonging to the same string you are about to start typing, and colours it > all using the colour you have selected for displaying string literals. > This is basically to make you seasick and to force you to type the closing > quote immediately and then to back arrow to inside the string again to > finish typing the string, thereby making sure that firstly you type more > keystrokes, which will look good on your productivity summary, and > secondly to save the Python parser the hassle of dealing with a string > that has no end quote. Yeah, that's about what I figured. I think I first came across it 15 years ago in Metrowerks CodeWarrior. I tried it for a while, but it didn't really help with any of my program bugs, so I turned it off. -- http://mail.python.org/mailman/listinfo/python-list
Re: What text editor is everyone using for Python
Steven D'Aprano writes: > e.g. I can instantly tell if I neglected to close a string, because > my code displays in red. I like syntax hightlighting for whitespace related things in python. e.g to highlight tabs, or whitespace at the end of a line. -- http://mail.python.org/mailman/listinfo/python-list