Bytes#
Added in version 2.32.
- class Bytes(**kwargs)#
A simple reference counted data type representing an immutable sequence of zero or more bytes from an unspecified origin.
The purpose of a GBytes is to keep the memory region that it holds
alive for as long as anyone holds a reference to the bytes. When
the last reference count is dropped, the memory is released. Multiple
unrelated callers can use byte data in the GBytes without coordinating
their activities, resting assured that the byte data will not change or
move while they hold a reference.
A GBytes can come from many different origins that may have
different procedures for freeing the memory region. Examples are
memory from malloc, from memory slices, from a
MappedFile or memory from other allocators.
GBytes work well as keys in HashTable. Use
equal and hash as parameters to
new or new_full.
GBytes can also be used as keys in a Tree by passing the
compare function to new.
The data pointed to by this bytes must not be modified. For a mutable
array of bytes see ByteArray. Use
unref_to_array to create a mutable array for a GBytes
sequence. To create an immutable GBytes from a mutable
ByteArray, use the free_to_bytes
function.
Constructors#
- class Bytes
- classmethod new(data: list[int] | None = None) Bytes#
Creates a new
Bytesfromdata.datais copied. Ifsizeis 0,datamay beNULL.As an optimization,
newmay avoid an extra allocation by copying the data within the resulting bytes structure if sufficiently small (since GLib 2.84).Added in version 2.32.
- Parameters:
data – the data to be used for the bytes
- classmethod new_from_bytes(bytes: Bytes, offset: int, length: int) Bytes#
Creates a
Byteswhich is a subsection of anotherGBytes.The
offset+lengthmay not be longer than the size ofbytes.A reference to
byteswill be held by the newly createdGBytesuntil the byte data is no longer needed.Since 2.56, if
offsetis 0 andlengthmatches the size ofbytes, thenbyteswill be returned with the reference count incremented by 1. Ifbytesis a slice of anotherGBytes, then the resultingGByteswill reference the sameGBytesinstead ofbytes. This allows consumers to simplify the usage ofGByteswhen asynchronously writing to streams.Added in version 2.32.
- Parameters:
bytes – a
Bytesoffset – offset which subsection starts at
length – length of subsection
- classmethod new_take(data: list[int] | None = None) Bytes#
Creates a new
Bytesfromdata.After this call,
databelongs to theGBytesand may no longer be modified by the caller. The memory ofdatahas to be dynamically allocated and will eventually be freed withfree.For creating
GByteswith memory from other allocators, seenew_with_free_func.datamay beNULLifsizeis 0.Added in version 2.32.
- Parameters:
data – the data to be used for the bytes
Methods#
- class Bytes
- compare(bytes2: Bytes) int#
Compares the two
Bytesvalues.This function can be used to sort
GBytesinstances in lexicographical order.If
bytes1andbytes2have different length but the shorter one is a prefix of the longer one then the shorter one is considered to be less than the longer one. Otherwise the first byte where both differ is used for comparison. Ifbytes1has a smaller value at that position it is considered less, otherwise greater thanbytes2.Added in version 2.32.
- Parameters:
bytes2 – a pointer to a
Bytesto compare withbytes1
- equal(bytes2: Bytes) bool#
Compares the two
Bytesvalues being pointed to and returnsTRUEif they are equal.This function can be passed to
newas thekey_equal_funcparameter, when using non-NULLGBytespointers as keys in aHashTable.Added in version 2.32.
- Parameters:
bytes2 – a pointer to a
Bytesto compare withbytes1
- get_data() list[int] | None#
Get the byte data in the
Bytes.This data should not be modified.
This function will always return the same pointer for a given
GBytes.NULLmay be returned ifsizeis 0. This is not guaranteed, as theGBytesmay represent an empty string withdatanon-NULLandsizeas 0.NULLwill not be returned ifsizeis non-zero.Added in version 2.32.
- get_region(element_size: int, offset: int, n_elements: int) Any | None#
Gets a pointer to a region in
bytes.The region starts at
offsetmany bytes from the start of the data and containsn_elementsmany elements ofelement_sizesize.n_elementsmay be zero, butelement_sizemust always be non-zero. Ideally,element_sizeis a static constant (eg:sizeofa struct).This function does careful bounds checking (including checking for arithmetic overflows) and returns a non-
NULLpointer if the specified region lies entirely within thebytes. If the region is in some way out of range, or if an overflow has occurred, thenNULLis returned.Note: it is possible to have a valid zero-size region. In this case, the returned pointer will be equal to the base pointer of the data of
bytes, plusoffset. This will be non-NULLexcept for the case wherebytesitself was a zero-sized region. Since it is unlikely that you will be using this function to check for a zero-sized region in a zero-sizedbytes,NULLeffectively always means ‘error’.Added in version 2.70.
- Parameters:
element_size – a non-zero element size
offset – an offset to the start of the region within the
bytesn_elements – the number of elements in the region