You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Docs: add a Windows troubleshooting section to the README #33
Hi!
Yes, you can take this one, I’ll assign it to you. It is a documentation-only change: edit README.md only, no code and no tests.
What to do: add a new section called ## Windows troubleshooting to the README, after the quickstart. It should cover:
Activating the virtual environment
PowerShell: venv\Scripts\Activate.ps1
cmd: venv\Scripts\activate.bat
Note that the source venv/bin/activate command in the quickstart is for Mac/Linux only.
PowerShell blocks the activation script (an error about “running scripts is disabled”). The fix is Set-ExecutionPolicy -Scope CurrentUser RemoteSigned.
fixit is not recognized. Explain the likely causes and fixes:
The virtual environment is not activated.
pip install -e ".[dev]" was not run yet.
Workaround that always works: python -m fixit wc "hello world".
python is not recognized. Try py instead, for example py -m venv venv.
Please test it yourself: run each command on your Windows machine and only document what actually works for you. Don’t copy fixes from the internet that you haven’t tried.
Rules for this PR:
Change only README.md, and only add the new section. Don’t reformat or rewrite other parts.
Activity
Giorgx12 commentedon Oct 9, 2026
In your opinion, could I do this? It's only the readme and troubleshooting, isn't it?
codepiyusss commentedon Oct 10, 2026
Hi!
Yes, you can take this one, I’ll assign it to you. It is a documentation-only change: edit
README.mdonly, no code and no tests.What to do: add a new section called
## Windows troubleshootingto the README, after the quickstart. It should cover:Activating the virtual environment
venv\Scripts\Activate.ps1venv\Scripts\activate.batvenv/bin/activatecommand in the quickstart is for Mac/Linux only.PowerShell blocks the activation script (an error about “running scripts is disabled”). The fix is
Set-ExecutionPolicy -Scope CurrentUser RemoteSigned.fixitis not recognized. Explain the likely causes and fixes:pip install -e ".[dev]"was not run yet.python -m fixit wc "hello world".pythonis not recognized. Trypyinstead, for examplepy -m venv venv.Please test it yourself: run each command on your Windows machine and only document what actually works for you. Don’t copy fixes from the internet that you haven’t tried.
Rules for this PR:
README.md, and only add the new section. Don’t reformat or rewrite other parts.Open the PR when you’re ready and I’ll review it. Ask here if anything is unclear.
Giorgx12 commentedon Oct 13, 2026
Can I separate Windows from Linux activation? Pls see my fork
codepiyusss commentedon Oct 13, 2026
Open the PR i'll review there.
Thanks!