TravisCI fails to push to Pypi due to importlib-metadata 0.18 ContextualVersionConflict

[achantavy]

Hi there, my project has been unable to push to pypi since 11/11 due to a ContextualVersionConflict.

As seen in lyft/cartography#460, my CI build (https://travis-ci.org/github/lyft/cartography/builds/743003897) fails with this message:

Writing cartography-0.29.0/setup.cfg
creating dist
Creating tar archive
removing 'cartography-0.29.0' (and everything under it)
Traceback (most recent call last):
  File "/home/travis/virtualenv/python3.6.7/bin/twine", line 8, in <module>
    sys.exit(main())
  File "/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages/twine/__main__.py", line 28, in main
    result = cli.dispatch(sys.argv[1:])
  File "/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages/twine/cli.py", line 80, in dispatch
    main = registered_commands[args.command].load()
  File "/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2446, in load
    self.require(*args, **kwargs)
  File "/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2469, in require
    items = working_set.resolve(reqs, env, installer, extras=self.extras)
  File "/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages/pkg_resources/__init__.py", line 775, in resolve
    raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (importlib-metadata 0.18 (/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages), Requirement.parse('importlib-metadata>=1; python_version < "3.8"'), {'keyring'})

Please also see:

• Related forum thread: https://travis-ci.community/t/cant-deploy-to-pypi-anymore-pkg-resources-contextualversionconflict-importlib-metadata-0-18/10494

• Proposed fix from that forum thread: Fix Pip not updating outdated dependency if it's preinstalled #1221

• Another affected issue: Travis pypi deploy failure beer-garden/beer-garden#742

[stale]

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues