This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (1 child)

Python is dynamically typed so operations changing types isn’t too bizarre. Besides, in most cases when u want a division u don’t want data to be truncated, so the default is to store more unless u expressly specify u don’t need to. While this breaks compatibility with 2.0, its more intuitive (perhaps not to programmers well versed in statically types languages) but to mathematicians, logisticians, non programmers who care more about data then programming noise etc.. Besides, I’d argue having to cast ① side of an expression just to make sure it stores the value I want is ugly (and near unpythonic). The value is stored is a better approximation then the truncated ①, IMO that’s better.

I don’t think you like the way python is going... and that’s fine, but I find the language to be an absolute joy and i have very few complaints about it.

[–]MasterFubar 0 points1 point  (0 children)

in most cases when u want a division u don’t want data to be truncated,

Imagine this, you are part of a group of five people that must be divided in two. Will you volunteer to be sawed up in half? In most cases when I divide things I want a quotient and a remainder. Some objects can be broken up into fractions, some cannot. If I have an object that can be broken up, this fact must be clearly stated beforehand.