Notices by Clément Robert :python: (neutrinoceros@fosstodon.org)

@powersoffour I want to laugh, but I fear I might only be getting one half of this joke. What’s the Logan Act ?

@powersoffour ah. I was this close to giving them a try about a year ago, but I went with Daredevil instead (I like following one series in details rather than several superficially). They just went up my list again, thanks !

I just setup my personal schedule for #PyConIt2024. I was pleasantly surprised with the export button which saved me the pain of manually creating calendar events for each talk. Many thanks to the organisers for this feature !

@powersoffour at this time of day ? At this time of year ? In this part of the country ? Localized entirely within your kitchen ?

@powersoffour I can help; let’s make an appointment.

Working on my first actual #rustlang (toy) project, which is nothing fancy, I started noticing how having the `Option` and `Result` enums baked into the standard library forces me to think about edge cases from the start so I know that when my code finally compiles, many rough edges are already solved.
It doesn’t remove the need for tests, but it definitely helps building robust software from the get go !

@powersoffour you’ve been waiting all month to do this one, right ?

Unexpected benefit from using #Python 3.10’s match/case syntax:
I replaced code that was essentially equivalent to
```
axes = {
CARTESIAN: ("x", "y", "z"),
CYLINDRICAL: ("r", "theta", "phi"),
}[geometry]
```
with
```
match geometry:
case CARTESIAN:
axes = ("x", "y", "z")
case CYLINDRICAL:
axes = ("r", "theta", "phi")
```
Which is equivalent, right ?
But the *coverage* is not necessarily so !

In fact one of my supported cases was never tested (and, of course, broken), but I would never have figured it out with the old code: all lines were being hit when the dictionary was initialised !

Initially I was motivated to switch to newer syntax because it supposedly will help catching missing cases in the future (combining enums and `typing.assert_never`), but I didn't except to find an existing bug !

Using gcc’s ffast-math and making my code Fast and Spurious.

@powersoffour maybe I didn’t get your question ? I’m also assuming that 30min is a normal amount of time for an email to be delayed, which hasn’t been true for at least 15 years at this point 😅

@powersoffour maybe 2 to 6 hours ?

How do you eat a binary elephant ?

Saying "no" to pull requests that just add functionality that hasn't been previously discussed or identified as needed may be my least favourite thing about maintaining code...
I think it's necessary to raise awareness in fly-by contributors that these create long term workload for *other* people. Though, no matter how much I sugar-coat my "no", I always feel like I'm being the vilain of someone else's story...

#Foss #maintenance #GitHub