Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.mixmin.net!hq-usenetpeers.eweka.nl!hq-usenetpeers.eweka.nl!xlned.com!feeder1.xlned.com!newsfeed.xs4all.nl!newsfeed1.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
In-Reply-To: <67700207-2d66-440b-ba9c-f33757cc9783@googlegroups.com>
References: <67700207-2d66-440b-ba9c-f33757cc9783@googlegroups.com>
From: Fabio Zadrozny <fabiofz@gmail.com>
Date: Tue, 2 Sep 2014 21:29:32 -0300
Subject: Re: PyDev Code Analysis
To: Wanderer <wanderer@dialup4less.com>
Content-Type: multipart/alternative; boundary=001a1133f7809f181a05021e556f
Cc: python list <python-list@python.org>
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.13721.1409704200.18130.python-list@python.org>
Lines: 114
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:77457

--001a1133f7809f181a05021e556f
Content-Type: text/plain; charset=UTF-8

On Tue, Sep 2, 2014 at 2:27 PM, Wanderer <wanderer@dialup4less.com> wrote:

>
> I'm trying to set up Eclipse with PyDev and I can't get the code analysis
> to work the way I want.
>
> Whenever I type 'def' it generates an error before I finish the line. I
> don't want to see errors until I finish typing. It's not an error I'm just
> not done yet. So I try to turn this off by going to
> Window>Preferences>PyDev>Editor>CodeAnalysis and setting the option When do
> we analyze? to Only on save. This doesn't stop these errors from showing up
> while I'm typing. What it does is stop checking for warnings like 'unused
> variable' even on save. If I set the option to 'On any successful parse'
> then it will check for these warning only on save.
>
> To summarize
> Setting 'Only on save', turns off warnings but keeps giving real time
> errors.
>
> Setting 'On any successful parse', checks for warnings only on save and
> keeps giving real time errors.
>
> I'm using
> Eclipse IDE for C/C++ Developers 4.4.0.21040612
> Pydev for Eclipse 3.7.0.201408261926
>
>
> What I am I doing wrong?
>
> Thanks
>

Well, there are 2 different things there:

Code analysis and syntax analysis.

Syntax analysis is always done on the fly (and you can't really turn it off
-- the places which require an AST will usually use the AST which is
computed there and when it's computed and there's a syntax error, that
error will be shown). It should usually be computed when a new line is
entered, on a save or after you entered some text and the timeout specified
at preferences > pydev > builders is elapsed.

As for the code analysis (which will check errors and warnings such as
unused imports / unresolved imports / undefined variables, etc.), it has
the options you saw (which are affected by the only on save/on any
successful parse).

Cheers,

Fabio

--001a1133f7809f181a05021e556f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Tue, Sep 2, 2014 at 2:27 PM, Wanderer <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:wanderer@dialup4less.com" target=3D"_blank">wanderer@dialup4less.com<=
/a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><br>
I&#39;m trying to set up Eclipse with PyDev and I can&#39;t get the code an=
alysis to work the way I want.<br>
<br>
Whenever I type &#39;def&#39; it generates an error before I finish the lin=
e. I don&#39;t want to see errors until I finish typing. It&#39;s not an er=
ror I&#39;m just not done yet. So I try to turn this off by going to Window=
&gt;Preferences&gt;PyDev&gt;Editor&gt;CodeAnalysis and setting the option W=
hen do we analyze? to Only on save. This doesn&#39;t stop these errors from=
 showing up while I&#39;m typing. What it does is stop checking for warning=
s like &#39;unused variable&#39; even on save. If I set the option to &#39;=
On any successful parse&#39; then it will check for these warning only on s=
ave.<br>


<br>
To summarize<br>
Setting &#39;Only on save&#39;, turns off warnings but keeps giving real ti=
me errors.<br>
<br>
Setting &#39;On any successful parse&#39;, checks for warnings only on save=
 and keeps giving real time errors.<br>
<br>
I&#39;m using<br>
Eclipse IDE for C/C++ Developers 4.4.0.21040612<br>
Pydev for Eclipse 3.7.0.201408261926<br>
<br>
<br>
What I am I doing wrong?<br>
<br>
Thanks<br></blockquote><div><br></div>Well, there are 2 different things th=
ere:<div><br></div><div>Code analysis and syntax analysis.</div><div><br></=
div><div>Syntax analysis is always done on the fly (and you can&#39;t reall=
y turn it off -- the places which require an AST will usually use the AST w=
hich is computed there and when it&#39;s computed and there&#39;s a syntax =
error, that error will be shown). It should usually be computed when a new =
line is entered, on a save or after you entered some text and the timeout s=
pecified at preferences &gt; pydev &gt; builders is elapsed.</div>

<div><br></div><div>As for the code analysis (which will check errors and w=
arnings such as unused imports / unresolved imports / undefined variables, =
etc.), it has the options you saw (which are affected by the only on save/o=
n any successful parse).</div>

<div><br></div><div>Cheers,</div><div><br></div><div>Fabio=C2=A0</div></div=
></div></div>

--001a1133f7809f181a05021e556f--