2 ms·

Wouldn't occur in this case, as the script starts with: #!/usr/bin/env python2

• Dylan16807 7y ago
  You're arguing against something I never said. Yes, this file, completely in isolation, has no problem. But people want to different pieces of python code together. If one or the other only works with a specific version, it becomes a problem when you try to combine them. Therefore, best practice is to get everyone on the same version. We want to stop having to ask which version everything is, and facing the disappointment when things can't go in the same program. We want to get back to the situation where it's just 'hammer', and that's good enough for 95% of people.
  • kick 7y ago
    ...use the hammer that didn't arbitrarily break compatibility, then? (Note that the original analogy pointed out that they couldn't be mixed, anyway: "or even take advantage of the nails you've hit!") This is like complaining that the well is poisoned when you're the one who put arsenic in it. This also isn't even an open source project, so it's not like you can mix and match anyway.
    • Dylan16807 7y ago
      I didn't make python 3, and "stick on python 2 forever" doesn't seem like the solution here as far as I can tell. > This also isn't even an open source project, so it's not like you can mix and match anyway. Again focusing on the execution of one specific project, as-is, is beside the point of "get everyone on the same hammer".
      • kick 7y ago
        I didn't make python 3 No, but you're complaining about a person using Python 2, the one that didn't arbitrarily break compatibility, while promoting the use of Python 3 because not being compatible is bad. Again focusing on the execution of one specific project, as-is, is beside the point of "get everyone on the same hammer". I agree with this.