The efforts are on average less demanding than this discussion. We are talking about adding entries to a list in most cases...
Also, while adding the optimization support for bento, I've noticed that a lot of the related distutils code is broken, and does not work as expected on at least OS X + clang. David On Sun, Jul 6, 2014 at 1:38 AM, Nathaniel Smith <n...@pobox.com> wrote: > On Sat, Jul 5, 2014 at 3:21 PM, David Cournapeau <courn...@gmail.com> > wrote: > > > > On Sat, Jul 5, 2014 at 11:17 PM, Nathaniel Smith <n...@pobox.com> wrote: > >> > >> Maybe bento will revive and take over the new python packaging world! > >> Maybe not. Maybe something else will. I don't see how our support for > >> it will really affect these outcomes in any way. And I especially > >> don't see why it's important to spend time *now* on keeping bento > >> working, just in case it becomes useful *later*. > > > > But it is working right now, so that argument is moot. > > My suggestion was that we should drop the rule that a patch has to > keep bento working to be merged. We're talking about future breakages > and future effort. The fact that it's working now doesn't say anything > about whether it's worth continuing to invest time in it. > > -- > Nathaniel J. Smith > Postdoctoral researcher - Informatics - University of Edinburgh > http://vorpus.org > _______________________________________________ > NumPy-Discussion mailing list > NumPy-Discussion@scipy.org > http://mail.scipy.org/mailman/listinfo/numpy-discussion >
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion