Add direct anchors to regex syntax documentation

Open
#83,156 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

Begin with PR #17470 and the regex syntax documentation it targets. The issue names no file or test, so identify the relevant documentation entry point from that PR; done means the requested direct anchors are present and the documentation change is accepted.

Written by the indexing model from the issue text.

Description

docs topic-regex type-feature
BPO 38975
Nosy @terryjreedy, @serhiy-storchaka, @bmispelon, @JulienPalard
PRs
  • python/cpython#17470
    		•

    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 = None
closed_at = None
created_at = <Date 2019-12-04.21:12:31.099>
labels = ['type-feature', 'docs']
title = 'Add direct anchors to regex syntax documentation'
updated_at = <Date 2019-12-09.21:41:44.691>
user = 'https://github.com/bmispelon'

    bugs.python.org fields:

    activity = <Date 2019-12-09.21:41:44.691>
actor = 'bmispelon'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2019-12-04.21:12:31.099>
creator = 'bmispelon'
dependencies = []
files = []
hgrepos = []
issue_num = 38975
keywords = ['patch']
message_count = 3.0
messages = ['357831', '357951', '358145']
nosy_count = 5.0
nosy_names = ['terry.reedy', 'docs@python', 'serhiy.storchaka', 'bmispelon', 'mdk']
pr_nums = ['17470']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue38975'
versions = []

    Dominant language
    Python
    Stars
    77.2k
    Forks
    36k
    Avg merge
    1d 9h
    Merged PRs (30d)
    558

    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/cpython

    All issues in python/cpython

    Similar issues

    More Python issues

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.