Usual reason for deprecation is not removing functionality, but to replace OldBusted eay of doing things with NewHotness way of things - so you should actially not despair if you see a deprecation warning but rather cherish the new and much easier way to accomplish your tasks.
Emerging design leads to warts that need to be ironed out at some point to keep the code maintainable and accessible for newcomers.
Want to know how to do it right/gentle might be boring, annoying for old hands but for me something where i feel i could be useful.
I would be interested to 'sell' the new policy to users (especially that we're aware of the pain and that we will not flood them with 'clusters of deprecation' (good name for a progressive death metal band)
users relax: pytest 3.0 != python 3.0