GH_Point in python component - Grasshopper2024-03-29T13:52:19Zhttps://www.grasshopper3d.com/forum/topics/gh-point-in-python-component?commentId=2985220%3AComment%3A1761509&xg_source=activity&feed=yes&xn_auth=noI agree. That said, dynamical…tag:www.grasshopper3d.com,2017-06-01:2985220:Comment:17615092017-06-01T12:11:53.992ZAnders Holden Deleuranhttps://www.grasshopper3d.com/profile/AndersHoldenDeleuran
<p>I agree. That said, dynamically typed doesn't necessarily imply not being explicitly (as in not being ambiguous) typed (such as in the case here). I personally wouldn't use a statically typed language unless I will be compiling (for the benefits of speed, modularity and <span>compilation errors)</span>, but I can certainly see why others would (again, personal preference does matter).</p>
<p>I agree. That said, dynamically typed doesn't necessarily imply not being explicitly (as in not being ambiguous) typed (such as in the case here). I personally wouldn't use a statically typed language unless I will be compiling (for the benefits of speed, modularity and <span>compilation errors)</span>, but I can certainly see why others would (again, personal preference does matter).</p> Quick best practice/tip: I wo…tag:www.grasshopper3d.com,2017-06-01:2985220:Comment:17613902017-06-01T07:16:34.936ZAnders Holden Deleuranhttps://www.grasshopper3d.com/profile/AndersHoldenDeleuran
<p>Quick best practice/tip: I would advise against using the <em>from foo import * </em>style. This not only makes it difficult/impossible to trace the namespace/module a function/class comes from, it can also lead to name conflicts if two (or more) namespaces have an object with the same name etc. More to the point though, within the context of GHPython, you'll be robbing yourself of what little intellisense we do have ;)<br></br><br></br>The current style I (and I think most of us here) use would be…</p>
<p>Quick best practice/tip: I would advise against using the <em>from foo import * </em>style. This not only makes it difficult/impossible to trace the namespace/module a function/class comes from, it can also lead to name conflicts if two (or more) namespaces have an object with the same name etc. More to the point though, within the context of GHPython, you'll be robbing yourself of what little intellisense we do have ;)<br/><br/>The current style I (and I think most of us here) use would be something like (you could of course also import child namespaces):<br/><br/><a href="http://storage.ning.com/topology/rest/1.0/file/get/2769293511?profile=original" target="_self"><img src="http://storage.ning.com/topology/rest/1.0/file/get/2769293511?profile=original" width="306" class="align-full"/></a><br/><br/><br/><br/> </p> Hi Tom,
Thank you very much,…tag:www.grasshopper3d.com,2017-05-31:2985220:Comment:17610652017-05-31T19:33:39.423ZNicholas Rawitscherhttps://www.grasshopper3d.com/profile/NicolasRawitscher
<p>Hi Tom,</p>
<p></p>
<p>Thank you very much, it worked perfectly.</p>
<p></p>
<p>Nicholas</p>
<p>Hi Tom,</p>
<p></p>
<p>Thank you very much, it worked perfectly.</p>
<p></p>
<p>Nicholas</p>