I thought about doing that... I'd have to re-write the "configurable python" fixes (mainly some boost stuff that was missing when building in my system, and some py2 compatibility stuff), but it's no longer needed, since I managed to iron out the wrinkles at the last minute (before I decided to nuke trunk).safemode wrote:klauss wrote:Well... it will be in sync by the time I'm finished merging, that's what I meant. I'm having trouble getting the PyInit_VS thing fixed, I think I have merged all revisions related to that, and I still get the error.safemode wrote:this patch isn't in mainline.. that's what i meant by in sync. I want the py3 branch to have the current re-balance and unit mods that are being done in this thread.
I'm not sure why the merging is a problem. Just overwrite the trunk branch with all the changes since py3 was split and you'll be good.
Merging the rest (cleanup) will come tomorrow probably, and data changes last.
You'll ask... why retain compatibility with py2? As we talked, if we did retain it at the source level (engine only), mods won't be forced to migrate to 3 rightaway. I think that's valuable, and it wasn't hard supporting both.
Furthermore, I managed to make all the python tools in objconv work on both versions with some __future__ magic. So... who knows... maybe we can support both everywhere. Not holding much hope in that though... no point in doing that in fact.
But it was important to make all the blender scripts in objconv work with py2, because we don't really control which version of python Blender uses.