Resolve problems with pint global settings

Open
#7 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
tooling

Research direction

Start by reviewing the global settings in src/cfpint/_core.py at lines 129-131 and the corresponding settings in Iris at lib/iris/common/mixin.py lines 549-551. Inspect how the current formatter and application_registry affect ordinary Pint units, then establish whether these settings are necessary. Done means ordinary Pint units are not unintentionally treated or formatted as cfpint units.

Written by the indexing model from the issue text.

Description

both the current formatter and application_registry
Note: this will impact the code in Iris too

At present we are making these settings
in cfpint
and in iris

This could cause problems because (I think) "ordinary" Pint units will also get created as cfpint units by default, and will also convert to/form strings differently.
And it isn't clear whether this is actually necessary.

Dominant language
Python
Stars
1
Forks
3
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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/cfpint

All issues in SciTools/cfpint

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.