chore: move from setup.cfg to pyproject.toml

Author: fstagni

.github/workflows/deployment.yml

@@ -103,7 +103,7 @@ jobs:
                 git show
                 # If we're making a release, pin DIRACCommon to exact version
                 python .github/workflows/pin_diraccommon_version.py "$NEW_VERSION"
-                git add setup.cfg
+                git add pyproject.toml
                 git commit -m "chore: Pin DIRACCommon to $NEW_VERSION"
                 git show
                 # Create the tag

.github/workflows/pin_diraccommon_version.py

@@ -1,6 +1,6 @@
 #!/usr/bin/env python3
 """
-Pin DIRACCommon version in setup.cfg during deployment.
+Pin DIRACCommon version in pyproject.toml during deployment.
 
 This script is used during the deployment process to ensure DIRAC
 depends on the exact version of DIRACCommon being released.
@@ -31,19 +31,19 @@ def get_diraccommon_version():
 
 
 def pin_diraccommon_version(version):
-    """Pin DIRACCommon to exact version in setup.cfg."""
-    setup_cfg = Path("setup.cfg")
-    content = setup_cfg.read_text()
+    """Pin DIRACCommon to exact version in pyproject.toml."""
+    pyproject_toml = Path("pyproject.toml")
+    content = pyproject_toml.read_text()
 
     # Replace the DIRACCommon line with exact version pin
     updated_content = re.sub(r"^(\s*)DIRACCommon\s*$", f"\\1DIRACCommon=={version}", content, flags=re.MULTILINE)
 
     if content == updated_content:
-        print(f"Warning: DIRACCommon line not found or already pinned in setup.cfg")
+        print(f"Warning: DIRACCommon line not found or already pinned in pyproject.toml")
         return False
 
-    setup_cfg.write_text(updated_content)
-    print(f"Pinned DIRACCommon to version {version} in setup.cfg")
+    pyproject_toml.write_text(updated_content)
+    print(f"Pinned DIRACCommon to version {version} in pyproject.toml")
     return True
 
 

MANIFEST.in

@@ -2,5 +2,5 @@ prune *
 graft src
 # graft tests
 
-include LICENSE README.rst pyproject.toml setup.py setup.cfg
+include LICENSE README.rst pyproject.toml
 global-exclude __pycache__ *.py[cod] .*

docs/source/DeveloperGuide/AddingNewComponents/DevelopingCommands/dirac_my_great_script.py

@@ -9,6 +9,7 @@
   This is the servicesList: MyService
   We are done with detail report.
 """
+
 from DIRAC import S_OK, S_ERROR, gLogger, exit as DIRACExit
 from DIRAC.Core.Base.Script import Script
 
@@ -91,7 +92,7 @@ def parseSwitchesAndPositionalArguments():
     return switches, repType, user, services
 
 
-# IMPORTANT: Make sure to add the console-scripts entry to setup.cfg as well!
+# IMPORTANT: Make sure to add the console-scripts entry to pyproject.toml as well!
 @Script()
 def main():
     """

docs/source/DeveloperGuide/AddingNewComponents/DevelopingCommands/index.rst

@@ -18,7 +18,7 @@ All scripts should live in the *scripts* directory of their parent system. For i
 
 will live in `src/DIRAC/WorkloadManagementSystem/scripts/dirac_wms_job_submit.py`.
 
-Scripts become command line scripts when DIRAC is pip-installed, using the `console_scripts entry point <https://setuptools.pypa.io/en/latest/userguide/entry_point.html>`_, meaning that new scripts should be added to the list in `setup.cfg file <https://github.com/DIRACGrid/DIRAC/blob/integration/setup.cfg>`_.
+Scripts become command line scripts when DIRAC is pip-installed, using the `console_scripts entry point <https://setuptools.pypa.io/en/latest/userguide/entry_point.html>`_, meaning that new scripts should be added to the list in `pyproject.toml file <https://github.com/DIRACGrid/DIRAC/blob/integration/pyproject.toml>`_.
 
 
 Coding commands