Skip to main content

uproot extension for reading custom classes

Project description

uproot-custom

This is a prototype repository of an extension that allows uproot to read custom classes from ROOT files.

uproot can already read some custom classes directly. However, in some cases, custom classes are too complex for uproot to read, such as when their Streamer methods are overridden or some specific data members are not supported by uproot.

This extension privides a Reader interface and allows you to read such custom classes by providing your own Reader. The Reader interface defines how to read the data members of a class from the binary stream.

Design overview

In ROOT, data are stored in a tree structure. For example, when a custom class is defined as:

class TMySubClass : public TObject {
    int m_index;
    float m_x;
};

class TMyClass : public TObject {
    double m_energy;
    std::vector<MySubClass> m_daughters;
};

The data tree is:

graph TD
    A([TMyClass]) --> B(double m_energy)
    A --> C(std::vector&lt;TMySubClass&gt; m_daughters)
    C --> D([TMySubClass])
    D --> E(int m_index)
    D --> F(float m_x)

To handle the tree-like data structure, Reader is introduced. It consists of Python and C++ parts. The Python part is responsible for generating the information tree, constructing C++ readers, and reconstructing data to awkward array. The C++ part is responsible for reading the data members of the class from the binary stream.

Generate information tree

uproot can read these structure information from the ROOT file, but not in tree format. So the first step is to generate an information tree from the ROOT file. The information tree is a nested structure that contains the data members of the class, including types, names and children if any.

Construct C++ readers

According to the information tree, we can instantiate C++ readers and combine them into a tree structure. The top reader drives its sub-readers to read data recursively. After the reading process, readers obtain the results from their sub-readers recursively, then the top reader returns the final result.

Reconstruct data to awkward array

Since embedding arrays together into awkward array in C++ is not straightforward, we left this task to Python. After the C++ reader returns the result, we can reconstruct the data into awkward array according to the information tree.

Predefined readers

uproot-custom provides some predefined readers for common ROOT classes:

Reader Description
BasicTypeReader Reads basic types like int, float, double, etc.
TObjectReader Skip TObject header when reading classes that inherit from TObject.
TStringReader Reads TString
STLSeqReader Reads std::vector, std::array, etc.
STLMapReader Reads std::map, std::unordered_map, etc.
STLStringReader Reads std::string
TArrayReader Reads TArray types like TArrayI, TArrayF, TArrayD, etc.
ObjectReader Reads custom classes that inherit from TObject.
CArrayReader Reads C-style arrays like int[]
EmptyReader A reader that does nothing. Some branches may not have any data, and the information of the corresponding class will not be stored in the ROOT file. In this case, EmptyReader is used to skip the branch.

Implement your own Reader

Full example

A complete example of how to impolement your own readers is available in the example directory of this repository.

Pre-requisites

Make sure you have GCC>13.1/Clang>=16.0.0/MSVC>=19.31, cmake installed on your system.

  1. Create a Python project and install uproot-custom:

    mkdir my_reader
    cd my_reader
    python3 -m venv .venv
    source .venv/bin/activate
    pip install uproot-custom
    
  2. Create a pyproject.toml file in the root directory of your project:

    [build-system]
    requires = ["scikit-build-core>=0.11", "pybind11>=2.10.0", "uproot-custom"]
    build-backend = "scikit_build_core.build"
    
    [project]
    name = "my-reader"
    requires-python = ">=3.9"
    dependencies = ["uproot-custom"]
    version = "0.1.0"
    
    [tool.scikit-build]
    wheel.packages = ["my_reader"]
    build-dir = "build/{wheel_tag}"
    cmake.source-dir = "cpp"
    cmake.build-type = "Debug" # Comment for release builds
    
    [tool.black]
    exclude = "/(build|dist|env|.git|.tox|.eggs|.venv)/"
    line-length = 95
    target-version = ['py39', 'py310', 'py311', 'py312', 'py313']
    

    you can change the name, version, and other fields as you like.

Reader interface

For a custom Reader, a C++ part and a Python part are both required.

For C++ part, the constructor must inherit from IElementReader, and these methods must be implemented:

  • void read(BinaryBuffer& buffer): Read data from the binary buffer.
  • py::object data() const: Return the data as a Python object. You can return anything defined in pybind11, such as py::tuple, py::list, py::array_t, etc.

