Thomas Robitaille 🇪🇺

You can now follow me on: @astrofrog" target="_blank" rel="nofollow noopener">fosstodon.org/@astrofrog bsky.app/profile/astrof… I will no longer be posting from Twitter/X going forward 👋

@ForrestTheWoods @ianhi7919 @matplotlib You can try playing with the dpi= option to scatter_density if you want to make the pixels of the density map larger, which might visually be similar to making the points larger.

@mileslucas_ Some dependencies of astropy are optional - to install astropy with all its dependencies, do: pip install astropy[all] If you still run into any issues after this, please let us know at github.com/astropy/astropy - thanks!

@maximetrebitsch @Anyway_the_wind @asclnet Please cite the Zenodo entry here: zenodo.org/record/3558614… - thanks!

Astrotwitter - anyone know how to cite the spectral_cube python package?

Excited to announce @aperio_software is hiring - come and work with @StuartMumford @DrewLeonard42 and myself on exciting open-source scientific projects! (we are involved in @astropy, @glueviz, @WWTelescope and more)

Come work with me! @WWTelescope and @glueviz are searching for a research software engineer eager to join a multidisciplinary team that's advancing the frontiers of scientific data visualization. Details? Details: 🧵 bit.ly/rse2021

When people said wildlife was doing well as a result of #lockdown, I did not expect to see a 🦊 building a ⛄️ in my garden 🤯

Ministers apparently not familiar with the Cobra effect... (en.wikipedia.org/wiki/Cobra_eff…)

I almost feel like some people have misunderstood something I wrote on Twitter and/or are distorting what I am saying when quoting me. But that shouldn't be possible, right?!? 😱🤣

@hannorein Yes my complaints about Apple was perhaps tangential to the point of the thread, and unfortunately seems to have started some Mac vs Linux vs Windows flame wars in the comments 😂

@hannorein I'm not against change - my main goal here was to push back against people who will update immediately after major releases like this and who will then be unhappy/unproductive when things don't work. I'm just suggesting waiting for issues to be ironed out.

And yes I know that upgrading to the new Apple hardware is far more risky - in fact it is almost guaranteed to not work smoothly unless all you do is browse the internet and check emails!

Epilogue: yes, I know that upgrading to Big Sur might work just fine for some, but I also know that it has broken things for others. The key message here is that by upgrading *this early* you are taking unnecessary risks (and this is true of every major OS X version)

Researchers who use Macs, PLEASE don't upgrade to MacOS X Big Sur or buy a new M1 mac yet: a short thread. (1/n)

@bigreddot @bokeh VisPy currently doesn't import (github.com/vispy/vispy/is…), which a number of packages depend on including napari and glueviz.

@te_pickering I don't debate that there's a huge difference - my point is more that the Big Sur changes are significant *enough* to break people's workflows (especially since the average researcher isn't using Python 3.9)

@te_pickering So while I wouldn't have made a big deal out of your average MacOS X 10.x upgrade, Big Sur from what I can see has had by far the most disruption to the Python ecosystem which is yet to be resolved.

@te_pickering These issues are going to require a new patch release of Python 3.8.x and 3.9.x and won't even be fixed in older Pythons. It's not clear how soon those patch releases will happen.