On Fri, Aug 9, 2019 at 11:22 PM Steven D'Aprano <[email protected]> wrote: > > And this change won't fix that, because *good* paths that currently work > today will fail in the future, but *bad* paths that silently do the > wrong thing will continue to silently do the wrong thing.
Except that many paths can be both "good" and "bad", because paths have multiple components. So the warning has a VERY high probability of happening. But I've given up on this debate. No more posts from me. Some things aren't worth fighting for. With the number of words posted in this thread saying "we need convenience, not correctness!!!!", I'm done arguing. ChrisA _______________________________________________ Python-Dev mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/K4T7V5Z5GSGGK7HO73ZMFGTTAGMKHDE3/
