pum 1.1.1__tar.gz → 1.1.3__tar.gz

{pum-1.1.1/pum.egg-info → pum-1.1.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pum
-Version: 1.1.1
+Version: 1.1.3
 Summary: Pum stands for "Postgres Upgrades Manager". It is a Database migration management tool very similar to flyway-db or Liquibase, based on metadata tables.
 Author-email: Denis Rouzaud <denis@opengis.ch>
 License-Expression: GPL-2.0-or-later
@@ -58,4 +58,4 @@ PUM (PostgreSQL Upgrades Manager) is a robust database migration management tool
 
 Managing database migrations in a Version Control System (VCS) can be challenging, especially for production databases. PUM simplifies this process by embedding version metadata directly into the database, enabling efficient tracking and application of migrations.
 
-PUM was developed to address challenges in the [TEKSI](https://github.com/TESKI) project, an open-source GIS for network management based on [QGIS](http://qgis.org/fr/site/).
+PUM was developed to address challenges in the [TEKSI](https://github.com/TEKSI) project, an open-source GIS for network management based on [QGIS](http://qgis.org/).

{pum-1.1.1 → pum-1.1.3}/README.md

@@ -22,4 +22,4 @@ PUM (PostgreSQL Upgrades Manager) is a robust database migration management tool
 
 Managing database migrations in a Version Control System (VCS) can be challenging, especially for production databases. PUM simplifies this process by embedding version metadata directly into the database, enabling efficient tracking and application of migrations.
 
-PUM was developed to address challenges in the [TEKSI](https://github.com/TESKI) project, an open-source GIS for network management based on [QGIS](http://qgis.org/fr/site/).
+PUM was developed to address challenges in the [TEKSI](https://github.com/TEKSI) project, an open-source GIS for network management based on [QGIS](http://qgis.org/).

{pum-1.1.1 → pum-1.1.3}/docs/docs/index.md

@@ -17,4 +17,4 @@ PUM (PostgreSQL Upgrades Manager) is a robust database migration management tool
 
 Managing database migrations in a Version Control System (VCS) can be challenging, especially for production databases. PUM simplifies this process by embedding version metadata directly into the database, enabling efficient tracking and application of migrations.
 
-PUM was developed to address challenges in the [TEKSI](https://github.com/TESKI) project, an open-source GIS for network management based on [QGIS](http://qgis.org/fr/site/).
+PUM was developed to address challenges in the [TEKSI](https://github.com/TEKSI) project, an open-source GIS for network management based on [QGIS](http://qgis.org/).

{pum-1.1.1 → pum-1.1.3}/pum/cli.py

@@ -349,7 +349,8 @@ def cli() -> int:  # noqa: PLR0912
                 demo_data=args.demo_data,
             )
             conn.commit()
-            upg.install_demo_data(name=args.demo_data, connection=conn, parameters=parameters)
+            if args.demo_data:
+                upg.install_demo_data(name=args.demo_data, connection=conn, parameters=parameters)
         elif args.command == "role":
             if not args.action:
                 logger.error(

{pum-1.1.1 → pum-1.1.3}/pum/pum_config.py

@@ -18,7 +18,6 @@ from .config_model import ConfigModel
 from .hook import HookHandler
 import tempfile
 import sys
-import atexit
 
 
 try:
@@ -250,6 +249,15 @@ class PumConfig:
         """Return a dictionary of demo data files defined in the configuration."""
         return {dm.name: dm.file for dm in self.config.demo_data}
 
+    def __del__(self):
+        # Cleanup temporary directories and sys.path modifications
+        if self.dependency_path:
+            # Remove from sys.path if present
+            sys.path = [p for p in sys.path if p != str(self.dependency_path)]
+            # Remove the directory if it exists and is a TemporaryDirectory
+            if hasattr(self, "_temp_dir") and self._temp_dir:
+                self.dependency_tmp.cleanup()
+
     def validate(self, install_dependencies: bool = False) -> None:
         """Validate the changelogs and hooks.
 
@@ -258,16 +266,10 @@ class PumConfig:
         """
 
         if install_dependencies and self.config.dependencies:
-            temp_dir = tempfile.TemporaryDirectory()
-            self.dependency_path = Path(temp_dir.name)
+            self.dependency_tmp = tempfile.TemporaryDirectory()
+            self.dependency_path = Path(self.dependency_tmp.name)
             sys.path.insert(0, str(self.dependency_path))
 
-            def cleanup():
-                sys.path = [p for p in sys.path if p != str(self.dependency_path)]
-                temp_dir.cleanup()
-
-            atexit.register(cleanup)
-
         parameter_defaults = {}
         for parameter in self.config.parameters:
             parameter_defaults[parameter.name] = psycopg.sql.Literal(parameter.default)

{pum-1.1.1 → pum-1.1.3/pum.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pum
-Version: 1.1.1
+Version: 1.1.3
 Summary: Pum stands for "Postgres Upgrades Manager". It is a Database migration management tool very similar to flyway-db or Liquibase, based on metadata tables.
 Author-email: Denis Rouzaud <denis@opengis.ch>
 License-Expression: GPL-2.0-or-later
@@ -58,4 +58,4 @@ PUM (PostgreSQL Upgrades Manager) is a robust database migration management tool
 
 Managing database migrations in a Version Control System (VCS) can be challenging, especially for production databases. PUM simplifies this process by embedding version metadata directly into the database, enabling efficient tracking and application of migrations.
 
-PUM was developed to address challenges in the [TEKSI](https://github.com/TESKI) project, an open-source GIS for network management based on [QGIS](http://qgis.org/fr/site/).
+PUM was developed to address challenges in the [TEKSI](https://github.com/TEKSI) project, an open-source GIS for network management based on [QGIS](http://qgis.org/).