The link below is suggested in the text msg during the build script as the replacement for depreciated or soon to be jsonschema. My builds seem to finish and the resulting executable installs fine… I just wanted to clean this up if I could
I just can hit on the right syntax on the MSYS2 command line to install this python component…
If anyone has done this with success could you steer me in the right direction…
THank you in advance…
simply don’t update that dependency in your build environment until someone changed the build receipt of darktable …
… if it ain’t broke, don’t fix it
To elaborate a bit, a depreciation warning is a way for developers to tell other developers that the deprecated part will be removed in a future version.
It’s not relevant to end users, and you can safely ignore those warnings unless you are maintaining the code. Like you said, the build finished, and the executable should run fine.
There can be several reasons why deprecated code is still in use. Time constraints are one (a seemingly trivial change at one point can mean hours of work to get the rest of the code to confirm). The possibility to introduce new bugs is another: the code replacing the deprecated part is (evidently) newer, so perhaps not as well tested yet.
@MStraeten @rvietor Thank you for taking the time to comment and clarify…
It’s also worth noting this is nothing MSYS2 specific and the warning is also shown in Linux and macOS build if the python-jsonschema package is more recent.