Remove all traces of Python 2

[JeanChristopheMorinPerso]

Support for Python 2 was removed in 3.0.0, but we left some leftovers. This issue lists what's left to be done to really remove all traces of Python 2 from the codebase.

Tasks

Preview Give feedback

1. Remove rez.backport
2. Remove rez.utils.py23 #1646
   difficulty/easy enhancement help wanted +3
3. Replace usages of rez.vendor.enum with the built-in enum module #1648
   difficulty/easy enhancement help wanted +3
4. Replace rez.utils.data_utils.cached_property with functools.cached_property #1637
   difficulty/hard enhancement help wanted +3
5. Remove/replace all deprecated (python 2) magic methods (__<method>__) #1833
   devdays24 difficulty/easy enhancement help wanted +4
6. Remove from __future__ import print_function from the code base #1636
   difficulty/easy enhancement help wanted +3
7. Look at PRs/commits that added support for Python 3 and see if we missed anything
8. Run https://github.com/asottile/pyupgrade

If you want to start working on one of these task and it's not yet converted to an issue, please comment in the issue and we will happily create an issue.

List of Python 2 to 3 PRs

Note that there is a lot of noise in these PRs. But they can be used to see what kind of compatibility layers were added to support both python 2 and 3. This will be handy to determine if something should be removed.

• py3 iterators conversion #736
• address py3.8 deprecation of collections direct ABC access #740
• py3 finalizations #742
• address #744 (rex dictmixin issue) #745
• use subprocess in 'text' mode in most cases #753
• revert progress iteration and update vendored #766
• bytecode / pycache related changes #733
• -robust py2/3 use of getargspec/getfullargspec #743
• modernize function manipulations and attrs #727
• add __bool__ operator #755
• make Version properly iterable in py3 #725
• .next() to next() #713
• very small py3 compat changes #712
• miscellanous atomic nonaffective py2/py3 compatibilities #710

[hww-nikhilshankarnoble]

@JeanChristopheMorinPerso has anyone picked up the removal of rez.utils.py23 task yet? I was looking for a straightforward task to kickstart hopefully contributing to Rez more in the future, and would like to pick it up if not :)

[JeanChristopheMorinPerso]

@hww-nikhilshankarnoble I don't think so. I have created #1646 if you want to work on it.

[lbreede]

@JeanChristopheMorinPerso has anyone tackled these magic methods yet?

Remove/replace all deprecated (python 2) magic methods ()

I may look into that as part of the Dev Days 2024.

[JeanChristopheMorinPerso]

Hi @lbreede . I don't think anyone did that. Feel free to give it a try. But note that rez is not participating to the dez days and as such we might not be able to review your contributions in time. We still appreciate all contributions, so please do contribute if you can. We might be slow to review though.

[lbreede]

@JeanChristopheMorinPerso, I may just tackle it regardless. Is there an issue for this specific task yet?

[JeanChristopheMorinPerso]

@lbreede I just created #1833.