conda-forge / uproot-feedstock

A conda-smithy repository for uproot.

About uproot-feedstock

Feedstock license: BSD-3-Clause

Home: https://github.com/scikit-hep/uproot5

Package license: BSD-3-Clause

Summary: ROOT I/O in pure Python and NumPy.

Development: https://github.com/scikit-hep/uproot5

Documentation: https://uproot.readthedocs.io/en/latest/

uproot (originally μproot, for "micro-Python ROOT") is a reader and a writer of the ROOT file format using only Python and Numpy. Unlike the standard C++ ROOT implementation, uproot is only an I/O library, primarily intended to stream data into machine learning libraries in Python. Unlike PyROOT and root_numpy, uproot does not depend on C++ ROOT. Instead, it uses Numpy calls to rapidly cast data blocks in the ROOT file as Numpy arrays.

Current build status

All platforms:

Current release info

Name	Downloads	Version	Platforms

Installing uproot

Installing uproot from the conda-forge channel can be achieved by adding conda-forge to your channels with:

conda config --add channels conda-forge
conda config --set channel_priority strict

Once the conda-forge channel has been enabled, uproot, uproot-base can be installed with conda:

conda install uproot uproot-base

or with mamba:

mamba install uproot uproot-base

It is possible to list all of the versions of uproot available on your platform with conda:

conda search uproot --channel conda-forge

or with mamba:

mamba search uproot --channel conda-forge

Alternatively, mamba repoquery may provide more information:

# Search all versions available on your platform:
mamba repoquery search uproot --channel conda-forge

# List packages depending on `uproot`:
mamba repoquery whoneeds uproot --channel conda-forge

# List dependencies of `uproot`:
mamba repoquery depends uproot --channel conda-forge

About conda-forge

conda-forge is a community-led conda channel of installable packages. In order to provide high-quality builds, the process has been automated into the conda-forge GitHub organization. The conda-forge organization contains one repository for each of the installable packages. Such a repository is known as a feedstock.

A feedstock is made up of a conda recipe (the instructions on what and how to build the package) and the necessary configurations for automatic building using freely available continuous integration services. Thanks to the awesome service provided by Azure, GitHub, CircleCI, AppVeyor, Drone, and TravisCI it is possible to build and upload installable packages to the conda-forge anaconda.org channel for Linux, Windows and OSX respectively.

To manage the continuous integration and simplify feedstock maintenance conda-smithy has been developed. Using the conda-forge.yml within this repository, it is possible to re-render all of this feedstock's supporting files (e.g. the CI configuration files) with conda smithy rerender.

For more information please check the conda-forge documentation.

Terminology

feedstock - the conda recipe (raw material), supporting scripts and CI configuration.

conda-smithy - the tool which helps orchestrate the feedstock. Its primary use is in the construction of the CI .yml files and simplify the management of many feedstocks.

conda-forge - the place where the feedstock and smithy live and work to produce the finished article (built conda distributions)

Updating uproot-feedstock

If you would like to improve the uproot recipe or build a new package version, please fork this repository and submit a PR. Upon submission, your changes will be run on the appropriate platforms to give the reviewer an opportunity to confirm that the changes result in a successful build. Once merged, the recipe will be re-built and uploaded automatically to the conda-forge channel, whereupon the built conda packages will be available for everybody to install and use from the conda-forge channel. Note that all branches in the conda-forge/uproot-feedstock are immediately built and any created packages are uploaded, so PRs should be based on branches in forks and branches in the main repository should only be used to build distinct package versions.

In order to produce a uniquely identifiable distribution:

• If the version of a package is not being increased, please add or increase the build/number.
• If the version of a package is being increased, please remember to return the build/number back to 0.

Feedstock Maintainers

• @agoose77
• @chrisburr
• @conda-forge/scikit-hep
• @henryiii
• @ioanaif
• @jpivarski
• @lgray

uproot-feedstock's Issues

e30b558ea045eaea49a61a96d23ccd22a09c3fb1 should have been a pull request

@chrisburr

Yikes! That should have been a pull request. It's referencing this: scikit-hep/uproot3#307. We're not depending on xxhash just yet, as the uproot PR has not been merged yet and we're still working on one issue. We really just need the xxhash dependency before that, but due to my mistake using GitHub's web interface, it looks like it's already applied.

Can't install Uproot 4

Has Uproot 4.0.0 been uploaded to Anaconda yet?
It's listet on the Anaconda website (https://anaconda.org/conda-forge/uproot/files) but the file is only 6.6 kB large and conda fails to install it for me under Windows 10.

Please add @agoose77 as a maintainer

To resolve some version incompatibilities between uproot-feedstock and awkward-feedstock that are being discussed on https://gitter.im/Scikit-HEP/uproot.

I would do it, but I don't have the level of access needed to add maintainers. @agoose77 is already a maintainer on awkward-feedstock.

Thanks!

@conda-forge-admin add bot automerge

The version for mac m1 devices is too low

• [✓] I read the conda-forge documentation and could not find the solution for my problem there.

Issue:

Hi, I use a MacBook Pro 13.3 M1 version now. I tried to install the uproot by conda. But only uproot 4.0.0 can be installed. Then, I tried to run my script, the output is quite strange and different from the output from another notebook. The uproot version is higher in that notebook. It seems like a bug in uproot 4.0.0. So the uproot 4.0.0 in my MacBook was removed, and uproot 4.1.7 was installed by pip in a virtual conda environment. This time the output is the same as in another device.

The uproot 4.1.7 installed by pip seems like works well. But I hope I can install the newer uproot by conda. Could the uproot for OSX-arm64 be updated?

Environment (conda list):

$ conda list

Details about conda and system ( conda info ):

conda 4.10.3 installed by Miniforge3-MacOSX-arm64