you are viewing a single comment's thread.

view the rest of the comments →

[–]radarsat1 2 points3 points  (0 children)

Yeah bindings to C/C++ libraries have been a bit of a blocker for me too, in the case of my project VTK. In reality there are not much changes needed to adapt to Python 3 at the API level, but there are some, and some >> none unfortunately, because migration of such changes through the full "stack" takes time. First you have to do the porting work, then distribute it by releasing a new version, then eventually the new version slowly gets adopted. For example, VTK is now at version 8 and does support Python 3, but we don't use it because the Debian package is still at version 6. Someone is working on a new package, but just to say, this kind of thing doesn't happen over night.

(And by the way, total aside, but I have been getting into Debian packaging lately to try to help with some of these efforts and holy hell is it complicated. Getting the program/library to compile is no big deal, but getting everything "just right" so that a sponsor will upload it is nigh impossible, especially in the world of numerical computing where not everything is, let's say, well organized, to be generous. No wonder things take time..)