Re: [SciPy-dev] [Numpy-discussion] Re: numpy.linalg prevents use of scipy.linalg?
Robert Kern wrote:
Zachary Pincus wrote:
What version of scipy are you using? Before reporting a bug, please make sure it exists in the current SVN revision.
Sorry I didn't include the version (0.4.6, by the way) in my first email. My oversight.
As to your latter statement, are you sure about that? You're only interested in getting bug reports from people who rebuild scipy from the svn every night, or who have tracked down the problem to the line so they know where in the svn to see if it's fixed?
No, I don't expect everyone to rebuild scipy every day. However, when you think you've found a bug, it is standard procedure for you to build the most recent version to test it and see if the bug is still there. So yes, I do expect people to build from SVN when they're about to report a bug, but no more often.
I don't expect this. I think a bug report against the latest released version is better than no bug report. If we think we've seen and fixed the bug in SVN, it takes us less time to reply "Hmmm, check this with the latest SVN" than it would take Zachary or another would-be bug reporter to check out and build the whole tree from SVN, just on the off-chance we've fixed it since then. This lowers the barrier to entry for helpers. Reading bug reports about the current released version can also be a helpful reminder to us of which bugs are still outstanding in the most recent release. -- Ed
Ed Schofield wrote:
No, I don't expect everyone to rebuild scipy every day. However, when you think you've found a bug, it is standard procedure for you to build the most recent version to test it and see if the bug is still there. So yes, I do expect people to build from SVN when they're about to report a bug, but no more often.
I don't expect this. I think a bug report against the latest released version is better than no bug report. If we think we've seen and fixed the bug in SVN, it takes us less time to reply "Hmmm, check this with the latest SVN" than it would take Zachary or another would-be bug reporter to check out and build the whole tree from SVN, just on the off-chance we've fixed it since then. This lowers the barrier to entry for helpers. Reading bug reports about the current released version can also be a helpful reminder to us of which bugs are still outstanding in the most recent release.
I don't want potential bug reports not to get filed, either. This is another advantage of the ticket system on the trac pages. The bug-reporter could just check that page to see if the problem has been fixed. Alternatively, the bug-reporter can do a search through the newsgroup to see if the problem has been talked about and reported as fixed. I think requiring all bug-reporters to build from SVN is a bit of a barrier that we don't want to push at this stage. Especially, when there may be many little bugs lurking from the transition. -Travis
Travis Oliphant wrote:
I don't want potential bug reports not to get filed, either. This is another advantage of the ticket system on the trac pages. The bug-reporter could just check that page to see if the problem has been fixed. Alternatively, the bug-reporter can do a search through the newsgroup to see if the problem has been talked about and reported as fixed.
I think requiring all bug-reporters to build from SVN is a bit of a barrier that we don't want to push at this stage. Especially, when there may be many little bugs lurking from the transition.
I worded myself poorly. I don't want people to forgo entering bugs in the tracker if they can't find the time to rebuild from SVN. But I do want them to try! -- Robert Kern robert.kern@gmail.com "In the fields of hell where the grass grows high Are the graves of dreams allowed to die." -- Richard Harter
participants (3)
-
Ed Schofield -
Robert Kern -
Travis Oliphant