FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

[Doc]: clarify when and how to use boilerplate.py · Issue #27190 · matplotlib/matplotlib · GitHub

Repository navigation

[Doc]: clarify when and how to use boilerplate.py #27190

Closed

Description

Documentation Link

No response

Problem

Per this discussion #27158 (comment), I (maybe other folk) are a bit confused on what the "do not edit" comments in pyplot mean given that boilerplate.py is never run automatically. Consensus seems to be that the process should be when changing the signature of a pyplot function, run boilerplate.py and commit those changes but that's not documented anywhere.

Suggested improvement

More clearly document using boilerplate.py by:

  1. changing the Autogen message to "generated by biolerplate.py, do not edit"
    AUTOGEN_MSG = """
    # Autogenerated by boilerplate.py. Do not edit as changes will be lost."""
  2. change the comment at the top of pyplot to something like "plotting signatures are generated by boilerplate.py, rerun when changing signatures and commit the changes
    # Note: The first part of this file can be modified in place, but the latter
    # part is autogenerated by the boilerplate.py script.
  3. add something like (note: this rst may be incorrect) to the coding guideline.
When a function in the :doc:`pyplot  API<doc/api/pyplot_summary>`, run :file:`lib/matplotlib/test_pyplot.py::test_pyplot_up_to_date`. If the test fails and and you intended to change those signatures, run boilerplate.py and commit the changes

Activity

  1. changed the title [-][Doc]: clarify when and how to use biolerplate.py[/-] [+][Doc]: clarify when and how to use boilerplate.py[/+] on Oct 25, 2023
  2. QuLogic commented on Oct 25, 2023

    Member

    Consensus seems to be that the process should be when changing the signature of a pyplot function, run boilerplate.py and commit those changes but that's not documented anywhere.

    This is generally true, though there are functions in there that are not part of the automatically generated set. An easier indicator is "if the lib/matplotlib/tests/test_pyplot.py::test_pyplot_up_to_date test fails", but one has to clarify that with "and you intended to change those signatures".

  3. added 4 commits that reference this issue on Sep 15, 2025
    8f78b99
    9571737
    49df95b
    c85328a
  4. added this to the v3.11.0 milestone on Sep 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions


      Back | FazBrowse Home | New Git URL