-
Notifications
You must be signed in to change notification settings - Fork 111
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
Regression on pyparsing 2.1.0 #38
Comments
I can reproduce this error on Python 2.7 and 3.5 with pyparsing 2.1.0. Downgrading to 2.0.7 makes the problem disappear. |
Issue reported upstream https://sourceforge.net/p/pyparsing/bugs/91/ |
https://sourceforge.net/p/pyparsing/bugs/92/ is the new issue tracking the bug -- upstream is reporting it's fixed in master. |
pyparsing 2.1.1 has been released. Once this issue is confirmed fixed, we'll bump the version in setup.py |
pyparsing 2.1.1 seems to have a different regression, so we're just going to stay on 2.0.7 for the near future. |
a7be84a should have fixed this for all recent versions of pyparsing. |
…had#38) Add multiprocessing option through emcee and make it default. * Add warning that MPIPool does not take cores argument. * Add default to available cores for emcee and dask (total number of cores) * Change expected default scheduler to emcee in tests
Database loading appears to hang on pyparsing 2.1.0.
Reporting user traceback:
The text was updated successfully, but these errors were encountered: