Is it normal that PyDev doesn't work with standard modules out of box?

nbd · 2015-01-30 04:10:16

On my machine PyDev doesn't see the standard compiled modules when they are imported with 'import' directive. Such modules as curses, termios, select etc. That is those modules that are residing in the '/usr/lib/python3.4/lib-dynload' directory. PyDev marks those modules as 'unresolved import' during the 'coding time'. Although if a module with such 'unresolved import' error mark is run within PyDev, it runs without problems.

The workaround that I found to this problem is to add the unresolved modules to the 'forced builtin' list in the PyDev configuration. But is it normal for PyDev that every standard module must be individually configured in order for PyDev could import it? Or there is some other solution that enables PyDev to work with standard compiled modules without adding every of them to 'forced builtins'?

Thanks.

whoops · 2015-01-30 21:16:12

Do you mean eclipse-pydev?

Had the same problem with that - also lots of trouble with context completion not working. There was a weird external script back then (2 years ago maybe) that ran over the modules and created some sort of reference files that then could be imported manually.... which "fixed" a lot of the issues. But also it was a huge mess and the results were still rather buggy. I asked in various irc's and forums - everyone told me to "just use something else". Haven't been able to figure out how this IDE is supposed to be used effectively despite much effort - maybe you already have to be a python expert to use it and it's just unsuited for learning.

Unless it's gotten a lot better in the last 2 years or you already tried everything else I wouldn't recommend you to waste too much time on it.
( because I did. And now I'm using c++ / cmake because it seemed so much easier than python after that )

Last edited by whoops (2015-01-30 21:17:18)

nbd · 2015-01-31 04:24:29

whoops wrote:

Had the same problem with that

Does it mean that everyone has this problem with the Python module of very popular IDE?? No one who installs PyDev has it working without first finding out why they have problems with importing standard modules (to find the solution to this problem took some web research for me) and after that adding every standard compiled module to some configuration list??

Last edited by nbd (2015-01-31 04:25:31)

whoops · 2015-01-31 06:56:08

I'm not sure anyone's been using pydev. From what I've heard there's not really much of a reason to set up eclipse for python development and "everyone" else is using geany / eric /kdevelop / just the python console + vim / whatever.

Then again - that was a whole while ago when the project seemed to be in worse shape and it almost looks as if development has been more active since and stuff has gotten a LOT more user-friendly: isn't everything you needed to do directly behind the "important getting started" link on their front page now? I only took a brief glance so I'm not sure, but it looks a LOT better than when I had the problem (http://pydev.org/manual_101_interpreter.html)

Last edited by whoops (2015-01-31 06:57:34)

nbd · 2015-01-31 07:07:02

Actually PyDev seems like a pretty good IDE for Python in other respects than then aforementioned problem with imports. Thats why it looks strange that this problem hasn't been corrected for years.

Arch Linux

#1 2015-01-30 04:10:16

Is it normal that PyDev doesn't work with standard modules out of box?

#2 2015-01-30 21:16:12

Re: Is it normal that PyDev doesn't work with standard modules out of box?

#3 2015-01-31 04:24:29

Re: Is it normal that PyDev doesn't work with standard modules out of box?

#4 2015-01-31 06:56:08

Re: Is it normal that PyDev doesn't work with standard modules out of box?

#5 2015-01-31 07:07:02

Re: Is it normal that PyDev doesn't work with standard modules out of box?

Board footer