It is kind of the same problem as for shared libraries. In the GNU universe the cleanest solution is to have multiple soversions. Transferred to jinja it would

It is kind of the same problem as for shared libraries. In the GNU universe the cleanest solution is to have multiple soversions. Transferred to jinja it would be jinja.so.1 and jinja.so.2. Maintaining fine grained symbol versioning is a pain and a massive amount of work for the package maintainer: https://invisible-island.net/ncurses/ncurses-mapsyms.html https://invisible-island.net/ncurses/ncurses-mapsyms.html Honestly, multiple installed versions like jinja1 and jinja2 sounds best to me.