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
'tqdm' object has no attribute 'disable’ (users with Mac OS and Python3.7+ affected) #80
Comments
I am afraid this is a possible bug in 'tqdm'. See tqdm/tqdm#487 This seems to be out of my competence and I do not have the time to investigate in depth how this can be fixed in 'tqdm'. I hope that the 'tqdm' developers will fix this soon. Perhaps you can open an issue in their git-hub? FYI, I cannot reproduce the problem under Linux/Ubuntu with Python3.8 and 3.9, but indeed the problem appears in Mac OS. I suspect this is somehow connected with how python3 handles multiprocessing/multithreading on Mac OS. A fix could be to simply tun-off the progress bar when running NS/MCMC git pull, and try again. Please report if this is a potential workaround! |
Unchecking MCMC progress bar seems to work in versions newer than Python 3.7.12. The MCMC analysis is performed while the Stdout/Stderr does not display any message. The problem looks indeed within macOS and the handling of multiprocessing in Python3.8 and newer. This thread in Stackoverflow supports this thesis, as I could reproduce both the problem and the solution. |
Any development on the "tqdm" side on this? |
Looks like the thread regarding this issue (tqdm/issues/487) is now closed, as brianbruggeman provided a working solution. Maybe this helps for now. |
This does not seem a general solution within tqdm. @ccifuentesr, when you have time, can you update your tqdm and Exo-Striker and try to reproduce the bug? |
This seems to be old and already fixed external bug, thus closing. |
When running MCMC I get an AttributeError: 'tqdm' object has no attribute 'disable’. This occurs in macOS (current version, 11.6) and Python >= 3.8. The error does not seem to arise in earlier versions of Python, in particular in 3.7.12.
The text was updated successfully, but these errors were encountered: