Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 25 Oct 2019 07:23:45 +0000
From:      bugzilla-noreply@freebsd.org
To:        python@FreeBSD.org
Subject:   [Bug 241463] [NEW PORT] devel/scons-py3: scons for python3
Message-ID:  <bug-241463-21822-v1EjtimWdT@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-241463-21822@https.bugs.freebsd.org/bugzilla/>
References:  <bug-241463-21822@https.bugs.freebsd.org/bugzilla/>

index | next in thread | previous in thread | raw e-mail

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241463

Kubilay Kocak <koobs@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|ports-bugs@FreeBSD.org      |sunpoet@FreeBSD.org
                 CC|                            |koobs@FreeBSD.org
              Flags|                            |maintainer-feedback?(sunpoe
                   |                            |t@FreeBSD.org)
           Keywords|patch                       |feature, needs-qa
             Status|New                         |Open
            Summary|new port: devel/scons-py3:  |[NEW PORT] devel/scons-py3:
                   |scons slave port for        |scons for python3
                   |python3                     |

--- Comment #3 from Kubilay Kocak <koobs@FreeBSD.org> ---
Though I understand the motivation for this port proposal, we'd prefer not to
add py2/3 specific ports, because:

- Python ports should always allow *any* Python version to be used for the
build that the upstream supports. Any Python port unnecessarily restricting the
declared version support is considered a bug.

- All else being equal, there ought to be no work required for 'specifically'
or explicitly flavouring any Python port, and instead leverage the automatic
flavouring that is produced solely by declaring the versions that the software
*supports*. Perhaps scons is differerent, but in that case, we should
understand where and how, and seek to aim our effort toward addressing those
questions rather than creating a potentially very short lived port that has
limited utility, and comes with downsides.

- It breaks with the conventions/mechanism that we have developed to allow
arbitrary user-selection of their preferred Python version, while minimising
conflicts between packages.

We should resolve any barriers/issues with the main scons port not allowing, or
not being currently appropriate for building with Python 3.x.

Could you please add any relevant scons issue ID's to this bugs See Also field

-- 
You are receiving this mail because:
You are on the CC list for the bug.

help

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-241463-21822-v1EjtimWdT>