This is awesome. If there isn't more feedback in the next few days expect
an approval early next week. (Ping me if you don't hear from me, I'm
juggling way too many small tasks so I'm likely to forget some.)
On Tue, Nov 28, 2017 at 3:00 AM, Nick Coghlan wrote:
> On 28 November 2017 at 09:52, Gui
On 28 November 2017 at 09:52, Guido van Rossum wrote:
> I am basically in agreement with this now. Some remarks:
I've pushed an update which should address most of these, as well as
Serhiy's comment about the existing FutureWarning use case:
https://github.com/python/peps/commit/aaa64f53d04347243
25.11.17 07:33, Nick Coghlan пише:
* ``FutureWarning``: always reported by default. The intended audience is users
of applications written in Python, rather than other Python developers
(e.g. warning about use of a deprecated setting in a configuration file
format).
Given its presence i
I am basically in agreement with this now. Some remarks:
- I would recommend adding a note to the abstract about the recommendation
for test runners to also enable these warnings by default.
- In some sense, simple scripts that are distributed informally (e.g. as
email attachments or via shared d
This is a new version of the proposal to show DeprecationWarning in __main__.
The proposal itself hasn't changed (it's still recommending a new
entry in the default filter list), but there have been several updates
to the PEP text based on further development work and comments in the
initial threa
