4 ms·

If you write new software in Python 3, why does it matter if division changed?

• geocar 10y ago
  First, it presupposes I'm going to write new software in Python 3 rather than justifying why I should write new software in python 3. Second, it matters because I'm thinking about python4 and python5. I've already been through this and got burned moving from python1.5 to python2, and python3 has been very uncomfortable thus far. Thirdly, it matters because I work in a lot of mature (multi-decade) codebases, and figuring out what division is supposed to mean twenty five years into development is disconcerting. Then when I'm simply not convinced python is a good investment anymore, this quippy attitude here is extremely off-putting. Do you really want to know why I don't like python as much as I used to? Or are you trying to justify your decision to further invest?
  • minitech 10y ago
    > First, it presupposes I'm going to write new software in Python 3 rather than justifying why I should write new software in python 3. It does, because that’s what you were responding to: > I believe the path being suggested is: write new software in Python 3, or at least in a 3-friendly way. I assumed your list was a list of reasons not to write new software in Python 3, and found division oddly out of place.
    • geocar 10y ago
      > It does, because that’s what you were responding to: I believe the path being suggested is: write new software in Python 3, or at least in a 3-friendly way. You're mistaken. Start at the top of the thread again[1]. The question is whether I (or anyone else) should even bother with Python3. [1]: https://news.ycombinator.com/item?id=13061570 https://news.ycombinator.com/item?id=13061570