easyscience 2.4.0__tar.gz → 3.0.2__tar.gz

{easyscience-2.4.0 → easyscience-3.0.2}/.copier-answers.yml

@@ -3,7 +3,7 @@
 _commit: v0.13.1
 _src_path: gh:easyscience/templates
 lib_docs_url: https://easyscience.github.io/core
-lib_doi: 10.5281/zenodo.18163581
+lib_doi: 10.5281/zenodo.19918609
 lib_package_name: easyscience
 lib_python_max: '3.14'
 lib_python_min: '3.11'

easyscience-3.0.2/.github/workflows/pypi-publish-check.yml

@@ -0,0 +1,77 @@
+# Dry run of the PyPI publishing workflow (see pypi-publish.yml).
+# Performs the same setup and build steps on a simulated release tag, but
+# never uploads anything. It fails if:
+# - pixi.lock is out of date for the pixi version used on GitHub runners
+#   (pixi commands without --frozen would rewrite it, e.g. the shell-hook
+#   run by setup-pixi to activate the environment)
+# - any tracked file is modified before the build, which gives
+#   versioningit a '+dirty' local version that PyPI rejects
+# - the built package has a local version or fails 'twine check'
+
+name: PyPI publishing check
+
+on:
+  pull_request:
+    branches: [master, develop]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  pypi-publish-check:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Check-out repository
+        uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+
+      # Same setup as in pypi-publish.yml, so any pixi.lock rewrite done by
+      # setup-pixi itself is reproduced here
+      - name: Set up pixi
+        uses: ./.github/actions/setup-pixi
+
+      # setup-pixi may already have rewritten pixi.lock, so compare it with
+      # the committed version as well as running 'pixi lock --check'
+      - name: Check pixi.lock is up to date
+        run: |
+          pixi --version
+          if ! git diff --quiet -- pixi.lock || ! pixi lock --check; then
+            git diff --stat -- pixi.lock
+            echo "::error file=pixi.lock::pixi.lock is out of date for $(pixi --version). Update pixi locally (pixi self-update), run 'pixi lock' and commit pixi.lock."
+            exit 1
+          fi
+
+      - name: Check working tree is clean
+        run: |
+          if [ -n "$(git status --porcelain --untracked-files=no)" ]; then
+            echo "::error::Tracked files were modified before the build, so the package version would get a '+dirty' suffix:"
+            git status --porcelain --untracked-files=no
+            git diff --stat
+            exit 1
+          fi
+
+      - name: Simulate release tag
+        run: git tag v9999.0.0
+
+      - name: Create Python package
+        run: pixi run --frozen default-build
+
+      - name: Check package version
+        run: |
+          ls -l dist/
+          for f in dist/*; do
+            if [[ "$(basename "$f")" == *+* ]]; then
+              echo "::error::$(basename "$f") has a local version, which PyPI rejects."
+              exit 1
+            fi
+          done
+
+      - name: Check package metadata
+        run: pipx run twine check --strict dist/*

{easyscience-2.4.0 → easyscience-3.0.2}/.github/workflows/pypi-publish.yml

@@ -28,8 +28,10 @@ jobs:
         uses: ./.github/actions/setup-pixi
 
       # Build the Python package (to dist/ folder)
+      # --frozen stops pixi from rewriting pixi.lock, which would make the
+      # tree dirty and give versioningit a '+dirty' version PyPI rejects
       - name: Create Python package
-        run: pixi run default-build
+        run: pixi run --frozen default-build
 
       # Publish the package to PyPI (from dist/ folder)
       # Instead of publishing with personal access token, we use

{easyscience-2.4.0 → easyscience-3.0.2}/.github/workflows/pypi-test.yml

@@ -69,10 +69,6 @@ jobs:
         working-directory: easyscience
         run: pixi run python -m pytest ../tests/unit/ --color=yes -v
 
-      - name: Run functional tests to verify the installation
-        working-directory: easyscience
-        run: pixi run python -m pytest ../tests/functional/ --color=yes -v
-
       - name: Run integration tests to verify the installation
         working-directory: easyscience
         run: pixi run python -m pytest ../tests/integration/ --color=yes -n auto

{easyscience-2.4.0 → easyscience-3.0.2}/.github/workflows/test.yml

@@ -102,21 +102,6 @@ jobs:
             pixi run --environment $env unit-tests
           done
 
-      - name: Run functional tests
-        shell: bash
-        run: |
-          set -euo pipefail
-
-          for py_ver in $PY_VERSIONS; do
-            echo
-            echo "🔹🔸🔹🔸🔹 Python: $py_ver 🔹🔸🔹🔸🔹"
-
-            env="py-$(echo $py_ver | tr -d .)-env" # Converts 3.XX -> py-3XX-env
-
-            echo "Running tests in environment: $env"
-            pixi run --environment $env functional-tests
-          done
-
       - name: Run integration tests ${{ needs.env-prepare.outputs.pytest-marks }}
         shell: bash
         run: |
@@ -258,25 +243,6 @@ jobs:
             cd ..
           done
 
-      - name: Run functional tests
-        shell: bash
-        run: |
-          set -euo pipefail
-
-          for py_ver in $PY_VERSIONS; do
-            echo
-            echo "🔹🔸🔹🔸🔹 Python: $py_ver 🔹🔸🔹🔸🔹"
-
-            echo "Entering pixi project directory easyscience_py$py_ver"
-            cd easyscience_py$py_ver
-
-            echo "Running tests"
-            pixi run python -m pytest ../tests/functional/ --color=yes -v
-
-            echo "Exiting pixi project directory"
-            cd ..
-          done
-
       - name: Run integration tests ${{ needs.env-prepare.outputs.pytest-marks }}
         shell: bash
         run: |

{easyscience-2.4.0 → easyscience-3.0.2}/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.4
+Metadata-Version: 2.5
 Name: easyscience
-Version: 2.4.0
+Version: 3.0.2
 Summary: Core building blocks for EasyScience
 Project-URL: Documentation, https://easyscience.github.io/core
 Project-URL: Release Notes, https://github.com/easyscience/core/releases
@@ -21,7 +21,7 @@ Classifier: Programming Language :: Python :: 3.14
 Classifier: Topic :: Scientific/Engineering
 Requires-Python: >=3.11
 Requires-Dist: asteval
-Requires-Dist: bumps
+Requires-Dist: bumps>=1.0.4
 Requires-Dist: dfo-ls
 Requires-Dist: lmfit
 Requires-Dist: numpy

{easyscience-2.4.0 → easyscience-3.0.2}/docs/docs/api-reference/index.md

@@ -8,19 +8,16 @@ This section contains the reference detailing the functions and modules
 available in EasyScience.
 
 - [base_classes](base_classes.md) – Core abstract and helper base
-  classes used to build EasyScience objects (e.g. `ObjBase`,
-  `ModelBase`).
-- [fitting](fitting.md) – Fitting utilities and interfaces, including
-  `Fitter` and available minimizers.
+  classes used to build EasyScience objects (e.g. `EasyBase`,
+  `ModelBase`, `EasyList`, `SerializerBase`).
+- [fitting](fitting.md) – Fitting and sampling, including `Fitter`,
+  `Sampler` and the available minimizers.
 - [global_object](global_object.md) – Global singleton providing shared
-  services (logger, map, undo/redo stack, script manager).
-- [io](io.md) – Serialization and deserialization framework for
-  persisting EasyScience objects (serializers and components).
+  services (logger and object registry).
 - [job](job.md) – Job and experiment abstractions for running and
   organizing analyses.
-- [models](models.md) – Predefined model implementations (e.g.
-  polynomial models) used in fitting workflows.
 - [utils](utils.md) – Miscellaneous utility functions and helpers (class
   tools, decorators, type helpers).
 - [variable](variable.md) – Descriptor types and variable abstractions
-  (e.g. `DescriptorNumber`, `Parameter`, `DescriptorArray`).
+  (e.g. `DescriptorNumber`, `Parameter`, `DescriptorArray`). All of them
+  are `EasyBase` objects, serialized with `to_dict`/`from_dict`.

{easyscience-2.4.0 → easyscience-3.0.2}/docs/docs/introduction/index.md

@@ -41,7 +41,7 @@ Zenodo, each with a version-specific Digital Object Identifier (DOI).
 
 Citation details in various styles (e.g., APA, MLA) and formats (e.g.,
 BibTeX, JSON) are available on the
-[Zenodo archive page](https://doi.org/10.5281/zenodo.18163581).
+[Zenodo archive page](https://doi.org/10.5281/zenodo.19918609).
 
 ## Contributing