Dependencies Viktor SDK

🚀 Support (Q&A) 🐛 Bug & Error Reports
1

Lately there are a lot of packages that have new major versions which can’t be installed due to conflicting dependencies with the Viktor SDK:
image

Some of these are:

  • Munch (v4)
  • Pandas (v2.1)

Even though it isn’t a major issue, it would be nice to at least keep the major (possibly minor) versions up to date with a maximum delay of lets say a month or so.

Thanks in advance :wink:

2

Hi Johan, thanks for bringing this up.

The VIKTOR SDK is using very basic functionality of munch and pandas, which I do not expect to change on major upgrades of these packages. This means that we can probably safely remove the upper limit to solve your issue.

Why are we pinning the upper limit? (for the interested reader) The reason for the upper limit in the VIKTOR SDK is to prevent backwards incompatible changes of dependencies breaking existing apps. If the VIKTOR SDK would not pin the major limit, the following could happen:
  • today you are publishing an app, viktor will be installed which uses the latest pandas version as of today (e.g. 2.1.0)
  • next year you are publishing the exact same app, viktor will be installed which uses the latest pandas version of that day (e.g. 4.1.2)

It could be possible that pandas has removed functionality between versions 2.1.0 and 4.1.2 that have been used by the VIKTOR SDK, therefore breaking the app.

3

This has been fixed in SDK v14.6.0! SDK v14.6.0 released 🎉

1 Like