PyXLL-Jupyter
Integration for Spyder IDE and Microsoft Excel.
Requirements
- PyXLL >= 5.1.0
- spyder-kernels >= 3.0.0
Installation
To install this package use:
pip install pyxll-spyder
Once installed a "Start Spyder Kernel" button will be added to the PyXLL ribbon tab in Excel, so long as you have PyXLL 5 or above already installed.
Click the button to start the Spyder kernel in Excel. A message box will be shown with the file name of the Spyder kernel, which is copied to the clipboard ready to paste in the next step.
The Spyder kernel runs inside the Excel process using PyXLL and can be connected to from Spyder using the menu item "Consoles -> Connect to Existing Kernel...". Paste the kernel file name copied in the previous step here.
Once connected, the Spyder can execute code in Excel. The usual PyXLL functions and decorators can be used which can be used to add new Excel functions and macros, as well as use the Excel Object Model API to interact with Excel.
1 maintainer
Metadata
1 maintainer
Release files for pyxll-spyder 0.0.2
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 | |
|---|---|---|---|---|
| pyxll_spyder-0.0.2.tar.gz | 14.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyxll_spyder-0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 28.8 kB
Release files / pyxll_spyder-0.0.2.tar.gz
| Download URL | pyxll_spyder-0.0.2.tar.gz |
|---|---|
| Size | 14.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
13a089ce756e752b74fc797aa0211ecf611496d7c79d4243f8c8a30835e599a7
|
|
BLAKE2b-256 checksum How to use checksums |
38368214e0c9d1de3a54b16aed30c1f36dfd7ee232e1d18e23cacbd7afe44d62
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Dec 10, 2025.
Transparency logRelease files / pyxll_spyder-0.0.2-py3-none-any.whl
| Download URL | pyxll_spyder-0.0.2-py3-none-any.whl |
|---|---|
| Size | 14.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5c26f466eb2e2d79b52e95f0f67799216c607d4b09331d30526085239de9c0f3
|
|
BLAKE2b-256 checksum How to use checksums |
eb654a75b6147606fc42ab93effe0e4b3d6627ddc8d552d4f11de3d196029a75
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Dec 10, 2025.
Transparency logSecurity for pyxll-spyder 0.0.2
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 2 files in this release have been uploaded with provenance metadata.
Attestation for pyxll_spyder-0.0.2.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 Dec 10, 2025.
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.
