-
Notifications
You must be signed in to change notification settings - Fork 199
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
Python support 3.x #82
Comments
In the meantime it's quite a challenge to get Python 2 running on a modern macOS. Even |
First, I support the idea of migrating this to Python v3. But, I don't know how much extra time @timsutton has currently. There is an old PR for Python 3 support. I actually recommend pyenv for your primary Python. Apple is still shipping v3.9.6 from June 2021. Maybe the are backporting security fixes. But, I doubt it. So while I suggest you make pyenv permanent, I will write these instructions so there is no permanent change to your system. pyenv - Simple Python Version Management
|
@jaredstanko Thx a lot for the pyenv Install Guide! Just want to add that under MacOS 11.13 (High Sierra) with an iMac 12,2 (27", mid 2011) I got an error while trying to run this:
This was easy to solve, I just installed virtualenv via After that I could run the brigadier script without any problems. Thank you so much @timsutton for writing this! Now I am a step further in reinstalling bootcamp :) |
This is not so much of an issue, but mostly security. Since python 2.x has been phased out, has brigadier moved to support current versions of phython 3.x ?
In the Wiki:Readme:
I'm looking to get the full functionality of the Magic Keyboard on a non-mac, non-apple, Microsoft Windows system. Additionally, read battery levels to determine why the Magic Keyboard is suddenly draining batteries in less than a day. Potentially a Microsoft update, though Bluetooth drivers have not changed nor anything else other than PowerToys.
https://www.bluetoothgoodies.com/info/apple-devices/ ,
also magicutilities but not in agreement with this particular developer.
The text was updated successfully, but these errors were encountered: