drop target_folder=None

benchmarks/bench_kfactor.py

@@ -14,7 +14,7 @@ def benchmark_kfactor_inclusion(test_files, tmp_path, test_pdf, lhapdf_path):
         test_files / "data" / "kfactors",
         fake_yaml_path,
         pto_to_update,
-        target_folder=tmp_path,
+        tmp_path,
     )
     pluskfactor_grid_path = tmp_path / "ATLAS_TTB_8TEV_LJ_TRAP.pineappl.lz4"
     with lhapdf_path(test_pdf):

docs/source/theory/kfactors.rst

@@ -14,7 +14,7 @@ where:
 - ``TARGET_FOLDER`` is the folder where the new updated grids is going to be saved,
 - ``PTO_TO_UPDATE`` is the :math:`\alpha_s` perturbative order to update or create,
   with the convention that ``LO=1``, ``NLO=2`` and so on, irrespectively to the powers of :math:`\alpha_s`.
-  Note also that this differs from the conventions by the NNPDF collaboration, 
+  Note also that this differs from the conventions by the NNPDF collaboration,
   but it is consistent with the pineappl convention.
 - ``--order_exists`` is a flag used to apply the kfactor to the specified perturbative order, insead of the next.
 

src/pineko/kfactor.py

@@ -291,7 +291,7 @@ def apply_to_dataset(
     kfactor_folder,
     yamldb_path,
     pto_to_update,
-    target_folder=None,
+    target_folder,
     order_exists=False,
 ):
     """Include the kfactor in the grid in order to have its associated order in the grid itself.