Re: Should we close python3-port branch in scons bitbucket?
Bill Deegan <bill-cJFiu+DHMVC5azolltMz9laTQe2KTcn/@public.gmane.org>
| Newsgroups | gmane.comp.programming.tools.scons.devel |
|---|---|
| Message-ID | <CAEyG4CFjuE-Reji9Ck3yA5G0TXLR+32b8x==fFMcaKzLpQOdYA@mail.gmail.com> |
Russel, So the branch your work is on in your repo is python3-port? I'm o.k. with CI going red for this. I don't want to delay the python 3 port any further. I think the project should go "all in" on getting py2/3 done at this point in time. How long would you expect getting your py3 work to run/pass all tests on py2.7? (Wild guesses are welcome) -Bill On Thu, Apr 14, 2016 at 10:46 AM, Russel Winder <[email protected]> wrote: > Bill, > > It is also worth thinking about the "CI shall never go red" vibe. > Currently my python3-port branch is very red. > > -- > 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