>
>
> For sure Fabio!
> Perhaps the following could make a nice addition to this page: what would
> be an
> effective manner of verifying that the dynamic code completion is working?
Basically, requesting code-completion in an empty file would be the best way
to check if the shell that gets builtins is working (so, if builtin classes
appear... e.g.: RuntimeError, AttributeError, etc, the shell should be doing
its job).
If it's distributed as a zip file, you have to get all the root packages
(that would normally be resolved in the pythonpath) within that zip and add
them in the forced builtins... That's because currently pydev does not
handle zip files (another option would be unzipping the .zip file and adding
the directory where it was unzipped to the pythonpath -- or to some folder
that's already in the pythonpath -- e.g.: /lib/site-packages)
A last question would be of there is a way to avoid having all modules
> re-scanned when changing interpreter?
Not currently... you can add that as a feature request... I think it could
be smarter and make some cache based on md5 hashes for modules already
parsed (and don't throw that information away while you're still in the
dialog to configure the interpreter).
Cheers,
Fabio
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Pydev-users mailing list
Pydev-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pydev-users
