pydev-users

[Pydev-users] [pydev - Users] RE: code checking not working for new modules

[SourceForge.net <no...@so...>]

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=3767170
By: fabioz

Are your files in your pythonpath? Do you have any errors in your error log?

______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: 
https://sourceforge.net/forum/unmonitor.php?forum_id=293649

[Pydev-users] [pydev - Users] RE: code checking not working for new modules

[SourceForge.net <no...@so...>]

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=3776125
By: nobody

Thanks...I just noticed the errors in my error log.  

______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: 
https://sourceforge.net/forum/unmonitor.php?forum_id=293649

[Pydev-users] [pydev - Users] RE: code checking not working for new modules

[SourceForge.net <no...@so...>]

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=3779817
By: xyld

This isn't working for me either. To be honest I'm not sure I can even pinpoint
how long it hasn't been working for! I can't remember it ever working since
I purchased the extension.

Code analysis doesn't seem to be working in:

  a) new projects with a new file,
  b) old projects,
  c) old projects with a new file.
  d) a completely fresh workbench with a new project and a new file.

I've checked my settings, code analysis is definitely turned on, auto-build
is on, auto-refresh is on.


______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: 
https://sourceforge.net/forum/unmonitor.php?forum_id=293649

[Pydev-users] [pydev - Users] RE: code checking not working for new modules

[SourceForge.net <no...@so...>]

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=3780198
By: fabioz

Have you checked for any message in your error log? Also, are your files under
the pythonpath in the project (does it have a source folder configured:
http://fabioz.com/pydev/manual_101_project_conf2.html)

Chers,

Fabio

______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: 
https://sourceforge.net/forum/unmonitor.php?forum_id=293649

[Pydev-users] [pydev - Users] RE: code checking not working for new modules

[SourceForge.net <no...@so...>]

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=3781721
By: xyld

You are right, of course, Fabio.

I _hadn't_ configured my pythonpath correctly, though I thought I had.

Just a suggestion -- perhaps some kind of warning could be generated somewhere
when it _isn't_ using code analysis on a python file, with possible fixes? It's
just that it is a case where it's not immediately obvious that it _isn't_ going,
because you might assume there is nothing wrong with the code :) In fact when
it did switch on, the only problems I had were import errors.

One more question, somewhat related: some of the .so files aren't being picked
up from my python path, in this case the lxml etree.so (installed
in site-packages/lxml-1.0.1-py2.4-linux-i686.egg/lxml/etree.so). Is there any
way to force that?

Many thanks,

Richard.

______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: 
https://sourceforge.net/forum/unmonitor.php?forum_id=293649

[Pydev-users] [pydev - Users] RE: code checking not working for new modules

[SourceForge.net <no...@so...>]

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=3784598
By: fabioz

Hi Richard,

1. Good you were able to fix it ;-)

2. The fixes without code-analysis are something that are very unlikely to happen,
mostly because the fixes are built upon the code-analysis.

3. It should be able to pick it if that folder is in the pythonpath. There is
a bug in release 1.1.0 where the pythonpath was not updated if you changed it
without pressing apply without any interpreter configured to clear the cache
(already fixed for the next release).

Cheers,

Fabio

______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: 
https://sourceforge.net/forum/unmonitor.php?forum_id=293649

[Pydev-users] [pydev - Users] RE: code checking not working for new modules

[SourceForge.net <no...@so...>]

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=3784718
By: xyld

Hi Fabio:

Regarding fixes: the fixes were something I wasn't really counting on. I guess
a "really nice to have" though would be something that tells you that code-analysis
isn't switched on for a particular python file. It's not immediately obvious
why things like "unused variable" don't work on a random python file :)

Regarding folders in python path: I should explain that the module in question
(lxml) has been installed from a python 'egg', as seems to be becoming more
popular. The egg directories are in the python path, but they _don't_ have an
__init__.py in them, because they're not the actual module directories, but
rather just _contain_ the module directories. The 'egg' installer (easy-install)
puts an easy-install.pth in the site-packages directory, which then adjusts
the python path. The only interim solution I can think of is to setup, individually,
all the 'eggs' I've installed.


Many thanks,

Richard.

______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: 
https://sourceforge.net/forum/unmonitor.php?forum_id=293649

[Pydev-users] [pydev - Users] RE: code checking not working for new modules

[SourceForge.net <no...@so...>]

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=3784818
By: fabioz

Hi Richard...

1. Ok, now I got it ;-)

2. Yeap, I think you have to do it manually... But actually, if it is under
the site-packages and your pythonpath is set, when you add the interpreter,
it should automatically get it (even if it is in a pth file and not in the env)...
That's why I asked about the cache... because if you install it after your
interpreter is already configured, you have to remove it, press apply, and then
add it again.

Cheers,

Fabio

______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: 
https://sourceforge.net/forum/unmonitor.php?forum_id=293649