I can have several different versions of this build tool running simultaneously, when I'm working on more than one project, release or feature. I don't know exactly how it works, but I activate (a python term I guess) a different python environment for each version of the software that I'm working on. Apparently, Sublime tries to use this environment when I start it from a command-line there I have activated the build tool. This results in a lot of tracebacks like the following when I run 'sublime_text.exe'.
- Code: Select all
Traceback (most recent call last):
File ".\sublime_plugin.py", line 1, in <module>
File ".\os.py", line 398, in <module>
File ".\UserDict.py", line 83, in <module>
File "C:\views\jsc_FwMainlinePrj\pooma\Lib.zip\Lib\abc.py", line 109, in register
File "C:\views\jsc_FwMainlinePrj\pooma\Lib.zip\Lib\abc.py", line 151, in __subclasscheck__
File "C:\views\jsc_FwMainlinePrj\pooma\Lib.zip\Lib\_weakrefset.py", line 69, in __contains__
TypeError: cannot create weak reference to 'classobj' object
The path 'C:\views\jsc_FwMainlinePrj' is one of the branches of our software that I'm working on and 'C:\views\jsc_FwMainlinePrj\pooma' is the path to the build tool. I know very little about python, but to me it looks like Sublime is trying to use the python environment that comes with the build tool. Is there a way I can make Sublime use its own python environment while the python environment for our custom build tool is still activated?