Re: [Pydev-code] Next release

[Aleks T. <a...@to...>]

Hi Fabio,
this is great news, way beyond what I was thinking about. I am 
sure the pydev users will love it. About feature freeze, that was 
just a suggestion, it seems as if everything you've done is ready 
to ship. You've

My current plan is to compile what we have, clean up the debugger 
bugs, and ship it, late tomorrow as 0.6. About documentation, 
I'll do what I can. Can you give me some good examples of how 
your features work? Maybe a python file with comments like "you 
can refactor this, you can do code completion on these".

For imports code completion, what are you using as your path?

Aleks

Fabio Zadrozny wrote:
> Hi All,
> 
> I've been working full time the last week in pydev (thanks to some support
> from my company), so, I have been able to introduce the following features
> in the plugin (yes Aleks, I saw you said freeze the features, but I was
> REALLY, REALLY in need for that):
> 
> Python shell integration
> 	- Using a python shell and communicating through sockets (for
> refactoring, search and code completion).
> 
> Refactoring:
> 	Completed:
> 	- Bicycle repair man (BRM) integration (support for rename and
> extract method). 
> 	- Added a view to show which files were affected by the last
> refactoring
> 	Missing:
> 	- Undo of the refactoring (it is supported by BRM but not
> integrated).
> 	- There are other refactorings that can be integrated. 
> 	- Only appearing on right click menu... Some keybindings could be
> used also.
> 
> Search:
> 	Using Bicycle repair man go to definition search on key F3. It is
> used because our search was only on the current buffer (and that was really
> annoying). 
> 
> Code completion:
> 	Basically, this was a rewrite from the python side of the code
> completion. I think there are better ways to do it, but time is never
> enough, so, code completion now works on:
> 		- import ...
> 		- from ... 
> 		- from a import ...
> 		- self.
> 		- any other token that we are able to get on the module
> level, that is, variables initialized inside methods or other scopes are not
> gotten (they weren't earlier either, so, that's not a retrocess).
> 
> 	So, missing for this feature is:
> 		- Work on inner scopes: this would require some good work
> with the python ast...
> 		- It still doesn't work on method parameters, but it could
> be added without too much effort (I will do it as soon as I can, but I still
> don't know when I will be able to do it - so, if anyone volunteers...).
> 
> Well, I think that's it... The bad part is that I didn't put it in pydev
> help (if someone volunteers...)
> 
> Anyway, I think that's enough for a 0.6 release, and if those features prove
> to be stable, it should be enough for a stable 1.0 release...
>