satnogs-predict 0.6__tar.gz → 1.1__tar.gz

satnogs_predict-1.1/CHANGELOG.md

@@ -0,0 +1,19 @@
+# Changelog
+
+## 1.0
+
+### Breaking Changes
+
+- `Satellite.identifier` no longer defaults to a generated UUID. It now defaults to an empty string and is treated as caller metadata.
+- `Observer.identifier` no longer defaults to a generated UUID. It now defaults to an empty string and is treated as caller metadata.
+- Skyfield satellite and observer caches **no longer use identifiers as cache keys**. Satellite cache identity is based on orbital data, and observer cache identity is based on latitude, longitude, and elevation.
+- `OMM.fields` is now stored as a read-only mapping. Use `OMM.to_dict()` when a mutable dictionary is needed.
+
+### Added
+
+- Added `cache_key` properties for `TLE`, `OMM`, `Orbit`, `Satellite`, and `Observer`.
+- Added a shared internal `cache_digest()` helper.
+
+### Improved
+
+- It is no longer the caller's responsibility to manage cache by using identifiers.

{satnogs_predict-0.6 → satnogs_predict-1.1}/CONTRIBUTING.md

@@ -11,6 +11,7 @@
   * [Respond to review comments](#respond-to-review-comments)
   * [Don’t get discouraged - or impatient](#dont-get-discouraged-or-impatient)
   * [Sign your work - the Developer’s Certificate of Origin](#sign-your-work-the-developers-certificate-of-origin)
+  * [Generative AI / LLM Policy](#generative-ai--llm-policy)
   * [References](#references)
 
 ## Introduction ##
@@ -22,7 +23,7 @@ It is based on Linux kernel patch submission guidelines.
 
 All Libre Space Foundation projects code is maintained under Git.
 Obtain a copy of the source code using `git clone`.
-Development usually takes place under `master` or `dev` branch.
+Development usually takes place under `main`, `master` or `dev` branch.
 
 ## Separate the changes ##
 
@@ -39,16 +40,16 @@ The point to remember is that each commit should make an easily understood chang
 Each commit should be justifiable on its own merits.
 
 When creating a merge request from a series of commits, take special care to ensure that the software builds and runs properly after each commit in the series.
-Developers using `git bisect` to track down a problem can end up splitting your merge request at any point; they will not thank you if you introduce bugs in the middle.
+Developers using `git bisect` to track down a problem can end up splitting your merge request at any point; not thanking you if you introduce bugs in the middle.
 
 If you cannot condense your merge request into a smaller set of commits, then only submit say 15 or so at a time and wait for review and integration.
 
-Never commit binary files.
+Never commit binary files or statically generated code.
 Once they are part of Git repository history they cannot be removed.
 
 ## Quality check of the changes ##
 
-Continuous Integration will check your changes automatically once you create a merge request.
+Continuous Integration checks your changes automatically once you create a merge request.
 Nevertheless, local quality check should also be done before submitting a merge request.
 The checks can include:
   * Static code analysis and coverage
@@ -78,10 +79,10 @@ See [Separate the changes](#separate-the-changes).
 
 Create commit or merge requests descriptions that are self-contained.
 This benefits both the maintainers and reviewers.
-Always use your real name and e-mail address for committing changes.
+Always use a known identity and email address for committing changes.
 
 If the commit fixes a reported issue, refer to that bug entry by issue number.
-The issue will be closed automatically after merge, if it matches [this regular expression](https://docs.gitlab.com/ce/user/project/issues/automatic_issue_closing.html).
+The issue closes automatically after merge, if it matches [this regular expression](https://docs.gitlab.com/ce/user/project/issues/automatic_issue_closing.html).
 
 ## Create a merge request ##
 
@@ -91,7 +92,7 @@ Merge requests must not contain other merge requests; re-base your commits if ne
 
 ## Respond to review comments ##
 
-Your merge request will almost certainly get comments from reviewers on ways in which it can be improved.
+Your merge request almost certainly gets comments from reviewers on ways in which it can be improved.
 You must respond to those comments; ignoring reviewers is a good way to get ignored in return.
 Be sure to tell the reviewers what changes you are making and to thank them for their time.
 Code review is a tiring and time-consuming process, and reviewers sometimes get grumpy.
@@ -106,9 +107,9 @@ Wait for a minimum of one week before pinging reviewers - possibly longer during
 
 ## Sign your work - the Developer’s Certificate of Origin ##
 
-To improve tracking of who did what, especially with commits that can percolate to their final resting place in Libre Space Foundation projects code-base through several layers of maintainers, we’ve introduced a “sign-off” procedure on commits.
+To improve tracking of who did what, especially with commits that can percolate to their final resting place in Libre Space Foundation projects code-base through several layers of maintainers, a “sign-off” procedure on commits is enforced.
 
-The sign-off is a simple line at the end of the explanation for the commit, which certifies that you wrote it or otherwise have the right to pass it on as an open-source patch.
+The sign-off is a simple line at the end of the explanation for the commit, which certifies that you wrote it or otherwise have the right to pass it on as an open source patch.
 The rules are pretty simple:
 
 if you can certify the below:
@@ -138,7 +139,7 @@ then you just add a line saying:
 
 `Signed-off-by: Random J Developer <random@developer.example.org>`
 
-using your real name (sorry, no pseudonyms or anonymous contributions.)
+using a known identity (sorry, no anonymous contributions.)
 
 If you are a maintainer, sometimes you need to slightly modify commits order to merge them.
 If you stick strictly to rule (c), you should ask the submitter to rediff, but this is a totally counter-productive waste of time and energy.
@@ -152,6 +153,83 @@ Signed-off-by: Random J Developer <random@developer.example.org>
 Signed-off-by: Lucky K Maintainer <lucky@maintainer.example.org>
 ```
 
+## Generative AI / LLM Policy ##
+
+We appreciate that we can't realistically police how you author your merge requests, which includes whether you employ large-language model (LLM)-based development tools.
+So, we don't.
+
+However, due to both legal and human reasons, we have to establish boundaries.
+
+### Overview ###
+
+- We take the responsibility for this project very seriously and we expect you to take your responsibility for your contributions seriously, too.
+  This used to be a given, but it changed now that a merge request is just one prompt away.
+- Every contribution has to be backed by a human who unequivocally owns the copyright for all changes.
+  No LLM bots in `Co-authored-by:`s.
+- Repeated slop contributions are unacceptable, and will be closed without review.
+  We reserve the right to exclude contributors who continue to submit such material.
+- Absolutely no unsupervised agentic tools like OpenClaw.
+
+By submitting a merge request, you certify that:
+
+- You are the author of the contribution or have the legal right to submit it.
+- You either hold the copyright to the changes or have explicit legal authorization to contribute them under this project's license.
+- You understand the code.
+- You accept full responsibility for it.
+
+### Legal ###
+
+There is ongoing legal uncertainty regarding the copyright status of LLM-generated works and their provenance.
+Because of this, allowing contributions by LLMs has unpredictable consequences for the copyright status of this project - even when leaving aside possible copyright violations due to plagiarism.
+
+### Human ###
+
+As the makers of software that is used by many people worldwide and with a reputation for high-quality maintenance, we take our responsibility to our users very seriously.
+No matter what LLM vendors or boosters on LinkedIn tell you, we have to manually review every change before merging, because it's our responsibility to keep the project stable.
+
+Please understand that by opening low-quality merge requests you're not helping anyone.
+Worse, you're [poisoning the open source ecosystem](https://lwn.net/Articles/1058266/) that was precarious even before the arrival of LLM tools.
+Having to wade through plausible-looking-but-low-quality merge requests and trying to determine which ones are legit is extremely demoralizing and has already burned out many good maintainers.
+
+In particular, note that [code reviews are a social process](https://blog.glyph.im/2026/03/what-is-code-review-for.html) and are *not* intended to catch bugs in PRs created by an LLM.
+If you submit a merge request, we expect you to engage with reviewers and learn from the review, not
+simply update the prompt that generated the PR and regenerate the code.
+
+Put bluntly, we have no time or interest to become part of your vibe coding loop where you drop LLM slop at our door, we spend time and energy to review it, and you just feed it back into the LLM for another iteration.
+
+This dynamic is especially pernicious because it poisons the well for mentoring new contributors which we are committed to.
+
+### Summary ###
+
+In practice, this means:
+
+- Merge requests that have an LLM product listed as co-author can't be merged and will be closed without further discussion.
+  We cannot risk the copyright status of this project.
+
+  If you used LLM tools during development, you may still submit - but you must remove any LLM co-author tags and take full ownership of every line.
+
+- By submitting a merge request, you take full technical and legal responsibility for the contents of the merge request and promise that you hold the copyright for the changes submitted.
+
+  "An LLM wrote it" is *not* an acceptable response to questions or critique.
+  If you cannot explain and defend the changes you submit, do not submit them and open a high-quality bug report or feature request instead.
+
+- Accounts that exercise bot-like behavior, like automated mass merge requests, will be permanently banned, whether they belong to a human or not.
+
+- LLM-generated comments must be concise and accurate, and you must be prepared to stand by them.
+  Do not post summaries unless you are certain that they add value to the discussion.
+  Remember that all LLM output *looks* plausible.
+  When using these tools, it's your responsibility to ensure that the output is correct, and useful.
+
+- Remember that LLM generated content is generally easier for you to produce, but *harder* for others to read, review or interpret.
+  Prioritising your time over that of others is contrary to the project's code of conduct.
+  Verbose, repetitive, or off topic comments may be marked as spam.
+
+### Thanks ###
+
+This LLM policy was based on the policy of the `pip` and `attrs` project.
+Many thanks to them for developing it.
+
 ## References ##
 
   * Linux kernel documentation - [Submitting patches: the essential guide to getting your code into the kernel](https://www.kernel.org/doc/html/latest/process/submitting-patches.html)
+  * pip AI policy - [Generative AI / LLM Policy](https://github.com/pypa/pip/blob/main/AI_POLICY.md)

{satnogs_predict-0.6 → satnogs_predict-1.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: satnogs-predict
-Version: 0.6
+Version: 1.1
 Summary: A package for calculating passes and observation windows for satellites.
 Requires-Python: >=3.11
 Description-Content-Type: text/markdown
@@ -46,6 +46,8 @@ from satnogs_predict import find_observation_windows
 
 For more complete examples and usage patterns, see [docs/docs.md](docs/docs.md).
 
+For release notes and breaking changes, see [CHANGELOG.md](CHANGELOG.md).
+
 ## License
 
 [![license](https://img.shields.io/badge/license-AGPL%203.0-6672D8.svg)](LICENSE)

{satnogs_predict-0.6 → satnogs_predict-1.1}/README.md

@@ -36,6 +36,8 @@ from satnogs_predict import find_observation_windows
 
 For more complete examples and usage patterns, see [docs/docs.md](docs/docs.md).
 
+For release notes and breaking changes, see [CHANGELOG.md](CHANGELOG.md).
+
 ## License
 
 [![license](https://img.shields.io/badge/license-AGPL%203.0-6672D8.svg)](LICENSE)

{satnogs_predict-0.6 → satnogs_predict-1.1}/docs/docs.md

@@ -20,10 +20,9 @@
 - [6 - Finding passes](#6---finding-passes)
   - [6.1 - Constraints](#61---constraints)
   - [6.2 - Windows returned](#62---windows-returned)
-  - [6.3 - Implementation Details](#63---implementation-details)
-  - [6.4 - Full workflow for finding passes](#64---full-workflow-for-finding-passes)
-  - [6.5 - Sampling point-in-time geometry](#65---sampling-point-in-time-geometry)
-  - [6.6 - Full workflow for validating time ranges that belong to passes](#66---full-workflow-for-validating-time-ranges-that-belong-to-passes)
+  - [6.3 - Full workflow for finding passes](#63---full-workflow-for-finding-passes)
+  - [6.4 - Sampling point-in-time geometry](#64---sampling-point-in-time-geometry)
+  - [6.5 - Full workflow for validating time ranges that belong to passes](#65---full-workflow-for-validating-time-ranges-that-belong-to-passes)
 
 
 # 1. Installation
@@ -102,8 +101,12 @@ satellite = Satellite.from_omm(
 )
 ```
 
-The `identifier` is optional and defaults to a random UUID. Provide an explicit
-identifier when you need a stable public value or cache key.
+The `identifier` is optional metadata and defaults to an empty string. It is copied
+to produced `ObservationWindow.sat_identifier` values so callers can conveniently connect windows back to their own satellite records.
+
+Because the underlying skyfield object EarthSatellite is computationally expensive to create, the EarthSatellite of the last-used satellite is cached. Cache identity is based on orbital state: TLE `line1`/`line2`, or normalized OMM fields.
+
+OMM field data are copied when the `OMM` object is created. The stored mapping is read-only, and `to_dict()` returns a mutable copy.
 
 For testing or development, you can also generate a synthetic TLE:
 
@@ -133,8 +136,11 @@ station = Observer(
 )
 ```
 
-The `identifier` is optional here as well and defaults to a random UUID. Provide one
-when you need a stable public value or cache key.
+The `identifier` is optional metadata and defaults to an empty string. It is copied
+to produced `ObservationWindow.observer_identifier` for convenience.
+
+Because the underlying skyfield object Topos that represents an observer is computationally expensive, the Topos of the last-used observer is cached.
+Observer cache identity depends on `lat_deg`, `lon_deg` and `elevation_meters`. The `horizon_deg` value is not part of the Topos object so it doesn't affect caching.
 
 
 ## 3.3 - Time Modeling
@@ -248,13 +254,14 @@ class ObservationWindow:
     A schedulable observation window.
     """
 
-    sat_identifier: str
-    observer_identifier: str
-
     start_sample: GeometrySample
     end_sample: GeometrySample
     max_altitude_sample: GeometrySample
 
+    # Caller metadata copied from Satellite.identifier and Observer.identifier.
+    sat_identifier: str = ""
+    observer_identifier: str = ""
+
     # The altitude has multiple peaks during the window (None means unknown)
     has_multiple_peaks: bool | None = None
 
@@ -404,15 +411,7 @@ For the helper `get_and_validate_pass_from_range`, constraints are validated via
 
 The function returns a tuple of observation window lists. The first element of the tuple is the list of valid windows, and the second is the list of windows that were rejected due to constraints.
 
-## 6.3 - Implementation Details
-
-Internally, satellite & observer are converted to Skyfield's types, which is computationally expensive. For this reason, the last satellite and the last observer used is cached, differentiated by the `identifier` field.
-
-This way, repeated consecutive calls of `find_observation_windows` with the same satellite, or with the same `observer` reuse the objects under the hood.
-
-If you need to clear these caches explicitly, the public helpers `clear_satellite_cache()` and `clear_observer_cache()` are available.
-
-## 6.4 - Full workflow for finding passes
+## 6.3 - Full workflow for finding passes
 
 High-level process:
 
@@ -484,7 +483,7 @@ valid_windows, rejected_windows = find_observation_windows(
 )
 ```
 
-## 6.5 - Sampling point-in-time geometry
+## 6.4 - Sampling point-in-time geometry
 
 For point-in-time queries, the public API also provides helpers for sampling a satellite relative to an observer at a single `Instant`.
 
@@ -506,7 +505,7 @@ range_sample = get_range(
 - `get_range()` returns a `RangeSample` with range in meters and range rate in meters per second.
 
 
-## 6.6 - Full workflow for validating time ranges that belong to passes
+## 6.5 - Full workflow for validating time ranges that belong to passes
 
 - Given a time range, we can validate whether it belongs to a single pass and whether it satisfies constraints.
 

satnogs_predict-1.1/src/satnogs_predict/domain/observer.py

@@ -0,0 +1,35 @@
+from __future__ import annotations
+
+from dataclasses import dataclass, field
+
+from satnogs_predict.utils import cache_digest
+
+from .validation import ensure_required_fields_not_none
+
+
+@dataclass(frozen=True, slots=True)
+class Observer:
+    """Observer to calculate passes over e.g. a ground station"""
+
+    lat_deg: float
+    lon_deg: float
+    elevation_meters: int
+    horizon_deg: float
+    identifier: str = ""
+    _cache_key: str = field(init=False, repr=False, compare=False, default="")
+
+    def __post_init__(self) -> None:
+        ensure_required_fields_not_none(self)
+        object.__setattr__(
+            self,
+            "_cache_key",
+            cache_digest(
+                str(self.lat_deg),
+                str(self.lon_deg),
+                str(self.elevation_meters),
+            ),
+        )
+
+    @property
+    def cache_key(self) -> str:
+        return self._cache_key

{satnogs_predict-0.6 → satnogs_predict-1.1}/src/satnogs_predict/domain/orbit.py

@@ -3,7 +3,9 @@ from __future__ import annotations
 from collections.abc import Mapping
 from dataclasses import dataclass, field
 from enum import IntEnum
-from uuid import uuid4
+from types import MappingProxyType
+
+from satnogs_predict.utils import cache_digest
 
 from .validation import ensure_required_fields_not_none
 
@@ -13,24 +15,41 @@ class TLE:
     line0: str
     line1: str
     line2: str
+    _cache_key: str = field(init=False, repr=False, compare=False, default="")
 
     def __post_init__(self) -> None:
         ensure_required_fields_not_none(self)
+        object.__setattr__(self, "_cache_key", cache_digest(self.line1, self.line2))
 
     def to_list(self) -> list[str]:
         return [self.line0, self.line1, self.line2]
 
+    @property
+    def cache_key(self) -> str:
+        return self._cache_key
+
 
 @dataclass(frozen=True, slots=True)
 class OMM:
-    fields: dict[str, str]
+    fields: Mapping[str, str]
+    _cache_key: str = field(init=False, repr=False, compare=False, default="")
 
     def __post_init__(self) -> None:
         ensure_required_fields_not_none(self)
+        fields = MappingProxyType(dict(self.fields))
+        object.__setattr__(self, "fields", fields)
+        parts: list[str] = []
+        for key, value in sorted(fields.items()):
+            parts.extend((key, value))
+        object.__setattr__(self, "_cache_key", cache_digest(*parts))
 
     def to_dict(self) -> dict[str, str]:
         return dict(self.fields)
 
+    @property
+    def cache_key(self) -> str:
+        return self._cache_key
+
 
 class OrbitRepresentation(IntEnum):
     TLE = 0
@@ -41,27 +60,37 @@ class OrbitRepresentation(IntEnum):
 class Orbit:
     representation: OrbitRepresentation
     data: TLE | OMM
+    _cache_key: str = field(init=False, repr=False, compare=False, default="")
 
     def __post_init__(self) -> None:
         ensure_required_fields_not_none(self)
+        object.__setattr__(self, "_cache_key", self.data.cache_key)
+
+    @property
+    def cache_key(self) -> str:
+        return self._cache_key
 
     @classmethod
     def from_omm(
         cls,
         fields: Mapping[str, str],
     ):
-        return cls(representation=OrbitRepresentation.OMM, data=OMM(fields=dict(fields)))
+        return cls(representation=OrbitRepresentation.OMM, data=OMM(fields=fields))
 
 
 @dataclass(frozen=True, slots=True)
 class Satellite:
     orbit: Orbit
-    identifier: str = field(default_factory=lambda: str(uuid4()))
+    identifier: str = ""
+    _cache_key: str = field(init=False, repr=False, compare=False, default="")
 
     def __post_init__(self) -> None:
-        if self.identifier is None:
-            object.__setattr__(self, "identifier", str(uuid4()))
         ensure_required_fields_not_none(self)
+        object.__setattr__(self, "_cache_key", self.orbit.cache_key)
+
+    @property
+    def cache_key(self) -> str:
+        return self._cache_key
 
     @classmethod
     def from_tle(
@@ -69,21 +98,17 @@ class Satellite:
         line0: str,
         line1: str,
         line2: str,
-        identifier: str | None = None,
+        identifier: str = "",
     ):
         tle = TLE(line0=line0, line1=line1, line2=line2)
         orbit = Orbit(representation=OrbitRepresentation.TLE, data=tle)
-        if identifier is None:
-            return cls(orbit=orbit)
         return cls(orbit=orbit, identifier=identifier)
 
     @classmethod
     def from_omm(
         cls,
         fields: Mapping[str, str],
-        identifier: str | None = None,
+        identifier: str = "",
     ):
         orbit = Orbit.from_omm(fields)
-        if identifier is None:
-            return cls(orbit=orbit)
         return cls(orbit=orbit, identifier=identifier)

{satnogs_predict-0.6 → satnogs_predict-1.1}/src/satnogs_predict/domain/window.py

@@ -19,13 +19,13 @@ class ObservationWindow:
     A schedulable observation window.
     """
 
-    sat_identifier: str
-    observer_identifier: str
-
     start_sample: GeometrySample
     end_sample: GeometrySample
     max_altitude_sample: GeometrySample
 
+    sat_identifier: str = ""
+    observer_identifier: str = ""
+
     # The altitude does has multiple peaks during the window (None means unknown)
     has_multiple_peaks: bool | None = None
 

{satnogs_predict-0.6 → satnogs_predict-1.1}/src/satnogs_predict/propagation/propagator.py

@@ -65,20 +65,20 @@ def _instant_from_skyfield_time(t: Time):
 
 
 _last_sat: EarthSatellite | None = None
-_last_sat_identifier: str | None = None
+_last_sat_cache_key: str | None = None
 
 
 def clear_satellite_cache() -> None:
-    global _last_sat, _last_sat_identifier
+    global _last_sat, _last_sat_cache_key
 
     _last_sat = None
-    _last_sat_identifier = None
+    _last_sat_cache_key = None
 
 
 def _skyfield_sat_from_satellite(satellite: Satellite) -> EarthSatellite:
-    global _last_sat, _last_sat_identifier
+    global _last_sat, _last_sat_cache_key
 
-    if _last_sat_identifier == satellite.identifier and _last_sat is not None:
+    if _last_sat_cache_key == satellite.cache_key and _last_sat is not None:
         return _last_sat
 
     match satellite.orbit.representation:
@@ -87,8 +87,7 @@ def _skyfield_sat_from_satellite(satellite: Satellite) -> EarthSatellite:
             skyfield_sat = EarthSatellite(
                 tle.line1,
                 tle.line2,
-                satellite.identifier,
-                ts,
+                ts=ts,
             )
         case OrbitRepresentation.OMM:
             omm = cast(OMM, satellite.orbit.data)
@@ -96,26 +95,26 @@ def _skyfield_sat_from_satellite(satellite: Satellite) -> EarthSatellite:
         case _:
             raise ValueError("Unknown orbit representation")
 
-    _last_sat_identifier = satellite.identifier
+    _last_sat_cache_key = satellite.cache_key
     _last_sat = skyfield_sat
     return skyfield_sat
 
 
 _last_topos: Topos | None = None
-_last_identifier: str | None = None
+_last_observer_cache_key: str | None = None
 
 
 def clear_observer_cache() -> None:
-    global _last_topos, _last_identifier
+    global _last_topos, _last_observer_cache_key
 
     _last_topos = None
-    _last_identifier = None
+    _last_observer_cache_key = None
 
 
 def _skyfield_topos_from_observer(observer: Observer) -> Topos:
-    global _last_topos, _last_identifier
+    global _last_topos, _last_observer_cache_key
 
-    if _last_identifier == observer.identifier and _last_topos is not None:
+    if _last_observer_cache_key == observer.cache_key and _last_topos is not None:
         return _last_topos
 
     _last_topos = Topos(
@@ -123,7 +122,7 @@ def _skyfield_topos_from_observer(observer: Observer) -> Topos:
         longitude_degrees=observer.lon_deg,
         elevation_m=observer.elevation_meters,
     )
-    _last_identifier = observer.identifier
+    _last_observer_cache_key = observer.cache_key
     return _last_topos
 
 

{satnogs_predict-0.6 → satnogs_predict-1.1}/src/satnogs_predict/tle.py

@@ -71,17 +71,17 @@ def generate_fake_tle(
     right_ascension = (observer_location.lst_hours_at(skyfield_time) * 15.0) % 360.0
     mean_anomaly = latitude % 360.0
 
-    epoch_year = epoch.year
+    epoch_year = epoch.year % 100
     epoch_day = _epoch_day_of_year_fraction(epoch)
 
     line0 = params.name.ljust(24)
 
     line1_no_checksum = (
-        "1 {:5.5}{:.1} {:8.8} {:.2}{:012.8f} {:>10.10} {:>8.8} {:>8.8} 0 {:>4.4}".format(
+        "1 {:5.5}{:.1} {:8.8} {:02d}{:012.8f} {:>10.10} {:>8.8} {:>8.8} 0 {:>4.4}".format(
             f"{params.catalog_num:05d}",
             params.classifier,
             params.cospar_id,
-            str(epoch_year),
+            epoch_year,
             epoch_day,
             params.mean_motion_first,
             params.mean_motion_second,

satnogs_predict-1.1/src/satnogs_predict/utils.py

@@ -0,0 +1,7 @@
+from __future__ import annotations
+
+from hashlib import sha256
+
+
+def cache_digest(*parts: str) -> str:
+    return sha256("".join(parts).encode()).hexdigest()

{satnogs_predict-0.6 → satnogs_predict-1.1}/src/satnogs_predict.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: satnogs-predict
-Version: 0.6
+Version: 1.1
 Summary: A package for calculating passes and observation windows for satellites.
 Requires-Python: >=3.11
 Description-Content-Type: text/markdown
@@ -46,6 +46,8 @@ from satnogs_predict import find_observation_windows
 
 For more complete examples and usage patterns, see [docs/docs.md](docs/docs.md).
 
+For release notes and breaking changes, see [CHANGELOG.md](CHANGELOG.md).
+
 ## License
 
 [![license](https://img.shields.io/badge/license-AGPL%203.0-6672D8.svg)](LICENSE)

{satnogs_predict-0.6 → satnogs_predict-1.1}/src/satnogs_predict.egg-info/SOURCES.txt

@@ -2,6 +2,7 @@
 .gitlab-ci.yml
 .pre-commit-config.yaml
 .python-version
+CHANGELOG.md
 CONTRIBUTING.md
 LICENSE
 README.md
@@ -12,10 +13,13 @@ docs/docs.md
 src/satnogs_predict/__init__.py
 src/satnogs_predict/py.typed
 src/satnogs_predict/tle.py
+src/satnogs_predict/utils.py
 src/satnogs_predict.egg-info/PKG-INFO
 src/satnogs_predict.egg-info/SOURCES.txt
 src/satnogs_predict.egg-info/dependency_links.txt
 src/satnogs_predict.egg-info/requires.txt
+src/satnogs_predict.egg-info/scm_file_list.json
+src/satnogs_predict.egg-info/scm_version.json
 src/satnogs_predict.egg-info/top_level.txt
 src/satnogs_predict/constraints/__init__.py
 src/satnogs_predict/constraints/constraints.py