[Scons-dev] SCons 3.0, sconsign files and Py2 vs Py3.. how to handle sconsign imcompatabilities

[Tim Jenness]

> On Sep 11, 2017, at 06:24, Bill Deegan <bill at baddogconsulting.com> wrote:
> 
> Likely the rebuild py2 vs py3 is the action signature for functions now uses the bytecode. The bytecode is different between py2 and py3.
> 
> Previously it was either pickling the function (which didn't adequately check for changes in the python functions), or dumping the string representation :
> <function a at 0x10e88fc80>
> For example.
> 
> 

Sounds like this can’t be solved then. Release v3.0 with pickle 2 and tell people there will be rebuilding if you flit between versions.

— 
Tim Jenness