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

Clean / clear all `__init__.py`

Open
  • Is something wrong?
#38 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
42/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

Inspect all __init__.py files, beginning with morphoclass/data/__init__.py, and identify code and __all__ statements in each one. Remove those contents while retaining the license header, module docstring, and optional future import; the work is done when every __init__.py follows that structure and the project still imports successfully.

Written by the indexing model from the issue text.

Description

It would be good to remove all code from all __init__.py files, in particular also all __all__ statements. See for example morphoclass/data/__init__.py. This will speed up imports since unused submodule imports will no longer be done, and will also render the code structure more simple and transparent.

Ideally all __init__.py should have at most these 3 elements:

  • License notice header
  • Module docstring
  • from __future__ import annotations (since isort is configured to automatically add this line to all .py-files)
Dominant language
Python
Stars
13
Forks
6
No merged PRs in 30d

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 BlueBrain/morphoclass

All issues in BlueBrain/morphoclass

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.