Light-curve

Latest version: v0.9.6

Safety actively analyzes 678576 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 8

0.9.0

Added

- `Roms` (robust median statistics) experimental feature, a variability index based on the deviation of observations
from the median. https://github.com/light-curve/light-curve-python/pull/315 Thanks GaluTi for their first
contribution

Changed

- **Breaking** `RainbowFit` is significantly refactored to make it more flexible for usage of different bolometric and
temperature functions. It deletes `RainbowRisingFit` and `RainbowSymmetricFit` in favor of a single `RainbowFit`
feature. https://github.com/light-curve/light-curve-python/pull/324
- **Breaking**: stop supporting Python 3.7 https://github.com/light-curve/light-curve-python/pull/282
- We stop distributing CPython wheels for specific Python versions, now we distribute ABI3 wheels which are compatible
with all future Python versions

Deprecated

--

Removed

- **Build breaking**: `abi311` Cargo feature is removed, now we plan to have `abi3` feature only, which would correspond
to the minimum supported Python version. Feel free to use `pyo3/abi3..` features directly for newer ABI versions.

Fixed

--

Security

--

0.8.2

Added

- New flavour of `RainbowFit`: `RainbowSymmetricFit` which will replace both `RainbowFit` and `RainbowRisingFit` in the
future. https://github.com/light-curve/light-curve-python/pull/314 Thanks karpov-sv for their first contribution
- New cargo build-time feature, `mimalloc`, it is default feature now. When activated, it gives up to 2.9x of
performance boost for some "fast" features. https://github.com/light-curve/light-curve-python/pull/302

Changed

- Refactoring of rainbow features, it reduces code duplication and makes it easier to add new variants like `RainbowFit`
and `RainbowRisingFit` in the future https://github.com/light-curve/light-curve-python/pull/293
- Another change for `Rainbow` features is changing `minuit` optimization
parameters https://github.com/light-curve/light-curve-python/pull/314
- **Build breaking**: bump `light-curve-feature` to v0.7.0, which requires ceres-solver v2.2 for `ceres-system` Cargo
feature.

Fixed

- `RainbowFit` and `RainbowRisingFit` initial guesses for baseline fluxes are now consistent with limits. We also use
band information to make initial guesses and limits more accurate. Note, that this change leads to different results
comparing to previous versions. https://github.com/light-curve/light-curve-python/pull/293

0.8.1

Added

