Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Final cleanup after constants migration

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Stale
Tech stack
python

Research direction

After issues #182–#186 are complete, inspect package_data in setup.py and verify the le_utils/resources/ directory is gone. Update README.md and CHANGELOG.md as specified, then run pytest tests/ -v, make build, and the package build/install commands; done means all listed acceptance criteria pass.

Written by the indexing model from the issue text.

Description

❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.

Overview

With #182–#186 landed, the package should stop shipping le_utils/resources/, and the README should describe the spec workflow instead of keeping Python and JSON in sync by hand.

Complexity: Low
Target branch: main

Context
  • pyproject.toml ships resources/*.json through [tool.setuptools.package-data].
  • The README's Constants section says a new constant means editing the Python file and the JSON file; its file formats and format presets sections link to formatlookup.json (on a personal fork) and presetlookup.json.
The Change
  • The README should say that a constant is added by editing its spec/ file and running make build.
Acceptance Criteria
  • The built le-utils wheel contains no resources/ files.
  • le_utils/resources/ contains only the languagelookup.json symlink.
  • README links to le_utils/resources/ point to the matching spec/ files instead, except the languagelookup.json link.

AI usage

I made the decisions recorded on #181 and #182; Claude Code applied them to this cleanup against the current code and drafted the issue.

Dominant language
Python
Stars
7
Forks
37
Avg merge
7d 42m
Merged PRs (30d)
7

Getting set up

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 learningequality/le-utils

All issues in learningequality/le-utils

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.