frontengine 1.0.77__tar.gz → 1.0.78__tar.gz

{frontengine-1.0.77 → frontengine-1.0.78}/PKG-INFO

@@ -1,10 +1,10 @@
 Metadata-Version: 2.4
 Name: frontengine
-Version: 1.0.77
+Version: 1.0.78
 Summary: FrontEngine is use-define frontview or only use like screen saver
 Author-email: JE-Chen <jechenmailman@gmail.com>
-Project-URL: Homepage, https://github.com/Intergration-Automation-Testing/FrontEngine
-Project-URL: Code, https://github.com/Intergration-Automation-Testing/FrontEngine
+Project-URL: Homepage, https://github.com/JeffreyChen-SteamProjects/FrontEngine
+Project-URL: Code, https://github.com/JeffreyChen-SteamProjects/FrontEngine
 Classifier: Programming Language :: Python :: 3.10
 Classifier: Development Status :: 2 - Pre-Alpha
 Classifier: Environment :: Win32 (MS Windows)
@@ -14,7 +14,7 @@ Classifier: Operating System :: OS Independent
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: PySide6==6.11.1
+Requires-Dist: PySide6==6.11.2
 Requires-Dist: qt-material
 Requires-Dist: PyOpenGL
 Requires-Dist: PyOpenGL_accelerate
@@ -427,16 +427,28 @@ it can be tested with a fake one.
 
 ## Continuous integration and releases
 
+Work flows `feature → dev → main`, and only the last step publishes:
+
+```
+feat/xyz  ──PR──►  dev  ──PR──►  main
+                    │              │
+              CI, no release   CI + release
+```
+
 | Workflow | Trigger | Purpose |
 | --- | --- | --- |
-| `CI` (`ci.yml`) | Push / PR to `main` or `dev`, or called by `Nightly` | Compile, run the unit tests, then build a wheel from *that checkout*, install it and start the app — on Python 3.10 / 3.11 / 3.12, Windows |
+| `CI` (`ci.yml`) | Push / PR to `main` or `dev`, manual dispatch, or called by `Nightly` | Compile, run the unit tests, then build a wheel from *that checkout*, install it and start the app — on Python 3.10 / 3.11 / 3.12, Windows |
 | `Nightly` (`nightly.yml`) | Daily cron, manual dispatch | Calls `CI`. The schedule lives here on purpose: GitHub disables workflows containing a cron after ~60 days of inactivity, and that would otherwise take the PR checks down with it |
-| `Release` (`release.yml`) | A pull request is merged into `main`, or manual dispatch | Bumps the version, commits it back with `[skip ci]`, swaps `stable.toml` → `pyproject.toml`, builds sdist + wheel, uploads to PyPI as `frontengine`, and creates a GitHub release tagged `v<version>` |
+| `Release` (`release.yml`) | A pull request **from `dev`** is merged into `main`, or manual dispatch | Bumps the version, commits it back with `[skip ci]`, swaps `stable.toml` → `pyproject.toml`, builds sdist + wheel, uploads to PyPI as `frontengine`, creates a GitHub release tagged `v<version>`, and fast-forwards `dev` |
+
+Publishing happens **only when `dev` merges into `main`**. Features land on `dev`
+without minting a version, and a release is a deliberate `dev → main` pull
+request. A feature PR aimed at `main` by mistake still merges but does not
+publish — the failure direction is a missing release, not an unwanted one.
 
-Publishing happens **only on merge to `main`** — pushing to `dev` runs CI and
-never publishes. The patch segment bumps automatically; for a minor or major
-release, run *Actions → Release → Run workflow* and pick the segment. That path
-also re-runs a failed publish without needing a new merge.
+The patch segment bumps automatically; for a minor or major release, run
+*Actions → Release → Run workflow* and pick the segment. That path also re-runs
+a failed publish without needing a new merge.
 
 Versions live in two files: `pyproject.toml` is the dev package
 (`frontengine_dev`) and `stable.toml` is the published one (`frontengine`).

{frontengine-1.0.77 → frontengine-1.0.78}/README.md

@@ -403,16 +403,28 @@ it can be tested with a fake one.
 
 ## Continuous integration and releases
 
