View Single Post
Old 07-12-2019, 12:08 AM   #472
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
Okay! Here comes some news on the Python front. As some of you may be aware, Python 2 is scheduled to go supernova on the first of January 2020. Which means I ought to offer a Python 3 package before that EoL deadline...
Well, that's today. Because I'm extremely lazy, the Python packages will now intall *both* Python 2.7 & Python 3.7. Which means they're twice as large, and take twice as long to install. Eh.

Until the EoL, the python symlink still points to python2.7. I urge you to update your shebang if you have some code that's not Py3k-ready that's currently using a generic "python" shebang.
FWIW, *all* of the various Kindle bits I ship that need Python depend on Python 2. Thankfully, they were always using an explicit python2 shebang, so, nothing will horribly break at random one day .

As far as 3rd-party modules go, when some/all of them start dropping Python 2 support, I'll simply freeze the Python 2 build to the latest supported version.

I've also updated the example code in FBInk's python bindings to behave properly on both Python versions.

On a slightly related note, because I had to vent my rage at Python's buildsystem somewhere, I worked on FBGrab: it's now much faster (some of that is actually achieved by making it go faster, and some of it by convincing libpng & zlib not to spend so much time on filtering & compression). (The standalone builds were also updated).

Anyway, obligatory finish-line shot:

On a PW2:
Code:
Python 3.7.3 (default, Jul 10 2019, 09:11:48) 
[GCC 7.4.1 20181213] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import platform
>>> platform.uname()
uname_result(system='Linux', node='kindle', release='3.0.35-lab126', version='#2 PREEMPT Tue Jul 24 06:43:56 PDT 2018', machine='armv7l', processor='')
>>>
Or, hell, even on a K2i:
Code:
Python 3.7.3 (default, Jul 11 2019, 05:54:06) 
[GCC 7.4.1 20181213] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import platform
>>> platform.uname()
uname_result(system='Linux', node='kindle', release='2.6.22.19-lab126', version='#3 PREEMPT Thu Jan 13 18:13:20 PST 2011', machine='armv6l', processor='')
>>>
PSA: This *requires* a recent MRPI version, so, do make sure you've successfully updated MRPI to the latest version *first*!

Last edited by NiLuJe; 07-18-2019 at 02:29 PM. Reason: Mention needing a recent MRPI version.
NiLuJe is offline   Reply With Quote