mininterface 1.1.3__tar.gz → 1.1.4__tar.gz

{mininterface-1.1.3 → mininterface-1.1.4}/PKG-INFO

@@ -1,18 +1,19 @@
 Metadata-Version: 2.4
 Name: mininterface
-Version: 1.1.3
+Version: 1.1.4
 Summary: A minimal access to GUI, TUI, CLI and config
 License: LGPL-3.0-or-later
 License-File: LICENSE
 Author: Edvard Rejthar
 Author-email: edvard.rejthar@nic.cz
-Requires-Python: >=3.10,<3.14
+Requires-Python: >=3.10,<4.0
 Classifier: License :: OSI Approved :: GNU Lesser General Public License v3 or later (LGPLv3+)
 Classifier: Programming Language :: Python :: 3
 Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
 Provides-Extra: all
 Provides-Extra: basic
 Provides-Extra: gui
@@ -130,6 +131,8 @@ with run(Env) as m:
 
 Wrapper between various libraries that provide a user interface.
 
+It allows you to focus on writing the program's core logic without worrying about input/output. It generates CLI arguments, parses config file, and shows a UI. Depending on the endpoint, the dialogs automatically use either a GUI, a mouse-clickable TUI, a lightweight terminal text interface, or be available via HTTP — all while maintaining exactly the same functionality.
+
 Writing a small and useful program might be a task that takes fifteen minutes. Adding a CLI to specify the parameters is not so much overhead. But building a simple GUI around it? HOURS! Hours spent on researching GUI libraries, wondering why the Python desktop app ecosystem lags so far behind the web world. All you need is a few input fields validated through a clickable window... You do not deserve to add hundred of lines of the code just to define some editable fields. *Mininterface* is here to help.
 
 The config variables needed by your program are kept in cozy dataclasses. Write less! The syntax of [tyro](https://github.com/brentyi/tyro) does not require any overhead (as its `argparse` alternatives do). You just annotate a class attribute, append a simple docstring and get a fully functional application:
@@ -337,3 +340,4 @@ If you're sure enough to start using *Mininterface*, convert the argparse into a
 
 !!! warning
     The argparse support is considered mostly for your evaluation as there are some [`differences`](Argparse-caveats.md) for advanced argparse CLI interfaces.
+

{mininterface-1.1.3 → mininterface-1.1.4}/README.md

@@ -91,6 +91,8 @@ with run(Env) as m:
 
 Wrapper between various libraries that provide a user interface.
 
+It allows you to focus on writing the program's core logic without worrying about input/output. It generates CLI arguments, parses config file, and shows a UI. Depending on the endpoint, the dialogs automatically use either a GUI, a mouse-clickable TUI, a lightweight terminal text interface, or be available via HTTP — all while maintaining exactly the same functionality.
+
 Writing a small and useful program might be a task that takes fifteen minutes. Adding a CLI to specify the parameters is not so much overhead. But building a simple GUI around it? HOURS! Hours spent on researching GUI libraries, wondering why the Python desktop app ecosystem lags so far behind the web world. All you need is a few input fields validated through a clickable window... You do not deserve to add hundred of lines of the code just to define some editable fields. *Mininterface* is here to help.
 
 The config variables needed by your program are kept in cozy dataclasses. Write less! The syntax of [tyro](https://github.com/brentyi/tyro) does not require any overhead (as its `argparse` alternatives do). You just annotate a class attribute, append a simple docstring and get a fully functional application:
@@ -297,4 +299,4 @@ print(m.env.time)  # -> 14:21
 If you're sure enough to start using *Mininterface*, convert the argparse into a dataclass. Then, the IDE will auto-complete the hints as you type.
 
 !!! warning
-    The argparse support is considered mostly for your evaluation as there are some [`differences`](Argparse-caveats.md) for advanced argparse CLI interfaces.
+    The argparse support is considered mostly for your evaluation as there are some [`differences`](Argparse-caveats.md) for advanced argparse CLI interfaces.

{mininterface-1.1.3 → mininterface-1.1.4}/mininterface/_mininterface/__init__.py

@@ -91,7 +91,7 @@ class Mininterface(Generic[EnvClass]):
         # m = run([Env, Env2]) -> .env will be the chosen one.
 
         # NOTE In Python3.14, type(self).__annotations__ will work.
-        self._adaptor = self.__annotations__["_adaptor"](self, settings)
+        self._adaptor = type(self).__annotations__["_adaptor"](self, settings)
 
     def __enter__(self) -> "Self":
         """Usage within the with statement makes the program to attempt for the following benefits:

{mininterface-1.1.3 → mininterface-1.1.4}/mininterface/_mininterface/adaptor.py

@@ -26,9 +26,16 @@ class BackendAdaptor(ABC):
 
     def __init__(self, interface: "Mininterface", settings: UiSettings | None):
         self.interface = interface
-        # NOTE self.__annotations__ will pose problem at Python3.14
-        self.facet = interface.facet = self.__annotations__["facet"](self, interface.env)
-        self.settings = settings or self.__annotations__["settings"]()
+
+        # Why looping mro? Since 3.14, ex. MockAdaptor does not inherit .facet annotation from MinAdaptor.
+        for cl in type(self).__mro__:
+            try:
+                self.facet = interface.facet = cl.__annotations__["facet"](self, interface.env)
+                self.settings = settings or cl.__annotations__["settings"]()
+            except KeyError:
+                pass
+            else:
+                break
 
     @abstractmethod
     def widgetize(self, tag: Tag):

{mininterface-1.1.3 → mininterface-1.1.4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "poetry.core.masonry.api"
 
 [tool.poetry]
 name = "mininterface"
-version = "1.1.3"
+version = "1.1.4"
 description = "A minimal access to GUI, TUI, CLI and config"
 authors = ["Edvard Rejthar <edvard.rejthar@nic.cz>"]
 license = "LGPL-3.0-or-later"
@@ -13,8 +13,7 @@ readme = "README.md"
 
 [tool.poetry.dependencies]
 # Minimal requirements (dialogs with partial .form support (m.form(dict) or m.form(dataclass_instance))
-python = ">=3.10,<3.14"
-# python = "^3.10" NOTE when tyro accepts Python3.14, get this line back
+python = "^3.10"
 simple_term_menu = "*"
 annotated-types = "*"
 # Basic requirements (CLI and full .form support (m.form(dataclass_class))