+Work flows `feature → dev → main`, and only the last step publishes:
+
+```
+feat/xyz  ──PR──►  dev  ──PR──►  main
+                    │              │
+              CI, no release   CI + release
+```
+
 | Workflow | Trigger | Purpose |
 | --- | --- | --- |
-| `CI` (`ci.yml`) | Push / PR to `main` or `dev`, or called by `Nightly` | Compile, run the unit tests, then build a wheel from *that checkout*, install it and start the app — on Python 3.10 / 3.11 / 3.12, Windows |
+| `CI` (`ci.yml`) | Push / PR to `main` or `dev`, manual dispatch, or called by `Nightly` | Compile, run the unit tests, then build a wheel from *that checkout*, install it and start the app — on Python 3.10 / 3.11 / 3.12, Windows |
 | `Nightly` (`nightly.yml`) | Daily cron, manual dispatch | Calls `CI`. The schedule lives here on purpose: GitHub disables workflows containing a cron after ~60 days of inactivity, and that would otherwise take the PR checks down with it |
-| `Release` (`release.yml`) | A pull request is merged into `main`, or manual dispatch | Bumps the version, commits it back with `[skip ci]`, swaps `stable.toml` → `pyproject.toml`, builds sdist + wheel, uploads to PyPI as `frontengine`, and creates a GitHub release tagged `v<version>` |
+| `Release` (`release.yml`) | A pull request **from `dev`** is merged into `main`, or manual dispatch | Bumps the version, commits it back with `[skip ci]`, swaps `stable.toml` → `pyproject.toml`, builds sdist + wheel, uploads to PyPI as `frontengine`, creates a GitHub release tagged `v<version>`, and fast-forwards `dev` |
+
+Publishing happens **only when `dev` merges into `main`**. Features land on `dev`
+without minting a version, and a release is a deliberate `dev → main` pull
+request. A feature PR aimed at `main` by mistake still merges but does not
+publish — the failure direction is a missing release, not an unwanted one.
 
-Publishing happens **only on merge to `main`** — pushing to `dev` runs CI and
-never publishes. The patch segment bumps automatically; for a minor or major
-release, run *Actions → Release → Run workflow* and pick the segment. That path
-also re-runs a failed publish without needing a new merge.
+The patch segment bumps automatically; for a minor or major release, run
+*Actions → Release → Run workflow* and pick the segment. That path also re-runs
+a failed publish without needing a new merge.
 
 Versions live in two files: `pyproject.toml` is the dev package
 (`frontengine_dev`) and `stable.toml` is the published one (`frontengine`).

frontengine-1.0.78/frontengine/utils/logging/loggin_instance.py

