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.2.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.2-cp313-cp313-win_amd64.whl (133.2 kB view details)

Uploaded CPython 3.13Windows x86-64

uproot_custom-1.1.2-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.2-cp313-cp313-macosx_11_0_arm64.whl (137.5 kB view details)

Uploaded CPython 3.13macOS 11.0+ ARM64

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

Uploaded CPython 3.12Windows x86-64

uproot_custom-1.1.2-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.2-cp312-cp312-macosx_11_0_arm64.whl (137.4 kB view details)

Uploaded CPython 3.12macOS 11.0+ ARM64

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

Uploaded CPython 3.11Windows x86-64

uproot_custom-1.1.2-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.2-cp311-cp311-macosx_11_0_arm64.whl (136.0 kB view details)

Uploaded CPython 3.11macOS 11.0+ ARM64

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

Uploaded CPython 3.10Windows x86-64

uproot_custom-1.1.2-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.2-cp310-cp310-macosx_11_0_arm64.whl (134.5 kB view details)

Uploaded CPython 3.10macOS 11.0+ ARM64

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

Uploaded CPython 3.9Windows x86-64

uproot_custom-1.1.2-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.2-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.2.tar.gz.

File metadata

  • Download URL: uproot_custom-1.1.2.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.2.tar.gz
Algorithm Hash digest
SHA256 35d2ab32d1752730cfa6e4f312f4c65d6541bd917f7225703ccf2745425a71e3
MD5 88b7fae7d761c8669d56f8671847726d
BLAKE2b-256 9260d21b3e715c979f3701ab75b41f2cee17e5db4ab05642656e6e2731c73864

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.2.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.2-cp313-cp313-win_amd64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.2-cp313-cp313-win_amd64.whl
Algorithm Hash digest
SHA256 18e16c650a7b7285371b2faf570cbe72f7bc3d9496b55c7a681faafe74d13b3e
MD5 31ce35e894a4b793e7cd1a2334524033
BLAKE2b-256 cd7ee92f0058f0ab1f3242e1bb0a323ea7022766bd2a14d7a48966e3036f9397

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.2-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.2-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.2-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 8a263c7c173abdd750960876a9bcb3594db59b24088798c0cd19a803a7add794
MD5 72a174a28f9cfea3c9f90db7bf084143
BLAKE2b-256 66be99a433bd8211cd5383c36713c636a88f1e22a7ba9962c1bf550c675f6005

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.2-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.2-cp313-cp313-macosx_11_0_arm64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.2-cp313-cp313-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 eb73967dbb0e1806eee1e0647ecdd073cbeb36e88880f9aa2ae765adf6542ca6
MD5 972030ffb1b5fd7da7d8acf212ba57aa
BLAKE2b-256 37cf03d919ab56c90823d50841cf9e7b8f611f6da2a1aa9a6248f35143b3753a

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.2-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.2-cp312-cp312-win_amd64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.2-cp312-cp312-win_amd64.whl
Algorithm Hash digest
SHA256 c23ebcb5c71a9fe652ba297b85f6e47ce39bafbab2db965a13d5e81d749b733b
MD5 1f04dee0fe8e20b9d920921da7783549
BLAKE2b-256 ea58613e3770e12894e6879d20a1dbb6499b97f9138b871796d61b7949b5b67b

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.2-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.2-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.2-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 0ebf6c670a838663ace2c9dd7e27f4f6a2f8f77e1bf357dd954c27fb7ede6e34
MD5 22c4e342a17162c1868e7559538802f4
BLAKE2b-256 0f5868785f6ef8b028551243e891a39c28962718dc1d73bf2b14011f3b864cee

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.2-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.2-cp312-cp312-macosx_11_0_arm64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.2-cp312-cp312-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 7d55463fbf52b31eaa6c71975e4bce4fe4ee4b3243945f2df585a81fa178c008
MD5 fb458cadd401b46de1a1bab8c1ae3c09
BLAKE2b-256 ebbad51b6ed5240f8bd0ef814d986e86d722453267f6a3f6029533352dd64100

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.2-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.2-cp311-cp311-win_amd64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.2-cp311-cp311-win_amd64.whl
Algorithm Hash digest
SHA256 479c51a0a95bbdca8d30f4b2ebb3af2e5ee4905dad2b9bf30d2c77e09c9e2d96
MD5 ae2825ab7468c89034d7352afd9c1bad
BLAKE2b-256 9a3374be05613ed45da1837a68bb2d4eb6d5a136df8646ce925f57f02983490f

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.2-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.2-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.2-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 2751481cad6a76b03bed1f50c7104df4e896084d76d6393d7b34b561b8fc7c3f
MD5 fec117268995285ba6ad54013f98b13d
BLAKE2b-256 8ee220f62bd3e6f57ccbf7c8d1c725225ffaf683e094785c994a4ea78f567745

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.2-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.2-cp311-cp311-macosx_11_0_arm64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.2-cp311-cp311-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 e29042e4ebd8389276503abde9788e72a32a245e795517155db5c4ab88c13be5
MD5 ed2a1b0223ea1c910d9e6c24b389e8a7
BLAKE2b-256 a65bafc4538664e7ed541b8702de02c2eb00bc4d53d2db617e39d7e2bd4533b1

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.2-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.2-cp310-cp310-win_amd64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.2-cp310-cp310-win_amd64.whl
Algorithm Hash digest
SHA256 ad611d6e8f547c4981efc7fae23d9004ccdda9ac838cb435fccace27a264ff5c
MD5 31c28ec8ed8614037fe63e99f9630c1a
BLAKE2b-256 af8c82f2012cdec3df416f6f06ac3eb2e6ac1af1ecf0ddb84a2477b331cb8d59

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.2-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.2-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.2-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 1e9a63bea2cbf7680d6a26199ef25d64361647488c973349fedb8466edea2f1e
MD5 e47c91a868e5628022017f860960da5c
BLAKE2b-256 6152512a3a71192f5bb74228e95b1d2268bf0a0a667795fe8b7ac3d80de70031

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.2-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.2-cp310-cp310-macosx_11_0_arm64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.2-cp310-cp310-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 3fd002b100cdc34263b4ccc247d54e91b6e7ff1eb6c3dfd683e30a58b125f533
MD5 68dd92e88751f2a9a793827dd4213b27
BLAKE2b-256 a40ad506fe5cf4db03595a9b49409c4968f5a973e21c62d731462a2f6d2c6665

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.2-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.2-cp39-cp39-win_amd64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.2-cp39-cp39-win_amd64.whl
Algorithm Hash digest
SHA256 79c97d3cbfcf5966b261e32772dba0be293fc7ac0e8429cc332d93338e2eb46b
MD5 8281dc83e724ccc4d4435ff023ee10e9
BLAKE2b-256 536d7914e06248cd19ba0c972d8561ded60b5f34824ed9f0a3d9ea57f111cac2

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.2-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.2-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.2-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 4f1c40127a1e225f6bf89264f3085a03831ed006f28fc761dd6a37f5073da4b2
MD5 e1ed607fc0820adcf4dd8f9a335119ca
BLAKE2b-256 75ab9cee31278fc852c207a44c4db8799e996d07bd10baf61546f573bf7a173b

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.2-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.2-cp39-cp39-macosx_11_0_arm64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.1.2-cp39-cp39-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 191319db57205d9b0d25502d1efe3afebf6dbd5f5efb102d42993095f0f00e1e
MD5 14dccb972fa79c7408ea0706270bd66c
BLAKE2b-256 b391be2eff1d542d0ace42e32e0c433b9a72727b147e3b6c7732bafb77a4cb3d

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.1.2-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