+1 for just merging the patch On Tue, Dec 15, 2015 at 3:36 AM, Bill Deegan <b...@baddogconsulting.com> wrote:
> Dirk, > > I think we've given enough notice that pre 2.7 is going to be dropped. > I'll take a pass through the updated pull request (#284) and merge it, > unless someone has serious issues with doing so. > > -Bill > > > On Mon, Dec 14, 2015 at 4:53 PM, Dirk Bächle <tshor...@gmx.de> wrote: > >> Hi there, >> >> On 11.12.2015 22:39, Bill Deegan wrote: >> >>> +1 on waiting for Dirks pull request to land. >>> He has a couple items to add before it's complete. >>> He said he'll be working on them over the weekend. >>> Might be done by Tuesday.. >>> >>> >> I've updated my pull request with an additional commit. So, short of a >> final review, it should be ready to get merged... >> >> I'd like to raise one question though: What about the integration of the >> "stubprocess.py" wrapper? Wasn't this planned for the next release 2.5? If >> we want to keep it this way, it might be better to *not* merge my PR into >> "trunk" right now, but only onto the python3 branch directly. >> Like this, we could work on the "stubprocess" thingy, merge it to "trunk" >> first, and only then put PR#284 on top. This would give us the opportunity >> to release a 2.5 with the "stubprocess.py" speedup, but still (some) >> backward compatibility to Python 2.6...so more users could benefit from >> this? >> >> Just as an idea... >> >> Best regards, >> >> Dirk >> >> >> >> _______________________________________________ >> Scons-dev mailing list >> Scons-dev@scons.org >> https://pairlist2.pair.net/mailman/listinfo/scons-dev >> > > > _______________________________________________ > Scons-dev mailing list > Scons-dev@scons.org > https://pairlist2.pair.net/mailman/listinfo/scons-dev > >
_______________________________________________ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