@@ -0,0 +1,130 @@
+"""
+The ``FrontEngine`` logger and the file it writes to.
+
+The log file is ``~/.frontengine/logs/FrontEngine.log`` unless the
+``FRONTENGINE_LOG_FILE`` environment variable names another path (a relative one
+resolves against the cwd at import time; ``os.devnull`` turns the file off). It
+used to be ``FrontEngine.log`` in the working directory, opened at import, so
+every process that imported the package -- JEditor and PyBreeze embed it -- left
+a log in whatever directory it started in, and a launch from a read-only
+directory had to fall back through a chain of candidates.
+
+The package's handler opens the file on the first record, so importing writes
+nothing. Every process on the account shares the file, so it is opened for
+append, each line carries the process id, and it is rotated only when a process
+opens it: Windows refuses to rename a file another process holds open, and a
+rotation attempted inside ``emit()`` would then fail on every later record.
+"""
+import logging
+import os
+import warnings
+from logging.handlers import RotatingFileHandler
+from pathlib import Path
+
+# 只調自己這個 logger 的層級。動 root logger 會把 DEBUG 強加給任何
+# `import frontengine` 的程式，連帶它用的每一個第三方套件。
+# Only this logger's level is ours to set. Touching the root logger forces DEBUG
+# onto any application that imports frontengine, and every library it uses.
+
+# 建立 FrontEngine logger
+front_engine_logger = logging.getLogger("FrontEngine")
+front_engine_logger.setLevel(logging.DEBUG)  # 建議與 handler 一致
+
+# 日誌格式
+# Log format
+formatter = logging.Formatter(
+    '%(asctime)s | %(process)d | %(name)s | %(levelname)s | %(message)s'
+)
+
+#: Environment variable that overrides where the log file is written.
+LOG_FILE_ENV = "FRONTENGINE_LOG_FILE"
+
+#: A file past this size is moved to ``<name>.1`` when a process opens it.
+ROTATE_AT_BYTES = 10 * 1024 * 1024
+
+
+def default_log_file() -> Path:
+    """Return the log file path: ``$FRONTENGINE_LOG_FILE``, else the home default."""
+    configured = os.environ.get(LOG_FILE_ENV, "").strip()
+    if configured:
+        return Path(configured).expanduser()
+    return Path.home() / ".frontengine" / "logs" / "FrontEngine.log"
+
+
+def _rotate_if_large(path: Path, limit: int) -> None:
+    """Move ``path`` to ``<path>.1`` when it is larger than ``limit`` bytes.
+
+    Best effort: while another process holds the file open Windows refuses the
+    rename, and the file is simply appended to until a later open succeeds.
+    """
+    try:
+        if limit <= 0 or not path.is_file() or path.stat().st_size <= limit:
+            return
+        os.replace(path, path.with_name(path.name + ".1"))
+    except OSError:
+        return
+
+
+class FrontEngineLoggingHandler(RotatingFileHandler):
+    """
+    FrontEngine 專用日誌處理器
+    FrontEngine's file handler: ``default_log_file()``, append, UTF-8.
+
+    ``delay=True`` defers opening (and creating the directory) to the first
+    record, which is how the package's own handler is built. A file that cannot
+    be opened is swapped for ``os.devnull`` with one ``RuntimeWarning``: losing
+    the log is acceptable, failing to start is not.
+    """
+
+    def __init__(
+        self,
+        filename: str | None = None,
+        mode: str = "a",
+        max_bytes: int = 0,
+        backup_count: int = 0,
+        errors: str = "backslashreplace",
+        delay: bool = False,
+    ):
+        # encoding="utf-8"：日誌會寫進翻譯過的字串與使用者的檔案路徑。
+        # 用系統預設編碼的話，cp950／cp1252 遇到俄文或中文就整行寫不進去，
+        # 還會把 logging 自己的錯誤倒進被導向的輸出面板。
+        # encoding="utf-8": the log carries translated strings and user file
+        # paths. On the locale codepage, cp950 or cp1252 drops any line with
+        # Russian or Chinese in it and spills logging's own traceback into the
+        # redirected output panel.
+        # errors="backslashreplace" (logging.basicConfig's own default): a lone
+        # surrogate from a Windows path still raises under strict, and an
+        # escaped record beats a lost one.
+        path = filename if filename is not None else str(default_log_file())
+        super().__init__(
+            filename=path, mode=mode, maxBytes=max_bytes,
+            backupCount=backup_count, encoding="utf-8", delay=delay,
+            errors=errors)
+        self.setFormatter(formatter)  # 正確套用 formatter
+        self.setLevel(logging.DEBUG)
+
+    def _open(self):
+        """Create the directory and rotate before opening; fall back to devnull."""
+        path = Path(self.baseFilename)
+        try:
+            path.parent.mkdir(parents=True, exist_ok=True)
+            _rotate_if_large(path, ROTATE_AT_BYTES)
+            return super()._open()
+        except OSError as error:
+            warnings.warn(
+                f"FrontEngine log file {path} unavailable, file logging off: {error!r}",
+                RuntimeWarning, stacklevel=2)
+            # The handler owns and closes this stream.
+            return open(os.devnull, self.mode, encoding=self.encoding, errors=self.errors)  # noqa: SIM115
+
+    def emit(self, record: logging.LogRecord) -> None:
+        """
+        實際輸出日誌紀錄
+        Emit log record
+        """
+        super().emit(record)
+
+
+# The file is opened on the first record, never at import.
+file_handler = FrontEngineLoggingHandler(delay=True)
+front_engine_logger.addHandler(file_handler)

{frontengine-1.0.77 → frontengine-1.0.78}/frontengine.egg-info/PKG-INFO

@@ -1,10 +1,10 @@
 Metadata-Version: 2.4
 Name: frontengine
-Version: 1.0.77
+Version: 1.0.78
 Summary: FrontEngine is use-define frontview or only use like screen saver
 Author-email: JE-Chen <jechenmailman@gmail.com>
