Remove abandoned `cf.etc` directory
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- build-system
Research direction
Locate the abandoned cf.etc directory, including cf.etc.coordinate_reference, and inspect how the package is included in the build configuration. Remove the unused directory, then run the packaging or CI check that currently reports the setuptools warning. Done means the directory is gone and the package build no longer warns about cf.etc.
Written by the indexing model from the issue text.
Description
As agreed offline, the etc directory has long not been in use (notably duplicating data now in constants module) and can be removed to tidy the codebase and to prevent packaging getting confused and raising warnings about it, e.g. from a CI job:
[90](https://github.com/NCAS-CMS/cf-python/actions/runs/34459805523/job/102814670829?pr=967#step:12:591)
!!
check.warn(importable)
/private/var/folders/20/jp1_0n3n7kndh6rnbqb5344m0000gn/T/build-env-27lv9eqx/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cf.etc.coordinate_reference' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'cf.etc.coordinate_reference' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
- Dominant language
- Python
- Stars
- 150
- Forks
- 23
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NCAS-CMS/cf-python
-
bug?
-
release
-
enhancement
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
API review (4.0.0) documentation
Difficulty 4/5 3-5 days Newbie friendliness 48/100
All issues in NCAS-CMS/cf-python
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100