4 ms·
Ok, yeah, maybe mercurial's case was special, but still, this seems like they made it harder on themselves needlessly. > One was that the added b characters wo
by raverbashing 7y ago
Ok, yeah, maybe mercurial's case was special, but still, this seems like they made it harder on themselves needlessly.
> One was that the added b characters would cause a lot of lines to grow beyond our length limits and we'd have to reformat code
ORLY?! Well, guess what: hard line size limits are stupid. Now you know why.
That's why "foolish consistency is the hobgoblin of little minds" is one of the 1st phrases of PEP-8.
But I'm tired of people saying "oooh let's cut all lines to be under 80-characters" like it's some kind of Biblical Mandate. No, it isn't. And the 80 chars limit is BS. Probably the part I hate the most about PEP-8 (and especially how people interpret the PEP-8)
> is its insistence that the world is Unicode
Oh please. Yes, the world is Unicode. Get over it. Maybe not bytes on disk/network. But apart from that? Yes. If libraries take bytes or unicodes I can agree it's a thorny issue, but let's move on because a happy day is a day where I don't get an UnicodeDecodeError because Python2, to add insult to the injury thinks the world is not only not Unicode, but it's all ASCII.
Windows made the right call a long time ago when it decided to make all strings Unicode. Ok, maybe UTF-8 would be better than 16, but it still does the job.
But I have to agree with them that any version < Py3.4 or 3.5 was really not worth it.
- yjftsjthsd-h 7y ago> the world is Unicode. Get over it. Maybe not bytes on disk/network. But apart from that? Yes So, just ignoring the 2 things that a version control system exists to work with directly?
- raverbashing 7y agoYou're ignoring the parts where they have several hardcoded byte/unicode strings. Otherwise just convert to and from when saving and sending it to network