Yeah I've burnt alot of time with this one over the last weekend.
Its patchy inconsistent and since I'm on the win7x64 side of things I'm finding most input is "huh works for me you must be dumb or something.." not so helpful. and many answers on here are from other platforms so sifting this info to determine whats useful is quite hard work.
I have found that with in config files the newer:
On winx64 just does not work.
Does not work with explicit paths, does not work with native envVars, although I don't know if it should?
It also does not work with python packaged in .zip, should it? who knows.. be nice if it did mind.
Nor does it work with an extracted typical installation of python i.e. c:/Python26/
at least in my experience
However the older:
// "PYTHONPATH":"C:/Python26: C:/Data/PythonProjects/homeProjects"
seemed to work more reliably, however more reliable in the sense that some .py files in the same project work and complete quite nicely and gave me quite a chill a thing of beauty and so much promise, yet another file in the same project in the same directory would not complete anything at all, most frustrating! yes I have been blowing away the db files and rebuilding between each alteration test cycle to see what changes.
I am unsure if comments in code blocks above cause failure?
I am unsure if the "env" settings can even be put in the config files? I did try.. no gravy..
forces it to use the specified python version which is nice otherwise it seems to find python in system paths somewhere, not sure where it gets them from the registry as that was the only place I found an entry for my local x64Python version at one point, I don't have PYTHONPATH and PATH pointing to installations on my machine. Any more checking is probably going to be a debugging and dissection session.
I have found I only get db files in the:
and not in the:
even though I have configs there I don't know if I should..
I would like to see :
PYTHONPATH : "path..", "path.."]
rather than :
PYTHONPATH : "C:/Python26: C:/Data/PythonProjects/homeProjects:$PYTHONPATH"
as its far easier to deal with.
and that $PYTHONPATH is it accessing the current system PYTHONPATH, is that consistent for all platforms, what is it doing?
All the apparently stupid questions I'm asking really need documentation to assist this tool(me and CodeIntel), sometimes you have to over communicate stuff that may seem really obvious, when to some its really not.
If I could get some sort of consistency I'd be quite happy to use it, its got so much potential and is really nice.. when it works!
But really as a result of the experience I've gone back to WINGIDE as it just works.. and the auto-complete and the debuggers are really something I need for speed whilst working in a development environment.
But I am using Sublime more and more for general stuff replacing a stack of other editors that all have bits of things that are really useful that sublime has or as I figure it out I can probably add.