[Numpy-discussion] Issue Tracking

josef.pktd at gmail.com josef.pktd at gmail.com
Tue May 1 21:04:48 EDT 2012

On Tue, May 1, 2012 at 8:29 PM, Fernando Perez <fperez.net at gmail.com> wrote:
> On Tue, May 1, 2012 at 5:24 PM, Charles R Harris
> <charlesr.harris at gmail.com> wrote:
>> I would agree that a good search facility is essential, and not keyword/tag
>> based.
> Github issues does have full-text search, and up until now I haven't
> really had too many problems with it.  No sophisticated filtering or
> anything, but basic search with the option to see open/closed/all
> issues seems to work OK.
> Josef I'm curious, which problems have you had with it?

maybe searching issues and pull requests is ok.
The problem is that in statsmodels we did a lot of commits without
pull requests, and I'm not very good searching in git either.
(I don't remember which change I looked for but I got lost for half an
hour searching for a change with git and github until I had to ask
Skipper, who found it immediately.)

What I was used to is integrated search without extra work, like this
and I had pretty much all the discussion to the history of a function.

scipy.stats is easy too search because the function names are good search terms.

scipy pull request don't have a search facility, as far as I was able
to figure out, because the issues are not enabled, so I cannot check
how good it would be.

> Cheers,
> f
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at scipy.org
> http://mail.scipy.org/mailman/listinfo/numpy-discussion

More information about the NumPy-Discussion mailing list