commit | 6b68a95f1b0ad62baf22578ede4b97d1c93f11f0 | [log] [tgz] |
---|---|---|
author | Philipp Hagemeister <phihag@phihag.de> | Sat Apr 14 19:53:49 2018 +0200 |
committer | Philipp Hagemeister <phihag@phihag.de> | Sat Apr 14 19:53:51 2018 +0200 |
tree | 2f06b298a23f04dd063a708a8ebf6df2470aaa08 | |
parent | 29604361a18d5dbf81d12b3a65d8ebecccda1dc4 [diff] |
release 1.0.21 I forgot to update the version number in setup.py, so bump version to 1.0.21 to make sure that this correct and complete release is actually recorded in a commit.
Python 3.3+'s ipaddress for Python 2.6, 2.7, 3.2.
Note that as in Python 3.3+ you must use character strings and not byte strings for textual IP address representations:
>>> from __future__ import unicode_literals >>> ipaddress.ip_address('1.2.3.4') IPv4Address(u'1.2.3.4')
or
>>> ipaddress.ip_address(u'1.2.3.4') IPv4Address(u'1.2.3.4')
but not:
>>> ipaddress.ip_address(b'1.2.3.4') Traceback (most recent call last): File "<stdin>", line 1, in <module> File "ipaddress.py", line 163, in ip_address ' a unicode object?' % address) ipaddress.AddressValueError: '1.2.3.4' does not appear to be an IPv4 or IPv6 address. Did you pass in a bytes (str in Python 2) instead of a unicode object?