What is PyneCore?
PyneCore runs Pine Script-style trading code in Python. You write ordinary Python, and PyneCore rewrites it at import time with AST transformations, so it executes bar by bar with Pine Script's semantics: series with history, variables that keep their value between bars, and na for missing data. The rest of the Python ecosystem stays available to the same code.
PyneCore is tested against TradingView on 1,000 published TradingView scripts (Pine Script v4 to v6, converted to Pyne code with PyneComp). All 1,353 comparable outputs match, 99.771% of 132 million plotted values are bit-identical, and 353,577 strategy trades match TradingView's timing (snapshot 2026-10-24). Every script and every result is public at Pyne in the Wild, and the Compatibility page lists the status of each Pine Script feature.
Key features
- Pine Script's bar-by-bar execution model in plain Python
- Scripts marked with
@pyneare transformed when they are imported - No mandatory dependencies outside the Python standard library
Seriesvariables with bar history andPersistentvariables that keep state between bars- Function isolation: every call of a function keeps its own persistent state
nahandling that follows Pine Script- Every
ta.*function of Pine Script v6 - Pine Script-compatible strategy backtesting
Quick example
"""
@pyne
"""
from pynecore.lib import script, close, ta, plot, color, input
@script.indicator(title="Bollinger Bands")
def main(
length=input.int(20, "Length", minval=1),
mult=input.float(2.0, "Multiplier", minval=0.1, step=0.1),
src=input.source(close, "Source")
):
# Calculate Bollinger Bands
basis = ta.sma(src, length)
dev = mult * ta.stdev(src, length)
upper = basis + dev
lower = basis - dev
# Output to chart
plot(basis, "Basis", color=color.orange)
plot(upper, "Upper", color=color.blue)
plot(lower, "Lower", color=color.blue)
Core concepts
The @pyne magic comment
A script is marked with a magic comment in its docstring:
"""
@pyne
"""
PyneCore's import hook recognizes the marker and applies its AST transformations to the module when it is imported.
Series variables
A series variable keeps its history across bars, as in Pine Script:
from pynecore import Series
price: Series[float] = close
previous_price = price[1] # Access previous bar's price
Persistent variables
A Persistent annotation keeps a variable's value from one bar to the next:
from pynecore import Persistent
counter: Persistent[int] = 0
counter += 1 # Increments with each bar
Function isolation
Every call of a function keeps its own persistent state:
def my_indicator(src, length):
# Each call gets its own instance of total
total: Persistent[float] = 0
total += src
return total / length
Installation
# Basic installation
pip install pynesys-pynecore
# With CLI tools (recommended)
pip install pynesys-pynecore[cli]
# With all features including data providers
pip install pynesys-pynecore[all]
Windows: PyneCore needs timezone data that Windows does not ship. The
[cli]and[all]extras install thetzdatapackage. With the basic installation, runpip install tzdataif you get timezone errors.
Getting started
Create a simple script
- Create a file with the
@pyneannotation:
"""
@pyne
"""
from pynecore.lib import script, close, plot
@script.indicator("My First Indicator")
def main():
# Calculate a simple moving average
sma_value = (close + close[1] + close[2]) / 3
# Plot the result
plot(sma_value, "Simple Moving Average")
- Run it with the PyneCore CLI:
# First, download some price data
pyne data download ccxt --symbol "BYBIT:BTC/USDT:USDT"
# Then run your script on the data
pyne run my_script.py ccxt_BYBIT_BTC_USDT_USDT_1D.ohlcv
Running Pine Script files
PyneCore runs Pyne code. Existing Pine Script (v4, v5 and v6, and v1 to v3 on a best-effort basis) is converted to Pyne code by PyneComp, a separate PyneSys service that needs an API key. With the key, the pyne CLI compiles .pine files for you:
# Run a Pine Script file directly (requires PyneSys API key)
pyne run my_indicator.pine ccxt_BYBIT_BTC_USDT_USDT_1D.ohlcv --api-key YOUR_API_KEY
# Or compile Pine Script to Python first
pyne compile my_indicator.pine --api-key YOUR_API_KEY
# Then run the compiled Python file
pyne run my_indicator.py ccxt_BYBIT_BTC_USDT_USDT_1D.ohlcv
You can get an API key at pynesys.io.
Why PyneCore?
- Your scripts run outside TradingView, without its platform restrictions or code size limits.
- Python's data science, machine learning and analysis libraries work in the same code as the trading logic.
- The match with TradingView is measured on real published scripts: 99.771% of 132 million plotted values are identical to the bit.
- The runtime and its library are open source under the Apache 2.0 license.
Converting Pine Script
If you have Pine Script code you want to run in Python, PyneComp converts it to Pyne code. You can use it on the web, from the pyne CLI with an API key, or through the PyneSys Discord bot: /pyne-help shows how the bot works, /pyne-convert converts a script, and every Discord user gets 3 free conversions.
The subscription plans on pynesys.io raise the daily conversion limit and the maximum script size. They also fund the development of PyneCore, which stays free and open source.
Documentation and support
- Documentation: pynecore.org
- Validation report: Pyne in the Wild, where every corpus script is compared with TradingView
Community
- Discussions: GitHub Discussions
- Discord: discord.pynesys.io
- X: x.com/pynesys
- Website: pynecore.org
License
PyneCore is licensed under the Apache License 2.0.
Disclaimer
Pine Script™ is a trademark of TradingView, Inc. PyneCore is not affiliated with, endorsed by, or sponsored by TradingView. This project is an independent implementation of the Pine Script language concept in Python; its results are measured against TradingView on Pyne in the Wild.
Risk warning
Trading involves significant risk of loss and is not suitable for all investors. The use of PyneCore does not guarantee any specific results. Past performance is not indicative of future results.
- PyneCore is provided "as is" without any warranty of any kind
- PyneCore is not a trading advisor and does not provide trading advice
- Scripts created with PyneCore should be thoroughly tested before using with real funds
- Users are responsible for their own trading decisions
- You should consult with a licensed financial advisor before making any financial decisions
By using PyneCore, you acknowledge that you are using the software at your own risk. The creators and contributors of PyneCore shall not be held liable for any financial loss or damage resulting from the use of this software.
Commercial support
PyneCore is part of the PyneSys ecosystem. For commercial support, custom development or enterprise solutions, contact us at pynesys.com/contact.
1 maintainer
Metadata
1 maintainer
Release files for pynesys-pynecore 6.13.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pynesys_pynecore-6.13.1.tar.gz | 3.3 MB | With provenance | Details for pynesys_pynecore-6.13.1.tar.gz |
Built distributions (wheels)
Total release size: 196.3 MB
Release files / pynesys_pynecore-6.13.1.tar.gz
| Download URL | pynesys_pynecore-6.13.1.tar.gz |
|---|---|
| Size | 3.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cd8e8b30ea73a94883c88daffcfff48e46b3a50c2093477f645b6131213fcec4
|
|
BLAKE2b-256 checksum How to use checksums |
da626f6a4831c628ef8138a10bfb817627d06fd2d9438ae27c64774a278bf439
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-py3-none-any.whl
| Download URL | pynesys_pynecore-6.13.1-py3-none-any.whl |
|---|---|
| Size | 2.6 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6e1842c4148090d50c9b18a4fa4ec74785dfee4caa2fd4c9e9a12831fea2bdd5
|
|
BLAKE2b-256 checksum How to use checksums |
4541c9f960e5a25cbc65a7722ce82e6fa1af47369f2cdde90a3d3ae79fe8113b
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp314-cp314-win_arm64.whl
| Download URL | pynesys_pynecore-6.13.1-cp314-cp314-win_arm64.whl |
|---|---|
| Size | 5.5 MB |
| Tags | CPython 3.14 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
4d9de6103669a010197e9f35c702b0a51bbb453088bb7e6d631092b295163ff1
|
|
BLAKE2b-256 checksum How to use checksums |
36d8af972ed9b9e14792b090282df72d393de8f20ce329e0aeefc367b3a0adf9
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp314-cp314-win_amd64.whl
| Download URL | pynesys_pynecore-6.13.1-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 5.7 MB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
511f012d9565030ba123d1c6718505797d33e15966afe4ecc41d848a4fc6bbef
|
|
BLAKE2b-256 checksum How to use checksums |
9ad060f428898241009227857b492789399328e8be9c2bddc00293151c3187a2
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp314-cp314-musllinux_1_2_x86_64.whl
| Download URL | pynesys_pynecore-6.13.1-cp314-cp314-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 6.6 MB |
| Tags | CPython 3.14 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
40789b7997bddd940870cd5781585cc0737cad7ca76a67d285ccf9ccd4b5d126
|
|
BLAKE2b-256 checksum How to use checksums |
dcc9537adf75673db84711e4c0b305f7ca17164e15924620974e6902b697710b
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp314-cp314-musllinux_1_2_aarch64.whl
| Download URL | pynesys_pynecore-6.13.1-cp314-cp314-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 6.3 MB |
| Tags | CPython 3.14 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
b97dbc103c586c144e49629ee90817801c93c5ab19c3a4958278cf88a7f8c72c
|
|
BLAKE2b-256 checksum How to use checksums |
6f00f21c38d755354884f441af3d97782f51785c437f87078db0adb81a90b0e4
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp314-cp314-manylinux_2_28_x86_64.whl
| Download URL | pynesys_pynecore-6.13.1-cp314-cp314-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 6.6 MB |
| Tags | CPython 3.14 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
1d54f5e8e64c02ffaaa44f0caa98b2851cec69ba3c211e43a8692a7f75d09a97
|
|
BLAKE2b-256 checksum How to use checksums |
d331e635c396330902b9b2be4dddbcaa2aff0275fca3b733b82033e3a552658c
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp314-cp314-manylinux_2_28_aarch64.whl
| Download URL | pynesys_pynecore-6.13.1-cp314-cp314-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 6.3 MB |
| Tags | CPython 3.14 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
b818fb61b1f790c23d9c8e934a743ae32b63704def63763056e3d646ab841981
|
|
BLAKE2b-256 checksum How to use checksums |
83b0e4651af7317a021c5107f9ec3d3dddcbf158c311476c7d2aecda6d1e6249
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp314-cp314-macosx_11_0_arm64.whl
| Download URL | pynesys_pynecore-6.13.1-cp314-cp314-macosx_11_0_arm64.whl |
|---|---|
| Size | 5.4 MB |
| Tags | CPython 3.14 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
dd8b8be5f1e7b9f48d52aa4f45b6f8680b2ade3a49b95170edf049cb98c4ac04
|
|
BLAKE2b-256 checksum How to use checksums |
7e2174cd854ef2ff7caa0f416914e90f84711eae8d7d1ec21f52f7978b89cc7f
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp314-cp314-macosx_10_15_x86_64.whl
| Download URL | pynesys_pynecore-6.13.1-cp314-cp314-macosx_10_15_x86_64.whl |
|---|---|
| Size | 5.6 MB |
| Tags | CPython 3.14 macOS 10.15+ x86-64 |
|
SHA-256 checksum How to use checksums |
15d4d614ca4672b1bb3da908b2f8dce967313e183878a4582628031f096c2436
|
|
BLAKE2b-256 checksum How to use checksums |
ea451f7796278c0fb0d5c60aef52727282ed2bb1c7632e701a9cf0a4f579c8e3
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp313-cp313-win_arm64.whl
| Download URL | pynesys_pynecore-6.13.1-cp313-cp313-win_arm64.whl |
|---|---|
| Size | 5.3 MB |
| Tags | CPython 3.13 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
682df06b29a806d21f60a0e6e93ab750d17890da2ff64265f3a90c9dec9f2b23
|
|
BLAKE2b-256 checksum How to use checksums |
76a0251432d59dbb3892666a6c5ce2c99cf39690546cd67f8d6d493e937c500c
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp313-cp313-win_amd64.whl
| Download URL | pynesys_pynecore-6.13.1-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 5.6 MB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
681a3e1b0163eff4f05041f5913b42e50c7477da3c9c774c52b2e45d6e36ccb6
|
|
BLAKE2b-256 checksum How to use checksums |
ede861ca3dff7ced781c9ad03f392bc1b98f446a4c9b7bee0ffe153c5c6bc093
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp313-cp313-musllinux_1_2_x86_64.whl
| Download URL | pynesys_pynecore-6.13.1-cp313-cp313-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 6.6 MB |
| Tags | CPython 3.13 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
59c6b5d1e8152902a39ad0576e737c48958ccfaf23dea24c85b9ee9cc1da6201
|
|
BLAKE2b-256 checksum How to use checksums |
2d3d8f8529f98047df7b6881bc0dd9567aab4a9b9b31d723fd2b495c1f62e9aa
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp313-cp313-musllinux_1_2_aarch64.whl
| Download URL | pynesys_pynecore-6.13.1-cp313-cp313-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 6.3 MB |
| Tags | CPython 3.13 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
d47c2e9db042583d43237892c929b30950169ae394e1c38d3820e561ca062845
|
|
BLAKE2b-256 checksum How to use checksums |
4f281b3167b80150a1ca3bee3124f8f547afb51efe23c1fad6fda13783e631b0
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp313-cp313-manylinux_2_28_x86_64.whl
| Download URL | pynesys_pynecore-6.13.1-cp313-cp313-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 6.6 MB |
| Tags | CPython 3.13 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
5c724c057bb2b841e1d5481dabb3c073b9e5d0e603264b5cb8539c2d920f885d
|
|
BLAKE2b-256 checksum How to use checksums |
8578d0d652331e5d4b7bbd15955463373e2e7bd054bb43319757e834749a6f7a
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp313-cp313-manylinux_2_28_aarch64.whl
| Download URL | pynesys_pynecore-6.13.1-cp313-cp313-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 6.3 MB |
| Tags | CPython 3.13 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
3081df12c65bf2c68f89e37002be26a26ef09c44b033979e74e94c4cdd16ef34
|
|
BLAKE2b-256 checksum How to use checksums |
4d824c657d66cd028ba01f5e3f269b995919240d4f612bb3105ac51a020f9ace
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | pynesys_pynecore-6.13.1-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 5.4 MB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
38dbe4c678fde93d3cde7c05bd4aa51ef09f1a05cbf9b21d853cf3abc13b11b4
|
|
BLAKE2b-256 checksum How to use checksums |
ef2c96b5214d50250df37f9023047b5fbf9dae299fc791df90e1ee548da58238
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp313-cp313-macosx_10_13_x86_64.whl
| Download URL | pynesys_pynecore-6.13.1-cp313-cp313-macosx_10_13_x86_64.whl |
|---|---|
| Size | 5.6 MB |
| Tags | CPython 3.13 macOS 10.13+ x86-64 |
|
SHA-256 checksum How to use checksums |
4c1525c345e24d0e41db3ef8217c357a19b95470f189b6b7a165c2df2b4da61a
|
|
BLAKE2b-256 checksum How to use checksums |
43d51dcc954c7ee4e8e283dcbfde068a6ee5e854a24b7276d01d619b0f15d7ea
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp312-cp312-win_arm64.whl
| Download URL | pynesys_pynecore-6.13.1-cp312-cp312-win_arm64.whl |
|---|---|
| Size | 5.3 MB |
| Tags | CPython 3.12 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
6333957076278f6d28edb5197b3a590526bf9ef6f49a448f0e98ecc850fbd766
|
|
BLAKE2b-256 checksum How to use checksums |
6866a7ac1264222fc822381b8001e611a4f1374882c92c2bc89bc45b8a1762b4
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp312-cp312-win_amd64.whl
| Download URL | pynesys_pynecore-6.13.1-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 5.6 MB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
104a1989c667a7df601d7cd6c195f09b5e8ec5c18ee0dc183b96c9f8fd6d0dde
|
|
BLAKE2b-256 checksum How to use checksums |
ca49399b1621da226c788abebad716ca1e5f25465714927fd621bdc4e5d0f471
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp312-cp312-musllinux_1_2_x86_64.whl
| Download URL | pynesys_pynecore-6.13.1-cp312-cp312-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 6.6 MB |
| Tags | CPython 3.12 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
306babb1290bcf24ea6beadf62c65e0066d33902988901809e9c42218f61a11b
|
|
BLAKE2b-256 checksum How to use checksums |
25507d03993fd69b8db70f28028821333a5ede8557679f6899d8a27b713cc903
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp312-cp312-musllinux_1_2_aarch64.whl
| Download URL | pynesys_pynecore-6.13.1-cp312-cp312-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 6.3 MB |
| Tags | CPython 3.12 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
9bf550e38cffd9b203ee8ef02d91a0cebc3382828c5dd98a5ce1b7d3d4f40e5f
|
|
BLAKE2b-256 checksum How to use checksums |
c0eb6e09774c167bc4d3508637e57917ed50f6ccba639c810d2182fcfb38f14a
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp312-cp312-manylinux_2_28_x86_64.whl
| Download URL | pynesys_pynecore-6.13.1-cp312-cp312-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 6.5 MB |
| Tags | CPython 3.12 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
f3389d46365c280e3b99ed99c7ca35cd10700d6abc2985e5fb4ac0c402fd1dca
|
|
BLAKE2b-256 checksum How to use checksums |
0fe48f2c1d4cb6a7141ece915ef6efa98ff6d34d82a718bf7e84e814b227bec0
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp312-cp312-manylinux_2_28_aarch64.whl
| Download URL | pynesys_pynecore-6.13.1-cp312-cp312-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 6.2 MB |
| Tags | CPython 3.12 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
a7ac321c1c5db2dd12f97f1ed04d3b1f6edefd85d3a4c67d1054ae3ddad4d982
|
|
BLAKE2b-256 checksum How to use checksums |
386e04da32754439f60e78b2ffe9edba94407d665a933a6b8c09dde78484ec81
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | pynesys_pynecore-6.13.1-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 5.4 MB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
1d1663d30755e0c20e89b7bd2d70775141216fba627c32c2dfcf6ed1fe7792c9
|
|
BLAKE2b-256 checksum How to use checksums |
72e4825a166300722dffe310eb6bae78d1d74f4d61d00791dcedd09e0dd0ca7f
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp312-cp312-macosx_10_13_x86_64.whl
| Download URL | pynesys_pynecore-6.13.1-cp312-cp312-macosx_10_13_x86_64.whl |
|---|---|
| Size | 5.6 MB |
| Tags | CPython 3.12 macOS 10.13+ x86-64 |
|
SHA-256 checksum How to use checksums |
fe8a80a6b84be12463594646d198c7cb967c0cfa5adf271f61e3d32458569ba5
|
|
BLAKE2b-256 checksum How to use checksums |
65bcade723e34639973282dd66582607c6cbf6e34afa0506ddfa5a77ab44c241
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp311-cp311-win_arm64.whl
| Download URL | pynesys_pynecore-6.13.1-cp311-cp311-win_arm64.whl |
|---|---|
| Size | 5.3 MB |
| Tags | CPython 3.11 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
f71d64c1dd7e8f058cdb8722d6d705ea1386bbad3ea1f2150b1d03a88f267488
|
|
BLAKE2b-256 checksum How to use checksums |
c3b135607f0bd6d9342da3adf9dd7dfeb0cf6c44116afee618a4aaa075be5a30
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp311-cp311-win_amd64.whl
| Download URL | pynesys_pynecore-6.13.1-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 5.6 MB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
0c0a074e49e8d8753490aa1481435a054becfe4ec7c5124998090c2fcc2ab95d
|
|
BLAKE2b-256 checksum How to use checksums |
65823b88a64fb7fd03db14fa2da1020e7285c8928d5d83f7562f0f025729ef8c
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp311-cp311-musllinux_1_2_x86_64.whl
| Download URL | pynesys_pynecore-6.13.1-cp311-cp311-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 6.5 MB |
| Tags | CPython 3.11 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
a8711f952c3d48a2ff61ca0ac678714448c284eef4a2c08df87e286dde355efd
|
|
BLAKE2b-256 checksum How to use checksums |
497e6cec47292c7c32f99280e6c43876cd969b7a7bc5c46392117c8bcaba9b1f
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp311-cp311-musllinux_1_2_aarch64.whl
| Download URL | pynesys_pynecore-6.13.1-cp311-cp311-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 6.3 MB |
| Tags | CPython 3.11 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
6da8698ac34e8b2ba82d13b756181686d819c9cf106930905bf508b719f09f5d
|
|
BLAKE2b-256 checksum How to use checksums |
db1f97969c2e6129bf655be13e57430aeb82f4f0fcdd7c40ba661dd696f6dc91
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp311-cp311-manylinux_2_28_x86_64.whl
| Download URL | pynesys_pynecore-6.13.1-cp311-cp311-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 6.5 MB |
| Tags | CPython 3.11 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
61a721d3b8c7b2b45a1aa5c2d8514bca3705610fe36131f8e3c501f845609d6e
|
|
BLAKE2b-256 checksum How to use checksums |
1d6cc0bb9bbf847d01429f2ae603e9b7e2764f80f030b44bff11fb26235d39cc
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp311-cp311-manylinux_2_28_aarch64.whl
| Download URL | pynesys_pynecore-6.13.1-cp311-cp311-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 6.2 MB |
| Tags | CPython 3.11 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
1dd17f66f74709a8399e6cd85fd735043da6e8f5304792e7fc5ab2104499844b
|
|
BLAKE2b-256 checksum How to use checksums |
dab601490968fdd7a61ad2ce5a391bc7df16da487b522ccb6e7287eb8a920e6d
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | pynesys_pynecore-6.13.1-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 5.4 MB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
3d3ea4ea75e210b03f96f6795fbfa0971b68f754e87c796c58dd6d0af0c6b6f8
|
|
BLAKE2b-256 checksum How to use checksums |
d2e55159ae87a071179b6eeb97433db3c8e0d56c0205428f065e331d432229db
|
| 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 8, 2026.
Transparency logRelease files / pynesys_pynecore-6.13.1-cp311-cp311-macosx_10_12_x86_64.whl
| Download URL | pynesys_pynecore-6.13.1-cp311-cp311-macosx_10_12_x86_64.whl |
|---|---|
| Size | 5.6 MB |
| Tags | CPython 3.11 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
43dc5cdbcccfc4a706daa95ad7e0c7457e0fc83776f9995b77b3a7b4858d52a2
|
|
BLAKE2b-256 checksum How to use checksums |
0742d8a3bfd565303616368231f2c03bd03747ab152769dda91a7f00fbd4b4e0
|
| 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 8, 2026.
Transparency logSecurity for pynesys-pynecore 6.13.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.
Full provenance
All 34 files in this release have been uploaded with provenance metadata.
Attestation for pynesys_pynecore-6.13.1.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 8, 2026.
Transparency logA 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.
