On 10.10.2016 17:28, François wrote:
> Hello,
>
> I suspect the copy_property function not to be thread safe. Remember that
> the issue I observe occurs when I re-use the predecessor map returned
> by shortest_distance. The copy_property is then called from
> topology/__init__.py:1441 and the parameter full is None.

I didn't realize all the workers shared a reference to the same graph.

Indeed this can be improved. To be honest, thread safety from the python
side is something that I often do not pay attention to, since it is almost
never worth it. But please open an issue in the website to make
copy_property() thread safe, and I will get around to it.

Best,
Tiago

--
Tiago de Paula Peixoto <[hidden email]>


_______________________________________________
graph-tool mailing list
[hidden email]
https://lists.skewed.de/mailman/listinfo/graph-tool

signature.asc (817 bytes) Download Attachment

--
Tiago de Paula Peixoto <tiago@skewed.de>

---

If you reply to this email, your message will be added to the discussion below:

http://main-discussion-list-for-the-graph-tool-project.982480.n3.nabble.com/shortest-distance-concurrency-graph-view-tp4026743p4026753.html

To start a new topic under Main discussion list for the graph-tool project, email ml-node+s982480n2141189h16@n3.nabble.com
To unsubscribe from Main discussion list for the graph-tool project, click here.
NAML