python3-by-default build of all FreeBSD ports finished, took 3 weeks. This is OK, as I can't keep up with fixing the fallout anyway. Well I'd say that #FreeBSD is mostly ready for #python3 by default as it is - there only were 311 failures, and most of these are not directly related stage-qa problems (shebangs mostly). Still there is stuff to fix, yay!
@brnrd Thank you, but I'm OK for now. As said, cannot keep up with the build anyway, and I just need to load that box with something.
Btw, it's a VM running on VMware vSphere, and it seems to me that it has much worse performance than HW would allow because of virtualization. I really need to learn #DTrace to investigate such stuff.
@AMDmi3
Could you upload a list of all failures? I'm wondering whether I could switch to python3.
@AMDmi3
Thanks. I successfully switched to python 3.6 on my server, and am rebuilding ports on my desktop.
Forgot to mention that there's a problem though, which is when a port installs python3-incompatible script which is not called in the build process of neither the port itself nor the ports that depend on it, so the build won't catch these.
I'll look for python3 compatibility checking tool, I guess I could run it on packages I now have to find unaccounted incompatibilities.
@AMDmi3 I have a box that I can run such tests on... Takes about 2 days for poudriere -af. I could try help out!