Every story and comment from the Hacker News API, in a layout borrowed from 2001.
A comment on Mercurial’s journey to and reflections on Python 3. Parent comment
as a mercurial user i never understood this decision. for instance look at this recent commit: https://www.mercurial-scm.org/repo/hg/rev/b4c82b704180
would anyone disagree with the fact that an error message should be a string?
a source transformer to add b'' all over the place? really?
and i still don't understand why the hg transition had to be more complex than: https://docs.djangoproject.com/en/1.11/topics/python3/
... and of course now this: https://www.mercurial-scm.org/wiki/OxidationPlan
i wonder what does matt mackall think of all these developments?
There are no comments on this comment yet.
as a mercurial user i never understood this decision. for instance look at this recent commit: https://www.mercurial-scm.org/repo/hg/rev/b4c82b704180
would anyone disagree with the fact that an error message should be a string?
a source transformer to add b'' all over the place? really?
and i still don't understand why the hg transition had to be more complex than: https://docs.djangoproject.com/en/1.11/topics/python3/
... and of course now this: https://www.mercurial-scm.org/wiki/OxidationPlan
i wonder what does matt mackall think of all these developments?