-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not working on Mac #39
Comments
Mmmh, did you installed your currently enabled Python version with pyenv or brew ? I know it can happen with pyenv if not correctly configured for MacOS, some "shims" can be unreachable. Also with Brew if you installed a different unsupported Python version, it possibly didn't have linked your Python version binaries. |
SOLVED! Well Python actually comes pre-installed on all new versions of Mac OS, so I didn't install it myself. I did a little digging on stackoverflow, see this answer/question, looks like this is an issue for any Python CLI app not just boussole. Turns out it was a path issue and the solution was to add Might be worth adding a line in the README to help Mac users.. up to you though. |
I will make a release this spring to align tox tests with the last libsass-python and will try to remember to put a notice about it, probably just a short notice using your links, i don't want to write too much on it as it could explain to a whole book.. Until now i keep your issues opened so everyone can see your resolution. Thanks for the feedback. |
Documentation have been updated in v2.1.0 |
Hey,
I installed boussole on my Ubuntu laptop and it works great, thanks so much!!!
However, this week I tried installing in on my Mac and unfortunately it doesn't seem to work. 😢
I've tried a simple
pip install boussole
andpip install boussole --user
. It installs fine but when I try to run a command likeboussole startproject
I get an errorcommand not found: boussole
.Somehow the command
boussole
doesn't seem to be in my path. Any ideas why this would be and how I can fix it?The text was updated successfully, but these errors were encountered: