Stephen Gruppetta @s_gruppetta@qoto.org

Since moving from #MATLAB to #Python all those years ago, I had used `meshgrid()` the "non-ideal" way for so long–it was just habit from many years of using it in MATLAB

But now I know better, and my memory usage will be happy in so many cases!!

https://thepythoncodingbook.com/2022/05/28/numpy-meshgrid/

#programming #coding #NumPy #Matplotlib

If you've come to #Python directly from #MATLAB, as I have, and you used to use `meshgrid` in MATLAB, you possibly use it in exactly the same way in Python?

I did for a very long time…

But Python has more options which can save you execution time and memory

Here's my exploration of #NumPy's #meshgrid and other related functions

https://thepythoncodingbook.com/2022/05/28/numpy-meshgrid/

#programming #coding #LearnPython #LearnToCode #ScientificProgramming #Visualisation

@paul @mborus on the web platform it depends on the server, I believe. For phone Apps, I don't know (I use the web platform on a phone, too, it's easier that way!!)

…time to get inspiration for some other #FourierOptics #Python tutorials to follow on from this, which remains the most popular post on the blog, **by far**

https://thepythoncodingbook.com/2021/08/30/2d-fourier-transform-in-python-and-fourier-synthesis-of-images/

#programming #FourierTransform #coding

My favourite textbook of all time – had been in storage for a while as we did a long, convoluted, house move…

It's back, safe and sound, nicely weathered and thumbed from all those years of use…

---

PS: just realised it's my wife's copy, not mine. **I Want My One Back!** (It's still in a box, somewhere…)

#Python #Fourier #FourierTransform #FourierOptics #programming

@laufi Plus there was this article shared on here a short while ago by @laurentabbal

https://forge.aeif.fr/laurentabbal/publication-sur-twitter-et-mastodon-avec-python/-/blob/main/publication_sur_twitter_et_mastodon_avec_python.ipynb

@laufi https://mastodonpy.readthedocs.io/en/stable/

@trinsec @mborus So toots will become mutable for us too, soon. Hurray!

@mborus Here's they're not. Not yet, anyway. Can't wait…

Some are confused about the terms "mutable" and "immutable" in #Python or #programming in general.

A Toot could be a good example but it seems that this is not the same for everyone (in the process of changing?)

For me, at the moment, a Toot is "immutable" –> Once it's published, it cannot be changed. I can delete it and replace it with a new one, but I cannot change the actual Toot

But for others (and from what I gather, for all of us in the near future?), a Toot is "mutable" if they can change the **same** toot, not just replace it with a new one

---

Let's say you have a string, an immutable type in Python:

`name = "Stephen"`

You change your mind and want it to be upper case:

`name = name.upper()`

You're creating a copy of the string which is uppercase and replacing the old string (which is binned) with the new one

---

That's not the case for a list, for example, which is mutable:

`numbers = [2, 5, 9]`
`numbers.append(100)`

You change the **same** list, not create a new one

---

Will Toots change from being an immutable type to a mutable type for all of us soon?

#coding #LearnToCode #LearnPython

@sibin although I should point out that that's just in one local accent/dialect. It's actually not that common in Britain, at all

But hey, I don't want to spoil the joke!