4 ms·

> as easy as a 2.x -> 2.y transition You mean I can just run all my python2 programs with python3 runtime with no changes at all. Because that was how every up

> as easy as a 2.x -> 2.y transition You mean I can just run all my python2 programs with python3 runtime with no changes at all. Because that was how every upgrade before python3 went.

scrollaway 10y ago
Nearly all my code co-runs on 2.7 / 3.6 with almost no hacks. So, yes.
- Chris2048 10y ago
  And your code is all code?
  - scrollaway 10y ago
    https://github.com/jleclanche https://github.com/jleclanche The code that doesn't run on Python 2+3 only runs on Python 3. Have at it.
    - Chris2048 10y ago
      What is your point here?
      - scrollaway 10y ago
        What is yours? You're the one asking.
        Chris2048 10y ago
        Asking what? eikenberry asked: "can just run all my python2 programs with python3 runtime with no changes at all" You replied: "Nearly all my code co-runs on 2.7 / 3.6 with almost no hacks. So, yes.", implying that, yes, you can run py2 programs without change, because this is true of your code To which I replied "And your code is all code?"; Meaning, just because this is true of your code, doesn't mean it is true of eikenberry's code, or any/all code. You then responded with a project that apparently runs fully on py3, but only partially on py2 - what is the point you are making by posting that project?
pekk 10y ago
This is simply not true. For example, Python 2.6 deprecated string exceptions. If you expect in any language to write code and have it run forever, you expect that language never to change.
- cookiecaper 10y ago
  Yep. It's not Python-exclusive either. I can't upgrade to Ruby 2.4 yet because one of my dependencies hasn't been updated. Breaking changes are a routine thing in any maintained language; heck, even a conservative project like GCC breaks code between major releases.
- Chris2048 10y ago
  Were string exceptions deprecated in 2.6 because they don't exist in py3?
  - scrollaway 10y ago
    String exceptions don't exist in py3 because they were deprecated in 2.6.

> as easy as a 2.x -> 2.y transition You mean I can just run all my python2 programs with python3 runtime with no changes at all. Because that was how every upgrade before python3 went.

scrollaway 10y ago

Nearly all my code co-runs on 2.7 / 3.6 with almost no hacks. So, yes.

Chris2048 10y ago
And your code is all code?
- scrollaway 10y ago
  https://github.com/jleclanche https://github.com/jleclanche The code that doesn't run on Python 2+3 only runs on Python 3. Have at it.
  - Chris2048 10y ago
    What is your point here?
    - scrollaway 10y ago
      What is yours? You're the one asking.
      - Chris2048 10y ago
        Asking what? eikenberry asked: "can just run all my python2 programs with python3 runtime with no changes at all" You replied: "Nearly all my code co-runs on 2.7 / 3.6 with almost no hacks. So, yes.", implying that, yes, you can run py2 programs without change, because this is true of your code To which I replied "And your code is all code?"; Meaning, just because this is true of your code, doesn't mean it is true of eikenberry's code, or any/all code. You then responded with a project that apparently runs fully on py3, but only partially on py2 - what is the point you are making by posting that project?

pekk 10y ago

This is simply not true. For example, Python 2.6 deprecated string exceptions. If you expect in any language to write code and have it run forever, you expect that language never to change.

cookiecaper 10y ago
Yep. It's not Python-exclusive either. I can't upgrade to Ruby 2.4 yet because one of my dependencies hasn't been updated. Breaking changes are a routine thing in any maintained language; heck, even a conservative project like GCC breaks code between major releases.
Chris2048 10y ago
Were string exceptions deprecated in 2.6 because they don't exist in py3?
- scrollaway 10y ago
  String exceptions don't exist in py3 because they were deprecated in 2.6.