macOS build docs need refresh (2019)
Offen
@ned-deily arbeitet bereits daran.
Seit 06.2.2019.
build
docs
OS-mac
- Vorherrschende Sprache
- Python
- Sterne
- 77.2k
- Forks
- 36k
- PR-Merge-Kennzahlen
- PR-Kennzahlen ausstehend
Beschreibung
| BPO | 35905 |
|---|---|
| Nosy | @warsaw, @jaraco, @ned-deily |
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/ned-deily'
closed_at = None
created_at = <Date 2019-02-06.00:12:22.643>
labels = ['3.8', 'docs']
title = 'macOS build docs need refresh (2019)'
updated_at = <Date 2022-03-24.16:40:40.166>
user = 'https://github.com/jaraco'
bugs.python.org fields:
activity = <Date 2022-03-24.16:40:40.166>
actor = 'Battant'
assignee = 'ned.deily'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2019-02-06.00:12:22.643>
creator = 'jaraco'
dependencies = []
files = []
hgrepos = []
issue_num = 35905
keywords = []
message_count = 4.0
messages = ['334895', '334898', '334943', '415959']
nosy_count = 5.0
nosy_names = ['barry', 'jaraco', 'ned.deily', 'docs@python', 'Battant']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue35905'
versions = ['Python 3.8']
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Bewertung
Dieses Issue wurde noch nicht bewertet.