mirror of
https://github.com/evroon/bracket.git
synced 2026-01-21 04:28:52 -05:00
ca8a240379
Updates the requirements on [pytest](https://github.com/pytest-dev/pytest) to permit the latest version. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/pytest-dev/pytest/releases">pytest's releases</a>.</em></p> <blockquote> <h2>8.2.0</h2> <h1>pytest 8.2.0 (2024-04-27)</h1> <h2>Deprecations</h2> <ul> <li> <p><a href="https://redirect.github.com/pytest-dev/pytest/issues/12069">#12069</a>: A deprecation warning is now raised when implementations of one of the following hooks request a deprecated <code>py.path.local</code> parameter instead of the <code>pathlib.Path</code> parameter which replaced it:</p> <ul> <li><code>pytest_ignore_collect</code>{.interpreted-text role="hook"} - the <code>path</code> parameter - use <code>collection_path</code> instead.</li> <li><code>pytest_collect_file</code>{.interpreted-text role="hook"} - the <code>path</code> parameter - use <code>file_path</code> instead.</li> <li><code>pytest_pycollect_makemodule</code>{.interpreted-text role="hook"} - the <code>path</code> parameter - use <code>module_path</code> instead.</li> <li><code>pytest_report_header</code>{.interpreted-text role="hook"} - the <code>startdir</code> parameter - use <code>start_path</code> instead.</li> <li><code>pytest_report_collectionfinish</code>{.interpreted-text role="hook"} - the <code>startdir</code> parameter - use <code>start_path</code> instead.</li> </ul> <p>The replacement parameters are available since pytest 7.0.0. The old parameters will be removed in pytest 9.0.0.</p> <p>See <code>legacy-path-hooks-deprecated</code>{.interpreted-text role="ref"} for more details.</p> </li> </ul> <h2>Features</h2> <ul> <li> <p><a href="https://redirect.github.com/pytest-dev/pytest/issues/11871">#11871</a>: Added support for reading command line arguments from a file using the prefix character <code>@</code>, like e.g.: <code>pytest @tests.txt</code>. The file must have one argument per line.</p> <p>See <code>Read arguments from file <args-from-file></code>{.interpreted-text role="ref"} for details.</p> </li> </ul> <h2>Improvements</h2> <ul> <li> <p><a href="https://redirect.github.com/pytest-dev/pytest/issues/11523">#11523</a>: <code>pytest.importorskip</code>{.interpreted-text role="func"} will now issue a warning if the module could be found, but raised <code>ImportError</code>{.interpreted-text role="class"} instead of <code>ModuleNotFoundError</code>{.interpreted-text role="class"}.</p> <p>The warning can be suppressed by passing <code>exc_type=ImportError</code> to <code>pytest.importorskip</code>{.interpreted-text role="func"}.</p> <p>See <code>import-or-skip-import-error</code>{.interpreted-text role="ref"} for details.</p> </li> <li> <p><a href="https://redirect.github.com/pytest-dev/pytest/issues/11728">#11728</a>: For <code>unittest</code>-based tests, exceptions during class cleanup (as raised by functions registered with <code>TestCase.addClassCleanup <unittest.TestCase.addClassCleanup></code>{.interpreted-text role="meth"}) are now reported instead of silently failing.</p> </li> <li> <p><a href="https://redirect.github.com/pytest-dev/pytest/issues/11777">#11777</a>: Text is no longer truncated in the <code>short test summary info</code> section when <code>-vv</code> is given.</p> </li> <li> <p><a href="https://redirect.github.com/pytest-dev/pytest/issues/12112">#12112</a>: Improved namespace packages detection when <code>consider_namespace_packages</code>{.interpreted-text role="confval"} is enabled, covering more situations (like editable installs).</p> </li> <li> <p><a href="https://redirect.github.com/pytest-dev/pytest/issues/9502">#9502</a>: Added <code>PYTEST_VERSION</code>{.interpreted-text role="envvar"} environment variable which is defined at the start of the pytest session and undefined afterwards. It contains the value of <code>pytest.__version__</code>, and among other things can be used to easily check if code is running from within a pytest run.</p> </li> </ul> <h2>Bug Fixes</h2> <ul> <li> <p><a href="https://redirect.github.com/pytest-dev/pytest/issues/12065">#12065</a>: Fixed a regression in pytest 8.0.0 where test classes containing <code>setup_method</code> and tests using <code>@staticmethod</code> or <code>@classmethod</code> would crash with <code>AttributeError: 'NoneType' object has no attribute 'setup_method'</code>.</p> <p>Now the <code>request.instance <pytest.FixtureRequest.instance></code>{.interpreted-text role="attr"} attribute of tests using <code>@staticmethod</code> and <code>@classmethod</code> is no longer <code>None</code>, but a fresh instance of the class, like in non-static methods.</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="6bd3f31344"><code>6bd3f31</code></a> Tweak changelog for 8.2.0</li> <li><a href="9b6219b5e8"><code>9b6219b</code></a> Prepare release version 8.2.0</li> <li><a href="835765c9d3"><code>835765c</code></a> Merge pull request <a href="https://redirect.github.com/pytest-dev/pytest/issues/12130">#12130</a> from bluetech/fixtures-inline</li> <li><a href="7e7503c0b0"><code>7e7503c</code></a> unittest: report class cleanup exceptions (<a href="https://redirect.github.com/pytest-dev/pytest/issues/12250">#12250</a>)</li> <li><a href="882c4da2f3"><code>882c4da</code></a> fixtures: inline <code>fail_fixturefunc</code></li> <li><a href="2e8fb9f140"><code>2e8fb9f</code></a> fixtures: extract a <code>_check_fixturedef</code> method</li> <li><a href="acf2971f46"><code>acf2971</code></a> fixtures: inline <code>_getnextfixturedef</code> into <code>_get_active_fixturedef</code></li> <li><a href="3c77aec1da"><code>3c77aec</code></a> fixtures: move "request" check early</li> <li><a href="d217d68cde"><code>d217d68</code></a> fixtures: inline <code>_compute_fixture_value</code></li> <li><a href="530be28575"><code>530be28</code></a> fixtures: use early return in <code>_get_active_fixturedef</code></li> <li>Additional commits viewable in <a href="https://github.com/pytest-dev/pytest/compare/1.0.0b3...8.2.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>
Demo · Documentation · Quickstart · GitHub · Releases
Tournament system meant to be easy to use. Bracket is written in async Python (with FastAPI) and Next.js as frontend using the Mantine library.
It has the following features:
- Supports single elimination, round-robin and swiss formats.
- Build your tournament structure with multiple stages that can have multiple groups/brackets in them.
- Drag-and-drop matches to different courts or reschedule them to another start time.
- Various dashboard pages are available that can be presented to the public, customized with a logo.
- Create/update teams, and add players to teams.
- Create multiple clubs, with multiple tournaments per club.
- Swiss tournaments can be handled dynamically, with automatic scheduling of matches.
Live Demo
A demo is available for free at https://www.bracketapp.nl/demo. The demo lasts for 30 minutes, after which your data will de deleted.
Quickstart
To quickly run bracket to see how it works, clone it and run docker-compose up:
git clone git@github.com:evroon/bracket.git
cd bracket
sudo docker-compose up -d
This will start the backend and frontend of Bracket, as well as a postgres instance. You should now be able to view bracket at http://localhost:3000. You can log in with the following credentials:
- Username:
test@example.org - Password:
aeGhoe1ahng2Aezai0Dei6Aih6dieHoo.
To insert dummy rows into the database, run:
sudo docker exec bracket-backend pipenv run ./cli.py create-dev-db
See also the quickstart docs.
Development setup
Read the development docs for how to run Bracket for development.
Prerequisites are yarn, postgresql and pipenv to run the frontend, database and backend.
Configuration
Read the configuration docs for how to configure Bracket.
Bracket's backend is configured using .env files (prod.env for production, dev.env for development etc.).
But you can also configure Bracket using environment variables directly, for example by specifying them in the docker-compose.yml.
The frontend doesn't can be configured by environment variables as well, as well as .env files using Next.js' way of loading environment variables.
Running Bracket in production
Read the deployment docs for how to deploy Bracket and run it in production.
Bracket can be run in Docker or by itself (using pipenv and yarn).
Translations
Based on your browser settings, your language should be automatically detected and loaded. For now, there's no manual way of choosing a different language.
Supported Languages
- 🇺🇸 English
en- Default - 🇨🇳 Chinese
zh- Contributed by @Sevichecc - 🇳🇱 Dutch
nl- Contributed by @evroon
More screenshots
Help
If you're having trouble getting Bracket up and running, or have a question about usage or configuration, feel free to ask. The best place to do this is by creating a Discussion.
Supporting Bracket
If you're using Bracket and would like to help support its development, that would be greatly appreciated!
Several areas that we need a bit of help with at the moment are:
- ⭐ Star Bracket on GitHub
- 🌐 Translating: Help make Bracket available to non-native English speakers by adding your language (via crowdin)
- 📣 Spread the word by sharing Bracket to help new users discover it
- 🖥️ Submit a PR to add a new feature, fix a bug, extend/update the docs or something else
See the contribution docs for more information on how to contribute
Contributors
Erik Vroon |
Null |
SevicheCC |
License
Bracket is licensed under AGPL-v3.0.
Please note that any contributions also fall under this license.
See LICENSE