News for hackers. Stuff that matters.
Re:Python 3 makes it easier to develop high-quality software by upofadown on Wednesday November 18, 2015 @11:35AM (#10588746)
You missed a whole subclass of people. Those that don't like Python3. Personally I believe Python3 took a wrong turn with the approach of converting everything to UTF-32 and making a big deal about the philosophical difference between "strings" and "bytes". I very much suspect the future will be something like how Julia deals with the issue, where UTF-8 can be just left as UTF-8.
Re:Python 3 makes it easier to develop high-quality software by mangecoeur on Wednesday November 18, 2015 @12:14PM (#10589071)
Apparently you don't deal with much non-ascii data if you don't like python3's string handling. It's literally the reason I first upgraded, because reading in simple text data on Python2 can break completely. Seeing as literally no language on earth can be written entirely in ascii characters (since even English text can contain words with accents or old fashioned things like the long s ſ) this is a pretty big issue.

Yes it is possibly to laboriously add code to check and encode/decode text, that might sometime be text and sometimes binary pretending to be text pretending to be binary. But why go through that pain when you could just use Python3 where things are clear and generally actually work.

Re:Python 3 makes it easier to develop high-quality software by eeZi on Wednesday November 18, 2015 @12:30PM (#10589216)
I fully agree. Python 3 makes life much, much easier with non-ASCII languages and prevents the annoying Unicode conversion bugs you see in most Python 2 code bases.

It's also very intuitive, which is great for teaching - I've always had a hard time explaining the difference between "strings" and "unicode" objects in Python 2, but the clear boundary makes it straight-forward in Python 3.

Re:Python 3 makes it easier to develop high-quality software by takeda on Wednesday November 18, 2015 @05:13PM (#10591158)
This is also significant reason why people have problem when migrating py2 code to py3. The code is actually buggy and mixes strings with bytes. Once they run it in Py3 all of the bugs show up because Py3 is stricter about it.

For the same reason if you need to write code that should work on Py2 and Py3, it's much easier to write it on Py3 and then add backward compatibility through "from __future__ import ..." and the six module.

Re:Python 3 makes it easier to develop high-quality software by eeZi on Friday November 20, 2015 @04:51PM (#10604110)
I've heard lots of good things about this project, by the way: http://python-future.org/

It's much less clunky than six. Instead of manually adding the compatibility layers to your code, it automates the process, which results in cleaner code. It can even translate (some) Python 2 modules on-the-fly.

Many projects switched to it from six.

Re:Python 3 makes it easier to develop high-quality software by SeanDav on Wednesday November 18, 2015 @03:19PM (#10590438)
Not always straight forward in Python 3. Try explaining to your class how to ignore case in string comparisons.
Re:Python 3 makes it easier to develop high-quality software by squeaky-clean on Wednesday November 18, 2015 @05:20PM (#10591193)
>Try explaining to your class how to ignore case in string comparisons

Okay: You can't. You'll need to convert both strings to the same case, and then compare those. In the majority of cases, you can do:

return string_a.lower() == string_b.lower()

But sometimes that won't work, because converting case isn't always easy. And that's a unicode issue, not a python issue. It's not even completely a unicode issue, just a "writing can be very weird" issue.

For example, "ß" (U+00DF) is a character that doesn't/shouldn't have an uppercase form. Unicode does support it as U+1E9E, but all the examples I know of will convert it to "SS" ([U+0053, U+0053]) instead.

Try this in a javascript console, for example.

  > "ß".toUpperCase().toLowerCase() === "ß".toLowerCase()
  false
  > "ß".toUpperCase() === "SS".toUpperCase()
  true
  > "ß".toLowerCase() === "SS".toLowerCase()
  false
  > "ß".length
  1
  > "ß".toLowerCase().length
  1
  > "ß".toUpperCase().length
  2
  > "ß".toUpperCase().toLowerCase()
  "ss"
Also, try ctrl+f'ing for "ss" on the Wiki page for ß [0] and see what it matches. Or ctrl+f this page for "ß" and it will match every "ss". I think it's pretty neat.

[0] https://en.wikipedia.org/wiki/%C3%9F

(edit: You might already know everything in this comment, but I started writing and it ended up being a cool exercise for myself, so I figured I'd submit).

Re:Python 3 makes it easier to develop high-quality software by mangecoeur on Thursday November 19, 2015 @05:05AM (#10593856)
> "writing can be very weird"

Absolutely! I think there's a lot of baggage in computing because it happened to emerge in places where language could mostly be written in simple characters with surprisingly simple rules. When exported internationally suddenly you deal with "oddities" that are really rather the norm in other languages.

In French for example is customary NOT to put accents on capital letters, even though it's possible. But then again sometime people do it anyway - it's not a hard rule. So often converting to lowercase may require contextual understanding because some words are written the same but with different accents, and would capitalize to the same string. Which word was meant would only be evident from the context of the sentence.

I suspect that if computing had rather developed somewhere where these things were commonplace we would have much better handling of it today.

Re:Python 3 makes it easier to develop high-quality software by throw_away on Thursday November 19, 2015 @01:10AM (#10593033)
Interesting that the "ss" search only works on safari and chrome, but not on firefox (which happens to be the only browser that lets you easily toggle case-matching AFAICT). I presume this means that the first two went with a toUpperCase() approach while FF went with toLowerCase(). I wonder which choice is better in the face of unicode type oddities like this one.
Re:Python 3 makes it easier to develop high-quality software by zo1 on Wednesday November 18, 2015 @03:34PM (#10590556)
That depends on the type of strings you are comparing. If you include the full Unicode set, you're going to run in to huge troubles in probably all languages simply due to the nature of the Unicode character set, rather than the specific language's handling of strings and Unicode code points.

But, personally, if you're teaching Python to a class, whether it's 2.x or 3.x. You should probably stick to using some variation of string.upper() == string.upper() to explain simple comparisons, due to simplicity.

Re:Python 3 makes it easier to develop high-quality software by c-oreills on Thursday November 19, 2015 @08:14AM (#10594529)
This is exactly what str.casefold is for: https://docs.python.org/3/library/stdtypes.html#str.casefold
Re:Python 3 makes it easier to develop high-quality software by SeanDav on Saturday November 21, 2015 @02:28PM (#10607732)
casefold is only part of the story and by itself does not supply a complete solution.
Re:Python 3 makes it easier to develop high-quality software by c-oreills on Monday November 23, 2015 @09:54AM (#10614866)
Could you expand on where it falls short? I'm interested, having not yet relied on it heavily.
Re:Python 3 makes it easier to develop high-quality software by krick on Wednesday November 18, 2015 @01:37PM (#10589756)
I would suspect that you don't deal with much non-ascii data if you like python3's string handling. In Python 2 you have control over encodings. You can work with unicode-strings internally, but you receive and produce bytes, which is actually the only truth in the computer world. Everything else is a lie. It would be nice to pretend that there's only 1 encoding in the world and that encoding is roughly equivalent to unicode itself, but this isn't true. World doesn't work on UTF-8. By abstracting encodings Python 3 obscures what's actually happening.
Re:Python 3 makes it easier to develop high-quality software by zo1 on Wednesday November 18, 2015 @03:38PM (#10590581)
Not at all, it forces you to unify to storing character data as Unicode code-points. Eventually if you go down far enough, you're reading the raw bytes you speak of from some sort of external system/file/DB. It's at that point that you define your encoding, and never worry about it every again. Except for when you touch those external systems/files again, again with full knowledge about what encoding is required.

Either way, if you're not dealing with differently encoded character data in Python 2.x as noted above, you're causing yourself some unnecessary headaches.

Re:Python 3 makes it easier to develop high-quality software by takeda on Wednesday November 18, 2015 @05:51PM (#10591343)
Something tells me you did not experience the pre-unicode world around 90s. I did, and I didn't like it. I prefer it is abstracted from me thankyouverymuch.

But seriously, all what python (and as a matter of the fact majority of languages) is placing a clear distinction between a byte and a character. This forces developers to keep in mind what they are dealing with and reduces number of bugs.

The truth is that if you treat everything as bytes, chances are that your program has bugs. Actually good test is to convert your existing Py2 code to Py3, if you have encoding/decoding errors then your code was buggy.

Re:Python 3 makes it easier to develop high-quality software by Avernar on Thursday November 19, 2015 @02:13AM (#10593229)
> But seriously, all what python (and as a matter of the fact majority of languages) is placing a clear distinction between a byte and a character.

No, they make a clear distinction between bytes and code points. This is the wrong approach as code points are not characters. People are going to think that everything is fine now that they're using code points and the unicode type when they should be using a unicode library for text manipulation.

Re:Python 3 makes it easier to develop high-quality software by vetinari on Wednesday November 18, 2015 @05:10PM (#10591145)
In Python2, I couldn't just print the string I just read from file - such were the joys of Windows console, which has different encoding than the rest of the system (cp85x in console, cp125x in filesystem & gui)...

Compared to that, Python3 was like gift from heaven.

Re:Python 3 makes it easier to develop high-quality software by yepguy on Wednesday November 18, 2015 @12:33PM (#10589235)
Python 3 is okay-ish for developers who don't think about encodings unless forced to, but it actually makes it more difficult to do "the right thing":

http://lucumr.pocoo.org/2014/5/12/everything-about-unicode/

Re:Python 3 makes it easier to develop high-quality software by vetinari on Wednesday November 18, 2015 @05:17PM (#10591178)
Having to thing about encoding all the time, without being forced to, brings in a lot of unwanted accidental complexity.

Did you know, that there is an operating system, where a simple loop that reads lines from file and prints them to the console will end up with errors? (that being Windows and some European code pages, where console is cp85x, filesystem read and write cp125x).

Re:Python 3 makes it easier to develop high-quality software by mark-r on Wednesday November 18, 2015 @06:21PM (#10591486)
The accidental complexity here is due to Windows, not Python. Python would rather generate an error than give you garbled output without your knowledge.
Re:Python 3 makes it easier to develop high-quality software by vetinari on Thursday November 19, 2015 @02:45AM (#10593335)
Most developers are not aware of that and write code, that just bombs out for the user. The user would prefer at least garbled text instead of exception, because he is used to that anyway in other apps. He has at least some result, instead of stack trace.

Well, and that's before the user tries to redirect stdout to file, in which case it will end up with error too, because that is going to be 7-bit ascii.

Anyway, Python3 does the right thing with defining the encoding at the edges and everything works right for the user out of the box.

Re:Python 3 makes it easier to develop high-quality software by maxerickson on Wednesday November 18, 2015 @11:46AM (#10588854)
Recent versions only convert to UTF-32 when a wide character is present (they also use 2 byte characters when that is sufficient):

https://docs.python.org/3.3/whatsnew/3.3.html#pep-393-flexib...

Glancing at Julia, I'm not sure "invalid character index" is really a great thing to have to handle when dealing with text. It does seem that systems for dealing with text will eventually offer various apis beyond just a somewhat disfunctional character api (which I think is a fair description of str in Python 3).

Re:Python 3 makes it easier to develop high-quality software by Avernar on Wednesday November 18, 2015 @03:25PM (#10590483)
> Recent versions only convert to UTF-32 when a wide character is present

It's non-BMP characters that trigger the conversion to 4 bytes per codepoint. Unfortunately Emoji are non-BMP and are super common.

Re:Python 3 makes it easier to develop high-quality software by rspeer on Wednesday November 18, 2015 @04:35PM (#10590916)
If you're dealing with emoji -- and yes, they are incredibly common -- you'd better not use any Python before 3.3.

Non-BMP characters in 2.x-3.2 give you implementation-specific behavior. It can vary from one system to the next. Some string methods fail on "narrow builds" of Python (the ones that store their characters in UCS-2), while others return different results than they would on a "wide build".

Re:Python 3 makes it easier to develop high-quality software by Avernar on Wednesday November 18, 2015 @04:48PM (#10591008)
Not an issue because I don't use the Unicode type. All my data comes in as UTF-8 on which I do a quick validation check. Then it's just handled as bytes all the way to and from my database.
Re:Python 3 makes it easier to develop high-quality software by rspeer on Thursday November 19, 2015 @03:04AM (#10593397)
Sure, that is an option that's always available. You don't have to worry if Python's string methods are wrong if you're opting not to use them.
Re:Python 3 makes it easier to develop high-quality software by upofadown on Wednesday November 18, 2015 @11:55AM (#10588919)
>Recent versions only convert to UTF-32 when a wide character is present (they also use 2 byte characters when that is sufficient) ...

I happen to know this fact. Are you really asking that everyone that comments on a language acknowledge all the possible implementation details? I at no point complained about the memory required to hold strings in CPython so I can't really understand why you would bring this up.

Re:Python 3 makes it easier to develop high-quality software by maxerickson on Wednesday November 18, 2015 @12:00PM (#10588963)
Because someone else reading "converting everything to UTF-32" might not be aware of the nuance. That's all.
Re:Python 3 makes it easier to develop high-quality software by teach on Wednesday November 18, 2015 @12:24PM (#10589174)
I'm a casual user of Python 2, and I certainly didn't know this, so I appreciated the clarification.
Re:Python 3 makes it easier to develop high-quality software by upofadown on Wednesday November 18, 2015 @05:56PM (#10591363)
Sorry for the snark but this has become a trigger for me. Every time anyone disagrees with the way Py3 does Unicode someone will immediately assume that that person is just confused about the implementation.
Re:Python 3 makes it easier to develop high-quality software by Avernar on Wednesday November 18, 2015 @03:19PM (#10590435)
I agree. Everything is so much simpler when you use UTF-8 everywhere. Being effectively forced to use the ASCII/UCS2/UCS4 unicode type in Python3 is the only thing that has kept me from switching to it.
Re:Python 3 makes it easier to develop high-quality software by 1st1 on Wednesday November 18, 2015 @04:15PM (#10590807)
The only thing you are forced to think about is whether you're working with strings or with bytes. Unicode is handled transparently (but you do need to know the encoding when you're decoding bytes). How it's stored internally is none of your concern.
Re:Python 3 makes it easier to develop high-quality software by Avernar on Wednesday November 18, 2015 @04:32PM (#10590903)
Yes it is. Every conversion to and from the unicode type and every expansion of the unicode type from 1 to 2 to 4 bytes eats up processor time, cache/memory bandwidth and puts more pressure on the garbage collector.

And I don't want to be forced to distinguish between strings and bytes. To me they are one and the same as I use UTF-8 for everything. Not once in my code do I need to encode/decode anything.

Re:Python 3 makes it easier to develop high-quality software by Avernar on Thursday November 19, 2015 @01:26AM (#10593089)
Nice, down voted for someone not agreeing with me. I'd rather know what you though was wrong with what I wrote.

I've always wanted to know how things are done internally. Makes me a better programmer. What I said about all this extra conversion does to performance is correct, especially when scaling up.

And my choice to use UTF-8 internally is a valid way to do things. I make sure that what comes in from the outside world is UTF-8 (either by rejecting or converting) and then don't have to worry about it from that point on. The bulk of my code deals with outbound data so no need for me to do any encoding as it's already UTF-8.

Re:Python 3 makes it easier to develop high-quality software by mark-r on Wednesday November 18, 2015 @06:17PM (#10591459)
Most of us aren't so lucky. I really do wish we lived in a 100% UTF-8 world. But even if we did, I don't see how e.g. regular expressions would work.
Re:Python 3 makes it easier to develop high-quality software by Avernar on Thursday November 19, 2015 @01:13AM (#10593044)
The world seems to be headed to UTF-8 for everything. That's why having Python3 force us away from it doesn't make sense to me.

As for regular expressions, they work perfectly if your delimiters are in the ASCII range. If you're trying to match a single character then they don't work for Unicode even when using Python3's unicode type. The reason is that code points are not characters.

Re:Python 3 makes it easier to develop high-quality software by 1st1 on Thursday November 19, 2015 @10:13AM (#10595173)
UTF-8 is just an encoding. Unicode is a more general term. Python 3 allows you to convert bytes to unicode from any encoding, including utf-8 (which is default). Using utf-8 as the internal unicode representation is flawed too - index and length operations are slow.

For regexes, \w matches any unicode word character (unless ASCII mode is on), just use it on strings. If you use it on bytes, then yes, you can only match bytes.

Re:Python 3 makes it easier to develop high-quality software by Avernar on Thursday November 19, 2015 @01:35PM (#10596570)
> Using utf-8 as the internal unicode representation is flawed too - index and length operations are slow.

And this perfectly illustrates what I posted in another comment elsewhere. Thinking that doing operations on code points (indexing and length) is the proper thing to do. You need to use a unicode library to work on graphemes and take into account grapheme clusters.

> For regexes, \w matches any unicode word character

From what I've read, \w just matches code points. I did find that the https://pypi.python.org/pypi/regex module supports \X which matches graphemes as per the unicode spec http://www.unicode.org/reports/tr29/.