Investigate making Shapely an optional dependency

Open
#6,837 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
build-system, testing

Research direction

Audit every Iris use of Shapely and determine whether it is part of core functionality. Based on that decision, review the optional-dependency patterns for unit versus integration tests, dependency listing, and user warnings; done means the core-versus-optional decision and all resulting areas are addressed.

Written by the indexing model from the issue text.

Description

Dragon Sub-Task 🦎

Confirm whether or not any Iris' uses of Shapely qualify as core Iris functionality.

  • Core: Shapely stays as a core dependency
  • Not core: adopt the optional dependency patterns for Shapely
    • Unit versus Integration testing
    • Dependency listing
    • User warning
Dominant language
Python
Stars
724
Forks
317
Avg merge
3d 20h
Merged PRs (30d)
9

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SciTools/iris

All issues in SciTools/iris

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.