On 5 Jul 2014 09:23, "Ralf Gommers" <ralf.gomm...@gmail.com> wrote: > > On Sat, Jul 5, 2014 at 10:13 AM, David Cournapeau <courn...@gmail.com> wrote: >> >> On Sat, Jul 5, 2014 at 11:25 AM, Charles R Harris < charlesr.har...@gmail.com> wrote: >>> >>> Ralf likes the speed of bento, but it is not currently maintained >> >> >> What exactly is not maintained ? > > > The issue is that Julian made some slightly nontrivial changes to core/setup.py and didn't want to update core/bscript. No one else has taken the time either to make those changes. That didn't bother me enough yet to go fix it, because they're all optional features and using Bento builds works just fine at the moment (and is part of the Travis CI test runs, so it'll keep working).
Perhaps a compromise would be to declare it officially unsupported and remove it from Travis CI, while leaving the files in place to be used on an at-your-own-risk basis? As long as it's in Travis, the default is that anyone who breaks it has to fix it. If it's not in Travis, then the default is that the people (person?) who use bento are responsible for keeping it working for their needs. > I don't think the above is a good reason to remove Bento support. The much faster builds alone are a good reason to keep it. And the assertion that all numpy devs understand numpy.distutils is more than a little questionable:) They surely don't. But thousands of people use setup.py, and one or two use bento. Yet supporting both requires twice as much energy and attention as supporting just one. We've probably spent more person-hours talking about this, documenting the missing bscript bits, etc. than you've saved on those fast builds. -n
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
