On 1/24/07, Fabio Zadrozny <[EMAIL PROTECTED]> wrote:
On 1/24/07, Patrick Gerken <[EMAIL PROTECTED]> wrote:
>
> Hi Fabio,
>
> thanks for your fast responses...
>
> everything moved to bug tracker entries:
>
https://sourceforge.net/tracker/index.php?func=detail&aid=1643635&group_id=85796&atid=577329
>
>
https://sourceforge.net/tracker/index.php?func=detail&aid=1643554&group_id=85796&atid=577329
>
>
>
Actually, it appears that you are working with pydev 1.2.6 and with
version 1.2.5 of pydev extensions (and they are conflicting... you must
have the same version of both), so, I guess you could try removing 1.2.5and
only letting
1.2.6 and it should work.
Yes, when I did an update of eclipse I did it with the automatic update
manager, and he only found an update for pydev, and not the extensions. I
was not thinking too much about it, and said ok, lets try.
Now I also got an updated pydev extensions, and it works like a charm.
Maybe Pydev Extensions could check that it matches the pydev version
number?
The docstring issue is still true.
Best regards,
Patrick
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
pydev-code mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pydev-code
