pluginify 0.1.0.post11.dev0__tar.gz → 1.19.1a0__tar.gz

{pluginify-0.1.0.post11.dev0 → pluginify-1.19.1a0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pluginify
-Version: 0.1.0.post11.dev0
+Version: 1.19.1a0
 Summary: Pluginify package
 License: LICENSE
 License-File: LICENSE

pluginify-1.19.1a0/docs/source/releases/latest/module-to-class-updates.yaml

@@ -0,0 +1,18 @@
+bug fix:
+- title: 'Fix bug where non-plugin modules are treated like plugins during registry initialization'
+  description: |
+    In GeoIPS 1342 we converted nearly all of the module-based plugins to true
+    class-based plugins. In doing so I discovered a bug where non-plugin modules living
+    in the geoips/plugins/classes/.../ directory caused errors when trying to build
+    the plugin registry. To fix this, I've added a check to see if a module has an
+    'interface' attribute set to None. If that condition is met, then just ignore the
+    module and continue to the next potential plugin.
+  files:
+    modified:
+      - pluginify/create_plugin_registries.py
+  related-issue:
+    number: null
+    repo_url: ''
+  date:
+    start: null
+    finish: null

{pluginify-0.1.0.post11.dev0 → pluginify-1.19.1a0}/pluginify/_version.py

@@ -3,5 +3,5 @@
 
 # DO NOT EDIT
 # managed by poetry-dynamic-versioning
-__version__ = "0.1.0.post11.dev0"
-__version_tuple__ = (0, 1, 0, "post11", "dev0")
+__version__ = "1.19.1a0"
+__version_tuple__ = (1, 19, "1a0")

{pluginify-0.1.0.post11.dev0 → pluginify-1.19.1a0}/pluginify/create_plugin_registries.py

@@ -957,6 +957,18 @@ def add_class_plugin(package, relpath, plugins):
                          at relpath '{relpath}'\n"""
         return error_message
 
+    # If interface is None, then legitimately skip the module.
+    # We want to skip this first, before we test anything else.
+    # If it is not a plugin, we don't care if there are other
+    # errors in it at this stage (ie, avoid unnecessary unrelated
+    # catastrophic failures)
+    if hasattr(module, "interface") and module.interface is None:
+        LOG.info(
+            f"Skipping module '{module_name}' from '{package}', "
+            "interface_name is 'None'"
+        )
+        return error_message
+
     # We've encountered a truly 'class-based' plugin. I.e. we don't need to generate
     # the plugin object from the module itself. Collect metadata from this plugin
     # in a different fashion to what we've done previously.

{pluginify-0.1.0.post11.dev0 → pluginify-1.19.1a0}/pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "pluginify" # package available at the root of the project
-version = "0.1.0.post11.dev0"
+version = "1.19.1a0"
 description = "Pluginify package"
 authors = ["Evan Rose", "evrose54@colostate.edu"]
 readme = "README.md"