0f370213d1
Bumps [pyinstaller](https://github.com/pyinstaller/pyinstaller) from 6.1.0 to 6.2.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/pyinstaller/pyinstaller/releases">pyinstaller's releases</a>.</em></p> <blockquote> <h2>v6.2.0</h2> <p>Please see the <a href="https://pyinstaller.org/en/v6.2.0/CHANGES.html#id1">v6.2.0 section of the changelog</a> for a list of the changes since v6.1.0.</p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/pyinstaller/pyinstaller/blob/develop/doc/CHANGES.rst">pyinstaller's changelog</a>.</em></p> <blockquote> <h2>6.2.0 (2023-11-11)</h2> <p>Features</p> <pre><code> * (macOS) At the end of analysis, verify the macOS SDK version reported by binaries to be collected, and warn when the version is either invalid (0.0.0) or too low (< 10.9.0). Such binaries will likely cause issues with code-signing and hardened runtime. (:issue:`8043`) * If the ``argcomplete`` Python module is installed, PyInstaller will use it enable tab completion for its CLI tools. PyInstaller CLIs can still be used without this optional dependency. To install ``argcomplete`` with PyInstaller, you can put ``pyinstaller[completion]`` in your dependencies. See also `the argcomplete documentation <https://kislyuk.github.io/argcomplete/>`_. (:issue:`8008`) <p>Bugfix</p> <pre><code> * (macOS) Fix the bug in binary processing and caching that would update the binary cache index before performing macOS-specific processing (architecture validation, path rewriting). If, for example, architecture validation failed during a build, subsequent build attempts with enabled binary cache (i.e., without the :option:`--clean` option) would pick up the partially-processed binary file from the cache, bypassing the architecture validation. NOTE: the existing binary caches need to be purged manually (using :option:`--clean` option once) for the fix to take effect! (:issue:`8068`) * (macOS) Prevent collection of ``.DS_Store`` files, which might be present in build environment's package directories after user navigated them using the Finder app. (:issue:`8042`) * (Windows) Fix marshal error at the start of binary dependency analysis, caused by inferred DLL search path ending up an instance of :class:`pathlib.Path` instead of :class:`str`. (:issue:`8081`) * Bump the required ``packaging`` version to 22.0, which is required for proper handling of metadata that contains markers with ``extra``\ s. (:issue:`8061`) * Fix erroneous DLL parent path preservation when :data:`sys.base_prefix` itself is a symbolic link. In such case, we need to exclude both resolved and unresolved path variant for ``sys.base_prefix``, in order to prevent either from ending up in the list of directories for which DLL parent paths are preserved. Failing to do so, for example, caused ``_ctypes`` failing to load in an application build on Windows with Python installed via ``scoop``, due to ``libffi-8.dll`` having spuriously preserved the parent directory path instead of being collected to top-level application directory. (:issue:`8023`) * Fix matching of pre-release versions in :func:`PyInstaller.utils.hooks.check_requirement` and &lt;/tr&gt;&lt;/table&gt; </code></pre> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
---|---|---|
.github | ||
docs | ||
examples | ||
mitmproxy | ||
release | ||
test | ||
web | ||
.gitattributes | ||
.gitignore | ||
CHANGELOG.md | ||
CONTRIBUTING.md | ||
LICENSE | ||
MANIFEST.in | ||
README.md | ||
SECURITY.md | ||
codecov.yml | ||
pyproject.toml | ||
setup.cfg |
README.md
mitmproxy
mitmproxy
is an interactive, SSL/TLS-capable intercepting proxy with a console
interface for HTTP/1, HTTP/2, and WebSockets.
mitmdump
is the command-line version of mitmproxy. Think tcpdump for HTTP.
mitmweb
is a web-based interface for mitmproxy.
Installation
The installation instructions are here. If you want to install from source, see CONTRIBUTING.md.
Documentation & Help
General information, tutorials, and precompiled binaries can be found on the mitmproxy website.
The documentation for mitmproxy is available on our website:
If you have questions on how to use mitmproxy, please use GitHub Discussions!
Contributing
As an open source project, mitmproxy welcomes contributions of all forms.
Also, please feel free to join our developer Slack! However, please note that the primary purpose of our Slack is direct communication between maintainers and contributors. If you have questions where the answer might be valuable to others, please use GitHub Discussions and not Slack.