Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 14:43
    MikiPWata synchronize #23587
  • 14:38
    MikiPWata synchronize #23587
  • 14:36
    oscargus synchronize #23605
  • 14:28
    oscargus synchronize #23605
  • 14:26
    oscargus opened #23605
  • 14:26
    oscargus labeled #23605
  • 14:24
    timhoffm commented #18289
  • 14:11
    tacaswell commented #22849
  • 13:56

    timhoffm on main

    Minor cleanup of axes_grid1 Merge pull request #23596 from … (compare)

  • 13:56
    timhoffm closed #23596
  • 13:55
    timhoffm milestoned #23596
  • 13:52
    timhoffm commented #18387
  • 13:37
    story645 edited #18289
  • 13:36
    story645 commented #18289
  • 13:35
    story645 commented #18289
  • 13:33
    oscargus demilestoned #15514
  • 13:33
    oscargus milestoned #15514
  • 13:32
    oscargus closed #15514
  • 13:32
    oscargus commented #15514
  • 13:24
    oscargus commented #18289
Bruno Beltran
@brunobeltran
I swear I always assume it's a DeprecationWarning subclass even after years of using knowing otherwise.
(I'm sure this conversation has been had before, but not since I've been around ;))
Jody Klymak
@jklymak
Note that the weekly developer call has moved to Tuesdays, 15:00 EDT (27 Oct = 19:00 UTC) and will follow America/New_York to 15:00 Standard time starting next week (3 Nov = 20:00 UTC).
hannah
@story645
@brunobeltran is totally acceptable to put hottakes on the agenda
Bruno Beltran
@brunobeltran
Done.
Jody Klymak
@jklymak
Maybe just open an issue for that and put on the agenda if it really is controversial? My assumption is that its not controversial and just hasn't been noticed
Tim Hoffmann
@timhoffm
Is gsod call today? If so, I‘ll join later.
Thomas A Caswell
@tacaswell
Yes, and OK
Jody Klymak
@jklymak
Dev call today at 15:00 EDT (19:00 UTC). Please populate agenda with things that need discussion https://hackmd.io/yeRgrkuRTC6wYEgcJL_SVQ
Bruno Beltran
@brunobeltran
There seems to be a meeting passcode now?
Thomas A Caswell
@tacaswell
should not be..
Bruno Beltran
@brunobeltran
jk needed to refresh hackmd
Thomas A Caswell
@tacaswell
re the NASA funding call, I have also reached out to a couple contacts I have at JPL
hannah
@story645
Anyone know why keypress events wouldn't work well in jupyter ?https://twitter.com/brandon_rhodes/status/1321099267294060549?s=19
hannah
@story645
Thanks @QuLogic! 😁
matrixbot
@matrixbot
physkets Hi! Say I have plots that use some colormap, and display a colorbar. Now, if I want all the colorbars to be of the same "size/extent", do I just set boundaries in colorbar()? Or do I need to make other changes as well?
matrixbot
@matrixbot
physkets Okay, sorry, boundaries is not the right thing... how do I control the extents of the colorbar?
matrixbot
@matrixbot
physkets Setting ticks manually also does not help...
matrixbot
@matrixbot
physkets hist2d does not have an extents argument, unlike imshow.
Jody Klymak
@jklymak
Do yo mean the min and max of the colormapping? Use vmin and vmax in the Norm or hist2d (which will pass to the norm)
matrixbot
@matrixbot
physkets Jody Klymak (Gitter): Yes! the min & max extents. No, setting the vmin & vmax in the Norm with just scale things. That is not what I want.
I have different plots, and I'd like to use the same colorbar for all of them. If I normalize them all, the values will be incorrect. So I need to pre-set the colorbar extents, and then have them plot as per the values obtained form hist2d.
Jody Klymak
@jklymak
Sorry that is not making much sense to me suggest you show what you are doing with code on discourse.matplotlib.org
matrixbot
@matrixbot
hannah
@story645
hey, any of the maintainers want to be on a PyData maintainers meet & greet panel for pydata diversity scholarship recipients? it's Wednesday, Nov. 11, 5-6 PM EST , super low stakes, tends to be very at teh "how to contribute" level
(my very personal opinion is it's good to mix up the folk out there representing the project)
Thomas A Caswell
@tacaswell
I already added it to the agenda for next Tuesday as well
hannah
@story645
yay!
matrixbot
@matrixbot
Cadair Hey could someone who has the permissions do me a favour and kill this Travis build: https://travis-ci.org/github/matplotlib/pytest-mpl/builds/739905148
Cadair it hasn't auto-cancelled and Travis is already painfully slow without waiting for that to finish as well :(
Cadair thanks
Jody Klymak
@jklymak
Suggest you just close and re-open the PR.
matrixbot
@matrixbot
Cadair Well it didn't autocancel for one reason, I didn't expect it to for a close either. It ran eventually anyway, I am now just waiting for it all to run again 😀
Jody Klymak
@jklymak
Are @tacaswell and @anntzer aware of this effort? matplotlib/pytest-mpl#101
matrixbot
@matrixbot
Cadair I did keep an eye on the work aroundGSOC
Jody Klymak
@jklymak
OK, great. Thats what they were working on
matrixbot
@matrixbot
Cadair but I finally cracked and needed to pull the hacks that lived in sunpy out to somewhere else, so I spent way too long this week doing that instead
Thomas A Caswell
@tacaswell
unfortunately I have not had the bandwidth to push that work forward once GCOS ended, but it is still on my (semi-inifinite) queue
would not be offended if someone else worked on it though :)
matrixbot
@matrixbot
Cadair I think the GSOC approach and that approach are different, although maybe close in terms of usability
Jody Klymak
@jklymak
I didn't fully understand the GSOC approach, and it seemed rather burdensome to contributors.
matrixbot
@matrixbot
Cadair This workflow has worked well for sunpy over the last few years with some iteration. I think maybe we have a slightly easier time than mpl core would in terms of potential for subtle layout changes etc.
Thomas A Caswell
@tacaswell
the sunpy approach is to at some point generate a sha of the output and then compare against that in the future?
which means you still track all of the details about what it should be, but do not have to check the full images into the repo
matrixbot
@matrixbot
Cadair yeah, keep those hashes in the repo, and then images externally
Cadair indeed
Thomas A Caswell
@tacaswell
that still leaves you vulnerable to system-to-system changes (e.g. different freetype)
matrixbot
@matrixbot
Cadair we encode the freetype version into the hash library filename, and only do the compare if it matches
Thomas A Caswell
@tacaswell
the GSOC approach is to assume that a developer can from the current tip of the default branch generate a set of "correct" baseline images and then use those as the baseline for any changes you make
if you want to change a test image you change the file name (so it is easy to keep both old and new around)