Possibly create action to check for missing __init__.py files that cause pylint
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4
- Forks
- 33
- Avg merge
- 3d 54m
- Merged PRs (30d)
- 2
Description
Missing __init__.py files cause pylint to fail to lint some modules as of Sept 22, 2025
Notes:
- Issue https://github.com/edx/edx-arch-experiments/issues/57 contains the following notes:
- This pylint issue was fixed, but it either didn't work or regressed, because this problem was see in opendx/ event-bus-kafka as of Sept 22
- edx-platform has a CI check that validates that every dir with Python code has a dunder-init file.
Options include:
- Proving that this is no longer an issue.
- Adding a new
.githubworkflow that can replicate the edx-platform CI check. Or, - Moving to Ruff, a replacement for pylint brought up in Discourse, might now have the same problem.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing issue 57 and the edx-platform CI check in pull request 27875, then verify whether missing init.py files still reproduce the reported pylint failure in opendx/event-bus-kafka. Compare the possible workflow check with Ruff's INP001 documentation; done means choosing and documenting one validated path, with a working check if a workflow is selected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100