Metadata-Version: 2.4
Name: amica
Version: 0.1.1
Summary: Renamed to jamica -- install `jamica` instead. This release installs it for you and ships no modules of its own.
Author-email: Sina Esmaeili <sina.esmaeili@umontreal.ca>
License: BSD-3-Clause
Project-URL: Homepage, https://github.com/snesmaeili/jamica
Project-URL: Documentation, https://snesmaeili.github.io/jamica/
Project-URL: Repository, https://github.com/snesmaeili/jamica.git
Project-URL: Issues, https://github.com/snesmaeili/jamica/issues
Classifier: Development Status :: 7 - Inactive
Classifier: Intended Audience :: Science/Research
Classifier: License :: OSI Approved :: BSD License
Classifier: Operating System :: OS Independent
Classifier: Programming Language :: Python :: 3
Classifier: Topic :: Scientific/Engineering
Requires-Python: >=3.10
Description-Content-Type: text/markdown
License-File: LICENSE
Requires-Dist: jamica>=0.2.0
Dynamic: license-file

# amica has been renamed to [jamica](https://pypi.org/project/jamica/)

**Install `jamica` instead:**

```bash
pip install jamica
```

```python
from jamica import Amica, AmicaConfig, fit_ica
```

This `amica` release (0.1.1) is a pointer. It contains no modules of its own — it only depends on `jamica`, so an existing `pip install amica` still ends up with working code.

## Why the rename

The name `amica` installed a top-level `amica` module. So does [`amica-python`](https://pypi.org/project/amica-python/), an independent implementation of the same algorithm by another author. The two overwrote each other's files, so only one could exist in a given environment — the conda-forge packages even had to be declared mutually exclusive.

That is an awkward constraint for any user, and a particularly bad one here: this project's own benchmark suite compares the two implementations against each other.

Under the name `jamica` the two share no files and install side by side.

## Migrating

Every exported name kept its spelling, and `ica.method` is still `"amica"`. Migration is one line:

```python
from amica import Amica, AmicaConfig    # 0.1.0 and earlier
from jamica import Amica, AmicaConfig   # 0.2.0 onward
```

## Note on `import amica`

This release intentionally ships no `amica` module, so `import amica` will not resolve to this package — that namespace is left to `amica-python`. If you upgraded from 0.1.0 and your code does `import amica`, change the import to `jamica` as shown above.

Versions 0.0.1 and 0.1.0 remain on PyPI unchanged if you need to pin the historical package.

- Source: <https://github.com/snesmaeili/jamica>
- Documentation: <https://snesmaeili.github.io/jamica/>
