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

CI breaks on python 2.7.10 #115

Closed
capelastegui opened this issue Feb 26, 2019 · 0 comments
Closed

CI breaks on python 2.7.10 #115

capelastegui opened this issue Feb 26, 2019 · 0 comments

Comments

@capelastegui
Copy link
Contributor

On Travis CI, we are getting an ImportError due to a conflict in the version of the 'six' library, when running on python 2.7.10

ImportError: Failed to import test module: tests.test_forecast_plot
Traceback (most recent call last):
  File "/opt/python/2.7.10/lib/python2.7/unittest/loader.py", line 254, in _find_tests
    module = self._get_module_from_name(name)
  File "/opt/python/2.7.10/lib/python2.7/unittest/loader.py", line 232, in _get_module_from_name
    __import__(name)
  File "tests/test_forecast_plot.py", line 23, in <module>
    from anticipy.utils_test import PandasTest
  File "anticipy/__init__.py", line 2, in <module>
    __version__ = pkg_resources.require(__name__)[0].version
  File "/home/travis/virtualenv/python2.7.10/lib/python2.7/site-packages/pkg_resources/__init__.py", line 900, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/home/travis/virtualenv/python2.7.10/lib/python2.7/site-packages/pkg_resources/__init__.py", line 791, in resolve
    raise VersionConflict(dist, req).with_context(dependent_req)
ContextualVersionConflict: (six 1.10.0 (/home/travis/virtualenv/python2.7.10/lib/python2.7/site-packages), Requirement.parse('six>=1.11.0'), set(['jsonschema']))

six is not a dependency of anticipy. It's probably used by some imported library. Since the code otherwise works fine on python 2.7.15 and 3, I think the best solution is to drop 2.7.10 from the CI script.

capelastegui added a commit that referenced this issue Mar 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant