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 har
> Adding *more* documentation can easily make the problem worse in some
ways. We're dealing with the very tricky problem of directing and
sustaining attention.
Improving the existing docs doesn't necessarily mean adding more in terms
to length or total content, even if an example or two were added
Kyle Stanley wrote:
> Hmm, I think we may benefit from focusing the efforts on this point (at
> least at first), particularly with regards to making the official
> documentation for the warnings module [1] easier to understand with some
> more examples, or perhaps writing a warnings HOWTO guide [2]
> 2. Looking it up is hard. If I Google "python ignore warnings" the top
result is a Stack Overflow question where neither the accepted answer nor
the most upvoted answer mention specifying a module. The second Google
result is the Python docs which are not easy to read through.
Hmm, I think we ma
