You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
from atlassian import Bitbucket
File "C:\Python27\lib\site-packages\atlassian\__init__.py", line 5, in<module>
from .confluence import Confluence
File "C:\Python27\lib\site-packages\atlassian\confluence.py", line 1343
r = self._session.get(f"{download_link}")
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?
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.
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.
atlassian-python-api/setup.py
Line 49 in 8f7e4e3
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?The text was updated successfully, but these errors were encountered: