Skip to main content

Hypertube allows you to reference and use modules or packages written in (Java/Kotlin/Groovy/Clojure, C#/VB.NET, Ruby, Perl, Python, JavaScript/TypeScript) like they were created in your technology. It works on Linux/Windows and MacOS for applications created in JVM, CLR/Netcore, Perl, Python, Ruby, NodeJS, C++ or GoLang and gives you unparalleled freedom and flexibility with native performance in building your mixed-technologies products. Let it be accessing best AI or cryptography libraries, devices SDKs, legacy client modules, internal custom packages or anything from public repositories available on NPM, Nuget, PyPI, Maven/Gradle, RubyGems or GitHub. Get free from programming languages barriers today! For more information check out our guides at https://www.hypertube.dev/guides/v2/

Loading another runtime in the in-memory channel

These settings apply only when this SDK loads a different technology in-process through the in-memory channel. The runtime that hosts the SDK itself is never configured this way. For example, a PHP application does not set HYPERTUBE_PHP_RUNTIME_PATH; it sets HYPERTUBE_PYTHON_RUNTIME_PATH or HYPERTUBE_RUBY_RUNTIME_PATH only when it loads Python or Ruby modules in memory.

  • .NET Framework (CLR), Windows only: the latest .NET Framework 4.x installed on the system (4.8 or newer).
  • .NET (netcore): the latest .NET runtime installed on the system. Set runtimePath for the channel to net8.0, net9.0 or net10.0 to stay on one major version.
  • Java (JVM): the JDK or JRE that JAVA_HOME points to. runtimePath for the channel or HYPERTUBE_JVM_RUNTIME_PATH take precedence.
  • Node.js: built in. Hypertube ships its own Node.js library, nothing to install.
  • Python, Ruby and PHP: Hypertube loads the runtime's shared library, not the interpreter executable, in this order:
    1. runtimePath set for the channel in the Hypertube configuration.
    2. An environment variable with the full path to the library:
      • HYPERTUBE_PYTHON_RUNTIME_PATH, for example C:\Python313\python313.dll or /usr/lib/x86_64-linux-gnu/libpython3.13.so
      • HYPERTUBE_RUBY_RUNTIME_PATH, for example C:\Ruby34-x64\bin\x64-ucrt-ruby340.dll or /usr/local/lib/libruby.so.3.4
      • HYPERTUBE_PHP_RUNTIME_PATH, for example C:\php85\php8ts.dll or /opt/php/8.5/lib/libphp.so
    3. The library file name in the system library search path: PATH on Windows, LD_LIBRARY_PATH, the ldconfig cache and default directories on Linux, dyld search paths on macOS.
      • Python 3.14 down to 3.6: python3XX.dll, libpython3.XX.so, libpython3.XX.dylib. Set HYPERTUBE_PYTHON_VERSION to load one version: 3.13 on Linux and macOS, 313 on Windows.
      • Ruby 4.0 down to 3.0: x64-ucrt-ruby340.dll style names (x64-msvcrt- too, aarch64-ucrt- on Windows ARM64), libruby.so or libruby.dylib and their versioned names. With RubyInstaller keep bin\ruby_builtin_dlls next to the Ruby DLL.
      • PHP: Thread Safe PHP 8.5 built with the embed SAPI (PHP 8.4 on Windows ARM64): php8ts.dll, libphp.so or libphp.dylib. The NTS php8.dll is rejected.

Metadata

Release files for hypertube-python-sdk 3.2.1

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

Built distribution (wheel)

Table of built distributions (wheels) for hypertube-python-sdk 3.2.1
File Interpreter ABI Platform Actions
hypertube_python_sdk-3.2.1-py3-none-any.whl Python 3 none any Details for hypertube_python_sdk-3.2.1-py3-none-any.whl

Release files / hypertube_python_sdk-3.2.1-py3-none-any.whl

Download URL hypertube_python_sdk-3.2.1-py3-none-any.whl
Size 189.8 MB
Tags Python 3
SHA-256 checksum
How to use checksums
3a2c13faff005f6ea337dd9f500698a9f65472d67865931c487728b3d5c92ce1
BLAKE2b-256 checksum
How to use checksums
8532f3812b065fe4a9f1fcb211f029a47031fb391c2d8d3d7d4c574b80a5bdc0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.10

Security for hypertube-python-sdk 3.2.1

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

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.2.1 This release

1 release file No 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