Skip to content

Ability to set default scatter edge parameters in matplotlibrc #11933

Closed as not planned

Description

@brewstronomy

Issue #6272 brought up the idea to edit the matplotlibrc to set the default marker when calling plt.scatter(). Can this be updated to include other default parameters, e.g. linewidths and/or edgecolors?

Activity

  1. timhoffm commented on Aug 25, 2018

    @timhoffm
    Member

    Most parameters are actually controlled via rcParams already, e.g. rcParams['lines.linewidth']. The case of marker was a bit different, because it had a hard-coded value.

    I'm not quite sure if we want to do per-plot-type settings of all the style parameters. It adds a bit more flexibility for default styles. On the other hand the styles would have to define many more parameters lines.linewidth, scatter.linewidth, ..., which most of the time will be identical. Or alternatively we would need to implement a cascaded style system with a general line width, which may be overriden with other per-plot-type settings.

    If we decide that per-plot-type settings are desireable, I propose to develop such a cascaded style system first to keep the complexity under control. Personally, I'm -0.5 on this because the gain is not large enough compared to the amount of required work.

    Another issue for colors (including edgecolors): The code is already quite complex and I strongly advise against adding more stuff in the current state. #11663 starts the color parsing refactoring and should be merged before changing anything color-related in scatter().

  2. github-actions commented on Jun 5, 2023

    @github-actions

    This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help!

  3. added
    status: closed as inactiveIssues closed by the "Stale" Github Action. Please comment on any you think should still be open.
    on Jul 5, 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

    status: closed as inactiveIssues closed by the "Stale" Github Action. Please comment on any you think should still be open.status: inactiveMarked by the “Stale” Github Actiontopic: rcparams

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions