Skip to main content

aurivis-simd

CPU feature detection, runtime dispatch and aligned memory for SIMD code.
Header-only C++20 with a small, fully typed Python API.


Python C++ Platforms License


Why this exists

Modern CPUs can process many values with a single instruction. These are the SIMD instruction sets: SSE, AVX2, AVX-512 on Intel and AMD, NEON on ARM. Used well, they make code like video decoding, audio processing or parsing several times faster.

The catch is that not every CPU has the same instructions. If your program uses AVX-512 on a machine that doesn't support it, it crashes. So most projects either build for the oldest CPU and leave a lot of speed on the table, or ship separate builds for every machine.

aurivis-simd solves this at runtime. You write the important parts of your code in a few versions, for example a plain one, one for AVX2 and one for AVX-512. aurivis-simd checks what the CPU and the operating system support and picks the fastest version that will actually run. One build works everywhere: an old laptop gets the plain version, a new workstation gets AVX-512.

It also comes with the memory tools that SIMD code needs: buffers aligned to 64 bytes and a buffer pool that reuses memory instead of asking the operating system again for every video frame.

Status

Feature Status
x86 detection (SSE2 to AVX-512) ✅
Dispatch tables ✅
AlignedBuffer, Pool ✅
Python API ✅
ARM detection (NEON, dotprod, SVE, SVE2) ❌
Portable vector types (Vec128, Vec256, Vec512) ❌

Installation

pip install aurivis-simd

The package contains both the Python module and the C++ headers.

Example: what can this CPU do? (Python)

Save this as cpu_info.py:

from aurivis_simd import Cpu, Level

class CpuReport:
    """Prints what the current machine supports."""

    @staticmethod
    def show() -> None:
        print(f'Best level:   {Cpu.best_level().name}')
        print(f'Active level: {Cpu.active_level().name}')
        print()
        for level in Level:
            print(f'  {level.name:<8} {"yes" if Cpu.supports(level) else "no"}')
        print()
        features = Cpu.features()
        print(f'AVX2 + FMA:       {features.avx2 and features.fma}')
        print(f'AVX-512 VNNI:     {features.avx512vnni}')

if __name__ == '__main__':
    CpuReport.show()

Run it with python cpu_info.py. On an Intel Core i7-11700F it prints:

Best level:   AVX512
Active level: AVX512

  GENERIC  yes
  SSE41    yes
  AVX2     yes
  AVX512   yes
  NEON     no

AVX2 + FMA:       True
AVX-512 VNNI:     True

The detection runs once, when you import the package. After that, every call just returns the stored result, so you can call Cpu.features() as often as you like. In a hot loop it's still a little faster to keep the features object around.

best_level() is the highest level the machine supports. active_level() is the one your code should use. They're the same unless you lower it with the AURIVIS_SIMD environment variable (see Testing the fallbacks).

Everything is typed and ships with py.typed, so your editor knows every attribute and return type, and the package passes mypy --strict.

Example: choosing the fastest implementation (C++)

This is what the library is really for. The program below sums a million floats. It contains a plain version, an AVX2 version and an AVX-512 version of the same function, and lets aurivis-simd pick the fastest one the machine can run. Save it as sum.cpp:

#include "Aurivis/Simd/Simd.hpp"

#include <cstddef>
#include <cstdio>

#if AURIVIS_ARCH_X86_64
#include <immintrin.h>
#endif

using SumFn = float (*)(const float* values, size_t count);

float SumGeneric(const float* values, size_t count) {
  float total = 0.0f;
  for (size_t i = 0; i < count; ++i) {
    total += values[i];
  }
  return total;
}

#if AURIVIS_ARCH_X86_64

AURIVIS_TARGET_AVX2 float SumAvx2(const float* values, size_t count) {
  __m256 total = _mm256_setzero_ps();
  size_t i = 0;
  for (; i + 8 <= count; i += 8) {
    total = _mm256_add_ps(total, _mm256_load_ps(values + i));
  }
  alignas(32) float lanes[8];
  _mm256_store_ps(lanes, total);
  float sum = 0.0f;
  for (const float lane : lanes) {
    sum += lane;
  }
  for (; i < count; ++i) {
    sum += values[i];
  }
  return sum;
}

AURIVIS_TARGET_AVX512 float SumAvx512(const float* values, size_t count) {
  __m512 total = _mm512_setzero_ps();
  size_t i = 0;
  for (; i + 16 <= count; i += 16) {
    total = _mm512_add_ps(total, _mm512_load_ps(values + i));
  }
  float sum = _mm512_reduce_add_ps(total);
  for (; i < count; ++i) {
    sum += values[i];
  }
  return sum;
}

static const Aurivis::Simd::DispatchTable<SumFn> SUM{.generic = &SumGeneric, .avx2 = &SumAvx2, .avx512 = &SumAvx512};

#else

static const Aurivis::Simd::DispatchTable<SumFn> SUM{.generic = &SumGeneric};

#endif

