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

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

@@ -1,7 +1,7 @@
 Metadata-Version: 2.4
 Name: pyhttp-app
-Version: 2.0.1
-Summary: A local, Postman-like HTTP client with a collection runner, scripts and an MCP server
+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
         
@@ -147,62 +147,10 @@ Requires-Dist: pyyaml>=6.0
 Requires-Dist: mcp>=2
 Dynamic: license-file
 
-cd C:\Users\vishv\Documents\www\pyhttp\
-C:\Users\vishv\Documents\www\pyhttp\pyhttp\
-claude --dangerously-skip-permissions
-# todo
-- kill port
-lsof -t -i:8765 | xargs kill -9
-
-<!-- - both show waiting while running in parallel -->
-<!-- - pretty/ raw bar with response must not scroll with response - fix that
-- in headers give select all/unselect all button or checkbox
-- auto dropdown in Token from env/global variables
-- if get method gives error show prompt or Tip: that use post or any other method method
-- observed a weird bug that body 1 somehow was doing conflict with body 2, when only sending body 2 getting same error that i must see in body 1 for the response in body 2 can you check this and fix if any such issue can happen -->
-
-<!-- - automatic api tester with a timer, where it will send an report of times and alert if failed api api -->
-<!-- - give mcp so this tool data like api body and etc can be filled and managed by ai , make this fully manageable tool by using ai -->
-- Later build feedback form in www /Users/vishvendra/Documents/www/pyhttp.com and app /Users/vishvendra/Documents/www/pyhttp/ 
-- seo
-
-
-<!-- - update www with all the updates we just made -->
-<!-- - delete all older releases with my name vishvendra singh if possible but keep the release 1.9 and after -->
-<!-- - if response is pushed to bottom by down button to view body the body and and list of bodies component must stretch to the bottm will the response window right now it remains sname, also when click the button to bring the response from bottom to the right it hides body and if i try to click the separator and drag it shows weird behaviour and does not work properly fix these issues and make it better  -->
-<!-- - dependent api - like token triggered automatically when any api is sent a call, so fetch token from using token api, where it will have a pm.environment.set(token) something like this - so it will set token in environment automatically and then call the pi - if put in as dependent api in any other api and set a time after which it must trigger automatically - like token has expired time - implement intelligently in a flow -->
-<!-- - remove my name and keep something like - "pyhttp Dev team - From the unknown to the unowned" like this -  in tagline and owner etc at all the palces in website and tool in current or next releases -->
-<!-- - lets say if there are multiple bodies in api then in scripts i want to give an option to select from - perform test and Pre-request based on bodies 1 or 2 or 3 etc (name of body) so user can select if same test are to be perfomed for all bodies or different - pre-request and test   - for each body - i told you to do this before but not able to see or find this change -->
-<!-- - run with csv - give sample file, also show multiple or single responses in api beside/below api definition or body for each run automatically -->
-<!-- - in current run on right hand side - write name of files in pop when clicked the tab - with little description, right now it is confusing - as user not understanding difference between api.json and api.body.json - do this change quickly and dont spend too much testing on it or build or relese there are more chaning i will be sending then test or do any other process afterward when i tell you -->
-<!-- - highly parallel request without sequence or allow to set in while trying to run on run name and confirmation screen also give button to skip and run directly without giving name -->
-<!-- - make default useragent - pyhttp and version -->
-<!-- - vertical partition compresses the search input box and "run selected" button which does not look good fix that on left hand side - fix ui/ux -->
-<!-- - settings menu seems like falling over each other give spacing and make better ui/ux -->
-<!-- - below button in bottom movies response window, can make this clearer so one can easily know what that button does or any other why make it easy ui/ux -->
-<!-- - put a hamburger menu on left hand side to show hide left hand sidebar -->
-<!-- - when there is an long error from api shown above the json response it adds horizontal scroller, i think you must text wrap that and must not add horizontal scroll in any case -->
-<!-- - tabs like api or body have very little vertical scroll, i think you must not show scroll anywhere instead put tabs above or below - and/or give this setting to set for user -->
-<!-- - rename Tests to scripts and there must be option to select body and apply test to that specific body or all body and separate test can be applied to separate bodies -->
-<!-- work on all of above intelligently and in such a way must be best decision from your research i want to make best http tool as per ui/ux and ease of use point of view -->
-<!-- - also i am thinking to make it free in license for everyone - what do you think -  -->
-<!-- - if i click on any other tab it selects all the bodies, but it must save the state like selected body only even when tabs are changes or this app is opened or closed -->
-<!-- - give cancel button in place of sending when sending api call to cancel running call/calls -->
-<!-- - give select and enclose/open javascript with arrow in left beside line numbers -->
-<!-- - ctrl+enter in windows and command+enter must send it api call -->
-<!-- - clicking tabs must not change the box/card size in settings -->
-<!-- - close icon/button foer current/history right side bar -->
-<!-- - open/cose button for response bar, i mean hide it so one can view entire body similar for response there must option to maximize it to view entire response -->
-<!-- - must be able to move tabs left and right -->
-<!-- - check now must show loading icon and show status beside that only -->
-<!-- - current run and history not showing in mac/windows -->
-<!-- - auto release not working -->
-<!-- - instead of pm.test make it ph or py.test which you feel is good, i feel py. is good in Tests
-- pretty is showing too much space after each line in response of json
-- in tests i keep getting error - invalid systax ("<test script>", line 1) and failing in setting any variables -->
 # pyhttp
 
-A local, Postman-like HTTP client with a built-in collection runner, in its
+A local API client and alternative to Postman — it imports Postman collections
+and runs Postman scripts — with a built-in collection runner, in its
 own desktop window. Everything stays on your machine: requests live in a SQLite
 file, every run writes its responses to plain files, and the backend listens
 only on `127.0.0.1`.
@@ -390,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.
@@ -498,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
@@ -559,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
@@ -624,11 +579,18 @@ 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).
 
+Postman is a trademark of Postman, Inc. pyhttp is an independent project and is
+not affiliated with or endorsed by Postman, Inc.; the name is used only to
+describe compatibility (importing Postman collections, running Postman-style
+scripts).
+
 The app itself stays free. If paid extras ever appear, they will be optional
 add-ons, services or support under their own terms, never a restriction on who
 may use pyhttp.

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

@@ -1,59 +1,7 @@
-cd C:\Users\vishv\Documents\www\pyhttp\
-C:\Users\vishv\Documents\www\pyhttp\pyhttp\
-claude --dangerously-skip-permissions
-# todo
-- kill port
-lsof -t -i:8765 | xargs kill -9
-
-<!-- - both show waiting while running in parallel -->
-<!-- - pretty/ raw bar with response must not scroll with response - fix that
-- in headers give select all/unselect all button or checkbox
-- auto dropdown in Token from env/global variables
-- if get method gives error show prompt or Tip: that use post or any other method method
-- observed a weird bug that body 1 somehow was doing conflict with body 2, when only sending body 2 getting same error that i must see in body 1 for the response in body 2 can you check this and fix if any such issue can happen -->
-
-<!-- - automatic api tester with a timer, where it will send an report of times and alert if failed api api -->
-<!-- - give mcp so this tool data like api body and etc can be filled and managed by ai , make this fully manageable tool by using ai -->
-- Later build feedback form in www /Users/vishvendra/Documents/www/pyhttp.com and app /Users/vishvendra/Documents/www/pyhttp/ 
-- seo
-
-
-<!-- - update www with all the updates we just made -->
-<!-- - delete all older releases with my name vishvendra singh if possible but keep the release 1.9 and after -->
-<!-- - if response is pushed to bottom by down button to view body the body and and list of bodies component must stretch to the bottm will the response window right now it remains sname, also when click the button to bring the response from bottom to the right it hides body and if i try to click the separator and drag it shows weird behaviour and does not work properly fix these issues and make it better  -->
-<!-- - dependent api - like token triggered automatically when any api is sent a call, so fetch token from using token api, where it will have a pm.environment.set(token) something like this - so it will set token in environment automatically and then call the pi - if put in as dependent api in any other api and set a time after which it must trigger automatically - like token has expired time - implement intelligently in a flow -->
-<!-- - remove my name and keep something like - "pyhttp Dev team - From the unknown to the unowned" like this -  in tagline and owner etc at all the palces in website and tool in current or next releases -->
-<!-- - lets say if there are multiple bodies in api then in scripts i want to give an option to select from - perform test and Pre-request based on bodies 1 or 2 or 3 etc (name of body) so user can select if same test are to be perfomed for all bodies or different - pre-request and test   - for each body - i told you to do this before but not able to see or find this change -->
-<!-- - run with csv - give sample file, also show multiple or single responses in api beside/below api definition or body for each run automatically -->
-<!-- - in current run on right hand side - write name of files in pop when clicked the tab - with little description, right now it is confusing - as user not understanding difference between api.json and api.body.json - do this change quickly and dont spend too much testing on it or build or relese there are more chaning i will be sending then test or do any other process afterward when i tell you -->
-<!-- - highly parallel request without sequence or allow to set in while trying to run on run name and confirmation screen also give button to skip and run directly without giving name -->
-<!-- - make default useragent - pyhttp and version -->
-<!-- - vertical partition compresses the search input box and "run selected" button which does not look good fix that on left hand side - fix ui/ux -->
-<!-- - settings menu seems like falling over each other give spacing and make better ui/ux -->
-<!-- - below button in bottom movies response window, can make this clearer so one can easily know what that button does or any other why make it easy ui/ux -->
-<!-- - put a hamburger menu on left hand side to show hide left hand sidebar -->
-<!-- - when there is an long error from api shown above the json response it adds horizontal scroller, i think you must text wrap that and must not add horizontal scroll in any case -->
-<!-- - tabs like api or body have very little vertical scroll, i think you must not show scroll anywhere instead put tabs above or below - and/or give this setting to set for user -->
-<!-- - rename Tests to scripts and there must be option to select body and apply test to that specific body or all body and separate test can be applied to separate bodies -->
-<!-- work on all of above intelligently and in such a way must be best decision from your research i want to make best http tool as per ui/ux and ease of use point of view -->
-<!-- - also i am thinking to make it free in license for everyone - what do you think -  -->
-<!-- - if i click on any other tab it selects all the bodies, but it must save the state like selected body only even when tabs are changes or this app is opened or closed -->
-<!-- - give cancel button in place of sending when sending api call to cancel running call/calls -->
-<!-- - give select and enclose/open javascript with arrow in left beside line numbers -->
-<!-- - ctrl+enter in windows and command+enter must send it api call -->
-<!-- - clicking tabs must not change the box/card size in settings -->
-<!-- - close icon/button foer current/history right side bar -->
-<!-- - open/cose button for response bar, i mean hide it so one can view entire body similar for response there must option to maximize it to view entire response -->
-<!-- - must be able to move tabs left and right -->
-<!-- - check now must show loading icon and show status beside that only -->
-<!-- - current run and history not showing in mac/windows -->
-<!-- - auto release not working -->
-<!-- - instead of pm.test make it ph or py.test which you feel is good, i feel py. is good in Tests
-- pretty is showing too much space after each line in response of json
-- in tests i keep getting error - invalid systax ("<test script>", line 1) and failing in setting any variables -->
 # pyhttp
 
