| Issue Number | 5325 |
|---|---|
| Summary | Test latest version of python |
| Created | 2024-05-08 11:37:45 |
| Issue Type | Task |
| Submitted By | Osei-Poku, William (NIH/NCI) [C] |
| Assigned To | Kline, Bob (NIH/NCI) [C] |
| Status | In Progress |
| Resolved | |
| Resolution | |
| Path | /home/bkline/backups/jira/ocecdr/issue.438124 |
CBIIT reached out to a couple of CIAT staff about upgrading to the current version of Python to the latest version due to known vulnerabilities in the currently installed version Python 3.11.1150.0. The latest version of Python needs to be tested to make sure it does not break the CDR.
I have begun the testing process on my Windows 10 VM. First obstacle
is that the pywin32 module does not yet work with the
latest version of Python. I have filed a bug report. https://github.com/mhammond/pywin32/issues/2254
Both of the problems reported to
the pywin32 maintainers have been corrected. They have not
yet responded to my inquiries about a timeline for the next release (the
current version was released over a year ago), but build artifacts
incorporating the commits for the bug fixes are available, and I have
successfully installed the latest released version of Python on my
Windows 10 VM, along with a version of the package which works with
Python 3.12.3 and have begun testing. I will coordinate with ~volker to see if/when he might
be available for testing on his Windows 10 VM.
As a reminder, a good resource for testing might be the Excel workbook listing the macros attached to OCECDR-5001.
~oseipokuw Assuming the XMetaL test machine is still in service, would I disrupt anything if I were to try and apply the Python upgrade to it?
I don't think that would affect anyone as far as I can tell. We set up Esther Pak to use it, but I don't know that she connected to it because she never got back to me about helping her to setup remote desktop on her mac.
Possibly related to at least some of the failures we've run into:
Elapsed: 0:00:00.001204