int main() {
  // 64-byte aligned, so the AVX2 and AVX-512 versions can use aligned loads.
  Aurivis::Simd::AlignedBuffer<float> values(1'000'000);
  for (size_t i = 0; i < values.GetCount(); ++i) {
    values[i] = static_cast<float>(i % 10);
  }

  const SumFn fastest = SUM.Select();
  const SumFn plain = SUM.SelectFor(Aurivis::Simd::Level::Generic);

  std::printf("Active level: %s\n", Aurivis::Simd::LevelToString(Aurivis::Simd::GetActiveLevel()));
  std::printf("Fastest sum:  %.0f\n", fastest(values.GetData(), values.GetCount()));
  std::printf("Generic sum:  %.0f\n", plain(values.GetData(), values.GetCount()));
  return 0;
}

The headers come with the Python package, so Headers.get_include() tells the compiler where to find them.

On Windows, in a Developer PowerShell for VS 2022:

$include = python -c "import aurivis_simd; print(aurivis_simd.Headers.get_include())"
cl /std:c++20 /O2 /EHsc /I $include sum.cpp
.\sum.exe

On Linux and macOS:

g++ -std=c++20 -O2 -I"$(python -c 'import aurivis_simd; print(aurivis_simd.Headers.get_include())')" sum.cpp -o sum
./sum

Output:

Active level: avx512
Fastest sum:  4500000
Generic sum:  4500000

A few things worth knowing:

  • Each SIMD version is marked with its AURIVIS_TARGET_* macro. GCC and Clang only allow AVX2 intrinsics in functions marked for AVX2, and this is how one file can contain all versions side by side. MSVC doesn't need the macros, they're simply empty there.
  • You don't have to fill in every level. This table has no SSE4.1 entry, so an SSE4.1 machine falls back to generic, which is the only entry you must provide.
  • Select() makes the choice once and caches it in the table. Calling it every time costs about as much as a normal function call.
  • SelectFor(Level::Generic) returns a specific version. Here it checks that the fast version gives the same result as the plain one.
  • On ARM the SIMD versions aren't compiled at all, and the program just uses SumGeneric.

Example: reusing frame buffers across threads (C++)

Video players need a fresh buffer for every frame, often 60 times a second, and usually on more than one thread. A Pool hands out buffers and takes them back, so memory is only allocated a few times. In this program a decoder thread fills frames and a renderer thread shows them. Save it as frames.cpp:

#include "Aurivis/Simd/Simd.hpp"

#include <condition_variable>
#include <cstdint>
#include <cstdio>
#include <deque>
#include <mutex>
#include <thread>
#include <utility>

using Frame = Aurivis::Simd::Pool<uint8_t>::Buffer;

int main() {
  constexpr int FRAME_COUNT = 1000;
  constexpr size_t QUEUE_LIMIT = 4;

  // One 1080p YUV 4:2:0 frame per buffer. Four are allocated up front.
  Aurivis::Simd::Pool<uint8_t> pool(1920 * 1080 * 3 / 2);
  pool.Reserve(QUEUE_LIMIT);

  std::mutex mutex;
  std::condition_variable changed;
  std::deque<Frame> queue;

  // The decoder takes a buffer from the pool, fills it and hands it over.
  std::thread decoder([&] {
    for (int i = 0; i < FRAME_COUNT; ++i) {
      Frame frame = pool.Acquire();
      frame[0] = static_cast<uint8_t>(i);
      std::unique_lock<std::mutex> lock(mutex);
      changed.wait(lock, [&] { return queue.size() < QUEUE_LIMIT; });
      queue.push_back(std::move(frame));
      changed.notify_all();
    }
  });

  // The renderer shows the frame. When `frame` goes out of scope, the buffer returns to the pool.
  std::thread renderer([&] {
    for (int i = 0; i < FRAME_COUNT; ++i) {
      std::unique_lock<std::mutex> lock(mutex);
      changed.wait(lock, [&] { return !queue.empty(); });
      Frame frame = std::move(queue.front());
      queue.pop_front();
      changed.notify_all();
    }
  });

  decoder.join();
  renderer.join();

  std::printf("Frames decoded:    %d\n", FRAME_COUNT);
  std::printf("Buffers allocated: %zu\n", pool.GetIdleCount());
  return 0;
}

Build it the same way as sum.cpp. On Linux, add -pthread. Output:

Frames decoded:    1000
Buffers allocated: 5

A thousand frames of 3 MB each, and only five buffers were ever allocated. Every other frame reused one of them, which takes about 14 ns instead of the roughly 7 µs a new 3 MB allocation costs.

  • A buffer can be returned from a different thread than the one that took it, as the renderer does here.
  • Each thread works in its own part of the pool, so threads rarely wait for each other.
  • Reserve() allocates buffers in advance, so playback never has to wait for the operating system.
  • A buffer may even outlive its pool. It's then freed when it's destroyed.
  • Buffers can be moved but not copied, so it's always clear which thread owns a frame. The memory isn't zeroed, because a decoder overwrites it anyway.

If you just need one aligned buffer, use AlignedBuffer<T> like in sum.cpp. It's aligned to 64 bytes and frees itself when it goes out of scope.

Example: your own Python extension (Cython)

The headers ship inside the wheel, so your own C++ extension can use them. Here is a complete project that sums float arrays with the fastest available version:

myproject/
├── pyproject.toml
├── setup.py
└── myproject/
    ├── __init__.py
    ├── _native.pyx
    └── kernels.hpp

pyproject.toml lists aurivis-simd as a build requirement, next to setuptools and Cython:

[build-system]
requires = ["setuptools>=77", "Cython>=3.1", "aurivis-simd"]
build-backend = "setuptools.build_meta"

[project]
name = "myproject"
version = "0.1.0"
requires-python = ">=3.11"

[tool.setuptools]
packages = ["myproject"]

setup.py passes the include directory to the compiler. setuptools compiles the .pyx file with Cython on its own:

import sys

import aurivis_simd
from setuptools import Extension, setup

class Build:
    """Builds the native extension against the aurivis-simd headers."""

    @staticmethod
    def extensions() -> list[Extension]:
        arguments = ['/std:c++20'] if sys.platform == 'win32' else ['-std=c++20']
        native = Extension(
            'myproject._native',
            ['myproject/_native.pyx'],
            include_dirs=[str(aurivis_simd.Headers.get_include()), 'myproject'],
            language='c++',
            extra_compile_args=arguments
        )
        return [native]

setup(ext_modules=Build.extensions())

myproject/kernels.hpp contains the C++ code with a plain and an AVX2 version:

#pragma once

#include "Aurivis/Simd/Simd.hpp"

#include <cstddef>

#if AURIVIS_ARCH_X86_64
#include <immintrin.h>
#endif

namespace MyProject {

using SumFn = float (*)(const float* values, size_t count);

inline float SumGeneric(const float* values, size_t count) {
  float total = 0.0f;
  for (size_t i = 0; i < count; ++i) {
    total += values[i];
  }
  return total;
}

#if AURIVIS_ARCH_X86_64

AURIVIS_TARGET_AVX2 inline float SumAvx2(const float* values, size_t count) {
  __m256 total = _mm256_setzero_ps();
  size_t i = 0;
  for (; i + 8 <= count; i += 8) {
    total = _mm256_add_ps(total, _mm256_load_ps(values + i));
  }
  alignas(32) float lanes[8];
  _mm256_store_ps(lanes, total);
  float sum = 0.0f;
  for (const float lane : lanes) {
    sum += lane;
  }
  for (; i < count; ++i) {
    sum += values[i];
  }
  return sum;
}

inline const Aurivis::Simd::DispatchTable<SumFn> SUM{.generic = &SumGeneric, .avx2 = &SumAvx2};

#else

inline const Aurivis::Simd::DispatchTable<SumFn> SUM{.generic = &SumGeneric};

#endif

/** @brief Sums the values with the fastest implementation this machine supports. */
inline float Sum(const float* values, size_t count) { return SUM.Select()(values, count); }

}  // namespace MyProject

myproject/_native.pyx connects it to Python. It uses cimport to work with the C++ API directly:

from libcpp.utility cimport move

from aurivis_simd.simd cimport AlignedBuffer, GetActiveLevel, LevelToString

cdef extern from 'kernels.hpp' namespace 'MyProject' nogil:
    float Sum(const float* values, size_t count)

class Native:
    """Fast helpers written in C++."""

    @staticmethod
    def level() -> str:
        """Returns the SIMD level the C++ code uses on this machine."""
        return LevelToString(GetActiveLevel()).decode()

    @staticmethod
    def total(values) -> float:
        """Sums a buffer of float32 values, e.g. an ``array('f')``."""
        cdef const float[::1] view = values
        cdef AlignedBuffer[float] buffer
        cdef size_t i
        cdef float result
        buffer = move(AlignedBuffer[float](view.shape[0]))
        for i in range(view.shape[0]):
            buffer[i] = view[i]
        with nogil:
            result = Sum(buffer.GetData(), buffer.GetCount())
        return result

myproject/__init__.py exports it:

from ._native import Native

__all__ = ['Native']

Install the project and try it:

pip install .
python -c "from array import array; from myproject import Native; print(Native.level(), Native.total(array('f', [i % 10 for i in range(1_000_000)])))"
avx512 4500000.0

Two things to note about the Cython side:

  • AlignedBuffer and Pool.Buffer can only be moved, not copied, so assign them with move(...).
  • Errors from C++ arrive as normal Python exceptions: an invalid alignment raises ValueError, running out of memory raises MemoryError.

Since the headers are compiled into your extension, your users don't need aurivis-simd installed at runtime.

Testing the fallbacks

On a fast machine you'd normally only ever run the fastest version of your code. The AURIVIS_SIMD environment variable lets you pretend the CPU is older, so you can test the other versions too.

PowerShell:

$env:AURIVIS_SIMD = 'sse41'
python cpu_info.py

Bash:

AURIVIS_SIMD=sse41 python cpu_info.py
Best level:   AVX512
Active level: SSE41
...

