[Python-Dev] Proposal: go back to enabling DeprecationWarning by default (original) (raw)

Nick Coghlan ncoghlan at gmail.com
Tue Nov 7 08:57:46 EST 2017

On 7 November 2017 at 23:44, Paul Moore <p.f.moore at gmail.com> wrote:

As I say, the proposal prioritises developer convenience over end user experience.

Users of applications written in Python are not python-dev's users: they're the users of those applications, and hence the quality of that experience is up to the developers of those applications. This is no different from the user experience of Instagram being Facebook's problem, the user experience of RHEL being Red Hat's problem, the user experience of YouTube being Google's problem, etc.

python-dev's users are developers, data analysts, educators, and so forth that are actually writing Python code, and at the moment we're making it hard for them to be suitably forewarned of upcoming breaking changes - they have to know the secret knock that says "I'd like to be warned about future breaking changes, please". Sure, a lot of people do learn what that knock is, and they often even remember to ask for it, but the entire reason this thread started was because I forgot that I needed to run "python3 -Wd" in order to check for async/await deprecation warnings in 3.6, and incorrectly assumed that their absence meant we'd forgotten to include them.

Cheers, Nick.

-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia

More information about the Python-Dev mailing list