- `RainbowRisingFit` experimental feature, https://github.com/light-curve/light-curve-python/pull/278
by [erusseil](https://github.com/erusseil)

0.8.0

Added

- **Breaking change in experimental features**: Multiband support is introduced for features implemented in Python. It
changes class inheritance interface in a backward-incompatible way
- `light-curve[full]` extras which installs all optional Python dependencies required by experimental features
- New `LinexpFit` feature for parametric model fit comes with `light-curve-feature` v0.6.0
- Experimental `RainbowFit` feature for fitting multiband light curves with a single model, Russeil+23 in prep. It
requires Python 3.8 or later because of `iminuit` dependency
- Optional `iminuit>=2,<3` Python dependency (included into `[full]`) for `RainbowFit` feature
- Add `once_cell` v1 dependency

Changed

- **Breaking change in experimental features** `scipy` dependency is now optional for experimental features implemented
in Python
- **Breaking change in experimental features**: All experimental features implemented in Python require keyword-only
arguments in their constructors. Also, all names of the arguments are changed to be the same as for Rust features
- **Build breaking**: "abi3-py310" Cargo feature is replaced with "abi3-py311". "abi3" feature is now linked to "
abi3-py311" feature. This is because our aim with ABI is to support future versions of Python
- **Build breaking**: minimum supported Rust version (MSRV) is changed from 1.62 to 1.67 (released 2023-01-26)
- Update `*Fit` fatures doc-strings to list names of the features they output
- Bump `light-curve-feature` 0.5.5 -> 0.6.0
- Bump `pyO3` 0.18.3 -> 0.19.1, it simplified signature generations for
classes https://github.com/light-curve/light-curve-python/pull/230
- Bump `rust-numpy` 0.18.0 -> 0.19.0 https://github.com/light-curve/light-curve-python/pull/230
- Bump `enum-iterator` 1.2.0 -> 1.4.1 https://github.com/light-curve/light-curve-python/pull/233
- Bump `thiserror` 1.0.41 -> 1.0.48 https://github.com/light-curve/light-curve-python/pull/242

0.7.3

Added

- All Rust features got `.to_json()` method to serialize their state to JSON
string. https://github.com/light-curve/light-curve-python/pull/226
- New special Rust feature `JSONDeserializedFeature` and a helper function `feature_from_json()` to deserialize features
from JSON string. https://github.com/light-curve/light-curve-python/pull/226
- Build: "abi3" and "abi3-py310" Cargo features (the least one is enabled by the first one) to build a wheel for CPython
3.10+. This stable ABI wheel is less performant than the regular one, but it is compatible with all future Python
versions. See [PEP 384](https://www.python.org/dev/peps/pep-0384/) for
details. https://github.com/light-curve/light-curve-python/issues/79

Changed

- **Build breaking**: the only Python build requirement `maturin` updated from v0.14.x to
v1.0 https://github.com/light-curve/light-curve-python/pull/216 https://github.com/light-curve/light-curve-python/pull/215
- CI: bump cibuildwheel to 2.13.1 https://github.com/light-curve/light-curve-python/pull/225
- Bump `itertools` 0.10.5 -> 0.11.0 https://github.com/light-curve/light-curve-python/pull/224
- Bump `pyO3` 0.18.2 -> 0.18.3 https://github.com/light-curve/light-curve-python/pull/207

Fixed

- Building from sdist on x86-64 macOS required manual setting of `$MACOSX_DEPLOYMENT_TARGET` to 10.9 or higher.
Recent `maturin` update allowed us to specify it via `pyproject.toml`

0.7.2

Added

- Feature transformations via `transform` constructor keyword. For most of the features it could accept string with a
transformation name such as 'arcsinh' or 'clipped_lg', `True` or 'default' for the default transformation, `None`
or `False` for no
transformation https://github.com/light-curve/light-curve-python/issues/184 https://github.com/light-curve/light-curve-python/pull/188
- Binary wheels for x86_64 Windows built with no Ceres nor GSL
features https://github.com/light-curve/light-curve-python/issues/12 https://github.com/light-curve/light-curve-python/pull/185
- `enum-iterator` crate dependency https://github.com/light-curve/light-curve-python/pull/188
- CI: code coverage with `codecov` https://github.com/light-curve/light-curve-python/pull/197
- Development: now project has extras for testing (`test`) and
development (`dev`) https://github.com/light-curve/light-curve-python/pull/197

Changed

- **Build breaking**: minimum supported Rust version (MSRV) is bump from 1.60 to 1.62
- Bump `light-curve-feature` 0.5.4 -> 0.5.5
- Bump `pyO3` 0.18.1 -> 0.18.2
- Most of the parametric features have default values for their parameters now, which, due to `pyO3` limitations, are
not presented in the signatures, but documented in the docstrings. It also makes Python and Rust implementations more
consistent https://github.com/light-curve/light-curve-python/issues/194 https://github.com/light-curve/light-curve-python/pull/195
- Development: switch from `pytest-markdown` to `markdown-pytest` which allowed us to use up-to-date
pytest https://github.com/light-curve/light-curve-python/pull/198

Deprecated

- `BazinFit` and `VillarFit` constructors will not accept `None` for `mcmc_niter`, `ceres_niter`, and `lmsder_niter`
arguments in the future, just do not specify them to use defaults
instead. https://github.com/light-curve/light-curve-python/pull/195
- `Periodogram` constructor will not accept `None` for `peaks`, `resolution`, `max_freq_factor`, `nyquist` and `fast` in
the future, just do not specify them to use defaults
instead. https://github.com/light-curve/light-curve-python/pull/195

Fixed

- `Bins` feature had non-optimal lower boundary check for time series length: it checked if it is at least unity for any
underlying features. Now it takes underlying feature requirements into account. It was fixed by
updating `light-curve-feature` to v0.5.5.

Page 2 of 8

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.