Suggestion to automate addition/check of directory for nth script to PATH

[nucleare]

Foreword:

This started out originally as an issue submission and during due process, was resolved and evolved into a suggestion if nothing else. Truth be told, I just didn't want all that effort of putting together all the information to go to waste, especially since I've done enough of that (wasting effort) already with my life. I mean, all that formatting too...

---

Installation in Windows Linux Subsystem on Python 3.8 fails to create the nth alias*

*It was originally believed that the nth command was an alias for the main.py

Overview:

Although I have not tested this on a native Linux system, I thought it would be worth mentioning in case someone else runs into a similar issue and may not have the know-how to incorporate a workaround and; otherwise it may be closed if found that the issue cannot be reproduced or as later determined personally in hindsight, a rare and more likely unique case. an erroneous mistake regarding missing PATHs.

System:

$ uname -r
5.4.72-microsoft-standard-WSL2

Issue:

Whereas, after successful installation using pip3 install name_that_hash and attempting to run nth per the installation instructions the command is not found.

• The name-that-hash and nth scripts were properly installed to the $HOME/user/.local/bin directory and triggers a warning of missing entries in PATH.

Installing collected packages: pygments, commonmark, rich, click, name-that-hash
  WARNING: The script pygmentize is installed in '/home/{user}/.local/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
  WARNING: The script cmark is installed in '/home/{user}/.local/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
  WARNING: The scripts name-that-hash and nth are installed in '/home/{user}/.local/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
Successfully installed click-8.0.3 commonmark-0.9.1 name-that-hash-1.10.0 pygments-2.11.1 rich-10.16.1

• After adding the directories to path (and confirming with echo $PATH) the commands were still not recognized when attempting to execute the commands nth and name-that-hash
• It was at this point that the [EDIT] comment was added below, as it was realized that even though I updated ~/.bashrc and used source ~/.bashrc to load the new PATH environment, the commands still would not call the scripts even when the PATH had been updated and it was later discovered that starting a new instance of WSL resolved the issue.

Notes:

This was later determined purely a result of missing entries in $PATH during installation which produced missing PATH warnings. After updating the PATH directories and restarting WSL, the issue is resolved. The emphasis being needing to actually restart WSL and not just refresh the terminal.

[EDIT: While reproducing the issue to gain more clarity on the root cause, it was realized that this issue is unrelated the code itself and has only been submitted for consideration of an accessibility feature whereby possibly updating/modifying the installation instructions that creates the nth script to also automatically the directory hosting the scripts to PATH. My apologies in advance if submitting such an issue was unnecessary or misplaced.]