commit | b16352a8cefb6ae1055411e15bf15381c54888cd | [log] [tgz] |
---|---|---|
author | Steven Laver <lavers@google.com> | Sat Nov 09 19:05:01 2019 -0800 |
committer | Steven Laver <lavers@google.com> | Sat Nov 09 19:05:01 2019 -0800 |
tree | e9fb14bd73b8f85c9c77b77ad76e7870a356acf0 | |
parent | 3884a8f51eacf4a5acc3749f6955a3c32652fc21 [diff] | |
parent | 0cf4bb3def7b80637e28106d1f8404d55d9537d3 [diff] |
Merge RP1A.191031.003 Change-Id: I5d4475cfcb87a55b8f26e1342222cdf6a94e57d3
Python 3.3+'s ipaddress for Python 2.6, 2.7, 3.2.
This repository tracks the latest version from cpython, e.g. ipaddress from cpython 3.8 as of writing.
Note that just like 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?