Misleading Python function error with negative NodeID

[tomdele]

Functions that take as an argument a NodeID will fail if you provide a negative number as a node id (which makes perfect sense).
For the C++ part, we are safe and it is easy to find where the problem comes from but with the python bindings this is a bit more tricky.

Ex :

edge_population.efferent_edges(-1)

TypeError: efferent_edges(): incompatible function arguments. The following argument types are supported:
    1. (self: libsonata._libsonata.EdgePopulation, source: int) -> libsonata._libsonata.Selection
    2. (self: libsonata._libsonata.EdgePopulation, source: List[int]) -> libsonata._libsonata.Selection

Invoked with: <libsonata._libsonata.EdgePopulation object at 0x2aab669176f0>, -1

The outputted error is quite unclear since the int/uint distinction does not exists in python.
Having an error message in the bindings saying that we cannot use NodeID < 0 would be a nice to have feature.

[alkino]

Could Selection throw if there is negative NodeID? Can it be something filling the request?

[tomdele]

Sure that would be perfect.