https://prefect.io logo
Title
b

Brett Naul

07/10/2019, 5:48 PM
hi all, quick dask q: it looks like the maximum allowed version is a bit behind latest, is there a reason for that or is it just an oversight? cf. https://github.com/PrefectHQ/prefect/pull/1181
c

Chris White

07/10/2019, 5:49 PM
no reason in particular - we are just being cautious and haven’t gotten a chance to test / review the changelog
if this is something you need for your work, I’m be happy to prioritize it
b

Brett Naul

07/10/2019, 5:55 PM
it's not critical but I was a bit surprised by the maximum
requirements.txt
versions in general; it basically means that if I want to install prefect, I have to exactly follow all of its package versioning opinions. you can imagine that if all pypi packages did that then you'd pretty quickly reach a state where everything disagrees and you can't install anything 🙃
c

Chris White

07/10/2019, 5:59 PM
That’s fair; we’ve been bitten by major version changes many times already, so it’s something we like to monitor — we definitely make an effort to keep everything up-to-date, and might consider relaxing those upper bounds one day if it becomes an issue for users
b

Brett Naul

07/10/2019, 6:10 PM
that makes sense, it's definitely a tricky balance to strike. only last point is that (for me at least) tight dask integration is the main selling point of prefect, and I think heavy dask users might be especially interested in keeping dask up-to-date as compared to other dependencies
anyway thanks for the quick response!
c

Chris White

07/10/2019, 6:11 PM
yup, that totally makes sense
anytime!
merged 😉 i’m reviewing distributed now and will presumably merge that shortly as well