-Project-URL: Homepage, https://github.com/Intergration-Automation-Testing/FrontEngine
-Project-URL: Code, https://github.com/Intergration-Automation-Testing/FrontEngine
+Project-URL: Homepage, https://github.com/JeffreyChen-SteamProjects/FrontEngine
+Project-URL: Code, https://github.com/JeffreyChen-SteamProjects/FrontEngine
 Classifier: Programming Language :: Python :: 3.10
 Classifier: Development Status :: 2 - Pre-Alpha
 Classifier: Environment :: Win32 (MS Windows)
@@ -14,7 +14,7 @@ Classifier: Operating System :: OS Independent
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: PySide6==6.11.1
+Requires-Dist: PySide6==6.11.2
 Requires-Dist: qt-material
 Requires-Dist: PyOpenGL
 Requires-Dist: PyOpenGL_accelerate
@@ -427,16 +427,28 @@ it can be tested with a fake one.
 
 ## Continuous integration and releases
 
+Work flows `feature → dev → main`, and only the last step publishes:
+
+```
+feat/xyz  ──PR──►  dev  ──PR──►  main
+                    │              │
+              CI, no release   CI + release
+```
+
 | Workflow | Trigger | Purpose |
 | --- | --- | --- |
-| `CI` (`ci.yml`) | Push / PR to `main` or `dev`, or called by `Nightly` | Compile, run the unit tests, then build a wheel from *that checkout*, install it and start the app — on Python 3.10 / 3.11 / 3.12, Windows |
+| `CI` (`ci.yml`) | Push / PR to `main` or `dev`, manual dispatch, or called by `Nightly` | Compile, run the unit tests, then build a wheel from *that checkout*, install it and start the app — on Python 3.10 / 3.11 / 3.12, Windows |
 | `Nightly` (`nightly.yml`) | Daily cron, manual dispatch | Calls `CI`. The schedule lives here on purpose: GitHub disables workflows containing a cron after ~60 days of inactivity, and that would otherwise take the PR checks down with it |
-| `Release` (`release.yml`) | A pull request is merged into `main`, or manual dispatch | Bumps the version, commits it back with `[skip ci]`, swaps `stable.toml` → `pyproject.toml`, builds sdist + wheel, uploads to PyPI as `frontengine`, and creates a GitHub release tagged `v<version>` |
+| `Release` (`release.yml`) | A pull request **from `dev`** is merged into `main`, or manual dispatch | Bumps the version, commits it back with `[skip ci]`, swaps `stable.toml` → `pyproject.toml`, builds sdist + wheel, uploads to PyPI as `frontengine`, creates a GitHub release tagged `v<version>`, and fast-forwards `dev` |
+
+Publishing happens **only when `dev` merges into `main`**. Features land on `dev`
+without minting a version, and a release is a deliberate `dev → main` pull
+request. A feature PR aimed at `main` by mistake still merges but does not
+publish — the failure direction is a missing release, not an unwanted one.
 
-Publishing happens **only on merge to `main`** — pushing to `dev` runs CI and
-never publishes. The patch segment bumps automatically; for a minor or major
-release, run *Actions → Release → Run workflow* and pick the segment. That path
-also re-runs a failed publish without needing a new merge.
+The patch segment bumps automatically; for a minor or major release, run
+*Actions → Release → Run workflow* and pick the segment. That path also re-runs
+a failed publish without needing a new merge.
 
 Versions live in two files: `pyproject.toml` is the dev package
 (`frontengine_dev`) and `stable.toml` is the published one (`frontengine`).

{frontengine-1.0.77 → frontengine-1.0.78}/frontengine.egg-info/requires.txt

@@ -1,4 +1,4 @@
-PySide6==6.11.1
+PySide6==6.11.2
 qt-material
 PyOpenGL
 PyOpenGL_accelerate

{frontengine-1.0.77 → frontengine-1.0.78}/pyproject.toml

@@ -6,12 +6,12 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "frontengine"
-version = "1.0.77"
+version = "1.0.78"
 authors = [
     { name = "JE-Chen", email = "jechenmailman@gmail.com" },
 ]
 dependencies = [
-    "PySide6==6.11.1", "qt-material", "PyOpenGL", "PyOpenGL_accelerate", "numpy", "pynput"
+    "PySide6==6.11.2", "qt-material", "PyOpenGL", "PyOpenGL_accelerate", "numpy", "pynput"
 ]
 description = "FrontEngine is use-define frontview or only use like screen saver"
 requires-python = ">=3.10"
