[Pydev-code] Some ideas about PyDev
Brought to you by:
fabioz
From: Radim K. <ra...@ku...> - 2008-07-27 23:10:24
|
Hi Fabio and all, I have a few ideas what I would like to change improve in current PyDev. Basically most of them are a result of my attempts to improve Python delelopment experience in our environment. I really like the fact that there is already so much work done. Thanks for that. Still there is some space for improvements. Some of them are general and some are more specific for my use cases. - speed and support for included/excluded resources: currently the initial scan of platform and project takes too long + it tries to scan recursively everything under the path root directories. This is very unfortunate if your project is using SCM shared by more projects and you really do not want to analyze unrelated sources. - coverage: currently there are several launch types (run, (unit)test, coverage) and two modes (exec/debug) while more natural to me is two launch types (run / test) and three modes (exec/debug/coverage). Note that this is similar to an approach taken by popular plugin for Java coverage EclEmma (http://eclemma.org/). Also the UI provided by current coverage supprt can by improved a lot - I'd like to see the result as some kind of annotation in editor - follow more Eclipse API/SPIs. Now I have some troubles as PyDev converts eclipse Path to java.io.File almost instantly. This makes it hard to use Eclipse links to link only to a specific directories (I do that to work around a problem mentioned above). I can submit patches for some of these as well as do some bugfixes if there is an agreement that these are good ideas. Comments, feedback? I'd also like to know what is current estimation for Ganymede (Eclipse 3.4) support? -Radim |