Skip to content
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

homebrew Python version & uv tool install --upgrade mflux issue -> documentation note? #107

Open
gmorain opened this issue Dec 23, 2024 · 3 comments
Labels
installation Installation issue or tips

Comments

@gmorain
Copy link

gmorain commented Dec 23, 2024

Hi,

I had an issue updating MFlux to 0.5.0 this morning, as the tool install --upgrade mflux command failed.

Homebrew is quite 'aggressive' in keeping all package versions up to date, so after a recent brew install <something> my setup was pushed to Python 3.13 (as seen with the python3 --version and uv python list commands).

Having met this kind of breaking behaviour before, and having seen the Python 3.13 note and issue in the MFlux README / repo, I reverted my default homebrew Python version to 3.9 and voilà! (uv still uses the recommended Python version defined in the toml file coming with mflux (ie something >=3.10 if I am not mistaken).

brew unlink [email protected]
brew unlink [email protected]
brew link --force --overwrite [email protected]
uv tool install --upgrade mflux

Hope this helps people getting the same issue while using homebrew and MFlux

@gmorain gmorain changed the title homebrew Python version & uv tool install --upgrade mflux issue -> documentation note? homebrew Python version & uv tool install --upgrade mflux issue -> documentation note? Dec 23, 2024
@filipstrand
Copy link
Owner

Thanks for sharing your issue and strategy here. I have not personally kept up with the state of python 3.13 yet, so cannot comment about that, but happy it worked by downgrading the python version!

I am happy to keep this issue open as a reference for others and I'll just make a small general note in the readme to point people to the issue section if they have any such troubles (a while back, I was thinking about adding a general "installation issues" sub section in the README, but it feels like there are so many ways things can break and differ between systems and setups, so I'll keep that section very brief and simply point people to the issue section)

@gmorain
Copy link
Author

gmorain commented Dec 26, 2024

Hi @filipstrand, having so many possible causes for trouble in this fast-moving space might indeed make the README grow beyond a manageable size, so I totally understand your point in keeping that in a separate place. May I suggest the introduction of tags so issues can be listed as "documentation", "improvement", and so on?

@filipstrand
Copy link
Owner

That is a good idea

@filipstrand filipstrand added the installation Installation issue or tips label Dec 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
installation Installation issue or tips
Projects
None yet
Development

No branches or pull requests

2 participants