News for hackers. Stuff that matters.
Re:NumPy 1.16 is the last release to support Python 2.7 by CJefferson on Monday January 21, 2019 @06:48AM (#18959690)
The problem I had with python is that (because it is dynamically typed), and quite a few methods take both bytes and strings, it can be tricky to track what you have and often things don't break until you feed in a non-UTF8 string.

I found it much easier in Rust, as the two types are just distinct, and an incorrect program just fails to compile.

Re:NumPy 1.16 is the last release to support Python 2.7 by orf on Monday January 21, 2019 @09:44AM (#18960659)
In Python 3 they are two distinct types as well.
Re:NumPy 1.16 is the last release to support Python 2.7 by lmm on Monday January 21, 2019 @11:04AM (#18961212)
They're not really "types" when you only find out at runtime.
Re:NumPy 1.16 is the last release to support Python 2.7 by joshuamorton on Monday January 21, 2019 @03:11PM (#18963204)
When handling tricky string issues, my first step is usually to explicitly type annotate the code (using mypy annotations). This makes string handling and tracking much simpler.
Re:NumPy 1.16 is the last release to support Python 2.7 by orf on Monday January 21, 2019 @11:10AM (#18961263)
Sure they are.