3 ms·
The author does touch on that. When Mercurial accepts a 3rd party package, downstream packagers like Debian get all hot and bothered and end up making question
by lacker 7y ago
The author does touch on that.
When Mercurial accepts a 3rd party package, downstream packagers like Debian get all hot and bothered and end up making questionable patches to our source code.
Some environments just can't use dependencies like this. IMO Python 3 was too much of a breaking change, and in particular, the ability to transition from 2 to 3 should have been better in Python itself.
- j88439h84 7y agoSix, for example, is designed to be a single file -- specifically to ease copying it directly into the code base. But the idea that Mercurial couldn't use dependencies because of fear for what Debian might do...I find it so hard to believe that's the best choice. Vendor if you must, but do not reinvent the wheel.
- masklinn 7y agoHaving done so, six really is not necessary for a transition. We went with forking werkzeug's minimalist compat file because six was waaay overkill, and that made it easier to progressively rip it out later. python-future is invaluable for the fixers (which are way better than 2to3's), the runtime stuff you can easily do without.