The following forum message was posted by agronholm at
http://sourceforge.net/projects/pydev/forums/forum/293649/topic/4477776:
First of all, I would like to thank fabioz for all the work he has done on
Pydev.
I continue recommending Pydev to others as the best open source Python
IDE available.
Nevertheless, I do have several issues that bug me every single day I use it.
I would like to hear which one of these I should open as issues in the tracker
and which ones have no hope of getting rectified.
So, here goes, in order of annoyance factor:
1. Pydev does not see namespace packages properly (ie. "paste" of Paste Deploy,
Pastescript and Paste) and considers them unresolved imports.
2. Code formatting messes up signed numbers ("-1" turns into "- 1").
3. Autocompletion for many standard library functions does not work. Try
autocompleting partial (from functools) or asctime (from time). Isn't this the
entire point of specifying forced built-ins in the interpreter configuration?
4. There seems to be no way to get rid of error markers coming from imports
that work but cannot be seen through static analysis of the code (ie. from
nose.tools
import assert_raises), at least not without entirely disabling import errors.
5. By default, and contrary to popular conventions, Pydev adds an "src"
directory
and marks that as the only source directory. Most Python projects host their
packages directly in project root. How many projects can you really find that
have an src directory? I don't think I've yet seen one in the wild.
6. The interactive interpreter does not respond correctly to arrow key presses.
If I press "up", I expect to get the previous entered line, or failing that,
no action. Instead, my cursor moves one line up. The same goes for other arrow
keys.
7. When the project is cleaned up, error markers that get removed leave the
red squiggly lines in the code behind. This applies to warnings too.
8. In Jython projects, Pydev does not recognize static Java imports such as
imports of inner classes or enum values and considers them unresolved imports.
9. There is no "rename module" functionalityin Pydev, so if you rename a module
and forget to add the .py extension, you end up with an extensionless file.
No biggie, but annoying nonetheless, since JDT handles this just fine.
10. Jython 2.5 grammar is slightly different from the CPython 2.5 grammar, but
Pydev does not support this. Jython 2.5 supports class decorators and allows
the use of the print keyword in imports (due to javax.print.* etc.). My request
for supporting this was flat out rejected.
11. The nose test runner does not display the list of unit tests beforehand,
despite this being supported in nose (nosetests --collect-only -v).
12. Pydev does not utilize the Java build path entries for import resolution
in joint Java/Jython projects (where a PythonInterpreter is used from the Java
application), so I have to add them separately to the project's Python
configuration
to get rid of the error markers (this is not necessary for running, that works
fine).
------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
Pydev-users mailing list
Pydev-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pydev-users
