On Sun, May 2, 2010 at 3:32 PM, Glyph Lefkowitz <gl...@twistedmatrix.com> wrote: > > On Apr 30, 2010, at 9:31 PM, Fabio Zadrozny wrote: > > So, as it is there's nothing that does what you want automatically. > Still, it should not be hard to make up a python script that you run > with the heuristic you just said that updates the .pydevproject file > with those configurations (which would update the information pydev > needs). > > Yes, and in fact I have written a little script that does what I need for my > particular projects. > Still, I believe it would provide a nicer first-time experience for pydev > users if the workflow were simply "here is my code, let's go", rather than > "here is my project, and no don't create a 'src' folder[1], and by the way > here is my interpreter, and by the way here are the locations in my project > folder where source code lives". I have to imagine that most people trying > out pydev are trying it on an existing codebase and not a fresh new project.
I think that's a nice idea... Can you create a feature request for that? I'm thinking in the terms of having a new project wizard from existing sources, what do you think? Also, as you already did a script for your needs, it could be nice adding that to the request. > To be fair, some of the problem lies with the various "Team" providers, as > they require you to create projects in your filesystem hierarchy wherever > the SVN checkout happens to be rather than where it makes sense for the > source code to be considered a 'project'. > > [1]: http://jcalderone.livejournal.com/39794.html Yes, and unfortunately that goes really deep within the eclipse APIs... Cheers, Fabio Cheers, Fabio ------------------------------------------------------------------------------ _______________________________________________ Pydev-users mailing list Pydev-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pydev-users
