Closed westurner closed 2 years ago
@Eman22S and @ngeiswei Can you guys please please please please get around to merging into master? Your code has been sitting derelict for far too long! You need to get into the habit of doing this all the time
@westurner These guys have allowed a huge number of commits to accumulate in private branches. I'm vaguely assuming that python3 fixes are in there. Doing much of anything with the master branch here is kind-of pointless until those other changes are merged. I'm trying to nag those guys to get-r-done, you are hardly the first to trip over assorted issues...
Sorry about that. I didn't forget about it, the whole time, I was just procrastinating due to uncertainties as well as minimizing pain and effort, but we've clearly passed the point of diminishing return. Anyway things have cleared up and I'm ready take care of it!
Closing. I ported to python3 in pull req #96
Thanks!
On Mon, Jul 25, 2022, 5:36 PM Linas Vepštas @.***> wrote:
Closed #70 https://github.com/opencog/asmoses/issues/70 as completed.
— Reply to this email directly, view it on GitHub https://github.com/opencog/asmoses/issues/70#event-7059888251, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAMNS3SDKLQBPIQFDN4HOLVV4CE7ANCNFSM4OEEQQSA . You are receiving this because you were mentioned.Message ID: @.***>
Python 2 is no longer updated or supported. Would running
2to3
be sufficient to upgrade the Python examples to Python 3, or would backward compatibility with Python 2 need to be retained?