dlax @dlax@mamot.fr

Pendant la fermeture d'une portion du périphérique parisien, et son utilisation par des cyclistes, on aurait constaté une baisse massive de la pollution de l'air. Bizarre... #carfree

http://carfree.fr/index.php/2019/10/10/la-disparition-de-la-pollution/

TypeError: '<' not supported between instances of 'NoneType' and '<whatever>'

my favorite thing when migrating a #python project to python3

#VendrediLecture "L'espace d'un an", de Becky Chambers : un space opéra où on suit l'équipage multi-espèces d'un vaisseau spatial ouvrier. Très agréable à lire, beaucoup d'émotions.

Once confident everything works fine with #python3 (tests suite is green, resolved all runtime errors spotted by, e.g., #sentry): drop #python2 support.
(7/7)

@logilab

Finish with all oddities left like comparison of values of heterogeneous type ("1 < 'infinity'" is True on #python2) or silly things like ordering a list of dicts.
(6/7)

@logilab

Then, it's often time to dig further into "text versus binary data" issues. Clearly the most painful part of the process because it's often has to do with non-obvious business logic. Things get even worse when third party libraries (e.g. lxml) are in use. https://docs.python.org/3/howto/pyporting.html#text-versus-binary-data

(5/7)

@logilab

Every time I see "open(filepath)", I change it into "io.open(filepath, 'rb')" to preserve #python2 behavior. This is fine most of the times; when it's not, it's usually because of some specific business logic you'll have to investigate on anyways. (Similarly, StringIO.StringIO -> io.BytesIO.)
(4/7)

@logilab

Try an automatic code porting tool, like https://python-modernize.readthedocs.io/, to remove #python2 idioms. This is no silver bullet but it helps. For instance, it will detect things now in six.moves (like itertools.imap) or usage of .next() and update your code. On the other hand, it sometimes does useless things like changing "for k, v in d.iteritems():" into "for k, v in six.iteritems(d):".
(3/7)

@logilab

First run flake8 with python3 and fix all spotted errors (e.g. "except ValueError, exc:"). Easy.
(2/7)

@logilab

Been porting a fair amount of code from #python2 to #python3 at @logilab recently. Here's a thread about how I usually proceed and what I learnt. (1/7)

As for other distros, #debian packages are automatically built and uploaded following upstream changes on thanks to the awesome builds.sr.ht system on #sourcehut. Package build logic and repo management lives at https://git.sr.ht/~dlax/sr.ht-debbuilds

Over the past few months, I've been working on packaging the #sourcehut forge for #debian. This is now available from the sr.ht mirror. See https://man.sr.ht/packages.md#debian to give it a try for self-hosting.