Search
293 results for “neutrinoceros”
-
I can't quite convince myself yet that all inheritance/coupling is intrinsically bad, but I'm more and more recognising abstract base classes (ABCs) and #mixin classes as anti-patterns because they hinder #testability, which to me is key to quality software; #ABCs and mixins are by construction impossible to test on their own, and both patterns only make sense if a language supports inheritance, so it seems that the simplest option to avoid them is to get rid of inheritance altogether.
-
Update: I am now embracing lock files in CI in most packages I control.
I’m very used to CI being a gamble: every time I push with confidence and see CI going red, my first reflex is to suspect something changed in the environment. I'm just coming to terms with the idea that *it doesn't need to be this way*; especially in projects that already a special CI job whose sole purpose is to catch incoming incompatibilities, it makes more sense that *other* jobs just be stable.
#astraluv #Python -
The thing with #astraluv is I don't think I understand lock files, and how they’re supposed to be used/maintained. Maybe it's because I mainly develop and maintain #Python libraries and it doesn't make as much sense in that space: I need to be able to test a range of versions of my dependencies (I have little control over my users’ environment), and lockfiles tend to add artificial restrictions to these ranges, to the benefit of (maybe ?) my immediate confort but to the detriment of my users.
-
@__sharky__ @bouncing
As far as I understand, stuff like `setattr` or any sort of cache needs to be handled with care in multi-threading. Again, this is already true with the GIL, it's just that I never considered the possibility of my code running concurrently at all and #freethreading #Python just gave me the push I needed to think about it. I also maintain packages filled with C and Cython extensions, so I need to know this stuff anyway. -
@bouncing no, you're right ! It’s just that my own pure Python libraries were *not* thread safe yet since I never considered it before.
Yet, #freethreading being marked as experimental (and overall brand new) I don't think it’d hurt to also test pure Python projects that already claim thread safety: you may discover the GIL was actually hiding bugs, or better yet, you might find edge cases where Python itself breaks.
-
Resources that helped me a lot getting started:
How to even get #freethreading #Python in CI, by @hugovk
https://dev.to/hugovk/help-test-python-313-14j1and the dedicated blog by the Quansight team
https://py-free-threading.github.io/Many thanks to the authors !
-
Getting my packages ready for #freethreading #Python (PEP 703) means I need to learn all-things-threads for the first time.
This wasn't obvious to me at first, but you can't just run your existing *single-threaded* tests suite: you also need to check how your objects behave in a multi-threaded context.
So you need new tests. Where should you even start ? A good strategy is to write tests around mutating methods. And boy am I glad that I already had an aversion for mutability. -
#astraluv 0.2.15 is out and includes a new tool that I’ve wanted for so long: `uv pip tree` displays the whole dependency tree in your current virtualenv !
https://pypi.org/project/deptree/ Already implemented this but it's much more convenient to have a version of this tool that doesn’t actively “pollute" the environment it’s meant to display.
kudos to @charliermarsh and team 🎉
-
I wonder what #condaforge’s plan is to handle the transition to #Numpy 2.0 (expected to land about a month from now). My guess is that all build-time dependent packages will probably need to be rebuilt ? I don’t really know who/where to ask about this, so any help would be welcome !
(If Numpy 2.0 is news to you and makes you nervous I suggest reading https://github.com/numpy/numpy/issues/24300#issue-1828940995)
-
Today I'm celebrating my first can-of-worms bug (a bug that’s discovered while fixing another bug) in #astropy ! 🎉
It’s a bit paradoxical: these situations are not exactly pleasant to work through, but I find that it’s actually a signal of extreme #codequality that it’s only happening *now*, after two months on the job just tracking #bugs down ! 🪲
-
New bio !
This week was my last as a researcher, and starting tomorrow I'll work as a contractual research software engineer for the #Astropy project !
I am thrilled about onboarding this thriving community and excited that fixing bugs is now my job instead a distraction from it ! -
This year’s masking policy was “wear a mask if you want, and some will be available on demand”. Clearly it didn’t work for me. I also haven’t heard anything about the matter from the staff while on site.
Sadly, I don’t think I’ll come back next year if the policy isn’t revised.
-
I’m seeing a lot of toots from people who came back from #PyConUS2024, and tested negative to COVID. Meanwhile, I’m just back from #PyConIt2024 : I don’t think I was ever that sick in my entire adult life, and I was one of maybe two to three attendees wearing a mask.
-
Today I'm celebrating my first can-of-worms bug (a bug that’s discovered while fixing another bug) in #astropy ! 🎉
It’s a bit paradoxical: these situations are not exactly pleasant to work through, but I find that it’s actually a signal of extreme #codequality that it’s only happening *now*, after two months on the job just tracking #bugs down ! 🪲
-
Today I'm celebrating my first can-of-worms bug (a bug that’s discovered while fixing another bug) in #astropy ! 🎉
It’s a bit paradoxical: these situations are not exactly pleasant to work through, but I find that it’s actually a signal of extreme #codequality that it’s only happening *now*, after two months on the job just tracking #bugs down ! 🪲
-
Today I'm celebrating my first can-of-worms bug (a bug that’s discovered while fixing another bug) in #astropy ! 🎉
It’s a bit paradoxical: these situations are not exactly pleasant to work through, but I find that it’s actually a signal of extreme #codequality that it’s only happening *now*, after two months on the job just tracking #bugs down ! 🪲
-
Today I'm celebrating my first can-of-worms bug (a bug that’s discovered while fixing another bug) in #astropy ! 🎉
It’s a bit paradoxical: these situations are not exactly pleasant to work through, but I find that it’s actually a signal of extreme #codequality that it’s only happening *now*, after two months on the job just tracking #bugs down ! 🪲
-
New bio !
This week was my last as a researcher, and starting tomorrow I'll work as a contractual research software engineer for the #Astropy project !
I am thrilled about onboarding this thriving community and excited that fixing bugs is now my job instead a distraction from it ! -
New bio !
This week was my last as a researcher, and starting tomorrow I'll work as a contractual research software engineer for the #Astropy project !
I am thrilled about onboarding this thriving community and excited that fixing bugs is now my job instead a distraction from it ! -
New bio !
This week was my last as a researcher, and starting tomorrow I'll work as a contractual research software engineer for the #Astropy project !
I am thrilled about onboarding this thriving community and excited that fixing bugs is now my job instead a distraction from it ! -
New bio !
This week was my last as a researcher, and starting tomorrow I'll work as a contractual research software engineer for the #Astropy project !
I am thrilled about onboarding this thriving community and excited that fixing bugs is now my job instead a distraction from it !