The fact of explicit dependency noting is why I suggested something that
explicitly defines multiple imports in one line
On Sat, Apr 28, 2018 at 9:28 PM Greg Ewing
wrote:
> Nick Coghlan wrote:
> > I find the imports at the top of the file to be a nice
> > catalog of external dependencies.
>
> No
> On 26 April 2018 at 14:29, Julian DeMille via Python-ideas
> > wrote:
> >> I personally would like a feature where instead of doing `from ...
> import
> >> ...` (which imports the specified items into the current namespace), one
> >> could use something a
Some library authors get pretty pissy about implicit imports at the root
On Thu, Apr 26, 2018, 09:37 Paul Moore wrote:
> On 26 April 2018 at 14:29, Julian DeMille via Python-ideas
> wrote:
> > I personally would like a feature where instead of doing `from ... import
> > ...`
I personally would like a feature where instead of doing `from ... import
...` (which imports the specified items into the current namespace), one
could use something along the lines of `import .{ , , ...
}` such that the imported modules/attributes could be accessed as
`.`, etc.
--
Thanks,
Julian