Accepted values are generic, sse41, avx2, avx512 and neon. The variable can only lower the level, never raise it beyond what the CPU supports, and invalid values are simply ignored. It's also useful in bug reports: if a problem goes away with AURIVIS_SIMD=generic, it's in one of the SIMD versions.

Levels

Each level stands for a set of instructions that all have to be present. The x86 levels match the standard x86-64 microarchitecture levels.

Level Required features
Generic none, runs everywhere
Sse41 x86-64-v2: SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT
Avx2 x86-64-v3: AVX, AVX2, FMA, BMI1, BMI2, F16C, LZCNT, MOVBE
Avx512 x86-64-v4: AVX-512 F, BW, CD, DQ, VL
Neon ARMv8 Advanced SIMD

A feature only counts as available when the operating system supports it too. Some systems can disable AVX even though the CPU has it, and that case is handled for you.

Benchmarks

We compared aurivis-simd with Google Highway 1.4.0 for C++, and with NumPy 2.5 and py-cpuinfo 9.0 for Python. Everything was measured on an Intel Core i7-11700F with Windows 11, MSVC 2022 and Python 3.14, using Release builds and the median of several runs. Expect your numbers to differ a little; the code is in benchmarks/ if you want to run it yourself.

Detection

aurivis-simd Highway
Asking again after the first detection ≈ 0 ns ¹ 341 ns ²
Running the detection itself 331 ns 341 ns
Very first call in a new process 2.1 µs 0.6 µs ³

Dispatch

aurivis-simd Highway
Choosing the implementation on every call 1.17 ns 1.41 ns
Calling a stored function pointer 0.93 ns 0.94 ns
Plain function call, for comparison 0.70 ns 0.70 ns

Memory

AlignedBuffer Pool::Acquire() hwy::AllocateAligned
2 KB 35 ns 13.8 ns 48 ns
64 KB 93 ns 13.8 ns 125 ns
1080p frame (3 MB) 7.0 µs 13.8 ns 7.2 µs
2 KB, 8 threads at once ⁴ 41 ns 2.2 ns –

Python

aurivis-simd NumPy py-cpuinfo
Import and first answer, new process 10.4 ms 102 ms 1,696 ms
Asking again, result kept 9.8 ns 20.4 ns 1,590 ms

¹ Too fast to measure: it takes as long as an empty loop iteration (1.6 ns).
² hwy::SupportedTargets() runs the full detection on every call. Highway remembers its dispatch choice elsewhere.
³ Highway is faster on the very first call. The difference is one-time setup in a new process: the operating system loads our code into memory, and C++ prepares the thread-safe cache on first use. The detection itself is just as fast, as the row above shows.
⁴ Throughput of all threads together. Each thread takes a buffer, writes to it and gives it back, in a loop.

Development

Build the extension in place once, then run the tests:

python setup.py build_ext --inplace
python -m unittest discover -s tests -v

The tests cover the Python API, the AURIVIS_SIMD variable and the C++ headers. The C++ part is compiled on the fly, so you need Cython, setuptools and a C++20 compiler.

The C++ benchmarks need CMake and download Highway automatically. The Python benchmark compares against NumPy and py-cpuinfo if they're installed:

pip install cmake numpy py-cpuinfo
cmake -S benchmarks/cpp -B benchmarks/cpp/build
cmake --build benchmarks/cpp/build --config Release
python benchmarks/cpp/run_cold_start.py
python benchmarks/python/bench_detection.py

Requirements

  • Python 3.11 or newer
  • Windows, macOS or Linux on x86_64 or arm64
  • For building against the headers: a C++20 compiler (MSVC 2022, GCC 10, Clang 12 or newer)

Part of Aurivis

aurivis-simd is one of the native libraries behind Aurivis, an API library for Python with its own music and media player, built from scratch. Aurivis connects to services like YouTube, plays music and video in apps and websites, and brings sound to Discord bots through integrations for discord.py and Pycord.

aurivis-simd works on its own and doesn't depend on Aurivis.

License

Apache-2.0, see LICENSE.

Metadata

Release files for aurivis-simd 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for aurivis-simd 0.1.0
File Size Uploaded
aurivis_simd-0.1.0.tar.gz 41.1 kB Details

Built distributions (wheels)

