Alejandro Candioti

Any defensive mechanism that could be placed here? So it fails to load backend but it does not crash the whole import

Yes, I know we couldn't repro but I was wondering if we can skip invalid backend names here: ```python backend_config = {} for backend, info in backend_info.items(): if "default_config" not...

We can emit a warning and ignore that backend from the dict of valid backends. To me that follows current approach of error handling in the backend module (for example,...

To check for name validity we can use `str.isidentifier`: ``` In [5]: str.isidentifier('nx-loopback') Out[5]: False In [6]: str.isidentifier('nx_loopback') Out[6]: True ```

@eriknw @dschult any change you can take a look at this small one? This should remove the limitation/restriction for backend graph types to implement `is_directed` and `is_multigraph`

> IIUC, this is basically "moving" the requirement for `is_directed` and `is_multigraph` from methods on the backend graph class to functions in the backend. From the perspective of the backend...

> Thanks @amcandio ! Property-based testing has definitely been on the radar/wishlist for a while! > > I'm also +1 on the `hypothesis` framework as that seems to be a...

Update from latest community discussions: we are agreed that is better to make hypothesis a test dependency and optional runtime dependency (so only users that import the specific module will...

FYI @dschult @rossbar I updated the framework as we discussed. The new description explains usage and that it is an optional dependency. I also enhanced the framework to explain how...

> Thanks @amcandio , I think type-based dispatching is a very interesting direction to explore! Hooking it up to the backend system is of course an excellent idea; one thing...