Difference between revisions of "ISFDB talk:Personal Linux Website"
(Response re Python 2.7) |
|||
| Line 16: | Line 16: | ||
: The upgrade to 2.7 ({{SR|142}}) has been on my list of things to do for a long time, but there have always been higher priority issue to tackle. Perhaps now that we have multiple editors and moderators working on Fixer (our data acquisition robot), I will have more time to work on it. [[User:Ahasuerus|Ahasuerus]] 19:55, 30 September 2019 (EDT) | : The upgrade to 2.7 ({{SR|142}}) has been on my list of things to do for a long time, but there have always been higher priority issue to tackle. Perhaps now that we have multiple editors and moderators working on Fixer (our data acquisition robot), I will have more time to work on it. [[User:Ahasuerus|Ahasuerus]] 19:55, 30 September 2019 (EDT) | ||
| + | |||
| + | :: OK, I'll give it a go with 2.7 later - worst case, I'll try to either fix the issues I see and/or document them on that ticket. [[User:ErsatzCulture|ErsatzCulture]] 05:35, 1 October 2019 (EDT) | ||
Revision as of 05:35, 1 October 2019
How hard is the dependency on Python 2.5.4 versus later Python 2.x.y versions?
Finally decided to try getting the full version of ISFDB (rather than just the DB) running locally, but I'm having a bit of pain getting Python 2.5.4 working. The platform I'm using is Fedora 26, which itself is pretty crusty these days, but ships with Python 2.7.15 (and Python 3.6.5, but lets not go there just yet...).
As far as I can see, python.org does not provide binaries for Linux, and nor can I see any pre-built packages in the Fedora or third-party repositories. Building from source seems to have problems that aren't immediately obvious, seemingly related to SSL/crypto library versions.
Perhaps this issue can be resolved without too much more effort, but I've only gotten to this point after a fair bit of yak-shaving already, and I'm not sure much more pain I care to put myself through - especially if it might turn out to be unnecessary, and 2.7.x works OK?
I did actually migrate some code from Python 2.5 to Python 2.7 a few years ago, and my vague recollection is that the language version issues were trivial to non-existent, and all the pain points were due to changes in the underlying platform (Google App Engine) and its APIs.
NB: I'm not asking for help in getting this working in my environment, and I appreciate that no-one's going to upgrade the live site and dev practices without proper investigation and testing, but I'm just wondering how much of that might already have been done?
ErsatzCulture 12:52, 30 September 2019 (EDT)
- I am afraid I don't know the answer. When I took over development in 2009, I tried Python 2.6 and it didn't work. I didn't dig too deep and I don't remember the details, only the outcome. It's entirely possible that the problems were minor and I simply didn't know enough about Python to fix them.
- The upgrade to 2.7 (SR 142) has been on my list of things to do for a long time, but there have always been higher priority issue to tackle. Perhaps now that we have multiple editors and moderators working on Fixer (our data acquisition robot), I will have more time to work on it. Ahasuerus 19:55, 30 September 2019 (EDT)
- OK, I'll give it a go with 2.7 later - worst case, I'll try to either fix the issues I see and/or document them on that ticket. ErsatzCulture 05:35, 1 October 2019 (EDT)