Consider adding a constraint for the dependency towards python-intervals
AlexandreDecan opened this issue · 3 comments
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).
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).
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!
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!