Tom Van Mele

@gonzalocasas recent versions of the mesh data structure use exclusively int keys. therefore it is no longer necessary to use `repr` and `literal_eval`. the current version of the mesh uses...

could you make the JSON available somewhere? i will try to add a fix for this, but i would like to make sure i am fixing the correct problem...

@salmamzfr in recent versions this compatibility problem should be solved. can you check if this issue can be closed?

not sure if this is the source of the problem, but on the CPython side you seem to be loading a `Mesh` and on the IronPython side a `Network`. could...

could you send me the json file(s) that you have been using?

```python import os from compas.datastructures import Network from compas_rhino.artists import NetworkArtist HERE = os.path.dirname(__file__) FILE = os.path.join(HERE, 'Datastructures', 'pr_net') net = Network.from_json(FILE) artist = NetworkArtist(net) artist.draw() ``` ![Screenshot 2020-11-23 at...

```python import os from compas.datastructures import Mesh from compas_rhino.artists import MeshArtist HERE = os.path.dirname(__file__) FILE = os.path.join(HERE, 'Datastructures', 'pr_mesh') mesh = Mesh.from_json(FILE) artist = MeshArtist(mesh) artist.draw() ``` ![Screenshot 2020-11-23 at...

@salmamzfr i can't really reproduce the problem. as you can see from the snippets and corresponding screenshots, for me these files just work...

> Also, I'm wondering if we can have a link to the source code in the API doc, maybe consider using sphinx.ext.viewcode? Examples can be found in pytorch's API doc...

> Other than this, is there anything else that developers need to pay attention to in order to conform to the existing compas doc convention? we have not yet released...