Skip to main content

IERS Earth Rotation and Leap Second tables for the astropy core package

https://zenodo.org/badge/644894042.svg

Note: This package is not currently meant to be used directly by users, and only meant to be used from the core astropy package.

https://docs.astropy.org/en/latest/utils/iers.html

License

This project is Copyright (c) Astropy Developers and licensed under the terms of the BSD 3-Clause license. This package is based upon the OpenAstronomy packaging guide which is licensed under the BSD 3-clause licence. See the licenses folder for more information.

Contributing

We love contributions! astropy-iers-data is open source, built on open source, and we’d love to have you hang out in our community.

Imposter syndrome disclaimer: We want your help. No, really.

There may be a little voice inside your head that is telling you that you’re not ready to be an open source contributor; that your skills aren’t nearly good enough to contribute. What could you possibly offer a project like this one?

We assure you - the little voice in your head is wrong. If you can write code at all, you can contribute code to open source. Contributing to open source projects is a fantastic way to advance one’s coding skills. Writing perfect code isn’t the measure of a good developer (that would disqualify all of us!); it’s trying to create something, making mistakes, and learning from those mistakes. That’s how we all improve, and we are happy to help others learn.

Being an open source contributor doesn’t just mean writing code, either. You can help out by writing documentation, tests, or even giving feedback about the project (and yes - that includes giving feedback about the contribution process). Some of these contributions may be the most valuable to the project as a whole, because you’re coming to the project with fresh eyes, so you can see the errors and assumptions that seasoned contributors have glossed over.

Note: This disclaimer was originally written by Adrienne Lowe for a PyCon talk, and was adapted by astropy-iers-data based on its use in the README file for the MetPy project.

Metadata

Release files for astropy-iers-data 0.2026.11.2.0.34.55

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

Source distribution (sdist)

Source distribution for astropy-iers-data 0.2026.11.2.0.34.55
File Size Uploaded Provenance Actions
astropy_iers_data-0.2026.11.2.0.34.55.tar.gz 2.0 MB With provenance Details for astropy_iers_data-0.2026.11.2.0.34.55.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for astropy-iers-data 0.2026.11.2.0.34.55
File Interpreter ABI Platform Actions
astropy_iers_data-0.2026.11.2.0.34.55-py3-none-any.whl Python 3 none any Details for astropy_iers_data-0.2026.11.2.0.34.55-py3-none-any.whl

Total release size: 4.0 MB

Release files / astropy_iers_data-0.2026.11.2.0.34.55.tar.gz

Download URL astropy_iers_data-0.2026.11.2.0.34.55.tar.gz
Size 2.0 MB
Tags Source
SHA-256 checksum
How to use checksums
20827b7431096723bbfac3f42eddc45df1bf35ea9bc6f3978837f65d8443cf6b
BLAKE2b-256 checksum
How to use checksums
c3e60f9740a39dbae6614444f4f29f71aa5fb977a75368e7bc74f998037fc496
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 2, 2026.

Transparency log

Release files / astropy_iers_data-0.2026.11.2.0.34.55-py3-none-any.whl

Download URL astropy_iers_data-0.2026.11.2.0.34.55-py3-none-any.whl
Size 2.0 MB
Tags Python 3
SHA-256 checksum
How to use checksums
785cd5bc193d9206316bd7c786fe0647e212ebf017cd861beabedd91cbe585bf
BLAKE2b-256 checksum
How to use checksums
97c179214b3d293c2a46869ba12ad4d20f3156653e15dabaddb02a6d644b0055
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 2, 2026.

Transparency log

Security for astropy-iers-data 0.2026.11.2.0.34.55

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.

Select from 2 files

Attestation for astropy_iers_data-0.2026.11.2.0.34.55.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 2, 2026.

Transparency log

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
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