docs: add note about logging level (#159)

* Bump version: 0.0.4-dev → 0.0.4

* Bump version: 0.0.4 → 0.0.5-dev

* docs: add note to docs about how to silence logger
Fixes #157

.bumpversion.cfg

@@ -1,5 +1,5 @@
 [bumpversion]
-current_version = 0.0.4-dev
+current_version = 0.0.5-dev
 commit = True
 tag = False
 parse = (?P<major>\d+)\.(?P<minor>\d+)\.(?P<patch>\d+)(?:-(?P<release>[0-9A-Za-z-]+(?:\.[0-9A-Za-z-]+)*))?(?:\+(?P<build>[0-9A-Za-z-]+(?:\.[0-9A-Za-z-]+)*))?

docs/source/conf.py

@@ -24,7 +24,7 @@
 author = "Kevin Maik Jablonka"
 
 # The full version, including alpha/beta/rc tags
-release = "0.0.4-dev"
+release = "0.0.5-dev"
 
 
 # -- General configuration ---------------------------------------------------

docs/source/getting_started.rst

@@ -106,3 +106,10 @@ Clearly, we do not consider floating solvent for the computation of the net.
     Also note that there are problems with analyzing the combinatorial topology of 1D rod MOFs.
     `There only recently has been an algorithm proposed that is implemented in ToposPro <https://link.springer.com/article/10.1007/s11224-016-0774-1>`_.
 
+
+.. admonition:: Customizing the log level 
+    :class: tip 
+
+    By default, you might find the output of the fragmentor a bit verbose.
+    You can change the log level by setting the environment variable :code:`LOGURU_LEVEL` to one of the
+    `loguru levels <https://loguru.readthedocs.io/en/stable/api/logger.html#loguru._logger.Logger.level>`_.

setup.cfg

@@ -1,6 +1,6 @@
 [metadata]
 name = moffragmentor
-version = 0.0.4-dev
+version = 0.0.5-dev
 description = Splits MOFs into metal nodes and linkers.
 author = Kevin Maik Jablonka
 author_email = mail@kjablonka.com

src/moffragmentor/version.py

@@ -14,7 +14,7 @@
     "get_git_hash",
 ]
 
-VERSION = "0.0.4-dev"
+VERSION = "0.0.5-dev"
 
 
 def get_git_hash() -> str: