Fix output of nest.spatial in Read the Docs

[med-ayssar]

Fixes #2513

[jessica-mitchell]

@med-ayssar Thanks for looking into this, I just checked the output, and it looks like its all there 🎉

I think in a separate PR we can look at combining the two spatial sections of the API

[med-ayssar]

@med-ayssar Thanks for looking into this, I just checked the output, and it looks like its all there tada

I think in a separate PR we can look at combining the two spatial sections of the API

What do you mean by combining here? I think that I am missing some context.

[jessica-mitchell]

There is nest.spatial and nest.lib.spatial - and these are separate sections in Read the Docs API, for "spatially-distributed nodes" and "spatial distributions", which is a bit confusing.
I want to know if we can either move lib.spatial into spatial or rename it. And clarify any relevant differences in the docs or simply combine them if that makes sense.

[hakonsbm]

I have just a couple suggestions for the code.

[Helveg]

We should avoid that distance is created at import time, which we can do by moving this logic to nest.spatial

[Helveg]

There is nest.spatial and nest.lib.spatial - and these are separate sections in Read the Docs API, for "spatially-distributed nodes" and "spatial distributions", which is a bit confusing. I want to know if we can either move lib.spatial into spatial or rename it. And clarify any relevant differences in the docs or simply combine them if that makes sense.

I'm also highly in favor of merging the 2 modules! It's confusing.

[Helveg]

Looks good. nest.spatial.distance works, import time code is avoided and the docs render and reference to distance just fine.