GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Migrate Argument Clinic docs from the CPython repo to the devguide · Issue #1148 · python/devguide

Migrate Argument Clinic docs from the CPython repo to the devguide #1148

New issue
Copy link
New issue
Copy link
Closed
#1160
Closed
Migrate Argument Clinic docs from the CPython repo to the devguide#1148
#1160
Copy link
Labels
type-featureAdditions; New content or section neededAdditions; New content or section needed

Description

@erlend-aasland
erlend-aasland
opened on Aug 2, 2023
Issue body actions

See topic on Discourse and python/cpython#107518

Prerequisites:

  • Where should clinic.rst live?
  • Which section (and sub-section) should the Argument Clinic docs live in? (Advanced Tools? CPython Internals?)
  • Prepare devguide; rename Advanced Tools to Development Tools, and move it between Testing and Buildbots and Core Developers

Activity

  1. erlend-aasland
    added
    type-featureAdditions; New content or section neededAdditions; New content or section needed
    on Aug 2, 2023
  2. erlend-aasland commented on Aug 2, 2023

    @erlend-aasland
    erlend-aasland
    on Aug 2, 2023
    ContributorAuthor
    More actions

    Perhaps the Development Workflow is a good fit. It already contains a section about writing extension modules (although that's just a collection of links).

  3. erlend-aasland commented on Aug 2, 2023

    @erlend-aasland
    erlend-aasland
    on Aug 2, 2023
    ContributorAuthor
    More actions

    Here's the filtered branch: https://github.com/erlend-aasland/devguide/tree/migrate-clinic-docs

  4. CAM-Gerlach commented on Aug 2, 2023

    @CAM-Gerlach
    CAM-Gerlach
    on Aug 2, 2023
    Member
    More actions

    I really struggled with that too when you first posed the issue of moving it; of the plausible candidates:

    • Development Workflow is the most crowded and is mostly focused on how to change different things rather than technical guides to specific tools, and currently has a clear and carefully thought out progression from giving an overview of CPython's development workflow and cycle to discussing how to make progressively larger and less common changes (from stdlib tweaks to porting to a whole new platform). Its not obvious where Argument Clinic would fit there (except at the end, but it still seems a little out of place).
    • CPython's Internals is mostly focused on explanation type content of how and why different parts of CPython work the way they do, rather than how-to guides on how to develop CPython or use specific tools, so doesn't seem like a good fit.
    • Advanced Tools is another option to consider, as it specifically covers how to use various tools for CPython development, so is at least nominally the most on-topic. It currently mostly focused on "advanced" tools (like GDB, Clang dynamic analysis, and Coverity) that won't be used by most CPython developers, so folks might not think to look there first. However, a rename to "Development Tools", a move to between Testing and Buildbots and Core Developers, and putting the Argument Clinic guide in the section first might help address that, as well as be a good spot for similar such guides in the future.

    Therefore, my preference would be for Development Tools (Advanced Tools) with the changes suggested above.

    Reacted by Erlend E. Aasland
  5. erlend-aasland commented on Aug 2, 2023

    @erlend-aasland
    erlend-aasland
    on Aug 2, 2023
    ContributorAuthor
    More actions

    Development Tools sounds good to me!

  6. erlend-aasland commented on Aug 2, 2023

    @erlend-aasland
    erlend-aasland
    on Aug 2, 2023
    ContributorAuthor
    More actions

    See #1149

  7. erlend-aasland
    closed this as completedin #1160on Sep 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    type-featureAdditions; New content or section neededAdditions; New content or section needed

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402520 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.