Skip to main content
Yanked

This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Consider using release 3.0.1 instead.
Reason given by maintainers: built windows/macos wheels

edge

Minimalistic C++20 rendering library with Vulkan, OpenGL ES 3.0 / WebGL 2 and Metal backends, and Python bindings (pyedge).

It has everything you need to load geometry, render it and develop your code in a platform and API independent manner.

It can read glTF and has an in-house fast-loading .edge format for models with support for LODs and mip chains.

It is meant to be read and changed: there is no scene editor, no scripting layer (except Python bindings) and no asset store.

It was refactored from a game engine from 2004 to render many scenes in parallel for robotics simulation (cameras, depth and lidar images for training and testing), where a general-purpose engine was too slow. Much of the binding code, refactorings, new backends and documentation were written with Claude and curated by the author. The library was also used successfully to build computer games which are running on MacOS, Windows, Linux, iOS, Android, and even web browsers.

Features

  • Backends: Vulkan 1.0 with VK_KHR_maintenance1 (Linux, Windows, Android, macOS through MoltenVK), OpenGL ES 3.0 and WebGL 2 (Emscripten), Metal (Apple silicon, macOS 13 and iOS 15 on), and a null renderer that keeps every rule and draws nothing (for tests). The frame and pass order and the error behaviour are the same on every backend.
  • Headless and parallel: renderers share no state, so a process runs one per thread, each offscreen, on one GPU or several. Frames in flight (1 to 4), batched texture downloads, GPU timers.
  • glTF 2.0: meshes, PBR metallic-roughness materials (normal, occlusion and emissive maps), KHR_texture_transform, skins and animations (linear, step and cubic), vertex colours, several UV sets. Loading is strict: a malformed file is an error that names what is wrong.
  • The .edge format and edge_convert: models converted ahead of time, with BC7 or ASTC textures and their mip chains, levels of detail (meshoptimizer), texture atlases (grid or xatlas), tiled ground meshes and pose bounds for skinned meshes. CMake helpers rebuild a model only when its inputs change.
  • Rendering: render targets with several colour attachments, layers and cube faces; readable depth and stencil; instancing; blended draws sorted back to front; levels of detail chosen by pixel error; frustum culling; debug lines; text (stb_truetype); a Dear ImGui renderer; a full-screen copy and a frame presenter for windows.
  • Shaders: GLSL 4.50 compiled to SPIR-V, and translated for GLES and Metal at build time. edge.glsl is the binding contract a custom shader includes, with BRDF, material and skinning helpers beside it.
  • Python: pyedge (nanobind) exposes renderers, models, materials, cameras and textures; downloads arrive as NumPy arrays, long calls release the GIL, and the module is built free-threaded for Python 3.14t.
  • edge_shot: draws a model to a PNG, a contact sheet of many, or a window to inspect it.

Status

edge is developed for the author's own projects, which use it in production. The API still changes between versions; see CHANGELOG.md. Contributions are welcome: see CONTRIBUTING.md.

Requirements

  • CMake 3.20 or newer, Ninja, a C++20 compiler (GCC 12, Clang 15, Apple Clang 15, MSVC 19.3x)
  • rove, the math library, checked out beside edge (../rove) or given with -DEDGE_ROVE_SOURCE_DIR=<path>
  • For Vulkan: the Vulkan headers and loader and glslangValidator. Without them edge builds without the Vulkan backend.
  • For OpenGL ES (-DEDGE_GLES=ON): GLES3/gl3.h and libGLESv3. For Metal: Xcode.
  • SDL3 for edge_sdl (windows and contexts), Boost.Test for the tests, Python 3.8 or newer with NumPy and pytest for pyedge
  • Network access on the first configure: the other dependencies are fetched at pinned versions (see THIRD_PARTY.md)

Install

pip (pip install pyedge, Linux wheels), Git submodules beside rove, Conan, vcpkg, or installed from source: docs/install.md has each, with the CMake that uses it:

add_subdirectory(rove)
add_subdirectory(edge)                            # or find_package(edge CONFIG REQUIRED)
target_link_libraries(my_app PRIVATE edge::edge)  # brings rove, spdlog, cereal and Vulkan

