Question: reason for dev mode in production #481
Comments
|
Ik not sure what you mean, the documentation page for running bracket in production doesn't mention any development environment: |
|
see also #441 |
|
I am so sorry, I was really busy and I forgot that I already asked this question. sorry for wasting your time. keep up the amazing work |
|
Ah no problem! Thanks :) |
evroon
pushed a commit
that referenced
this issue
Apr 22, 2024
Updates the requirements on [pluggy](https://github.com/pytest-dev/pluggy) to permit the latest version. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/pytest-dev/pluggy/blob/main/CHANGELOG.rst">pluggy's changelog</a>.</em></p> <blockquote> <h1>pluggy 1.5.0 (2024-04-19)</h1> <h2>Features</h2> <ul> <li> <p><code>[#178](pytest-dev/pluggy#178) <https://github.com/pytest-dev/pluggy/issues/178></code>_: Add support for deprecating specific hook parameters, or more generally, for issuing a warning whenever a hook implementation requests certain parameters.</p> <p>See :ref:<code>warn_on_impl</code> for details.</p> </li> </ul> <h2>Bug Fixes</h2> <ul> <li><code>[#481](pytest-dev/pluggy#481) <https://github.com/pytest-dev/pluggy/issues/481></code>_: <code>PluginManager.get_plugins()</code> no longer returns <code>None</code> for blocked plugins.</li> </ul> <h1>pluggy 1.4.0 (2024-01-24)</h1> <h2>Features</h2> <ul> <li> <p><code>[#463](pytest-dev/pluggy#463) <https://github.com/pytest-dev/pluggy/issues/463></code>_: A warning :class:<code>~pluggy.PluggyTeardownRaisedWarning</code> is now issued when an old-style hookwrapper raises an exception during teardown. See the warning documentation for more details.</p> </li> <li> <p><code>[#471](pytest-dev/pluggy#471) <https://github.com/pytest-dev/pluggy/issues/471></code>_: Add :func:<code>PluginManager.unblock <pluggy.PluginManager.unblock></code> method to unblock a plugin by plugin name.</p> </li> </ul> <h2>Bug Fixes</h2> <ul> <li> <p><code>[#441](pytest-dev/pluggy#441) <https://github.com/pytest-dev/pluggy/issues/441></code>_: Fix :func:<code>~pluggy.HookCaller.call_extra()</code> extra methods getting ordered before everything else in some circumstances. Regressed in pluggy 1.1.0.</p> </li> <li> <p><code>[#438](pytest-dev/pluggy#438) <https://github.com/pytest-dev/pluggy/issues/438></code>_: Fix plugins registering other plugins in a hook when the other plugins implement the same hook itself. Regressed in pluggy 1.1.0.</p> </li> </ul> <h1>pluggy 1.3.0 (2023-08-26)</h1> <h2>Deprecations and Removals</h2> <ul> <li><code>[#426](pytest-dev/pluggy#426) <https://github.com/pytest-dev/pluggy/issues/426></code>_: Python 3.7 is no longer supported.</li> </ul> <h2>Features</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pytest-dev/pluggy/commit/f8aa4a009716a7994f2f6c1947d9fa69feccbdd5"><code>f8aa4a0</code></a> Preparing release 1.5.0</li> <li><a href="https://github.com/pytest-dev/pluggy/commit/b4a8c92fb15dc05376ddb9b48e601be00ee3ee1b"><code>b4a8c92</code></a> Merge pull request <a href="https://github.com/pytest-dev/pluggy/issues/495">#495</a> from bluetech/warn-on-impl-args</li> <li><a href="https://github.com/pytest-dev/pluggy/commit/6f6ea680ca5a1f73dca356eb23c0dd6bd5f7190e"><code>6f6ea68</code></a> Add support deprecating hook parameters</li> <li><a href="https://github.com/pytest-dev/pluggy/commit/91f88d28e30c12612d671100b7a60dfbf4990446"><code>91f88d2</code></a> Merge pull request <a href="https://github.com/pytest-dev/pluggy/issues/496">#496</a> from bluetech/codecov-action</li> <li><a href="https://github.com/pytest-dev/pluggy/commit/89ce829b44274569de83173867ce29828b620fe8"><code>89ce829</code></a> ci: replace upload-coverage script with codecov github action</li> <li><a href="https://github.com/pytest-dev/pluggy/commit/29f104d21f06f0bf1415a8e872657bc10a768954"><code>29f104d</code></a> Lift pluggy (<a href="https://github.com/pytest-dev/pluggy/issues/493">#493</a>)</li> <li><a href="https://github.com/pytest-dev/pluggy/commit/c2b36b44af5c2530813e18553b54158535d4820a"><code>c2b36b4</code></a> Merge pull request <a href="https://github.com/pytest-dev/pluggy/issues/491">#491</a> from pytest-dev/pre-commit-ci-update-config</li> <li><a href="https://github.com/pytest-dev/pluggy/commit/2b533c9d9f7421c9353aa32da967733bfe4c1c85"><code>2b533c9</code></a> [pre-commit.ci] pre-commit autoupdate</li> <li><a href="https://github.com/pytest-dev/pluggy/commit/04d1bcdbc751a90ff79b72caf85dc96e1664ae45"><code>04d1bcd</code></a> [pre-commit.ci] pre-commit autoupdate (<a href="https://github.com/pytest-dev/pluggy/issues/490">#490</a>)</li> <li><a href="https://github.com/pytest-dev/pluggy/commit/f74e94b17d986c18e9039af87ecded9c9546ac32"><code>f74e94b</code></a> [pre-commit.ci] pre-commit autoupdate (<a href="https://github.com/pytest-dev/pluggy/issues/489">#489</a>)</li> <li>Additional commits viewable in <a href="https://github.com/pytest-dev/pluggy/compare/0.3.0...1.5.0">compare view</a></li> </ul> </details> <br /> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Your documentation seems to suggest that the environment needs to be set to "DEVELOPMENT" as per your docker compose file. If it can be avoided i would prefer to not do that in production. Is there a specific reason for that and if so can I still avoid that?
The text was updated successfully, but these errors were encountered: