Speaking as someone who started but then stopped dabbling in the NumPy C core, having to think about two build system is a huge turn-off. Getting into the NumPy C code is hard enough without having to worry about multiple build systems.
Bryan On Jul 5, 2014, at 6:42 PM, Ralf Gommers <ralf.gomm...@gmail.com> wrote: > > > > On Sat, Jul 5, 2014 at 4:17 PM, Nathaniel Smith <n...@pobox.com> wrote: > On Sat, Jul 5, 2014 at 2:32 PM, Ralf Gommers <ralf.gomm...@gmail.com> wrote: > > > > On Sat, Jul 5, 2014 at 1:54 PM, Nathaniel Smith <n...@pobox.com> wrote: > >> > >> On 5 Jul 2014 09:23, "Ralf Gommers" <ralf.gomm...@gmail.com> wrote: > >> 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. > > > > -1 that just means that simple changes like adding a new extension will not > > get made before PRs get merged, and bento support will be in a broken state > > much more often. > > Yes, and then the handful of people who care about this would fix it > or not. > > What next, we give Alan Isaac commit rights and then it's OK to break > numpy.matrix when that's convenient? > > Your -1 is attempting to veto other people's *not* paying > attention to this build system. I... don't think -1's work that way > :-( > > You're proposing it'll be OK for others to break stuff that the people before > them put quite some effort into implementing. I damn well have the right to > give that a -1. > > David is fixing the few existing problems now, so there should be zero issues > here. You're deliberately mischaracterizing the situation (pre-alpha, lot of > effort, etc.), so I'm not going to bother responding to the rest, I'm annoyed > enough as is. > > Ralf > > P.S. if anyone wants to spend some productive energy on the build situation, > MSVC 2010 support for Python 3.x would be nice: > https://github.com/numpy/numpy/issues/4245 > > _______________________________________________ > 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
