On 2023-05-19 00:54, Greg Ewing wrote:
On 19/05/23 4:16 am, Christopher Barker wrote:
The problem with "batteries included" is that what exactly is a
battery is hard to define, and everyone has a different opinion about it.
To my mind, "batteries included" means you can do *something*
useful
On 19/05/23 4:16 am, Christopher Barker wrote:
The problem with "batteries included" is that what exactly is a
battery is hard to define, and everyone has a different opinion about it.
To my mind, "batteries included" means you can do *something*
useful with it out of the box. It doesn't mean
A simple virtual package could be:
# foo.py
__path__ = [__file__ + ".d"]
But unfortunately this doesn't work with -m:
# foo.py.d/__main__.py
print("this will never run")
(n.b. -m foo.__main__ works but nobody's writing that.)
Is it possible to change this backwards-compatibly? If not, is it
The problem with "batteries included" is that what exactly is a battery is
hard to define, and everyone has a different opinion about it.
It's my observation that in recent (~10?) years, the core devs are pretty
carfeul about including anything new in teh stdlib -- it has its upsides,
for sure,
