From 478a69d795eb30277c7405b86766e06d6cb61294 Mon Sep 17 00:00:00 2001 From: hejamu Date: Thu, 29 Oct 2026 01:37:01 +0100 Subject: [PATCH 01/10] Require maicos 0.13 and drop the mdacli pin --- CHANGELOG.rst | 5 +++++ pyproject.toml | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.rst b/CHANGELOG.rst index 7add0f2..1c74603 100644 --- a/CHANGELOG.rst +++ b/CHANGELOG.rst @@ -11,6 +11,11 @@ The rules for spectrumkit's CHANGELOG file: .. inclusion-marker-changelog-start +Unreleased +---------- + +- Require ``maicos>=0.13``, drop the ``mdacli<=0.1.35`` pin. (#20) + v0.1.0 (2026/05/20) ------------------- diff --git a/pyproject.toml b/pyproject.toml index 5f9cd14..219fd43 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -38,7 +38,7 @@ classifiers = [ "Topic :: Scientific/Engineering :: Physics", "Topic :: Software Development :: Libraries :: Python Modules", ] -dependencies = ["maicos>=0.11.2", "mdacli<=0.1.35"] +dependencies = ["maicos>=0.13"] dynamic = ["version"] [project.optional-dependencies] From f00ec0dbbf1494ed3795410932f70ad7a9c74988 Mon Sep 17 00:00:00 2001 From: hejamu Date: Thu, 29 Oct 2026 01:43:03 +0100 Subject: [PATCH 02/10] Treat warnings as errors in tests, test binning with binafter=0 (2 tests fail) --- CHANGELOG.rst | 1 + pyproject.toml | 2 +- tests/tests.py | 17 +++++++++++++++++ 3 files changed, 19 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.rst b/CHANGELOG.rst index 1c74603..31ce2ab 100644 --- a/CHANGELOG.rst +++ b/CHANGELOG.rst @@ -14,6 +14,7 @@ The rules for spectrumkit's CHANGELOG file: Unreleased ---------- +- Treat all warnings as errors in tests. - Require ``maicos>=0.13``, drop the ``mdacli<=0.1.35`` pin. (#20) v0.1.0 (2026/05/20) diff --git a/pyproject.toml b/pyproject.toml index 219fd43..9ca36d8 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -68,12 +68,12 @@ show_missing = true [tool.pytest.ini_options] testpaths = "tests" python_files = ["test_*.py", "*_test.py", "tests.py"] +filterwarnings = ["error"] addopts = [ "--cov", "--cov-append", "--cov-report=", "--import-mode=append", - "--disable-warnings", ] [tool.ruff] diff --git a/tests/tests.py b/tests/tests.py index acaf8dc..4ac43aa 100644 --- a/tests/tests.py +++ b/tests/tests.py @@ -134,6 +134,23 @@ def test_basic_calculation(self): assert results["susc"].dtype == complex assert results["dsusc"].dtype == complex + def test_binning_without_unbinned_points(self): + """Test logarithmic binning when no low-frequency points stay unbinned.""" + rng = np.random.default_rng(0) + results = calculate_spectrum_from_dipole( + dipole_moment=rng.standard_normal((1000, 3)), + dt=1.0, + volume=1000.0, + temperature=300.0, + segs=1, + bins=5, + binafter=0, + ) + + # the zero frequency stays on its own, the rest is binned logarithmically + assert results["nu_binned"][0] == results["nu"][0] + assert 1 < len(results["nu_binned"]) <= 6 + def test_consistency_with_dielectric_spectrum(self, monkeypatch, tmp_path): """Test that standalone function gives same results as class method.""" monkeypatch.chdir(tmp_path) From 3d91bc14ef7b3792483f9298f087e262f6f679bc Mon Sep 17 00:00:00 2001 From: hejamu Date: Thu, 29 Oct 2026 01:43:42 +0100 Subject: [PATCH 03/10] Fix logarithmic binning with binafter=0 --- CHANGELOG.rst | 2 ++ src/spectrumkit/dielectricspectrum.py | 12 ++++++++---- src/spectrumkit/lib/util.py | 2 +- 3 files changed, 11 insertions(+), 5 deletions(-) diff --git a/CHANGELOG.rst b/CHANGELOG.rst index 31ce2ab..a78b814 100644 --- a/CHANGELOG.rst +++ b/CHANGELOG.rst @@ -14,6 +14,8 @@ The rules for spectrumkit's CHANGELOG file: Unreleased ---------- +- Fix logarithmic binning with ``binafter=0``, which averaged the whole spectrum + into one bin. - Treat all warnings as errors in tests. - Require ``maicos>=0.13``, drop the ``mdacli<=0.1.35`` pin. (#20) diff --git a/src/spectrumkit/dielectricspectrum.py b/src/spectrumkit/dielectricspectrum.py index 9731636..0b2e623 100755 --- a/src/spectrumkit/dielectricspectrum.py +++ b/src/spectrumkit/dielectricspectrum.py @@ -183,12 +183,14 @@ def calculate_spectrum_from_dipole( # Bin data if there are too many points if not nobin and seglen > bins: + # the zero frequency always stays unbinned, the log spacing can't start at 0 + unbinned = max(binafter, 1) bin_indices = np.logspace( - np.log(binafter) / np.log(10), + np.log(unbinned) / np.log(10), np.log(len(susc)) / np.log(10), bins - binafter + 1, ).astype(int) - bin_indices = np.unique(np.append(np.arange(binafter), bin_indices))[:-1] + bin_indices = np.unique(np.append(np.arange(unbinned), bin_indices))[:-1] results["nu_binned"] = bin(nu, bin_indices) results["susc_binned"] = bin(susc, bin_indices) @@ -353,12 +355,14 @@ def calculate_spectrum_from_current( # Bin data if there are too many points if not nobin and seglen > bins: + # the zero frequency always stays unbinned, the log spacing can't start at 0 + unbinned = max(binafter, 1) bin_indices = np.logspace( - np.log(binafter) / np.log(10), + np.log(unbinned) / np.log(10), np.log(len(susc)) / np.log(10), bins - binafter + 1, ).astype(int) - bin_indices = np.unique(np.append(np.arange(binafter), bin_indices))[:-1] + bin_indices = np.unique(np.append(np.arange(unbinned), bin_indices))[:-1] results["nu_binned"] = bin(nu, bin_indices) results["susc_binned"] = bin(susc, bin_indices) diff --git a/src/spectrumkit/lib/util.py b/src/spectrumkit/lib/util.py index 46786ba..694722d 100644 --- a/src/spectrumkit/lib/util.py +++ b/src/spectrumkit/lib/util.py @@ -28,7 +28,7 @@ def bin(a: np.ndarray, bins: np.ndarray) -> np.ndarray: The "bins" array should contain the INDEX (integer) where each bin begins. """ - if np.iscomplex(a).any(): + if np.iscomplexobj(a): avg = np.zeros(len(bins), dtype=complex) # average of data else: avg = np.zeros(len(bins)) From e03df759b700b35b4195ebaab17b10249476176e Mon Sep 17 00:00:00 2001 From: hejamu Date: Thu, 29 Oct 2026 01:47:52 +0100 Subject: [PATCH 04/10] Test weekly against maicos main and the latest release, run doctests --- .github/workflows/tests-dev.yml | 58 +++++++++++++++++++++++++++++++++ CHANGELOG.rst | 2 ++ src/spectrumkit/lib/__init__.py | 16 +++++++++ tests/requirements.txt | 2 ++ tox.ini | 20 +++++++----- 5 files changed, 89 insertions(+), 9 deletions(-) create mode 100644 .github/workflows/tests-dev.yml create mode 100644 src/spectrumkit/lib/__init__.py create mode 100644 tests/requirements.txt diff --git a/.github/workflows/tests-dev.yml b/.github/workflows/tests-dev.yml new file mode 100644 index 0000000..9ec020a --- /dev/null +++ b/.github/workflows/tests-dev.yml @@ -0,0 +1,58 @@ +name: Tests dev + +on: + schedule: + # check once a week on mondays + - cron: '0 10 * * 1' + +jobs: + tests-dev: + runs-on: ubuntu-latest + strategy: + matrix: + python-version: ["3.11", "3.14"] + + steps: + - uses: actions/checkout@v7 + with: + fetch-depth: 0 + + - name: Set up Python ${{ matrix.python-version }} + uses: actions/setup-python@v7 + with: + python-version: ${{ matrix.python-version }} + + - name: Install tests dependencies + run: python -m pip install tox + + - name: Run tests against MAICoS dev version + run: tox -e tests-dev + + tests-release: + runs-on: ubuntu-latest + strategy: + matrix: + python-version: ["3.11", "3.14"] + + steps: + - uses: actions/checkout@v7 + with: + fetch-depth: 0 + + - name: Set up Python ${{ matrix.python-version }} + uses: actions/setup-python@v7 + with: + python-version: ${{ matrix.python-version }} + + # v0.1.0 predates tests/requirements.txt, so install them before the checkout + - name: Install released spectrumkit and test dependencies + run: | + python -m pip install spectrumkit + python -m pip install -r tests/requirements.txt + python -m pip list + + - name: Check out latest release tag + run: git checkout $(git describe --tags --abbrev=0) + + - name: Run tests against released versions + run: pytest diff --git a/CHANGELOG.rst b/CHANGELOG.rst index a78b814..9661aeb 100644 --- a/CHANGELOG.rst +++ b/CHANGELOG.rst @@ -14,6 +14,8 @@ The rules for spectrumkit's CHANGELOG file: Unreleased ---------- +- Test weekly against the MAICoS dev version and the latest release, run + doctests. - Fix logarithmic binning with ``binafter=0``, which averaged the whole spectrum into one bin. - Treat all warnings as errors in tests. diff --git a/src/spectrumkit/lib/__init__.py b/src/spectrumkit/lib/__init__.py new file mode 100644 index 0000000..177bcff --- /dev/null +++ b/src/spectrumkit/lib/__init__.py @@ -0,0 +1,16 @@ +# Copyright (c) 2025 Authors and contributors +# (see the AUTHORS.rst file for the full list of names) +# +# Released under the GNU Public Licence, v3 or any higher version +# SPDX-License-Identifier: GPL-3.0-or-later +"""Library modules of spectrumkit. + +This library contains general and mathematical helper functions, which are used in +the analysis modules. +""" + +__all__ = [ + "math", + "preprocessing", + "util", +] diff --git a/tests/requirements.txt b/tests/requirements.txt new file mode 100644 index 0000000..9955dec --- /dev/null +++ b/tests/requirements.txt @@ -0,0 +1,2 @@ +pytest +pytest-cov diff --git a/tox.ini b/tox.ini index 0f73e6a..e753a45 100644 --- a/tox.ini +++ b/tox.ini @@ -28,19 +28,21 @@ platform = [testenv:tests] description = Run test suite with pytest and {basepython}. usedevelop = true -deps = - coverage[toml] - hypothesis - pytest - pytest-cov - pytest-mock - setuptools +deps = -r tests/requirements.txt commands = # Run unit tests pytest {posargs} - # Run documentation tests on all Python files and the README.rst - ; pytest --doctest-modules --pyargs spectrumkit + # Run documentation tests on all Python files + pytest --doctest-modules --pyargs spectrumkit + +[testenv:tests-dev] +description = Run test suite against MAICoS dev version +deps = + -r tests/requirements.txt + maicos @ git+https://github.com/maicos-devel/maicos.git +commands = + pytest {posargs} [testenv:lint] description = Run linters and type checks From 81a6d7f4835440264f11af4e7aec1e599aaaa230 Mon Sep 17 00:00:00 2001 From: hejamu Date: Thu, 29 Oct 2026 01:48:08 +0100 Subject: [PATCH 05/10] Test on macOS and Windows, upload coverage to Codecov --- .codecov.yml | 12 ++++++++++++ .github/workflows/tests.yml | 34 ++++++++++++++++++++-------------- CHANGELOG.rst | 1 + pyproject.toml | 23 +++++++++++++++++++++++ 4 files changed, 56 insertions(+), 14 deletions(-) create mode 100644 .codecov.yml diff --git a/.codecov.yml b/.codecov.yml new file mode 100644 index 0000000..090fc45 --- /dev/null +++ b/.codecov.yml @@ -0,0 +1,12 @@ +coverage: + ignore: + - "examples/.*" + - "src/spectrumkit/_version.py" + - "tests/.*" + status: + project: + default: + target: auto + patch: false + +comment: false diff --git a/.github/workflows/tests.yml b/.github/workflows/tests.yml index 97ef7f7..00a9265 100644 --- a/.github/workflows/tests.yml +++ b/.github/workflows/tests.yml @@ -11,13 +11,19 @@ on: jobs: tests: - runs-on: ubuntu-24.04 - name: Python ${{ matrix.python-version }} + runs-on: ${{ matrix.os }} + name: ${{ matrix.os }} / Python ${{ matrix.python-version }} strategy: matrix: - python-version: - - "3.11" - - "3.14" + include: + - os: ubuntu-latest + python-version: "3.11" + - os: ubuntu-latest + python-version: "3.14" + - os: macos-latest + python-version: "3.14" + - os: windows-latest + python-version: "3.14" steps: - uses: actions/checkout@v7 @@ -33,13 +39,13 @@ jobs: - run: python -m pip install tox coverage[toml] - name: run Python tests - run: | - tox -e tests - # coverage xml + run: tox -e tests + - name: generate coverage report + run: coverage xml - # - name: upload to codecov.io - # uses: codecov/codecov-action@v5 - # with: - # fail_ci_if_error: true - # files: tests/coverage.xml - # token: ${{ secrets.CODECOV_TOKEN }} + - name: upload to codecov.io + uses: codecov/codecov-action@v7 + with: + fail_ci_if_error: true + files: coverage.xml + token: ${{ secrets.CODECOV_TOKEN }} diff --git a/CHANGELOG.rst b/CHANGELOG.rst index 9661aeb..04e2b63 100644 --- a/CHANGELOG.rst +++ b/CHANGELOG.rst @@ -14,6 +14,7 @@ The rules for spectrumkit's CHANGELOG file: Unreleased ---------- +- Test on macOS and Windows, upload coverage to Codecov. - Test weekly against the MAICoS dev version and the latest release, run doctests. - Fix logarithmic binning with ``binafter=0``, which averaged the whole spectrum diff --git a/pyproject.toml b/pyproject.toml index 9ca36d8..ee069cd 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -61,9 +61,32 @@ ignore_missing_imports = true [tool.coverage.paths] source = ["src/spectrumkit", "*/site-packages"] +[tool.coverage.run] +omit = [ + "examples/*", + "src/spectrumkit/_version.py", + "tests/*", + "tests/**/*", + "*/tests/*", + "*/tests/**/*", +] + [tool.coverage.report] skip_covered = true show_missing = true +exclude_lines = [ + "if __name__ == .__main__.:", + "if TYPE_CHECKING:", + "\\.\\.\\.", +] +omit = [ + "examples/*", + "src/spectrumkit/_version.py", + "tests/*", + "tests/**/*", + "*/tests/*", + "*/tests/**/*", +] [tool.pytest.ini_options] testpaths = "tests" From 1aecdb42aa09769245fe905941d88cf4a4933d73 Mon Sep 17 00:00:00 2001 From: hejamu Date: Thu, 29 Oct 2026 01:51:59 +0100 Subject: [PATCH 06/10] Sync tox, lint and packaging configuration with maicos 0.13 --- .github/workflows/build.yml | 10 +- .readthedocs.yml | 2 + CHANGELOG.rst | 7 +- LICENSE | 674 ++++++++++++++++++ MANIFEST.in | 18 +- .../analysis-modules/dielectricspectrum.rst | 0 docs/src/conf.py | 8 +- docs/src/get-started/changelog.rst | 0 docs/src/get-started/installation.rst | 0 examples/mdanalysis_workflow.py | 7 +- pyproject.toml | 13 +- src/spectrumkit/dielectricspectrum.py | 2 - tox.ini | 38 +- 13 files changed, 729 insertions(+), 50 deletions(-) create mode 100644 LICENSE mode change 100755 => 100644 docs/src/analysis-modules/dielectricspectrum.rst mode change 100755 => 100644 docs/src/get-started/changelog.rst mode change 100755 => 100644 docs/src/get-started/installation.rst mode change 100755 => 100644 src/spectrumkit/dielectricspectrum.py diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml index 7a3d9c3..bdcb0d0 100644 --- a/.github/workflows/build.yml +++ b/.github/workflows/build.yml @@ -31,15 +31,17 @@ jobs: check-latest: true - name: Install dependencies - run: python -m pip install wheel build tox + run: python -m pip install tox - - name: Test build integrity + - name: Test build integrity and build sdist run: tox -e build - uses: actions/upload-artifact@v7 with: - name: build - path: dist/* + name: files + path: | + dist/*.tar.gz + dist/*.whl release: name: Release package diff --git a/.readthedocs.yml b/.readthedocs.yml index 421e1bf..b91d6ff 100644 --- a/.readthedocs.yml +++ b/.readthedocs.yml @@ -24,3 +24,5 @@ python: - requirements: docs/requirements.txt - method: pip path: . + extra_requirements: + - examples diff --git a/CHANGELOG.rst b/CHANGELOG.rst index 04e2b63..3fec367 100644 --- a/CHANGELOG.rst +++ b/CHANGELOG.rst @@ -14,11 +14,14 @@ The rules for spectrumkit's CHANGELOG file: Unreleased ---------- +- Sync ``tox``, lint and packaging configuration with MAICoS 0.13: lint + examples, docs and the CHANGELOG, add a ``LICENSE`` file, leave ``docs`` out + of the source distribution. - Test on macOS and Windows, upload coverage to Codecov. - Test weekly against the MAICoS dev version and the latest release, run doctests. -- Fix logarithmic binning with ``binafter=0``, which averaged the whole spectrum - into one bin. +- Fix logarithmic binning with ``binafter=0``, which averaged the whole + spectrum into one bin. - Treat all warnings as errors in tests. - Require ``maicos>=0.13``, drop the ``mdacli<=0.1.35`` pin. (#20) diff --git a/LICENSE b/LICENSE new file mode 100644 index 0000000..f288702 --- /dev/null +++ b/LICENSE @@ -0,0 +1,674 @@ + GNU GENERAL PUBLIC LICENSE + Version 3, 29 June 2007 + + Copyright (C) 2007 Free Software Foundation, Inc. + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The GNU General Public License is a free, copyleft license for +software and other kinds of works. + + The licenses for most software and other practical works are designed +to take away your freedom to share and change the works. By contrast, +the GNU General Public License is intended to guarantee your freedom to +share and change all versions of a program--to make sure it remains free +software for all its users. We, the Free Software Foundation, use the +GNU General Public License for most of our software; it applies also to +any other work released this way by its authors. You can apply it to +your programs, too. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +them if you wish), that you receive source code or can get it if you +want it, that you can change the software or use pieces of it in new +free programs, and that you know you can do these things. + + To protect your rights, we need to prevent others from denying you +these rights or asking you to surrender the rights. Therefore, you have +certain responsibilities if you distribute copies of the software, or if +you modify it: responsibilities to respect the freedom of others. + + For example, if you distribute copies of such a program, whether +gratis or for a fee, you must pass on to the recipients the same +freedoms that you received. You must make sure that they, too, receive +or can get the source code. And you must show them these terms so they +know their rights. + + Developers that use the GNU GPL protect your rights with two steps: +(1) assert copyright on the software, and (2) offer you this License +giving you legal permission to copy, distribute and/or modify it. + + For the developers' and authors' protection, the GPL clearly explains +that there is no warranty for this free software. For both users' and +authors' sake, the GPL requires that modified versions be marked as +changed, so that their problems will not be attributed erroneously to +authors of previous versions. + + Some devices are designed to deny users access to install or run +modified versions of the software inside them, although the manufacturer +can do so. This is fundamentally incompatible with the aim of +protecting users' freedom to change the software. The systematic +pattern of such abuse occurs in the area of products for individuals to +use, which is precisely where it is most unacceptable. Therefore, we +have designed this version of the GPL to prohibit the practice for those +products. If such problems arise substantially in other domains, we +stand ready to extend this provision to those domains in future versions +of the GPL, as needed to protect the freedom of users. + + Finally, every program is threatened constantly by software patents. +States should not allow patents to restrict development and use of +software on general-purpose computers, but in those that do, we wish to +avoid the special danger that patents applied to a free program could +make it effectively proprietary. To prevent this, the GPL assures that +patents cannot be used to render the program non-free. + + The precise terms and conditions for copying, distribution and +modification follow. + + TERMS AND CONDITIONS + + 0. Definitions. + + "This License" refers to version 3 of the GNU General Public License. + + "Copyright" also means copyright-like laws that apply to other kinds of +works, such as semiconductor masks. + + "The Program" refers to any copyrightable work licensed under this +License. Each licensee is addressed as "you". "Licensees" and +"recipients" may be individuals or organizations. + + To "modify" a work means to copy from or adapt all or part of the work +in a fashion requiring copyright permission, other than the making of an +exact copy. The resulting work is called a "modified version" of the +earlier work or a work "based on" the earlier work. + + A "covered work" means either the unmodified Program or a work based +on the Program. + + To "propagate" a work means to do anything with it that, without +permission, would make you directly or secondarily liable for +infringement under applicable copyright law, except executing it on a +computer or modifying a private copy. Propagation includes copying, +distribution (with or without modification), making available to the +public, and in some countries other activities as well. + + To "convey" a work means any kind of propagation that enables other +parties to make or receive copies. Mere interaction with a user through +a computer network, with no transfer of a copy, is not conveying. + + An interactive user interface displays "Appropriate Legal Notices" +to the extent that it includes a convenient and prominently visible +feature that (1) displays an appropriate copyright notice, and (2) +tells the user that there is no warranty for the work (except to the +extent that warranties are provided), that licensees may convey the +work under this License, and how to view a copy of this License. If +the interface presents a list of user commands or options, such as a +menu, a prominent item in the list meets this criterion. + + 1. Source Code. + + The "source code" for a work means the preferred form of the work +for making modifications to it. "Object code" means any non-source +form of a work. + + A "Standard Interface" means an interface that either is an official +standard defined by a recognized standards body, or, in the case of +interfaces specified for a particular programming language, one that +is widely used among developers working in that language. + + The "System Libraries" of an executable work include anything, other +than the work as a whole, that (a) is included in the normal form of +packaging a Major Component, but which is not part of that Major +Component, and (b) serves only to enable use of the work with that +Major Component, or to implement a Standard Interface for which an +implementation is available to the public in source code form. A +"Major Component", in this context, means a major essential component +(kernel, window system, and so on) of the specific operating system +(if any) on which the executable work runs, or a compiler used to +produce the work, or an object code interpreter used to run it. + + The "Corresponding Source" for a work in object code form means all +the source code needed to generate, install, and (for an executable +work) run the object code and to modify the work, including scripts to +control those activities. However, it does not include the work's +System Libraries, or general-purpose tools or generally available free +programs which are used unmodified in performing those activities but +which are not part of the work. For example, Corresponding Source +includes interface definition files associated with source files for +the work, and the source code for shared libraries and dynamically +linked subprograms that the work is specifically designed to require, +such as by intimate data communication or control flow between those +subprograms and other parts of the work. + + The Corresponding Source need not include anything that users +can regenerate automatically from other parts of the Corresponding +Source. + + The Corresponding Source for a work in source code form is that +same work. + + 2. Basic Permissions. + + All rights granted under this License are granted for the term of +copyright on the Program, and are irrevocable provided the stated +conditions are met. This License explicitly affirms your unlimited +permission to run the unmodified Program. The output from running a +covered work is covered by this License only if the output, given its +content, constitutes a covered work. This License acknowledges your +rights of fair use or other equivalent, as provided by copyright law. + + You may make, run and propagate covered works that you do not +convey, without conditions so long as your license otherwise remains +in force. You may convey covered works to others for the sole purpose +of having them make modifications exclusively for you, or provide you +with facilities for running those works, provided that you comply with +the terms of this License in conveying all material for which you do +not control copyright. Those thus making or running the covered works +for you must do so exclusively on your behalf, under your direction +and control, on terms that prohibit them from making any copies of +your copyrighted material outside their relationship with you. + + Conveying under any other circumstances is permitted solely under +the conditions stated below. Sublicensing is not allowed; section 10 +makes it unnecessary. + + 3. Protecting Users' Legal Rights From Anti-Circumvention Law. + + No covered work shall be deemed part of an effective technological +measure under any applicable law fulfilling obligations under article +11 of the WIPO copyright treaty adopted on 20 December 1996, or +similar laws prohibiting or restricting circumvention of such +measures. + + When you convey a covered work, you waive any legal power to forbid +circumvention of technological measures to the extent such circumvention +is effected by exercising rights under this License with respect to +the covered work, and you disclaim any intention to limit operation or +modification of the work as a means of enforcing, against the work's +users, your or third parties' legal rights to forbid circumvention of +technological measures. + + 4. Conveying Verbatim Copies. + + You may convey verbatim copies of the Program's source code as you +receive it, in any medium, provided that you conspicuously and +appropriately publish on each copy an appropriate copyright notice; +keep intact all notices stating that this License and any +non-permissive terms added in accord with section 7 apply to the code; +keep intact all notices of the absence of any warranty; and give all +recipients a copy of this License along with the Program. + + You may charge any price or no price for each copy that you convey, +and you may offer support or warranty protection for a fee. + + 5. Conveying Modified Source Versions. + + You may convey a work based on the Program, or the modifications to +produce it from the Program, in the form of source code under the +terms of section 4, provided that you also meet all of these conditions: + + a) The work must carry prominent notices stating that you modified + it, and giving a relevant date. + + b) The work must carry prominent notices stating that it is + released under this License and any conditions added under section + 7. This requirement modifies the requirement in section 4 to + "keep intact all notices". + + c) You must license the entire work, as a whole, under this + License to anyone who comes into possession of a copy. This + License will therefore apply, along with any applicable section 7 + additional terms, to the whole of the work, and all its parts, + regardless of how they are packaged. This License gives no + permission to license the work in any other way, but it does not + invalidate such permission if you have separately received it. + + d) If the work has interactive user interfaces, each must display + Appropriate Legal Notices; however, if the Program has interactive + interfaces that do not display Appropriate Legal Notices, your + work need not make them do so. + + A compilation of a covered work with other separate and independent +works, which are not by their nature extensions of the covered work, +and which are not combined with it such as to form a larger program, +in or on a volume of a storage or distribution medium, is called an +"aggregate" if the compilation and its resulting copyright are not +used to limit the access or legal rights of the compilation's users +beyond what the individual works permit. Inclusion of a covered work +in an aggregate does not cause this License to apply to the other +parts of the aggregate. + + 6. Conveying Non-Source Forms. + + You may convey a covered work in object code form under the terms +of sections 4 and 5, provided that you also convey the +machine-readable Corresponding Source under the terms of this License, +in one of these ways: + + a) Convey the object code in, or embodied in, a physical product + (including a physical distribution medium), accompanied by the + Corresponding Source fixed on a durable physical medium + customarily used for software interchange. + + b) Convey the object code in, or embodied in, a physical product + (including a physical distribution medium), accompanied by a + written offer, valid for at least three years and valid for as + long as you offer spare parts or customer support for that product + model, to give anyone who possesses the object code either (1) a + copy of the Corresponding Source for all the software in the + product that is covered by this License, on a durable physical + medium customarily used for software interchange, for a price no + more than your reasonable cost of physically performing this + conveying of source, or (2) access to copy the + Corresponding Source from a network server at no charge. + + c) Convey individual copies of the object code with a copy of the + written offer to provide the Corresponding Source. This + alternative is allowed only occasionally and noncommercially, and + only if you received the object code with such an offer, in accord + with subsection 6b. + + d) Convey the object code by offering access from a designated + place (gratis or for a charge), and offer equivalent access to the + Corresponding Source in the same way through the same place at no + further charge. You need not require recipients to copy the + Corresponding Source along with the object code. If the place to + copy the object code is a network server, the Corresponding Source + may be on a different server (operated by you or a third party) + that supports equivalent copying facilities, provided you maintain + clear directions next to the object code saying where to find the + Corresponding Source. Regardless of what server hosts the + Corresponding Source, you remain obligated to ensure that it is + available for as long as needed to satisfy these requirements. + + e) Convey the object code using peer-to-peer transmission, provided + you inform other peers where the object code and Corresponding + Source of the work are being offered to the general public at no + charge under subsection 6d. + + A separable portion of the object code, whose source code is excluded +from the Corresponding Source as a System Library, need not be +included in conveying the object code work. + + A "User Product" is either (1) a "consumer product", which means any +tangible personal property which is normally used for personal, family, +or household purposes, or (2) anything designed or sold for incorporation +into a dwelling. In determining whether a product is a consumer product, +doubtful cases shall be resolved in favor of coverage. For a particular +product received by a particular user, "normally used" refers to a +typical or common use of that class of product, regardless of the status +of the particular user or of the way in which the particular user +actually uses, or expects or is expected to use, the product. A product +is a consumer product regardless of whether the product has substantial +commercial, industrial or non-consumer uses, unless such uses represent +the only significant mode of use of the product. + + "Installation Information" for a User Product means any methods, +procedures, authorization keys, or other information required to install +and execute modified versions of a covered work in that User Product from +a modified version of its Corresponding Source. The information must +suffice to ensure that the continued functioning of the modified object +code is in no case prevented or interfered with solely because +modification has been made. + + If you convey an object code work under this section in, or with, or +specifically for use in, a User Product, and the conveying occurs as +part of a transaction in which the right of possession and use of the +User Product is transferred to the recipient in perpetuity or for a +fixed term (regardless of how the transaction is characterized), the +Corresponding Source conveyed under this section must be accompanied +by the Installation Information. But this requirement does not apply +if neither you nor any third party retains the ability to install +modified object code on the User Product (for example, the work has +been installed in ROM). + + The requirement to provide Installation Information does not include a +requirement to continue to provide support service, warranty, or updates +for a work that has been modified or installed by the recipient, or for +the User Product in which it has been modified or installed. Access to a +network may be denied when the modification itself materially and +adversely affects the operation of the network or violates the rules and +protocols for communication across the network. + + Corresponding Source conveyed, and Installation Information provided, +in accord with this section must be in a format that is publicly +documented (and with an implementation available to the public in +source code form), and must require no special password or key for +unpacking, reading or copying. + + 7. Additional Terms. + + "Additional permissions" are terms that supplement the terms of this +License by making exceptions from one or more of its conditions. +Additional permissions that are applicable to the entire Program shall +be treated as though they were included in this License, to the extent +that they are valid under applicable law. If additional permissions +apply only to part of the Program, that part may be used separately +under those permissions, but the entire Program remains governed by +this License without regard to the additional permissions. + + When you convey a copy of a covered work, you may at your option +remove any additional permissions from that copy, or from any part of +it. (Additional permissions may be written to require their own +removal in certain cases when you modify the work.) You may place +additional permissions on material, added by you to a covered work, +for which you have or can give appropriate copyright permission. + + Notwithstanding any other provision of this License, for material you +add to a covered work, you may (if authorized by the copyright holders of +that material) supplement the terms of this License with terms: + + a) Disclaiming warranty or limiting liability differently from the + terms of sections 15 and 16 of this License; or + + b) Requiring preservation of specified reasonable legal notices or + author attributions in that material or in the Appropriate Legal + Notices displayed by works containing it; or + + c) Prohibiting misrepresentation of the origin of that material, or + requiring that modified versions of such material be marked in + reasonable ways as different from the original version; or + + d) Limiting the use for publicity purposes of names of licensors or + authors of the material; or + + e) Declining to grant rights under trademark law for use of some + trade names, trademarks, or service marks; or + + f) Requiring indemnification of licensors and authors of that + material by anyone who conveys the material (or modified versions of + it) with contractual assumptions of liability to the recipient, for + any liability that these contractual assumptions directly impose on + those licensors and authors. + + All other non-permissive additional terms are considered "further +restrictions" within the meaning of section 10. If the Program as you +received it, or any part of it, contains a notice stating that it is +governed by this License along with a term that is a further +restriction, you may remove that term. If a license document contains +a further restriction but permits relicensing or conveying under this +License, you may add to a covered work material governed by the terms +of that license document, provided that the further restriction does +not survive such relicensing or conveying. + + If you add terms to a covered work in accord with this section, you +must place, in the relevant source files, a statement of the +additional terms that apply to those files, or a notice indicating +where to find the applicable terms. + + Additional terms, permissive or non-permissive, may be stated in the +form of a separately written license, or stated as exceptions; +the above requirements apply either way. + + 8. Termination. + + You may not propagate or modify a covered work except as expressly +provided under this License. Any attempt otherwise to propagate or +modify it is void, and will automatically terminate your rights under +this License (including any patent licenses granted under the third +paragraph of section 11). + + However, if you cease all violation of this License, then your +license from a particular copyright holder is reinstated (a) +provisionally, unless and until the copyright holder explicitly and +finally terminates your license, and (b) permanently, if the copyright +holder fails to notify you of the violation by some reasonable means +prior to 60 days after the cessation. + + Moreover, your license from a particular copyright holder is +reinstated permanently if the copyright holder notifies you of the +violation by some reasonable means, this is the first time you have +received notice of violation of this License (for any work) from that +copyright holder, and you cure the violation prior to 30 days after +your receipt of the notice. + + Termination of your rights under this section does not terminate the +licenses of parties who have received copies or rights from you under +this License. If your rights have been terminated and not permanently +reinstated, you do not qualify to receive new licenses for the same +material under section 10. + + 9. Acceptance Not Required for Having Copies. + + You are not required to accept this License in order to receive or +run a copy of the Program. Ancillary propagation of a covered work +occurring solely as a consequence of using peer-to-peer transmission +to receive a copy likewise does not require acceptance. However, +nothing other than this License grants you permission to propagate or +modify any covered work. These actions infringe copyright if you do +not accept this License. Therefore, by modifying or propagating a +covered work, you indicate your acceptance of this License to do so. + + 10. Automatic Licensing of Downstream Recipients. + + Each time you convey a covered work, the recipient automatically +receives a license from the original licensors, to run, modify and +propagate that work, subject to this License. You are not responsible +for enforcing compliance by third parties with this License. + + An "entity transaction" is a transaction transferring control of an +organization, or substantially all assets of one, or subdividing an +organization, or merging organizations. If propagation of a covered +work results from an entity transaction, each party to that +transaction who receives a copy of the work also receives whatever +licenses to the work the party's predecessor in interest had or could +give under the previous paragraph, plus a right to possession of the +Corresponding Source of the work from the predecessor in interest, if +the predecessor has it or can get it with reasonable efforts. + + You may not impose any further restrictions on the exercise of the +rights granted or affirmed under this License. For example, you may +not impose a license fee, royalty, or other charge for exercise of +rights granted under this License, and you may not initiate litigation +(including a cross-claim or counterclaim in a lawsuit) alleging that +any patent claim is infringed by making, using, selling, offering for +sale, or importing the Program or any portion of it. + + 11. Patents. + + A "contributor" is a copyright holder who authorizes use under this +License of the Program or a work on which the Program is based. The +work thus licensed is called the contributor's "contributor version". + + A contributor's "essential patent claims" are all patent claims +owned or controlled by the contributor, whether already acquired or +hereafter acquired, that would be infringed by some manner, permitted +by this License, of making, using, or selling its contributor version, +but do not include claims that would be infringed only as a +consequence of further modification of the contributor version. For +purposes of this definition, "control" includes the right to grant +patent sublicenses in a manner consistent with the requirements of +this License. + + Each contributor grants you a non-exclusive, worldwide, royalty-free +patent license under the contributor's essential patent claims, to +make, use, sell, offer for sale, import and otherwise run, modify and +propagate the contents of its contributor version. + + In the following three paragraphs, a "patent license" is any express +agreement or commitment, however denominated, not to enforce a patent +(such as an express permission to practice a patent or covenant not to +sue for patent infringement). To "grant" such a patent license to a +party means to make such an agreement or commitment not to enforce a +patent against the party. + + If you convey a covered work, knowingly relying on a patent license, +and the Corresponding Source of the work is not available for anyone +to copy, free of charge and under the terms of this License, through a +publicly available network server or other readily accessible means, +then you must either (1) cause the Corresponding Source to be so +available, or (2) arrange to deprive yourself of the benefit of the +patent license for this particular work, or (3) arrange, in a manner +consistent with the requirements of this License, to extend the patent +license to downstream recipients. "Knowingly relying" means you have +actual knowledge that, but for the patent license, your conveying the +covered work in a country, or your recipient's use of the covered work +in a country, would infringe one or more identifiable patents in that +country that you have reason to believe are valid. + + If, pursuant to or in connection with a single transaction or +arrangement, you convey, or propagate by procuring conveyance of, a +covered work, and grant a patent license to some of the parties +receiving the covered work authorizing them to use, propagate, modify +or convey a specific copy of the covered work, then the patent license +you grant is automatically extended to all recipients of the covered +work and works based on it. + + A patent license is "discriminatory" if it does not include within +the scope of its coverage, prohibits the exercise of, or is +conditioned on the non-exercise of one or more of the rights that are +specifically granted under this License. You may not convey a covered +work if you are a party to an arrangement with a third party that is +in the business of distributing software, under which you make payment +to the third party based on the extent of your activity of conveying +the work, and under which the third party grants, to any of the +parties who would receive the covered work from you, a discriminatory +patent license (a) in connection with copies of the covered work +conveyed by you (or copies made from those copies), or (b) primarily +for and in connection with specific products or compilations that +contain the covered work, unless you entered into that arrangement, +or that patent license was granted, prior to 28 March 2007. + + Nothing in this License shall be construed as excluding or limiting +any implied license or other defenses to infringement that may +otherwise be available to you under applicable patent law. + + 12. No Surrender of Others' Freedom. + + If conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot convey a +covered work so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you may +not convey it at all. For example, if you agree to terms that obligate you +to collect a royalty for further conveying from those to whom you convey +the Program, the only way you could satisfy both those terms and this +License would be to refrain entirely from conveying the Program. + + 13. Use with the GNU Affero General Public License. + + Notwithstanding any other provision of this License, you have +permission to link or combine any covered work with a work licensed +under version 3 of the GNU Affero General Public License into a single +combined work, and to convey the resulting work. The terms of this +License will continue to apply to the part which is the covered work, +but the special requirements of the GNU Affero General Public License, +section 13, concerning interaction through a network will apply to the +combination as such. + + 14. Revised Versions of this License. + + The Free Software Foundation may publish revised and/or new versions of +the GNU General Public License from time to time. Such new versions will +be similar in spirit to the present version, but may differ in detail to +address new problems or concerns. + + Each version is given a distinguishing version number. If the +Program specifies that a certain numbered version of the GNU General +Public License "or any later version" applies to it, you have the +option of following the terms and conditions either of that numbered +version or of any later version published by the Free Software +Foundation. If the Program does not specify a version number of the +GNU General Public License, you may choose any version ever published +by the Free Software Foundation. + + If the Program specifies that a proxy can decide which future +versions of the GNU General Public License can be used, that proxy's +public statement of acceptance of a version permanently authorizes you +to choose that version for the Program. + + Later license versions may give you additional or different +permissions. However, no additional obligations are imposed on any +author or copyright holder as a result of your choosing to follow a +later version. + + 15. Disclaimer of Warranty. + + THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY +APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT +HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY +OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, +THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM +IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF +ALL NECESSARY SERVICING, REPAIR OR CORRECTION. + + 16. Limitation of Liability. + + IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS +THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY +GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE +USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF +DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD +PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), +EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF +SUCH DAMAGES. + + 17. Interpretation of Sections 15 and 16. + + If the disclaimer of warranty and limitation of liability provided +above cannot be given local legal effect according to their terms, +reviewing courts shall apply local law that most closely approximates +an absolute waiver of all civil liability in connection with the +Program, unless a warranty or assumption of liability accompanies a +copy of the Program in return for a fee. + + END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest +possible use to the public, the best way to achieve this is to make it +free software which everyone can redistribute and change under these terms. + + To do so, attach the following notices to the program. It is safest +to attach them to the start of each source file to most effectively +state the exclusion of warranty; and each file should have at least +the "copyright" line and a pointer to where the full notice is found. + + + Copyright (C) + + This program is free software: you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation, either version 3 of the License, or + (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this program. If not, see . + +Also add information on how to contact you by electronic and paper mail. + + If the program does terminal interaction, make it output a short +notice like this when it starts in an interactive mode: + + Copyright (C) + This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + +The hypothetical commands `show w' and `show c' should show the appropriate +parts of the General Public License. Of course, your program's commands +might be different; for a GUI interface, you would use an "about box". + + You should also get your employer (if you work as a programmer) or school, +if any, to sign a "copyright disclaimer" for the program, if necessary. +For more information on this, and how to apply and follow the GNU GPL, see +. + + The GNU General Public License does not permit incorporating your program +into proprietary programs. If your program is a subroutine library, you +may consider it more useful to permit linking proprietary applications with +the library. If this is what you want to do, use the GNU Lesser General +Public License instead of this License. But first, please read +. diff --git a/MANIFEST.in b/MANIFEST.in index 6d40ecf..57fa786 100644 --- a/MANIFEST.in +++ b/MANIFEST.in @@ -1,25 +1,19 @@ graft src -recursive-include docs *.bib -recursive-include docs *.py -recursive-include docs *.rst -recursive-include docs *.svg -recursive-include docs *.txt -prune docs/build -prune docs/src/generated_examples -include AUTHORS.rst -include CHANGELOG.rst -include README.rst -include MANIFEST.in +include *.rst +include LICENSE prune .tox prune developer +prune docs prune examples prune tests +prune .github exclude .gitattributes exclude .gitignore -exclude tox.ini exclude .readthedocs.yml +exclude .codecov.yml +exclude tox.ini global-exclude *.py[cod] __pycache__/* *.so *.dylib diff --git a/docs/src/analysis-modules/dielectricspectrum.rst b/docs/src/analysis-modules/dielectricspectrum.rst old mode 100755 new mode 100644 diff --git a/docs/src/conf.py b/docs/src/conf.py index 18bd71b..4a3be5d 100644 --- a/docs/src/conf.py +++ b/docs/src/conf.py @@ -1,5 +1,3 @@ -#!/usr/bin/env python -# # Copyright (c) 2025 Authors and contributors # (see the AUTHORS.rst file for the full list of names) # @@ -116,9 +114,9 @@ # font-awesome logos html_css_files = [ - "https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.0.0/css/fontawesome.min.css", # noqa: E501 - "https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.0.0/css/solid.min.css", # noqa: E501 - "https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.0.0/css/brands.min.css", # noqa: E501 + "https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.0.0/css/fontawesome.min.css", + "https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.0.0/css/solid.min.css", + "https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.0.0/css/brands.min.css", ] # -- Options for HTMLHelp output --------------------------------------------- diff --git a/docs/src/get-started/changelog.rst b/docs/src/get-started/changelog.rst old mode 100755 new mode 100644 diff --git a/docs/src/get-started/installation.rst b/docs/src/get-started/installation.rst old mode 100755 new mode 100644 diff --git a/examples/mdanalysis_workflow.py b/examples/mdanalysis_workflow.py index bb1d318..70b1536 100644 --- a/examples/mdanalysis_workflow.py +++ b/examples/mdanalysis_workflow.py @@ -1,4 +1,3 @@ -#!/usr/bin/env python """.. _howto-mdanalysis-workflow: MDAnalysis Workflow @@ -11,6 +10,7 @@ """ import MDAnalysis as mda + from spectrumkit import DielectricSpectrum # %% @@ -49,8 +49,9 @@ print(f"Average volume: {analysis.results.V:.2f} Ų") print(f"Number of frames: {len(analysis.results.P)}") print(f"Frequency points: {len(analysis.results.nu)}") -print(f"Frequency range: {analysis.results.nu[0]:.4f} - " - f"{analysis.results.nu[-1]:.4f} THz") +print( + f"Frequency range: {analysis.results.nu[0]:.4f} - {analysis.results.nu[-1]:.4f} THz" +) # %% # diff --git a/pyproject.toml b/pyproject.toml index ee069cd..fcc05da 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -51,10 +51,10 @@ issues = "https://github.com/maicos-devel/spectrumkit/issues" [tool.check-manifest] # ignore files missing in VCS -ignore = ["src/spectrumkit/_version.py", "docs/src/sg_execution_times.rst"] +ignore = ["src/spectrumkit/_version.py"] [tool.mypy] -exclude = ["docs/src/examples"] +exclude = ["docs/src/generated_examples"] follow_imports = 'skip' ignore_missing_imports = true @@ -100,6 +100,7 @@ addopts = [ ] [tool.ruff] +exclude = ["docs/src/generated_examples/**", "src/spectrumkit/_version.py"] line-length = 88 [tool.ruff.lint] @@ -140,6 +141,14 @@ ignore = [ "LOG015", # Logging using root logger #TODO(@PicoCentauri): Check this ] +[tool.ruff.lint.per-file-ignores] +"**/{docs,examples}/*" = [ + "T20", # Don't require any docstrings in these directories + "D212", # docstring summary not starting at first line + "D205", # 1 blank line required between summary line and description + "D415", # sphinx-gallery labels precede the summary line +] + [tool.ruff.lint.isort] known-first-party = ["spectrumkit"] diff --git a/src/spectrumkit/dielectricspectrum.py b/src/spectrumkit/dielectricspectrum.py old mode 100755 new mode 100644 index 0b2e623..f50b98c --- a/src/spectrumkit/dielectricspectrum.py +++ b/src/spectrumkit/dielectricspectrum.py @@ -1,5 +1,3 @@ -#!/usr/bin/env python -# # Copyright (c) 2025 Authors and contributors # (see the AUTHORS.rst file for the full list of names) # diff --git a/tox.ini b/tox.ini index e753a45..9cd8550 100644 --- a/tox.ini +++ b/tox.ini @@ -7,19 +7,18 @@ envlist = lint build tests + docs lint_folders = "{toxinidir}/src" \ - "{toxinidir}/tests" + "{toxinidir}/tests" \ + "{toxinidir}/examples" \ + "{toxinidir}/docs/src/" # configures which environments run with each python version [testenv] # Passing through all enviroment variables to tox jobs passenv = * -platform = - linux: linux - macos: darwin - windows: win32 # Default package_env, used for building source distribution [testenv:.pkg] @@ -58,14 +57,19 @@ commands = sphinx-lint \ --enable all \ --disable line-too-long \ - -i "{toxinidir}/docs/src/examples" \ - {[tox]lint_folders} "{toxinidir}/README.rst" + -i "{toxinidir}/docs/src/generated_examples" \ + {[tox]lint_folders} \ + "{toxinidir}/README.rst" \ + "{toxinidir}/AUTHORS.rst" \ + "{toxinidir}/CHANGELOG.rst" + # Enforce the 79 chars/line rule stated in the CHANGELOG header + sphinx-lint \ + --disable all \ + --enable line-too-long \ + --max-line-length 79 \ + "{toxinidir}/CHANGELOG.rst" [testenv:build] -platform = - linux: linux - macos: darwin - windows: win32 description = Asserts package build integrity for {platform} with {basepython}. usedevelop = true deps = @@ -73,9 +77,7 @@ deps = check-manifest twine allowlist_externals = - linux: bash - macos: zsh - windows: foreach + bash commands_pre = python {toxinidir}/developer/clean_dist_check.py commands = @@ -83,12 +85,8 @@ commands = twine check dist/*.tar.gz dist/*.whl check-manifest {toxinidir} # Workaround using shells since tox does not support wildcards - linux: bash -c "python -m pip install --force-reinstall dist/spectrumkit-*.tar.gz" - linux: bash -c "python -m pip install --force-reinstall dist/spectrumkit-*.whl" - macos: zsh -c "python -m pip install --force-reinstall dist/spectrumkit-*.tar.gz" - macos: zsh -c "python -m pip install --force-reinstall dist/spectrumkit-*.whl" - windows: foreach ($i in ls dist\*.tar.gz) \{pip install --force-reinstall $i\} - windows: foreach ($i in ls dist\*.whl) \{pip install --force-reinstall $i\} + bash -c "python -m pip install --force-reinstall dist/spectrumkit-*.tar.gz" + bash -c "python -m pip install --force-reinstall dist/spectrumkit-*.whl" [testenv:docs] description = Building the package documentation. From 11d8bf01867efa823791c1c496aac19ddb6c2642 Mon Sep 17 00:00:00 2001 From: hejamu Date: Thu, 29 Oct 2026 01:52:20 +0100 Subject: [PATCH 07/10] Check for a changelog entry in pull requests --- .github/workflows/docs.yml | 6 +++++- CHANGELOG.rst | 1 + developer/check_changelog.py | 42 ++++++++++++++++++++++++++++++++++++ 3 files changed, 48 insertions(+), 1 deletion(-) create mode 100755 developer/check_changelog.py diff --git a/.github/workflows/docs.yml b/.github/workflows/docs.yml index 52815d0..6d77496 100644 --- a/.github/workflows/docs.yml +++ b/.github/workflows/docs.yml @@ -24,11 +24,15 @@ jobs: check-latest: true - name: install dependencies - run: python -m pip install tox + run: python -m pip install tox gitpython - name: build documentation run: tox -e docs + - name: Check for Changelog + if: github.event_name == 'pull_request' + run: python ./developer/check_changelog.py + - name: put documentation in the website run: | git clone https://github.com/$GITHUB_REPOSITORY --branch gh-pages gh-pages diff --git a/CHANGELOG.rst b/CHANGELOG.rst index 3fec367..5d36902 100644 --- a/CHANGELOG.rst +++ b/CHANGELOG.rst @@ -14,6 +14,7 @@ The rules for spectrumkit's CHANGELOG file: Unreleased ---------- +- Check for a CHANGELOG entry in pull requests. - Sync ``tox``, lint and packaging configuration with MAICoS 0.13: lint examples, docs and the CHANGELOG, add a ``LICENSE`` file, leave ``docs`` out of the source distribution. diff --git a/developer/check_changelog.py b/developer/check_changelog.py new file mode 100755 index 0000000..dde67bd --- /dev/null +++ b/developer/check_changelog.py @@ -0,0 +1,42 @@ +#!/usr/bin/env python +"""Check if the CHANGELOG has been modified with respect to the main branch.""" +import os + +import git + + +class ChangelogError(Exception): + """Changelog error.""" + + pass + + +changelog = "CHANGELOG.rst" +repo_path = os.path.realpath(os.path.join(os.path.dirname(__file__), "..")) + +repo = git.Repo(repo_path) + +file = repo.git.show(f"origin/main:{changelog}") + +with open(os.path.join(repo_path, changelog)) as f: + workfile = f.read() + +if file.strip() == workfile.strip(): + # Check for changed files and ignore .github/ changes + head_commit = repo.head.commit + diff = head_commit.diff("origin/main") + changed_files = [] + for x in diff: + if x.a_blob.path not in changed_files: + changed_files.append(x.a_blob.path) + if x.b_blob is not None and x.b_blob.path not in changed_files: + changed_files.append(x.b_blob.path) + changed_files = [x for x in changed_files if not x.startswith(".github/")] + + if len(changed_files) > 0: + raise ChangelogError("You have not updated the CHANGELOG file. Please " + f"add a summary of your additions to {changelog}.") + else: + print("No changes detected.") +else: + print("CHANGELOG is up to date.") From 752646d764fd6cd8526e935525d0585583f26af2 Mon Sep 17 00:00:00 2001 From: hejamu Date: Thu, 29 Oct 2026 01:53:06 +0100 Subject: [PATCH 08/10] Fix leftover maicos and scatterkit references in the docs --- CHANGELOG.rst | 2 ++ docs/src/api-documentation/lib/index.rst | 3 ++- docs/src/api-documentation/lib/preprocessing.rst | 9 +++++++++ docs/src/conf.py | 2 +- docs/src/get-started/units.rst | 2 +- docs/src/get-started/usage-python.rst | 2 +- docs/src/index.rst | 8 ++++---- examples/README.rst | 4 ++-- 8 files changed, 22 insertions(+), 10 deletions(-) create mode 100644 docs/src/api-documentation/lib/preprocessing.rst diff --git a/CHANGELOG.rst b/CHANGELOG.rst index 5d36902..e4eca7e 100644 --- a/CHANGELOG.rst +++ b/CHANGELOG.rst @@ -14,6 +14,8 @@ The rules for spectrumkit's CHANGELOG file: Unreleased ---------- +- Fix leftover MAICoS and Scatterkit references in the documentation, document + ``lib.preprocessing``. - Check for a CHANGELOG entry in pull requests. - Sync ``tox``, lint and packaging configuration with MAICoS 0.13: lint examples, docs and the CHANGELOG, add a ``LICENSE`` file, leave ``docs`` out diff --git a/docs/src/api-documentation/lib/index.rst b/docs/src/api-documentation/lib/index.rst index e5bc7b3..ff55add 100644 --- a/docs/src/api-documentation/lib/index.rst +++ b/docs/src/api-documentation/lib/index.rst @@ -3,7 +3,7 @@ Library functions ################# -.. automodule:: maicos.lib +.. automodule:: spectrumkit.lib .. toctree:: :titlesonly: @@ -11,4 +11,5 @@ Library functions :caption: Library functions math + preprocessing util diff --git a/docs/src/api-documentation/lib/preprocessing.rst b/docs/src/api-documentation/lib/preprocessing.rst new file mode 100644 index 0000000..a9443d7 --- /dev/null +++ b/docs/src/api-documentation/lib/preprocessing.rst @@ -0,0 +1,9 @@ +.. _preprocessing_helper_functions: + +Preprocessing helper functions +############################## + +.. automodule:: spectrumkit.lib.preprocessing + :members: + :undoc-members: + :show-inheritance: diff --git a/docs/src/conf.py b/docs/src/conf.py index 4a3be5d..5a6fcd0 100644 --- a/docs/src/conf.py +++ b/docs/src/conf.py @@ -127,7 +127,7 @@ # -- Extension configuration ------------------------------------------------- # Configuration for intersphinx: refer to the Python standard library -# and other packages used by MAICoS +# and other packages used by spectrumkit intersphinx_mapping = { "scipy": ("https://docs.scipy.org/doc/scipy/", None), "matplotlib": ("https://matplotlib.org/stable/", None), diff --git a/docs/src/get-started/units.rst b/docs/src/get-started/units.rst index bd92930..cdbaa96 100644 --- a/docs/src/get-started/units.rst +++ b/docs/src/get-started/units.rst @@ -1,7 +1,7 @@ Some conventions ---------------- -The base units of Scatterkit are consistent with those of `MDAnalysis`_. Keeping inputs and +The base units of Spectrumkit are consistent with those of `MDAnalysis`_. Keeping inputs and outputs consistent with this set of units reduces ambiguity, so we encourage everyone to use them exclusively. diff --git a/docs/src/get-started/usage-python.rst b/docs/src/get-started/usage-python.rst index 88fa041..9d99b51 100644 --- a/docs/src/get-started/usage-python.rst +++ b/docs/src/get-started/usage-python.rst @@ -9,4 +9,4 @@ To use Spectrumkit using the Python interpreter see the Molecular Analysis for Interfacial and Confined Systems toolkit. .. _MAICOS tutorial: - https://maicos-analysis.org/stable/examples/usage-python.html + https://maicos-analysis.org/stable/get-started/basic-usage.html diff --git a/docs/src/index.rst b/docs/src/index.rst index 44ab483..7d740ba 100644 --- a/docs/src/index.rst +++ b/docs/src/index.rst @@ -36,16 +36,16 @@ API Documentation ----------------- The :ref:`userdoc_api-documentation` section is for Spectrumkit for advanced users, it contains technical references and parameter list for the APIs behind the library. It -describes the various functionalities provided by Scatterkit. You can always refer to this -section to learn more about classes, functions, modules, and other aspects of Scatterkit +describes the various functionalities provided by Spectrumkit. You can always refer to this +section to learn more about classes, functions, modules, and other aspects of Spectrumkit machinery you may come across behind the analysis classes described in :ref:`userdoc-analysis-modules`. Concepts & Explanations ----------------------- The :ref:`userdoc-concepts-explanations` section discusses key topics and concepts at a -fairly high level and provides explanations to expand your knowledge of Scatterkit. It -requires at least basic to intermediate knowledge of Scatterkit. +fairly high level and provides explanations to expand your knowledge of Spectrumkit. It +requires at least basic to intermediate knowledge of Spectrumkit. .. toctree:: diff --git a/examples/README.rst b/examples/README.rst index b00184c..625f5ea 100644 --- a/examples/README.rst +++ b/examples/README.rst @@ -6,9 +6,9 @@ How-to guides Like a cooking recipe, How-to guides help you solve key problems and use cases. If you are a total spectrumkit beginner, you should start with the :ref:`userdoc-get-started` section. Otherwise this section consists of introductory examples and examples -demonstrating specific features of scatterkit using its Python API. +demonstrating specific features of spectrumkit using its Python API. -For running the examples install scatterkit with the ``examples`` optional dependencies. +For running the examples install spectrumkit with the ``examples`` optional dependencies. .. code-block:: bash From 8af283588b9e1e1e785f8405fcf913892067d1f1 Mon Sep 17 00:00:00 2001 From: hejamu Date: Thu, 29 Oct 2026 01:54:40 +0100 Subject: [PATCH 09/10] Add issue forms and contributing guidelines --- .github/ISSUE_TEMPLATE/1-bug_report.yml | 78 ++++++++++ .../ISSUE_TEMPLATE/2-documentation_issue.yml | 45 ++++++ .github/ISSUE_TEMPLATE/3-feature_request.yml | 43 ++++++ .github/ISSUE_TEMPLATE/4-blank_issue.yml | 12 ++ .github/ISSUE_TEMPLATE/Bug.md | 45 ------ .github/ISSUE_TEMPLATE/Feature.md | 17 --- .github/ISSUE_TEMPLATE/config.yml | 5 + CHANGELOG.rst | 1 + CONTRIBUTING.rst | 133 ++++++++++++++++++ tox.ini | 3 +- 10 files changed, 319 insertions(+), 63 deletions(-) create mode 100644 .github/ISSUE_TEMPLATE/1-bug_report.yml create mode 100644 .github/ISSUE_TEMPLATE/2-documentation_issue.yml create mode 100644 .github/ISSUE_TEMPLATE/3-feature_request.yml create mode 100644 .github/ISSUE_TEMPLATE/4-blank_issue.yml delete mode 100644 .github/ISSUE_TEMPLATE/Bug.md delete mode 100644 .github/ISSUE_TEMPLATE/Feature.md create mode 100644 .github/ISSUE_TEMPLATE/config.yml create mode 100644 CONTRIBUTING.rst diff --git a/.github/ISSUE_TEMPLATE/1-bug_report.yml b/.github/ISSUE_TEMPLATE/1-bug_report.yml new file mode 100644 index 0000000..aaa95a6 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/1-bug_report.yml @@ -0,0 +1,78 @@ +name: 🐛 Bug report +description: Create a bug report to help us eliminate issues and improve. +title: "BUG: " +labels: [bug] +body: + - type: markdown + attributes: + value: | + Thanks for taking the time to fill out this bug report! + - type: textarea + id: summary + attributes: + label: Summary + description: A clear and concise description of what the bug is. + placeholder: Describe the bug clearly and concisely. + validations: + required: true + - type: textarea + id: expected_behavior + attributes: + label: Expected behavior + description: | + A clear and concise description of what you want to do and what you think should happen. + (Code and files to reproduce the behavior can be added below). + placeholder: Describe what you expected to happen. + validations: + required: true + - type: textarea + id: actual_behavior + attributes: + label: Actual behavior + description: | + Describe the actual behavior, how it differs from the expected behavior, and how this can be observed. + + Try to be specific and do **not** use vague terms like "doesn't work" or "wrong result". + + Do not assume that the person reading this has any experience with or knowledge of your specific area of research. + placeholder: Describe the actual behavior. + validations: + required: true + - type: input + id: version + attributes: + label: Version + description: | + What versions of spectrumkit and MAICoS are you using and on what platform? You can find them by running: + + ```bash + python -c "import spectrumkit, maicos; print(spectrumkit.__version__, maicos.__version__)" + python -V + ``` + placeholder: e.g., 0.1.0, 0.13 + validations: + required: true + - type: textarea + id: steps_to_reproduce + attributes: + label: Steps to reproduce + description: | + Describe the steps required to (quickly) reproduce the issue. + + You can attach (small) files to the section below or add URLs where to download an archive with all necessary files. + + Please try to create an input set that is as minimal and small as possible and reproduces the bug as quickly as possible. + + **NOTE:** the less effort and time it takes to reproduce your reported bug, the more likely it becomes that somebody will look into it and fix the problem. + placeholder: List the steps to reproduce here. + validations: + required: false + - type: textarea + id: further_info + attributes: + label: Further information, files, and links + description: | + Any relevant information that might help us to understand the issue. + placeholder: Add relevant files, logs, or links here. + validations: + required: false diff --git a/.github/ISSUE_TEMPLATE/2-documentation_issue.yml b/.github/ISSUE_TEMPLATE/2-documentation_issue.yml new file mode 100644 index 0000000..9a5f8f4 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/2-documentation_issue.yml @@ -0,0 +1,45 @@ +name: 📚 Documentation issue +description: Report an issue related to the documentation. +title: "DOC: " +labels: [documentation] +body: + - type: markdown + attributes: + value: | + Report a mistake, missing information, or improvement suggestion related to the documentation. + - type: textarea + id: location + attributes: + label: Location of the issue + description: | + Provide the location of the documentation issue. This could be a URL, file path, or section heading. + placeholder: e.g., https://maicos-devel.github.io/spectrumkit/stable/get-started/installation.html or "Getting started -> Installation" + validations: + required: true + - type: textarea + id: description + attributes: + label: Description of the issue + description: | + Describe the issue you found. Be as specific as possible. + For example: typo, outdated information, unclear explanation, missing example, etc. + placeholder: Describe the problem clearly. + validations: + required: true + - type: textarea + id: suggestion + attributes: + label: Suggested fix or improvement (optional) + description: | + If you have an idea of how to fix or improve the documentation, please share it here. + placeholder: Suggest the corrected text or improvement. + validations: + required: false + - type: textarea + id: additional_context + attributes: + label: Additional context + description: Add any other context, screenshots, or links that might help clarify the issue. + placeholder: Additional context, links, or screenshots. + validations: + required: false diff --git a/.github/ISSUE_TEMPLATE/3-feature_request.yml b/.github/ISSUE_TEMPLATE/3-feature_request.yml new file mode 100644 index 0000000..ed062a1 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/3-feature_request.yml @@ -0,0 +1,43 @@ +name: ✨ Feature request +description: Suggest an idea or improvement. +title: "FEATURE: " +labels: [enhancement] +body: + - type: markdown + attributes: + value: | + Suggest an idea or improvement for this project. + - type: textarea + id: problem_description + attributes: + label: Is your feature request related to a problem? Please describe. + description: | + A clear and concise description of what the problem is. + Example: "I'm always frustrated when [...]" + placeholder: Describe the problem you are facing or the motivation for the feature. + validations: + required: true + - type: textarea + id: solution + attributes: + label: Describe the solution you'd like + description: A clear and concise description of what you want to happen. + placeholder: Describe the ideal solution or feature you would like to see. + validations: + required: true + - type: textarea + id: alternatives + attributes: + label: Describe alternatives you've considered + description: A clear and concise description of any alternative solutions or features you've considered. + placeholder: Mention any workarounds or alternative ideas you have explored. + validations: + required: false + - type: textarea + id: additional_context + attributes: + label: Additional context + description: Add any other context or screenshots about the feature request here. + placeholder: Provide links, images, or related discussions if available. + validations: + required: false diff --git a/.github/ISSUE_TEMPLATE/4-blank_issue.yml b/.github/ISSUE_TEMPLATE/4-blank_issue.yml new file mode 100644 index 0000000..2e074f0 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/4-blank_issue.yml @@ -0,0 +1,12 @@ +name: 📝 Blank issue +description: Create a new issue from scratch. +body: + - type: textarea + id: description + attributes: + label: Description of the issue + description: | + Describe the issue you found. Be as specific as possible. + placeholder: Describe the problem clearly. + validations: + required: true diff --git a/.github/ISSUE_TEMPLATE/Bug.md b/.github/ISSUE_TEMPLATE/Bug.md deleted file mode 100644 index de38271..0000000 --- a/.github/ISSUE_TEMPLATE/Bug.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -name: Bug report -about: Create a report to help us improve - ---- - -**Expected behavior** - - - -**Actual behavior** - - - - -**Code to reproduce the behavior** - - - -**Current version** - - - -**Describe the solution you'd like** - - -**Describe alternatives you've considered** - - -**Additional context** - diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml new file mode 100644 index 0000000..2e1eece --- /dev/null +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -0,0 +1,5 @@ +blank_issues_enabled: false +contact_links: + - name: 💬 Questions & Discussions + url: https://discord.gg/mnrEQWVAed + about: Please ask and answer questions on our discord server. diff --git a/CHANGELOG.rst b/CHANGELOG.rst index e4eca7e..d2bf059 100644 --- a/CHANGELOG.rst +++ b/CHANGELOG.rst @@ -14,6 +14,7 @@ The rules for spectrumkit's CHANGELOG file: Unreleased ---------- +- Add issue forms and contributing guidelines. - Fix leftover MAICoS and Scatterkit references in the documentation, document ``lib.preprocessing``. - Check for a CHANGELOG entry in pull requests. diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst new file mode 100644 index 0000000..fb49a2b --- /dev/null +++ b/CONTRIBUTING.rst @@ -0,0 +1,133 @@ +Spectrumkit is a community effort, driven mainly by scientists working on +molecular simulations of fluids. It is developed in open collaboration by the MAICoS +developer team and contributors from across the world. +As such, we welcome contributions from anyone who is interested in improving +Spectrumkit, and we are committed to providing a welcoming and inclusive environment for +all contributors. + +To ensure a positive and productive experience for everyone involved in the project, +we have established the following guidelines for contributing. +Please read them carefully before submitting any contributions to Spectrumkit. + +Code of Conduct +--------------- + +As contributors and maintainers of Spectrumkit, we pledge to respect all people who +contribute through reporting issues, posting feature requests, updating documentation, +submitting merge requests or patches, and other activities. + +We are committed to making participation in this project a harassment-free experience +for everyone, regardless of level of experience, gender, gender identity and expression, +sexual orientation, disability, personal appearance, body size, race, ethnicity, age, or +religion. + +Examples of unacceptable behavior by participants include the use of sexual language or +imagery, derogatory comments or personal attacks, trolling, public or private +harassment, insults, or other unprofessional conduct. + +Project maintainers have the right and responsibility to remove, edit, or reject +comments, commits, code, wiki edits, issues, and other contributions that are not +aligned to this Code of Conduct. Project maintainers who do not follow the Code of +Conduct may be removed from the project team. + +This code of Conduct applies both within project spaces and in public spaces when an +individual is representing the project or its community. + +Instances of abusive, harassing, or otherwise unacceptable behavior should be +reported to the `project maintainers`_. + +This Code of Conduct is adapted from the `Contributor Covenant`_, version 1.1.0, +available at https://contributor-covenant.org/version/1/1/0/ + +.. _`project maintainers` : https://github.com/maicos-devel/spectrumkit/blob/main/AUTHORS.rst +.. _`Contributor Covenant` : https://contributor-covenant.org + +Getting involved +---------------- + +Contribution via pull requests are always welcome. Source code is available from +`GitHub`_. Before submitting a pull request, please open an issue to discuss your +changes. Use only the ``main`` branch for submitting your requests. + +.. _`GitHub` : https://github.com/maicos-devel/spectrumkit/ + +By contributing to Spectrumkit, you accept and agree to the following terms and +conditions for your present and future contributions submitted to Spectrumkit. Except for +the license granted herein to Spectrumkit and recipients of software distributed by +Spectrumkit, you reserve all right, title, and interest in and to your contributions. + +Getting started +--------------- + +To help with developing start by installing the development dependencies. Our continuous +integration pipeline is based on Tox_. So you need to install ``tox`` first + +.. code-block:: bash + + pip install tox + # or + conda install -c conda-forge tox + +Then go to the `Spectrumkit develop project`_ page, hit the ``Fork`` button and clone +your forked branch to your machine. + +.. code-block:: bash + + git clone git@github.com:your-user-name/spectrumkit.git + +Now you have a local version on your machine which you can install by + +.. code-block:: bash + + cd spectrumkit + pip install -e . + +This install the package in development mode, making it importable globally and allowing +you to edit the code and directly use the updated version. + +To run the tests, the linters, or build the documentation use + +.. code-block:: bash + + tox -e tests + tox -e lint + tox -e docs + +.. _Tox: https://tox.readthedocs.io/en/latest/ +.. _`Spectrumkit develop project` : https://github.com/maicos-devel/spectrumkit + +Useful developer scripts +------------------------ + +The following scripts can be useful to developers: + +- ``./developer/clean_dist_check.py``: Clean dist files. Useful before/after ``tox -e + build`` +- ``./developer/check_changelog.py``: Check that the CHANGELOG has been updated with + respect to the ``main`` branch. + +Automated Contributions Policy +------------------------------ + +Contributing to Spectrumkit requires human judgment, contextual understanding, and +familiarity with concepts related to spectra from molecular simulations. +It is not suitable for automatic processing by AI tools. + +Please refrain from submitting issues or pull requests generated by +fully-automated tools. Maintainers reserve the right, at their sole discretion, +to close such submissions and to block any account responsible for them. + +Review all code or documentation changes made by AI tools and make sure you +understand all changes and can explain them on request, before submitting them +under your name. Do not submit any AI-generated code that you haven’t personally +reviewed, understood and tested, as this wastes maintainers’ time. +To enhance the review process, please indicate if significant parts of your +contribution were generated or modified by AI tools (typically this is the +case beyond simple code suggestions e.g. inside IDEs). + +Please do not paste AI generated text in the description of issues, PRs or in comments +as this makes it harder for reviewers to assess your contribution. +We are happy for it to be used to improve grammar or if you are not a native English +speaker. + +PRs that appear to violate this policy will be closed without review. diff --git a/tox.ini b/tox.ini index 9cd8550..262409e 100644 --- a/tox.ini +++ b/tox.ini @@ -61,7 +61,8 @@ commands = {[tox]lint_folders} \ "{toxinidir}/README.rst" \ "{toxinidir}/AUTHORS.rst" \ - "{toxinidir}/CHANGELOG.rst" + "{toxinidir}/CHANGELOG.rst" \ + "{toxinidir}/CONTRIBUTING.rst" # Enforce the 79 chars/line rule stated in the CHANGELOG header sphinx-lint \ --disable all \ From 46331a102282cb2e9f9b2ce285841ca47d4979a7 Mon Sep 17 00:00:00 2001 From: hejamu Date: Thu, 29 Oct 2026 02:03:12 +0100 Subject: [PATCH 10/10] Fix changelog --- CHANGELOG.rst | 14 +------------- 1 file changed, 1 insertion(+), 13 deletions(-) diff --git a/CHANGELOG.rst b/CHANGELOG.rst index d2bf059..9e72ff2 100644 --- a/CHANGELOG.rst +++ b/CHANGELOG.rst @@ -14,19 +14,7 @@ The rules for spectrumkit's CHANGELOG file: Unreleased ---------- -- Add issue forms and contributing guidelines. -- Fix leftover MAICoS and Scatterkit references in the documentation, document - ``lib.preprocessing``. -- Check for a CHANGELOG entry in pull requests. -- Sync ``tox``, lint and packaging configuration with MAICoS 0.13: lint - examples, docs and the CHANGELOG, add a ``LICENSE`` file, leave ``docs`` out - of the source distribution. -- Test on macOS and Windows, upload coverage to Codecov. -- Test weekly against the MAICoS dev version and the latest release, run - doctests. -- Fix logarithmic binning with ``binafter=0``, which averaged the whole - spectrum into one bin. -- Treat all warnings as errors in tests. +- Fix logarithmic binning with ``binafter=0`` (#23). - Require ``maicos>=0.13``, drop the ``mdacli<=0.1.35`` pin. (#20) v0.1.0 (2026/05/20)