Tom Van Mele

i don't see the point of `git submodules` in this context. i also don't think the concern of @gonzalocasas is related to keeping the repos synced, but rather the individually...

yes, we could implement the "r" versions of the magic methods, but i don't know if there would be any unwanted side-effects... ```python def __rmul__(self, factor): ... ```

i agree, that is why never implemented the "r" versions. i think it is easy enough for the user to be explicit about their intent by writing the compas object...

do you have Rhino plugins like Ladybug installed by any chance?

@gonzalocasas is this resolved?

in general, if we can use something that already exists, we should. and since we stopped caring about IronPython, there is no need to make a pure Python version...

i would double check your test because the result seems correct to me... ```python from compas.geometry import Point, Line from compas_view2.app import App line = Line(Point(-6.0, 0.0, 0.0), Point(7.5, 0.0,...

`t` is expressed wrt to the direction vector, which is a unit vector. therefore `1.0` seems to make sense, since `Point(5, 0, 0)` is `Point(-6, 0, 0) + Vector(1, 0,...

the difference with the C++ implementation lies mostly in the division by the squared length of the vector of the line, but that is implicitly included in the Python implementation...

no, you're right. it should be possible to combine the two. it was not clear to me from your question/statements that this was the problem...