http://www.jetbrains.net/confluence/display/PYH/JetBrains+PyCharm+PreviewEnjoy--
Vous recevez ce message, car vous êtes abonné au groupe Google Groupes MontrealPython.
Pour envoyer un message à ce groupe, adressez un e-mail à montrea...@googlegroups.com.
Pour vous désabonner de ce groupe, envoyez un e-mail à l'adresse montrealpytho...@googlegroups.com.
Pour plus d'options, consultez la page de ce groupe : http://groups.google.com/group/montrealpython?hl=fr-CA
scrap the caveat!
turns out there's a netbeans plugin that does a full vim "emulation" (it
actually uses a lot of vim code to do so) - http://jvi.sourceforge.net/
And it supports most of what vim does, it's not just a custom
keybinding setting that emulates vi.
My only caveat so far is that it doesn't read in ~/.vimrc, so you have
to reset your options (such as expandtabs), but you can set them
nonetheless from the GUI.
There was a long thread in the linkedin python group about Python IDEs:
http://www.linkedin.com/groupAnswers?viewQuestionAndAnswers=&gid=25827&discussionID=10990694
Considering you have eclipse+pydev, netbeans/python and eric that are chock full of all features you'd want (short of actual emacs or vim integration :) ), i really don't see at this point why anyone would spend time with a non-free python IDE.
Maybe I'm old school but I don't quite get what the point of an IDE
is. If want to edit code, I use and editor with programmable macros;
if I need to interact with my code, I use the greatest Python shell
out there, ipython; if I want to debug, I use the greatest debugger
money can buy, the Pylons debugger (or pdb once in a while); and if I
want to edit a gui, I fire up Qt Designer. These tools are all
related but they are loosely coupled and cramping them inside a single
window provides very little benefit compared to them being only one
alt-tab away.
Now you might be tempted to reply to me and to start a long flame war,
but that would not be very productive. The productive way to do it is
to jump on the stage, just like Jean did, and to show us how your
programming environment helps you to work better. Don't try to bash
on other tools; it feels good but it won't help others to understand
how to work with your tools.
Any taker?
--
Yannick Gingras
http://ygingras.net
http://confoo.ca -- track coordinator
http://montrealpython.org -- lead organizer
;-P
a
2010/2/9 Yannick Gingras <ygin...@ygingras.net>:
--
Alexandre Quessy
http://alexandre.quessy.net/
On February 9, 2010, Éric St-Jean wrote:
> There was a long thread in the linkedin python group about Python IDEs:
> http://www.linkedin.com/groupAnswers?viewQuestionAndAnswers=&gid=25827&discussionID=10990694
>
Maybe I'm old school but I don't quite get what the point of an IDE
is.
Now I'm no AOP expert, so I speak from experience on OO-style
projects, but I did notice that the only time I need to touch more
than 3-4 files is when the core library did not respond to my
expectations (poor docs or buggy code) or I'm not focusing on a single
task. I feel like as code matures and as my skills improve, both
issues disappear.
This is all assuming you are programming in Python. I remember the
saying "Life is too short for Java"; I would add that there is no
screen big enough to hold its code. When I work with Java, I make
where I have a mouse with a scroll wheel.
Dimitry
You both have excellent points, but recently i've been working on a
contract working with Zope+Plone. Arg! what a mess. A simple document
type (which holds a page you see in the site) has 800+ attributes and
methods. They went completely insanely crazy with multiple inheritance,
so you have no idea where one of those methods came from. In such a
model, you always have to play with 4-5 files open at once. My normal
vim setup has a tree on the left (with classes and methods of the open
files) and 2 open files side-by-side. It works well. But having an IDE
which will have indexed all of zope+plone+the libs+my project+python
libs allows me to easily jump to the actual definition of a method. I
know this can all be done with vim or emacs, but then there's also easy
debugging: editing the file and just easily do "run my project until it
hits my cursor". What i normally do in vim is to add "import pdb;
pdb.set_trace()", then switch to shell and run it. That works, but at
some point things just become disjointed, i find. So i'm generally not
an IDE person, and for 95% of my tasks i'll stick with my vim setup. But
for some tasks and huge messes like plone, i think i'll give
netbeans/python a try, especially now that i found this full vim mode
for it...
i'm not sure it'll foot the bill and i'll probably go back to vim,
though :)
but i do see a point to using IDEs for large code bases.
The eternal debate: simple tools vs swiss knife
I use eclipse daily both as an IDE and as a development platform.
what I like about it:
* its compiler that can recompile only changes to resources (it can be
used on its own)
* some refactoring methods
* api to create your own plugins to access the underlying AST/resources/etc
* great [java] debugger
* errors/warnings views and error markers containing the exact
location in the file
what I dislike:
* editing code in a file editor is much slower than editing it in vim
* not following the unix philosophy of breaking tools apart
* voodoo art for the product build system (it generates on the fly
huge amounts of ant code .. an ant diarrhea)
* all the bloatness associated with it (mylyn, team, synchronization,
xml tools, etc)
* requires at least 2 screens to work with big projects (file editors,
console, junit, problems, etc)
some solutions
* eclim http://eclim.org/ "The primary goal of eclim is to bring
Eclipse functionality to the Vim editor."
* the "golden path": decoupling the IDE:
* $EDITOR for file editing
* another program to deal with the resources/ast/indexing of the
underlying code base
* api for the AST
* refactoring could be scripted instead
In python, I usually use screen with multiple tabs (vim editors,
ipython shell, etc).
In big java enterprisey applications with huge dependencies, only
using vim is not always enough.
> Other than that, I think it is a matter of personal affairs.
>
> A+
>
> -------------
> Pierre
>
I do agree with your statement that the choice of your development
environment is a personal matter, but perhaps with a twist. I'm a
believer in the social-psychological-emotional motivation of software
choices (including development tools). David Hansson's (Rails dude)
"programmer happiness" applies here. Not sure if happiness leads to
better efficiency (presumably the goal of a better software choice?!),
but if it does, use whatever you like to write your software even if it
is a pencil and a paper. Anyone knows an interested research
psychologist who perhaps can help here? :)
Cheers,
Ahmed