New submission from FeRD (Frank Dana) :
socket._GLOBAL_DEFAULT_TIMEOUT's status as a bare object() instance has been
brought up before (bpo-12441). That was reported as a bug, but appeared to stem
from developer confusion, so it was correctly closed as "not a bug". At the
time
FeRD (Frank Dana) added the comment:
Readding Tal to the nosy list, since my previous comment was inadvertently
accompanied by an eviction! (Sorry about that.)
--
nosy: +taleinat
___
Python tracker
<https://bugs.python.org/issue46
FeRD (Frank Dana) added the comment:
Maybe,
"""
This won’t work for __main__.py files in the root directory of a .zip file
though. Thus, for consistency, it is usually preferred to place code in other
modules. That code can then be invoked from a minima
FeRD (Frank Dana) added the comment:
TBH, personally I don't think I'd just reword it with "below". That seems like
the path of least resistance, but then the sentence becomes this:
"""
This won’t work for __main__.py files in the root directory of a .zip file
thoug
New submission from FeRD (Frank Dana) :
The expanded documentation on top-level environments is quite an improvement,
but there's one passage that causes some confusion. In the section '__main__.py
in Python Packages', towards the end, it reads:
"""
This won’t work for __
