Description:
When installing graphifyy on Windows using:
the installation completes successfully, but running:
fails with:
graphify: The term 'graphify' is not recognized as a name of a cmdlet...
Root Cause:
The CLI executable (graphify.exe) is installed in the user Scripts directory:
C:\Users\<username>\AppData\Roaming\Python\Python3xx\Scripts
However, this directory is not automatically added to the system PATH, so PowerShell cannot find the command.
Pip does show a warning:
WARNING: The script graphify.exe is installed in ...\Scripts which is not on PATH.
But the project documentation does not mention this, which can confuse users.
Suggested Fix (Docs Update):
Add a Windows-specific note in the README under installation:
Windows Users:
After installation, you may need to add the Python Scripts directory to your PATH:
Temporary fix (current session):
$env:Path += ";C:\Users\<username>\AppData\Roaming\Python\Python3xx\Scripts"
Permanent fix:
[Environment]::SetEnvironmentVariable(
"Path",
$env:Path + ";C:\Users\<username>\AppData\Roaming\Python\Python3xx\Scripts",
"User"
)
Then restart your terminal.
Alternative Workaround:
You can also run the CLI without modifying PATH:
Why this matters:
This is a common Windows issue with user-level pip installs, and documenting it would significantly improve onboarding for new users.
Environment:
- OS: Windows 11
- Python: 3.14
- graphifyy: 0.4.18
- Shell: PowerShell
Description:
When installing
graphifyyon Windows using:the installation completes successfully, but running:
fails with:
Root Cause:
The CLI executable (
graphify.exe) is installed in the user Scripts directory:However, this directory is not automatically added to the system
PATH, so PowerShell cannot find the command.Pip does show a warning:
But the project documentation does not mention this, which can confuse users.
Suggested Fix (Docs Update):
Add a Windows-specific note in the README under installation:
Windows Users:
After installation, you may need to add the Python Scripts directory to your PATH:
Temporary fix (current session):
Permanent fix:
Then restart your terminal.
Alternative Workaround:
You can also run the CLI without modifying PATH:
Why this matters:
This is a common Windows issue with user-level pip installs, and documenting it would significantly improve onboarding for new users.
Environment: