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

Make `Settings` attributes warn on *assign*, not on *access* (or reset)

Open
#89 3 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
64/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python

Research direction

Start by locating the Settings implementation and its pydantic integration, then inspect how attribute access, assignment, and reset currently trigger warnings. Update the behavior so user-facing assignment warns while internal reads and reset do not, and add or adjust tests to verify each case.

Written by the indexing model from the issue text.

Description

Description of feature

Settings get read internally and assigning them is the user facing API.

Therefore pydantic’s behavior of warning on access (which is also triggered by reset btw.) but not on assignment doesn’t fit and we should change that.

This tripped up @ilan-gold and me in https://github.com/scverse/anndata/pull/2643

Dominant language
Python
Stars
6
Forks
2
Avg merge
2h 29m
Merged PRs (30d)
10

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 scverse/scverse-misc

All issues in scverse/scverse-misc

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.