templates
/
KiBot
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Added more notes about Windows CI/CD

This commit is contained in:
Salvador E. Tropea 2022-07-03 20:48:06 -03:00
parent e98c0cf933
commit 35a4cb71ee
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
experiments/Windows/GitHub/README.md
View File

@ -81,8 +81,13 @@ Is a mess.
Problems: Problems:
1. Only `python` binary, no `python3`. Even when they include `pip` and `pip3`! 1. Only `python` binary, no `python3`. Even when they include `pip` and `pip3`!
*Workaround*: Use `python`
2. You can't run pip installed scripts. They have a wrong shebang, useless for bash and Power Shell. You must use `python FULL_PATH`. 2. You can't run pip installed scripts. They have a wrong shebang, useless for bash and Power Shell. You must use `python FULL_PATH`.
*Workaround*: Use `python SCRIPT` or switch to entry-points.
3. Power Shell silently fails if the shebang is wrong!!! 3. Power Shell silently fails if the shebang is wrong!!!
*Workaround*: Add more debug to know it even tried to execute it
4. `pip install .` doesn't work.
*Workaround*: Use `pip install DIR`
# KiCad command shell # KiCad command shell
@ -151,3 +156,6 @@ The /k means continue.
- Run with: `python "C:\Program Files\KiCad\6.0\bin\Scripts\kibot"` - Run with: `python "C:\Program Files\KiCad\6.0\bin\Scripts\kibot"`
- We should try to add an entry point so we can avoid the shebang problem - We should try to add an entry point so we can avoid the shebang problem
# Conclusions
1. The Python included with KiCad is broken, it can't handle *scripts*, just entry points.