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

Update six version requirement to >= 1.10, < 2.0 #279

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

DanielSwain
Copy link

Current version of six is 1.12. Being conservative by keeping less than 2.0.

@jpweytjens jpweytjens closed this Jul 16, 2019
@jpweytjens
Copy link
Contributor

Closed by #292.

@mikebridge
Copy link

@jpweytjens #292 pins six to 1.12 rather than making it >= 1.12 and < 2.0 as proposed here. Are there any known issues with using newer versions? Is it feasible to switch to a range?

@ellr
Copy link

ellr commented Oct 26, 2020

@jpweytjens #292 pins six to 1.12 rather than making it >= 1.12 and < 2.0 as proposed here. Are there any known issues with using newer versions? Is it feasible to switch to a range?

I'm interested in that as well. I'm not familiar with six, but if we could allow later releases (like >= 1.14) as well would help a lot. I would welcome to switch to the range mentioned by @mikebridge rather tan pinning it to a fixed version, if this is feasilbe.

@vladox
Copy link

vladox commented Sep 16, 2021

@jpweytjens This is still an issue today is conflicting with newer versions of other packages

@jpweytjens
Copy link
Contributor

@traverseda What's your opinion? I've heard arguments both ways with respect to pinning fixed versions, setting a range or keeping a dependency up to date.

@jpweytjens jpweytjens reopened this Sep 16, 2021
@makretch
Copy link

Any updates on whether or not it's possible to use a later release of six?

@kxrob
Copy link

kxrob commented Mar 12, 2022

These outdated fixed version dependencies really mess up installations and cause conflicts unnecessarily in an unparalleled manner - hardly seen elsewhere.
Better use >= or nothing (and < only by exception WHEN concrete knowledge of problems which cannot be fixed easily.)

@deanmalmgren
Copy link
Owner

deanmalmgren commented Mar 12, 2022 via email

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

Successfully merging this pull request may close these issues.

None yet

8 participants