array — Efficient arrays of numeric values¶
This module defines an object type which can compactly represent an array of basic values: characters, integers, floating point numbers. Arrays are sequence types and behave very much like lists, except that the type of objects stored in them is constrained. The type is specified at object creation time by using a type code, which is a single character. The following type codes are defined:
Type code |
C Type |
Python Type |
Minimum size in bytes |
Notes |
|---|---|---|---|---|
|
signed char |
int |
1 |
|
|
unsigned char |
int |
1 |
|
|
wchar_t |
Unicode character |
2 |
(1) |
|
signed short |
int |
2 |
|
|
unsigned short |
int |
2 |
|
|
signed int |
int |
2 |
|
|
unsigned int |
int |
2 |
|
|
signed long |
int |
4 |
|
|
unsigned long |
int |
4 |
|
|
signed long long |
int |
8 |
|
|
unsigned long long |
int |
8 |
|
|
float |
float |
4 |
|
|
double |
float |
8 |
Notes:
It can be 16 bits or 32 bits depending on the platform.
Changed in version 3.9:
array('u')now useswchar_tas C type instead of deprecatedPy_UNICODE. This change doesn’t affect to its behavior becausePy_UNICODEis alias ofwchar_tsince Python 3.3.Deprecated since version 3.3, will be removed in version 4.0.
The actual representation of values is determined by the machine architecture
(strictly speaking, by the C implementation). The actual size can be accessed
through the itemsize attribute.
The module defines the following type:
-
class
array.array(typecode[, initializer])¶ A new array whose items are restricted by typecode, and initialized from the optional initializer value, which must be a list, a bytes-like object, or iterable over elements of the appropriate type.
If given a list or string, the initializer is passed to the new array’s
fromlist(),frombytes(), orfromunicode()method (see below) to add initial items to the array. Otherwise, the iterable initializer is passed to theextend()method.Raises an auditing event
array.__new__with argumentstypecode,initializer.
-
array.typecodes¶ A string with all available type codes.
Array objects support the ordinary sequence operations of indexing, slicing,
concatenation, and multiplication. When using slice assignment, the assigned
value must be an array object with the same type code; in all other cases,
TypeError is raised. Array objects also implement the buffer interface,
and may be used wherever bytes-like objects are supported.
The following data items and methods are also supported:
-
array.typecode¶ The typecode character used to create the array.
-
array.itemsize¶ The length in bytes of one array item in the internal representation.
-
array.append(x)¶ Append a new item with value x to the end of the array.
-
array.buffer_info()¶ Return a tuple
(address, length)giving the current memory address and the length in elements of the buffer used to hold array’s contents. The size of the memory buffer in bytes can be computed asarray.buffer_info()[1] * array.itemsize. This is occasionally useful when working with low-level (and inherently unsafe) I/O interfaces that require memory addresses, such as certainioctl()operations. The returned numbers are valid as long as the array exists and no length-changing operations are applied to it.Note
When using array objects from code written in C or C++ (the only way to effectively make use of this information), it makes more sense to use the buffer interface supported by array objects. This method is maintained for backward compatibility and should be avoided in new code. The buffer interface is documented in Buffer Protocol.
-
array.byteswap()