#5549 (Is Python 3.8 really too old for Lino?)

by Luc Saffre · in Developers · assigned to Luc Saffre

2 years, 6 months ago by Luc Saffre about #5549 (Is Python 3.8 really too old for Lino?) : IOW I still cannot reproduce this problem, which I saw with my own eyes (via Jitsi) on Joy's computer. The traceback said something about "collections.abc.Iterable is not indexable".
2 years, 6 months ago by Luc Saffre about #5549 (Is Python 3.8 really too old for Lino?) : Strange: I added a doctest to cover "python -m lino.hello" ([url gitlab.com/lino-framework/book/-/commit/b0178f47cb19c3e9d87bc18cb96df7838f7f9191 commit]), but it passes on GitLab: we have still the same [url gitlab.com/lino-framework/book/-/jobs/6608554699 four unrelated failures].
2 years, 6 months ago by Luc Saffre about #5549 (Is Python 3.8 really too old for Lino?) : According to GitLab, Lino runs perfectly under Python 3.8: the [url gitlab.com/lino-framework/book/-/jobs/6606415681 four failures] are unrelated. But the test suite did not run "python -m lino.hello" in a shell. I now added this test. Let's see whether we get to reproduce Joy's error!
2 years, 6 months ago by Luc Saffre about #5549 (Is Python 3.8 really too old for Lino?) : Created new Ticket #5549 (Is Python 3.8 really too old for Lino?).