tag:blogger.com,1999:blog-8550962.post3362967179188323514..comments2016-12-06T03:20:31.133-08:00Comments on PyDev adventures: Pydev release 1.2.6Fabio Zadroznyhttp://www.blogger.com/profile/04202246218394712738noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-8550962.post-26686138488626565682007-02-02T02:52:00.000-08:002007-02-02T02:52:00.000-08:00The opengl stuff works for me...
Is the module Op...The opengl stuff works for me...<br /><br />Is the module OpenGl set for you in the forced builtins?<br /><br />Can you give some example code that has the problems (also, check your error log)...<br /><br />Another thing... I think we should continue this in the sourceforge forum: https://sourceforge.net/forum/forum.php?forum_id=293649 as it could help more people there...Fabio Zadroznyhttp://www.blogger.com/profile/04202246218394712738noreply@blogger.comtag:blogger.com,1999:blog-8550962.post-66875803078184583052007-01-30T12:26:00.000-08:002007-01-30T12:26:00.000-08:00Hello,
I'm trying to use pydev on a project refer...Hello,<br /><br />I'm trying to use pydev on a project referring numpy, pyopengl and a lot of other libraries. My project runs fine and everything, however pydev reports errors that some of the types cannot be resolved. For instance pydev cannot resolve float32. Can this be because whichever library defines float32 (my guess is PyOpenGL) gets it from a dll file? Is there a way to make pydev find this information so I can get rid of the warnings?<br /><br />Thanks for pydev and help in advance!Andréhttp://www.blogger.com/profile/03837009153847170227noreply@blogger.comtag:blogger.com,1999:blog-8550962.post-35754821749397737212007-01-28T04:24:00.000-08:002007-01-28T04:24:00.000-08:00Yes, you're right about pylint, that's a bug... I'...Yes, you're right about pylint, that's a bug... I've just fixed it in the cvs (hope to release it this week).<br /><br />Cheers,<br /><br />FabioFabio Zadroznyhttp://www.blogger.com/profile/04202246218394712738noreply@blogger.comtag:blogger.com,1999:blog-8550962.post-49658071492328472212007-01-27T11:35:00.000-08:002007-01-27T11:35:00.000-08:00Since updating to 1.2.6 (pydev only, no pydev exte...Since updating to 1.2.6 (pydev only, no pydev extensions), the PYTHONPATH seems to not be set according to the project settings before pylint runs.<br /><br />The source folders are set up in my project to include all of the modules that end up in the python path at runtime. This used to work fine, and pylint could find all of the modules in these additional folders.<br /><br />Now, since updating to 1.2.6 (on two different machines), pylint reports errors that it can't find modules that are in directories specified in the source folders and external source folders for the project.<br /><br />Am I right that pydev should set the PYTHONPATH according to the project settings before running pylint? Or am I just confused.<br /><br />ScottAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-8550962.post-57088241759923824902007-01-27T09:54:00.000-08:002007-01-27T09:54:00.000-08:00This plug-in is fantastic. It would be nice howeve...This plug-in is fantastic. It would be nice however if there were a version for IntelliJ too, since it has much more and powerful refactorings and smarter code support than Eclipse. Even more, for open souce development IntelliJ is free.<br /><br />Also, many users wouldn't mind at all if the plug-in would be commercial (e.g. as your pydev extension).<br />At the moment there's a only a very primitive Python support in the form of a plug-in in IntelliJ:<a href="https://pythonid.dev.java.net/">PythonID</a><br />so a plug-in like pydev should be a real success.<br /><br />Thank you,<br /><br />D.demetrioshttp://www.blogger.com/profile/06305976623803819238noreply@blogger.com