Change by John Florian :
--
nosy: -John Florian
___
Python tracker
<https://bugs.python.org/issue14243>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from John Florian :
The docs say """The meaning of address is as in the constructor of IPv4Network,
except that arbitrary host addresses are always accepted."""
However, that doesn't seem to be entirely true:
>>> tup1 = ('192.168.123
New submission from John Florian :
I wanted a simple is_valid_ipv4_network() function, so I wrote one and a bunch
of unit tests where I discovered that I can legally:
>>> n = IPv4Network(('192.168.123.234', 12345678))
>>> n
IPv4Network('192.168.123.234/12345678')
>&g
John Florian added the comment:
Okay Nick. Thanks for the detailed info. I suspected buffering was a factor,
but wasn't certain. Would it be worthwhile pursuing a note in the docs or would
that constitute clutter over what should be a standard assumption? I was thrown
off course for all
John Florian added the comment:
I just stumbled onto this though I'm not writing for Windows. Instead, I'm on
Fedora 25 with Python 3.5.2 and I went nearly crazy tracing down what seemed to
be inconsistent behavior. My use case has Python using
NamedTemporaryFile(delete=True) in a CM
