Remove conda dev environment and devcontainer (pip-only)#102
Merged
Conversation
Pynteny is a pure-pip package, so the conda-based developer tooling is no longer needed: - Delete envs/pynteny-dev.yml and the miniconda-based .devcontainer/. - Add requirements-dev.txt with the development tools that used to live in the conda env file (ruff, black, coverage, and the mkdocs documentation stack). - CONTRIBUTING.md: install dev tools via `pip install -r requirements-dev.txt` and drop the conda env note and the (now obsolete) conda Codespaces section. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Final piece of the conda → pip migration: remove the conda-based developer tooling, which is no longer needed now that Pynteny is a pure-pip package.
Changes
envs/pynteny-dev.ymland the miniconda-based.devcontainer/.requirements-dev.txtwith the development tools that used to live in the conda env file's pip section (ruff,black,coverage, and the mkdocs documentation stack).CONTRIBUTING.md: developer setup now installs dev tools viapip install -r requirements-dev.txt; removed the conda env note and the obsolete conda-based Codespaces section.Verified there are no remaining references to
envs/,.devcontainer, conda, or mamba anywhere in the docs/config. The repo is now conda-free end to end (package, CI, packaging, and dev setup).🤖 Generated with Claude Code