Dsegog 369 migrate to python 3.11

[moonraker595]

The dev server currently uses Rocky 8 with the API running Python 3.8.

Migrating the dev server to Rocky 9 means updating to Python 3.9 as it doesn’t come with 3.8.

We might as well migrate the code base and associated setup to Python 3.11 to save doing it later.

This PR makes the necessary code changes to get the API running, and tested on 3.11.

The main issue has been getting the tests to run given a newer version of matplotlib, which includes some aliases. These have been excluded from the test as they are the same as the existing ones.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.67%. Comparing base (8ba1a40) to head (d465310).
Report is 21 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff            @@
##             main     #147    +/-   ##
========================================
  Coverage   95.67%   95.67%            
========================================
  Files          73       73            
  Lines        3765     3766     +1     
  Branches      387      659   +272     
========================================
+ Hits         3602     3603     +1     
  Misses        113      113            
  Partials       50       50            

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[kevinphippsstfc]

Just doing a search for 3.8 across the repo I found that there is a reference to 3.8, 3.9, 3.10 in the docs/github_actions.md file so that paragraph could do with updating as we do not have that complication any more.

[moonraker595]

Hi, I appreciate the heads-up on this. I encountered this late last night and didn’t realise this was the issue. From: patrick-austin ***@***.***> Date: Monday, 27 January 2025 at 17:04 To: ral-facilities/operationsgateway-api ***@***.***> Cc: Kemp, Alexander (STFC,RAL,SC) ***@***.***>, Author ***@***.***> Subject: Re: [ral-facilities/operationsgateway-api] Dsegog 369 migrate to python 3.11 (PR #147) @patrick-austin commented on this pull request.

________________________________ In pyproject.toml<#147 (comment)>:

@@ -26,7 +26,7 @@ matplotlib = "^3.5.2"

gunicorn = "^23.0.0" orjson = "^3.10.3" python-dateutil = "^2.8.2"

…

-PyJWT = "2.4.0" +PyJWT = "2.10.1" cryptography = "^43.0.1" python-ldap = "3.4.2" boto3 = "^1.26.97" ⬇️ Suggested change

-boto3 = "^1.26.97" +boto3 = ">=1.26.97,<1.36.0" FYI, I ran into this<boto/boto3#4398> both in this repo and in the FDP work. I think it might be because we're using the CephOS interface, which isn't strictly S3? Regardless of the reason, I can't run ingest locally with v1.36 (which I still had installed from starting on #152<#152> ): $ python ../util/ingest_hdf.py --username backend --password back --path v1.1 Checking if API started API not started yet... API not started yet... API not started yet... API not started yet... API started on http://127.0.0.1:8000 Login as 'backend' to get access token Ingested channel manifest file, ID: 20250127154737 Iterating through v1.1/h5 500 returned ('{"detail":"MissingContentLength when uploading file at ' '\'waveforms/20230606120000/CM-202-CVC-SP.json\'"}') Ingestion of v1.1/h5 complete, time taken: 1.39 seconds API stopped on http://127.0.0.1:8000 $ pip list | grep boto3 boto3 1.36.6 $ poetry install Installing dependencies from lock file Package operations: 0 installs, 18 updates, 0 removals - Downgrading botocore (1.36.6 -> 1.35.67) [...] $ python ../util/ingest_hdf.py --username backend --password back --path v1.1 Checking if API started API not started yet... API not started yet... API not started yet... API not started yet... API started on http://127.0.0.1:8000 Login as 'backend' to get access token Ingested channel manifest file, ID: 20250127155434 Iterating through v1.1/h5 Ingested 2023-06-06T1200.h5, time taken: 7.31 seconds Ingestion of v1.1/h5 complete, time taken: 7.31 seconds API stopped on http://127.0.0.1:8000 Since this change would upgrade us to 1.36.2 (see poetry.lock) I think it would be good to pin the version of boto3 to avoid introducing that failure. — Reply to this email directly, view it on GitHub<#147 (review)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFS6J3JFBX72HEEUUCWYHIT2MZRJLAVCNFSM6AAAAABSSOXBSGVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDKNZWGAZDENZZGA>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[patrick-austin]

Have only reviewed the changes since Kevin's last review (24e0651 onward) and these look fine and address the comments so approving.