From regebro at gmail.com  Tue Oct  1 17:24:47 2019
From: regebro at gmail.com (Lennart Regebro)
Date: Tue, 1 Oct 2019 23:24:47 +0200
Subject: [Python-porting] obsolete Python 2 builtin
In-Reply-To: <CAKgNTd+tVrBXZ8Ks3VHwkG6RVa63YJKsZczmvKonV80UbtXdgQ@mail.gmail.com>
References: <CAKgNTd+tVrBXZ8Ks3VHwkG6RVa63YJKsZczmvKonV80UbtXdgQ@mail.gmail.com>
Message-ID: <CAL0kPAVGu_y2h3AKfgC+d+umosHdz5kmHz1anzTV4w7Y06+q8g@mail.gmail.com>

On Tue, Oct 1, 2019 at 8:42 PM Wayne Cass via Python-porting
<python-porting at python.org> wrote:
>
> Hi
>
> I understood, that by using:
> from future.builtins.disabled import *
>
> I would get NameError: obsolete Python 2 builtin apply is disabled, for modules, which are not compatible with Python3.X

Only if you actually try to use any of the disabled builtins.
And why would you want that? It's easier to just not use the builtin
in question.

> ModuleNotFoundError: No module named 'future'

It looks like the future module isn't installed with the Python
installation you are using.