countdown-cli 1.0.3__tar.gz → 1.1.0__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (48) hide show
  1. countdown_cli-1.1.0/.claude/settings.local.json +22 -0
  2. countdown_cli-1.1.0/.gitattributes +1 -0
  3. countdown_cli-1.1.0/.github/labels.yml +66 -0
  4. countdown_cli-1.1.0/.github/release-drafter.yml +29 -0
  5. countdown_cli-1.1.0/.github/workflows/labeler.yml +19 -0
  6. countdown_cli-1.1.0/.github/workflows/release.yml +66 -0
  7. countdown_cli-1.1.0/.github/workflows/tests.yml +71 -0
  8. countdown_cli-1.1.0/.gitignore +10 -0
  9. countdown_cli-1.1.0/.pre-commit-config.yaml +15 -0
  10. countdown_cli-1.1.0/.python-version-default +1 -0
  11. countdown_cli-1.1.0/CODE_OF_CONDUCT.rst +105 -0
  12. countdown_cli-1.1.0/CONTRIBUTING.rst +121 -0
  13. {countdown_cli-1.0.3 → countdown_cli-1.1.0}/PKG-INFO +12 -14
  14. countdown_cli-1.1.0/codecov.yml +9 -0
  15. countdown_cli-1.1.0/htmlcov/.gitignore +2 -0
  16. countdown_cli-1.1.0/htmlcov/class_index.html +183 -0
  17. countdown_cli-1.1.0/htmlcov/coverage_html_cb_6fb7b396.js +733 -0
  18. countdown_cli-1.1.0/htmlcov/coverage_html_cb_da166b87.js +717 -0
  19. countdown_cli-1.1.0/htmlcov/favicon_32_cb_58284776.png +0 -0
  20. countdown_cli-1.1.0/htmlcov/function_index.html +683 -0
  21. countdown_cli-1.1.0/htmlcov/index.html +164 -0
  22. countdown_cli-1.1.0/htmlcov/keybd_closed_cb_ce680311.png +0 -0
  23. countdown_cli-1.1.0/htmlcov/status.json +1 -0
  24. countdown_cli-1.1.0/htmlcov/style_cb_6b508a39.css +377 -0
  25. countdown_cli-1.1.0/htmlcov/style_cb_8e611ae1.css +337 -0
  26. countdown_cli-1.1.0/htmlcov/z_55719c21e2af63da___init___py.html +105 -0
  27. countdown_cli-1.1.0/htmlcov/z_55719c21e2af63da___main___py.html +236 -0
  28. countdown_cli-1.1.0/htmlcov/z_55719c21e2af63da_digits_py.html +158 -0
  29. countdown_cli-1.1.0/htmlcov/z_a44f0ac069e85531___init___py.html +100 -0
  30. countdown_cli-1.1.0/htmlcov/z_a44f0ac069e85531_conftest_py.html +128 -0
  31. countdown_cli-1.1.0/htmlcov/z_a44f0ac069e85531_test_main_py.html +645 -0
  32. countdown_cli-1.1.0/images/1457.png +0 -0
  33. countdown_cli-1.1.0/images/3253.png +0 -0
  34. countdown_cli-1.1.0/images/python-morsels-logo.png +0 -0
  35. countdown_cli-1.1.0/justfile +46 -0
  36. countdown_cli-1.1.0/noxfile.py +27 -0
  37. countdown_cli-1.1.0/pyproject.toml +96 -0
  38. {countdown_cli-1.0.3 → countdown_cli-1.1.0}/src/countdown/__main__.py +28 -17
  39. countdown_cli-1.1.0/src/countdown/digits.py +59 -0
  40. countdown_cli-1.1.0/src/countdown/numbers.txt +36 -0
  41. countdown_cli-1.1.0/tests/__init__.py +1 -0
  42. countdown_cli-1.1.0/tests/conftest.py +29 -0
  43. countdown_cli-1.1.0/tests/test_main.py +546 -0
  44. countdown_cli-1.1.0/uv.lock +319 -0
  45. countdown_cli-1.0.3/pyproject.toml +0 -72
  46. {countdown_cli-1.0.3 → countdown_cli-1.1.0}/LICENSE.rst +0 -0
  47. {countdown_cli-1.0.3 → countdown_cli-1.1.0}/README.rst +0 -0
  48. {countdown_cli-1.0.3 → countdown_cli-1.1.0}/src/countdown/__init__.py +0 -0
