pyg4ometry 1.3.2__tar.gz → 1.3.4__tar.gz

{pyg4ometry-1.3.2 → pyg4ometry-1.3.4}/.pre-commit-config.yaml

@@ -28,19 +28,19 @@ repos:
         args: ["--line-length", "100"]
 
   - repo: https://github.com/asottile/blacken-docs
-    rev: "1.18.0"
+    rev: "1.19.1"
     hooks:
       - id: blacken-docs
         additional_dependencies: [black==23.3.0]
 
   - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: "v0.6.9"
+    rev: "v0.8.6"
     hooks:
       - id: ruff
         args: ["--fix", "--show-fixes"]
 
   - repo: https://github.com/mgedmin/check-manifest
-    rev: "0.49"
+    rev: "0.50"
     hooks:
       - id: check-manifest
         stages: [manual]
@@ -76,7 +76,7 @@ repos:
         types_or: [yaml, markdown, html, css, scss, javascript, json]
 
   - repo: https://github.com/kynan/nbstripout
-    rev: "0.7.1"
+    rev: "0.8.1"
     hooks:
       - id: nbstripout
         args:
@@ -87,7 +87,7 @@ repos:
           ]
 
   - repo: https://github.com/pre-commit/mirrors-clang-format
-    rev: "v19.1.1"
+    rev: "v19.1.6"
     hooks:
       - id: clang-format
         types_or: [c++, c, cuda]

{pyg4ometry-1.3.2 → pyg4ometry-1.3.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: pyg4ometry
-Version: 1.3.2
+Version: 1.3.4
 Summary: Geometry package for high energy physics (Geant4, Fluka)
 Author-Email: "Stewart T. Boogert" <stewart.boogert@rhul.ac.uk>
 Maintainer-Email: "Stewart T. Boogert" <stewart.boogert@rhul.ac.uk>
@@ -729,10 +729,10 @@ Carlo (Geant4 and Fluka) geometries.
 
 [![PyPI](https://img.shields.io/pypi/v/pyg4ometry?logo=pypi)](https://pypi.org/project/pyg4ometry/)
 ![GitHub tag (latest by date)](https://img.shields.io/github/v/tag/g4edge/pyg4ometry?logo=git)
-[![GitHub Workflow Status](https://img.shields.io/github/checks-status/g4edge/pyg4ometry/main?label=main%20branch&logo=github)](https://github.com/pyg4ometry/pyg4ometry/actions)
+[![GitHub Workflow Status](https://img.shields.io/github/checks-status/g4edge/pyg4ometry/main?label=main%20branch&logo=github)](https://github.com/g4edge/pyg4ometry/actions)
 [![pre-commit](https://img.shields.io/badge/pre--commit-enabled-brightgreen?logo=pre-commit&logoColor=white)](https://github.com/pre-commit/pre-commit)
 [![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black)
-[![Codecov](https://img.shields.io/codecov/c/github/g4edge/pyg4ometry?logo=codecov)](https://app.codecov.io/gh/pyg4ometry/pyg4ometry)
+[![Codecov](https://img.shields.io/codecov/c/github/g4edge/pyg4ometry?logo=codecov)](https://app.codecov.io/gh/g4edge/pyg4ometry)
 ![GitHub issues](https://img.shields.io/github/issues/g4edge/pyg4ometry?logo=github)
 ![GitHub pull requests](https://img.shields.io/github/issues-pr/g4edge/pyg4ometry?logo=github)
 ![License](https://img.shields.io/github/license/g4edge/pyg4ometry)

{pyg4ometry-1.3.2 → pyg4ometry-1.3.4}/README.md

@@ -5,10 +5,10 @@ Carlo (Geant4 and Fluka) geometries.
 
 [![PyPI](https://img.shields.io/pypi/v/pyg4ometry?logo=pypi)](https://pypi.org/project/pyg4ometry/)
 ![GitHub tag (latest by date)](https://img.shields.io/github/v/tag/g4edge/pyg4ometry?logo=git)
-[![GitHub Workflow Status](https://img.shields.io/github/checks-status/g4edge/pyg4ometry/main?label=main%20branch&logo=github)](https://github.com/pyg4ometry/pyg4ometry/actions)
+[![GitHub Workflow Status](https://img.shields.io/github/checks-status/g4edge/pyg4ometry/main?label=main%20branch&logo=github)](https://github.com/g4edge/pyg4ometry/actions)
 [![pre-commit](https://img.shields.io/badge/pre--commit-enabled-brightgreen?logo=pre-commit&logoColor=white)](https://github.com/pre-commit/pre-commit)
 [![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black)
-[![Codecov](https://img.shields.io/codecov/c/github/g4edge/pyg4ometry?logo=codecov)](https://app.codecov.io/gh/pyg4ometry/pyg4ometry)
+[![Codecov](https://img.shields.io/codecov/c/github/g4edge/pyg4ometry?logo=codecov)](https://app.codecov.io/gh/g4edge/pyg4ometry)
 ![GitHub issues](https://img.shields.io/github/issues/g4edge/pyg4ometry?logo=github)
 ![GitHub pull requests](https://img.shields.io/github/issues-pr/g4edge/pyg4ometry?logo=github)
 ![License](https://img.shields.io/github/license/g4edge/pyg4ometry)

pyg4ometry-1.3.4/docs/source/manual/cli.rst

@@ -0,0 +1,97 @@
+.. _cli:
+
+======================
+Command Line Interface
+======================
+
+pyg4ometry provides a command line interface that is installed along with the package. Outside
+of Python, you will find the executable :code:`pyg4ometry`. This can be executed in a terminal
+without the need to start Python.
+
+Any example and test data may be used by prefixing the path with :code:`g4edgetestdata/`, e.g.
+:code:`pyg4ometry -i g4edgetestdata/gdml/001_box.gdml -v`. Files are specified from the
+`data` directory here: https://github.com/g4edge/testdata/tree/main/data.
+
+The following commands are available: ::
+
+    Usage: pyg4ometry [options]
+
+    Options:
+      -h, --help            show this help message and exit
+      -a, --analysis        geometry information
+      -b, --bounding        calculate bounding box
+      -c, --checkoverlaps   check overlaps
+      -C CLIP, --clip=CLIP  clip to a box of full widths px,py,pz in mm
+      -d COMPAREFILE, --compare=COMPAREFILE
+                            comp(a)re geometry
+      -e APPENDFILE, --append=APPENDFILE
+                            append geometry
+      -f FEATUREDATA, --feature=FEATUREDATA
+                            feature extraction from simple geometry
+                            (planeQuality,circumference)
+      -F FEATUREFILE, --featureExtractOutput=FEATUREFILE
+                            feature extract output
+      -i INFILE, --file=INFILE
+                            (i)nput file (gdml, stl, inp, step)
+      -I INFO, --info=INFO  information on geometry (tree, reg, instance)
+      -l LVNAME, --logical=LVNAME
+                            extract logical LVNAME
+      -m MATERIAL, --material=MATERIAL
+                            material dictionary ("lvname":"nist")
+      -n, --nullmesh        disable null mesh exception
+      -o OUTFILE, --output=OUTFILE
+                            (o)utout file (gdml, inp, usd, vtp)
+      -p PLANECUTTER, --planeCutter=PLANECUTTER
+                            add (p)plane cutter -p x,y,z,nx,ny,nz
+      -P CUTTERFILE, --planeCutterOutput=CUTTERFILE
+                            plane cutter output file
+      -r TX,TY,TZ, --rotation=TX,TY,TZ
+                            rotation (Tait-Bryan) tx,ty,tz (used with
+                            append/exchange)
+      -s PYTHONSOLID, --solid=PYTHONSOLID
+                            solid in python constructor syntax (used with
+                            exchange). Registry must be reg and _np used for numpy
+      -S SCALE, --gltfScale=SCALE
+                            scale factor for gltf conversion
+      -t X,Y,Z, --translation=X,Y,Z
+                            translation x,y,z (used with append/exchange)
+      -v, --view            view geometry
+      -V, --verbose         verbose script
+      -x LVNAME, --exchange=LVNAME
+                            replace solid for logical volume, LVNAME is logical
+                            volume name
+      -z, --citation        print citation text
+
+
+Viewing Geometry
+----------------
+::
+
+  pyg4ometry -i box.gdml -v
+
+
+Using g4edge test data: ::
+
+  pyg4ometry -i g4edgetestdata/gdml/CompoundExamples/bdsim/vkickers.gdml -v
+
+
+Converting Geometry
+-------------------
+
+Conversion can be done directly by specifying an output format. If this is different
+from the input format, it will be converted automatically. ::
+
+  pyg4ometry -i g4edgetestdata/gdml/001_box.gdml -o box.inp
+
+
+Rotations and Translations
+--------------------------
+
+Various commands can be used in combination with a single rotation and translation. In
+each case, the rotation is a Tait-Bryan rotation in radians and the translation is in mm.
+These are given as three comma-separated numbers with no spaces. Fractions and `pi` can be used.
+e.g.: ::
+
+  -r 0,pi/2,0
+  -r -3*pi/2,0,0
+  -t 10,123.45,100

{pyg4ometry-1.3.2 → pyg4ometry-1.3.4}/docs/source/manual/index.rst

@@ -16,6 +16,7 @@ User Manual
    comparing
    analysing
    rendering
+   cli
 
 
 Indices and tables

{pyg4ometry-1.3.2 → pyg4ometry-1.3.4}/docs/source/manual/loading.rst

@@ -9,16 +9,24 @@ load a file, and it creates a Registry object (see :ref:`introduction-registry`)
 the model. The registry is the final object from a reader, and its top-most volume can be
 used for visualisation or other operations.
 
-.. tab:: GDML
+Here, we use example files provided in the g4edge-testdata package that can be installed with:
+::
+
+    pip install g4edge-testdata
+
+
+An instance of the test data can be used to access any file.
 
-  In directory :code:`pyg4ometry/test/gdmlG4examples/ChargeExchangeMC/`
+.. tab:: GDML
 
   .. code-block:: python
     :linenos:
 
     import pyg4ometry
+    import g4edgetestdata
 
-    r = pyg4ometry.gdml.Reader("lht.gdml")
+    d = g4edgetestdata.G4EdgeTestData()
+    r = pyg4ometry.gdml.Reader(d["gdml/ChargeExchangeMC/lht.gdml"])
     l = r.getRegistry().getWorldVolume()
     v = pyg4ometry.visualisation.VtkViewerColouredMaterial()
     v.addLogicalVolume(l)
@@ -32,17 +40,18 @@ used for visualisation or other operations.
 
 .. tab:: FLUKA
 
-  In directory :code:`pyg4ometry/test/flukaCompoundExamples`
-
   **Note** FLUKA geometry can be loaded but cannot be visualised directly without
-  conversion to a Geant4 model. This is not necessary for loading, but shown here.
+  conversion to a Geant4 model. This is not necessary for simiply loading, but it is
+  shown here.
 
   .. code-block:: python
     :linenos:
 
     import pyg4ometry
+    import g4edgetestdata
 
-    r = pyg4ometry.fluka.Reader("corrector-dipole2.inp")
+    d = g4edgetestdata.G4EdgeTestData()
+    r = pyg4ometry.fluka.Reader(d["fluka/ex-geometry.inp"])
     flukaRegistry = r.flukaregistry
 
     geantRegistry = pyg4ometry.convert.fluka2Geant4(flukaRegistry)
@@ -56,18 +65,18 @@ used for visualisation or other operations.
       :width: 80%
       :align: center
 
-      FLUKA example of a dipole magnet.
+      FLUKA example.
 
 .. tab:: ROOT
 
-  In directory :code:`pyg4ometry/test/root2Gdml`
-
   .. code-block:: python
     :linenos:
 
     import pyg4ometry
+    import g4edgetestdata
 
-    r = pyg4ometry.io.ROOTTGeo.Reader("example.root")
+    d = g4edgetestdata.G4EdgeTestData()
+    r = pyg4ometry.io.ROOTTGeo.Reader(d["root/lht.root"])
     l = r.getRegistry().getWorldVolume()
     v = pyg4ometry.visualisation.VtkViewerColouredMaterial()
     v.addLogicalVolume(l)
@@ -82,18 +91,19 @@ used for visualisation or other operations.
 
 .. tab:: STL
 
-  In directory :code:`pyg4ometry/test/stl`
-
   STL files are typically used for a single watertight solid mesh. This mesh is
   converted to a TesselatedSolid and then a logical volume which can be placed
-  in a geometry. In directory :code:`pyg4ometry/test/stl`.
+  in a geometry.
 
   .. code-block:: python
+    :linenos:
 
     import pyg4ometry
+    import g4edgetestdata
 
+    d = g4edgetestdata.G4EdgeTestData()
     reg = pyg4ometry.geant4.Registry()
-    r = pyg4ometry.stl.Reader("utahteapot.stl", reg)
+    r = pyg4ometry.stl.Reader(d["stl/utah_teapot.stl"], reg)
     s = r.getSolid()
     copper = pyg4ometry.geant4.MaterialPredefined("G4_Cu", reg)
     l = pyg4ometry.geant4.LogicalVolume(s, copper, "utahteapot_lv", reg)
@@ -102,26 +112,43 @@ used for visualisation or other operations.
     v.view()
 
   .. figure:: tutorials/tutorial2.png
- :alt: Example of STL loading in pyg4ometry
+        :width: 80%
+        :align: center
+        :alt: Example of STL loading in pyg4ometry
 
+        Example of STL loading in pyg4ometry. Pressing :code:`s` on the keyboard
+        when in the visualiser will switch to solid mode. :code:`w`, conversely will
+        switch to wireframe.
 
-.. tab:: STEP
 
+.. tab:: STEP
 
-  In directory :code:`pyg4ometry/test/freecad`
+  STEP file loading is possible in pyg4ometry. Note, here only a basic loading is shown
+  without material assignment, which normally is not information contained in a STEP file
+  but is necessary for Geant4 or FLUKA simulations.
 
   .. code-block:: python
     :linenos:
 
     import pyg4ometry
-
-    r = pyg4ometry.freecad.Reader("08_AshTray.step")
-    r.relabelModel()
-    r.convertFlat()
-    l = r.getRegistry().getWorldVolume()
-    v = pyg4ometry.visualisation.VtkViewer()
-    v.addLogicalVolume(l)
+    import g4edgetestdata
+
+    d = g4edgetestdata.G4EdgeTestData()
+    r = pyg4ometry.pyoce.Reader(d["step/1_BasicSolids_Bodies.step"])
+    ls = r.freeShapes()
+    worldName = pyg4ometry.pyoce.pythonHelpers.get_TDataStd_Name_From_Label(ls.Value(1))
+    mats, skip, mesh = {}, [], {}
+    reg = pyg4ometry.convert.oce2Geant4(r.shapeTool, worldName, mats, skip, mesh)
+    wl = reg.logicalVolumeDict[worldName]
+    v = pyg4ometry.visualisation.VtkViewerColouredMaterial()
+    v.addLogicalVolume(wl)
     v.view()
 
-  .. figure:: tutorials/tutorial3.png
-      :alt: Example of STEP loading in pyg4ometry
+  .. figure:: figures/viewing-step.png
+        :width: 80%
+        :align: center
+        :alt: Example of STEP loading in pyg4ometry
+
+        STEP file loading example in pyg4ometry. Pressing :code:`s` on the keyboard
+        when in the visualiser will switch to solid mode. :code:`w`, conversely will
+        switch to wireframe.

{pyg4ometry-1.3.2 → pyg4ometry-1.3.4}/docs/source/manual/rendering.rst

@@ -11,21 +11,24 @@ format is Universal Scene Description (USD). USD can be loaded in
 many packages and so a dedicated UDS converter/viewer is available
 in pyg4ometry. For example to load and convert a file to USD
 
-  .. code-block:: python
+.. code-block:: python
     :linenos:
+
     r = pyg4ometry.gdml.Reader("lht.gdml")
     l = r.getRegistry().getWorldVolume()
     v = pyg4ometry.visualisation.UsdViewer("lht.usd")
     v.traverseHierarchy(l)
     v.save()
 
+
 This will write a file called lht.gdml which can be viewed in
 a USD viewer like usdview. USD has a preview shader. The settings
 can set via the `VisualisationOptions` stored in logical volumes
 (`visOption`), so for example
 
-  .. code-block:: python
+.. code-block:: python
     :linenos:
+
     r = pyg4ometry.gdml.Reader("lht.gdml")
     reg = r.getRegistry()
     reg.logicalVolumeDict["vCalorimeter"].visOptions.color = [1, 0, 0]

{pyg4ometry-1.3.2 → pyg4ometry-1.3.4}/docs/source/manual/validating.rst

@@ -5,7 +5,6 @@ Validating Geometry
 ===================
 
 
-
 Overlap Checking
 ----------------
 
@@ -23,6 +22,7 @@ the following code:
 
     lv.checkOverlaps()
 
+
 This will check only the immediate daughters of this logical volume. To descend further into
 a geometry, the recursive flag can be used:
 
@@ -30,6 +30,7 @@ a geometry, the recursive flag can be used:
 
     lv.checkOverlaps(recursive=True)
 
+
 See :ref:`g4-module` : :code:`LogicalVolume.checkOverlaps()` for full details. A more
 complete example is:
 
@@ -46,6 +47,7 @@ complete example is:
    v.addLogicalVolume(l)
    v.view()
 
+
 .. figure:: pythonscripting/pythonscripting2.png
    :alt: Example overlap visualisation
 

{pyg4ometry-1.3.2 → pyg4ometry-1.3.4}/docs/source/manual/viewing.rst

@@ -27,6 +27,7 @@ and have the same functionality and differ only in colouring of volumes.
 Generally:
 
 .. code-block:: python
+    :linenos:
 
     v = pyg4ometry.visualisation.VtkViewer()
     v.addLogicalVolume(lv)
@@ -123,6 +124,7 @@ logical volume has no concept of translation or rotation on its own, so it is pl
 in the centre of the visualiser coordinate system, i.e. in its own frame.
 
 .. code-block:: python
+    :linenos:
 
     lv  # pyg4ometry.geant4.LogicalVolume instance
     v = pyg4ometry.visualisation.VtkViewer()
@@ -133,29 +135,34 @@ It is possible to view the logical volume with an offset (i.e. translation) and
 rotation. This is purely for adding the scene of the viewer and does not affect
 the logical volume itself or anything it is used in. We can see the docstring:
 
->>> v = pyg4ometry.visualisation.VtkViewer()
->>> v.addLogicalVolume?
-Signature:
-v.addLogicalVolume(
-logical,
-mtra=matrix([[1, 0, 0],
-[0, 1, 0],
-[0, 0, 1]]),
-tra=array([0, 0, 0]),
-recursive=True,
-)
+::
+
+    v = pyg4ometry.visualisation.VtkViewer()
+    v.addLogicalVolume?
+    Signature:
+    v.addLogicalVolume(
+    logical,
+    mtra=matrix([[1, 0, 0],
+    [0, 1, 0],
+    [0, 0, 1]]),
+    tra=array([0, 0, 0]),
+    recursive=True,
+    )
+
 
 If we start from a rotation as a series of Tait-Bryan angles, we can turn this into
 a matrix with:
 
-.. code-block::
+.. code-block:: python
+    :linenos:
+
+    import numpy as np
 
-   import numpy as np
-   rotation = [0, np.pi/2, 0] # for example
-   matrix = np.linalg.inv(pyg4ometry.transformation.tbxyz2matrix(rotation))
-   l # a pyg4ometry.geant4.LogicalVolume instance
-   v = pyg4ometry.visualisation.VtkViewer()
-   v.addLogicalVolume(l, mtra=rotation, tra=[0,0,500])
+    rotation = [0, np.pi / 2, 0]  # for example
+    matrix = np.linalg.inv(pyg4ometry.transformation.tbxyz2matrix(rotation))
+    l  # a pyg4ometry.geant4.LogicalVolume instance
+    v = pyg4ometry.visualisation.VtkViewer()
+    v.addLogicalVolume(l, mtra=rotation, tra=[0, 0, 500])
 
 
 .. note::
@@ -183,16 +190,19 @@ Similarly to a logical volume, an individual solid has no concept of placement p
 and will by default be placed at the centre of the scene. It is also possible to add it
 to the scene with a rotation and translation.
 
->>> v.addSolid?
-Signature:
-v.addSolid(
-solid,
-rotation=[0, 0, 0],
-position=[0, 0, 0],
-representation='surface',
-colour=[0.5, 0.5, 0.5],
-opacity=0.2,
-)
+::
+
+    v.addSolid?
+    Signature:
+    v.addSolid(
+    solid,
+    rotation=[0, 0, 0],
+    position=[0, 0, 0],
+    representation='surface',
+    colour=[0.5, 0.5, 0.5],
+    opacity=0.2,
+    )
+
 
 This uses Tait-Bryan angles for the rotation.
 
@@ -204,12 +214,14 @@ in these and it is useful to understand the individual constituents even if the
 a valid solid or mesh (i.e. completely disconnected solids). To do this we can visualise just
 a Boolean solid on its own.
 
-.. code-block::
+.. code-block:: python
+    :linenos:
+
+    s  # e.g. a pyg4ometry.geant4.solid.Subtraction instance
+    v = pyg4ometry.visualisation.VtkViewer()
+    v.addBooleanSolidRecursive(s)
+    v.view()
 
-   s # e.g. a pyg4ometry.geant4.solid.Subtraction instance
-   v = pyg4ometry.visualisation.VtkViewer()
-   v.addBooleanSolidRecursive(s)
-   v.view()
 
 This will work recursively for each solid that makes up the Boolean even if they are Booleans
 themselves. It will tolerate shapes that cannot form a valid mesh such as the resultant Boolean
@@ -232,7 +244,7 @@ Random Colours
 With the :code:`VtkViewerColoured` class, we can supply the default colour as :code:`"random"`,
 which will result in every volume being visualised with a random colour to be different.
 
-.. code-block::
+.. code-block:: python
 
    v = pyg4ometry.visualisation.VtkViewerColoured(defaultColour="random")
 
@@ -258,22 +270,25 @@ Cutters are a feature in the visualiser to generate the usually red, green, blue
 that intercept the edges of the geometry in a given plane. By default, these are along
 each axis aligned with 0,0,0. These can be plotted or added to an existing plot as follows:
 
-:: code-block::
+.. code-block:: python
+    :linenos:
 
-    pyg4ometry.visualisation.Plot.AddCutterDataToPlot("crosssection-ZX.dat",
-                                                      "zx",
-                                                      unitsFactor=0.001)
+    pyg4ometry.visualisation.Plot.AddCutterDataToPlot(
+        "crosssection-ZX.dat", "zx", unitsFactor=0.001
+    )
 
 
 An optional Matplotlib axes instance can be given if there is one from an existing plot.
 
-:: code-block::
+.. code-block:: python
+    :linenos:
 
     f = matplotlib.pyplot.figure()
     ax = f.add_subplot(111)
-    ax.plot([0,1],[0,1])
-    pyg4ometry.visualisation.Plot.AddCutterDataToPlot("crosssection-ZX.dat",
-                                                      "zx", ax,
-                                                      unitsFactor=0.001)
+    ax.plot([0, 1], [0, 1])
+    pyg4ometry.visualisation.Plot.AddCutterDataToPlot(
+        "crosssection-ZX.dat", "zx", ax, unitsFactor=0.001
+    )
+
 
 The full documentation can be found for :meth:`pyg4ometry.visualisation.Plot.AddCutterDataToPlot`.

{pyg4ometry-1.3.2 → pyg4ometry-1.3.4}/pyproject.toml

@@ -51,7 +51,7 @@ dependencies = [
 ]
 
 [project.scripts]
-pyg4ometry = "pyg4ometry.cli:main"
+pyg4ometry = "pyg4ometry.cli:mainNoExceptions"
 
 [project.urls]
 Homepage = "https://github.com/g4edge/pyg4ometry"
@@ -123,13 +123,14 @@ lint.select = [
   "EXE",         # flake8-executable
   "NPY",         # NumPy specific rules
   # "PD",          # pandas-vet
+  "T201",
 ]
 
 lint.extend-ignore = [
   "PLR",    # Design related pylint codes
   "E501",   # Line too long
-  "PT004",  # Use underscore for non-returning fixture (use usefixture instead)
   "RUF012", # Mutable class attributes should be annotated with typing.ClassVar
+  "RUF100", # unused noqa TODO: remove after print() migration
 ]
 src = ["src"]
 lint.unfixable = [
@@ -141,7 +142,16 @@ lint.flake8-unused-arguments.ignore-variadic-names = true
 lint.isort.required-imports = ["from __future__ import annotations"]
 
 [tool.ruff.lint.per-file-ignores]
+# ignores because of tests.
 "tests/**" = ["T20"]
+"src/pyg4ometry/misc/TestUtils.py" = ["T201"]
+"src/pyg4ometry/compare/_Compare.py" = ["T201"]
+# further ignores, TODO: should be removed.
+"src/pyg4ometry/gui/**" = ["T201"]
+"src/pyg4ometry/{fluka,convert}/**" = ["T201"]
+"src/pyg4ometry/{io,analysis,features}/**" = ["T201"]
+"src/pyg4ometry/{freecad,pycgal,pyoce}/**" = ["T201"]
+"src/pyg4ometry/visualisation/{UsdViewer,ViewerHierarchyBase}.py" = ["T201"]
 
 [tool.cibuildwheel]
 build = ["*macosx*", "*manylinux_x86_64", "*windows*"]

{pyg4ometry-1.3.2 → pyg4ometry-1.3.4}/src/pyg4ometry/__init__.py

@@ -5,6 +5,10 @@ except ImportError:
     __version__ = "unknown version"
     version_tuple = (0, 0, "unknown version")
 
+import logging
+
+_log = logging.getLogger(__name__)
+
 from . import config
 from . import compare
 from . import convert
@@ -19,7 +23,7 @@ from . import pycgal
 try:
     from . import pyoce
 except ImportError:
-    print("Failed to import open cascade")
+    _log.error("Failed to import opencascade")
 from . import stl
 from . import transformation
 from . import visualisation
@@ -29,8 +33,4 @@ from . import cli
 from . import misc
 from . import analysis
 from . import montecarlo
-
-try:
-    from . import usd
-except ImportError:
-    print("Failed to import open usd")
+from . import usd