[Raion]

Nekoware does have Python 3.1... But I understand that's far too old to do anything with. My suggestion:

Check my wiki page for building GCC 5, build it into nekoware, then try grabbing the RSE patches for Python3 manually (as well as any deps not in Nekoware) and try building it in there. The 4.7.1 should work, you may need to do a full bootstrap though...

But as much as I want to believe you when you say they don't conflict, I have seen stuff break. And while I've not tested RSE, some things like libdicl and Erno's older GCC tardists do replace or overwrite or use special headers or libs that do not function under certain assumptions, and have broken stuff for MIPSPro for me. That's why I segregate things

I'm not pushing you to not do it however you want, by any means do what you prefer and are comfortable with, but please don't mix packages or code and expect it to just work. That's pretty much asking for trouble, and very few people here are going to be able to help with the RSE side, and at SGUG, many don't even seem to acknowledge the work or strides Nekoware accomplished, let alone have used it in-depth as some of us have. That sets you and other users up for failure. That's why I say stick with things. I wish I had Nekoware II for release even in a preliminary state, but I'm not authorized by Axatax to do that yet for a variety of reasons.

I hate saying this sort of thing over and over ad nauseaum, for those who've witnessed the last time this kind of talk erupted; but it's a little too much to ask of the 'veterans' here to use a software distribution they're not interested in. It's not elitist purism. Some like myself work on or have worked on RHEL or Fedora or CentOS for years and may not really like the idea of forgoing native packaging for something straight out of GNU/Linux. I don't like RPM on AIX for the same reason. I'm not a veteran, but many of the ex-Nekochanners here are.

Hopefully that lays out the problem. I can't make promises about Nekoware II since my job is testing and packaging, but Axatax is in charge of building our "base"