@@ -0,0 +1,22 @@
1
+ {
2
+ "permissions": {
3
+ "allow": [
4
+ "Bash(uv sync:*)",
5
+ "Bash(just --list:*)",
6
+ "Bash(just test:*)",
7
+ "Bash(uv run pytest:*)",
8
+ "Bash(just check:*)",
9
+ "Bash(uv run python:*)",
10
+ "Bash(just lint:*)",
11
+ "Bash(uv run:*)",
12
+ "Bash(uvx nox:*)",
13
+ "Bash(just test-all)",
14
+ "WebSearch",
15
+ "WebFetch(domain:nox.thea.codes)",
16
+ "Bash(uv build:*)",
17
+ "Bash(unzip:*)"
18
+ ],
19
+ "deny": [],
20
+ "ask": []
21
+ }
22
+ }
@@ -0,0 +1 @@
1
+ * text=auto eol=lf
@@ -0,0 +1,66 @@
1
+ ---
2
+ # Labels names are important as they are used by Release Drafter to decide
3
+ # regarding where to record them in changelog or if to skip them.
4
+ #
5
+ # The repository labels will be automatically configured using this file and
6
+ # the GitHub Action https://github.com/marketplace/actions/github-labeler.
7
+ - name: breaking
8
+ description: Breaking Changes
9
+ color: bfd4f2
10
+ - name: bug
11
+ description: Something isn't working
12
+ color: d73a4a
13
+ - name: build
14
+ description: Build System and Dependencies
15
+ color: bfdadc
16
+ - name: ci
17
+ description: Continuous Integration
18
+ color: 4a97d6
19
+ - name: dependencies
20
+ description: Pull requests that update a dependency file
21
+ color: 0366d6
22
+ - name: documentation
23
+ description: Improvements or additions to documentation
24
+ color: 0075ca
25
+ - name: duplicate
26
+ description: This issue or pull request already exists
27
+ color: cfd3d7
28
+ - name: enhancement
29
+ description: New feature or request
30
+ color: a2eeef
31
+ - name: github_actions
32
+ description: Pull requests that update Github_actions code
33
+ color: "000000"
34
+ - name: good first issue
35
+ description: Good for newcomers
36
+ color: 7057ff
37
+ - name: help wanted
38
+ description: Extra attention is needed
39
+ color: 008672
40
+ - name: invalid
41
+ description: This doesn't seem right
42
+ color: e4e669
43
+ - name: performance
44
+ description: Performance
45
+ color: "016175"
46
+ - name: python
47
+ description: Pull requests that update Python code
48
+ color: 2b67c6
49
+ - name: question
50
+ description: Further information is requested
51
+ color: d876e3
52
+ - name: refactoring
53
+ description: Refactoring
54
+ color: ef67c4
55
+ - name: removal
56
+ description: Removals and Deprecations
57
+ color: 9ae7ea
58
+ - name: style
59
+ description: Style
60
+ color: c120e5
61
+ - name: testing
62
+ description: Testing
63
+ color: b1fc6f
64
+ - name: wontfix
65
+ description: This will not be worked on
66
+ color: ffffff
@@ -0,0 +1,29 @@
1
+ categories:
2
+ - title: ":boom: Breaking Changes"
3
+ label: "breaking"
4
+ - title: ":rocket: Features"
5
+ label: "enhancement"
6
+ - title: ":fire: Removals and Deprecations"
7
+ label: "removal"
8
+ - title: ":beetle: Fixes"
9
+ label: "bug"
10
+ - title: ":racehorse: Performance"
11
+ label: "performance"
12
+ - title: ":rotating_light: Testing"
13
+ label: "testing"
14
+ - title: ":construction_worker: Continuous Integration"
15
+ label: "ci"
16
+ - title: ":books: Documentation"
17
+ label: "documentation"
18
+ - title: ":hammer: Refactoring"
19
+ label: "refactoring"
20
+ - title: ":lipstick: Style"
21
+ label: "style"
22
+ - title: ":package: Dependencies"
23
+ labels:
24
+ - "dependencies"
25
+ - "build"
26
+ template: |
27
+ ## Changes
28
+
29
+ $CHANGES
@@ -0,0 +1,19 @@
1
+ name: Labeler
2
+
3
+ on:
4
+ push:
5
+ branches:
6
+ - main
7
+ - master
8
+
9
+ jobs:
10
+ labeler:
11
+ runs-on: ubuntu-latest
12
+ steps:
13
+ - name: Check out the repository
14
+ uses: actions/checkout@v3.3.0
15
+
16
+ - name: Run Labeler
17
+ uses: crazy-max/ghaction-github-labeler@v3.1.1
18
+ with:
19
+ skip-delete: true
@@ -0,0 +1,66 @@
1
+ name: Release
2
+
3
+ on:
4
+ push:
5
+ branches:
6
+ - main
7
+ - master
8
+
9
+ jobs:
10
+ release:
11
+ name: Release
12
+ runs-on: ubuntu-latest
13
+ steps:
14
+ - name: Check out the repository
15
+ uses: actions/checkout@v4
16
+ with:
17
+ fetch-depth: 2
18
+
19
+ - name: Set up Python
20
+ uses: actions/setup-python@v5
21
+ with:
22
+ python-version: "3.12"
23
+
24
+ - name: Install uv
25
+ uses: astral-sh/setup-uv@v5
26
+
27
+ - name: Check if there is a parent commit
28
+ id: check-parent-commit
29
+ run: |
30
+ echo "::set-output name=sha::$(git rev-parse --verify --quiet HEAD^)"
31
+
32
+ - name: Detect and tag new version
33
+ id: check-version
34
+ if: steps.check-parent-commit.outputs.sha
35
+ uses: salsify/action-detect-and-tag-new-version@v2.0.1
36
+ with:
37
+ version-command: |
38
+ bash -o pipefail -c "grep '^version =' pyproject.toml | awk -F '\"' '{ print \$2 }'"
39
+
40
+ - name: Bump version for developmental release
41
+ if: "! steps.check-version.outputs.tag"
42
+ run: |
43
+ current_version=$(grep '^version =' pyproject.toml | awk -F '"' '{ print $2 }')
44
+ IFS='.' read -r major minor patch <<< "$current_version"
45
+ new_patch=$((patch + 1))
46
+ dev_version="${major}.${minor}.${new_patch}.dev$(date +%s)"
47
+ sed -i "s/^version = .*/version = \"$dev_version\"/" pyproject.toml
48
+ echo "Bumped version from $current_version to $dev_version"
49
+
50
+ - name: Build package
51
+ run: |
52
+ uv build
53
+
54
+ - name: Publish package on PyPI
55
+ if: steps.check-version.outputs.tag
56
+ uses: pypa/gh-action-pypi-publish@release/v1
57
+ with:
58
+ password: ${{ secrets.PYPI_TOKEN }}
59
+
60
+ - name: Publish the release notes
61
+ uses: release-drafter/release-drafter@v5.18.1
62
+ with:
63
+ publish: ${{ steps.check-version.outputs.tag != '' }}
64
+ tag: ${{ steps.check-version.outputs.tag }}
65
+ env:
66
+ GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
@@ -0,0 +1,71 @@
1
+ name: Tests
2
+
3
+ on:
4
+ - push
5
+ - pull_request
6
+
7
+ jobs:
8
+ build-package:
9
+ name: Build & verify package
10
+ runs-on: ubuntu-latest
11
+
12
+ steps:
13
+ - uses: actions/checkout@v4
14
+ with:
15
+ fetch-depth: 0
16
+
17
+ - uses: hynek/build-and-inspect-python-package@v2
18
+ id: baipp
19
+
20
+ outputs:
21
+ python-versions: ${{ steps.baipp.outputs.supported_python_classifiers_json_array }}
22
+
23
+ tests:
24
+ name: Tests on ${{ matrix.python-version }}
25
+ needs: build-package
26
+ runs-on: ubuntu-latest
27
+ strategy:
28
+ fail-fast: false
29
+ matrix:
30
+ python-version: ${{ fromJson(needs.build-package.outputs.python-versions) }}
31
+
32
+ steps:
33
+ - uses: actions/checkout@v4
34
+ - name: Download pre-built packages
35
+ uses: actions/download-artifact@v4
36
+ with:
37
+ name: Packages
38
+ path: dist
39
+ - run: tar xf dist/*.tar.gz --strip-components=1
40
+ - uses: actions/setup-python@v5
41
+ with:
42
+ python-version: ${{ matrix.python-version }}
43
+ allow-prereleases: true
44
+
45
+ - name: Install uv
46
+ uses: astral-sh/setup-uv@v5
47
+
48
+ - name: Install nox
49
+ run: uv tool install nox
50
+
51
+ - name: Run tests with nox
52
+ run: uvx nox --force-color --python=${{ matrix.python-version }} -s tests
53
+
54
+ - name: Upload coverage to Codecov (Python 3.12 only)
55
+ if: matrix.python-version == '3.12'
56
+ uses: codecov/codecov-action@v4
57
+
58
+ required-checks-pass:
59
+ name: Ensure everything required is passing for branch protection
60
+ if: always()
61
+
62
+ needs:
63
+ - tests
64
+
65
+ runs-on: ubuntu-latest
66
+
67
+ steps:
68
+ - name: Decide whether the needed jobs succeeded or failed
69
+ uses: re-actors/alls-green@release/v1
70
+ with:
71
+ jobs: ${{ toJSON(needs) }}
@@ -0,0 +1,10 @@
1
+ .mypy_cache/
2
+ /.coverage
3
+ /.coverage.*
4
+ /.nox/
5
+ /.python-version
6
+ /.pytype/
7
+ /dist/
8
+ /docs/_build/
9
+ /src/*.egg-info/
10
+ __pycache__/
@@ -0,0 +1,15 @@
1
+ repos:
2
+ - repo: https://github.com/astral-sh/ruff-pre-commit
3
+ rev: v0.4.0
4
+ hooks:
5
+ - id: ruff
6
+ args: [--fix]
7
+ - id: ruff-format
8
+ - repo: https://github.com/pre-commit/pre-commit-hooks
9
+ rev: v4.6.0
10
+ hooks:
11
+ - id: check-added-large-files
12
+ - id: check-toml
13
+ - id: check-yaml
14
+ - id: end-of-file-fixer
15
+ - id: trailing-whitespace
@@ -0,0 +1 @@
1
+ 3.12
@@ -0,0 +1,105 @@
1
+ Contributor Covenant Code of Conduct
2
+ ====================================
3
+
4
+ Our Pledge
5
+ ----------
6
+
7
+ We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
8
+
9
+ We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
10
+
11
+
12
+ Our Standards
13
+ -------------
14
+
15
+ Examples of behavior that contributes to a positive environment for our community include:
16
+
17
+ - Demonstrating empathy and kindness toward other people
18
+ - Being respectful of differing opinions, viewpoints, and experiences
19
+ - Giving and gracefully accepting constructive feedback
20
+ - Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
21
+ - Focusing on what is best not just for us as individuals, but for the overall community
22
+
23
+ Examples of unacceptable behavior include:
24
+
25
+ - The use of sexualized language or imagery, and sexual attention or
26
+ advances of any kind
27
+ - Trolling, insulting or derogatory comments, and personal or political attacks
28
+ - Public or private harassment
29
+ - Publishing others' private information, such as a physical or email
30
+ address, without their explicit permission
31
+ - Other conduct which could reasonably be considered inappropriate in a
32
+ professional setting
33
+
34
+ Enforcement Responsibilities
35
+ ----------------------------
36
+
37
+ Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
38
+
39
+ Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
40
+
41
+
42
+ Scope
43
+ -----
44
+
45
+ This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
46
+
47
+
48
+ Enforcement
49
+ -----------
50
+
51
+ Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at trey@treyhunner.com. All complaints will be reviewed and investigated promptly and fairly.
52
+
53
+ All community leaders are obligated to respect the privacy and security of the reporter of any incident.
54
+
55
+
56
+ Enforcement Guidelines
57
+ ----------------------
58
+
59
+ Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
60
+
61
+
62
+ 1. Correction
63
+ ~~~~~~~~~~~~~
64
+
65
+ **Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
66
+
67
+ **Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
68
+
69
+
70
+ 2. Warning
71
+ ~~~~~~~~~~
72
+
73
+ **Community Impact**: A violation through a single incident or series of actions.
74
+
75
+ **Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
76
+
77
+
78
+ 3. Temporary Ban
79
+ ~~~~~~~~~~~~~~~~
80
+
81
+ **Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
82
+
83
+ **Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
84
+
85
+
86
+ 4. Permanent Ban
87
+ ~~~~~~~~~~~~~~~~
88
+
89
+ **Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
90
+
91
+ **Consequence**: A permanent ban from any sort of public interaction within the community.
92
+
93
+
94
+ Attribution
95
+ -----------
96
+
97
+ This Code of Conduct is adapted from the `Contributor Covenant <homepage_>`__, version 2.0,
98
+ available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
99
+
100
+ Community Impact Guidelines were inspired by `Mozilla’s code of conduct enforcement ladder <https://github.com/mozilla/diversity>`__.
101
+
102
+ .. _homepage: https://www.contributor-covenant.org
103
+
104
+ For answers to common questions about this code of conduct, see the FAQ at
105
+ https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.
@@ -0,0 +1,121 @@
1
+ Contributor Guide
2
+ =================
3
+
4
+ Thank you for your interest in improving this project.
5
+ This project is open-source under the `MIT license`_ and
6
+ welcomes contributions in the form of bug reports, feature requests, and pull requests.
7
+
8
+ Here is a list of important resources for contributors:
9
+
10
+ - `Source Code`_
11
+ - `Issue Tracker`_
12
+ - `Code of Conduct`_
13
+
14
+ .. _MIT license: https://opensource.org/licenses/MIT
15
+ .. _Source Code: https://github.com/treyhunner/countdown-cli
16
+ .. _Issue Tracker: https://github.com/treyhunner/countdown-cli/issues
17
+
18
+ How to report a bug
19
+ -------------------
20
+
21
+ Report bugs on the `Issue Tracker`_.
22
+
23
+ When filing an issue, make sure to answer these questions:
24
+
25
+ - Which operating system and Python version are you using?
26
+ - Which version of this project are you using?
27
+ - What did you do?
28
+ - What did you expect to see?
29
+ - What did you see instead?
30
+
31
+ The best way to get your bug fixed is to provide a test case,
32
+ and/or steps to reproduce the issue.
33
+
34
+
35
+ How to request a feature
36
+ ------------------------
37
+
38
+ Request features on the `Issue Tracker`_.
39
+
40
+
41
+ How to set up your development environment
42
+ ------------------------------------------
43
+
44
+ You need Python 3.7+ and the following tools:
45
+
46
+ - Poetry_
47
+ - Nox_
48
+ - nox-poetry_
49
+
50
+ Install the package with development requirements:
51
+
52
+ .. code:: console
53
+
54
+ $ poetry install
55
+
56
+ You can now run an interactive Python session,
57
+ or the command-line interface:
58
+
59
+ .. code:: console
60
+
61
+ $ poetry run python
62
+ $ poetry run countdown
63
+
64
+ .. _Poetry: https://python-poetry.org/
65
+ .. _Nox: https://nox.thea.codes/
66
+ .. _nox-poetry: https://nox-poetry.readthedocs.io/
67
+
68
+
69
+ How to test the project
70
+ -----------------------
71
+
72
+ Run the full test suite:
73
+
74
+ .. code:: console
75
+
76
+ $ nox
77
+
78
+ List the available Nox sessions:
79
+
80
+ .. code:: console
81
+
82
+ $ nox --list-sessions
83
+
84
+ You can also run a specific Nox session.
85
+ For example, invoke the unit test suite like this:
86
+
87
+ .. code:: console
88
+
89
+ $ nox --session=tests
90
+
91
+ Unit tests are located in the ``tests`` directory,
92
+ and are written using the pytest_ testing framework.
93
+
94
+ .. _pytest: https://pytest.readthedocs.io/
95
+
96
+
97
+ How to submit changes
98
+ ---------------------
99
+
100
+ Open a `pull request`_ to submit changes to this project.
101
+
102
+ Your pull request needs to meet the following guidelines for acceptance:
103
+
104
+ - The Nox test suite must pass without errors and warnings.
105
+ - Include unit tests. This project maintains 100% code coverage.
106
+ - If your changes add functionality, update the documentation accordingly.
107
+
108
+ Feel free to submit early, though—we can always iterate on this.
109
+
110
+ To run linting and code formatting checks before committing your change, you can install pre-commit as a Git hook by running the following command:
111
+
112
+ .. code:: console
113
+
114
+ $ nox --session=pre-commit -- install
115
+
116
+ It is recommended to open an issue before starting work on anything.
117
+ This will allow a chance to talk it over with the owners and validate your approach.
118
+
119
+ .. _pull request: https://github.com/treyhunner/countdown-cli/pulls
120
+ .. github-only
121
+ .. _Code of Conduct: CODE_OF_CONDUCT.rst
@@ -1,23 +1,22 @@
1
- Metadata-Version: 2.1
1
+ Metadata-Version: 2.4
2
2
  Name: countdown-cli
3
- Version: 1.0.3
3
+ Version: 1.1.0
4
4
  Summary: Terminal program to display countdown timer
5
- Home-page: https://github.com/treyhunner/countdown-cli
6
- License: MIT
5
+ Project-URL: homepage, https://github.com/treyhunner/countdown-cli
6
+ Project-URL: repository, https://github.com/treyhunner/countdown-cli
7
+ Project-URL: Changelog, https://github.com/treyhunner/countdown-cli/releases
7
8
  Author: Trey Hunner
8
- Author-email: trey@treyhunner.com
9
- Requires-Python: >=3.8.1,<4.0.0
9
+ License: MIT
10
+ License-File: LICENSE.rst
10
11
  Classifier: Development Status :: 4 - Beta
11
- Classifier: License :: OSI Approved :: MIT License
12
- Classifier: Programming Language :: Python :: 3
13
- Classifier: Programming Language :: Python :: 3.9
14
12
  Classifier: Programming Language :: Python :: 3.10
15
13
  Classifier: Programming Language :: Python :: 3.11
16
14
  Classifier: Programming Language :: Python :: 3.12
17
- Classifier: Programming Language :: Python :: 3.8
18
- Requires-Dist: click (>=8.0.1,<9.0.0)
19
- Project-URL: Changelog, https://github.com/treyhunner/countdown-cli/releases
20
- Project-URL: Repository, https://github.com/treyhunner/countdown-cli
15
+ Classifier: Programming Language :: Python :: 3.13
16
+ Classifier: Programming Language :: Python :: 3.14
17
+ Classifier: Programming Language :: Python :: 3.15
18
+ Requires-Python: >=3.10
19
+ Requires-Dist: click>=8.0.1
21
20
  Description-Content-Type: text/x-rst
22
21
 
23
22
  countdown-cli
@@ -140,4 +139,3 @@ This project was generated from `@cjolowicz`_'s `Hypermodern Python Cookiecutter
140
139
  .. _pip: https://pip.pypa.io/
141
140
  .. github-only
142
141
  .. _Contributor Guide: CONTRIBUTING.rst
143
-
@@ -0,0 +1,9 @@
1
+ comment: false
2
+ coverage:
3
+ status:
4
+ project:
5
+ default:
6
+ target: "100"
7
+ patch:
8
+ default:
9
+ target: "100"
@@ -0,0 +1,2 @@
1
+ # Created by coverage.py
2
+ *