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

Import pyparsing in testing so twill's older version doesn't get loaded. #2656

Merged
merged 1 commit into from
Jul 26, 2016

Conversation

jmchilton
Copy link
Member

There are unintended consequences if not, such as svgwrite not loading properly.

@martenson
Copy link
Member

martenson commented Jul 26, 2016

@jmchilton F401 'pyparsing' imported but unused

@galaxybot galaxybot added this to the 16.07 milestone Jul 26, 2016
There are unintended consequences if not, such as svgwrite not loading properly.
@jmchilton jmchilton force-pushed the pyparsing_testing branch from 7a37345 to 93ba35f Compare July 26, 2016 15:18
@nsoranzo
Copy link
Member

nsoranzo commented Jul 26, 2016

What about using a fork of the unmaintained twill instead? Branch 2.0 of @Cito's fork seems pretty good and does not ship an embedded pyparsing any more. This will also give us Python3 support.

@martenson
Copy link
Member

@nsoranzo I am +1 on using that fork but that will not make it to 16.07 so I will merge this once tests pass. Would you like to create an issue for swapping?

@nsoranzo
Copy link
Member

@martenson Why is that needed for 16.07?

@martenson
Copy link
Member

@nsoranzo I do not think it is needed, but given we have a working fix (this PR) and that the fix you mentioned would supersede this I am just saying that we don't have time to wait for it.

@martenson martenson merged commit 9607e52 into galaxyproject:dev Jul 26, 2016
@nsoranzo nsoranzo mentioned this pull request Jul 26, 2016
14 tasks
mvdbeek added a commit to bxlab/galaxy-hackathon that referenced this pull request Jul 26, 2016
@nsoranzo nsoranzo deleted the pyparsing_testing branch February 27, 2020 16:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants