pyhttp-app 2.0.1.post1__tar.gz → 2.0.2__tar.gz

{pyhttp_app-2.0.1.post1 → pyhttp_app-2.0.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pyhttp-app
-Version: 2.0.1.post1
+Version: 2.0.2
 Summary: Local API client and alternative to Postman: collection runner, Postman-compatible scripts, mock servers and an MCP server
 Author-email: pyhttp Dev Team <dev@pyhttp.com>
 License: # pyhttp Free License 1.1
@@ -338,8 +338,11 @@ pyhttp
 ```
 
 On Linux, install the GTK webview bindings first (see *Linux* below) or use
-`pyhttp --browser`. `brew install pyhttp2/pyhttp/pyhttp-app` installs the
-same package through Homebrew (macOS and Linux, Intel and ARM).
+`pyhttp --browser`. `brew install pyhttp2/pyhttp/pyhttp` installs the
+same package through Homebrew (macOS and Linux, Intel and ARM; the tap is
+[pyhttp2/homebrew-pyhttp](https://github.com/pyhttp2/homebrew-pyhttp)) — or tap
+once with `brew tap pyhttp2/pyhttp`, after which plain `brew install pyhttp`,
+`brew upgrade pyhttp` and `brew install --cask pyhttp` all work.
 
 **Windows**: double-click `run.bat`. The window opens without a console.
 WebView2 ships with Windows 10/11.
@@ -446,7 +449,7 @@ Packaged builds bundle Python and every dependency, so users just double-click.
 |---|---|---|
 | Windows 10/11 | `pyhttp-<version>-windows-x64-setup.exe`: installer (per user, no admin rights, into `%LOCALAPPDATA%\Programs\pyhttp`, Start menu entry, optional desktop icon, uninstaller in *Apps*) | `%APPDATA%\pyhttp` |
 | Windows 10/11 | `pyhttp-<version>-windows-x64.exe`: portable, one file, no install | `%APPDATA%\pyhttp` |
-| macOS 11+ | `brew tap pyhttp2/pyhttp https://github.com/pyhttp2/pyhttp-releases && brew install --cask pyhttp2/pyhttp/pyhttp`, or `pyhttp-<version>-macos-arm64.dmg` (drag pyhttp to Applications) | `~/Library/Application Support/pyhttp` |
+| macOS 11+ | `brew install --cask pyhttp2/pyhttp/pyhttp`, or `pyhttp-<version>-macos-arm64.dmg` (drag pyhttp to Applications) | `~/Library/Application Support/pyhttp` |
 | Ubuntu 22.04+, Debian 12+ | `sudo apt install ./pyhttp-<version>-linux-amd64.deb`: installs to `/usr/lib/pyhttp`, adds `pyhttp` to the PATH and an app-menu entry; uses the distro's GTK and WebKitGTK (pulled in as dependencies) | `~/.local/share/pyhttp` |
 
 Running from source keeps using `./data`. In the packaged app, output that would
@@ -507,10 +510,14 @@ python packaging/bump.py 0.1.2
 ```
 
 That sets `__version__`, commits, creates the tag `v0.1.2` and pushes both. The
-tag run publishes the installer, the portable `.exe`, the `.dmg`, `SHA256SUMS.txt`,
-the license files and the Homebrew cask to the public
-[pyhttp-releases](https://github.com/pyhttp2/pyhttp-releases) repository (needs the
-`RELEASE_TOKEN` secret). The Windows runner installs Inno Setup with Chocolatey when
+tag run publishes the installer, the portable `.exe`, the `.dmg`, `SHA256SUMS.txt`
+and the license files to this repository's Releases page, uploads `pyhttp-app` to
+PyPI (secret `PYPI_API_TOKEN`), updates the Homebrew tap
+([homebrew-pyhttp](https://github.com/pyhttp2/homebrew-pyhttp): cask + formula)
+and mirrors everything to
+[pyhttp-releases](https://github.com/pyhttp2/pyhttp-releases) so installs from
+before the move keep updating (the mirror and taps need the `RELEASE_TOKEN`
+secret, a fine-grained PAT with Contents: write on those two repositories). The Windows runner installs Inno Setup with Chocolatey when
 it is not already there. The in-app updater refuses a release without `SHA256SUMS.txt`,
 so keep that step in the workflow. A tag whose version differs from `__version__` is refused,
 because the release name, file names and the in-app update check all come from
@@ -572,8 +579,10 @@ is not allowed, and the name and logo stay with the project. The source code is
 published on PyPI as [`pyhttp-app`](https://pypi.org/project/pyhttp-app/)
 so it can be inspected and installed with pip; you may modify your own copy but
 not distribute the changes. The packaged installer, `.exe`, `.dmg` and `.deb`
-builds are published from the public
-[pyhttp-releases](https://github.com/pyhttp2/pyhttp-releases) repository.
+builds are published on this repository's
+[Releases](https://github.com/pyhttp2/pyhttp/releases) page and mirrored to
+[pyhttp-releases](https://github.com/pyhttp2/pyhttp-releases), the old home,
+so installs from before the move keep updating.
 Bundled open-source components are listed in
 [THIRD-PARTY-NOTICES.md](THIRD-PARTY-NOTICES.md).
 

{pyhttp_app-2.0.1.post1 → pyhttp_app-2.0.2}/README.md

@@ -189,8 +189,11 @@ pyhttp
 ```
 
 On Linux, install the GTK webview bindings first (see *Linux* below) or use
-`pyhttp --browser`. `brew install pyhttp2/pyhttp/pyhttp-app` installs the
-same package through Homebrew (macOS and Linux, Intel and ARM).
+`pyhttp --browser`. `brew install pyhttp2/pyhttp/pyhttp` installs the
+same package through Homebrew (macOS and Linux, Intel and ARM; the tap is
+[pyhttp2/homebrew-pyhttp](https://github.com/pyhttp2/homebrew-pyhttp)) — or tap
+once with `brew tap pyhttp2/pyhttp`, after which plain `brew install pyhttp`,
+`brew upgrade pyhttp` and `brew install --cask pyhttp` all work.
 
 **Windows**: double-click `run.bat`. The window opens without a console.
 WebView2 ships with Windows 10/11.
@@ -297,7 +300,7 @@ Packaged builds bundle Python and every dependency, so users just double-click.
 |---|---|---|
 | Windows 10/11 | `pyhttp-<version>-windows-x64-setup.exe`: installer (per user, no admin rights, into `%LOCALAPPDATA%\Programs\pyhttp`, Start menu entry, optional desktop icon, uninstaller in *Apps*) | `%APPDATA%\pyhttp` |
 | Windows 10/11 | `pyhttp-<version>-windows-x64.exe`: portable, one file, no install | `%APPDATA%\pyhttp` |
-| macOS 11+ | `brew tap pyhttp2/pyhttp https://github.com/pyhttp2/pyhttp-releases && brew install --cask pyhttp2/pyhttp/pyhttp`, or `pyhttp-<version>-macos-arm64.dmg` (drag pyhttp to Applications) | `~/Library/Application Support/pyhttp` |
+| macOS 11+ | `brew install --cask pyhttp2/pyhttp/pyhttp`, or `pyhttp-<version>-macos-arm64.dmg` (drag pyhttp to Applications) | `~/Library/Application Support/pyhttp` |
 | Ubuntu 22.04+, Debian 12+ | `sudo apt install ./pyhttp-<version>-linux-amd64.deb`: installs to `/usr/lib/pyhttp`, adds `pyhttp` to the PATH and an app-menu entry; uses the distro's GTK and WebKitGTK (pulled in as dependencies) | `~/.local/share/pyhttp` |
 
 Running from source keeps using `./data`. In the packaged app, output that would
@@ -358,10 +361,14 @@ python packaging/bump.py 0.1.2
 ```
 
 That sets `__version__`, commits, creates the tag `v0.1.2` and pushes both. The
-tag run publishes the installer, the portable `.exe`, the `.dmg`, `SHA256SUMS.txt`,
-the license files and the Homebrew cask to the public
-[pyhttp-releases](https://github.com/pyhttp2/pyhttp-releases) repository (needs the
-`RELEASE_TOKEN` secret). The Windows runner installs Inno Setup with Chocolatey when
+tag run publishes the installer, the portable `.exe`, the `.dmg`, `SHA256SUMS.txt`
+and the license files to this repository's Releases page, uploads `pyhttp-app` to
+PyPI (secret `PYPI_API_TOKEN`), updates the Homebrew tap
+([homebrew-pyhttp](https://github.com/pyhttp2/homebrew-pyhttp): cask + formula)
+and mirrors everything to
+[pyhttp-releases](https://github.com/pyhttp2/pyhttp-releases) so installs from
+before the move keep updating (the mirror and taps need the `RELEASE_TOKEN`
+secret, a fine-grained PAT with Contents: write on those two repositories). The Windows runner installs Inno Setup with Chocolatey when
 it is not already there. The in-app updater refuses a release without `SHA256SUMS.txt`,
 so keep that step in the workflow. A tag whose version differs from `__version__` is refused,
 because the release name, file names and the in-app update check all come from
@@ -423,8 +430,10 @@ is not allowed, and the name and logo stay with the project. The source code is
 published on PyPI as [`pyhttp-app`](https://pypi.org/project/pyhttp-app/)
 so it can be inspected and installed with pip; you may modify your own copy but
 not distribute the changes. The packaged installer, `.exe`, `.dmg` and `.deb`
-builds are published from the public
-[pyhttp-releases](https://github.com/pyhttp2/pyhttp-releases) repository.
+builds are published on this repository's
+[Releases](https://github.com/pyhttp2/pyhttp/releases) page and mirrored to
+[pyhttp-releases](https://github.com/pyhttp2/pyhttp-releases), the old home,
+so installs from before the move keep updating.
 Bundled open-source components are listed in
 [THIRD-PARTY-NOTICES.md](THIRD-PARTY-NOTICES.md).
 

{pyhttp_app-2.0.1.post1 → pyhttp_app-2.0.2}/pyhttp/__init__.py

@@ -1,6 +1,6 @@
 """pyhttp - a local API client and alternative to Postman, with a collection runner."""
 
-__version__ = "2.0.1.post1"
+__version__ = "2.0.2"
 # sent with every request unless the user sets their own in Settings; the convention is "product/version (+url)"
 USER_AGENT = f"pyhttp/{__version__}"
 __license__ = "pyhttp Free License 1.0 (free for everyone; source not distributed)"

{pyhttp_app-2.0.1.post1 → pyhttp_app-2.0.2}/pyhttp/app.py

@@ -24,7 +24,7 @@ from . import (USER_AGENT, __version__, console, curl, db, mock, monitors, oauth
 from .templating import build_context, render
 
 STATIC_DIR = Path(__file__).parent / "static"
-DEFAULT_RELEASE_REPO = "pyhttp2/pyhttp-releases"  # public repo that holds the .exe/.dmg releases
+DEFAULT_RELEASE_REPO = "pyhttp2/pyhttp"  # public repo whose Releases page holds the .exe/.dmg builds
 try:  # written by packaging/build.py so packaged apps know where their releases live
     from ._build import GITHUB_REPO as _BUILT_REPO
 except ImportError:  # pragma: no cover - source checkout

{pyhttp_app-2.0.1.post1 → pyhttp_app-2.0.2}/pyhttp/updater.py

@@ -31,7 +31,7 @@ from . import USER_AGENT
 FROZEN = bool(getattr(sys, "frozen", False))
 CASK = "pyhttp"
 TAP = "pyhttp2/pyhttp"
-TAP_URL = "https://github.com/pyhttp2/pyhttp-releases"
+TAP_URL = "https://github.com/pyhttp2/homebrew-pyhttp"
 SUMS_FILE = "SHA256SUMS.txt"
 SELF_UPDATE_KINDS = ("installer", "portable", "brew")
 

{pyhttp_app-2.0.1.post1 → pyhttp_app-2.0.2}/pyhttp_app.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pyhttp-app
-Version: 2.0.1.post1
+Version: 2.0.2
 Summary: Local API client and alternative to Postman: collection runner, Postman-compatible scripts, mock servers and an MCP server
 Author-email: pyhttp Dev Team <dev@pyhttp.com>
 License: # pyhttp Free License 1.1
@@ -338,8 +338,11 @@ pyhttp
 ```
 
 On Linux, install the GTK webview bindings first (see *Linux* below) or use
-`pyhttp --browser`. `brew install pyhttp2/pyhttp/pyhttp-app` installs the
-same package through Homebrew (macOS and Linux, Intel and ARM).
+`pyhttp --browser`. `brew install pyhttp2/pyhttp/pyhttp` installs the
+same package through Homebrew (macOS and Linux, Intel and ARM; the tap is
+[pyhttp2/homebrew-pyhttp](https://github.com/pyhttp2/homebrew-pyhttp)) — or tap
+once with `brew tap pyhttp2/pyhttp`, after which plain `brew install pyhttp`,
+`brew upgrade pyhttp` and `brew install --cask pyhttp` all work.
 
 **Windows**: double-click `run.bat`. The window opens without a console.
 WebView2 ships with Windows 10/11.
@@ -446,7 +449,7 @@ Packaged builds bundle Python and every dependency, so users just double-click.
 |---|---|---|
 | Windows 10/11 | `pyhttp-<version>-windows-x64-setup.exe`: installer (per user, no admin rights, into `%LOCALAPPDATA%\Programs\pyhttp`, Start menu entry, optional desktop icon, uninstaller in *Apps*) | `%APPDATA%\pyhttp` |
 | Windows 10/11 | `pyhttp-<version>-windows-x64.exe`: portable, one file, no install | `%APPDATA%\pyhttp` |
-| macOS 11+ | `brew tap pyhttp2/pyhttp https://github.com/pyhttp2/pyhttp-releases && brew install --cask pyhttp2/pyhttp/pyhttp`, or `pyhttp-<version>-macos-arm64.dmg` (drag pyhttp to Applications) | `~/Library/Application Support/pyhttp` |
+| macOS 11+ | `brew install --cask pyhttp2/pyhttp/pyhttp`, or `pyhttp-<version>-macos-arm64.dmg` (drag pyhttp to Applications) | `~/Library/Application Support/pyhttp` |
 | Ubuntu 22.04+, Debian 12+ | `sudo apt install ./pyhttp-<version>-linux-amd64.deb`: installs to `/usr/lib/pyhttp`, adds `pyhttp` to the PATH and an app-menu entry; uses the distro's GTK and WebKitGTK (pulled in as dependencies) | `~/.local/share/pyhttp` |
 
 Running from source keeps using `./data`. In the packaged app, output that would
@@ -507,10 +510,14 @@ python packaging/bump.py 0.1.2
 ```
 
 That sets `__version__`, commits, creates the tag `v0.1.2` and pushes both. The
-tag run publishes the installer, the portable `.exe`, the `.dmg`, `SHA256SUMS.txt`,
-the license files and the Homebrew cask to the public
-[pyhttp-releases](https://github.com/pyhttp2/pyhttp-releases) repository (needs the
-`RELEASE_TOKEN` secret). The Windows runner installs Inno Setup with Chocolatey when
+tag run publishes the installer, the portable `.exe`, the `.dmg`, `SHA256SUMS.txt`
+and the license files to this repository's Releases page, uploads `pyhttp-app` to
+PyPI (secret `PYPI_API_TOKEN`), updates the Homebrew tap
+([homebrew-pyhttp](https://github.com/pyhttp2/homebrew-pyhttp): cask + formula)
+and mirrors everything to
+[pyhttp-releases](https://github.com/pyhttp2/pyhttp-releases) so installs from
+before the move keep updating (the mirror and taps need the `RELEASE_TOKEN`
+secret, a fine-grained PAT with Contents: write on those two repositories). The Windows runner installs Inno Setup with Chocolatey when
 it is not already there. The in-app updater refuses a release without `SHA256SUMS.txt`,
 so keep that step in the workflow. A tag whose version differs from `__version__` is refused,
 because the release name, file names and the in-app update check all come from
@@ -572,8 +579,10 @@ is not allowed, and the name and logo stay with the project. The source code is
 published on PyPI as [`pyhttp-app`](https://pypi.org/project/pyhttp-app/)
 so it can be inspected and installed with pip; you may modify your own copy but
 not distribute the changes. The packaged installer, `.exe`, `.dmg` and `.deb`
-builds are published from the public
-[pyhttp-releases](https://github.com/pyhttp2/pyhttp-releases) repository.
+builds are published on this repository's
+[Releases](https://github.com/pyhttp2/pyhttp/releases) page and mirrored to
+[pyhttp-releases](https://github.com/pyhttp2/pyhttp-releases), the old home,
+so installs from before the move keep updating.
 Bundled open-source components are listed in
 [THIRD-PARTY-NOTICES.md](THIRD-PARTY-NOTICES.md).