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.0.0.tar.gz (57.3 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.0.0-cp313-cp313-win_amd64.whl (131.0 kB view details)

Uploaded CPython 3.13Windows x86-64

uproot_custom-1.0.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl (158.8 kB view details)

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

uproot_custom-1.0.0-cp313-cp313-macosx_11_0_arm64.whl (134.7 kB view details)

Uploaded CPython 3.13macOS 11.0+ ARM64

uproot_custom-1.0.0-cp312-cp312-win_amd64.whl (131.0 kB view details)

Uploaded CPython 3.12Windows x86-64

uproot_custom-1.0.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl (158.7 kB view details)

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

uproot_custom-1.0.0-cp312-cp312-macosx_11_0_arm64.whl (134.6 kB view details)

Uploaded CPython 3.12macOS 11.0+ ARM64

uproot_custom-1.0.0-cp311-cp311-win_amd64.whl (130.1 kB view details)

Uploaded CPython 3.11Windows x86-64

uproot_custom-1.0.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl (159.9 kB view details)

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

uproot_custom-1.0.0-cp311-cp311-macosx_11_0_arm64.whl (133.0 kB view details)

Uploaded CPython 3.11macOS 11.0+ ARM64

uproot_custom-1.0.0-cp310-cp310-win_amd64.whl (129.6 kB view details)

Uploaded CPython 3.10Windows x86-64

uproot_custom-1.0.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl (158.5 kB view details)

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

uproot_custom-1.0.0-cp310-cp310-macosx_11_0_arm64.whl (131.5 kB view details)

Uploaded CPython 3.10macOS 11.0+ ARM64

uproot_custom-1.0.0-cp39-cp39-win_amd64.whl (129.1 kB view details)

Uploaded CPython 3.9Windows x86-64

uproot_custom-1.0.0-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl (159.1 kB view details)

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

uproot_custom-1.0.0-cp39-cp39-macosx_11_0_arm64.whl (131.6 kB view details)

Uploaded CPython 3.9macOS 11.0+ ARM64

File details

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

File metadata

  • Download URL: uproot_custom-1.0.0.tar.gz
  • Upload date:
  • Size: 57.3 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.0.0.tar.gz
Algorithm Hash digest
SHA256 fc58f4be4b9cdd8e295ffc03d4d0437d3135967b1eee9c80340eddb418847553
MD5 4b05d410ba0c0fb01bd65dbaf13f4ed4
BLAKE2b-256 60f1783937b71622e0f54e6f4e282e1d31ab7faf8932df8dbff5432feee573b4

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for uproot_custom-1.0.0-cp313-cp313-win_amd64.whl
Algorithm Hash digest
SHA256 eba7de533dd42b8c485dc5f041e779ec76e10a83012bb38b30ebcee6f37c2364
MD5 4353d2c36c5d28e2cc076c4d8fdb7772
BLAKE2b-256 2318858ea9b321477d38fabd3965e19374f09736859229c093c5c8decf8f39bd

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for uproot_custom-1.0.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 d47e79ea7c4ca4ef3d0a89e1b2a4f6a5765bbeb790e742e20a91a83cba9429ce
MD5 734ea61ac6e316589ce279d66d4ad55a
BLAKE2b-256 faf4ed84626ddf8e75e477071c265bf4ed6c62fcafea922a2a306cdac1d999ee

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for uproot_custom-1.0.0-cp313-cp313-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 7a34663049c1c11523609ad7c1c376c17cfea78f7457e156ca62cea0e516a53d
MD5 f877c42ce5ee5078b8e55253ca4824b6
BLAKE2b-256 133bad999dd0a1cfb33050cccf7b58aea4bba3eeea795dbf1c7133283f9609b6

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for uproot_custom-1.0.0-cp312-cp312-win_amd64.whl
Algorithm Hash digest
SHA256 4582c687c44941de5ffb7c44bf94736fcc68e83db8242e0faf0693f1d36c2c02
MD5 05e56a2ddb8e0a22c6ce600c086926b1
BLAKE2b-256 fabad84a9705a88fc27e7f5a1147a65b999e486c120989d4b8562379b4f998eb

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for uproot_custom-1.0.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 b87de55c9dc0bd9f6b14cb4746fa51ab3871acfe9d3f929bdeb5d291a65b33d4
MD5 35d5d5614f91d70a733c23cac221141a
BLAKE2b-256 25cf182d629b3accdd8e7047b70069a3a721904a891bf3e63bb46ad5ea4209da

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for uproot_custom-1.0.0-cp312-cp312-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 3248cc7d910eefc50a5c7f4043786151266f3a7139911f66dd22b95a8f6b0471
MD5 c5bedcd8c808b6eacbdda62e7b94e92e
BLAKE2b-256 b36d554c529090a74261842cea753c69ccfe9b7c7a581a8e71c898f12467f5c0

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for uproot_custom-1.0.0-cp311-cp311-win_amd64.whl
Algorithm Hash digest
SHA256 1c480341c14f05bd231ed0c1f54907938a0fa8f682797a1f0261b9e2d16496e8
MD5 a6670aba9dbe20239483c060d059cf38
BLAKE2b-256 77b7cd3cb22a50b09e18657e05dc9aa2a2d0881db4b18e5415670fb5ef2a47c1

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for uproot_custom-1.0.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 79f5de549872d1724fadb7e9cc4b2e7ddf06dbea00801df746b042c490428b63
MD5 f14149a87303fa7287e7dccca7de959b
BLAKE2b-256 ca5edd08c7404ac5d2e3ed1c3853e65180b98a4b0d75beeb2bbb89c32b5eb98b

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for uproot_custom-1.0.0-cp311-cp311-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 16e0adcbc9b0d68cc8eb1c01d69314ee915e195cdacb6be8747d0fa041dc4ebc
MD5 48d4bf78bb6479be2173063e9c5c0521
BLAKE2b-256 be7c67315fd7a3924cade4e634c4063c059921505f56a03cd2d9a25cec606486

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for uproot_custom-1.0.0-cp310-cp310-win_amd64.whl
Algorithm Hash digest
SHA256 48846e8640747cd6d3252e989f424c1138f2bceadd309c5da3f1bdf7912713c2
MD5 0581086bde6560cdde9e7fd8be9324f2
BLAKE2b-256 1deae68e981ce96e2be390da6d8e991753adbd7e27b1da6d330d5f2f619b1f8b

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for uproot_custom-1.0.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 1a9f105210a421b6e578aa67d12faa966b3bb1cab4d7042ca28fb0620b9211ac
MD5 5e678ecccc04458914e6014b4e589831
BLAKE2b-256 adf01b63d230a29df9292de94be484b00f021876645094063d71fa7ce8fdffee

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for uproot_custom-1.0.0-cp310-cp310-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 509cb804fc87bd904bea37a4eb9958ec349f7affa542a566dbfb85f7d3b9ef14
MD5 4110ebe606aa649dff44471d825dffe0
BLAKE2b-256 944b27a3cc8f87cc51ca09ba2fa7492c275c6a25d0f005a706f9d790c2ebfff0

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for uproot_custom-1.0.0-cp39-cp39-win_amd64.whl
Algorithm Hash digest
SHA256 2ed95307ef477da83315d82e749c387be09dcb51fe040bea7336228b670762cf
MD5 045c333524e349f70b0ef6ce62c0f6b7
BLAKE2b-256 9abeaa6e13a45c43cb9d66a1017ccfa2ebc8d26fd5c2a4f3d8dc4b4ff4e75b97

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for uproot_custom-1.0.0-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 291a7cb37d36328ae4161902cee40aed3589788d5478aa20453933d059a1a925
MD5 ce46ce57649cdd4f307be190e74d2d85
BLAKE2b-256 7037b05c573d12e7f54223e4387953b30a7ee68b6799568c7d3c88a035c3b85d

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for uproot_custom-1.0.0-cp39-cp39-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 a285c8f80348ddbbbfbff81c87a34e5222554fdcfa6831fe90b7d6bd58bde11c
MD5 d397b3313f63b723c7366bc34d393aaf
BLAKE2b-256 8856fd3caa07aad21118b3bb7d73e8fcb8663103063cfd52e0f23fe297308c28

See more details on using hashes here.

Provenance

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