edge_add_shaders(my_shaders DESTINATION ${CMAKE_BINARY_DIR}/shaders SOURCES src/sea.vert src/sea.frag)
edge_bundle_runtime(my_runtime DESTINATION ${CMAKE_BINARY_DIR})     # edge's shaders beside the binary
edge_convert_models(my_models SOURCE_DIR ${CMAKE_SOURCE_DIR}/assets DESTINATION ${CMAKE_BINARY_DIR}/models)

Build and test

git clone https://github.com/mnvl/rove
git clone https://github.com/mnvl/edge
cmake -S edge -B edge/build -G Ninja -DCMAKE_BUILD_TYPE=RelWithDebInfo
cmake --build edge/build
ctest --test-dir edge/build -j$(nproc) --output-on-failure

Without a GPU, Mesa's lavapipe (Vulkan) and llvmpipe (OpenGL ES) run the whole test suite on the CPU; etc/container/test.sh builds and tests edge in such a Linux container.

A frame

#include <edge/camera.h>
#include <edge/load_model.h>
#include <edge/scheduler.h>
#include <edge/vulkan_renderer.h>

auto renderer = std::make_shared<edge::VulkanRenderer>(640, 480);
auto scheduler = std::make_shared<edge::Scheduler>(renderer);
auto model = edge::load_model(renderer, scheduler, "robot.glb");     // a .glb, .gltf or .edge file
auto target = renderer->create_render_target(640, 480, edge::RenderTargetFormat());

auto camera = std::make_shared<edge::Camera>();
camera->set_perspective_projection(1.0f, 640.0f / 480.0f, 0.1f, 100.0f);
camera->look_at({0, 1, 4}, {0, 1, 0}, {0, 1, 0});

renderer->begin_frame();
model->draw(camera, rove::matrix<4, 4>());          // queues the model's draw calls
renderer->begin_pass(target);                        // cleared to black
scheduler->flush();                                  // sorted, culled, drawn
renderer->end_pass();
renderer->finish_frame();                            // waits for the GPU: the target can be downloaded now

From Python the calls are the same (pyedge.create_renderer(640, 480), renderer.begin_frame(), ...), and a downloaded texture is a NumPy array (texture.to_numpy()). examples/ has complete scripts.

Documentation

docs/install.md pip, Git submodules, Conan, vcpkg, installing from source
docs/building.md Requirements, CMake options, the install tree, where shaders are found
docs/architecture.md Conventions, the frame, backends, threads, design decisions
docs/coordinates.md World and clip space, matrix order, the viewport flip, winding, pixel formats
docs/shaders.md Writing shaders against edge.glsl
docs/render-targets.md Targets of several colours, layers and cube faces
docs/models.md Model types, ModelBuilder, the .edge format
docs/python.md pyedge
docs/tools.md edge_shot, edge_convert, CMake helpers for a game
docs/logging.md The log and its levels

The headers in src/ document each class and function.

License

MIT; see LICENSE. The libraries edge fetches when it is built are listed with their licenses in THIRD_PARTY.md.

Metadata

Release files for pyedge 3.0.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 pyedge 3.0.0
File Size Uploaded Provenance Actions
pyedge-3.0.0.tar.gz 356.2 kB With provenance Details for pyedge-3.0.0.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for pyedge 3.0.0
File Actions
pyedge-3.0.0-cp314-cp314t-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.14 CPython 3.14 free-threading Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details for pyedge-3.0.0-cp314-cp314t-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
pyedge-3.0.0-cp314-cp314t-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl CPython 3.14 CPython 3.14 free-threading Linux glibc 2.28+ ARM64, Linux glibc 2.27+ ARM64 Details for pyedge-3.0.0-cp314-cp314t-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
pyedge-3.0.0-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.27+ x86-64, Linux glibc 2.28+ x86-64 Details for pyedge-3.0.0-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
pyedge-3.0.0-cp314-cp314-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl CPython 3.14 CPython 3.14 Linux glibc 2.28+ ARM64, Linux glibc 2.27+ ARM64 Details for pyedge-3.0.0-cp314-cp314-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
pyedge-3.0.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details for pyedge-3.0.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
pyedge-3.0.0-cp313-cp313-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl CPython 3.13 CPython 3.13 Linux glibc 2.28+ ARM64, Linux glibc 2.27+ ARM64 Details for pyedge-3.0.0-cp313-cp313-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
pyedge-3.0.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.27+ x86-64, Linux glibc 2.28+ x86-64 Details for pyedge-3.0.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
pyedge-3.0.0-cp312-cp312-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl CPython 3.12 CPython 3.12 Linux glibc 2.28+ ARM64, Linux glibc 2.27+ ARM64 Details for pyedge-3.0.0-cp312-cp312-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
pyedge-3.0.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details for pyedge-3.0.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
pyedge-3.0.0-cp311-cp311-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl CPython 3.11 CPython 3.11 Linux glibc 2.27+ ARM64, Linux glibc 2.28+ ARM64 Details for pyedge-3.0.0-cp311-cp311-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
pyedge-3.0.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details for pyedge-3.0.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
pyedge-3.0.0-cp310-cp310-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl CPython 3.10 CPython 3.10 Linux glibc 2.27+ ARM64, Linux glibc 2.28+ ARM64 Details for pyedge-3.0.0-cp310-cp310-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
pyedge-3.0.0-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.9 CPython 3.9 Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details for pyedge-3.0.0-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
pyedge-3.0.0-cp39-cp39-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl CPython 3.9 CPython 3.9 Linux glibc 2.27+ ARM64, Linux glibc 2.28+ ARM64 Details for pyedge-3.0.0-cp39-cp39-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl

Total release size: 26.9 MB

Release files / pyedge-3.0.0.tar.gz

Download URL pyedge-3.0.0.tar.gz
Size 356.2 kB
Tags Source
SHA-256 checksum
How to use checksums
9b225f6a5ae847f48f63235e896e3a732b49f9f6006d32f7595cb1d58cf2f5f1
BLAKE2b-256 checksum
How to use checksums
389ede46d6ac416ef80d93e2785f2a6654c7658a3cbff7569497d8eedeaff929
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 6, 2026.

Transparency log

Release files / pyedge-3.0.0-cp314-cp314t-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL pyedge-3.0.0-cp314-cp314t-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 2.0 MB
Tags CPython 3.14 CPython 3.14 free-threading Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
ebde1ee8838a1890dfaf20de2b5874c8b8ac10487b265f829a7b4f175c798340
BLAKE2b-256 checksum
How to use checksums
4a7821e37904a2fc5f53e2eae41c53621a681734b33077b2c278444bf11eaf60
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 6, 2026.

Transparency log

Release files / pyedge-3.0.0-cp314-cp314t-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl

Download URL pyedge-3.0.0-cp314-cp314t-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
Size 1.8 MB
Tags CPython 3.14 CPython 3.14 free-threading Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
f538f35aa8d44e8de80722d40b90978011d8268293288bfcff5e205bb81d31cc
BLAKE2b-256 checksum
How to use checksums
729149c71f853a9fca45a7f91c047d09e52880e2b15243e498a06fa0da84e100
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 6, 2026.

Transparency log

Release files / pyedge-3.0.0-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL pyedge-3.0.0-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 2.0 MB
Tags CPython 3.14 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
873e2a162f97c17a53dbe74a38831efa53b5b5f10020c3af9b7146a18190bb94
BLAKE2b-256 checksum
How to use checksums
0d42dc1db6b2b808474966f0cd005e4b3c45c02416599392426aa5735d466329
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 6, 2026.

Transparency log

Release files / pyedge-3.0.0-cp314-cp314-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl

Download URL pyedge-3.0.0-cp314-cp314-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
Size 1.8 MB
Tags CPython 3.14 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
b5685532590e5678e6d34e0e1718105a270042794ced3ac7a32931a8c4624db8
BLAKE2b-256 checksum
How to use checksums
bc2458c9d5879a290565f933918e27885a95bd927dc3af574bdd1f9b84d0ac1c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 6, 2026.

Transparency log

Release files / pyedge-3.0.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL pyedge-3.0.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 2.0 MB
Tags CPython 3.13 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
862c5c7dffe4ba1f732856f1391ea163c754145d73971788bbacb11f4ddfa51f
BLAKE2b-256 checksum
How to use checksums
af7eb570f03fe1cf8e65db2fb9b3f494eb11b94f4b95c4df1802351662b89b77
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 6, 2026.

Transparency log

Release files / pyedge-3.0.0-cp313-cp313-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl

Download URL pyedge-3.0.0-cp313-cp313-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
Size 1.8 MB
Tags CPython 3.13 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
2e3fe77e34f77e904d0c9f34856abec7e4697f0e4291e920a410b4830626a771
BLAKE2b-256 checksum
How to use checksums
58e31c0f5c6142fb6fb2718ebc0a73a26944d27a2af33a6417c954867b243274
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 6, 2026.

Transparency log

Release files / pyedge-3.0.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL pyedge-3.0.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 2.0 MB
Tags CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
e4153fe7c0c9eb65a659ed14576e35d41516a3383543121bfcc2b20bd635455c
BLAKE2b-256 checksum
How to use checksums
af60dc44788e61598661d5d54a39df21163b40825d5539eeffabc59bde48e202
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 6, 2026.

Transparency log

Release files / pyedge-3.0.0-cp312-cp312-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl

Download URL pyedge-3.0.0-cp312-cp312-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
Size 1.8 MB
Tags CPython 3.12 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
41c7aa4e34b178953fb5fd33e475b6244c54c3f26ccfb1802613b0552d45f38c
BLAKE2b-256 checksum
How to use checksums
afbc39e35ac2b05f4870551ac8349c1ec2bab88ec4bb827490e4911764048444
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 6, 2026.

Transparency log

Release files / pyedge-3.0.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL pyedge-3.0.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 2.0 MB
Tags CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
8634e2174cc226e4797b0c990d2d53af7de0e8f723f71c65e69ab88da5802052
BLAKE2b-256 checksum
How to use checksums
0e88365ee2fb9d4375acead7e5709682f4604fbe616adb99fbb47a852ee4bb43
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 6, 2026.

Transparency log

Release files / pyedge-3.0.0-cp311-cp311-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl

Download URL pyedge-3.0.0-cp311-cp311-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
Size 1.8 MB
Tags CPython 3.11 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
52844a8d49a0f0f22a5cef5e563d6778848855955c40e28a1ea8332ffbd2c377
BLAKE2b-256 checksum
How to use checksums
83da6b715797615e5e8af7b3bab17571e2656635743d08f327f44a0554f001df
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 6, 2026.

Transparency log

Release files / pyedge-3.0.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL pyedge-3.0.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 2.0 MB
Tags CPython 3.10 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
2259ed87a48f6efde9daf168558fe20ce589f5aa8f1d69de0ec7584ac86a3ff0
BLAKE2b-256 checksum
How to use checksums
3390e2aa1522c6a9b5d61e794d3c3ea0a1ab0d77fc29b415055d4fecdf5a053e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 6, 2026.

Transparency log

Release files / pyedge-3.0.0-cp310-cp310-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl

Download URL pyedge-3.0.0-cp310-cp310-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
Size 1.8 MB
Tags CPython 3.10 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
d730c46f9c2221659379428d9fc0f6589473b0ea0511f3f2199f236ed0d6b0d1
BLAKE2b-256 checksum
How to use checksums
7f980cc63e1017c00e220bdf86698443fa4fd5e1513c02e8270aa5373adb1d4d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 6, 2026.

Transparency log

Release files / pyedge-3.0.0-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL pyedge-3.0.0-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 2.0 MB
Tags CPython 3.9 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
5d833fa7e72af339047bbe07f16626eb39b258cb71d28021bce852cf3da55d33
BLAKE2b-256 checksum
How to use checksums
c5e0a6e7f3552301ce9bbb6d810f09b37350d4c5277706ebdbb4e8754c211d74
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 6, 2026.

Transparency log

Release files / pyedge-3.0.0-cp39-cp39-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl

Download URL pyedge-3.0.0-cp39-cp39-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
Size 1.8 MB
Tags CPython 3.9 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
4122e89c63c1e90b76aeb0f0ff7873b3710c1cfa48fbe594efe4e45a57a5e87d
BLAKE2b-256 checksum
How to use checksums
719f68f9f0e57d945edac2c517f21c74444fdc24cc7a07bd6130983d5ac2dfce
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 6, 2026.

Transparency log

Security for pyedge 3.0.0

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.

Full provenance

All 15 files in this release have been uploaded with provenance metadata.

Select from 15 files

Attestation for pyedge-3.0.0.tar.gz

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 Nov 6, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

3.0.0 This release

15 release files Full provenance

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