For Python part, the class must inherit from uproot_custom.BaseReader and implement the following class methods:

  • gen_tree_config: Generate a configuration dictionary for the reader based on the information tree. It should return a dictionary if you want your reader to be used, otherwise return None.
  • get_cpp_reader: Identify the tree configuration and return the C++ reader instance if it matches, otherwise return None.
  • reconstruct_array: Reconstruct the raw data to an awkward array according to the tree configuration.

Implement the C++ reader

  1. Create a cpp directory in the root directory of your project, and create a my_reader.cc file in it.

  2. In my_reader.cc, include the necessary headers and implement your reader class. For example:

    #include "uproot-custom/uproot-custom.hh"
    using namespace uproot;
    
    class MyReader : public IElementReader {
        public:
            // Must at least receive a name
            MyReader( std::string name )
                : IElementReader(name), m_data( std::make_shared<std::vector<int>>() ) {}
    
            // Implement these methods
            void read( BinaryBuffer& buffer ) {
                // Read data from the buffer
                // Implement your reading logic here
            }
    
            py::object data() const {
                // Return the data as a Python object
                return make_array( m_data );
            }
    
        private:
            const std::string m_name;
            std::shared_ptr<std::vector<int>> m_data; // Example data member
    };
    

    then declare the C++ module in the same file:

    PYBIND11_MODULE( my_reader_cpp, m ) {
        register_reader<MyReader>(m, "MyReader");
    }
    

    if the constructor requires more parameters, register it with the constructor signature (except the name):

    // Constructor signature:
    MyReader( std::string name, bool param1, std::vector<IElementReader> sub_readers )
    
    // Register the reader with the constructor signature:
    PYBIND11_MODULE( my_reader_cpp, m ) {
        register_reader<MyReader, bool, std::vector<IElementReader>>(m, "MyReader");
    }
    

[!IMPORTANT] Use std::shared_ptr for data members in your reader class, as uproot-custom will manage the memory of the data members. This is important to avoid memory leaks and ensure proper cleanup.

  1. Create a CMakeLists.txt file in cpp directory:

    cmake_minimum_required(VERSION 3.20)
    
    if(CMAKE_VERSION VERSION_GREATER_EQUAL 3.27)
        cmake_policy(SET CMP0148 NEW)
    endif()
    
    set(CMAKE_EXPORT_COMPILE_COMMANDS ON)
    set(CMAKE_CXX_STANDARD 20)
    
    project(${SKBUILD_PROJECT_NAME}
        VERSION ${SKBUILD_PROJECT_VERSION}
        LANGUAGES CXX
    )
        
    set(PYBIND11_NEWPYTHON ON)
    find_package(pybind11 REQUIRED)
    find_package(uproot-custom REQUIRED)
    
    pybind11_add_module(my_reader_cpp
        my_reader.cc
        # Add other source files here if needed
    )
    
    target_link_libraries(my_reader_cpp PRIVATE uproot-custom)
    
    if(DEFINED SKBUILD_PROJECT_NAME)
        install(
            TARGETS my_reader_cpp
            LIBRARY DESTINATION ${SKBUILD_PROJECT_NAME}
        )
    endif()
    

Implement the Python reader

  1. Create a my_reader directory in the root directory of your project, and create a __init__.py file in it.

  2. In __init__.py, import the C++ module and implement your Python reader class:

    from . import my_reader_cpp as _cpp
    from uproot_custom import BaseReader
    
    
    class MyReader(BaseReader):
        @classmethod
        def gen_tree_config(
            cls,
            top_type_name: str,
            cls_streamer_info: dict,
            all_streamer_info: dict,
            item_path: str = "",
        ) -> dict | None:
            """
            Identify the node in the information tree,
            return the configuration dictionary if the node is matched,
            otherwise return None.
            """
    
        @classmethod
        def get_cpp_reader(cls, tree_config) -> _cpp.MyReader | None:
            """
            Identify the tree_config,
            if it is matched, return the C++ reader instance,
            otherwise return None.
            """
    
        @classmethod
        def reconstruct_array(cls, raw_data, tree_config):
            """
            Reconstruct the raw data to an `awkward` array according to the tree_config.
            """
    

    ![NOTE] The @classmethod is not necesarry, but when a regular member method is used, you should pass the instance of the class to registered_readers.

