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

PEP 557 interop namespace

Open
#686 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python

Research direction

Start by reading PEP 557 and comparing its dataclasses and fields interfaces with attrs' field and attr.ib APIs. Define the intended namespace and document the incompatibilities and adapter scope before proposing an implementation. Done means the migration and compatibility behavior are specified clearly enough to review.

Written by the indexing model from the issue text.

Description

Feature

Extracted from https://github.com/python-attrs/attrs/issues/408#issuecomment-514375369

On the other side of this, what about making a namespace that actually is intentionally similar to PEP 557 dataclasses and fields, and just has a thin adapter layer between field and attr.ib, etc? How much incompatibility is there beyond the names? Isn't attrs mostly a superset?

It would be good for migrating from large codebases where dataclasses are already used, or for pythonistas who want codebases/apis that stick close to the PEP specifications where possible.

Dominant language
Python
Stars
5.8k
Forks
480
Avg merge
2h 15m
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

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 python-attrs/attrs

All issues in python-attrs/attrs

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.