Python package refresh for version 1.0

Issue #959 resolved
David Platten created an issue

Make sure latest version of packages are being used.

Make the version range suitable for python 3.8 to 3.11

Comments (7)

  1. David Platten reporter

    Updated python packages to their latest versions using a fresh installation of python 3.11 with no restrictions on python package versions except for Django. Checked that OpenREM works (it does). Then fixed the package versions and checked that this worked with a fresh installation of python 3.8 - it does. Updated plotly JavaScript file to match the python package. Also added a little code to suppress the future warning for two bits of chart code. Refs issue #959

    → <<cset e32398d6e8ba>>

  2. Ed McDonagh

    Created docker image with this branch, created new install, worked. Time for a PR @David Platten ?

  3. Ed McDonagh

    I’ve now also updated an old test install of a linux to docker upgrade/migration with the docker image from this branch, so I’d like to roll it in.

    Do your future warning suppressions need noting or somehow exposing for after this release?

  4. David Platten reporter

    Updated plotly package and associated JavaScript file to latest version. Updated Django minimum requirement to 3.2.16 (the last 3.2 version). Updated matplotlib, numpy, scipy and pandas packages to latest versions. Replaced use of np.float with in-built, identical python float because numpy 1.24 has dropped support for the depreciated np.float (see https://numpy.org/doc/stable/release/1.24.0-notes.html#expired-deprecations). All tests passed on a local system running python 3.10 and python 3.11. Refs issue #959

    → <<cset ac6335f800a2>>

  5. Log in to comment