Register the reader

Register branch path

The default interpretation uproot_custom.AsCustom needs to know which branch to read with custom readers. You can export the branch path with:

import uproot
from uproot_custom import regularize_object_path

f = uproot.open("my_file.root")
branch = f["path/to/my_branch"]

print(regularize_object_path(branch.object_path))

This will print the regularized object path like /my_tree:my_branch. Then you can add it to the AsCustom.target_branches set:

from uproot_custom import AsCustom

AsCustom.target_branches.add("your-branch-path")

Register the reader

To let uproot_custom.AsCustom know your reader, you need to register it:

from uproot_custom import registered_readers
from my_reader import MyReader

registered_readers.add(MyReader)

Then you can use uproot to read the custom class as usual.

[!TIP] It is recommended to do the registration in your project __init__.py, so that you can use your custom reader as long as you import your project.

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

uproot_custom-1.1.1.tar.gz (70.0 kB view details)

Uploaded Source

Built Distributions

If you're not sure about the file name format, learn more about wheel file names.

uproot_custom-1.1.1-cp313-cp313-win_amd64.whl (133.2 kB view details)

Uploaded CPython 3.13Windows x86-64

uproot_custom-1.1.1-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl (162.1 kB view details)

Uploaded CPython 3.13manylinux: glibc 2.27+ x86-64manylinux: glibc 2.28+ x86-64

uproot_custom-1.1.1-cp313-cp313-macosx_11_0_arm64.whl (137.5 kB view details)

Uploaded CPython 3.13macOS 11.0+ ARM64

uproot_custom-1.1.1-cp312-cp312-win_amd64.whl (133.3 kB view details)

Uploaded CPython 3.12Windows x86-64

uproot_custom-1.1.1-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl (161.9 kB view details)

Uploaded CPython 3.12manylinux: glibc 2.27+ x86-64manylinux: glibc 2.28+ x86-64

uproot_custom-1.1.1-cp312-cp312-macosx_11_0_arm64.whl (137.4 kB view details)

Uploaded CPython 3.12macOS 11.0+ ARM64

uproot_custom-1.1.1-cp311-cp311-win_amd64.whl (132.3 kB view details)

Uploaded CPython 3.11Windows x86-64

uproot_custom-1.1.1-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl (161.8 kB view details)

Uploaded CPython 3.11manylinux: glibc 2.27+ x86-64manylinux: glibc 2.28+ x86-64

uproot_custom-1.1.1-cp311-cp311-macosx_11_0_arm64.whl (136.0 kB view details)

Uploaded CPython 3.11macOS 11.0+ ARM64

uproot_custom-1.1.1-cp310-cp310-win_amd64.whl (131.8 kB view details)

Uploaded CPython 3.10Windows x86-64

uproot_custom-1.1.1-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl (160.9 kB view details)

Uploaded CPython 3.10manylinux: glibc 2.27+ x86-64manylinux: glibc 2.28+ x86-64

uproot_custom-1.1.1-cp310-cp310-macosx_11_0_arm64.whl (134.5 kB view details)

Uploaded CPython 3.10macOS 11.0+ ARM64

uproot_custom-1.1.1-cp39-cp39-win_amd64.whl (131.3 kB view details)

Uploaded CPython 3.9Windows x86-64

uproot_custom-1.1.1-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl (161.1 kB view details)

Uploaded CPython 3.9manylinux: glibc 2.27+ x86-64manylinux: glibc 2.28+ x86-64

uproot_custom-1.1.1-cp39-cp39-macosx_11_0_arm64.whl (134.6 kB view details)

Uploaded CPython 3.9macOS 11.0+ ARM64

File details

Details for the file uproot_custom-1.1.1.tar.gz.

File metadata

  • Download URL: uproot_custom-1.1.1.tar.gz
  • Upload date:
  • Size: 70.0 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.12.9

File hashes

