On 1/29/2017 9:40:15 PM, "John W. O'Brien" <j...@saltant.com> wrote:
On 1/29/17 14:22, Eitan Adler wrote:
On 29 January 2017 at 11:08, John W. O'Brien <j...@saltant.com>
wrote:
Hello FreeBSD Python,
On the
other hand, there are lots of ports for which concurrent is a no-op,
and
lots more that don't support python3 at all meaning that concurrent
has
little to no chance to cause harm.
What I propose is to enable the concurrent behavior by default and
to
provide a feature to disable it when necessary.
silly question but why is it an option in the first place?
Not at all silly. I can only guess at the answer though. Let's consult
its implementer [0].
[0] https://svnweb.freebsd.org/ports?view=revision&revision=356921
Because at that time python ports existed, which did not build cleanly
with python3,
but which were dependencies to many other ports. The situation may have
changed
now.
Cheers
Marcus
_______________________________________________
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
