python-spin
Port variant v12
Summary Developer tool for scientific libraries (3.12)
BROKEN
Package version 0.12
Homepage https://github.com/scientific-python/spin
Keywords python
Maintainer Python Automaton
License Not yet specified
Other variants v11
Ravenports Buildsheet | History
Ravensource Port Directory | History
Last modified 07 SEP 2024, 17:00:23 UTC
Port created 10 OCT 2023, 04:40:21 UTC
Subpackage Descriptions
single # 💫 Scientific Python INcantations (`spin`) ## A developer tool for scientific Python libraries Developers need to memorize a whole bunch of magic command-line incantations. These incantations may also change over time. Often, Makefiles are used to provide aliases, but Makefiles can be convoluted, are not written in Python, and are hard to extend. The goal of `spin` is therefore to provide a simple, user-friendly, extendable interface for common development tasks. It comes with a few common build commands out the box, but can easily be customized per project. As a curiosity: the impetus behind developing the tool was the mass migration of scientific Python libraries (SciPy, scikit-image, and NumPy, etc.) to Meson, after distutils was deprecated. When many of the build and installation commands changed, it made sense to abstract away the nuisance of having to re-learn them. _Note:_ We now have experimental builds for editable installs. Most of the Meson commands listed below should work "out of the box" for those. ## Installation ` pip install spin ` ## Configuration Settings are stored in `.spin.toml`, `spin.toml`, or your project's `pyproject.toml`. As an example, see the `[tool.spin]` section of [an example `pyproject.toml`]. The `[project]` section should contain `name`. The `[tool.spin]` section should contain: ``` package = "pkg_importname" # name of your package commands = [ "spin.cmds.meson.build", "spin.cmds.meson.test" ] ``` See [the command selection] below. ### Command sections Once you have several commands, it may be useful to organize them into sections. In `pyproject.toml`, instead of specifying the commands as a list, use the following structure: ```toml [tool.spin.commands] "Build" = [ "spin.cmds.meson.build", "spin.cmds.meson.test" ] "Environments" = [ "spin.cmds.meson.ipython", "spin.cmds.meson.run" ] ``` These commands will then be rendered as: ``` Build: build 🔧 Build package with Meson/ninja test 🔧 Run tests Environments: ipython 💻 Launch IPython shell with PYTHONPATH set run 🏁 Run a shell command with PYTHONPATH set ``` ## Running ` spin ` or ``` python -m spin ``` ## Built-in commands ### [Meson] Available as `spin.cmds.meson.*`. ```
Configuration Switches (platform-specific settings discarded)
PY311 OFF Build using Python 3.11 PY312 ON Build using Python 3.12
Package Dependencies by Type
Build (only) python312:dev:std
python-pip:single:v12
autoselect-python:single:std
Build and Runtime python312:primary:std
Runtime (only) python-click:single:v12
python-importlib-metadata:single:v12
Download groups
main mirror://PYPIWHL/05/8f/0991efd9da175a552386720e06e43a7618ee0c60122936b3939d00b0cd27
Distribution File Information
648a03d7b7e4cb25a7ced5247ae7e2a5191d9e3678a9f8defcab891d9cba4bfa 27542 spin-0.12-py3-none-any.whl
Ports that require python-spin:v12
python-numpy:v12 Array computing for Python (3.12)