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 — boxplot treats iterables differently by type · Issue #2539 · matplotlib/matplotlib

boxplot treats iterables differently by type #2539

New issue
Copy link
New issue
Copy link
Closed
Closed
boxplot treats iterables differently by type#2539
Copy link
Labels
API: consistencyConsistency of the matplotlib API, including naming, behavior, defaults, …Consistency of the matplotlib API, including naming, behavior, defaults, …status: duplicatethird-party integration
Milestone
v2.2.0

Description

@jseabold
jseabold
opened on Oct 23, 2013
Issue body actions

It's stated in the documentation, but I find this behavior to be rather wart-y, and it led to some bugs in statsmodels. Why treat x array different from x sequence of lists?

For an array it iterates over the first axis

import numpy as np
import matplotlib.pyplot as plt

x = np.random.normal(size=(2,1000))
fig, ax = plt.subplots()

ax.boxplot(x.T)

for lists it iterates over the zero axis

fig, ax = plt.subplots()
ax.boxplot([x[0,:],x[1,:]])

Why the distinction? I'd expect them to be the same (i.e., the list gets an np.asarray call) and it seems inconsistent that they're not.

Activity

  1. efiring commented on Oct 27, 2013

    @efiring
    efiring
    on Oct 27, 2013
    Member
    More actions

    From the general mpl and python standpoints, I agree entirely with @jseabold. It is unfortunate that this aspect of the signature is present; the question is what, if anything, to do about it now.

  2. tacaswell commented on Jan 22, 2014

    @tacaswell
    tacaswell
    on Jan 22, 2014
    Member
    More actions

    @jseabold Have you seen PR #2643 to overhaul boxplot by @phobson?

  3. tacaswell
    added this to the This milestone has been deleted milestone on Aug 17, 2014
  4. tacaswell commented on Aug 17, 2014

    @tacaswell
    tacaswell
    on Aug 17, 2014
    Member
    More actions

    This might have to get punted to 2.0

  5. story645
    added
    third-party integration
    on Jun 1, 2016
  6. tacaswell
    modified the milestones: This milestone has been deleted, This milestone has been deleted on Oct 3, 2017
  7. anntzer commented on Oct 19, 2017

    @anntzer
    anntzer
    on Oct 19, 2017
    Contributor
    More actions

    I think most of the discussion is in #8092 now.

  8. anntzer
    closed this as completedon Oct 19, 2017
  9. anntzer
    added
    status: duplicate
    on Oct 19, 2017
  10. QuLogic
    modified the milestones: This milestone has been deleted, v2.2.0 on Feb 12, 2018
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

    API: consistencyConsistency of the matplotlib API, including naming, behavior, defaults, …Consistency of the matplotlib API, including naming, behavior, defaults, …status: duplicatethird-party integration

    Type

    No type

    Projects

    No projects

      Milestone

      • v2.2.0

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — 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.