In the IDE or not? Beginner Developer Dilemma

Question

Basically, my friend and I are just planning to work on a Python project that will have a GUI interface, as well as enable file transfer and remote file listing. We have most of the tools we will use, Glade, Python, etc.

I just want to know whether to use an IDE or not.

I only heard good things about Anjuta, but I am not convinced of its support for Python; follow comments?
And is there also another good IDE I have to check?

I am currently just planning on coding, as usual, in vim.

Answer 1

There are many IDEs you can check. Take a look at PyDev , PIDA , Komodo , Eric .

I personally do not think that IDEs add so much to software development (on this scale and in this language). Python has great external debugging tools, and refactoring is not that difficult with a program of this size.

Are you currently using or want to use any functions that you skip in the current editor? If so, choose another, otherwise stick to what you like best.

As long as you have version control integration, you should be fine.

Answer 2

Debugging with the IDE makes your life a lot easier.

Answer 3

Python is a particularly strange language, since a full-fledged IDE doesn’t really add a lot (and some argue that the IDE tends to severely restrict your flow with the mouse in Python). I use regular Vim and Gedit for development in Python and have never missed using the IDE.

Text editors like Vim or Emacs can be configured flexibly enough to match the power of the IDE, so it doesn't matter which direction you go.

Answer 4

Personally, I use most of my Python codes in Vim, but from time to time I want to use the full IDE, and I use Eclipse with Pydev back then.

It depends on your own preferences, some people absolutely love Vim and will not use anything else. Others simply cannot work without an IDE.

Here is the list:

• Python IDE: http://wiki.python.org/moin/IntegratedDevelopmentEnvironments
• Python Editors: http://wiki.python.org/moin/PythonEditors

Answer 5

From the point of view of using the IDE or not, it does not matter. I prefer to use the IDE, because I like to have the tools I need, in one beautiful, neat little package that can handle all my development. However, using a text editor is just as good, especially those that are powerful and extensible like vi (m) and (x) emacs. However, the real reasons for using the IDE are code completion, indentation management, code folding, refactoring support, and debugging.

If you want to check out other IDEs for Python development, I would also suggest looking at NetBeans and Eclipse with their respective plugins. I personally prefer NetBeans, because I have a feeling that PyDev is going to go down since Aptana bought them (they previously destroyed RadRails, which is the Eclipse plugin for developing Ruby on Rails) and don’t want to build a tool that may not be practical long term.

Answer 6

With Java, I would not say an IDE for beginners, because you have to understand CLASSPATH first.

With Python, I would say PyCharm from JetBrains. IntelliJ - the best Java IDE; PyCharm does my Python work with pleasure.

Answer 7

IMHO, without using an IDE for development, just like using a typewriter to write a novel. No one said you cannot, but why should you try this when you already have a laptop?

Answer 8

I am code in Vim for python. If you want to use the IDE, I would recommend IntelliJ PyCharm. I use vim because the actual editing is far superior, and if you are a strong user, there is very little that you cannot do easily.

PyCharm provides assistance with api, providing completion and helps with some basic refactoring. These benefits wear out sooner than you expected. I use the grep and vim regular expression for refactoring - this is a little more work than pycharm, but if you can handle it, the benefits of vim clearly outweigh with ide.

I assume that you are developing in a * nix environment, if you use windows, I would recommend using Ide.

Answer 9

Unlike some other guys, I think the IDE does a lot for software development, even for a dynamically typed language like Python, which makes static analysis difficult.

The preferred IDE for Python development is Eclipse with PyDev. Before that, I encoded in Notepad ++, which is not much different from the PyDev editor in terms of features. PyDev has some great features that you won't find in a "normal" editor:

• It displays warnings and syntax errors (almost) in real time. The text editor will not tell me about typos, but PyDev. As another example, unresolved imports or undefined functions (e.g. due to a typo) are marked as warnings / errors. And there are many more common errors that are automatically detected, and PyDev can be integrated with pylint so that warnings and errors from pylint are displayed using regular icons in the editor.
• Introspection AutoComplete
• General view of the current module and its classes

In addition, Eclipse is also great for any programming project. I especially like the fully integrated interface - project explorer, editor, outline, console, problem overview, startup configurations, etc. When using Vim, Emacs or the like, I think you will need to install many plugins or custom scripts to achieve the same.

As you said, you want to make a project, I think Eclipse is a good choice. To quickly crack a small Python script, it certainly overflows.

Answer 10

If you are just starting to learn the python / glade / gtk stack, I would say that you should start without an IDE to find out how it works inside. This will help you later when your code is bigger and more complex.

However, a good IDE helps in many ways; I would not recommend using them in the long run. This article can help you decide if you need to: http://infoworld.com/d/developer-world/infoworld-review-nine-fine-python-development-tools-374

Answer 11

these are horses for courses, I personally am much happier with textmate or vim and a pleasant cup of coffee, but this is what is more convenient for you.

there is no shame in using the IDE, if this is what gives you the idea that the masses are the most effective, then use whatever you like.

however, when you start, I would approve of something with intellisense, as it will teach you the basics, when you print, give it a year, and you will become the master.

Answer 12

Two ways to approach this:

• Use what you are used to. If you've used the editor in the past and know its quirks, stick with it. You will spend less time figuring out how to work with the tool and spend more time on the actual project.

• Use something new. Anjuta, vim, whatever, if you have not spent too much time on this. You will learn a lot of new things besides your actual project, but the project itself will not be completed as quickly as it can be.

Personally, I prefer 2. Always learn something new if it doesn't crackle and it should be done on Fridays. The IDE can only help you so much, but when you are still in the training phase, the more time you spend on the code yourself, the better.

Answer 13

I am not a Python programmer, but I prefer not to use an IDE.
The reason for this is because the IDEs are often large and do too many things for me, and using Notepad ++ and the command line allows me to trim things according to my needs, rather than being surrounded by functions that I don’t use. This makes it easier for me to learn, because I have more control over what is happening.

Answer 14

Do not learn coding with the IDE. Code with him!

Answer 15

I find using the IDE to significantly improve the performance of my Python code. In particular, using wingide makes coding in python a pleasure. It has all the normal things you expect (syntax highlighting, autocomplete, etc.), but the killer functions are a debugger and a debugging probe.

These two functions are worth the cost of the program. It allows you to see the current state of the application and try out python commands in real time at breakpoints. I find this especially useful for examining the current state and trying out the code to see if it will work. I often write some of the more complex sections of code in the live debugging probe, and they copy them into my application. Very nice.