Explanation: Python is a programming language. Numpy is a library for python that makes it possible to run large computations much faster than in native python. In order to make that possible, it needs to keep its own set of data types that are different from python’s native datatypes, which means you now have two different bool types and two different sets of True and False. Lovely.

Mypy is a type checker for python (python supports static typing, but doesn’t actually enforce it). Mypy treats numpy’s bool_ and python’s native bool as incompatible types, leading to the asinine error message above. Mypy is “technically” correct, since they are two completely different classes. But in practice, there is little functional difference between bool and bool_. So you have to do dumb workarounds like declaring every bool values as bool | np.bool_ or casting bool_ down to bool. Ugh. Both numpy and mypy declared this issue a WONTFIX. Lovely.

@breadsmasher@lemmy.world
link
fedilink
English
2
edit-2
4M

Well, yes exactly

  1. Create fixes
  2. Request merge. assume denied
  3. Fork numpy and add your changes there
  4. after just continue to pull new changes over from source of the fork and deal with any merge issues with the fix
@fossphi@lemm.ee
link
fedilink
English
114M

Fork numpy

I have a feeling that you’re grossly underestimating the magnitude of this endeavour

Im making no estimation one way or the other

That’s incredibly inconvenient.

Thats what adding strong typing does for you

Create a post

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

  • Posts must be relevant to programming, programmers, or computer science.
  • No NSFW content.
  • Jokes must be in good taste. No hate speech, bigotry, etc.
  • 1 user online
  • 120 users / day
  • 257 users / week
  • 744 users / month
  • 3.72K users / 6 months
  • 1 subscriber
  • 1.47K Posts
  • 32.3K Comments
  • Modlog