Movatterモバイル変換
[0]ホーム
[Python-Dev] Proposal: go back to enabling DeprecationWarning by default
Nick Coghlanncoghlan 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 thatexperience is up to the developers of those applications. This is nodifferent from the user experience of Instagram being Facebook'sproblem, the user experience of RHEL being Red Hat's problem, the userexperience of YouTube being Google's problem, etc.*python-dev's* users are developers, data analysts, educators, and soforth that are actually writing Python code, and at the moment we'remaking it hard for them to be suitably forewarned of upcoming breakingchanges - they have to know the secret knock that says "I'd like to bewarned about future breaking changes, please". Sure, a lot of peopledo learn what that knock is, and they often even remember to ask forit, but the entire reason this thread started was because *I* forgotthat I needed to run "python3 -Wd" in order to check for async/awaitdeprecation warnings in 3.6, and incorrectly assumed that theirabsence meant we'd forgotten to include them.Cheers,Nick.-- Nick Coghlan |ncoghlan at gmail.com | Brisbane, Australia
More information about the Python-Devmailing list
[8]ページ先頭