IDLE search and replace should use 'hit' tag instead of 'hilite'
Ouverte
@terryjreedy y travaille déjà.
Depuis le 28/1/2017.
topic-IDLE
type-feature
- Langage dominant
- Python
- Étoiles
- 77.2k
- Forks
- 36k
- Merge moyen
- 1 j 9 h
- PR mergées (30 j)
- 558
Description
| BPO | 29382 |
|---|---|
| Nosy | @terryjreedy |
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/terryjreedy'
closed_at = None
created_at = <Date 2017-01-28.01:03:15.392>
labels = ['expert-IDLE', 'type-feature', '3.10']
title = "IDLE search and replace should use 'hit' tag instead of 'hilite'"
updated_at = <Date 2020-06-06.22:09:25.323>
user = 'https://bugs.python.org/ds2'
bugs.python.org fields:
activity = <Date 2020-06-06.22:09:25.323>
actor = 'terry.reedy'
assignee = 'terry.reedy'
closed = False
closed_date = None
closer = None
components = ['IDLE']
creation = <Date 2017-01-28.01:03:15.392>
creator = 'd s2'
dependencies = []
files = []
hgrepos = []
issue_num = 29382
keywords = []
message_count = 3.0
messages = ['286393', '286395', '286397']
nosy_count = 2.0
nosy_names = ['terry.reedy', 'd s2']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue29382'
versions = ['Python 3.10']
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Évaluation
Cette issue n'a pas encore été évaluée.