python-docs-ko/howto/ipaddress.po at 3.6 · python/python-docs-ko

313 lines (265 loc) · 10.4 KB
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001-2017, Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2017.
"Project-Id-Version: Python 3.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-11-26 18:49+0900\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.5.1\n"
#: ../Doc/howto/ipaddress.rst:9
msgid "An introduction to the ipaddress module"
#: ../Doc/howto/ipaddress.rst
msgid "author"
#: ../Doc/howto/ipaddress.rst:11
msgid "Peter Moody"
#: ../Doc/howto/ipaddress.rst:12
msgid "Nick Coghlan"
#: ../Doc/howto/ipaddress.rst:16
"This document aims to provide a gentle introduction to the "
":mod:`ipaddress` module. It is aimed primarily at users that aren't "
"already familiar with IP networking terminology, but may also be useful "
"to network engineers wanting an overview of how :mod:`ipaddress` "
"represents IP network addressing concepts."
#: ../Doc/howto/ipaddress.rst:24
msgid "Creating Address/Network/Interface objects"
#: ../Doc/howto/ipaddress.rst:26
"Since :mod:`ipaddress` is a module for inspecting and manipulating IP "
"addresses, the first thing you'll want to do is create some objects.  You"
" can use :mod:`ipaddress` to create objects from strings and integers."
#: ../Doc/howto/ipaddress.rst:32
msgid "A Note on IP Versions"
#: ../Doc/howto/ipaddress.rst:34
"For readers that aren't particularly familiar with IP addressing, it's "
"important to know that the Internet Protocol is currently in the process "
"of moving from version 4 of the protocol to version 6. This transition is"
" occurring largely because version 4 of the protocol doesn't provide "
"enough addresses to handle the needs of the whole world, especially given"
" the increasing number of devices with direct connections to the "
"internet."
#: ../Doc/howto/ipaddress.rst:41
"Explaining the details of the differences between the two versions of the"
" protocol is beyond the scope of this introduction, but readers need to "
"at least be aware that these two versions exist, and it will sometimes be"
" necessary to force the use of one version or the other."
#: ../Doc/howto/ipaddress.rst:48
msgid "IP Host Addresses"
#: ../Doc/howto/ipaddress.rst:50
"Addresses, often referred to as \"host addresses\" are the most basic "
"unit when working with IP addressing. The simplest way to create "
"addresses is to use the :func:`ipaddress.ip_address` factory function, "
"which automatically determines whether to create an IPv4 or IPv6 address "
"based on the passed in value:"
#: ../Doc/howto/ipaddress.rst:61
"Addresses can also be created directly from integers. Values that will "
"fit within 32 bits are assumed to be IPv4 addresses::"
#: ../Doc/howto/ipaddress.rst:69
"To force the use of IPv4 or IPv6 addresses, the relevant classes can be "
"invoked directly. This is particularly useful to force creation of IPv6 "
"addresses for small integers::"
#: ../Doc/howto/ipaddress.rst:82
msgid "Defining Networks"
#: ../Doc/howto/ipaddress.rst:84
"Host addresses are usually grouped together into IP networks, so "
":mod:`ipaddress` provides a way to create, inspect and manipulate network"
" definitions. IP network objects are constructed from strings that define"
" the range of host addresses that are part of that network. The simplest "
"form for that information is a \"network address/network prefix\" pair, "
"where the prefix defines the number of leading bits that are compared to "
"determine whether or not an address is part of the network and the "
"network address defines the expected value of those bits."
#: ../Doc/howto/ipaddress.rst:93
"As for addresses, a factory function is provided that determines the "
"correct IP version automatically::"
#: ../Doc/howto/ipaddress.rst:101
"Network objects cannot have any host bits set.  The practical effect of "
"this is that ``192.0.2.1/24`` does not describe a network.  Such "
"definitions are referred to as interface objects since the ip-"
"on-a-network notation is commonly used to describe network interfaces of "
"a computer on a given network and are described further in the next "
#: ../Doc/howto/ipaddress.rst:107
"By default, attempting to create a network object with host bits set will"
" result in :exc:`ValueError` being raised. To request that the additional"
" bits instead be coerced to zero, the flag ``strict=False`` can be passed"
" to the constructor::"
#: ../Doc/howto/ipaddress.rst:119
"While the string form offers significantly more flexibility, networks can"
" also be defined with integers, just like host addresses. In this case, "
"the network is considered to contain only the single address identified "
"by the integer, so the network prefix includes the entire network "
"address::"
#: ../Doc/howto/ipaddress.rst:129
"As with addresses, creation of a particular kind of network can be forced"
" by calling the class constructor directly instead of using the factory "
"function."
#: ../Doc/howto/ipaddress.rst:135
msgid "Host Interfaces"
#: ../Doc/howto/ipaddress.rst:137
"As mentioned just above, if you need to describe an address on a "
"particular network, neither the address nor the network classes are "
"sufficient. Notation like ``192.0.2.1/24`` is commonly used by network "
"engineers and the people who write tools for firewalls and routers as "
"shorthand for \"the host ``192.0.2.1`` on the network ``192.0.2.0/24``\","
" Accordingly, :mod:`ipaddress` provides a set of hybrid classes that "
"associate an address with a particular network. The interface for "
"creation is identical to that for defining network objects, except that "
"the address portion isn't constrained to being a network address."
#: ../Doc/howto/ipaddress.rst:152
"Integer inputs are accepted (as with networks), and use of a particular "
"IP version can be forced by calling the relevant constructor directly."
#: ../Doc/howto/ipaddress.rst:157
msgid "Inspecting Address/Network/Interface Objects"
#: ../Doc/howto/ipaddress.rst:159
"You've gone to the trouble of creating an "
"IPv(4|6)(Address|Network|Interface) object, so you probably want to get "
"information about it.  :mod:`ipaddress` tries to make doing this easy and"
" intuitive."
#: ../Doc/howto/ipaddress.rst:163
msgid "Extracting the IP version::"
#: ../Doc/howto/ipaddress.rst:172
msgid "Obtaining the network from an interface::"
#: ../Doc/howto/ipaddress.rst:181
msgid "Finding out how many individual addresses are in a network::"
#: ../Doc/howto/ipaddress.rst:190
msgid "Iterating through the \"usable\" addresses on a network::"
#: ../Doc/howto/ipaddress.rst:205
"Obtaining the netmask (i.e. set bits corresponding to the network prefix)"
" or the hostmask (any bits that are not part of the netmask):"
#: ../Doc/howto/ipaddress.rst:220
msgid "Exploding or compressing the address::"
#: ../Doc/howto/ipaddress.rst:231
"While IPv4 doesn't support explosion or compression, the associated "
"objects still provide the relevant properties so that version neutral "
"code can easily ensure the most concise or most verbose form is used for "
"IPv6 addresses while still correctly handling IPv4 addresses."
#: ../Doc/howto/ipaddress.rst:238
msgid "Networks as lists of Addresses"
#: ../Doc/howto/ipaddress.rst:240
"It's sometimes useful to treat networks as lists.  This means it is "
"possible to index them like this::"
#: ../Doc/howto/ipaddress.rst:253
"It also means that network objects lend themselves to using the list "
"membership test syntax like this::"
#: ../Doc/howto/ipaddress.rst:259
msgid "Containment testing is done efficiently based on the network prefix::"
#: ../Doc/howto/ipaddress.rst:269
msgid "Comparisons"
#: ../Doc/howto/ipaddress.rst:271
":mod:`ipaddress` provides some simple, hopefully intuitive ways to "
"compare objects, where it makes sense::"
#: ../Doc/howto/ipaddress.rst:277
"A :exc:`TypeError` exception is raised if you try to compare objects of "
"different versions or different types."
#: ../Doc/howto/ipaddress.rst:282
msgid "Using IP Addresses with other modules"
#: ../Doc/howto/ipaddress.rst:284
"Other modules that use IP addresses (such as :mod:`socket`) usually won't"
" accept objects from this module directly. Instead, they must be coerced "
"to an integer or string that the other module will accept::"
#: ../Doc/howto/ipaddress.rst:296
msgid "Getting more detail when instance creation fails"
#: ../Doc/howto/ipaddress.rst:298
"When creating address/network/interface objects using the version-"
"agnostic factory functions, any errors will be reported as "
":exc:`ValueError` with a generic error message that simply says the "
"passed in value was not recognized as an object of that type. The lack of"
" a specific error is because it's necessary to know whether the value is "
"*supposed* to be IPv4 or IPv6 in order to provide more detail on why it "
"has been rejected."
#: ../Doc/howto/ipaddress.rst:305
"To support use cases where it is useful to have access to this additional"
" detail, the individual class constructors actually raise the "
":exc:`ValueError` subclasses :exc:`ipaddress.AddressValueError` and "
":exc:`ipaddress.NetmaskValueError` to indicate exactly which part of the "
"definition failed to parse correctly."
#: ../Doc/howto/ipaddress.rst:311
"The error messages are significantly more detailed when using the class "
"constructors directly. For example::"
#: ../Doc/howto/ipaddress.rst:332
"However, both of the module specific exceptions have :exc:`ValueError` as"
" their parent class, so if you're not concerned with the particular type "
"of error, you can still write code like the following::"
Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

FilesExpand file tree

ipaddress.po

Latest commit

History

ipaddress.po

File metadata and controls
