PiDP-8/I SoftwarePython 3
Not logged in

Python 3

(1) By Bill Cattey (poetnerd) on 2020-03-24 23:54:21 [link] [source]

I see that back in May 2019, work was done to get os8-run working under python3.

I've just checked in updates to os8script.py.in and simh.py.in, and now I have a successful end-to-end clean build under python3.

Although I'd personally planned never to leave python2, I've had to accept the reality that everybody is shifting to python3, and many platforms and environments are deleting python2.

We should formulate a plan for migrating to python3.

(2) By Warren Young (tangent) on 2020-03-25 01:13:53 [link] [source] in reply to 1

I've just checked in updates to os8script.py.in and simh.py.in, and now I have a successful end-to-end clean build under python3.

Cool!

many platforms and environments are deleting python2.

Yes, I expected to be forced to resolve this branch no later than the next major release of Raspbian. It's good to get it handled ahead of time.

We should formulate a plan for migrating to python3.

Same as all portability matters: detect the feature in auto.def, then switch versions seamlessly, if possible.

Therefore:

  1. Does the current branch still work with Python 2?

  2. If not, can it be made to do so?

  3. All top-level Python scripts probably need to become *.in files and have the shebang line dynamically switched, and depending on the answers to the above questions, have Python 3 code conditionally run or included by Autosetup.

Bottom line, I want the software to continue working on Python 2 based systems until those are ~10ish years gone, hopefully without saying "Revert to the 2019.xx.yy branch" or similar.

(3) By Bill Cattey (poetnerd) on 2020-03-27 01:29:39 [source] in reply to 2

I shall attempt to investigate the answer to question #1. Unfortunately, I broke python2 on my Mac, which is why I troubled myself to get the python3 branch building.