I would personally make it a separate file. I'm a very OOP-centric geek. V/R, William
On Mon, Jan 25, 2016 at 8:39 PM, Vasily <[email protected]> wrote: > Any answer to my question about the place and approach for stubprocess to > live in? > > Thanks, > Vasily > 16 янв. 2016 г. 0:17 пользователь "Vasily" <[email protected]> > написал: > > I have started looking into the docs for integrating stubprocess in there. >> >> My current thoughts are to put it as a separate file next to posix.py in >> "Platform", any objections to this approach? Should I maybe put it to >> "compat"? >> >> Thanks, >> Vasily >> 15 янв. 2016 г. 21:05 пользователь "Bill Deegan" < >> [email protected]> написал: >> >>> I'm not going to merge any pull request for such until 2.5 is out though. >>> >>> Is anyone able to work on getting stubprocess logic into 2.5? >>> If not I'll roll up 2.5 this weekend. >>> >>> -Bill >>> >>> On Fri, Jan 15, 2016 at 10:04 AM, Bill Deegan <[email protected] >>> > wrote: >>> >>>> +1. >>>> >>>> I'll see if I can get a python 3.5 buildbot slave up soon. >>>> >>>> -Bill >>>> >>>> On Fri, Jan 15, 2016 at 6:01 AM, William Blevins <[email protected] >>>> > wrote: >>>> >>>>> +1 >>>>> >>>>> On Fri, Jan 15, 2016 at 1:24 PM, Russel Winder <[email protected]> >>>>> wrote: >>>>> >>>>>> Will try to do some more on this over the weekend. >>>>>> >>>>>> I got stuck on the weird os.mkinfo problem (still unsolved) and got a >>>>>> bit distracted by Me TV rewrite required to be ready soon so as to >>>>>> watch the 6 Nations games. New DVB-T2 USB sticks arriving tomorrow. >>>>>> >>>>>> On the really up-side, it appears that "futurize -1" is properly >>>>>> idempotent, making it a lot easier to work with than anything >>>>>> previously. >>>>>> >>>>>> Aim is still to get the code-base working properly, i.e passing all >>>>>> tests, as a Python 2.7 program, so that it can then become the default >>>>>> branch. My thinking here is that if we do not have a separate branch, >>>>>> but instead are evolving default to be Python 3 compatible as a Python >>>>>> 2.7 codebase then Python 3 usage will happen faster. The "down side" >>>>>> is >>>>>> that all Python 2 code must be written with Python 3 compliance from >>>>>> merge time on on, this includes all pull requests. >>>>>> >>>>>> -- >>>>>> Russel. >>>>>> >>>>>> ============================================================================= >>>>>> Dr Russel Winder t: +44 20 7585 2200 voip: >>>>>> sip:[email protected] >>>>>> 41 Buckmaster Road m: +44 7770 465 077 xmpp: >>>>>> [email protected] >>>>>> London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>> >>>>> >>>> >>> >>> _______________________________________________ >>> 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 > >
_______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev
