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

six is fixed at v1.13.0 #65

Closed
sj-curtin opened this issue Jan 21, 2020 · 2 comments
Closed

six is fixed at v1.13.0 #65

sj-curtin opened this issue Jan 21, 2020 · 2 comments
Assignees

Comments

@sj-curtin
Copy link

Describe the bug

To Reproduce
Steps to reproduce the behavior:

  • Have 2 python modules that use six
  • One is dependant >= 1.13.0
  • One is == 1.13.0

Expected behavior
Both Python Modules install fine

Actual behavior
We get a dependency confilct :(

Environment:

  • any
@fedelemantuano
Copy link
Contributor

Hi @sjcurtinibm,
this is a problem on your system and not of mail-parser. You should use virtualenv.
I can upgrade the library, but the best practice is the virtualenv.

fedelemantuano added a commit that referenced this issue Jan 23, 2020
@seanthegeek
Copy link

@fedelemantuano six is updated often, and other packages have different version requirements. Setting a static version causes conflicts with setup.py requirements in other modules that use slightly newer or older versions of six, even if you use pip in a virtualenv. I agree with @sjcurtinibm , six should really be set at six>=1.12.0 to be more friendly to other dependencies in the same virtualenv.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants