Re: Processed: Re: scons: Python2 removal in sid/bullseye
Bill Deegan <bill-cJFiu+DHMVC5azolltMz9laTQe2KTcn/@public.gmane.org> Tue, 3 Dec 2019 07:47:26 -0800
| Newsgroups | gmane.comp.programming.tools.scons.devel |
|---|---|
| Message-ID | <CAEyG4CGeJsTnykLQi5J=FzgsrRRj3X=RZs+VJQp_JR-YGbDm9w@mail.gmail.com> |
So sounds like the SCons project doesn't need to do anything. It's up to the projects which use SCons? -Bill On Mon, Dec 2, 2019 at 10:09 PM Changwoo Ryu <[email protected]> wrote: > 2019년 12월 3일 (화) 오후 1:58, Bill Deegan <bill-cJFiu+DHMVC5azolltMz9laTQe2KTcn/@public.gmane.org>님이 작성: > > > > What do you need me to do? > > > > -Bill > > SCons Project Co-Manager. > > I just merged the duplicated bugs and marked version. :) > > I understand that Debian scons py3 switching is not easy because of > the py2 dependent build files. In case of Fedora, py3 ready packages > use python3-scons which includes /usr/bin/scons-3 for python3. Anyway > the transition plan is up to the maintainer(s) decision. > > Regards, > _______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev