Closed VanamalaNarasimhaBhargav closed 6 months ago
nagarwal01
commented
6 months ago @VanamalaNarasimhaBhargav after changing python version, how do we verify if things are still working, if the semaphore job passes, is that enough?
asking because when we change the version, it may require changes in requirements.txt as well to fix dependent modules versions.
sonarqube-confluent[bot]
commented
6 months ago 
0 Bugs
0 Vulnerabilities
0 Code Smells
No coverage information (0.00% Estimated after merge)
No duplication information (0.00% Estimated after merge)Project ID: control-center-images
VanamalaNarasimhaBhargav
commented
6 months ago @VanamalaNarasimhaBhargav after changing python version, how do we verify if things are still working, if the semaphore job passes, is that enough?
asking because when we change the version, it may require changes in requirements.txt as well to fix dependent modules versions.
@nagarwal01 service.yml file was recently added by me(commit history) and the reason I choose 2.7 was as per setup.py supported python_version is >= 2.7 .
Error specified above means semaphore can't use python 2.7 to run this package due to its own configuration (check build the build failure to get more clarity) but the control-center-images repo still supports >=2.7. So changing the version that semaphore uses to 3.7
Service Bot updates are failing due to python version related issue so updating python version to latest.
CMD: sem-version python 2.7[2024-05-22T07:42:25+00:00]: specified version of Python is end of life. Must be >= 3.7. If you think you received this message in error and you are a Confluent employee, see https://go/semaphore-support. Otherwise, contact the maintainer of the Semaphore project.Corresponding Build: https://semaphore.ci.confluent.io/jobs/3eb4ccc8-9cf2-4c22-b3d7-6bfddf87c3e8