Adding light-curve-python

[hombit]

Checklist

• Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
• License file is packaged (see here for an example).
• Source is from official source.
• Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
• If static libraries are linked in, the license of the static library is packaged.
• Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
• Build number is 0.
• A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
• GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
• When in trouble, please check our knowledge base documentation before pinging a team.

[github-actions]

Hi! This is the staged-recipes linter and I found some lint.

It looks like some changes were made outside the recipes/ directory. To ensure everything runs smoothly, please make sure that recipes are only added to the recipes/ directory and no other files are changed.

If these changes are intentional (and you aren't submitting a recipe), please add a maintenance label to the PR.

File-specific lints and/or hints:

• .ci_support/osx_arm64.yaml:
  • lints:
    • Do not edit files outside of the recipes/ directory.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR () and found it was in an excellent condition.

[github-actions]

Hi! This is the staged-recipes linter and your PR looks excellent! 🚀

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/light-curve-python/meta.yaml) and found some lint.

Here's what I've got...

For recipes/light-curve-python/meta.yaml:

• ❌ requirements: host: maturin>=1,<2 must contain a space between the name and the pin, i.e. maturin >=1,<2
• ❌ requirements: run: numpy<3 must contain a space between the name and the pin, i.e. numpy <3
• ❌ requirements: run: iminuit>=2.21,<3 must contain a space between the name and the pin, i.e. iminuit >=2.21,<3
• ❌ requirements: run: scipy>=1,<2 must contain a space between the name and the pin, i.e. scipy >=1,<2
• ❌ Non noarch packages should have python requirement without any version constraints.
• ❌ Non noarch packages should have python requirement without any version constraints.

For recipes/light-curve-python/meta.yaml:

• ℹ️ No valid build backend found for Python recipe for package light-curve-python using pip. Python recipes using pip need to explicitly specify a build backend in the host section. If your recipe has built with only pip in the host section in the past, you likely should add setuptools to the host section of your recipe.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12673964927. Examine the logs at this URL for more detail.}

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/light-curve-python/meta.yaml) and found it was in an excellent condition.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/light-curve-python/meta.yaml) and found some lint.

Here's what I've got...

For recipes/light-curve-python/meta.yaml:

• ❌ Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [33, 41]

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12682088575. Examine the logs at this URL for more detail.}

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/light-curve-python/meta.yaml) and found it was in an excellent condition.

[hombit]

@conda-forge/help-python, it almost ready for review. I have a question about the license: my package is built with Rust and depends on a lot of packages Rust packages. How should I attach licenses to the recipe?

cargo license --no-default-features --features=fftw-system output

(MIT OR Apache-2.0) AND Unicode-3.0 (1): unicode-ident
0BSD (2): enum-iterator, enum-iterator-derive
0BSD OR Apache-2.0 OR MIT (1): adler2
Apache-2.0 (1): noisy_float
Apache-2.0 OR Apache-2.0 WITH LLVM-exception OR MIT (1): wasi
Apache-2.0 OR BSD-2-Clause OR MIT (2): zerocopy, zerocopy-derive
Apache-2.0 OR BSL-1.0 (1): ryu
Apache-2.0 OR MIT (91): addr2line, autocfg, backtrace, bitflags, cfg-if, crossbeam-deque, crossbeam-epoch, crossbeam-utils, custom_derive, dyn-clone, either, enum_dispatch, enumflags2, enumflags2_derive, equivalent, error-chain, getrandom, gimli, hashbrown, heck, hermit-abi, indexmap, indoc, inventory, iter-read, itertools, itertools, itoa, lazy_static, libc, matrixmultiply, ndarray, ndarray, ndarray-stats, num-bigint, num-complex, num-integer, num-traits, num_cpus, object, once_cell, paste, portable-atomic, portable-atomic-util, ppv-lite86, proc-macro2, pyo3, pyo3-build-config, pyo3-ffi, pyo3-macros, pyo3-macros-backend, quote, rand, rand, rand, rand_chacha, rand_core, rand_core, rand_core, rand_xoshiro, rawpointer, rayon, rayon-core, rustc-demangle, rustc-hash, rustversion, serde, serde-pickle, serde_derive, serde_derive_internals, serde_json, syn, thiserror, thiserror, thiserror-impl, thiserror-impl, thread_local, unicode-xid, unindent, winapi, winapi-i686-pc-windows-gnu, winapi-x86_64-pc-windows-gnu, windows-targets, windows_aarch64_gnullvm, windows_aarch64_msvc, windows_i686_gnu, windows_i686_gnullvm, windows_i686_msvc, windows_x86_64_gnu, windows_x86_64_gnullvm, windows_x86_64_msvc
Apache-2.0 OR MIT OR Zlib (1): miniz_oxide
Apache-2.0 WITH LLVM-exception (1): target-lexicon
Apache-2.0) OR MIT AND (MIT (1): libm
BSD-2-Clause (1): numpy
Custom License File (3): fftw, fftw-sys, fuchsia-cprng
GPL-3.0-or-later (2): light-curve-feature, light-curve-python
ISC (1): rdrand
MIT (8): conv, emcee, light-curve-dmdt, macro_const, memoffset, schemars, schemars_derive, unzip3
MIT OR Unlicense (2): byteorder, memchr
Zlib (2): const_format, const_format_proc_macros

[synapticarbors]

see:
https://conda-forge.org/docs/maintainer/adding_pkgs/#licenses-of-included-dependencies

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint --conda-forge . from the recipe directory. You can also examine the workflow logs for more detail.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12699019287. Examine the logs at this URL for more detail.}

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/light-curve-python/meta.yaml) and found it was in an excellent condition.

[hombit]

@conda-forge/help-python, @synapticarbors It is ready for review. I created the third-party license file.

I left the “static library” and “vendoring” boxes unchecked because I am not sure if this terminology applies to Rust packages. I believe there are no C/C++ packages bundled with the package.

I don't understand why the CI doesn't build the package for python 3.13. However the package can be built in a ABI3-compatible mode (it is what I use for PyPI), but I don't know how to specify that it is built in this way in meta.yaml.