I suggest you use your google foo that you just showed to search in this group for the numerous discussions about emacs, vi, eclipse+pydev, wing ide, komodo and notepad.
> I suggest you use your google foo that you just showed to search in this > group for the numerous discussions about emacs, vi, eclipse+pydev, wing > ide, komodo and notepad.
I see too many threads. But I don't any of them give me a complete comparison between different choices. If you are familiar with different choices, would you please give me some advices?
> On Nov 15, 11:15 am, "Diez B. Roggisch" <de...@nospam.web.de> wrote: >> Peng Yu schrieb:
>>> There had been some discussion on IDE. But I'm not sure what pros and >>> cons of each choice. Current, I'm using vim and ctags. >>> Could somebody give some advices on choosing the best IDE for me? >>> http://groups.google.com/group/comp.lang.python/browse_thread/thread/... >> I suggest you use your google foo that you just showed to search in this >> group for the numerous discussions about emacs, vi, eclipse+pydev, wing >> ide, komodo and notepad.
> I see too many threads. But I don't any of them give me a complete > comparison between different choices. If you are familiar with > different choices, would you please give me some advices?
Again: read the threads. They discuss the various aspects. They arose because of the same question asked as yours. If you don't find in them what you are looking for, chances are hight that you won't get it.
This is very much a question of personal preferences, not of feature-matrices and strict metrics. So go, read, and them make an informed choice on what at least to try. Stick with what you prefer.
And given your track record in this group here, I assume regardless of *what* beautiful scheme of explaining various IDEs and their respective merits, they all fall short of your "unique" way of doing things.
On 15 Nov, 18:09, Peng Yu <pengyu...@gmail.com> wrote:
> There had been some discussion on IDE. But I'm not sure what pros and > cons of each choice. Current, I'm using vim and ctags.
> Could somebody give some advices on choosing the best IDE for me?
There is a plug-in to develop (amd debug) Python using MS Visual Studio. It works with IronPython and CPython.
There is the PyDev plug-in for Eclipse.
There is Komodo from ActiveState.
There is KDevelop in KDE4.
Which is better? I don't know.
My impression is that Python development does noe need an IDE like e.g. C++ development do. There is no build process, which takes the major advantage of the IDE away. I am fine with a editor like IDLE or Kate.
> On 15 Nov, 18:09, Peng Yu <pengyu...@gmail.com> wrote:
> > There had been some discussion on IDE. But I'm not sure what pros and > > cons of each choice. Current, I'm using vim and ctags.
> > Could somebody give some advices on choosing the best IDE for me?
> There is a plug-in to develop (amd debug) Python using MS Visual > Studio. It works with IronPython and CPython.
> There is the PyDev plug-in for Eclipse.
> There is Komodo from ActiveState.
> There is KDevelop in KDE4.
> Which is better? I don't know.
> My impression is that Python development does noe need an IDE like > e.g. C++ development do. There is no build process, which takes the > major advantage of the IDE away. I am fine with a editor like IDLE or > Kate.
I'd like to offer the group the anecdote of the great Resolver IDE migration.
Developers at Resolver, where I work, choose their own IDE. Being developers, that meant every single person chose a different one. We had them all. Which turned out, slightly unexpectedly, to be just fine.
We pair on all production code. So this meant we all spent a lot of time sitting at each other's desks. We soon all became pretty familiar with each other's environments - there's nothing like 8 hours a day of hands-on usage, coupled with sitting right next to a bone-fide expert to get you up to speed pretty quick. I even learned a little Emacs, holy cow!
Occasionally, after seeing the details of how well some other IDE worked, developers would switch from one to another.
Then, after about a year, a curious thing happened. One by one, in entirely independent decisions, almost all developers decided to migrate to either Emacs or Vi.*
Each person decided that the fancy features of their IDE wasn't as useful to them as having a flexible, powerful and lightweight editor which can easily be scripted to provide whatever ad-hoc features they need.
I regard this as an example of the way pairing spreads knowledge.
* I say 'most developers' - there were two notable exceptions: Michael Foord, who's prodigious contributions are legend, who likes Wing, and Will Reade, our tame brainiac, responsible for the exceedingly clever 'IronClad' open-source project, who likes the uncomplicated simplicity of TextPad.
As far as I can make out, TextPad has only two features, syntax highlighting and the ability to define a 'make' command, and a regex that is used to extract filenames and line-numbers from the resulting output of that make command. These are, it turns out, sufficient to transform a program that would otherwise simply be 'Notepad' into an entirely credible development environment.
On 16 Nov, 10:05, Jonathan Hartley <tart...@tartley.com> wrote:
> As far as I can make out, TextPad has only two features, syntax > highlighting and the ability to define a 'make' command, and a regex > that is used to extract filenames and line-numbers from the resulting > output of that make command. These are, it turns out, sufficient to > transform a program that would otherwise simply be 'Notepad' into an > entirely credible development environment.
When working with Java or C++ I like and IDE like KDevelop because it makes makefiles for me. And when debugging it is easier to insert break points graphically than use gdb from the terminal.
But apart from that, I prefer a tiny editor like Kate (yes I know, call me a heretic for not using emacs).
> On 15 Nov, 18:09, Peng Yu <pengyu...@gmail.com> wrote: >> There had been some discussion on IDE. But I'm not sure what pros and >> cons of each choice. Current, I'm using vim and ctags.
>> Could somebody give some advices on choosing the best IDE for me?
> There is a plug-in to develop (amd debug) Python using MS Visual > Studio. It works with IronPython and CPython.
> There is the PyDev plug-in for Eclipse.
> There is Komodo from ActiveState.
> There is KDevelop in KDE4.
> Which is better? I don't know.
> My impression is that Python development does noe need an IDE like > e.g. C++ development do. There is no build process, which takes the > major advantage of the IDE away. I am fine with a editor like IDLE or > Kate.
For more than ten years I had the same opinion. I found that a very lightweight "IDE" like PythonWin is sufficient for me together with print statements and the built-in post-mortem debugger for debugging.
But then, last year I had to find a tricky bug in my GUI code (wxPython) and thought that for this problem a debugger would be helpful. So I gave the Wing IDE with it's debugger a try and have been using it since then. Even though an IDE is not an absolute must, I found that my productivity increased a lot (25%?) and I would not want to miss: - code completion - powerful debugger (even if you only use the post-mortem debugger it will save you a lot of time compared to pdb.pm() as it takes only a mouse click to move to the exception point in the editor instead of looking at the line number and then find the same point in the editor...) - Mercurial integration - PyFlakes integration
On Nov 16, 1:05 am, Jonathan Hartley <tart...@tartley.com> wrote:
> Then, after about a year, a curious thing happened. One by one, in > entirely independent decisions, almost all developers decided to > migrate to either Emacs or Vi.*
> Each person decided that the fancy features of their IDE wasn't as > useful to them as having a flexible, powerful and lightweight editor > which can easily be scripted to provide whatever ad-hoc features they > need.
> I regard this as an example of the way pairing spreads knowledge.
That's the best justification for pair programming I've seen yet.
Jonathan Hartley <tart...@tartley.com> writes: > I'd like to offer the group the anecdote of the great Resolver IDE > migration.
[…]
It's great to see something refreshing and new — data beyond a single person's subjective experience! — come out of a topic that looked like it was just going to re-hash the same tired topic.
Thank you.
-- \ “What I resent is that the range of your vision should be the | `\ limit of my action.” —Henry James | _o__) | Ben Finney
|
