Right, they could have paid a nontrivial cost (asking devs to use b-strings, pri...

		weberc2 on Jan 13, 2020 \| parent \| context \| favorite \| on: Mercurial’s journey to and reflections on Python 3 Right, they could have paid a nontrivial cost (asking devs to use b-strings, print_function, etc) but didn't by fiat, choosing instead to pay a greater cost during the migration in addition to the nontrivial cost. My comment expresses skepticism about that decision.