pySpextool
Python code to reduce data obtained with the SpeX spectrograph.
Recommended Installation Instructions
-
Setup your computer and install miniforge, if you haven't already.
Follow Steps 0-2 of the Astropy Workshop Setup instructions to install WSL (for Windows) and install conda with miniforge.
-
Make a
pyspextool_3.13conda environment with Python 3.13.conda create -n pyspextool_3.13 python=3.13 -
Activate the new environment
conda activate pyspextool_3.13 -
Install the
pyspextoolpackage from PyPI usingpip. This also installs the other Python packages thatpyspextooldepends upon.pip install pyspextool -
Install other Python packages
If you want to use Jupyter notebooks or other Python tools with
pyspextool, you need to install them in the new environment. For example:pip install jupyterlab
Instructions for using the example notebooks
-
The Jupyter notebook tutorials are under
notebooks/for preupgraded and upgraded SpeX Prism, SXD, and LXD data. -
Follow the instructions above to download the test data which will be saved under
tests/test_data/. To get the data used by the Jupyter notebooks, clone the test_data repository.git clone git@github.com:pyspextool/test_data.gitThe raw and processed example data products are available under
tests/test_data/raw/andtests/test_data/processed/respectively. The data products include thecal(calibration data),proc(processed data), andqa(quality assurance plots). -
While users should be able to run the Jupyter notebook tutorials without changing the output paths, users are encouraged to move the data folder and rename the output paths. The default saving directory is
/test_pyspextool/test_data/processed/.
Developer Instructions
If you plan to contribute code to pyspextool, you should clone a fork of this repo.
You will also need pytest and the test data in order to run the tests.
-
Make your own fork of this repository.
-
Clone the fork to your computer.
-
Make and activate a dedicated virtual environment, ideally with Python 3.13.
-
Install and editable version of
pyspextooland install the extra packages needed for testing and developing. In thepyspextool/direcotry:pip install -e ".[test]" -
Setup and download the
test_data/submodulegit submodule update --init --recursive
Metadata
Release files for pyspextool 2.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 |
|---|---|---|---|---|
| pyspextool-2.1.tar.gz | 69.7 MB | With provenance | Details for pyspextool-2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyspextool-2.1-py3-none-any.whl | Python 3 | none | any | Details for pyspextool-2.1-py3-none-any.whl |
Total release size: 96.3 MB
Release files / pyspextool-2.1.tar.gz
| Download URL | pyspextool-2.1.tar.gz |
|---|---|
| Size | 69.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9789ff2c774bd38f095ed15d6e2181317874d8a46f724056527fd5cf3dd05fa9
|
|
BLAKE2b-256 checksum How to use checksums |
41502fec3f2cab66397e8c4bc4ea3c90c2152b658d03fbe7ec103f74bfa5df65
|
| 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 Oct 22, 2026.
Transparency logRelease files / pyspextool-2.1-py3-none-any.whl
| Download URL | pyspextool-2.1-py3-none-any.whl |
|---|---|
| Size | 26.6 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d5fbd7695c4c83c94b52b3a8b518be7223f56036464072709a0b3c50db873bc3
|
|
BLAKE2b-256 checksum How to use checksums |
cb1cf1ed367e31d1ec6cf9eeb8276b1b8b39269006df67143a9aa354943325e7
|
| 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 Oct 22, 2026.
Transparency logSecurity for pyspextool 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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pyspextool-2.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 Oct 22, 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.