On 07. 05. 20 23:35, Felix Schwarz wrote: Most of the exceptions don't have a deadline set. The one with babel certainly doesn't. We will be happy to have trac ported to Python 3 (it is the last Python 2 app in Fedora designed to be possibly internet facing -- and security of Python 2 will become major PITA), but until that happens, as long as you are happy to keep shipping pytohn2-babel, you can. Depends on you. The exception has this covered. Splitting to a separate component is also possible (in case babel can no longer be updated in single component, etc.). For now. Once this is no longer true, a sepearate component might be the only option (in any case, please don't package two different babel versions from the same spec, but I guess you wouldn't). Also note that as Python 3 moves forward, single code-base will eventually get trickier and trickier. We've managed to postpone the removals of some long deprecated py2 compatibility from Python 3.9 to 3.10, but the message was pretty strong: No more further delays. However, that second thing is more a concern for babel upstream. Either they will manage somehow, or they'll split. When they split, we need to split as well. What crusade are you talking about? I'm just kidding. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok