Skip to main content

website documentation

Code quality Test suite Coverage

Testing Linux/Ubuntu Testing macOS Testing Windows

pre-commit ruff-formatter ruff-linter

BeamMe (previously MeshPy) is a general purpose 3D beam finite element input generator written in Python. It contains advanced geometry creation and manipulation functions to create complex beam geometries, including a consistent handling of finite rotations. It can be used to create input files for the following finite element solvers (adaption to other solvers is easily possibly):

  • 4C (academic finite element solver)
  • Abaqus (commercial software package)
  • AceFEM (Finite element package for automation of the finite element method in Mathematica)

BeamMe is jointly developed at the Institute for Mathematics and Computer-Based Simulation (IMCS) at the Universität der Bundeswehr München and the Institute for Computational Mechanics (LNM) at the Technical University Munich.

Overview

Examples

Honeycomb structure under tension
Fiber reinforced composite plate
Fiber reinforced pipe under pressure
Fiber reinforcements of a twisted plate

How to use BeamMe?

BeamMe provides example notebooks to showcase its core features and functionality. The examples can be found in the examples/ directory. They can be run locally or directly tested from your browser via the following links:

  • Example 1: Finite rotation framework Binder
  • Example 2: Core mesh generation functions Binder

You can also interactively test the entire BeamMe framework directly from your browser here Binder

Getting started

This example demonstrates how to create a small structural model using BeamMe:

from beamme.core.element_beam import Beam3
from beamme.core.material import MaterialBeamBase
from beamme.core.mesh import Mesh
from beamme.mesh_creation_functions.beam_helix import create_beam_mesh_helix

# Create a new empty BeamMe mesh container
mesh = Mesh()

# Create a helical beam structure (other options include lines, arcs, curves, ...)
create_beam_mesh_helix(
    mesh=mesh,  # The helix will be added to this mesh
    beam_class=Beam3,  # Type of beam element for the line
    material=MaterialBeamBase(radius=0.05, nu=0.3, youngs_modulus=10, density=1.0),  #  Simple circular cross-section beam material
    axis_vector=[1, 1, 1],  # Vector for the orientation of the helical center axis
    axis_point=[0, 0, 0],  # Point defining the helical center axis
    start_point=[1, 0, 0],  # Start point of the helix. Defines the radius.
    height_helix=5,  # Height of helix
    turns=1.5,  # Number of turns
    n_el=20,  # Number of beam elements along the helix
)

# Visualize the final structure with PyVista
mesh.display_pyvista()

# Alternatively, write the mesh to a VTK file that can be opened in ParaView.
mesh.write_vtu("getting_started.vtu")

This will open the following window, displaying the created beam structure:

How to cite BeamMe?

Whenever you use or mention BeamMe in some sort of scientific document, publication or presentation, please cite BeamMe as

BeamMe: A general purpose 3D beam finite element input generator, https://beamme-py.github.io/beamme

This could be done with the following BiBTeX entry:

@misc{BeamMe,
  author       = {{BeamMe Authors}},
  title        = {{B}eam{M}e -- {A} general purpose {3D} beam finite element input generator},
  howpublished = {\url{https://beamme-py.github.io/beamme}},
  year         = {YEAR},
  note         = {Accessed: DATE}
}

Feel free to leave a ⭐️ on GitHub.

Work that uses BeamMe

Peer-reviewed articles

  1. Ranno, A., Manjunatha, K., Koritzius, T., Steinbrecher, I., Hosters, N., Nachtsheim, M., Nilcham, P., Schaaps, N., Turoni-Glitz, A., Datz, J., Popp, A., Linka, K., Vogt, F., and Behr, M. (2025): A computational model of coronary arteries with in-stent restenosis coupling hemodynamics and pharmacokinetics with growth mechanics. Scientific Reports, 15, 39229 https://doi.org/10.1038/s41598-025-22291-w
  2. Steinbrecher, I., Hagmeyer, N. Meier, C., Popp, A. (2025): A consistent mixed-dimensional coupling approach for 1D Cosserat beams and 2D surfaces in 3D space. Computational Mechanics, 76(5), 1233-1260, https://doi.org/10.1007/s00466-025-02647-9
  3. Datz, J.C., Steinbrecher, I., Meier, C., Engel, L.C., Popp, A., Pfaller, M.R., Schunkert, H., Wall, W.A. (2025): Patient-specific coronary angioplasty simulations — A mixed-dimensional finite element modeling approach. Computers in Biology and Medicine, 189, 109914, https://doi.org/10.1016/j.compbiomed.2025.109914
  4. Firmbach, M., Steinbrecher, I., Popp, A., Mayr, M. (2024): An approximate block factorization preconditioner for mixed-dimensional beam-solid interaction. Computer Methods in Applied Mechanics and Engineering, 431, 117256. https://doi.org/10.1016/j.cma.2024.117256
  5. Hagmeyer, N., Mayr, M., Popp, A. (2024): A fully coupled regularized mortar-type finite element approach for embedding one-dimensional fibers into three-dimensional fluid flow. International Journal for Numerical Methods in Engineering, 125, e7435, https://doi.org/10.1002/nme.7435
  6. Steinbrecher, I., Popp, A., Meier, C. (2022): Consistent coupling of positions and rotations for embedding 1D Cosserat beams into 3D solid volumes, Computational Mechanics, 69(3), 701–732. https://doi.org/10.1007/s00466-021-02111-4
  7. Hagmeyer, N., Mayr, M., Steinbrecher, I., Popp, A. (2022): One-way coupled fluid-beam interaction: Capturing the effect of embedded slender bodies on global fluid flow and vice versa. Advanced Modeling and Simulation in Engineering Sciences, 9, https://doi.org/10.1186/s40323-022-00222-y
  8. Steinbrecher, I., Mayr, M., Grill, M.J., Kremheller, J., Meier, C., Popp, A. (2020): A mortar-type finite element approach for embedding 1D beams into 3D solid volumes, Computational Mechanics, 66(6), 1377–1398. https://doi.org/10.1007/s00466-020-01907-0

PhD thesis

  1. Hagmeyer, N.: A computational framework for balloon angioplasty and stented arteries based on mixed-dimensional modeling, https://athene-forschung.rz.unibw-muenchen.de/146359, (2023)
  2. Steinbrecher, I.: Mixed-dimensional finite element formulations for beam-to-solid interaction, https://athene-forschung.unibw.de/143755, (2022)

Installation

Python environment

BeamMe is tested with, and supports Python versions 3.11-3.14. It is recommended to use a virtual Python environment such as Conda/Miniforge or venv.

  • A Conda/Miniforge environment can be created and loaded with
    # Create the environment (this only has to be done once)
    conda create -n beamme python=3.14
    # Activate the environment
    conda activate beamme
    
  • A venv virtual environment can be created and loaded with (on Debian systems the following packages might have to be installed: sudo apt-get install python3-venv python3-dev)
    # Create the environment (this only has to be done once)
    python -m venv <path-to-env-folder>/beamme-env
    # Activate the environment
    source <path-to-env-folder>/beamme-env/bin/activate
    

Install BeamMe via pip / PyPI (latest release)

You can quickly install BeamMe into your current environment using pip:

pip install beamme

Optional dependencies (for development and extra features) can be installed with: pip install "beamme[dev]"

Note: On Zsh, you may need to quote the brackets as shown to avoid shell expansion.

Install BeamMe from GitHub (most recent version)

If you want to install the current main version of BeamMe directly from GitHub, simply run:

pip install git+https://github.com/beamme-py/beamme.git@main

Install BeamMe from source

You can either install BeamMe directly from the source in a non-editable and editable fashion like:

  • Non-editable: This allows you to use BeamMe, but changing the source code will not have any effect on the installed package
    git clone git@github.com:beamme-py/beamme.git
    cd beamme
    pip install .
    
  • Editable: This allows you to change the source code without reinstalling the module
    git clone git@github.com:beamme-py/beamme.git
    cd beamme
    pip install -e .
    

Now you are able to use BeamMe. A good way to get started is by going through the examples

jupyter notebook examples/

If you also want to execute the associated test suite check out our development section.

Optional dependencies

4C

BeamMe can run 4C simulations directly from within a Python script, allowing for full control over arbitrarily complex simulation workflows. Fore more information, please have a look at the beamme.four_c.run_four_c module.

CubitPy

CubitPy is a Python library that contains utility functions extending the Cubit/Coreform Python interface. Furthermore, it allows for the easy creation of 4C-compatible input files directly from within Python. BeamMe can import meshes created with CubitPy and allows for further modification and manipulation of them.

CubitPy can be installed as an optional dependency with:

pip install -e .[cubitpy]

BeamMe can optionally execute its geometric search functions using the C++ library ArborX. First make sure the pybind11 submodule is loaded

cd <path_to_beamme>
git submodule update --init

To setup BeamMe with ArborX, CMake and Kokkos have to be available on your system (the preferred variant is via Spack). Create a build directory

mkdir -p <path_to_beamme>/src/build/geometric_search

Configure cmake and build the extension

cd <path_to_beamme>/build/geometric_search
cmake ../../beamme/geometric_search/src/
make -j4

Note: Currently ArborX only works if BeamMe is installed in editable mode.

Developing BeamMe

If you want to actively develop BeamMe or run the test suite, you must install BeamMe in editable (-e) mode and with our optional developer dependencies ([dev]) like

pip install -e ".[dev]" # Quotation marks are required for some shells

You can now run the BeamMe test suite to check that everything worked as expected

pytest

Coding guidelines

  • When working on BeamMe, use a leading underscore (_) to indicate functions, classes, and variables that are intended for internal use only. This is a coding convention rather than an enforced rule, so apply it where it improves code clarity, especially for functions that check consistency or modify internal states.

  • To avoid ambiguous or incorrect imports when using BeamMe as a library, internal imports must follow a strict aliasing convention as illustrated below:

    Import guidelines
    # Not OK
    import numpy  # No alias
    import numpy as np  # Missing leading underscore
    
    from numpy import *  # Wildcard imports
    from numpy import _core  # We don't allow the import of private functionality
    from numpy.linalg import norm  # No alias
    from numpy import sin as sin2  # Missing leading underscore
    from beamme.core.mesh import Mesh as _BeamMesh  # BeamMe imports have to be aliased with the same name, i.e., should be `_Mesh` (imports from third party libraries can be renamed)
    
    # OK
    import numpy as _np
    import sys as _sys
    
    from pathlib import Path as _Path
    
    from math import sin as _math_sin
    from numpy import sin as _np_sin
    
    import beamme.core.conf as _conf
    from beamme.core.mesh import Mesh as _Mesh
    from beamme.core.node import Node as _Node
    from beamme.core.node import NodeCosserat as _NodeCosserat
    

Testing

BeamMe provides a flexible testing system where additional tests can be enabled using specific flags. The following flags can be used with pytest to enable specific test sets:

  • --exclude-standard-tests: Disables the default test suite
  • --4C: Runs tests related to 4C integration
  • --ArborX: Enables tests for ArborX-related functionality
  • --Coreform: Runs tests that require Coreform Cubit
  • --performance-tests: Includes performance tests

These flags can be combined arbitrarily; for example, to run the 4C, Coreform Cubit, and ArborX tests but exclude the default test suite, use:

# 4C Tests require a path to a 4C executable
export BEAMME_FOUR_C_EXE=<path_to_4C>
# Coreform Tests require a path to a CubitPy configuration file
export CUBITPY_CONFIG_PATH=<path_to_CubitPy_config_file>

pytest --4C --ArborX --Coreform --exclude-standard-tests

Some performance critical geometric search algorithms in BeamMe are written in Cython. If Cython code is changed, it has to be recompiled. This can be done by running

python setup.py build_ext --inplace

Contributing

If you are interested in contributing to BeamMe, we welcome your collaboration. For general questions, feature request and bug reports please open an issue.

If you contribute actual code, fork the repository and make the changes in a feature branch. Depending on the topic and amount of changes you also might want to open an issue. To merge your changes into the BeamMe repository, create a pull request to the main branch. A few things to keep in mind:

  • Read our coding guidelines.
  • It is highly encouraged to add tests covering the functionality of your changes, see the test suite in tests/.
  • To maintain high code quality, BeamMe uses a number of different pre-commit hooks to check committed code. Make sure to set up the pre-commit hooks before committing your changes
    pre-commit install
    
  • Check that you did not break anything by running the BeamMe tests. For most changes it should be sufficient to run the standard test suite:
    pytest
    
  • Feel free to add yourself to the authors section in the README.md file.

Authors

Maintainers

  • Ivo Steinbrecher (@isteinbrecher)
  • David Rudlstorfer (@davidrudlstorfer)

Contributors (in alphabetical order)

  • Dao Viet Anh
  • Max Firmbach (@maxfirmbach)
  • Martin Frank (@knarfnitram)
  • Nora Hagmeyer (@NoraHagmeyer)
  • Matthias Mayr (@mayrmt)
  • Gabriela Loera (@eulovi)

Metadata

Release files for BeamMe 0.3.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 BeamMe 0.3.0
File Size Uploaded
beamme-0.3.0.tar.gz 2.8 MB Details

Built distributions (wheels)

Table of built distributions (wheels) for BeamMe 0.3.0
File
beamme-0.3.0-cp314-cp314-win_amd64.whl CPython 3.14 CPython 3.14 Windows x86-64 Details
beamme-0.3.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.28+ x86-64, Linux glibc 2.5+ x86-64 Details
beamme-0.3.0-cp314-cp314-macosx_11_0_arm64.whl CPython 3.14 CPython 3.14 macOS 11.0+ ARM64 Details
beamme-0.3.0-cp313-cp313-win_amd64.whl CPython 3.13 CPython 3.13 Windows x86-64 Details
beamme-0.3.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
beamme-0.3.0-cp313-cp313-macosx_11_0_arm64.whl CPython 3.13 CPython 3.13 macOS 11.0+ ARM64 Details
beamme-0.3.0-cp312-cp312-win_amd64.whl CPython 3.12 CPython 3.12 Windows x86-64 Details
beamme-0.3.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
beamme-0.3.0-cp312-cp312-macosx_11_0_arm64.whl CPython 3.12 CPython 3.12 macOS 11.0+ ARM64 Details
beamme-0.3.0-cp311-cp311-win_amd64.whl CPython 3.11 CPython 3.11 Windows x86-64 Details
beamme-0.3.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
beamme-0.3.0-cp311-cp311-macosx_11_0_arm64.whl CPython 3.11 CPython 3.11 macOS 11.0+ ARM64 Details

Total release size: 7.0 MB

Release files / beamme-0.3.0.tar.gz

Download URL beamme-0.3.0.tar.gz
Size 2.8 MB
Tags Source
SHA-256 checksum
How to use checksums
06ce0e951fd26edd144acd097c68bf83c94309a974976de62941d2974cc2d6c5
BLAKE2b-256 checksum
How to use checksums
462ae0d9ba78972c0a8bc81c1585247db6a8861260e573b3e283319dd65ab8ab
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 Jul 8, 2026.

Transparency log

Release files / beamme-0.3.0-cp314-cp314-win_amd64.whl

Download URL beamme-0.3.0-cp314-cp314-win_amd64.whl
Size 250.2 kB
Tags CPython 3.14 Windows x86-64
SHA-256 checksum
How to use checksums
cbe8dff7941860dc568555c6e7f8b9a7e551e11340b73fc34fbf0c4eff2639e5
BLAKE2b-256 checksum
How to use checksums
d325aeb3517bd1758dde64eea1fb2cd96d98539e5d959e1507b96fe134338ff2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 Jul 8, 2026.

Transparency log

Release files / beamme-0.3.0-cp314-cp314-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl

Download URL beamme-0.3.0-cp314-cp314-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
Size 448.9 kB
Tags CPython 3.14 Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64
SHA-256 checksum
How to use checksums
4febd3c5d0be1e0c6d39714d35dadc14f26dba184d0f85daeac8d6b523697145
BLAKE2b-256 checksum
How to use checksums
fd5cbb720e9dd61adfe490a2b4028e3cf63fec814b97f00accd71a66e4173477
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 Jul 8, 2026.

Transparency log

Release files / beamme-0.3.0-cp314-cp314-macosx_11_0_arm64.whl

Download URL beamme-0.3.0-cp314-cp314-macosx_11_0_arm64.whl
Size 336.4 kB
Tags CPython 3.14 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
669b6499b9fbd6c03fe5ed970092b72ba30bf6e04dd797120e185be22328af4c
BLAKE2b-256 checksum
How to use checksums
a8f5de939f4974e6c97a88e0e9b11bc5d81c327d0e2311e12eddd8c55682bcad
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 Jul 8, 2026.

Transparency log

Release files / beamme-0.3.0-cp313-cp313-win_amd64.whl

Download URL beamme-0.3.0-cp313-cp313-win_amd64.whl
Size 248.3 kB
Tags CPython 3.13 Windows x86-64
SHA-256 checksum
How to use checksums
4fed2e2a48eb0c117d319b3c295030eb65b4cbde57f56d21c17beb799a3836f2
BLAKE2b-256 checksum
How to use checksums
d316a5cf7a49dbe51ee65832c14a2e19c556f7539d92a03aef69d26af0b18ee3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 Jul 8, 2026.

Transparency log

Release files / beamme-0.3.0-cp313-cp313-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl

Download URL beamme-0.3.0-cp313-cp313-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
Size 449.1 kB
Tags CPython 3.13 Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64
SHA-256 checksum
How to use checksums
3a60a597b2caa51bb3039d39c9d9ec6fcf3568358cf834497c197ecbf1519388
BLAKE2b-256 checksum
How to use checksums
41e5a54f116997e2c4af628c439e67aecbd5dfe6079a069f3e6ab7470e151212
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 Jul 8, 2026.

Transparency log

Release files / beamme-0.3.0-cp313-cp313-macosx_11_0_arm64.whl

Download URL beamme-0.3.0-cp313-cp313-macosx_11_0_arm64.whl
Size 335.2 kB
Tags CPython 3.13 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
b131623a73da037fe7516299dc5e983d182f2502866b9c4dade68ab20a57197b
BLAKE2b-256 checksum
How to use checksums
6ed34fa4263ae1e4d60c2959b6edab4dde01c0066f1b9ceff933c9e6bb110b2c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 Jul 8, 2026.

Transparency log

Release files / beamme-0.3.0-cp312-cp312-win_amd64.whl

Download URL beamme-0.3.0-cp312-cp312-win_amd64.whl
Size 249.1 kB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
5e89385921f827cbe60b3ba597f4410c30468eff4aa15f319e1ccf2aa9e230fb
BLAKE2b-256 checksum
How to use checksums
7daa712f9237865981a467ad7ddc12bcc34f86fadb26f642d2a9c4564244c4e1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 Jul 8, 2026.

Transparency log

Release files / beamme-0.3.0-cp312-cp312-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl

Download URL beamme-0.3.0-cp312-cp312-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
Size 457.3 kB
Tags CPython 3.12 Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64
SHA-256 checksum
How to use checksums
7b28263bbc90af73eae0a6433df2fbde984163272f5b5d5ba7643dc54241bbca
BLAKE2b-256 checksum
How to use checksums
10d716855c914c8ed28b93bcca6593e891d14de1baacc6193d9a105c12375afd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 Jul 8, 2026.

Transparency log

Release files / beamme-0.3.0-cp312-cp312-macosx_11_0_arm64.whl

Download URL beamme-0.3.0-cp312-cp312-macosx_11_0_arm64.whl
Size 336.0 kB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
5af69a6d599c5c9dffb335c5ac760d337023030eabe9fe03505406d4aaa79c60
BLAKE2b-256 checksum
How to use checksums
2212b4d05a11493f17ce5c0a75df121e07b613304b4a4440a3a84576c1cead85
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 Jul 8, 2026.

Transparency log

Release files / beamme-0.3.0-cp311-cp311-win_amd64.whl

Download URL beamme-0.3.0-cp311-cp311-win_amd64.whl
Size 249.0 kB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
c0013a5e84dac8c9874781ccdf1843ccb8356d7c75b84b8938f2183b094f9db8
BLAKE2b-256 checksum
How to use checksums
fb923172df070bbfb502a886da230e67b5efc3522c797e518a774121e33b6c44
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 Jul 8, 2026.

Transparency log

Release files / beamme-0.3.0-cp311-cp311-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl

Download URL beamme-0.3.0-cp311-cp311-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
Size 443.6 kB
Tags CPython 3.11 Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64
SHA-256 checksum
How to use checksums
143197999e8465d4f0a7c1a136879f401ec7b91cf33e2020f0159c36b5dcd723
BLAKE2b-256 checksum
How to use checksums
ad6ffcb276780a4159773a44dc6ef74c9b50f86c28d6ace0921d05e785eae943
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 Jul 8, 2026.

Transparency log

Release files / beamme-0.3.0-cp311-cp311-macosx_11_0_arm64.whl

Download URL beamme-0.3.0-cp311-cp311-macosx_11_0_arm64.whl
Size 334.8 kB
Tags CPython 3.11 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
e4b7da3d621d4c73c840caec869cbb91bdf320ed91e50c3c000f882dce9c94e0
BLAKE2b-256 checksum
How to use checksums
f9df3b29172fb42685847af1cdc483af33981c7f72f1e2bf8498ef618053359a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 Jul 8, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.3.0 This release

13 release files

0.2.0

13 release files

0.1.4

13 release files

0.1.3

13 release files

0.1.2

12 release files

0.1.0

1 release file

0.0.1

2 release files

0.0.0

2 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