agronholm/gist:912493

## gistfile1.txt
Pydev does not see namespace packages properly (ie. "paste" of Paste Deploy, Pastescript and Paste) and considers them unresolved imports.

Code formatting messes up signed numbers ("-1" turns into "- 1").

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?

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.

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.

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.

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.

In Jython projects, Pydev does not recognize static Java imports such as imports of inner classes or enum values and considers them
unresolved imports.

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.

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.

The nose test runner does not display the list of unit tests beforehand, despite this being supported in nose (nosetests --collect-only -v).

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).
	Pydev does not see namespace packages properly (ie. "paste" of Paste Deploy, Pastescript and Paste) and considers them unresolved imports.

	Code formatting messes up signed numbers ("-1" turns into "- 1").

	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?

	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.

	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.

	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.

	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.

	In Jython projects, Pydev does not recognize static Java imports such as imports of inner classes or enum values and considers them
	unresolved imports.

	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.

	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.

	The nose test runner does not display the list of unit tests beforehand, despite this being supported in nose (nosetests --collect-only -v).

	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).