8000 Use greek small letter mu "\u03bc" instead of micro sign "\u00B5" for micro unit prefix (alt 1) by jbouwh · Pull Request #144853 · home-assistant/core · GitHub
[go: up one dir, main page]

Skip to content

Use greek small letter mu "\u03bc" instead of micro sign "\u00B5" for micro unit prefix (alt 1) #144853

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 23 commits into
base: dev
Choose a base branch
from

Conversation

jbouwh
Copy link
Contributor
@jbouwh jbouwh commented 10000 May 14, 2025

Breaking change

Breaks sensors that pass their unit by config (e.g. YAML) or custom integrations that use the the other unicode. MQTT sensors have been made compatible with equivalent units.

This should be followed op in future PR's..

Proposed change

To represent the micro sign there are 2 different UNICODE characters used:

https://www.compart.com/en/unicode/U+00B5
-> 0xC2 0xB5 b'\xce\xbc' "\u00b5"
µ: MICRO SIGN

https://www.compart.com/en/unicode/U+03BC
-> 0xCE 0xBC b'\xc2\xb5' "\u03bc"
μ: Greek Small Letter Mu

This PR implements the use of "\u03bc" (the Greek small letter mu) to encode the micro unit prefix, instead of the legacy migro sign "\u00B5".

To see the change impact the other way see #144898

According to The Unicode Consortium, the Greek letter character is preferred,[10] but implementations must recognize the micro sign as well, for compatibility with legacy character sets.

So then U+03BC μ GREEK SMALL LETTER MU (Alt+956) should prehaps prevail?

See also: astral-sh/ruff#14433

A pylint linter is added to ensure we use the correct encoding when using MU in a constant or StrEnum assignment

Equivalent units have been added to prevent breaking sensor statistics in the HA recorder.

MQTT sensors allow equivalent units in their configs to prevent breaking.

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Deprecation (breaking change to happen in the future)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue:
  • Link to documentation pull request:
  • Link to developer documentation pull request:
  • Link to frontend pull request:

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • I have followed the perfect PR recommendations
  • The code has been formatted using Ruff (ruff format homeassistant tests)
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

Copy link
codecov bot commented May 14, 2025

❌ We are unable to process any of the uploaded JUnit XML files. Please ensure your files are in the right format.

@MartinHjelmare
Copy link
Member

The PR description doesn't match the PR title. In the description it says that we should use b'\xc2\xb5', while in the title it says we should use b'\xce\xbc'

@MartinHjelmare
Copy link
Member

It would be interesting to describe where and how much we use each of the characters today.

@jbouwh jbouwh changed the title Use b'\xce\xbc` for micro sign instead of b'\xc2\xb5' Use b'\xce\xbc` for micro sign instead of b'\xc2\xb5' alt 1 May 14, 2025
@jbouwh jbouwh changed the title Use b'\xce\xbc` for micro sign instead of b'\xc2\xb5' alt 1 Use Greek micro sign b'\xc2\xb5' for micro sign instead of b'\xce\xbc` alt 1 May 17, 2025
@jbouwh jbouwh marked this pull request as ready for review May 21, 2025 11:39
@emontnemery emontnemery marked this pull request as draft May 21, 2025 14:08
@emontnemery
Copy link
Contributor

Setting to draft until some discussion on Discord is completed

@jbouwh jbouwh marked this pull request as ready for review May 21, 2025 21:13
@emontnemery emontnemery marked this pull request as draft May 22, 2025 13:28
@emontnemery emontnemery changed the title Use Greek micro sign b'\xc2\xb5' for micro sign instead of b'\xce\xbc` alt 1 Use micro sign b'\xc2\xb5' instead of greek small letter mu b'\xce\xbc` for micro unit prefix (alt 1) May 22, 2025
@jbouwh jbouwh marked this pull request as ready for review May 28, 2025 06:31
@jbouwh jbouwh marked this pull request as draft May 28, 2025 06:31
@jbouwh jbouwh force-pushed the fix-microsign-alt1 branch from 93e67f3 to 358e27a Compare May 28, 2025 06:41
@jbouwh jbouwh force-pushed the fix-microsign-alt1 branch from 0b65412 to e3fe99e Compare May 28, 2025 13:36
@jbouwh jbouwh marked this pull request as ready for review June 2, 2025 06:38
@jbouwh jbouwh requested a review from fabaff as a code owner June 2, 2025 06:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0