pydev-code Mailing List for PyDev for Eclipse (Page 30)
Brought to you by:
fabioz
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
(14) |
Apr
(18) |
May
(12) |
Jun
(34) |
Jul
(31) |
Aug
(37) |
Sep
(22) |
Oct
(2) |
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(1) |
Feb
(4) |
Mar
(9) |
Apr
(1) |
May
|
Jun
(2) |
Jul
(24) |
Aug
(3) |
Sep
(5) |
Oct
(3) |
Nov
(3) |
Dec
(5) |
| 2006 |
Jan
(5) |
Feb
(23) |
Mar
(5) |
Apr
(80) |
May
(26) |
Jun
(13) |
Jul
(13) |
Aug
(4) |
Sep
(31) |
Oct
(24) |
Nov
(6) |
Dec
(2) |
| 2007 |
Jan
(7) |
Feb
|
Mar
(26) |
Apr
(3) |
May
(8) |
Jun
(6) |
Jul
(11) |
Aug
(2) |
Sep
(4) |
Oct
|
Nov
(9) |
Dec
(3) |
| 2008 |
Jan
(7) |
Feb
(1) |
Mar
(6) |
Apr
(7) |
May
(9) |
Jun
(14) |
Jul
(9) |
Aug
(6) |
Sep
(10) |
Oct
(5) |
Nov
(8) |
Dec
(5) |
| 2009 |
Jan
(8) |
Feb
(10) |
Mar
(10) |
Apr
(1) |
May
(3) |
Jun
(5) |
Jul
(10) |
Aug
(3) |
Sep
(12) |
Oct
(6) |
Nov
(22) |
Dec
(12) |
| 2010 |
Jan
(10) |
Feb
(17) |
Mar
(5) |
Apr
(9) |
May
(8) |
Jun
(2) |
Jul
(4) |
Aug
(12) |
Sep
(1) |
Oct
(1) |
Nov
(8) |
Dec
|
| 2011 |
Jan
(14) |
Feb
(8) |
Mar
(3) |
Apr
(11) |
May
(6) |
Jun
(5) |
Jul
(10) |
Aug
(7) |
Sep
|
Oct
(4) |
Nov
(4) |
Dec
(8) |
| 2012 |
Jan
|
Feb
(8) |
Mar
(10) |
Apr
(5) |
May
(4) |
Jun
(10) |
Jul
|
Aug
(2) |
Sep
(2) |
Oct
(11) |
Nov
(1) |
Dec
|
| 2013 |
Jan
(1) |
Feb
(2) |
Mar
(11) |
Apr
(10) |
May
(7) |
Jun
(9) |
Jul
(13) |
Aug
(20) |
Sep
(4) |
Oct
(18) |
Nov
(5) |
Dec
(7) |
| 2014 |
Jan
(3) |
Feb
(5) |
Mar
(7) |
Apr
(5) |
May
(10) |
Jun
(2) |
Jul
|
Aug
(1) |
Sep
(7) |
Oct
(1) |
Nov
(1) |
Dec
(1) |
| 2015 |
Jan
(1) |
Feb
(1) |
Mar
(8) |
Apr
(3) |
May
(1) |
Jun
(2) |
Jul
(1) |
Aug
(2) |
Sep
(1) |
Oct
(3) |
Nov
(5) |
Dec
(1) |
| 2016 |
Jan
(26) |
Feb
(10) |
Mar
(4) |
Apr
|
May
(4) |
Jun
(3) |
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
(4) |
Dec
(3) |
| 2017 |
Jan
(3) |
Feb
|
Mar
(9) |
Apr
(2) |
May
|
Jun
(1) |
Jul
|
Aug
(9) |
Sep
(1) |
Oct
|
Nov
(2) |
Dec
|
| 2018 |
Jan
|
Feb
(2) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(4) |
Oct
(2) |
Nov
(1) |
Dec
(3) |
| 2019 |
Jan
(4) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(4) |
Aug
|
Sep
|
Oct
(3) |
Nov
|
Dec
|
| 2020 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(4) |
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
(11) |
| 2021 |
Jan
(3) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
|
From: Fabio Z. <fa...@gm...> - 2007-07-18 15:38:43
|
Hi All, Pydev and Pydev Extensions 1.3.8 have been released Details on Pydev Extensions: http://www.fabioz.com/pydev Details on Pydev: http://pydev.sf.net Details on its development: http://pydev.blogspot.com Release Highlights in Pydev Extensions: ----------------------------------------------------------------- * Code-analysis: Detects mixing of spaces and tabs. * Code-analysis: Reimport not flagged when inside of try..except ImportError. Release Highlights in Pydev: ---------------------------------------------- * Fixed problems related to the pydev package explorer that appeared when using java 1.6 (ConcurrentModificationException) * Other minor bug-fixes What is PyDev? --------------------------- PyDev is a plugin that enables users to use Eclipse for Python and Jython development -- making Eclipse a first class Python IDE -- It comes with many goodies such as code completion, syntax highlighting, syntax analysis, refactor, debug and many others. Cheers, -- Fabio Zadrozny ------------------------------------------------------ Software Developer ESSS - Engineering Simulation and Scientific Software http://www.esss.com.br Pydev Extensions http://www.fabioz.com/pydev Pydev - Python Development Enviroment for Eclipse http://pydev.sf.net http://pydev.blogspot.com |
|
From: Anders D. <an...@da...> - 2007-07-15 13:11:35
|
On 7/15/07, Fabio Zadrozny <fa...@gm...> wrote: > > > Have you seen my answer in the forum: > https://sourceforge.net/forum/message.php?msg_id=4413030 ?(you could > simply configure an external python script to react to changes as a builder) > Ooops, missed that. Thanks -- Anders Dahnielson <an...@da...> |
|
From: Fabio Z. <fa...@gm...> - 2007-07-15 13:06:19
|
On 7/15/07, Anders Dahnielson <an...@da...> wrote: > > > > On 7/15/07, Anders Dahnielson <an...@da...> wrote: > > > > > > On 7/15/07, Anders Dahnielson < an...@da...> wrote: > > > > > Reacting to save events and getting all the necessary paths was fairly > > > easy (for a Jython and Eclipse n00b) but I hit trouble when I tried to save > > > myself some coding and instead leverage an existing test runner "nose" [1]. > > > It simply do not run under Jython (dang!). So my brilliant plan B (I > > > thought) was to run it under CPython using the os.command module. > > > Turns out that Jython doesn't have a popen() (dang again!). > > > > > > I just realized that running tests under Jython isn't what I want. So, > > plan B is the new plan A. > > > > Of course! I'll just use the standard Java call java.lang.Runtime instead > (he said after googling). I have to keep reminding myself that Jython isn't > Python... > Have you seen my answer in the forum: https://sourceforge.net/forum/message.php?msg_id=4413030 ?(you could simply configure an external python script to react to changes as a builder) Cheers, Fabio |
|
From: Anders D. <an...@da...> - 2007-07-15 08:35:28
|
On 7/15/07, Anders Dahnielson <an...@da...> wrote: > > > On 7/15/07, Anders Dahnielson <an...@da...> wrote: > > > Reacting to save events and getting all the necessary paths was fairly > > easy (for a Jython and Eclipse n00b) but I hit trouble when I tried to save > > myself some coding and instead leverage an existing test runner "nose" [1]. > > It simply do not run under Jython (dang!). So my brilliant plan B (I > > thought) was to run it under CPython using the os.command module. Turns > > out that Jython doesn't have a popen() (dang again!). > > > I just realized that running tests under Jython isn't what I want. So, > plan B is the new plan A. > Of course! I'll just use the standard Java call java.lang.Runtime instead (he said after googling). I have to keep reminding myself that Jython isn't Python... -- Anders Dahnielson <an...@da...> |
|
From: Anders D. <an...@da...> - 2007-07-15 07:30:10
|
On 7/15/07, Anders Dahnielson <an...@da...> wrote: > Reacting to save events and getting all the necessary paths was fairly > easy (for a Jython and Eclipse n00b) but I hit trouble when I tried to save > myself some coding and instead leverage an existing test runner "nose" [1]. > It simply do not run under Jython (dang!). So my brilliant plan B (I thought) was to run it under CPython using the > os.command module. Turns out that Jython doesn't have a popen() (dang > again!). I just realized that running tests under Jython isn't what I want. So, plan B is the new plan A. So my question is: > > * Is it possible to run "nose" using the CPython interpreter from within a > Jython for PyDev script? > > [1] http://somethingaboutorange.com/mrl/projects/nose/ > > -- Anders Dahnielson <an...@da...> |
|
From: Anders D. <an...@da...> - 2007-07-14 23:18:30
|
Hi all! I've just started to dabble with the Jython-scripting of PyDev, trying to get a hang of it. What I'm trying to accomplice is unit testing whenever a python module is saved. Reacting to save events and getting all the necessary paths was fairly easy (for a Jython and Eclipse n00b) but I hit trouble when I tried to save myself some coding and instead leverage an existing test runner "nose" [1]. It simply do not run under Jython (dang!). So my brilliant plan B (I thought) was to run it under CPython using the os.command module. Turns out that Jython doesn't have a popen() (dang again!). So my question is: * Is it possible to run "nose" using the CPython interpreter from within a Jython for PyDev script? [1] http://somethingaboutorange.com/mrl/projects/nose/ -- Anders Dahnielson <an...@da...> |
|
From: Fabio Z. <fa...@gm...> - 2007-07-09 19:21:42
|
Hi All, Pydev and Pydev Extensions 1.3.7 have been released Details on Pydev Extensions: http://www.fabioz.com/pydev Details on Pydev: http://pydev.sf.net Details on its development: http://pydev.blogspot.com Release Highlights: ---------------------------------------------- * Support for Eclipse 3.3 * Bug Fix: Interpreter modules not correctly set/persisted after specifying interpreter (so, the builtins and other system libraries would not be available in completions). * Mylyn integration. * Open With Pydev: does not appear for containers anymore. * Code-completion: The folowing cases are now considered in code-completion to discover the type of a variable: o Type/Interface checking: (note that 'assert' is required) assert isinstance(obj, Interface) -- default from python o assert Interface.implementedBy(obj) -- zope o assert IsImplementation(obj, Interface) -- custom request o assert IsInterfaceDeclared(obj, Interface) -- custom request o Factory methods a = adapt(obj, Interface) -- pyprotocols o a = obj.GetAdapter(Interface) -- custom request o a = obj.get_adapter(Interface) -- custom request o a = GetSingleton(Interface) -- custom request o a = GetImplementation(Interface) -- custom request What is PyDev? --------------------------- PyDev is a plugin that enables users to use Eclipse for Python and Jython development -- making Eclipse a first class Python IDE -- It comes with many goodies such as code completion, syntax highlighting, syntax analysis, refactor, debug and many others. Cheers, -- Fabio Zadrozny ------------------------------------------------------ Software Developer ESSS - Engineering Simulation and Scientific Software http://www.esss.com.br Pydev Extensions http://www.fabioz.com/pydev Pydev - Python Development Enviroment for Eclipse http://pydev.sf.net http://pydev.blogspot.com |
|
From: Fabio Z. <fa...@gm...> - 2007-07-06 10:58:22
|
Hi Chris,
I've created a new implementation for listFilesForCompletion (had to
> change a little bit of changePythonPath, too), and it seems to work here
> locally, all modules are found regardless whether linked or not.
>
> Now I'm testing a little bit, and found out the following does NOT work:
>
> from xml.dom import minidom
> doc = minidom.parse("test.xml")
> e = doc. <-- no completion on "doc"
>
> On the other hand, if I write
>
> doc2 = minidom.Document()
>
> code completion on doc2 works as expected.
>
> Could this be related to my patch, or is it a general problem?
It's a 'general problem'. Basically, pydev will try to analyze the parse
function for its return value and is unable to discover the likely value in
the return, whereas in the other option, it can readily find the assignment
to Document.
Cheers,
Fabio
|
|
From: chris v. <chr...@gm...> - 2007-07-06 10:44:07
|
Hi Fabio,
> I'll try over the weekend.
>
I've created a new implementation for listFilesForCompletion (had to
change a little bit of changePythonPath, too), and it seems to work here
locally, all modules are found regardless whether linked or not.
Now I'm testing a little bit, and found out the following does NOT work:
from xml.dom import minidom
doc = minidom.parse("test.xml")
e = doc. <-- no completion on "doc"
On the other hand, if I write
doc2 = minidom.Document()
code completion on doc2 works as expected.
Could this be related to my patch, or is it a general problem?
regards,
chris
|
|
From: Fabio Z. <fa...@gm...> - 2007-06-29 18:40:08
|
Hi All, Pydev and Pydev Extensions 1.3.6 have been released Details on Pydev Extensions: http://www.fabioz.com/pydev Details on Pydev: http://pydev.sf.net Details on its development: http://pydev.blogspot.com Release Highlights in Pydev Extensions: ----------------------------------------------------------------- * Bug-Fixes Release Highlights in Pydev: ---------------------------------------------- * Bug Fix: Builtins were not correctly used after specifying interpreter (so, the builtins would not be available in completions/code-analysis). * Patch (from Carl Robinson): PyLint severities can now be specified. What is PyDev? --------------------------- PyDev is a plugin that enables users to use Eclipse for Python and Jython development -- making Eclipse a first class Python IDE -- It comes with many goodies such as code completion, syntax highlighting, syntax analysis, refactor, debug and many others. Cheers, -- Fabio Zadrozny ------------------------------------------------------ Software Developer ESSS - Engineering Simulation and Scientific Software http://www.esss.com.br Pydev Extensions http://www.fabioz.com/pydev Pydev - Python Development Enviroment for Eclipse http://pydev.sf.net http://pydev.blogspot.com |
|
From: chris v. <chr...@gm...> - 2007-06-28 13:54:41
|
Hi Fabio, Fabio Zadrozny schrieb: > The solutions available (I think) would be: > - Creating a new resolveModule that would work on existing files > - Resolving the module when we're looking for the files in the > pythonpath (currently in listFilesForCompletion, it uses > pythonPathHelper.getModulesBelow to get a list of files and then > resolves it, but maybe this could be changed to resolve the File and > the actual module name at the same time). > > I think that the second approach would probably be better... would you > be willing to take a look at it? I'll try over the weekend. regards, chris |
|
From: Fabio Z. <fa...@gm...> - 2007-06-25 11:10:34
|
On 6/25/07, chris vigelius <chr...@gm...> wrote: > > Hello, Hi Chris, I'm currently trying to make a patch which adresses the long-standing > symlink problem on Unix platforms, as I am using Ubuntu Feisty and they > have almost every library symlinked... > > ... > > REF.getFileAbsolutePath() canonicalizes the path passed to it, so > resolveModule is called with "/usr/share/python-support/...". But > resolveModule() internally matches the passed file against pythonpath, > and since this is different from the real path (because of the resolved > symlink), it is dropped. > > My question is now, why this matching is done in the first place? To > determine the package name, one could just walk up the directories and > look for __init.py__, that would be not only faster but also remove the > symlink problem. Are there any special reasons why the canonical path of > a module must be compared against pythonpath? The current implementation is the way it is because it can resolve module names even if the file does not exist. E.g.: When a file is removed, the code-completion builder will have to remove the AST cache for that file -- but when that happens, the file does not actually exist anymore... you can see that the signature it has is: public String resolveModule(String fullPath, final boolean requireFileToExist) So, if the file does not exist, it might be difficult to resolve it... Still, I thought it didn't actually resolve symlinks, but you're right about getCanonicalPath, so, I think this can be worked on -- initially making it resolve the modules in the changePythonPath, when we know that the files exist -- fixing it in the builder (for projects) may be a different story (at: ProjectModulesManagerBuild.rebuildModule)... anyway, 1st things 1st... The solutions available (I think) would be: - Creating a new resolveModule that would work on existing files - Resolving the module when we're looking for the files in the pythonpath (currently in listFilesForCompletion, it uses pythonPathHelper.getModulesBelow to get a list of files and then resolves it, but maybe this could be changed to resolve the File and the actual module name at the same time). I think that the second approach would probably be better... would you be willing to take a look at it? Cheers, Fabio |
|
From: chris v. <chr...@gm...> - 2007-06-25 10:09:32
|
Hello,
I'm currently trying to make a patch which adresses the long-standing
symlink problem on Unix platforms, as I am using Ubuntu Feisty and they
have almost every library symlinked...
I have debugged this a little (using Eclipse 3.2 and the 1.3.5 zipped
src) and I've found out that this is neither a Java problem nor an
Eclipse problem; both of them can in fact handle symlinks just as one
would expect them to (I just mention this because I've seen statements
on this list claiming otherwise). It is actually Pydev's usage of
canonical vs. absolute paths which is causing the problem. pygtk.py is a
good example to show what is happening:
The file pygtk.py is physically located at
/usr/share/python-support/python-gobject/, while the pythonpath points
to /var/lib/python-support/python2.5/. But since
/var/lib/python-support/python2.5/pygtk.py is a symlink to the physical
location, python will accept an "import pygtk" without complaining.
Testing with the aforementioned file, the following behaviour can be seen:
File f = new File("/var/lib/python-support/python2.5/pygtk.py");
f.isFile() returns true
f.getCanonicalPath() returns
"/usr/share/python-support/python-gobject/pygtk.py"
This is in line with the Java Documentation which states that
getCanonicalPath() resolves symlinks. ModulesManager.changePythonPath()
contains the following code (f is pointing to the symlinked location
"/var/lib/.." retrieved by scanning the pythonpath):
String fileAbsolutePath = REF.getFileAbsolutePath(f);
String m = pythonPathHelper.resolveModule(fileAbsolutePath);
REF.getFileAbsolutePath() canonicalizes the path passed to it, so
resolveModule is called with "/usr/share/python-support/...". But
resolveModule() internally matches the passed file against pythonpath,
and since this is different from the real path (because of the resolved
symlink), it is dropped.
My question is now, why this matching is done in the first place? To
determine the package name, one could just walk up the directories and
look for __init.py__, that would be not only faster but also remove the
symlink problem. Are there any special reasons why the canonical path of
a module must be compared against pythonpath?
regards,
chris
|
|
From: Ben A. <ben...@st...> - 2007-06-25 09:31:17
|
Hello there I would greatly appreciate a small amount of your time to assist with my doctoral research at The University of Newcastle. The research concerns open source licensing and we're seeking developers working on Java projects. The research is supervised, ethics-approved, anonymous and results will be freely available. Participation will also provide a custom licensing report for your project. To learn more, please visit: http://licensing-research.newcastle.edu.au Thanks for reading this email, and I hope you'll consider participating. Best regards Ben Alex (My apologies for being off-topic; this list will not be emailed again) |
|
From: Fabio Z. <fa...@gm...> - 2007-06-20 17:07:46
|
Hi All, Pydev and Pydev Extensions 1.3.5 have been released Details on Pydev Extensions: http://www.fabioz.com/pydev Details on Pydev: http://pydev.sf.net Details on its development: http://pydev.blogspot.com Release Highlights in Pydev Extensions: ----------------------------------------------------------------- * Auto-Import: o Import is now set in correct line even with multi-line imports. o Added option to disable the introduction of auto-imports. o Added option to remove modules that start with '_' from the imports (so, tokens would have to be found in __init__.py files). * Code Analysis: Having a list comprehension with a subscript was not being treated correctly. * Debugger: Working with jython. * Debugger: Working with wxPython. Release Highlights in Pydev: ---------------------------------------------- * Eclipse 3.3 Integration: Does not keep eclipse from a correct shutdown anymore. * Docstrings and code completion pop-up: o The docstrings are now wrapped to the size of the pop-up window. o The initial columns with whitespaces that are common for all the docstring is now removed. o The previous size of the pop-up window in completions is now restored. * Extract method refactoring: was not adding 'if' statement correctly on a specific case. * Organize imports: (Ctrl+Shift+O): comments are not erased in import lines when using it anymore. * Interpreter Config: solved a concurrency issue (which could issue an exception when configuring the interpreter). * Jython integration: can now work with a j9 vm. * Jython integration: those that don't use jython can now use eclipse without JDT (but it's still required for jython development). * Outline: o The comments are now set in the correct level (below module, class or method). o Comments are sorted by their position even when alphabetic sorting is in place. o Comments are added to the outline if they start or end with '---'. What is PyDev? --------------------------- PyDev is a plugin that enables users to use Eclipse for Python and Jython development -- making Eclipse a first class Python IDE -- It comes with many goodies such as code completion, syntax highlighting, syntax analysis, refactor, debug and many others. Cheers, -- Fabio Zadrozny ------------------------------------------------------ Software Developer ESSS - Engineering Simulation and Scientific Software http://www.esss.com.br Pydev Extensions http://www.fabioz.com/pydev Pydev - Python Development Enviroment for Eclipse http://pydev.sf.net http://pydev.blogspot.com |
|
From: Fabio Z. <fa...@gm...> - 2007-05-30 12:56:40
|
Hi All, Pydev and Pydev Extensions 1.3.4 have been released Details on Pydev Extensions: http://www.fabioz.com/pydev Details on Pydev: http://pydev.sf.net Details on its development: http://pydev.blogspot.com Release Highlights in Pydev Extensions: ----------------------------------------------------------------- * Mark Occurrences: 'global' used in the global scope is correctly treated. * Code Analysis: __builtins__ considered in global namespace Release Highlights in Pydev: ---------------------------------------------- * Debugger: Breakpoints working correctly on external files opened with 'File > Open File...'. * Debugger: Python 2.5 accepts breakpoints in the module level. * Debugger: Unicode variables can be shown in the variables view. * Editor: Coding try..except / try..finally auto-dedents. * Code Completion: __builtins__ considered a valid completion * Pydev Package Explorer: Opens files with correct editor (the pydev editor was forced). What is PyDev? --------------------------- PyDev is a plugin that enables users to use Eclipse for Python and Jython development -- making Eclipse a first class Python IDE -- It comes with many goodies such as code completion, syntax highlighting, syntax analysis, refactor, debug and many others. Cheers, -- Fabio Zadrozny ------------------------------------------------------ Software Developer ESSS - Engineering Simulation and Scientific Software http://www.esss.com.br Pydev Extensions http://www.fabioz.com/pydev Pydev - Python Development Enviroment for Eclipse http://pydev.sf.net http://pydev.blogspot.com |
|
From: Fabio Z. <fa...@gm...> - 2007-05-15 12:14:36
|
Hi All, Pydev and Pydev Extensions 1.3.3 have been released Details on Pydev Extensions: http://www.fabioz.com/pydev Details on Pydev: http://pydev.sf.net Details on its development: http://pydev.blogspot.com Release Highlights in Pydev Extensions: ----------------------------------------------------------------- * Quick-fix: When an import is added from the auto-import quick-fix, a code-analysis is requested right after it. * Minor bugs fixed. Release Highlights in Pydev: ---------------------------------------------- * Performance: Optimizations in the code-completion structure. * Debugger: Performance improvements (it will only actually trace contexts that have breakpoints -- it was doing that in a module context before). * Debugger: Step over correctly stops at the previous context. * Debugger: Breakpoint labels correct when class/function name changes. * Quick-Fix: Move import to global scope would not be correct if the last line was a multi-line import. * Outline: Syntax errors will show in the outline. * Outline: Selection on import nodes is now correct. * Outline: Link with editor created. * Outline: Show in outline added to the pydev perspective. * Find Previous Problem: action created (Ctrl+Shift+.). * Extract method refactoring: end line delimiters are gotten according to the document (it was previously fixed to \n). * Extension-points: Documentation added for some of the extension points available. * Perspective: The pydev package explorer has been set as the preferred browser in the pydev perspective. What is PyDev? --------------------------- PyDev is a plugin that enables users to use Eclipse for Python and Jython development -- making Eclipse a first class Python IDE -- It comes with many goodies such as code completion, syntax highlighting, syntax analysis, refactor, debug and many others. Cheers, -- Fabio Zadrozny ------------------------------------------------------ Software Developer ESSS - Engineering Simulation and Scientific Software http://www.esss.com.br Pydev Extensions http://www.fabioz.com/pydev Pydev - Python Development Enviroment for Eclipse http://pydev.sf.net http://pydev.blogspot.com |
|
From: Neil <nei...@ut...> - 2007-05-08 03:10:23
|
Thanks, that's exactly the pointer I needed! neil On 5/5/07, Fabio Zadrozny <fa...@gm...> wrote: > > > On 5/4/07, Neil <nei...@ut...> wrote: > > That makes sense... > > > > what I'm stuck on is trying to get my own plugin activated. I'm > > currently extending org.python.pydev.pydev_builder, but I'm not sure > > what this provides me... do I need to implement a particular > > interface, which is then added to the listener pool by Eclipse by > > default? > > > > It would be great if someone had some sample code on how to use these > > extension points... I'd rather not hack into the PyDev source > > directly. > > > Actually, I think the extension point > org.python.pydev.parser.pydev_parser_observer is more what > you want: > > <extension > point="org.python.pydev.parser.pydev_parser_observer "> > <parser_observer class="my.parser.Observer"/> > </extension> > > and the Observer class must implement > org.python.pydev.core.parser.IParserObserver (it already > gives you the generated ast -- the outline is also based on this extension). > > Cheers, > > Fabio > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > pydev-code mailing list > pyd...@li... > https://lists.sourceforge.net/lists/listinfo/pydev-code > > -- Neil A. Ernst Ph.D. Candidate University of Toronto http://neilernst.net |
|
From: Fabio Z. <fa...@gm...> - 2007-05-06 00:00:33
|
On 5/4/07, Neil <nei...@ut...> wrote:
>
> That makes sense...
>
> what I'm stuck on is trying to get my own plugin activated. I'm
> currently extending org.python.pydev.pydev_builder, but I'm not sure
> what this provides me... do I need to implement a particular
> interface, which is then added to the listener pool by Eclipse by
> default?
>
> It would be great if someone had some sample code on how to use these
> extension points... I'd rather not hack into the PyDev source
> directly.
Actually, I think the extension point
org.python.pydev.parser.pydev_parser_observer is more what you want:
<extension point="org.python.pydev.parser.pydev_parser_observer">
<parser_observer class="my.parser.Observer"/>
</extension>
and the Observer class must implement
org.python.pydev.core.parser.IParserObserver (it already gives you the
generated ast -- the outline is also based on this extension).
Cheers,
Fabio
|
|
From: Fabio Z. <fa...@gm...> - 2007-05-05 23:01:39
|
On 5/4/07, Neil <nei...@ut...> wrote:
>
> That makes sense...
>
> what I'm stuck on is trying to get my own plugin activated. I'm
> currently extending org.python.pydev.pydev_builder, but I'm not sure
> what this provides me... do I need to implement a particular
> interface, which is then added to the listener pool by Eclipse by
> default?
>
> It would be great if someone had some sample code on how to use these
> extension points... I'd rather not hack into the PyDev source
> directly.
You'd need to add to your plugin:
<extension point="org.python.pydev.pydev_builder">
<builder_participant class="my.pydev.Builder"/>
</extension>
and it needs to extend org.python.pydev.builder.PyDevBuilderVisitor
I'll take a look at the current schemas and give a better documentation for
the next release.
Cheers,
Fabio
thanks
> neil
>
> On 5/4/07, Ueli Kistler <uki...@hs...> wrote:
> > Hi,
> >
> > basically you need to write your own visitor class.
> > This is easily done extending VisitorBase. VisitorBase will traverse
> > "automatically" all nodes you don't want to handle yourself.
> > Override the traverse-method and call "node.traverse(this)".
> >
> > For the nodes you are interested in:
> > This class will traverse all nodes of the AST and use a "callback"
> > method when traversing a node.
> > E.g. if it traverses a ClassDef Node it will call visitClassDef(ClassDef
> > node).
> > So actually the visitor can construct your treeview-model, if you just
> > override all the visit-Methods for AST nodes you require.
> > E.g. visitClassDef, visitFunctionDef, visitCall, etc. etc. ..
> >
> > Note also that there are different AST nodes for "variables" and also
> > for "control structures"...
> > you should be able to figure out what is what for by having a look at
> > the AST Rewriter i wrote for PEPTIC (especiall visit-methods).
> > Have a look at
> >
> http://pydev.cvs.sourceforge.net/pydev/org.python.pydev.refactoring/src/org/python/pydev/refactoring/ast/rewriter/RewriterVisitor.java?revision=1.2&view=markup
> >
> > Cheers,
> > Ueli
> >
> > --
> >
> > Neil wrote:
> > > Hi Fabio, I'm following along with the mailing list advice stated
> here:
> > >
> http://www.nabble.com/PyDev-Extension-Points-Quick-Fix-%28copied-from-pydev-forum%29-tf503666.html#a1365501
> > >
> > > where you advise extending from pydev_builder to walk the AST.
> > >
> > > However, I'm new to Eclipse plugin programming so I wonder if you
> > > could be a bit more specific.
> > >
> > > Currently my plugin does something like:
> > >
> > > public class PyGoal extends PyDevBuilderVisitor {
> > > SourceModule sm = (SourceModule) getSourceModule(resource, document,
> nature);
> > > SimpleNode sn = sm.getAst();
> > > EasyASTIteratorVisitor vis = new EasyASTIteratorVisitor();
> > > try{
> > > sn.accept(vis);
> > > } catch(Exception e) {}
> > > }
> > > What I'd like to do is create a simplified syntax tree structure that
> > > just stores functions, variables, control structures, and calls. I'd
> > > then do various specific things to that tree for my own plugin.
> > >
> > > Can you illustrate how I would visit a particular document's AST,
> > > putting the elements of interest in my own data structure? How do I
> > > tell the PyDevBuilderVisitor what document/resource I'm working with?
> > >
> > > thanks
> > > neil ernst
> > >
> > > On 4/25/07, Neil Ernst <ne...@cs...> wrote:
> > >
> > >> I think it would look something like the JDT AST viewer plugin:
> > >>
> http://www.eclipse.org/articles/Article-JavaCodeManipulation_AST/index.html
> > >>
> > >> I think I should probably create a separate plugin project that calls
> > >> on PyDev to do the actual AST generation, then load that into my
> > >> plugin.
> > >>
> > >> thanks for the advice
> > >> neil
> > >>
> > >> On 4/25/07, Ueli Kistler <uki...@hs...> wrote:
> > >>
> > >>> Hi,
> > >>>
> > >>> i would not recommend using JGraph as I did... it would make more
> sense
> > >>> to extend the current outline view or provide a new "outline"-like
> view
> > >>> (i think there can be only one "true" outline view actually because
> its
> > >>> bound to an editor implementation? Not sure about this..)
> > >>>
> > >>> This could of course be done in a separate project... it would
> require
> > >>> similiar dependencies from PyDev as PEPTIC.
> > >>>
> > >>> Cheers,
> > >>> Ueli
> > >>>
> > >>> --
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> Fabio Zadrozny wrote:
> > >>>
> > >>>>> My first challenge is to view the ASTs for the entire project (I'm
> > >>>>> looking at the Trac source code). I notice in your code you have a
> > >>>>> class for viewing the AST using JGraph. Would you be able to
> point me
> > >>>>> to a way to have this done in PyDev? I've been exploring the
> Jython
> > >>>>> scripting elements of PyDev but I can't get your viewer to start
> that
> > >>>>> way.
> > >>>>>
> > >>>> The viewer that uses JGraph is not bundled in the pydev
> distribution
> > >>>> and thus cannot be accessed with the scripting... If you have the
> > >>>> source code, you can change those files from the 'contrib' source
> > >>>> folder to the actual 'src' source folder so that they can be
> accessed
> > >>>> (and add the related jars as dependencies for the plugin... or
> maybe a
> > >>>> better idea would be creating another plugin to hold those things,
> > >>>> which you can use and extend with your own code).
> > >>>>
> > >>>> Also, I think I would need more info on what you actually want to
> > >>>> access to help you better...
> > >>>>
> > >>>> Cheers,
> > >>>>
> > >>>> Fabio
> > >>>>
> > >>>
> > >
> > >
> > >
> >
> >
> >
> -------------------------------------------------------------------------
> > This SF.net email is sponsored by DB2 Express
> > Download DB2 Express C - the FREE version of DB2 express and take
> > control of your XML. No limits. Just data. Click to get it now.
> > http://sourceforge.net/powerbar/db2/
> > _______________________________________________
> > pydev-code mailing list
> > pyd...@li...
> > https://lists.sourceforge.net/lists/listinfo/pydev-code
> >
>
>
> --
> Neil A. Ernst
> Ph.D. Candidate
> University of Toronto
> http://neilernst.net
>
>
> --
> Neil A. Ernst
> Ph.D. Candidate
> University of Toronto
> http://neilernst.net
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> pydev-code mailing list
> pyd...@li...
> https://lists.sourceforge.net/lists/listinfo/pydev-code
>
|
|
From: Neil <nei...@ut...> - 2007-05-04 22:06:38
|
That makes sense... what I'm stuck on is trying to get my own plugin activated. I'm currently extending org.python.pydev.pydev_builder, but I'm not sure what this provides me... do I need to implement a particular interface, which is then added to the listener pool by Eclipse by default? It would be great if someone had some sample code on how to use these extension points... I'd rather not hack into the PyDev source directly. thanks neil On 5/4/07, Ueli Kistler <uki...@hs...> wrote: > Hi, > > basically you need to write your own visitor class. > This is easily done extending VisitorBase. VisitorBase will traverse > "automatically" all nodes you don't want to handle yourself. > Override the traverse-method and call "node.traverse(this)". > > For the nodes you are interested in: > This class will traverse all nodes of the AST and use a "callback" > method when traversing a node. > E.g. if it traverses a ClassDef Node it will call visitClassDef(ClassDef > node). > So actually the visitor can construct your treeview-model, if you just > override all the visit-Methods for AST nodes you require. > E.g. visitClassDef, visitFunctionDef, visitCall, etc. etc. .. > > Note also that there are different AST nodes for "variables" and also > for "control structures"... > you should be able to figure out what is what for by having a look at > the AST Rewriter i wrote for PEPTIC (especiall visit-methods). > Have a look at > http://pydev.cvs.sourceforge.net/pydev/org.python.pydev.refactoring/src/org/python/pydev/refactoring/ast/rewriter/RewriterVisitor.java?revision=1.2&view=markup > > Cheers, > Ueli > > -- > > Neil wrote: > > Hi Fabio, I'm following along with the mailing list advice stated here: > > http://www.nabble.com/PyDev-Extension-Points-Quick-Fix-%28copied-from-pydev-forum%29-tf503666.html#a1365501 > > > > where you advise extending from pydev_builder to walk the AST. > > > > However, I'm new to Eclipse plugin programming so I wonder if you > > could be a bit more specific. > > > > Currently my plugin does something like: > > > > public class PyGoal extends PyDevBuilderVisitor { > > SourceModule sm = (SourceModule) getSourceModule(resource, document, nature); > > SimpleNode sn = sm.getAst(); > > EasyASTIteratorVisitor vis = new EasyASTIteratorVisitor(); > > try{ > > sn.accept(vis); > > } catch(Exception e) {} > > } > > What I'd like to do is create a simplified syntax tree structure that > > just stores functions, variables, control structures, and calls. I'd > > then do various specific things to that tree for my own plugin. > > > > Can you illustrate how I would visit a particular document's AST, > > putting the elements of interest in my own data structure? How do I > > tell the PyDevBuilderVisitor what document/resource I'm working with? > > > > thanks > > neil ernst > > > > On 4/25/07, Neil Ernst <ne...@cs...> wrote: > > > >> I think it would look something like the JDT AST viewer plugin: > >> http://www.eclipse.org/articles/Article-JavaCodeManipulation_AST/index.html > >> > >> I think I should probably create a separate plugin project that calls > >> on PyDev to do the actual AST generation, then load that into my > >> plugin. > >> > >> thanks for the advice > >> neil > >> > >> On 4/25/07, Ueli Kistler <uki...@hs...> wrote: > >> > >>> Hi, > >>> > >>> i would not recommend using JGraph as I did... it would make more sense > >>> to extend the current outline view or provide a new "outline"-like view > >>> (i think there can be only one "true" outline view actually because its > >>> bound to an editor implementation? Not sure about this..) > >>> > >>> This could of course be done in a separate project... it would require > >>> similiar dependencies from PyDev as PEPTIC. > >>> > >>> Cheers, > >>> Ueli > >>> > >>> -- > >>> > >>> > >>> > >>> > >>> > >>> Fabio Zadrozny wrote: > >>> > >>>>> My first challenge is to view the ASTs for the entire project (I'm > >>>>> looking at the Trac source code). I notice in your code you have a > >>>>> class for viewing the AST using JGraph. Would you be able to point me > >>>>> to a way to have this done in PyDev? I've been exploring the Jython > >>>>> scripting elements of PyDev but I can't get your viewer to start that > >>>>> way. > >>>>> > >>>> The viewer that uses JGraph is not bundled in the pydev distribution > >>>> and thus cannot be accessed with the scripting... If you have the > >>>> source code, you can change those files from the 'contrib' source > >>>> folder to the actual 'src' source folder so that they can be accessed > >>>> (and add the related jars as dependencies for the plugin... or maybe a > >>>> better idea would be creating another plugin to hold those things, > >>>> which you can use and extend with your own code). > >>>> > >>>> Also, I think I would need more info on what you actually want to > >>>> access to help you better... > >>>> > >>>> Cheers, > >>>> > >>>> Fabio > >>>> > >>> > > > > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > pydev-code mailing list > pyd...@li... > https://lists.sourceforge.net/lists/listinfo/pydev-code > -- Neil A. Ernst Ph.D. Candidate University of Toronto http://neilernst.net -- Neil A. Ernst Ph.D. Candidate University of Toronto http://neilernst.net |
|
From: Ueli K. <uki...@hs...> - 2007-05-04 08:32:01
|
Hi, basically you need to write your own visitor class. This is easily done extending VisitorBase. VisitorBase will traverse "automatically" all nodes you don't want to handle yourself. Override the traverse-method and call "node.traverse(this)". For the nodes you are interested in: This class will traverse all nodes of the AST and use a "callback" method when traversing a node. E.g. if it traverses a ClassDef Node it will call visitClassDef(ClassDef node). So actually the visitor can construct your treeview-model, if you just override all the visit-Methods for AST nodes you require. E.g. visitClassDef, visitFunctionDef, visitCall, etc. etc. .. Note also that there are different AST nodes for "variables" and also for "control structures"... you should be able to figure out what is what for by having a look at the AST Rewriter i wrote for PEPTIC (especiall visit-methods). Have a look at http://pydev.cvs.sourceforge.net/pydev/org.python.pydev.refactoring/src/org/python/pydev/refactoring/ast/rewriter/RewriterVisitor.java?revision=1.2&view=markup Cheers, Ueli -- Neil wrote: > Hi Fabio, I'm following along with the mailing list advice stated here: > http://www.nabble.com/PyDev-Extension-Points-Quick-Fix-%28copied-from-pydev-forum%29-tf503666.html#a1365501 > > where you advise extending from pydev_builder to walk the AST. > > However, I'm new to Eclipse plugin programming so I wonder if you > could be a bit more specific. > > Currently my plugin does something like: > > public class PyGoal extends PyDevBuilderVisitor { > SourceModule sm = (SourceModule) getSourceModule(resource, document, nature); > SimpleNode sn = sm.getAst(); > EasyASTIteratorVisitor vis = new EasyASTIteratorVisitor(); > try{ > sn.accept(vis); > } catch(Exception e) {} > } > What I'd like to do is create a simplified syntax tree structure that > just stores functions, variables, control structures, and calls. I'd > then do various specific things to that tree for my own plugin. > > Can you illustrate how I would visit a particular document's AST, > putting the elements of interest in my own data structure? How do I > tell the PyDevBuilderVisitor what document/resource I'm working with? > > thanks > neil ernst > > On 4/25/07, Neil Ernst <ne...@cs...> wrote: > >> I think it would look something like the JDT AST viewer plugin: >> http://www.eclipse.org/articles/Article-JavaCodeManipulation_AST/index.html >> >> I think I should probably create a separate plugin project that calls >> on PyDev to do the actual AST generation, then load that into my >> plugin. >> >> thanks for the advice >> neil >> >> On 4/25/07, Ueli Kistler <uki...@hs...> wrote: >> >>> Hi, >>> >>> i would not recommend using JGraph as I did... it would make more sense >>> to extend the current outline view or provide a new "outline"-like view >>> (i think there can be only one "true" outline view actually because its >>> bound to an editor implementation? Not sure about this..) >>> >>> This could of course be done in a separate project... it would require >>> similiar dependencies from PyDev as PEPTIC. >>> >>> Cheers, >>> Ueli >>> >>> -- >>> >>> >>> >>> >>> >>> Fabio Zadrozny wrote: >>> >>>>> My first challenge is to view the ASTs for the entire project (I'm >>>>> looking at the Trac source code). I notice in your code you have a >>>>> class for viewing the AST using JGraph. Would you be able to point me >>>>> to a way to have this done in PyDev? I've been exploring the Jython >>>>> scripting elements of PyDev but I can't get your viewer to start that >>>>> way. >>>>> >>>> The viewer that uses JGraph is not bundled in the pydev distribution >>>> and thus cannot be accessed with the scripting... If you have the >>>> source code, you can change those files from the 'contrib' source >>>> folder to the actual 'src' source folder so that they can be accessed >>>> (and add the related jars as dependencies for the plugin... or maybe a >>>> better idea would be creating another plugin to hold those things, >>>> which you can use and extend with your own code). >>>> >>>> Also, I think I would need more info on what you actually want to >>>> access to help you better... >>>> >>>> Cheers, >>>> >>>> Fabio >>>> >>> > > > |
|
From: Neil <nei...@ut...> - 2007-05-03 23:24:23
|
Hi Fabio, I'm following along with the mailing list advice stated here: http://www.nabble.com/PyDev-Extension-Points-Quick-Fix-%28copied-from-pydev-forum%29-tf503666.html#a1365501 where you advise extending from pydev_builder to walk the AST. However, I'm new to Eclipse plugin programming so I wonder if you could be a bit more specific. Currently my plugin does something like: public class PyGoal extends PyDevBuilderVisitor { SourceModule sm = (SourceModule) getSourceModule(resource, document, nature); SimpleNode sn = sm.getAst(); EasyASTIteratorVisitor vis = new EasyASTIteratorVisitor(); try{ sn.accept(vis); } catch(Exception e) {} } What I'd like to do is create a simplified syntax tree structure that just stores functions, variables, control structures, and calls. I'd then do various specific things to that tree for my own plugin. Can you illustrate how I would visit a particular document's AST, putting the elements of interest in my own data structure? How do I tell the PyDevBuilderVisitor what document/resource I'm working with? thanks neil ernst On 4/25/07, Neil Ernst <ne...@cs...> wrote: > I think it would look something like the JDT AST viewer plugin: > http://www.eclipse.org/articles/Article-JavaCodeManipulation_AST/index.html > > I think I should probably create a separate plugin project that calls > on PyDev to do the actual AST generation, then load that into my > plugin. > > thanks for the advice > neil > > On 4/25/07, Ueli Kistler <uki...@hs...> wrote: > > Hi, > > > > i would not recommend using JGraph as I did... it would make more sense > > to extend the current outline view or provide a new "outline"-like view > > (i think there can be only one "true" outline view actually because its > > bound to an editor implementation? Not sure about this..) > > > > This could of course be done in a separate project... it would require > > similiar dependencies from PyDev as PEPTIC. > > > > Cheers, > > Ueli > > > > -- > > > > > > > > > > > > Fabio Zadrozny wrote: > > > > My first challenge is to view the ASTs for the entire project (I'm > > > > looking at the Trac source code). I notice in your code you have a > > > > class for viewing the AST using JGraph. Would you be able to point me > > > > to a way to have this done in PyDev? I've been exploring the Jython > > > > scripting elements of PyDev but I can't get your viewer to start that > > > > way. > > > > > > The viewer that uses JGraph is not bundled in the pydev distribution > > > and thus cannot be accessed with the scripting... If you have the > > > source code, you can change those files from the 'contrib' source > > > folder to the actual 'src' source folder so that they can be accessed > > > (and add the related jars as dependencies for the plugin... or maybe a > > > better idea would be creating another plugin to hold those things, > > > which you can use and extend with your own code). > > > > > > Also, I think I would need more info on what you actually want to > > > access to help you better... > > > > > > Cheers, > > > > > > Fabio > > > > > -- Neil A. Ernst Ph.D. Candidate University of Toronto http://neilernst.net |
|
From: Fabio Z. <fa...@gm...> - 2007-04-17 12:40:06
|
Hi All, Pydev and Pydev Extensions 1.3.2 have been released Details on Pydev Extensions: http://www.fabioz.com/pydev Details on Pydev: http://pydev.sf.net Details on its development: http://pydev.blogspot.com Release Highlights in Pydev Extensions: ----------------------------------------------------------------- * Fix: The vmargs in the interactive console are now only really passed to the jython process * Fix: Rename refactoring was not getting some references that mapped to imports initially (and not directly to classes or functions) * Fix: Mark Occurrences marks correctly the keyword parameters in referencing calls Release Highlights in Pydev: ---------------------------------------------- * Pydev Editor: If multiple editors are open for the same file, a parser is shared among them (which greatly improves the performance in this case) * Pydev Editor: Backspace is now indentation-aware (so, it'll try to dedent to legal levels) * Pydev Editor: sometimes the 'import' string was added when it shouldn't * Fix: Code-completion: case where a package shadows a .pyd is now controlled (this happened with mxDateTime.pyd) * Fix: Code-completion: recursion condition was wrongly detected * Fix: Code-completion: halting condition was found and removed * Fix: Project Config: if a closed project was referenced, no project was gathered for any operation (e.g.: code-completion) * Fix: The filter for showing only pydev projects is not active by default anymore What is PyDev? --------------------------- PyDev is a plugin that enables users to use Eclipse for Python and Jython development -- making Eclipse a first class Python IDE -- It comes with many goodies such as code completion, syntax highlighting, syntax analysis, refactor, debug and many others. Cheers, -- Fabio Zadrozny ------------------------------------------------------ Software Developer ESSS - Engineering Simulation and Scientific Software http://www.esss.com.br Pydev Extensions http://www.fabioz.com/pydev Pydev - Python Development Enviroment for Eclipse http://pydev.sf.net http://pydev.blogspot.com |
|
From: Fabio Z. <fa...@gm...> - 2007-04-06 10:45:14
|
On 4/5/07, Igor Foox <if...@re...> wrote: > > Hi Fabio, > > I'm packaging PyDev for Fedora and one of the issues that came up was > the origin and licensing of some of the python files that come with > PyDev. I was hoping that you'd be able to help me out in > understanding what these files are used for and wether it's OK to use > the versions that are already in Fedora. > > org.python.pydev.jython/Lib contains 125 files, of them 112 seem to > come from the python distribution, 19 seem to come from the jython > distribution, with 11 of them being shared. These 11 have some > differences among them. The other 5 files seem to be from older > distributions of python (older than 2.5) and no longer exist in 2.5. All beneath org.python.pydev.jython/Lib come from jython 2.1. I just extracted it and bundled it in pydev (the jython guys probably have taken some of them from python). My question is, what versions of Python/Jython are these files from > and what is their use in PyDev? Would it be safe for me to link these > files with the files that come with the stock Python 2.5 or Jython > 2.2beta1 distributions? I don't think it's really safe to change those files, as it could break some things... that internal jython distribution is actually only used for jython scripting inside of pydev, but those scripts would have to be re-checked if an upgrade is done (I'd rather only do that update once jython 2.2 is stable). Similarly, the files in org.python.pydev/PySrc. Some of them are > clearly developed specifically for pydev, but some others seem to > come from elsewhere. The files from org.python.pydev/PySrc/ThirdParty are either from Bycicle repair man or ctypes (they are distributed in pydev, and executed under a separate shell). Cheers, Fabio |