Table of built distributions (wheels) for aurivis-simd 0.1.0
File
aurivis_simd-0.1.0-cp314-cp314-win_arm64.whl CPython 3.14 CPython 3.14 Windows ARM64 Details
aurivis_simd-0.1.0-cp314-cp314-win_amd64.whl CPython 3.14 CPython 3.14 Windows x86-64 Details
aurivis_simd-0.1.0-cp314-cp314-musllinux_1_2_x86_64.whl CPython 3.14 CPython 3.14 Linux musl 1.2+ x86-64 Details
aurivis_simd-0.1.0-cp314-cp314-musllinux_1_2_aarch64.whl CPython 3.14 CPython 3.14 Linux musl 1.2+ ARM64 Details
aurivis_simd-0.1.0-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.14 CPython 3.14 Linux glibc 2.17+ ARM64, Linux glibc 2.28+ ARM64 Details
aurivis_simd-0.1.0-cp314-cp314-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.5+ x86-64, Linux glibc 2.28+ x86-64 Details
aurivis_simd-0.1.0-cp314-cp314-macosx_11_0_arm64.whl CPython 3.14 CPython 3.14 macOS 11.0+ ARM64 Details
aurivis_simd-0.1.0-cp314-cp314-macosx_10_15_x86_64.whl CPython 3.14 CPython 3.14 macOS 10.15+ x86-64 Details
aurivis_simd-0.1.0-cp313-cp313-win_arm64.whl CPython 3.13 CPython 3.13 Windows ARM64 Details
aurivis_simd-0.1.0-cp313-cp313-win_amd64.whl CPython 3.13 CPython 3.13 Windows x86-64 Details
aurivis_simd-0.1.0-cp313-cp313-musllinux_1_2_x86_64.whl CPython 3.13 CPython 3.13 Linux musl 1.2+ x86-64 Details
aurivis_simd-0.1.0-cp313-cp313-musllinux_1_2_aarch64.whl CPython 3.13 CPython 3.13 Linux musl 1.2+ ARM64 Details
aurivis_simd-0.1.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.13 CPython 3.13 Linux glibc 2.28+ ARM64, Linux glibc 2.17+ ARM64 Details
aurivis_simd-0.1.0-cp313-cp313-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.5+ x86-64, Linux glibc 2.28+ x86-64 Details
aurivis_simd-0.1.0-cp313-cp313-macosx_11_0_arm64.whl CPython 3.13 CPython 3.13 macOS 11.0+ ARM64 Details
aurivis_simd-0.1.0-cp313-cp313-macosx_10_13_x86_64.whl CPython 3.13 CPython 3.13 macOS 10.13+ x86-64 Details
aurivis_simd-0.1.0-cp312-cp312-win_arm64.whl CPython 3.12 CPython 3.12 Windows ARM64 Details
aurivis_simd-0.1.0-cp312-cp312-win_amd64.whl CPython 3.12 CPython 3.12 Windows x86-64 Details
aurivis_simd-0.1.0-cp312-cp312-musllinux_1_2_x86_64.whl CPython 3.12 CPython 3.12 Linux musl 1.2+ x86-64 Details
aurivis_simd-0.1.0-cp312-cp312-musllinux_1_2_aarch64.whl CPython 3.12 CPython 3.12 Linux musl 1.2+ ARM64 Details
aurivis_simd-0.1.0-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.12 CPython 3.12 Linux glibc 2.17+ ARM64, Linux glibc 2.28+ ARM64 Details
aurivis_simd-0.1.0-cp312-cp312-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.28+ x86-64, Linux glibc 2.5+ x86-64 Details
aurivis_simd-0.1.0-cp312-cp312-macosx_11_0_arm64.whl CPython 3.12 CPython 3.12 macOS 11.0+ ARM64 Details
aurivis_simd-0.1.0-cp312-cp312-macosx_10_13_x86_64.whl CPython 3.12 CPython 3.12 macOS 10.13+ x86-64 Details
aurivis_simd-0.1.0-cp311-cp311-win_arm64.whl CPython 3.11 CPython 3.11 Windows ARM64 Details
aurivis_simd-0.1.0-cp311-cp311-win_amd64.whl CPython 3.11 CPython 3.11 Windows x86-64 Details
aurivis_simd-0.1.0-cp311-cp311-musllinux_1_2_x86_64.whl CPython 3.11 CPython 3.11 Linux musl 1.2+ x86-64 Details
aurivis_simd-0.1.0-cp311-cp311-musllinux_1_2_aarch64.whl CPython 3.11 CPython 3.11 Linux musl 1.2+ ARM64 Details
aurivis_simd-0.1.0-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.11 CPython 3.11 Linux glibc 2.17+ ARM64, Linux glibc 2.28+ ARM64 Details
aurivis_simd-0.1.0-cp311-cp311-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.5+ x86-64, Linux glibc 2.28+ x86-64 Details
aurivis_simd-0.1.0-cp311-cp311-macosx_11_0_arm64.whl CPython 3.11 CPython 3.11 macOS 11.0+ ARM64 Details
aurivis_simd-0.1.0-cp311-cp311-macosx_10_9_x86_64.whl CPython 3.11 CPython 3.11 macOS 10.9+ x86-64 Details

Total release size: 12.9 MB

Release files / aurivis_simd-0.1.0.tar.gz

Download URL aurivis_simd-0.1.0.tar.gz
Size 41.1 kB
Tags Source
SHA-256 checksum
How to use checksums
8d499606494c8091e816282ad037db1e775f90f451f6700fa43da309672ecbb9
BLAKE2b-256 checksum
How to use checksums
ef4bb322f4751ed9e0be1df8c705b26133e92a4874b370e63cc2996557b79c0a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp314-cp314-win_arm64.whl

Download URL aurivis_simd-0.1.0-cp314-cp314-win_arm64.whl
Size 64.6 kB
Tags CPython 3.14 Windows ARM64
SHA-256 checksum
How to use checksums
2d350d88613bc096b059cd490b04096dc2057c64852ddee5761b74470e2e99d2
BLAKE2b-256 checksum
How to use checksums
19befa502864abe13ae21b7ce416b5d72fc8ca4c05821312607272264b415b8a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp314-cp314-win_amd64.whl

Download URL aurivis_simd-0.1.0-cp314-cp314-win_amd64.whl
Size 67.4 kB
Tags CPython 3.14 Windows x86-64
SHA-256 checksum
How to use checksums
818fda6728a6949b1f4c0eade8a33a6bf2a93412d5cb1d22adff4e69a2a62c45
BLAKE2b-256 checksum
How to use checksums
41f47e27ac66472f1c3a57408733fbb37980c5d2684b2a554b531c8c36411557
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp314-cp314-musllinux_1_2_x86_64.whl

Download URL aurivis_simd-0.1.0-cp314-cp314-musllinux_1_2_x86_64.whl
Size 1.3 MB
Tags CPython 3.14 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
b8b13f3cf8e44cbe276b6c1f8f1ed41abb655b538287aa4db9dc82cc6a1a0616
BLAKE2b-256 checksum
How to use checksums
8ff9d4a2fbee90872485e3c82e3a48c51ae17fb7cc088c48e04ea960f9f45f46
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp314-cp314-musllinux_1_2_aarch64.whl

Download URL aurivis_simd-0.1.0-cp314-cp314-musllinux_1_2_aarch64.whl
Size 1.2 MB
Tags CPython 3.14 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
044d70c5ccb68b198408e289979d20afd42f335c9690be123729fcfb51c420a3
BLAKE2b-256 checksum
How to use checksums
0b5da7037c6c93cc07486a138bf3603345cdf3280db9c0e1dc15e4fa48c5ea23
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL aurivis_simd-0.1.0-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 227.9 kB
Tags CPython 3.14 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
e4ebd61cf22e0e83da602ab5017f4aa9511660ddd79a8117bed12596f3ab8f57
BLAKE2b-256 checksum
How to use checksums
bf637b5264d68b1d8af54b5b942c0830f810322efd0806399e2f78412990d24d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp314-cp314-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl

Download URL aurivis_simd-0.1.0-cp314-cp314-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
Size 233.7 kB
Tags CPython 3.14 Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64
SHA-256 checksum
How to use checksums
cf2d2dd65c57e336ac0c7006f2cf43844736f16f44450027857bcc6f02b17b98
BLAKE2b-256 checksum
How to use checksums
3f226ab592a83b2f1544ce8ecb2bc335942bb1b7d009102bc4eadc08113223fb
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp314-cp314-macosx_11_0_arm64.whl

Download URL aurivis_simd-0.1.0-cp314-cp314-macosx_11_0_arm64.whl
Size 70.0 kB
Tags CPython 3.14 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
10c45a41a2f64a1f2e3ea06fe760f429f4bbb7e80631869042a8547c960cb2c4
BLAKE2b-256 checksum
How to use checksums
8baec4923ad671970ac1ac56a5f9757b8f6c8335c98355aedc0d4a7b9be23440
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp314-cp314-macosx_10_15_x86_64.whl

Download URL aurivis_simd-0.1.0-cp314-cp314-macosx_10_15_x86_64.whl
Size 69.5 kB
Tags CPython 3.14 macOS 10.15+ x86-64
SHA-256 checksum
How to use checksums
bb0d2ebd0ce4551bf4548d07ca954aa7d4fa997b7bb80e093ae4582ae3716eff
BLAKE2b-256 checksum
How to use checksums
6999745e5f4025b6b89cef6a38eba24f42d378092e2e764fbf9785a3838e1daa
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp313-cp313-win_arm64.whl

Download URL aurivis_simd-0.1.0-cp313-cp313-win_arm64.whl
Size 63.4 kB
Tags CPython 3.13 Windows ARM64
SHA-256 checksum
How to use checksums
d212618945dbf2e0c0f8c25aa1d75b6830530af691320eb735804cff3cce221e
BLAKE2b-256 checksum
How to use checksums
35b790494847fa1e5a566112eda309df30d1f7c0a46023e3b4fac68ccaa80b82
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp313-cp313-win_amd64.whl

Download URL aurivis_simd-0.1.0-cp313-cp313-win_amd64.whl
Size 66.5 kB
Tags CPython 3.13 Windows x86-64
SHA-256 checksum
How to use checksums
f0f19151d61e38b6007f53c5c2e493a0dc361d8df4b31d8cbf33b5e8b5b5b1a0
BLAKE2b-256 checksum
How to use checksums
1c484d3b5e6698638912bfdc3ac5959b31057aff1a547de720967b2632ffeb07
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp313-cp313-musllinux_1_2_x86_64.whl

Download URL aurivis_simd-0.1.0-cp313-cp313-musllinux_1_2_x86_64.whl
Size 1.3 MB
Tags CPython 3.13 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
86f42ecd8ed258ce3ea83ad83643ebb1bd77985fe2c0bf9bad2b92879312a24f
BLAKE2b-256 checksum
How to use checksums
78f7150c4463746b1d65dbbc1c7bf3bcfaf570aa1d4a17692431f5d326eaf6c8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp313-cp313-musllinux_1_2_aarch64.whl

Download URL aurivis_simd-0.1.0-cp313-cp313-musllinux_1_2_aarch64.whl
Size 1.2 MB
Tags CPython 3.13 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
2fa8b792ab67a3fce28279db3d5ab022639e30dfab47959d5ea3a18efc616ad2
BLAKE2b-256 checksum
How to use checksums
fe2cffd1a20515a06deda23c92906501e8ce1f988a3bc6cf38116be4cb1631c2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL aurivis_simd-0.1.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 229.4 kB
Tags CPython 3.13 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
1fed6314a5ed56f3f2f0c0deaef61f680255f9d2ca3b385dad45c074052bde57
BLAKE2b-256 checksum
How to use checksums
0e5f536d8137d09e35435760bab69de79a85e866e9b1659eb38b7990c784b22c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp313-cp313-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl

Download URL aurivis_simd-0.1.0-cp313-cp313-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
Size 235.8 kB
Tags CPython 3.13 Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64
SHA-256 checksum
How to use checksums
1610148950d532e51c463d2aca9fa432a4f4e66567c9a79ec6cde90104bf254e
BLAKE2b-256 checksum
How to use checksums
a20e1862f5c74ad86857cecf6865feade372b0414065e4715c13a6dbb0dc4c6e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp313-cp313-macosx_11_0_arm64.whl

Download URL aurivis_simd-0.1.0-cp313-cp313-macosx_11_0_arm64.whl
Size 70.0 kB
Tags CPython 3.13 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
fd85b2e714d18799a87cd174e6458ed908f710d64bc96f5f862a8af88c3b889a
BLAKE2b-256 checksum
How to use checksums
e357eaaf7782b8d8d425b5814d7d0fd7ecd5373a40c24ec67a0ae77206ecb15e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp313-cp313-macosx_10_13_x86_64.whl

Download URL aurivis_simd-0.1.0-cp313-cp313-macosx_10_13_x86_64.whl
Size 69.4 kB
Tags CPython 3.13 macOS 10.13+ x86-64
SHA-256 checksum
How to use checksums
d8f4232fe89f1be8686ba1fd49718e5674781de3ef8fec9a1e17b3577322cf52
BLAKE2b-256 checksum
How to use checksums
801cff802326079e666ef3d0f676115ad67a7e1365328799ce8b3fa7106b66eb
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp312-cp312-win_arm64.whl

Download URL aurivis_simd-0.1.0-cp312-cp312-win_arm64.whl
Size 64.0 kB
Tags CPython 3.12 Windows ARM64
SHA-256 checksum
How to use checksums
d94a3abd1bd4da69bf433ccd2c83e9b3d2765c8477618319f7e7d7fe519b09a7
BLAKE2b-256 checksum
How to use checksums
b2cb48660b5b3a740c8871cb5be4ee96492ec77c879c2d60c7aa0cf2d0aba32c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp312-cp312-win_amd64.whl

Download URL aurivis_simd-0.1.0-cp312-cp312-win_amd64.whl
Size 67.3 kB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
206ee4987a12083df0fb149e56bf769a58c05089312220d9e57eeb730242a98b
BLAKE2b-256 checksum
How to use checksums
a45f51cbeeec0efab203d20ba65b3027566ee62313c2c42e9e0825e04759c1bc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp312-cp312-musllinux_1_2_x86_64.whl

Download URL aurivis_simd-0.1.0-cp312-cp312-musllinux_1_2_x86_64.whl
Size 1.3 MB
Tags CPython 3.12 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
408ecae69eb5bd01c62eb844b68d101e85149a4d6b943096e3f8e518cc05f082
BLAKE2b-256 checksum
How to use checksums
d78447460b8e378c544e41b3b84026677882f2563ebbca947d0715afdf33bdca
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp312-cp312-musllinux_1_2_aarch64.whl

Download URL aurivis_simd-0.1.0-cp312-cp312-musllinux_1_2_aarch64.whl
Size 1.2 MB
Tags CPython 3.12 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
8b774871bd4f058c1bcf96807106782a87562db0a4ac4d43e122008308593ecf
BLAKE2b-256 checksum
How to use checksums
6d0ff11c5a62e457caef2198dbc215860f1b35a5003cf8f6a58eb2519d897ecf
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL aurivis_simd-0.1.0-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 241.5 kB
Tags CPython 3.12 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
623321002e01e6453a32fff077885aaa0d7f39742c9c1075cded75739e583b3b
BLAKE2b-256 checksum
How to use checksums
db17ab61db911606c2a4d9f9a93f49dc9e7d6497658798bb09c220486d8bc2f8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp312-cp312-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl

Download URL aurivis_simd-0.1.0-cp312-cp312-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
Size 247.5 kB
Tags CPython 3.12 Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64
SHA-256 checksum
How to use checksums
d2d33f3f3fa782494c76eaedaf02deff454bdc26f8332ce42c0495657c210188
BLAKE2b-256 checksum
How to use checksums
1b6404a0f8ed616c73134972e4d1b66ac791b0f47c0522c06e41723b6c87bf1a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp312-cp312-macosx_11_0_arm64.whl

Download URL aurivis_simd-0.1.0-cp312-cp312-macosx_11_0_arm64.whl
Size 71.0 kB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
18eef9dec819e40e3e81b3c3b501d71d20e2193f3393efa5ff65ea40054944cf
BLAKE2b-256 checksum
How to use checksums
fda3eb40246907286c28e5973579b2c085de33682415b95ad8c3c498f5ce7770
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp312-cp312-macosx_10_13_x86_64.whl

Download URL aurivis_simd-0.1.0-cp312-cp312-macosx_10_13_x86_64.whl
Size 70.4 kB
Tags CPython 3.12 macOS 10.13+ x86-64
SHA-256 checksum
How to use checksums
77247f62a49b433aae02f0a9e05ee256ddc2658857b7589b89a3bb2c85aa9056
BLAKE2b-256 checksum
How to use checksums
131579313f967936055d5d467f7594d239cb9df68e8034c2e44ea8f96c66005d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp311-cp311-win_arm64.whl

Download URL aurivis_simd-0.1.0-cp311-cp311-win_arm64.whl
Size 64.1 kB
Tags CPython 3.11 Windows ARM64
SHA-256 checksum
How to use checksums
ad83867c1396830239e10068e2f78c4ed7a2b73c1de38a51dd5587be5e143bba
BLAKE2b-256 checksum
How to use checksums
ae271c12bb63107fcdc8875e648093d5f220b094222b4283b7511cb640ec0ad2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp311-cp311-win_amd64.whl

Download URL aurivis_simd-0.1.0-cp311-cp311-win_amd64.whl
Size 67.1 kB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
ae7806ff31c1ab3bb878cc921030e14c35a70d967b2a8f08267e261ecd3bf81f
BLAKE2b-256 checksum
How to use checksums
dcc6e8f25315e2c1953bb81d677627722fd5b984c636f5ea73c177479557b2d3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp311-cp311-musllinux_1_2_x86_64.whl

Download URL aurivis_simd-0.1.0-cp311-cp311-musllinux_1_2_x86_64.whl
Size 1.3 MB
Tags CPython 3.11 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
d60c3db7da1ddc6e1669718263d3653ecc7bc262a08d74acef6e9e3edf828624
BLAKE2b-256 checksum
How to use checksums
755c1c1d9821e0bfafcfc939aff6cf339954c91ee7b5e197b0af8f6dc565f822
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp311-cp311-musllinux_1_2_aarch64.whl

Download URL aurivis_simd-0.1.0-cp311-cp311-musllinux_1_2_aarch64.whl
Size 1.2 MB
Tags CPython 3.11 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
c202982d354e66dd21197e2406309a9265b38a2ed9f639b47fd43595e0ae63a9
BLAKE2b-256 checksum
How to use checksums
4d1091687c3f06f7666098c03573143c798ec74c04729d5dcf5a4353bae9cd50
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL aurivis_simd-0.1.0-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 229.8 kB
Tags CPython 3.11 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
d600b61d1ee006d7c2afa694b803244398e911aaf353f3912a04ebefab168be6
BLAKE2b-256 checksum
How to use checksums
08f512bb8d9a20783ef96d6dae96e5279f4dc350aba4f6fc26064255cd3e366b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp311-cp311-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl

Download URL aurivis_simd-0.1.0-cp311-cp311-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
Size 234.3 kB
Tags CPython 3.11 Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64
SHA-256 checksum
How to use checksums
c64532483b37cac61419f75e13a5eccdabb086ff1f97891351ddd79515bb0ea0
BLAKE2b-256 checksum
How to use checksums
bc98285f2cc62fd7d7a5022908b1aee56df155d8d9e31191577494a476d22181
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp311-cp311-macosx_11_0_arm64.whl

Download URL aurivis_simd-0.1.0-cp311-cp311-macosx_11_0_arm64.whl
Size 70.3 kB
Tags CPython 3.11 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
566efc6b818edac68eb1d7dce30d103db2431e09307da9c1b7fb77fe348e5ae0
BLAKE2b-256 checksum
How to use checksums
34874aaed50e558212a522e8e6b7821c00dadf924684761e2caa17782d967c88
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / aurivis_simd-0.1.0-cp311-cp311-macosx_10_9_x86_64.whl

Download URL aurivis_simd-0.1.0-cp311-cp311-macosx_10_9_x86_64.whl
Size 69.8 kB
Tags CPython 3.11 macOS 10.9+ x86-64
SHA-256 checksum
How to use checksums
50ee1eee24b18a0401834c7930e8feffbf45624eb0bc0355e39dac368333b6a5
BLAKE2b-256 checksum
How to use checksums
93a0cf8b258b246b74527ff27976de449c6f1c96eb76d3395d6321741f6e9f38
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.0 This release

33 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page