How does it handle versioning for new releases?

The skill supports multiple strategies including manual versioning in pyproject.toml, dynamic versioning from __init__.py, or VCS-based versioning using plugins like hatch-vcs.

Does this skill support legacy setup.py files?

No, this skill follows modern Python packaging standards (PEP 517/518/621) which prioritize pyproject.toml over legacy setup.py or setup.cfg files.

Can I use this for non-scientific Python libraries?

Yes. While it adheres to Scientific Python community best practices, these patterns represent the 'gold standard' for all high-quality, modern Python library development.

Why is the src/ layout recommended for scientific packages?

The src/ layout prevents users from accidentally importing the local code instead of the installed package, which ensures that tests run against the actual distribution and that all necessary files are correctly packaged.

Scientific Python Packaging

Name: Scientific Python Packaging
Author: robertpelloni

byrobertpelloni

•

Data Science & ML

Builds and publishes standards-compliant scientific Python packages using pyproject.toml and Hatchling.

About

This skill provides Claude with specialized knowledge for architecting, configuring, and distributing Python packages specifically tailored for the scientific computing community. It implements modern standards such as the src/ layout, PEP 621 metadata, and the Hatchling build backend, ensuring that research software is reproducible, installable, and ready for publication on PyPI. From dependency management with version constraints to automated publishing workflows and documentation best practices, it streamlines the lifecycle of scientific software development and ensures compliance with Scientific Python community guidelines.

Key Features

Configures pyproject.toml with PEP 621 metadata and Hatchling build backend
Manages scientific dependencies and PEP 735 dependency groups
Provides automated workflows for PyPI and TestPyPI distribution
3 GitHub stars
Implements modern src/ layout for package isolation and testing integrity
Generates boilerplate for CLI tools, Sphinx documentation, and GitHub Actions

Use Cases

Migrating legacy setup.py configurations to modern, tool-independent standards
Converting research scripts into a distributable library for the scientific community
Structuring complex research software for peer review and open-source publication

About

Key Features

Configures pyproject.toml with PEP 621 metadata and Hatchling build backend
Manages scientific dependencies and PEP 735 dependency groups
Provides automated workflows for PyPI and TestPyPI distribution
3 GitHub stars
Implements modern src/ layout for package isolation and testing integrity
Generates boilerplate for CLI tools, Sphinx documentation, and GitHub Actions

Use Cases

Migrating legacy setup.py configurations to modern, tool-independent standards
Converting research scripts into a distributable library for the scientific community
Structuring complex research software for peer review and open-source publication