3 ms·
This article gets worse with every paragraph: > My code for Python 3.5 won't work with the Python 3.7 installation unless I intentionally port it to 3.7. Prob
by mixmastamyk 8y ago
This article gets worse with every paragraph:
> My code for Python 3.5 won't work with the Python 3.7 installation unless I intentionally port it to 3.7.
Probably not. While I can't guarantee there are zero breaking changes, it is highly unlikely to encounter any from 3.5 to 3.7. Another numerical pair might have been a better example.
The split between 2/3 was an issue, widely known, and in the past. Personally I'm glad some big problems in 2 were fixed, though there was some pain.
> When Perl5 came out, a lot of people just switched to a different programming language that was more stable.
Nope, Perl 5 was incredibly popular. It was 6 and the two decade wait where folks jumped ship.
> And I pity anyone who miscounts spaces and accidentally puts in three spaces instead of four somewhere -- this can take hours to debug and track down.
Nope, it tells you the first line where the indent is wrong.
> imports: then search every file in every directory
Nope, just type import ... If you want to know which file it found, print(module).
....
Others have found the other issues. Most of these are nitpicks from someone who doesn't fully understand or agree with the tradeoffs chosen.
IMHO, the biggest design flaw left in Python is that it is always dynamic and that's what makes it so slow.
Why too dynamic? Well, changing types of variables isn't used much in practice. So, to pay a time cost for it on every single line is unnecessary. If types were fixed by default but let you opt in to dynamic when needed, we'd have the best of both worlds. Speedy most of the time, dynamic and slow when actually useful.
Basically whole infrastructures like Cython have been built to correct this.
- a-dub 8y agohah yeah, perl5 was basically perl's renaissance. the web took off and perl was basically used to glue it all together. they did go crazy with perl6 though, and i think a lot of the reason why python took off was because of the hole the perl developers left and google liked python. it seems the performance problems in python can (and are) being fixed. the big downsides i see are the 2to3 mess (which seems like it will be solved with time), weak concurrency support in the default implementation and the lack of the ability to do much real static analysis. makes for great interactive glue though!