-A local, Postman-like HTTP client with a built-in collection runner, in its
+A local API client and alternative to Postman — it imports Postman collections
+and runs Postman scripts — with a built-in collection runner, in its
 own desktop window. Everything stays on your machine: requests live in a SQLite
 file, every run writes its responses to plain files, and the backend listens
 only on `127.0.0.1`.
@@ -241,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.
@@ -349,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
@@ -410,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
@@ -475,11 +430,18 @@ 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).
 
+Postman is a trademark of Postman, Inc. pyhttp is an independent project and is
+not affiliated with or endorsed by Postman, Inc.; the name is used only to
+describe compatibility (importing Postman collections, running Postman-style
+scripts).
+
 The app itself stays free. If paid extras ever appear, they will be optional
 add-ons, services or support under their own terms, never a restriction on who
 may use pyhttp.

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

@@ -1,6 +1,6 @@
-"""pyhttp - a local, Postman-like HTTP client with a collection runner."""
+"""pyhttp - a local API client and alternative to Postman, with a collection runner."""
 
-__version__ = "2.0.1"
+__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 → pyhttp_app-2.0.2}/pyhttp/__main__.py

@@ -189,7 +189,7 @@ def main() -> None:
         from . import mcp
         mcp.main(sys.argv[2:], DEFAULT_DATA_DIR)
         return
