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

[Tim Jenness]

> On Sep 11, 2017, at 10:09 , Bill Deegan <bill at baddogconsulting.com> wrote:
> 
> One thought would be to allow annotating the function with a specified csig. and/or version #.
> This would help (at least) for internal action functions (built in to scons).
> 

That would be great but I think it can probably wait for v3.1. I don’t imagine that many people will be using py2 and py3 with the same scons and the same build (depends how they configure their PATH I guess).

> On Mon, Sep 11, 2017 at 10:23 AM, Tim Jenness <tjenness at lsst.org <mailto:tjenness at lsst.org>> wrote:
> 
> > On Sep 11, 2017, at 06:24, Bill Deegan <bill at baddogconsulting.com <mailto: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
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist2.pair.net/pipermail/scons-dev/attachments/20170911/14db760d/attachment.html>