News for hackers. Stuff that matters.
Re:More Itertools by benkuykendall on Monday May 27, 2024 @10:45PM (#40496874)
My favorite function here is more_itertools.one. Especially in something like a unit test, where ValueErrors from unexpected conditions are desirable, we can use it to turn code like

  results = list(get_some_stuff(...))
  assert len(results) = 1
  result = results[0]
into

  result = one(get_some_stuff(...))
I guess you could also use tuple-unpacking:

  result, = get_some_stuff(...)
But the syntax is awkward to unpack a single item. Doesn't that trailing comma just look implausible? (Also I've worked with type-checkers that will complain when a tuple-unpacking could potentially fail, while one has a clear type signatures Iterable[T] -> T.)
Re:More Itertools by rjmill on Monday May 27, 2024 @10:54PM (#40496917)
You can also do

  [result] = get_some_stuff(...)
Re:More Itertools by adammarples on Tuesday May 28, 2024 @06:20AM (#40499191)
Do tuple unpacking like this

result, _* = iterable()

Re:More Itertools by plyp on Tuesday May 28, 2024 @12:54PM (#40502788)
That’s not the same though. Your unpacking allows for any non-empty iterable while OPs only allows for an iterable with exactly one item or else it throws an exception.