Motivation
This is the first roadblock that a lot of people have encountered when trying out this package:
Proposed Solution
@ncguilbeault wrote a very nice comment on troubleshooting steps which I think could be easily converted to a main article at least on the Manual section:
The article should then be linked on the current Introduction page and the API reference for the CreateRuntime operator.
Alternative Solution
I am always wondering if this error could be easily resolved by specifying the python executable path separate from the virtual environment home. This link seems to indicate that we can pass additional environment variables to Python.Net? Not sure if I am understanding that link right so I am not sure how feasible this alternative solution is.
Motivation
This is the first roadblock that a lot of people have encountered when trying out this package:
Proposed Solution
@ncguilbeault wrote a very nice comment on troubleshooting steps which I think could be easily converted to a main article at least on the
Manualsection:The article should then be linked on the current
Introductionpage and the API reference for theCreateRuntimeoperator.Alternative Solution
I am always wondering if this error could be easily resolved by specifying the python executable path separate from the virtual environment home. This link seems to indicate that we can pass additional environment variables to
Python.Net? Not sure if I am understanding that link right so I am not sure how feasible this alternative solution is.