I'm still not clear on what the problem is with a function that prints code to be copy pasted. It should probably output to stderr rather than stdout, and maybe that can be configurable, but I don't think that's what your problem is.
I think that even if you've filtered warnings before, it's hard to remember how and looking it up is still reasonably difficult and tedious. Solving this problem by improving documentation is a delicate art that's difficult to measure and easy to get wrong, and it can only improve the situation somewhat. I'm not against it, but someone has to volunteer to do it, and I'm expecting it's just not going to happen. On the other hand, the goal of this proposal is that once you've looked up the function once, you have a decent chance of remembering it without looking it up again. It could also be a primary target to attract user attention while browsing through documentation, making the lookup process easier. Yes, that was the stackoverflow question I was referring to, and I think that comment is too far down to be sufficiently noticeable. You can see from the comment upvotes that most people are very happy to filter an entire category and leave it at that. > While I agree in general I think I'm missing something because in the rest of the paragraph it just sounds like you continue to agree with me in the specifics as well. _______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/HNONAR4LZSJ4SQIEW3F5A5DWHRKRSR7L/ Code of Conduct: http://python.org/psf/codeofconduct/
