Is there any way to specify the python interpreter (in settings) using a path variable rather than an absolute path? I would like to put eclipse + pydev on a flash drive. I think the only stumbling block to doing that is the python interpreter config. If this can't be done currently, could you point me in the right direction w/in the codebase so I could add this functionality?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've been thinking a bit about that, and the problem is not actually pydev, but putting your workspace there (that's where the interpreter config is stored). If you want to have the interpreter 'pre-configured', I'd suggest putting the interpreter in the drive and always mapping that drive to the same path... (is this enough for you?)
Cheers,
Fabio
p.s. It's far from trivial making that info relative and not absolute...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think there may be a workaround for me that involves simply creating a drive mapping each time. However, if the interpreter location could be made relative or variable, it would be much more convenient. My idea was actually to see if I could make the interpreter location support variable mappings, much like the eclipse java classpath. I was going to start out by trying to support environment variables (which would solve my particular problem) and then, if that worked out, move on to classpath-type mappings.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
By the way, I do intend to install the interpreter on the flash drive as well, along with all of the requirements of my particular python application (wx, 4suite, etc). I think I should be able to get it all to work - ideally I want to simply be able to pop in the flash drive and launch a .bat file. The .bat file would set up some env variables and then launch eclipse. Seems possible.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Is there any way to specify the python interpreter (in settings) using a path variable rather than an absolute path? I would like to put eclipse + pydev on a flash drive. I think the only stumbling block to doing that is the python interpreter config. If this can't be done currently, could you point me in the right direction w/in the codebase so I could add this functionality?
Hi Eric,
I've been thinking a bit about that, and the problem is not actually pydev, but putting your workspace there (that's where the interpreter config is stored). If you want to have the interpreter 'pre-configured', I'd suggest putting the interpreter in the drive and always mapping that drive to the same path... (is this enough for you?)
Cheers,
Fabio
p.s. It's far from trivial making that info relative and not absolute...
I think there may be a workaround for me that involves simply creating a drive mapping each time. However, if the interpreter location could be made relative or variable, it would be much more convenient. My idea was actually to see if I could make the interpreter location support variable mappings, much like the eclipse java classpath. I was going to start out by trying to support environment variables (which would solve my particular problem) and then, if that worked out, move on to classpath-type mappings.
By the way, I do intend to install the interpreter on the flash drive as well, along with all of the requirements of my particular python application (wx, 4suite, etc). I think I should be able to get it all to work - ideally I want to simply be able to pop in the flash drive and launch a .bat file. The .bat file would set up some env variables and then launch eclipse. Seems possible.
Hi Eric. I'm curious, were you able to work out a solution? If so, how is it working for you?
I ended up using the windows 'subst' command to map my portable drive to a consistent drive letter.
It ended up being a moot point though, since the flash drive (at least the one I have) is just too slow to do development on.