By updating to a later released version of pluginbase (one of our Python dependencies) I was able to fix a DeprecationWarning we were seeing when running the test suite.
However, when I came to update this dependency, I wasn't sure how I should go about it. So, I read our CONTRIBUTING guidelines which instructs the reader how to update dependencies, which, consequently, updates all Python deps (see !1587).
It seems like this didn't cause any breakages and we've agreed that we could probably do with an update. However, we should discuss and document the policy as to when we update our Python dependencies.
See original issue on GitLab In GitLab by [Gitlab user @jennis] on Sep 9, 2019, 15:04
Summary
By updating to a later released version of pluginbase (one of our Python dependencies) I was able to fix a
DeprecationWarning
we were seeing when running the test suite.However, when I came to update this dependency, I wasn't sure how I should go about it. So, I read our CONTRIBUTING guidelines which instructs the reader how to update dependencies, which, consequently, updates all Python deps (see !1587).
It seems like this didn't cause any breakages and we've agreed that we could probably do with an update. However, we should discuss and document the policy as to when we update our Python dependencies.