@@ -29,8 +29,8 @@ classifiers = [
 frontengine = "frontengine.ui.main_ui:main"
 
 [project.urls]
-Homepage = "https://github.com/Intergration-Automation-Testing/FrontEngine"
-Code = "https://github.com/Intergration-Automation-Testing/FrontEngine"
+Homepage = "https://github.com/JeffreyChen-SteamProjects/FrontEngine"
+Code = "https://github.com/JeffreyChen-SteamProjects/FrontEngine"
 
 [project.readme]
 file = "README.md"

frontengine-1.0.77/frontengine/utils/logging/loggin_instance.py

@@ -1,80 +0,0 @@
-import logging
-from logging.handlers import RotatingFileHandler
-from pathlib import Path
-
-# 只調自己這個 logger 的層級。動 root logger 會把 DEBUG 強加給任何
-# `import frontengine` 的程式，連帶它用的每一個第三方套件。
-# Only this logger's level is ours to set. Touching the root logger forces DEBUG
-# onto any application that imports frontengine, and every library it uses.
-
-# 建立 FrontEngine logger
-front_engine_logger = logging.getLogger("FrontEngine")
-front_engine_logger.setLevel(logging.DEBUG)  # 建議與 handler 一致
-
-# 日誌格式
-# Log format
-formatter = logging.Formatter(
-    '%(asctime)s | %(name)s | %(levelname)s | %(message)s'
-)
-
-# 日誌檔名 / The log file's name
-LOG_FILE_NAME = "FrontEngine.log"
-
-
-class FrontEngineLoggingHandler(RotatingFileHandler):
-    """
-    FrontEngine 專用日誌處理器
-    FrontEngine custom logging handler using RotatingFileHandler
-    """
-
-    def __init__(
-        self,
-        filename: str = LOG_FILE_NAME,
-        mode: str = "a",  # 建議使用 append 模式
-        max_bytes: int = 1073741824,  # 1GB
-        backup_count: int = 3         # 保留 3 個備份檔案
-    ):
-        # encoding="utf-8"：日誌會寫進翻譯過的字串與使用者的檔案路徑。
-        # 用系統預設編碼的話，cp950／cp1252 遇到俄文或中文就整行寫不進去，
-        # 還會把 logging 自己的錯誤倒進被導向的輸出面板。
-        # encoding="utf-8": the log carries translated strings and user file
-        # paths. On the locale codepage, cp950 or cp1252 drops any line with
-        # Russian or Chinese in it and spills logging's own traceback into the
-        # redirected output panel.
-        super().__init__(
-            filename=filename, mode=mode, maxBytes=max_bytes,
-            backupCount=backup_count, encoding="utf-8")
-        self.setFormatter(formatter)  # 正確套用 formatter
-        self.setLevel(logging.DEBUG)
-
-    def emit(self, record: logging.LogRecord) -> None:
-        """
-        實際輸出日誌紀錄
-        Emit log record
-        """
-        super().emit(record)
-
-
-def _build_file_handler() -> logging.Handler:
-    """
-    日誌優先寫在工作目錄，寫不了就退到家目錄，再不行就不寫檔。
-    從唯讀目錄或系統目錄啟動（自動啟動很容易這樣）不該讓程式打不開——
-    少一份日誌可以接受，開不起來不行。
-    Prefer the working directory, fall back to the home directory, and give up
-    on file logging if neither works. Being launched from a read-only or system
-    directory - which autostart makes easy - must not stop the app from opening:
-    losing the log is acceptable, failing to start is not.
-    """
-    for candidate in (LOG_FILE_NAME, str(Path.home() / LOG_FILE_NAME)):
-        try:
-            # 建構子本身就會開檔，所以「開得起來」就是這裡的測試
-            # The constructor opens the file, so building it is the test.
-            return FrontEngineLoggingHandler(filename=candidate)
-        except OSError:
-            continue
-    return logging.NullHandler()
-
-
-# 建立並加入 handler
-file_handler = _build_file_handler()
-front_engine_logger.addHandler(file_handler)