[Submission]: Huez – Intelligent Color Management for Python Visualization

[HzaCode]

Submitting Author: (@HzaCode)
All current maintainers: (@HzaCode)
Package Name: Huez
One-Line Description of Package: An intelligent color management system for Python visualization that unifies colors across libraries and ensures accessibility.
Repository Link: https://github.com/HzaCode/Huez
Version submitted: 0.1.0
EiC: @yeelauren
Editor: TBD
Reviewer 1: TBD
Reviewer 2: TBD
Archive: TBD
JOSS DOI: TBD
Version accepted: TBD
Date accepted (month/day/year): TBD

---

Code of Conduct & Commitment to Maintain Package

• I agree to abide by [pyOpenSci's Code of Conduct][PyOpenSciCodeOfConduct] during the review process and in future interactions in spaces supported by pyOpenSci should it be accepted.
• I have read and will commit to package maintenance after the review as per the [pyOpenSci Policies Guidelines][Commitment].

Description

Huez provides a unified, configurable color system for Python visualization. It applies consistent palettes and styles across multiple plotting libraries, supports automatic colormap detection (e.g., sequential vs. diverging), LAB-space color expansion for large categorical plots, and accessibility checks (e.g., color-vision deficiencies). A command-line interface and YAML-based configuration enable repeatable, project-level workflows.

Scope

• Please indicate which category or categories.
  Check out our [package scope page][PackageCategories] to learn more about our
  scope. (If you are unsure of which category you fit, we suggest you make a pre-submission inquiry):

  • Data retrieval
  • Data extraction
  • Data processing/munging
  • Data deposition
  • Data validation and testing
  • Data visualization
  • Workflow automation
  • Citation management and bibliometrics
  • Scientific software wrappers
  • Database interoperability

Domain Specific

• Geospatial
• Education

Community Partnerships

If your package is associated with an
existing community please check below:

• Astropy:[My package adheres to Astropy community standards](https://www.pyopensci.org/software-peer-review/partners/astropy.html)
• Pangeo: My package adheres to the [Pangeo standards listed in the pyOpenSci peer review guidebook][PangeoCollaboration]

• For all submissions, explain how and why the package falls under the categories you indicated above. In your explanation, please address the following points (briefly, 1-2 sentences for each):

  • Target audience & applications. Researchers and engineers who need consistent, accessible color schemes across Python plotting libraries for publication-quality figures and reproducible pipelines.

  • Related packages & differences. Existing packages (e.g., seaborn palettes, palettable, colorcet) configure colors within a single library or require manual per-plot choices. Huez focuses on cross-library unification, automatic colormap selection, accessibility checks, and a CLI/config system for reproducible project-level styling.

  • Pre-submission enquiry. None yet.

Technical checks

For details about the pyOpenSci packaging requirements, see our [packaging guide][PackagingGuide]. Confirm each of the following by checking the box. This package:

• does not violate the Terms of Service of any service it interacts with.
• uses an [OSI approved license][OsiApprovedLicense]. (MIT)
• contains a README with instructions for installing the package.
• includes documentation with examples for all functions.
• contains a tutorial with examples of its essential functions and uses.
• has a test suite.
• has continuous integration setup, such as GitHub Actions CircleCI, and/or others.

Publication Options

• Do you wish to automatically submit to the [Journal of Open Source Software][JournalOfOpenSourceSoftware]? If so:

JOSS Checks

• The package has an obvious research application according to JOSS's definition in their [submission requirements][JossSubmissionRequirements]. Be aware that completing the pyOpenSci review process does not guarantee acceptance to JOSS. Be sure to read their submission requirements (linked above) if you are interested in submitting to JOSS.
• The package is not a "minor utility" as defined by JOSS's [submission requirements][JossSubmissionRequirements]: "Minor ‘utility’ packages, including ‘thin’ API clients, are not acceptable." pyOpenSci welcomes these packages under "Data Retrieval", but JOSS has slightly different criteria.
• The package contains a paper.md matching [JOSS's requirements][JossPaperRequirements] with a high-level description in the package root or in inst/.
• The package is deposited in a long-term repository with the DOI:

Note: JOSS accepts our review as theirs. You will NOT need to go through another full review. JOSS will only review your paper.md file. Be sure to link to this pyOpenSci issue when a JOSS issue is opened for your package. Also be sure to tell the JOSS editor that this is a pyOpenSci reviewed package once you reach this step.

Are you OK with Reviewers Submitting Issues and/or pull requests to your Repo Directly?

This option will allow reviewers to open smaller issues that can then be linked to PR's rather than submitting a more dense text based review. It will also allow you to demonstrate addressing the issue via PR links.

• Yes I am OK with reviewers submitting requested changes as issues to my repo. Reviewers will then link to the issues in their submitted review.

Confirm each of the following by checking the box.

• I have read the [author guide](https://www.pyopensci.org/software-peer-review/how-to/author-guide.html).
• I expect to maintain this package for at least 2 years and can help find a replacement for the maintainer (team) if needed.