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

Consider adding a constraint for the dependency towards python-intervals #4

Closed
AlexandreDecan opened this issue Feb 28, 2020 · 3 comments
Labels
dependency Issue related to other api we use

Comments

@AlexandreDecan
Copy link

Hello,

I see that you're relying on python-intervals. I suggest to add a dependency constraint (e.g. <2.0.0) since version 2.0.0 will be released soon, and contains backward incompatible changes (e.g. .is_empty() method will be replaced by .empty property).

@AlexandreDecan
Copy link
Author

The newer 2.0.0 version was released today, but should not break your code since it has been released with a new package name (portion has replaced python-intervals).

@andrewhabib
Copy link
Contributor

Hi Alexandre,

Thank you for pointing out the migration to the new package name... I am glad this did not affect our project here.
I will look into migrating to the new library. But thanks for a nice and handy project!

@AlexandreDecan
Copy link
Author

Hi,

You're welcome. I'm glad to see my library being used by other people ;-)
Feel free to contact me if you have questions or need help when migrating to portion!

@andrewhabib andrewhabib added the dependency Issue related to other api we use label Jun 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependency Issue related to other api we use
Projects
None yet
Development

No branches or pull requests

2 participants