[Scons-dev] Processed: Re: scons: Python2 removal in sid/bullseye

[Bill Deegan]

SCons can't tell (in general) if the SConstructs/SConscripts run with SCons
aren't py3 compatible except when user runs scons with py3.
That said we'll be dropping py2 support with SCons 4.0.
Timeline for that's a bit in flux.

That said the scripts installed current expect "python" and not "python2"
or "python3"

On Tue, Dec 3, 2019 at 2:01 PM Changwoo Ryu <cwryu at debian.org> wrote:

> In general, it would be helpful if the Scons project has a policy of
> deprecating python 2.x, e.g. printing a warning message for py2
> project files. Without such policy, people will just use old project
> files.
>
> And for distributions, it would be also useful to have a policy about
> command names for scons+python2 and scons+python3, like PEP 394.
> Fedora seems to choose /usr/bin/scons-2 and /usr/bin/scons-3.
>
>
> 2019년 12월 4일 (수) 오전 12:47, Bill Deegan <bill at baddogconsulting.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 <cwryu at debian.org> wrote:
> >>
> >> 2019년 12월 3일 (화) 오후 1:58, Bill Deegan <bill at baddogconsulting.com>님이 작성:
> >> >
> >> > 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,
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist2.pair.net/pipermail/scons-dev/attachments/20191203/e628d1fd/attachment.html>