Open HoussemNasri opened 7 months ago
hmm.. in my opinion setup.py should be updated to remove python2.7 - it hit EOL long time ago so there is no reason to be worried about backward compatibility with already obsolete version.
hmm.. in my opinion setup.py should be updated to remove python2.7 - it hit EOL long time ago so there is no reason to be worried about backward compatibility with already obsolete version.
It would certainly make supporting the library a bit easier.
So Let's drop python 2, as I see stats goes down
Python 2.7 is listed in the trove classifiers, but using the library in a Python 2 project yields errors due to the usage of f-strings.
https://github.com/atlassian-api/atlassian-python-api/blob/8f7e4e368fcff54d8566746955aacec9cbad2b24/setup.py#L49
This is the error:
I ran
python -m compileall .
using python2.7 and got the following result. It suggests that there has been 3 occasions where backward compatibility was broken. Do you think we can change these 3 cases to maintain python2.7 compatibility in upstream or you want to keep using python 3?