Hashes for uproot_custom-1.1.1.tar.gz
Algorithm Hash digest
SHA256 51418bb49aa02b0673c589926409989db24247fe51ba5529bb583cfc55837025
MD5 a1fe545b9540e10522fb053fbda56e92
BLAKE2b-256 3a25daa2f4fbf777ef7c298421907837dba1da0fa7bc152bc94d8bfa4da69524

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.1.tar.gz:

Publisher: python-publish.yml on mrzimu/uproot-custom

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file uproot_custom-1.1.1-cp313-cp313-win_amd64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.1-cp313-cp313-win_amd64.whl
Algorithm Hash digest
SHA256 23fca1f6cab229950ce402f5e7055d9a0953fef312d81e712acce36ae0d132dd
MD5 51556170f5547adc947f9d79c04fd766
BLAKE2b-256 3982018ca72a48ca605ba77b5a4230865c9bc85f7db5a38c2e53eaf9f229c6fb

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.1-cp313-cp313-win_amd64.whl:

Publisher: python-publish.yml on mrzimu/uproot-custom

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file uproot_custom-1.1.1-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.1-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 a1d48dfab394884c19869e88e67dba0f5e662c8eeb73da03ca62640dd40d850d
MD5 4774418d17fe9d19d03a45860e940c0d
BLAKE2b-256 7c8fae84abf140f911bfbad42f90c7c5cd6d3edc0d0455f169a482c7c58aac5c

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.1-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl:

Publisher: python-publish.yml on mrzimu/uproot-custom

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file uproot_custom-1.1.1-cp313-cp313-macosx_11_0_arm64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.1-cp313-cp313-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 6581c765d07d794129c069c152375494d61670029a42b97d8ef4520b274f351c
MD5 0e1abb091f548be3e64847bb57e1cb45
BLAKE2b-256 f386200da27b017f3736ee7ac2bf2d86a3e65854f20ccda5d2f30115fee0601b

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.1-cp313-cp313-macosx_11_0_arm64.whl:

Publisher: python-publish.yml on mrzimu/uproot-custom

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file uproot_custom-1.1.1-cp312-cp312-win_amd64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.1-cp312-cp312-win_amd64.whl
Algorithm Hash digest
SHA256 65c75a6484187560e81c112eef95709b72ea5afd1294b95bc5e40e5084184ab5
MD5 a974b316ca299b7f3040a78de895b6d0
BLAKE2b-256 1bd3aa22d04c46e7f78c098c91533ca4f1fad8e584d62bece44d0a5728ba3c3d

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.1-cp312-cp312-win_amd64.whl:

Publisher: python-publish.yml on mrzimu/uproot-custom

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file uproot_custom-1.1.1-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.1-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 c6da9005ee017a8d55454621a31cf53899df4d4181200496273943e2f0015da1
MD5 3945b56030f1e34b3e5baafee7851bee
BLAKE2b-256 e3c23b4c38b3c4e475f656108e3dd42f919cbbd7bfa9a8a37d704d735e1eff35

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.1-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl:

Publisher: python-publish.yml on mrzimu/uproot-custom

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file uproot_custom-1.1.1-cp312-cp312-macosx_11_0_arm64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.1-cp312-cp312-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 47451b06308ab831f9c498ade0d7c634111d103e7a0baba54c342070279d0e92
MD5 d92cbc1f762518af7d6d0bec99a23483
BLAKE2b-256 55dacdf2385fece21f0ba1599baf3ac8a8e8283b9907d890b703decd4359c3e8

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.1-cp312-cp312-macosx_11_0_arm64.whl:

Publisher: python-publish.yml on mrzimu/uproot-custom

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file uproot_custom-1.1.1-cp311-cp311-win_amd64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.1-cp311-cp311-win_amd64.whl
Algorithm Hash digest
SHA256 724cee3ef142baba8638bef78efd526d11960ee0344ad3b2a2c783f5145b9bce
MD5 8a16fb7dedd2fdd3fd9bc8ae421ea3ee
BLAKE2b-256 7980bdf663152160f31b334545c40fbc3e62b96eb955edd306216d5e48e74202

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.1-cp311-cp311-win_amd64.whl:

