dictation-toolbox / natlink

Natlink provides the interface between Dragon and python
Other
25 stars 17 forks source link

Powershell to allow users to enter Natlink python environment #138

Closed LexiconCode closed 11 months ago

LexiconCode commented 1 year ago

While there are many ways to go about this having a single place to enter into Natlink python environment to manage packages will simplify the experience.

The trick here is when the installer builds is it creates this file to the correct Python environment. That way when the user installs Natlink it always has the correct Python path.

Ideally it would be nice to use visualized python environments but that is not possible at this time.

quintijn commented 1 year ago

Hi LexiconCode, I cannot judge on this. We should discuss this further, or with Doug Ransom.

LexiconCode commented 1 year ago

The issue is Python can be off or on path. As we provide documentation this can be a challenge as the documentation is a bit different per environment. The point is we don't when I leave this up to the end user having to figure out this process will when we can provide a clear path that works. So instead of reconciling these differences in the documentation provide one method for both scenarios. This could be very simple.

cd C:\Program Files (x86)\Python310-32 into the Natlink Python environment wherever that path may be.

That way any command like python eg ('python -m pip install package') will work as expected.

Once that's accomplished the documentation can be as go to "natlink_environment.bat" and manage any python packages

so the question is how do we get the path?

So if the CLI/GUI is initialized it could add/update key a path to the python

LexiconCode commented 11 months ago

done in https://github.com/dictation-toolbox/natlink/commit/f30fb8ee06615752e3c2434552c3c7856e32c966