One thought that came to mind as perhaps a way more in line with how other
parts of python work, is to extend the “name mangling” aspect of __ to this
sort of context. (Just __ at the beginning, not both before and after).
In class members these become _ClassName_, and thus a subclass trying to
Can you articulate where such a “private” flag would be benefiting developers
in a use case?
From my initial view on reading this you have documented the convention for
marking something as designed for internal use / don’t rely on this being
available. However users of the library can still lo
> On Nov 21, 2025, at 4:20 PM, Bjørnar Remmen via Python-list
> wrote:
>
> I would like to open up for a discussion on how we can introduce a way to
> hide imports.
>
My first thought is this isn’t the way Python tends to do things, and what it
means to implement this is that a lookup in a
Hi, this is my first time here on the mailing list.
I would like to open up for a discussion on how we can introduce a way to hide
imports.
I am proposing the introduction of an optional, non-breaking keyword, private,
to be used when importing a file. The goal is to allow developer to hide
in