Publisher: python-publish.yml on mrzimu/uproot-custom

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file uproot_custom-1.1.1-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.1-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 22972ccb5617e756ddfe17ace43c5a8b8adeb21d6883517eef5eeece060e3f47
MD5 05578cf619781514daa260a34d1650e2
BLAKE2b-256 d109add553e75a28fb11082b2ddc5337eec176ead4b656f142f844f79260e089

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.1-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl:

Publisher: python-publish.yml on mrzimu/uproot-custom

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file uproot_custom-1.1.1-cp311-cp311-macosx_11_0_arm64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.1-cp311-cp311-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 52baa6095dafb03eb5e2784396e2f82a307879e14a60919f4efb874e502bffc4
MD5 849d2ff2a370292f334cd7d3ee69dd7c
BLAKE2b-256 2f6aaf94d0947cf373221a5861f16b4b821c3ae08c80db65461f42c5c134de59

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.1-cp311-cp311-macosx_11_0_arm64.whl:

Publisher: python-publish.yml on mrzimu/uproot-custom

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file uproot_custom-1.1.1-cp310-cp310-win_amd64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.1-cp310-cp310-win_amd64.whl
Algorithm Hash digest
SHA256 87156a79d54ad1c09dfaacc3c4c6902d112083c62e5c16db1e009d04fc6532ba
MD5 8bb37a8d8c2e390b2247ca13c9644bb2
BLAKE2b-256 6e8e5ea291914d9dcbc4d83c943e3bad47c05a74724d62ea3665d14dac23166b

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.1-cp310-cp310-win_amd64.whl:

Publisher: python-publish.yml on mrzimu/uproot-custom

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file uproot_custom-1.1.1-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.1-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 876e15a504132dcdaae064c374d57b8a8640db3800dd63d33bf2b297a736c7c2
MD5 9aa3607d07468ef62d516b9ecd4396c3
BLAKE2b-256 2d4de3ce4258859977161b6812c564e7b68909d2d47afef8f12039b238671f8f

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.1-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl:

Publisher: python-publish.yml on mrzimu/uproot-custom

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file uproot_custom-1.1.1-cp310-cp310-macosx_11_0_arm64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.1-cp310-cp310-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 306aba517696a1dc832791c68357a537ee161385f876b5c76780ac6d26d98955
MD5 9658848f676a28c289cac4e21d709a6e
BLAKE2b-256 4de211b562bc1b93740cf5c7836d8911ffba1241f805fbd1904a05c76bae1030

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.1-cp310-cp310-macosx_11_0_arm64.whl:

Publisher: python-publish.yml on mrzimu/uproot-custom

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file uproot_custom-1.1.1-cp39-cp39-win_amd64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.1-cp39-cp39-win_amd64.whl
Algorithm Hash digest
SHA256 4671893229f0492737286aaea92ae08b02c7cfb3611ac06727e5d483e22a6f18
MD5 0662b97e8d1211af8bb0d69ff7064dbe
BLAKE2b-256 8e07576ef7ed94867169d94c71cfe4321bd3b297719f9d07772b82c0bfcf1ea2

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.1-cp39-cp39-win_amd64.whl:

Publisher: python-publish.yml on mrzimu/uproot-custom

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file uproot_custom-1.1.1-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.1-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 59357c0204330e900f227adf8ca8dca47ca0e27baeed13e77616e9344124e704
MD5 f9626e6f110d312bb36650710a3f2b2b
BLAKE2b-256 571173ec8c189c98a1eaac416cb1ec4f209aaefd750973cee431c484b7f90aef

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.1-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl:

Publisher: python-publish.yml on mrzimu/uproot-custom

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file uproot_custom-1.1.1-cp39-cp39-macosx_11_0_arm64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.1-cp39-cp39-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 f61ffe4f9587e94c5abd92421905eb1618a58ef80337212adc05ea660d3b9629
MD5 be736be25ccfb8d23238c020bc8a035e
BLAKE2b-256 94a95cbee20b71a8b1e185df7700a17bbe58caffd9ba0195736470e4594d9956

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.1-cp39-cp39-macosx_11_0_arm64.whl:

Publisher: python-publish.yml on mrzimu/uproot-custom

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page