On Wed, Aug 19, 2015 at 1:22 AM, Nathaniel Smith wrote:
> On Tue, Aug 18, 2015 at 4:15 PM, David Cournapeau
> wrote:
> > If everybody wants to remove bento, we should remove it.
>
> FWIW, I don't really have an opinion either way on bento versus
> distutils, I just feel that we shouldn't maintai
On Tue, Aug 18, 2015 at 4:15 PM, David Cournapeau wrote:
> If everybody wants to remove bento, we should remove it.
FWIW, I don't really have an opinion either way on bento versus
distutils, I just feel that we shouldn't maintain two build systems
unless we're actively planning to get rid of one
If everybody wants to remove bento, we should remove it.
Regarding single file builds, why would it help for static builds ? I
understand it would make things slightly easier to have one .o per
extension, but it does not change the fundamental process as the exported
symbols are the same in the en
Hi All,
.
I'm bringing up this topic again on account of the discussion at
https://github.com/numpy/numpy/pull/6199. The proposal is to stop (trying)
to support the Bento build system for Numpy and remove it. Votes and
discussion welcome.
Along the same lines, Pauli has suggested removing the sin
