# Revision history [back]

### ${} in Launch Configurations In Wing 7x I used this pattern often${DCCSI_PY_IDE} to define interpreters for launch configurations.

In Wing 7, I used this as my project properties interpreter: ${DCCSI_PY_IDE} Then I would set up other python.exe as additional launch configurations: •${DCCSI_PY_MAYA}
• ${DCCSI_PY_SUBSTANCE} • ... That allowed me to switch interpreters on the fly, and validate code on different python interpreters of my DCC tools. This broke in Wing 8 as far as I can tell, I can use this is as the slug for me project properties, and it will work as the primary interpreter:${DCCSI_PY_IDE} But if I then use the same slug as a shared launch configuration, that configuration willl not be able to start the interpreter.

I even tried the following ... I set up a shared launch configuration, using env hooks, like: ${MAYA_BIN_PATH}\mayapy.exe ^ that does not work in Wing 8 I have verified that the envar is set, I can retrieve it from the console. • import os • print(os.getenv('MAYA_BIN_PATH')) • C:\Program Files\Autodesk\Maya2022\bin I do not have enough points to upload an image.  2 retagged Wingware Support 3826 ●2 ●120 ●16 https://wingware.com/ ###${} in Launch Configurations

In Wing 7x I used this pattern often ${DCCSI_PY_IDE} to define interpreters for launch configurations. In Wing 7, I used this as my project properties interpreter:${DCCSI_PY_IDE} Then I would set up other python.exe as additional launch configurations:

• ${DCCSI_PY_MAYA} •${DCCSI_PY_SUBSTANCE}
• ...

That allowed me to switch interpreters on the fly, and validate code on different python interpreters of my DCC tools.

This broke in Wing 8 as far as I can tell, I can use this is as the slug for me project properties, and it will work as the primary interpreter: ${DCCSI_PY_IDE} But if I then use the same slug as a shared launch configuration, that configuration willl not be able to start the interpreter. I even tried the following ... I set up a shared launch configuration, using env hooks, like:${MAYA_BIN_PATH}\mayapy.exe ^ that does not work in Wing 8 I have verified that the envar is set, I can retrieve it from the console.

• import os
• print(os.getenv('MAYA_BIN_PATH'))
• C:\Program Files\Autodesk\Maya2022\bin

I do not have enough points to upload an image.

 3 retagged Wingware Support 3826 ●2 ●120 ●16 https://wingware.com/

### ${} in Launch Configurations In Wing 7x I used this pattern often${DCCSI_PY_IDE} to define interpreters for launch configurations.

In Wing 7, I used this as my project properties interpreter: ${DCCSI_PY_IDE} Then I would set up other python.exe as additional launch configurations: •${DCCSI_PY_MAYA}
• ${DCCSI_PY_SUBSTANCE} • ... That allowed me to switch interpreters on the fly, and validate code on different python interpreters of my DCC tools. This broke in Wing 8 as far as I can tell, I can use this is as the slug for me project properties, and it will work as the primary interpreter:${DCCSI_PY_IDE} But if I then use the same slug as a shared launch configuration, that configuration willl not be able to start the interpreter.

I even tried the following ... I set up a shared launch configuration, using env hooks, like: \${MAYA_BIN_PATH}\mayapy.exe ^ that does not work in Wing 8 I have verified that the envar is set, I can retrieve it from the console.

• import os
• print(os.getenv('MAYA_BIN_PATH'))
• C:\Program Files\Autodesk\Maya2022\bin

I do not have enough points to upload an image.