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
Investigate issue with pyparsing 2.1.6 #6932
Comments
Also given that this is the third time within a relatively short time span that a new version of pyparsing breaks we should perhaps consider limiting the version number |
Or perhaps do an intervention with the pyparsing devs? On Tue, Aug 9, 2016 at 4:04 AM, Jens Hedegaard Nielsen <
|
Yes that would be ideal. Pyparsing is currently on sourceforge and in SVN I think. It would be ideal to move it to github and add Travis or similar to it |
Dear pyparsing, Thank you for giving me the chance to talk to you today. There are so many Before you began doing poor releases, we were so close. There was nothing I Sincerely, On Tue, Aug 9, 2016 at 10:10 AM, Jens Hedegaard Nielsen <
|
It seems like the issue has been fixed with pyparsing 2.1.7 |
Travis is failing with pyparsing 2.1.6 workaround in #6931
Need to figure out if this is a bug that needs reporting upstream or if we are doing anything wrong
The text was updated successfully, but these errors were encountered: