python / python/cpython

dataclass defaults and property don't work together

Offen
#83,428 20 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@ericvsmith arbeitet bereits daran.

Seit 07.1.2020.

3.10 3.11 3.7 (EOL) 3.8 (EOL) 3.9 (EOL) stdlib topic-dataclasses type-bug
Vorherrschende Sprache
Python
Sterne
77.2k
Forks
36k
Ø Merge
1 T. 9 Std.
Gemergte PRs (30 T.)
558

Beschreibung

BPO 39247
Nosy @ericvsmith, @anthrax_0, @UnHumbleBen

Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

Show more details

GitHub fields:

assignee = 'https://github.com/ericvsmith'
closed_at = None
created_at = <Date 2020-01-07.17:35:37.533>
labels = ['type-bug', '3.8', '3.9', '3.10', '3.11', '3.7', 'library']
title = "dataclass defaults and property don't work together"
updated_at = <Date 2021-10-21.22:51:04.309>
user = 'https://bugs.python.org/MichaelRobellard'

bugs.python.org fields:

activity = <Date 2021-10-21.22:51:04.309>
actor = 'Thomas701'
assignee = 'eric.smith'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-01-07.17:35:37.533>
creator = 'Michael Robellard'
dependencies = []
files = []
hgrepos = []
issue_num = 39247
keywords = []
message_count = 19.0
messages = ['359528', '359564', '359757', '359764', '359774', '366546', '371820', '395191', '395192', '395195', '395196', '404617', '404624', '404625', '404648', '404684', '404685', '404694', '404700']
nosy_count = 6.0
nosy_names = ['eric.smith', 'Michael Robellard', 'juanpa.arrivillaga', 'iivanyuk', 'UnHumbleBen', 'Thomas701']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue39247'
versions = ['Python 3.7', 'Python 3.8', 'Python 3.9', 'Python 3.10', 'Python 3.11']

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.