Stefan Krah added the comment: Martin v. L??wis <rep...@bugs.python.org> wrote: > I don't mind that at all, either. What I dislike is "I have this issue, > here is what I've got, and I will continue to work on it" kind of reports > (when Dave clearly said that his patch is work-in-progress). There is a > worse kind, where people say "I have this issue", followed (after 15 minutes) > with "I found out more", and then going on with that for a while. I feel > that this wastes the reader's time (who may actually start to work on the > issue as well, duplicating efforts) - this is something that submitters > really need to consider. It's not this bad in this issue, since Dave said > from the beginning that it is work-in-progress.
I think Dave's main issue was: Here's a problem with NumPy/3.3, could we perhaps remove an assert() to keep NumPy working. That was the one-liner patch. The NumPy patches were probably there for illustration. -- It might be unusual to post patches for third party packages on the tracker, but NumPy is in a very special situation right now: Version 1.7 is about to be released and is currently not 3.3 compatible. As Nick said, NumPy is a blocker for Python-3.3 integration into Fedora. So, I hope that Travis doesn't mind if people keep pushing the issue a bit. On the positive side, it's a sign that people care a lot about NumPy. > On-topic: what action do you suggest for this issue? As for the action, I think everyone agrees that no changes to Python are necessary. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15540> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