-    parser = argparse.ArgumentParser(prog="pyhttp", description="Local Postman-like HTTP client",
+    parser = argparse.ArgumentParser(prog="pyhttp", description="Local API client (alternative to Postman)",
                                      epilog="Headless runs for CI: pyhttp run --help")
     mode = parser.add_mutually_exclusive_group()
     mode.add_argument("--browser", action="store_true", help="open the UI in your web browser")

{pyhttp_app-2.0.1 → 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 → pyhttp_app-2.0.2}/pyhttp/mcp.py

@@ -25,7 +25,7 @@ BODY_LIMIT = 40_000  # characters of a response body per tool result
 
 server = MCPServer(
     "pyhttp",
-    instructions="A local HTTP client (Postman-like). Requests live in folders, can hold several named "
+    instructions="A local HTTP client (alternative to Postman). Requests live in folders, can hold several named "
     "bodies, tests and scripts, and use {{variables}} from the active environment and globals. "
     "send_request/send return the response; run executes many requests in order and reports.",
 )

{pyhttp_app-2.0.1 → 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 → pyhttp_app-2.0.2}/pyhttp_app.egg-info/PKG-INFO

@@ -1,7 +1,7 @@
 Metadata-Version: 2.4
 Name: pyhttp-app
-Version: 2.0.1
-Summary: A local, Postman-like HTTP client with a collection runner, scripts and an MCP server
+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
         
@@ -147,62 +147,10 @@ Requires-Dist: pyyaml>=6.0
 Requires-Dist: mcp>=2
 Dynamic: license-file
 
-cd C:\Users\vishv\Documents\www\pyhttp\
-C:\Users\vishv\Documents\www\pyhttp\pyhttp\
-claude --dangerously-skip-permissions
-# todo
-- kill port
-lsof -t -i:8765 | xargs kill -9
-
-<!-- - both show waiting while running in parallel -->
-<!-- - pretty/ raw bar with response must not scroll with response - fix that
-- in headers give select all/unselect all button or checkbox
-- auto dropdown in Token from env/global variables
-- if get method gives error show prompt or Tip: that use post or any other method method
-- observed a weird bug that body 1 somehow was doing conflict with body 2, when only sending body 2 getting same error that i must see in body 1 for the response in body 2 can you check this and fix if any such issue can happen -->
-
-<!-- - automatic api tester with a timer, where it will send an report of times and alert if failed api api -->
-<!-- - give mcp so this tool data like api body and etc can be filled and managed by ai , make this fully manageable tool by using ai -->
-- Later build feedback form in www /Users/vishvendra/Documents/www/pyhttp.com and app /Users/vishvendra/Documents/www/pyhttp/ 
-- seo
-
-
-<!-- - update www with all the updates we just made -->
-<!-- - delete all older releases with my name vishvendra singh if possible but keep the release 1.9 and after -->
-<!-- - if response is pushed to bottom by down button to view body the body and and list of bodies component must stretch to the bottm will the response window right now it remains sname, also when click the button to bring the response from bottom to the right it hides body and if i try to click the separator and drag it shows weird behaviour and does not work properly fix these issues and make it better  -->
-<!-- - dependent api - like token triggered automatically when any api is sent a call, so fetch token from using token api, where it will have a pm.environment.set(token) something like this - so it will set token in environment automatically and then call the pi - if put in as dependent api in any other api and set a time after which it must trigger automatically - like token has expired time - implement intelligently in a flow -->
-<!-- - remove my name and keep something like - "pyhttp Dev team - From the unknown to the unowned" like this -  in tagline and owner etc at all the palces in website and tool in current or next releases -->
-<!-- - lets say if there are multiple bodies in api then in scripts i want to give an option to select from - perform test and Pre-request based on bodies 1 or 2 or 3 etc (name of body) so user can select if same test are to be perfomed for all bodies or different - pre-request and test   - for each body - i told you to do this before but not able to see or find this change -->
-<!-- - run with csv - give sample file, also show multiple or single responses in api beside/below api definition or body for each run automatically -->
-<!-- - in current run on right hand side - write name of files in pop when clicked the tab - with little description, right now it is confusing - as user not understanding difference between api.json and api.body.json - do this change quickly and dont spend too much testing on it or build or relese there are more chaning i will be sending then test or do any other process afterward when i tell you -->
-<!-- - highly parallel request without sequence or allow to set in while trying to run on run name and confirmation screen also give button to skip and run directly without giving name -->
-<!-- - make default useragent - pyhttp and version -->
-<!-- - vertical partition compresses the search input box and "run selected" button which does not look good fix that on left hand side - fix ui/ux -->
-<!-- - settings menu seems like falling over each other give spacing and make better ui/ux -->
-<!-- - below button in bottom movies response window, can make this clearer so one can easily know what that button does or any other why make it easy ui/ux -->
-<!-- - put a hamburger menu on left hand side to show hide left hand sidebar -->
-<!-- - when there is an long error from api shown above the json response it adds horizontal scroller, i think you must text wrap that and must not add horizontal scroll in any case -->
-<!-- - tabs like api or body have very little vertical scroll, i think you must not show scroll anywhere instead put tabs above or below - and/or give this setting to set for user -->
-<!-- - rename Tests to scripts and there must be option to select body and apply test to that specific body or all body and separate test can be applied to separate bodies -->
-<!-- work on all of above intelligently and in such a way must be best decision from your research i want to make best http tool as per ui/ux and ease of use point of view -->
-<!-- - also i am thinking to make it free in license for everyone - what do you think -  -->
-<!-- - if i click on any other tab it selects all the bodies, but it must save the state like selected body only even when tabs are changes or this app is opened or closed -->
-<!-- - give cancel button in place of sending when sending api call to cancel running call/calls -->
-<!-- - give select and enclose/open javascript with arrow in left beside line numbers -->
-<!-- - ctrl+enter in windows and command+enter must send it api call -->
-<!-- - clicking tabs must not change the box/card size in settings -->
-<!-- - close icon/button foer current/history right side bar -->
-<!-- - open/cose button for response bar, i mean hide it so one can view entire body similar for response there must option to maximize it to view entire response -->
-<!-- - must be able to move tabs left and right -->
-<!-- - check now must show loading icon and show status beside that only -->
-<!-- - current run and history not showing in mac/windows -->
-<!-- - auto release not working -->
-<!-- - instead of pm.test make it ph or py.test which you feel is good, i feel py. is good in Tests
-- pretty is showing too much space after each line in response of json
-- in tests i keep getting error - invalid systax ("<test script>", line 1) and failing in setting any variables -->
 # pyhttp
 
-A local, Postman-like HTTP client with a built-in collection runner, in its
+A local API client and alternative to Postman — it imports Postman collections
+and runs Postman scripts — with a built-in collection runner, in its
 own desktop window. Everything stays on your machine: requests live in a SQLite
 file, every run writes its responses to plain files, and the backend listens
 only on `127.0.0.1`.
@@ -390,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.
@@ -498,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
@@ -559,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
@@ -624,11 +579,18 @@ 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).
 
+Postman is a trademark of Postman, Inc. pyhttp is an independent project and is
+not affiliated with or endorsed by Postman, Inc.; the name is used only to
+describe compatibility (importing Postman collections, running Postman-style
+scripts).
+
 The app itself stays free. If paid extras ever appear, they will be optional
 add-ons, services or support under their own terms, never a restriction on who
 may use pyhttp.

{pyhttp_app-2.0.1 → pyhttp_app-2.0.2}/pyproject.toml

@@ -11,7 +11,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "pyhttp-app"
-description = "A local, Postman-like HTTP client with a collection runner, scripts and an MCP server"
+description = "Local API client and alternative to Postman: collection runner, Postman-compatible scripts, mock servers and an MCP server"
 readme = "README.md"
 requires-python = ">=3.10"
 license = { file = "LICENSE.md" }