Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-07-09 Thread Marten van Kerkwijk
Hi Peter, In the context of the discussion here, the fact that Quantity is a subclass and not a duck-type array makes no difference for scipy code - in either case, the code would eat the unit (if it would work at all). My only argument was that sub-classing is not particularly worse than trying t

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-07-08 Thread Peter Creasey
> From: Marten van Kerkwijk > > Though based on my experience with Quantity, I'd also argue that the > more annoying problems are not so much with `ndarray` itself, but > rather with the helper functions. Just to give an alternative view - as another astronomer I would say that concerns about the

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-07-08 Thread josef . pktd
On Fri, Jul 7, 2017 at 6:42 PM, Ryan May wrote: > On Fri, Jul 7, 2017 at 4:27 PM, Marten van Kerkwijk < > m.h.vankerkw...@gmail.com> wrote: > >> Hi All, >> >> I doubt I'm really the last one thinking ndarray subclassing is a good >> idea, but as that was stated, I feel I should at least pipe in.

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-07-08 Thread Marten van Kerkwijk
Hi Ryan, Indeed, the liberal use of `np.asarray` is one of the main reason the helper routines are relatively annoying. Of course, that is not an argument for using duck-types over subclasses: those wouldn't even survive `asanyarray` (which many numpy routines now have moved to). All the best, M

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-07-07 Thread Ryan May
On Fri, Jul 7, 2017 at 4:27 PM, Marten van Kerkwijk < m.h.vankerkw...@gmail.com> wrote: > Hi All, > > I doubt I'm really the last one thinking ndarray subclassing is a good > idea, but as that was stated, I feel I should at least pipe in. It > seems to me there is both a perceived problem -- with

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-07-07 Thread Marten van Kerkwijk
Hi All, I doubt I'm really the last one thinking ndarray subclassing is a good idea, but as that was stated, I feel I should at least pipe in. It seems to me there is both a perceived problem -- with the two subclasses that numpy provides -- `matrix` and `MaskedArray` -- both being problematic in

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-07-06 Thread Stephan Hoyer
On Thu, Jul 6, 2017 at 9:42 AM, Chris Barker wrote: > In NumPy, this could go along with NDArrayOperatorsMixins in >> numpy/lib/mixins.py >> >> > > Yes! I had no idea that existed. > It's brand new

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-07-06 Thread Stephan Hoyer
On Thu, Jul 6, 2017 at 4:42 AM, Ben Rowland wrote: > Slightly off topic, but as someone who has just spent a fair amount of > time implementing various > subclasses of nd-array, I am interested (and a little concerned), that the > consensus is not to use > them. Is there anything available which

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-07-06 Thread Chris Barker
On Wed, Jul 5, 2017 at 11:05 AM, Stephan Hoyer wrote: > That is, the boilerplate needed for multi-dimensional indexing and >> slicing, etc... >> >> That could be a nice little sprint-able project. >> > > Indeed. Let me highlight a few mixins >

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-07-06 Thread Ben Rowland
> On 5 Jul 2017, at 19:05, Stephan Hoyer wrote: > > On Wed, Jul 5, 2017 at 10:40 AM, Chris Barker > wrote: > Along those lines, there was some discussion of having a set of utilities (or > maybe eve3n an ABC?) that would make it easier to create a ndarray-like > o

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-07-05 Thread Stephan Hoyer
On Wed, Jul 5, 2017 at 10:40 AM, Chris Barker wrote: > Along those lines, there was some discussion of having a set of utilities > (or maybe eve3n an ABC?) that would make it easier to create a ndarray-like > object. > > That is, the boilerplate needed for multi-dimensional indexing and > slicing

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-07-05 Thread Chris Barker
On Mon, Jul 3, 2017 at 4:27 PM, Stephan Hoyer wrote: > If someone who does subclasses/array-likes or so (e.g. like Stefan >> Hoyer ;)) and is interested, and also we do some >> teleconferencing/chatting (and I have time) I might be interested >> in discussing and possibly trying to develop th

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-07-05 Thread Charles R Harris
Lots of good ideas here. It would help if issues were opened for them and flagged with the sprint label. I'll be doing some myself, but I'm not as intimately familiar with some of the topics as the proposers are. Chuck ___ NumPy-Discussion mailing list

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-07-05 Thread David Cournapeau
On Wed, Jul 5, 2017 at 10:43 AM, Ralf Gommers wrote: > > > On Mon, Jul 3, 2017 at 7:01 AM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> >> >> On Sun, Jul 2, 2017 at 9:33 AM, Sebastian Berg < >> sebast...@sipsolutions.net> wrote: >> >>> On Sun, 2017-07-02 at 10:49 -0400, Allan Halda

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-07-05 Thread Matthew Brett
On Wed, Jul 5, 2017 at 11:31 AM, Peter Cock wrote: > On Wed, Jul 5, 2017 at 11:25 AM, Ralf Gommers wrote: >> >> >> On Wed, Jul 5, 2017 at 10:14 PM, Peter Cock >> wrote: >>> >>> Note that TravisCI does not yet have official Python support on Mac OS X, >>> >>> https://github.com/travis-ci/travis-c

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-07-05 Thread Matthew Brett
On Wed, Jul 5, 2017 at 11:25 AM, Ralf Gommers wrote: > > > On Wed, Jul 5, 2017 at 10:14 PM, Peter Cock > wrote: >> >> Note that TravisCI does not yet have official Python support on Mac OS X, >> >> https://github.com/travis-ci/travis-ci/issues/2312 >> >> I believe it is possible to do anyway by f

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-07-05 Thread Peter Cock
On Wed, Jul 5, 2017 at 11:25 AM, Ralf Gommers wrote: > > > On Wed, Jul 5, 2017 at 10:14 PM, Peter Cock > wrote: >> >> Note that TravisCI does not yet have official Python support on Mac OS X, >> >> https://github.com/travis-ci/travis-ci/issues/2312 >> >> I believe it is possible to do anyway by f

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-07-05 Thread Ralf Gommers
On Wed, Jul 5, 2017 at 10:14 PM, Peter Cock wrote: > Note that TravisCI does not yet have official Python support on Mac OS X, > > https://github.com/travis-ci/travis-ci/issues/2312 > > I believe it is possible to do anyway by faking it under another setting > (e.g. pretend to be a generic langua

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-07-05 Thread Peter Cock
Note that TravisCI does not yet have official Python support on Mac OS X, https://github.com/travis-ci/travis-ci/issues/2312 I believe it is possible to do anyway by faking it under another setting (e.g. pretend to be a generic language build, and use the system Python or install your own specifi

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-07-05 Thread Ralf Gommers
On Mon, Jul 3, 2017 at 7:01 AM, Charles R Harris wrote: > > > On Sun, Jul 2, 2017 at 9:33 AM, Sebastian Berg > wrote: > >> On Sun, 2017-07-02 at 10:49 -0400, Allan Haldane wrote: >> > On 07/02/2017 10:03 AM, Charles R Harris wrote: >> > > Updated list below. >> > > >> > > On Sat, Jul 1, 2017 at

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-07-03 Thread Stephan Hoyer
On Sun, Jul 2, 2017 at 8:33 AM Sebastian Berg wrote: > If someone who does subclasses/array-likes or so (e.g. like Stefan > Hoyer ;)) and is interested, and also we do some > teleconferencing/chatting (and I have time) I might be interested > in discussing and possibly trying to develop the n

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-07-02 Thread Charles R Harris
On Sun, Jul 2, 2017 at 9:33 AM, Sebastian Berg wrote: > On Sun, 2017-07-02 at 10:49 -0400, Allan Haldane wrote: > > On 07/02/2017 10:03 AM, Charles R Harris wrote: > > > Updated list below. > > > > > > On Sat, Jul 1, 2017 at 7:08 PM, Benjamin Root > > > > > > wrote:

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-07-02 Thread Sebastian Berg
On Sun, 2017-07-02 at 10:49 -0400, Allan Haldane wrote: > On 07/02/2017 10:03 AM, Charles R Harris wrote: > > Updated list below. > > > > On Sat, Jul 1, 2017 at 7:08 PM, Benjamin Root >   > > > wrote: > > > > Just a heads-up. There is now a sphinx-gallery plugin.

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-07-02 Thread Allan Haldane
On 07/02/2017 10:03 AM, Charles R Harris wrote: Updated list below. On Sat, Jul 1, 2017 at 7:08 PM, Benjamin Root > wrote: Just a heads-up. There is now a sphinx-gallery plugin. Matplotlib and a few other projects have migrated their docs over to use it.

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-07-02 Thread Charles R Harris
Updated list below. On Sat, Jul 1, 2017 at 7:08 PM, Benjamin Root wrote: > Just a heads-up. There is now a sphinx-gallery plugin. Matplotlib and a > few other projects have migrated their docs over to use it. > > https://sphinx-gallery.readthedocs.io/en/latest/ > > Cheers! > Ben Root > > > On Sa

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-07-01 Thread Benjamin Root
Just a heads-up. There is now a sphinx-gallery plugin. Matplotlib and a few other projects have migrated their docs over to use it. https://sphinx-gallery.readthedocs.io/en/latest/ Cheers! Ben Root On Sat, Jul 1, 2017 at 7:12 AM, Ralf Gommers wrote: > > > On Fri, Jun 30, 2017 at 6:50 AM, Paul

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-07-01 Thread Ralf Gommers
On Fri, Jun 30, 2017 at 6:50 AM, Pauli Virtanen wrote: > Charles R Harris kirjoitti 29.06.2017 klo 20:45: > > Here's a random idea: how about building a NumPy gallery? > > scikit-{image,learn} has it, and while those projects may have more > > visual datasets, I can imagine something

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-06-30 Thread David Cournapeau
Will it be possible for people not at SciPy to participate ? The timing looks I could finally spend some time on numpy again this year David On Thu, Jun 29, 2017 at 7:07 PM, Charles R Harris wrote: > Hi All, > > I will be running the NumPy sprint at Scipy 2017 and I'm trying to put > together a

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-06-29 Thread Evgeni Burovski
> Convert the doctest in `numpy/lib/tests/test_polynomial.py` to regular tests. Might be tricky as it mostly checks print formatting. Port scipy's refguide-check and enhance/fix/improve code examples in docstrings? Also somewhat janitorial though. ___

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-06-29 Thread Pauli Virtanen
Charles R Harris kirjoitti 29.06.2017 klo 20:45: > Here's a random idea: how about building a NumPy gallery? > scikit-{image,learn} has it, and while those projects may have more > visual datasets, I can imagine something along the lines of Nicolas > Rougier's beautiful book: > >

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-06-29 Thread Charles R Harris
On Thu, Jun 29, 2017 at 12:15 PM, Stefan van der Walt wrote: > On Thu, Jun 29, 2017, at 11:09, Charles R Harris wrote: > > > On Thu, Jun 29, 2017 at 12:07 PM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > > I will be running the NumPy sprint at Scipy 2017 and I'm trying to put > togeth

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-06-29 Thread Stefan van der Walt
On Thu, Jun 29, 2017, at 11:09, Charles R Harris wrote: > > On Thu, Jun 29, 2017 at 12:07 PM, Charles R Harris > wrote:>> I will be running the NumPy sprint at > Scipy 2017 and I'm trying to >> put together a suitable list of things to sprint on. In my >> experience, sprinting on NumPy is hard,

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-06-29 Thread Charles R Harris
On Thu, Jun 29, 2017 at 12:07 PM, Charles R Harris < charlesr.har...@gmail.com> wrote: > Hi All, > > I will be running the NumPy sprint at Scipy 2017 and I'm trying to put > together a suitable list of things to sprint on. In my experience, > sprinting on NumPy is hard, enhancements generally need

[Numpy-discussion] Scipy 2017 NumPy sprint

2017-06-29 Thread Charles R Harris
Hi All, I will be running the NumPy sprint at Scipy 2017 and I'm trying to put together a suitable list of things to sprint on. In my experience, sprinting on NumPy is hard, enhancements generally need lengthy review and even finding and doing simple bug fixes can take time. What I have in mind at