Revisiting coding convention in build123d documentation on importing build123d in light of use of multiple code-CAD libraries in PartCAD

[kcleung]

Currently, the Build123D documentation encourages users to import build123d by:

from build123d import *

for the sake of simplicity

However, thanks to PartCAD, it is much easier to reuse other parts created by Build123D or other code-CAD systems in public repositories.

This will make it more likely for a build123d part to be imported together with other python-based parts such as a cadquery part.

Therefore, moving forward, to avoid the risk of namespace collision, would it be a good idea to call build123d each time:

import build123d

build123. ......

[gumyr]

It's up to the user how they do the import but the documentation is for build123d users and represents the most simple and clear way to use it. The documentation will not be changed in this way.