ipaapi 1.0.0__tar.gz → 1.2.0__tar.gz

{ipaapi-1.0.0 → ipaapi-1.2.0}/CHANGELOG.md

@@ -7,6 +7,105 @@ minor, fixes bump the patch.
 Check what you're running with `ipaapi --version`, which reports the version,
 the install location, and whether it's an editable checkout rather than a wheel.
 
+## 1.2.0 — 2026-08-24
+
+### Fixed
+
+- **Long observation names are shortened automatically.** IPA rejects an
+  observation name past roughly 65 characters and reports it as *"The page you
+  are looking for is currently unavailable"* — the same page it returns for a
+  duplicate dataset name, and for a genuine outage. Because the observation
+  name defaults to the filename, descriptive pipeline output names tripped it,
+  and a batch died on its first file looking like a total service failure.
+
+  Established by A/B on one file, holding project, reference set and data
+  constant: a 25-character observation name with an 82-character dataset name
+  was accepted (it reached IPA's allowance check); a 25-character *dataset*
+  name with an 82-character observation name was rejected. So the limit is
+  specific to the observation — a long dataset name is fine.
+
+  Names are now brought under 60 characters automatically, removing what
+  carries the least meaning first. Two parts of a pipeline filename matter —
+  the contrast (`Estrus_vs_2dpp`) and the cell type the comparison came from
+  (`Immature_cortical_ovarian_stroma`) — and everything appended about how the
+  pipeline ran does not.
+
+  Paralome output is cut on its own structure rather than by heuristic. It
+  names files
+  `<contrast>_<celltype>_<method>_<test>_significant_<threshold>_<assay>`, so
+  the `significant` literal anchors the cut exactly: drop it and everything
+  after, drop the test immediately before it, drop the aggregation method. No
+  list of test names is needed — the test is whatever token precedes the
+  anchor, so `wilcox` works as well as `t`. Methods are matched as whole
+  phrases in that one position only, since a cell type of `Naive_T_cell`
+  shares both words with the `naive_cell` method.
+
+  Files from anything else fall back to generic metadata removal, then any
+  suffix the batch shares, then the shared prefix, and only as a last resort a
+  two-ended cut marked with `..`.
+
+  Comparison is token by token, so `Mature` is never read as a prefix of
+  `Immature` and `cell_type` is never left as `cell_t`. Any step is abandoned
+  if it would make two names identical or leave one unreadable, since
+  observation names are what IPA lists side by side in a comparison analysis.
+  Names already within the limit are untouched, and the dataset and analysis
+  always keep the full filename.
+
+- Rejection guidance now names the observation length first, since it is the
+  cause hardest to guess from what IPA returns.
+
+### Added
+
+- **`--strip TEXT`**, repeatable, removes text from observation names before
+  shortening — for a pipeline whose suffix the built-in list does not cover.
+  Ignored as a whole if applying it would leave the names empty, unreadable, or
+  no longer distinct.
+
+### Notes
+
+- This is a *second*, independent cause of the same misleading page — 1.1.0
+  fixed duplicate dataset names. Having already attributed that page once made
+  this one harder to see, not easier. If a batch dies on its first file with
+  that wording, both causes are worth ruling out.
+
+## 1.1.0 — 2026-08-05
+
+### Added
+
+- **Duplicate dataset names are detected before submitting.** IPA refuses a
+  dataset whose name already exists in a project, and reports it as *"The page
+  you are looking for is currently unavailable"* — wording that reads as an
+  outage. Because dataset names come from filenames, re-running a batch retried
+  names an earlier run had created, so the run died on its first file and
+  looked like a total service failure. It cost a day to find.
+
+  Established by experiment: the identical 2 KB request succeeded and then
+  failed twice; with unique dataset names three consecutive submissions all
+  succeeded. Not size, not rate limiting, not parameters, not an outage.
+
+  `submit` now checks the submission log for that project and dataset name
+  first, skips the file with an explanation, and files it under `submitted/`.
+  `--force` overrides.
+
+### Notes
+
+- The guard covers submissions made through this tool with the same log file.
+  A collision caused by another user or the IPA client still surfaces as the
+  misleading outage page; the troubleshooting table now says so.
+
+## 1.0.1 — 2026-08-05
+
+### Fixed
+
+- **An IPA outage is no longer reported as a bad parameter.** IPA's maintenance
+  page ("currently unavailable", "experiencing technical difficulties", "try
+  again later") is HTML, so it fell through to `MalformedRequestError` and the
+  message told the user to check `--reference-set` and `--ID` — sending them to
+  rewrite a command that was correct. New `ServiceUnavailableError`, also
+  raised on 502/503/504, says plainly that IPA is down, that nothing about the
+  command needs changing, and that re-running later resumes. Files are left in
+  place, as before.
+
 ## 1.0.0 — 2026-08-05
 
 First stable release. No code changes from 0.5.0 — the version marks that the

{ipaapi-1.0.0 → ipaapi-1.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: ipaapi
-Version: 1.0.0
+Version: 1.2.0
 Summary: Command-line client for QIAGEN Ingenuity Pathway Analysis: map arbitrary column layouts, submit datasets in bulk, and resume cleanly when the analysis allowance runs out.
 Author-email: Ken Jones <Ken.Jones@bioinformaticsolutions.com>
 License: MIT License
@@ -251,7 +251,8 @@ Used by `validate` and `submit`.
 | `--sep` | `CHAR` | field delimiter (sniffed from the header line by default) |
 | `--pattern` | `TEXT` | when PATH is a directory: substring or glob selecting files |
 | `--recursive` | flag | search subdirectories too |
-| `--observation` | `NAME` | observation name in IPA (default: the filename). Single file only |
+| `--observation` | `NAME` | observation name in IPA (default: the filename). Single file only. Shortened to 60 characters if needed — see [long observation names](#long-observation-names) |
+| `--strip` | `TEXT` | remove TEXT from observation names before shortening. Repeatable |
 | `--no-range-check` | flag | skip the value-range validation |
 | `--list-id-types` | flag | print all 33 gene ID types and exit |
 
@@ -443,6 +444,147 @@ A type outside the documented list produces a warning with a near-match
 suggestion but is still sent, since IPA is the authority and the list will age.
 An unrecognised value fails before anything is uploaded, and IPA names it.
 
+### Duplicate dataset names
+
+**IPA refuses to create a dataset whose name already exists in a project — and
+reports it as "The page you are looking for is currently unavailable."** The
+wording says outage; the cause is a name collision. This is the single most
+misleading response the API produces, and it cost a full day to identify.
+
+Verified: the same 2 KB request, byte for byte, succeeded and then failed twice
+in a row. With unique dataset names, three consecutive submissions all
+succeeded.
+
+Since dataset names come from filenames, re-running a batch retries names an
+earlier run already created — so the run dies on its *first* file and looks
+like a total outage.
+
+The package prevents this using the submission log. Before uploading, it checks
+whether that dataset name already went to that project:
+
+```
+skipping SampleA_DEG: already submitted to 'Study1' on 2026-08-05T08:35:53-06:00
+as analysis 43595039. IPA would reject a second dataset of the same name.
+Use --force to submit it again anyway.
+```
+
+Skipped files are filed under `submitted/`, because they are. `--force`
+overrides, though IPA will normally reject it.
+
+The guard only knows about submissions made through this tool with the same log
+file. If you hit the collision anyway — a colleague's upload, or the IPA client
+— the fix is a different `--project`, a different `--dataset-name`, or deleting
+the existing dataset in IPA.
+
+### Long observation names
+
+**IPA rejects a long observation name, and reports it as "The page you are
+looking for is currently unavailable."** The same misleading page as a
+duplicate dataset name, from an entirely unrelated cause — which is what made
+this one expensive to find: the obvious explanation had already been used up.
+
+The observation name defaults to the filename, so descriptive pipeline output
+names run past the limit without anyone choosing a long name. A long *dataset*
+name is fine; only the observation is affected.
+
+Established by A/B on one file, holding project, reference set and data
+constant:
+
+| dataset name | observation name | result |
+| --- | --- | --- |
+| short (25) | **long (82)** | rejected as an "outage" |
+| **long (82)** | short (25) | accepted — reached IPA's allowance check |
+
+65 characters is known good and 82 known bad; the exact limit is undocumented.
+Since 1.2.0 the observation name is brought under 60 characters automatically.
+
+**What gets removed is chosen by what it means, not by where it sits.** Two
+parts of a Paralome filename carry information: the contrast (`Estrus_vs_2dpp`)
+and the cell type the comparison was computed from
+(`Immature_cortical_ovarian_stroma`). Everything the pipeline appends about how
+it ran — `_naive_cell_t_significant_p0.05_rna`, `_pseudobulk_t_significant_p0.05_rna` —
+is disposable. So that is what goes first:
+
+```
+Estrus_vs_2dpp_Immature_cortical_ovarian_stroma_naive_cell_t_significant_p0.05_rna
+ -> Estrus_vs_2dpp_Immature_cortical_ovarian_stroma
+
+Estrus_vs_2dpp_Glandular_epithelium_pseudobulk_t_significant_p0.05_rna
+ -> Estrus_vs_2dpp_Glandular_epithelium
+```
+
+**Paralome output is cut on its own structure, not by guesswork.** Paralome
+names its files
+`<contrast>_<celltype>_<method>_<test>_significant_<threshold>_<assay>`, and
+the `significant` literal is a reliable anchor:
+
+```
+Estrus_vs_2dpp_Immature_cortical_ovarian_stroma | naive_cell | t | significant_p0.05_rna
+Estrus_vs_2dpp_Glandular_epithelium             | pseudobulk | t | significant_p0.05_rna
+```
+
+Working backwards from the anchor: drop it and everything after, drop the
+statistical test immediately before it, then drop the aggregation method. The
+test needs no list of names — it is simply the token before the anchor, so
+`wilcox` works as well as `t` without anyone maintaining a vocabulary. Methods
+are matched as **whole phrases in that one position only**, because a cell type
+of `Naive_T_cell` shares both words with the `naive_cell` method and loose
+matching cut it to `Naive_T`.
+
+Removal is graded, least damaging first, and stops as soon as the names fit:
+
+1. anything named with `--strip`
+2. the Paralome tail, cut at its anchor as above
+3. trailing pipeline metadata, for files from anything else — tokens like
+   `significant`, `deseq2`, `filtered`, and cutoffs in any of the shapes
+   `p0.05`, `fdr0.01`, `padj0.05`, `0.05`, read right to left and stopping at
+   the first token that isn't recognisable as a setting
+4. the suffix every file in the batch happens to share
+5. the prefix every file shares — this costs the contrast, so it is late
+6. a two-ended cut with `..` marking the gap, on a token boundary
+
+Steps 2 to 4 always run together rather than stopping the moment the names
+merely fit, since half a removed suffix reads worse than either whole. Comparison
+is **whole tokens at a time**, so `Mature` is never treated as a prefix of
+`Immature` and `cell_type` is never left as `cell_t`. Names already within the
+limit are returned untouched.
+
+Any step is abandoned if it would make two names identical, or leave one under
+four characters or without a letter — reducing files to `1` and `2` keeps them
+distinct and makes the analysis unreadable. Distinctness is the property being
+protected: observation names are what IPA lists side by side in a comparison
+analysis, so two files reduced to the same label would be worse than a long name.
+
+Everything removed is printed:
+
+```
+note: shortened 2 observation names. IPA rejects a long observation name and
+reports it as an outage, so this is not optional.
+      Datasets and analyses keep the full filename; only the observation label
+      inside the analysis is shorter.
+      Estrus_vs_2dpp_Glandular_epithelium_pseudobulk_t_significant_p0.05_rna
+   -> Estrus_vs_2dpp_Glandular_epithelium
+```
+
+If your pipeline's suffix is not recognised, name it explicitly. `--strip` is
+repeatable, applied before anything else, and ignored as a whole if it would
+leave the names unusable:
+
+```bash
+ipaapi submit ~/data --ID 1:mousesymeg --FC 4:foldchange --skip-rows 1 \
+    --project Study --strip _significant_p0.05_rna
+```
+
+Because steps 4 and 5 depend on the other files in the run, **the same file
+submitted in a different batch can get a different observation label**. Steps 1 to 3
+do not — they read only the name in front of them, which is why a
+single-file submit shortens as well as a batch does. The dataset and analysis
+always keep the full filename, so `ipaapi history` and the IPA project view are
+unaffected.
+
+`--observation` sets the name explicitly for a single file and is shortened the
+same way if it needs to be.
+
 ### The reference set
 
 The background enrichment is scored against — the denominator of the Fisher's
@@ -525,6 +667,7 @@ boilerplate and the page footer, and classifies what's left:
 | `Unknown GeneId Type (X)` | `MalformedRequestError` | stops; names the flag; moves nothing |
 | `Unable to run analysis: Analysis limit exceeded` | `QuotaExceededError` | stops; leaves remaining files for the next run |
 | `Unable to run analysis: …` (other) | `AnalysisRefusedError` | as above — reached the analysis logic, so not a parameter fault |
+| `currently unavailable` / `technical difficulties`, or 502/503/504 | `ServiceUnavailableError` | IPA is down; stops, moves nothing, says the command is fine |
 | anything else | `SubmissionError` | files that one under `failed/` |
 
 Quota matching is deliberately broad (`ipaapi.client.QUOTA_PATTERNS` plus HTTP
@@ -691,6 +834,10 @@ cp, ur, df = results                  # unpacks like the demo's ipa_results()
 | `--FC refers to column N, but the file has only M column(s)` | 1-based counting, or wrong `--skip-rows` | positions are 0-based, from the header |
 | `Every row is missing an identifier` | wrong column, or no header | check with `head -1 file \| tr '\t' '\n' \| nl -v0` |
 | `the analysis allowance appears to be exhausted` | daily/period limit | re-run later; files left in place resume |
+| `IPA appears to be down or having trouble` | IPA outage — **or a duplicate dataset name, or a long observation name**, all reported identically | `ipaapi --version` (1.2.0+ handles the name length); check `ipaapi history --project X` for the dataset name; otherwise wait |
+| Batch dies on the first file, names come from long filenames | observation name too long | upgrade to 1.2.0+, or pass a short `--observation` |
+| Batch dies on the *first* file after an earlier run | dataset names already exist in the project | expected — 1.1.0 skips them automatically; before that, use a new `--project` |
+| `Cannot listen on 127.0.0.1:8000` | stale login process, or another user mid-login | `ss -ltnp 'sport = :8000'`, then kill it if it's yours |
 | Login prompt on every run | token cache not writable | `export IPAAPI_TOKEN_FILE=...`; check for a root-owned cache |
 | `Could not open a browser automatically` | headless | `ssh -X`, or copy a token across |
 | `report` returns HTTP 500 on a succeeded analysis | unconfirmed; possibly add-on licence | open the analysis in IPA; see `examples/probe_interpret.py` |

{ipaapi-1.0.0 → ipaapi-1.2.0}/README.md

@@ -202,7 +202,8 @@ Used by `validate` and `submit`.
 | `--sep` | `CHAR` | field delimiter (sniffed from the header line by default) |
 | `--pattern` | `TEXT` | when PATH is a directory: substring or glob selecting files |
 | `--recursive` | flag | search subdirectories too |
-| `--observation` | `NAME` | observation name in IPA (default: the filename). Single file only |
+| `--observation` | `NAME` | observation name in IPA (default: the filename). Single file only. Shortened to 60 characters if needed — see [long observation names](#long-observation-names) |
+| `--strip` | `TEXT` | remove TEXT from observation names before shortening. Repeatable |
 | `--no-range-check` | flag | skip the value-range validation |
 | `--list-id-types` | flag | print all 33 gene ID types and exit |
 
@@ -394,6 +395,147 @@ A type outside the documented list produces a warning with a near-match
 suggestion but is still sent, since IPA is the authority and the list will age.
 An unrecognised value fails before anything is uploaded, and IPA names it.
 
+### Duplicate dataset names
+
+**IPA refuses to create a dataset whose name already exists in a project — and
+reports it as "The page you are looking for is currently unavailable."** The
+wording says outage; the cause is a name collision. This is the single most
+misleading response the API produces, and it cost a full day to identify.
+
+Verified: the same 2 KB request, byte for byte, succeeded and then failed twice
+in a row. With unique dataset names, three consecutive submissions all
+succeeded.
+
+Since dataset names come from filenames, re-running a batch retries names an
+earlier run already created — so the run dies on its *first* file and looks
+like a total outage.
+
+The package prevents this using the submission log. Before uploading, it checks
+whether that dataset name already went to that project:
+
+```
+skipping SampleA_DEG: already submitted to 'Study1' on 2026-08-05T08:35:53-06:00
+as analysis 43595039. IPA would reject a second dataset of the same name.
+Use --force to submit it again anyway.
+```
+
+Skipped files are filed under `submitted/`, because they are. `--force`
+overrides, though IPA will normally reject it.
+
+The guard only knows about submissions made through this tool with the same log
+file. If you hit the collision anyway — a colleague's upload, or the IPA client
+— the fix is a different `--project`, a different `--dataset-name`, or deleting
+the existing dataset in IPA.
+
+### Long observation names
+
+**IPA rejects a long observation name, and reports it as "The page you are
+looking for is currently unavailable."** The same misleading page as a
+duplicate dataset name, from an entirely unrelated cause — which is what made
+this one expensive to find: the obvious explanation had already been used up.
+
+The observation name defaults to the filename, so descriptive pipeline output
+names run past the limit without anyone choosing a long name. A long *dataset*
+name is fine; only the observation is affected.
+
+Established by A/B on one file, holding project, reference set and data
+constant:
+
+| dataset name | observation name | result |
+| --- | --- | --- |
+| short (25) | **long (82)** | rejected as an "outage" |
+| **long (82)** | short (25) | accepted — reached IPA's allowance check |
+
+65 characters is known good and 82 known bad; the exact limit is undocumented.
+Since 1.2.0 the observation name is brought under 60 characters automatically.
+
+**What gets removed is chosen by what it means, not by where it sits.** Two
+parts of a Paralome filename carry information: the contrast (`Estrus_vs_2dpp`)
+and the cell type the comparison was computed from
+(`Immature_cortical_ovarian_stroma`). Everything the pipeline appends about how
+it ran — `_naive_cell_t_significant_p0.05_rna`, `_pseudobulk_t_significant_p0.05_rna` —
+is disposable. So that is what goes first:
+
+```
+Estrus_vs_2dpp_Immature_cortical_ovarian_stroma_naive_cell_t_significant_p0.05_rna
+ -> Estrus_vs_2dpp_Immature_cortical_ovarian_stroma
+
+Estrus_vs_2dpp_Glandular_epithelium_pseudobulk_t_significant_p0.05_rna
+ -> Estrus_vs_2dpp_Glandular_epithelium
+```
+
+**Paralome output is cut on its own structure, not by guesswork.** Paralome
+names its files
+`<contrast>_<celltype>_<method>_<test>_significant_<threshold>_<assay>`, and
+the `significant` literal is a reliable anchor:
+
+```
+Estrus_vs_2dpp_Immature_cortical_ovarian_stroma | naive_cell | t | significant_p0.05_rna
+Estrus_vs_2dpp_Glandular_epithelium             | pseudobulk | t | significant_p0.05_rna
+```
+
+Working backwards from the anchor: drop it and everything after, drop the
+statistical test immediately before it, then drop the aggregation method. The
+test needs no list of names — it is simply the token before the anchor, so
+`wilcox` works as well as `t` without anyone maintaining a vocabulary. Methods
+are matched as **whole phrases in that one position only**, because a cell type
+of `Naive_T_cell` shares both words with the `naive_cell` method and loose
+matching cut it to `Naive_T`.
+
+Removal is graded, least damaging first, and stops as soon as the names fit:
+
+1. anything named with `--strip`
+2. the Paralome tail, cut at its anchor as above
+3. trailing pipeline metadata, for files from anything else — tokens like
+   `significant`, `deseq2`, `filtered`, and cutoffs in any of the shapes
+   `p0.05`, `fdr0.01`, `padj0.05`, `0.05`, read right to left and stopping at
+   the first token that isn't recognisable as a setting
+4. the suffix every file in the batch happens to share
+5. the prefix every file shares — this costs the contrast, so it is late
+6. a two-ended cut with `..` marking the gap, on a token boundary
+
+Steps 2 to 4 always run together rather than stopping the moment the names
+merely fit, since half a removed suffix reads worse than either whole. Comparison
+is **whole tokens at a time**, so `Mature` is never treated as a prefix of
+`Immature` and `cell_type` is never left as `cell_t`. Names already within the
+limit are returned untouched.
+
+Any step is abandoned if it would make two names identical, or leave one under
+four characters or without a letter — reducing files to `1` and `2` keeps them
+distinct and makes the analysis unreadable. Distinctness is the property being
+protected: observation names are what IPA lists side by side in a comparison
+analysis, so two files reduced to the same label would be worse than a long name.
+
+Everything removed is printed:
+
+```
+note: shortened 2 observation names. IPA rejects a long observation name and
+reports it as an outage, so this is not optional.
+      Datasets and analyses keep the full filename; only the observation label
+      inside the analysis is shorter.
+      Estrus_vs_2dpp_Glandular_epithelium_pseudobulk_t_significant_p0.05_rna
+   -> Estrus_vs_2dpp_Glandular_epithelium
+```
+
+If your pipeline's suffix is not recognised, name it explicitly. `--strip` is
+repeatable, applied before anything else, and ignored as a whole if it would
+leave the names unusable:
+
+```bash
+ipaapi submit ~/data --ID 1:mousesymeg --FC 4:foldchange --skip-rows 1 \
+    --project Study --strip _significant_p0.05_rna
+```
+
+Because steps 4 and 5 depend on the other files in the run, **the same file
+submitted in a different batch can get a different observation label**. Steps 1 to 3
+do not — they read only the name in front of them, which is why a
+single-file submit shortens as well as a batch does. The dataset and analysis
+always keep the full filename, so `ipaapi history` and the IPA project view are
+unaffected.
+
+`--observation` sets the name explicitly for a single file and is shortened the
+same way if it needs to be.
+
 ### The reference set
 
 The background enrichment is scored against — the denominator of the Fisher's
@@ -476,6 +618,7 @@ boilerplate and the page footer, and classifies what's left:
 | `Unknown GeneId Type (X)` | `MalformedRequestError` | stops; names the flag; moves nothing |
 | `Unable to run analysis: Analysis limit exceeded` | `QuotaExceededError` | stops; leaves remaining files for the next run |
 | `Unable to run analysis: …` (other) | `AnalysisRefusedError` | as above — reached the analysis logic, so not a parameter fault |
+| `currently unavailable` / `technical difficulties`, or 502/503/504 | `ServiceUnavailableError` | IPA is down; stops, moves nothing, says the command is fine |
 | anything else | `SubmissionError` | files that one under `failed/` |
 
 Quota matching is deliberately broad (`ipaapi.client.QUOTA_PATTERNS` plus HTTP
@@ -642,6 +785,10 @@ cp, ur, df = results                  # unpacks like the demo's ipa_results()
 | `--FC refers to column N, but the file has only M column(s)` | 1-based counting, or wrong `--skip-rows` | positions are 0-based, from the header |
 | `Every row is missing an identifier` | wrong column, or no header | check with `head -1 file \| tr '\t' '\n' \| nl -v0` |
 | `the analysis allowance appears to be exhausted` | daily/period limit | re-run later; files left in place resume |
+| `IPA appears to be down or having trouble` | IPA outage — **or a duplicate dataset name, or a long observation name**, all reported identically | `ipaapi --version` (1.2.0+ handles the name length); check `ipaapi history --project X` for the dataset name; otherwise wait |
+| Batch dies on the first file, names come from long filenames | observation name too long | upgrade to 1.2.0+, or pass a short `--observation` |
+| Batch dies on the *first* file after an earlier run | dataset names already exist in the project | expected — 1.1.0 skips them automatically; before that, use a new `--project` |
+| `Cannot listen on 127.0.0.1:8000` | stale login process, or another user mid-login | `ss -ltnp 'sport = :8000'`, then kill it if it's yours |
 | Login prompt on every run | token cache not writable | `export IPAAPI_TOKEN_FILE=...`; check for a root-owned cache |
 | `Could not open a browser automatically` | headless | `ssh -X`, or copy a token across |
 | `report` returns HTTP 500 on a succeeded analysis | unconfirmed; possibly add-on licence | open the analysis in IPA; see `examples/probe_interpret.py` |

{ipaapi-1.0.0 → ipaapi-1.2.0}/src/ipaapi/__init__.py

@@ -56,7 +56,7 @@ from .models import GENE_ID_TYPES, AnalysisStatus, MeasurementType, ReferenceSet
 
 #: Single source of truth for the package version; pyproject.toml reads it from
 #: here at build time. Bump it in this file and nowhere else.
-__version__ = "1.0.0"
+__version__ = "1.2.0"
 
 __all__ = [
     "__version__",