@EP01 @stigarn If there's any possibility you can put some python3 through it's paces on unstable, would be appreciated. Everything should work bar openshot, but some of the older python packages might need updated versions for better python 3.6 support is all I can think of.

Will do @sunnyflunk, I'll let you know here if I spot anything. Thanks for all the work to do the upgrade, bet you can't wait to do it all again for 3.7! How much did you manage to script?

@EP01 90%, (but then I deleted 15 packages by mistake...). Next time will be much, much easier as 40% of the packages wouldn't build first go due to: no component key, the python macros having changed and make bump was screwing up the source (I think it might happen when there's extra whitespace), then later builds breaking due to pkgconfig(python3.5), which worked locally until the update was pushed to Solus. So it was pretty time consuming, but now all the issues are resolved for next time, though there are a couple of circular dependencies in the python tests (which I'll know about). All part of the repo cleanup efforts really, updating packages to the current format and standards which makes them cake to maintain.

Also managed to merge all the Diffs for updates while doing it xD

Rebuild appears to be complete now. Would only be if I deprecated repos that are still in Solus the other week.

$ egrep -nir python3.5 | grep pspec
sardi-icons/pspec_x86_64.xml:2903:            <Path fileType="data">/usr/share/icons/Sardi-Flexible/scalable/apps/python3.5.svg</Path>
sardi-icons/pspec_x86_64.xml:7345:            <Path fileType="data">/usr/share/icons/Sardi-Mono/scalable/apps/python3.5.svg</Path>
numix-icon-theme-circle/pspec_x86_64.xml:3362:            <Path fileType="data">/usr/share/icons/Numix-Circle/48/apps/python3.5.svg</Path>
numix-icon-theme-square/pspec_x86_64.xml:3362:            <Path fileType="data">/usr/share/icons/Numix-Square/48/apps/python3.5.svg</Path>
$ egrep -nir python-35 | grep pspec
$ egrep -nir libpython3.5 | grep abi_used_libs
$

@sunnyflunk

In T5695#103219, @sunnyflunk wrote:

@EP01 @stigarn If there's any possibility you can put some python3 through it's paces on unstable, would be appreciated. Everything should work bar openshot, but some of the older python packages might need updated versions for better python 3.6 support is all I can think of.

I'm sorry but I don't understand what you mean.

@stigarn well I notice you package a fair few python packages, so figured you might be better positioned than most for updating to unstable for a moment and testing those python packages still work as expected. If you don't want to, that is also ok

In T5695#103270, @sunnyflunk wrote:

@stigarn well I notice you package a fair few python packages, so figured you might be better positioned than most for updating to unstable for a moment and testing those python packages still work as expected. If you don't want to, that is also ok

Now I understand and that is no problem to do. I have a Virtual machine that is on unstable so I can test some packages this afternoon.

I've updated all "my" packages and they work fine, no problems there.

The only issue I found, was this package that wasn't in the list : dde3f3224b82
Actually it seems that python 3 isn't required to build this package. I am preparing the libboost update, and I'll have to rebuild this package so I'll fix it at the same time.

If it's just a general (non versioned) .py file it shouldn't need a rebuild (i.e. interpreted at runtime with whatever you have installed they typically get versioned when compiled), but I have no objection to being safe than sorry (can rebuild the repo if you really want). Though may be it's different if there's .pyc files built with it which might cause conflict and is certainly worth rebuilding for runtime performance.