Date: Sun, 29 Jan 2017 11:22:00 -0800 From: Eitan Adler <lists@eitanadler.com> To: "John W. O'Brien" <john@saltant.com> Cc: FreeBSD Python List <freebsd-python@freebsd.org> Subject: Re: Proposal: default to concurrent Message-ID: <CAF6rxg=96giSsOS5MQBEujbFNKzCHk%2BF2sanjH7sOJ4nE_5Y=A@mail.gmail.com> In-Reply-To: <b331f7bb-f258-e157-45bb-20cec74b54f0@saltant.com> References: <b331f7bb-f258-e157-45bb-20cec74b54f0@saltant.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 29 January 2017 at 11:08, John W. O'Brien <john@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? -- Eitan Adler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxg=96giSsOS5MQBEujbFNKzCHk%2BF2sanjH7sOJ4nE_5Y=A>