I have a question about python naming conventions. The answer is readily available on the Python documentation, but I think it would make for a great Stack Overflow question. Is it ok to still ask it?
Then there is no need to ask a question about it. Stack Overflow does not exist to copy existing documentation.
Let's turn it around a bit. Say you asked the question. The answer would really be "well, that's explicitly stated in the documentation". Which in turn would mean your research has been insufficient, which might well see your question downvoted.
So in short, if the question doesn't really add anything that exceeds the current documentation, don't ask it.
Well, it depends.
Documentation sometimes sucks. I'm presently thinking of the AngularJS documentation. Invariably, documentation pre-supposes that you know what it refers to. It's not generally made for the person who doesn't understand the system they're dealing with.
In the cases where the documentation does not adequately explain or cover a topic well, I fully expect people to have questions about it, and I hope they ask those questions on Stack Overflow. I think of Stack Overflow like BASF for documentation. We don't make documentation. We make documentation better.
So long as your question pertaining to documentation:
In this case, your question is about naming conventions. By and large, this is a style issue (and even where it's not, it's generally one of the things documentation gets right). Because of these factors, it is not a good question for Stack Overflow.
If the answer can easily be found in the official documentation, then it wouldn't make a good Stack Overflow question. If you have to piece together a solution from several sources that you find on Google, then you might have a good question/answer to post.