This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author dsvensson
Recipients dsvensson, georg.brandl
Date 2009-06-02.08:06:04
SpamBayes Score 3.996197e-05
Marked as misclassified No
Message-id <1243929967.67.0.34945506806.issue6175@psf.upfronthosting.co.za>
In-reply-to
Content
The documentation for inet_aton specifically says that it's used to
"Convert an IPv4 address from dotted-quad string format". This however
is not really true, it does accept dotted-quad, but not dotted-quad
alone, but also these forms from inet(3) man page:

       a.b.c.d   Each of the four numeric parts specifies a byte of the
address; the bytes are assigned in left-to-right order to produce the
binary address.

       a.b.c     Parts a and b specify the first two bytes of the binary
address.  Part c is interpreted as a 16-bit value that defines the
rightmost two bytes of the binary address.  This notation is suitable
for specifying (outmoded) Class B network addresses.

       a.b       Part a specifies the first byte of the binary address.
 Part b is interpreted as a 24-bit value that defines the rightmost
three bytes of the binary address.  This notation is suitable for
specifying (outmoded) Class C network addresses.

       a         The value a is interpreted as a 32-bit value that is
stored directly into the binary address without any byte rearrangement.

Sure, it references the man-page, but if anything it should say among
the formats it supports, dotted-quad is *one* of them.

http://docs.python.org/library/socket.html#socket.inet_aton
History
Date User Action Args
2009-06-02 08:06:07dsvenssonsetrecipients: + dsvensson, georg.brandl
2009-06-02 08:06:07dsvenssonsetmessageid: <1243929967.67.0.34945506806.issue6175@psf.upfronthosting.co.za>
2009-06-02 08:06:06dsvenssonlinkissue6175 messages
2009-06-02 08:06:04dsvenssoncreate