[Python-Dev] [python-committers] Reminder: 12 weeks to 3.7 feature code cutoff (original) (raw)
Stephen J. Turnbull turnbull.stephen.fw at u.tsukuba.ac.jp
Mon Nov 6 01:00:50 EST 2017
- Previous message (by thread): [Python-Dev] [python-committers] Reminder: 12 weeks to 3.7 feature code cutoff
- Next message (by thread): [Python-Dev] [python-committers] Reminder: 12 weeks to 3.7 feature code cutoff
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
-committers and some individuals dropped from address list.
Nick Coghlan writes:
Gah, seven years on from Python 2.7's release, I still get caught by that. I'm tempted to propose we reverse that decision and go back to enabling them by default :P
If app devs don't want their users seeing deprecation warnings, they can silence them globally during app startup, and end users can do the same in PYTHONSTARTUP for their interactive sessions.
This point was debated then, and there were good reasons why a lot of users can't/won't do this. The two I remember are (1) a lot of non-technical users use apps that aren't getting upgraded, and so will always emit those warnings, which often scare or confuse them, and (2) doing it in PYTHONSTARTUP is indeed global, and the kind of people who use interactive sessions typically want to see those warnings, but only some of them and only sometimes.
FWIW YMMV
Steve
- Previous message (by thread): [Python-Dev] [python-committers] Reminder: 12 weeks to 3.7 feature code cutoff
- Next message (by thread): [Python-Dev] [python-committers] Reminder: 12 weeks to 3.7 feature code cutoff
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]