This is great news. I’d think that switching py2 with py3 scons within a single build tree is going to be fairly rare and can be documented as part of the 3.0 release.
— Tim Jenness > On Feb 20, 2017, at 16:49, Bill Deegan <[email protected]> wrote: > > Greetings, > > I'm making fairly good headway on this but I think I've found something which > may be hard to work around. > > When creating the action signature in some cases it will use pickle to > serialize the object. > (Functions, class instances,etc) > In those cases the pickled contents are different between python 2 and > python3. > This means that any build swapping between 2 and 3 would likely run into > extraneous actions (builders) being run. (When in fact nothing has changed) > > Additionally I found one assumption in the code to create signatures from > functions which is not correct. (That the first item in list of constants is > always the docstring, it is not if there is no docstring). > > Thoughts? > Clearly the py3/2 version of SCons will be a major version release (3.0). > > > -Bill > > _______________________________________________ > Scons-dev mailing list > [email protected] > https://pairlist2.pair.net/mailman/listinfo/scons-dev _______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev
