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

Write and require docstrings for public module functions

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
cli, documentation

Research direction

Start by reviewing issue #42 and identifying the core functionality being moved into a Python module. Enumerate its public functions and decide which docstring style and linting approach fit the project. Done means public module functions have usage-reflecting docstrings and a test or lint check verifies their presence.

Written by the indexing model from the issue text.

Description

loe 2 sdk-cli

As part of https://github.com/mapbox/tilesets-cli/issues/42, we'll be moving core functionality to a python module. All public module functions should have a docstring reflecting the usage of said function.

Some initial ideas are:

cc @Gerdie

Dominant language
Python
Stars
141
Forks
27
PR merge metrics
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 mapbox/tilesets-cli

All issues in mapbox/tilesets-cli

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.