flake8-ic 0.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.
- flake8_ic-0.1.0/.coveragerc +14 -0
- flake8_ic-0.1.0/.github/CODE_OF_CONDUCT.md +132 -0
- flake8_ic-0.1.0/.github/CONTRIBUTING.md +20 -0
- flake8_ic-0.1.0/.github/ISSUE_TEMPLATE/bug_report.yaml +25 -0
- flake8_ic-0.1.0/.github/ISSUE_TEMPLATE/feature_request.yaml +23 -0
- flake8_ic-0.1.0/.github/workflows/release.yaml +93 -0
- flake8_ic-0.1.0/.github/workflows/testing.yaml +28 -0
- flake8_ic-0.1.0/.gitignore +159 -0
- flake8_ic-0.1.0/.pre-commit-config.yaml +7 -0
- flake8_ic-0.1.0/.python-version +1 -0
- flake8_ic-0.1.0/.vscode/settings.json +13 -0
- flake8_ic-0.1.0/LICENSE +21 -0
- flake8_ic-0.1.0/PKG-INFO +93 -0
- flake8_ic-0.1.0/README.md +47 -0
- flake8_ic-0.1.0/pyproject.toml +49 -0
- flake8_ic-0.1.0/src/flake8_ic/__init__.py +3 -0
- flake8_ic-0.1.0/src/flake8_ic/checker.py +41 -0
- flake8_ic-0.1.0/src/flake8_ic/metadata.py +19 -0
- flake8_ic-0.1.0/tests/__init__.py +0 -0
- flake8_ic-0.1.0/tests/checker_test.py +18 -0
- flake8_ic-0.1.0/uv.lock +407 -0
|
@@ -0,0 +1,132 @@
|
|
|
1
|
+
# Contributor Covenant Code of Conduct
|
|
2
|
+
|
|
3
|
+
## Our Pledge
|
|
4
|
+
|
|
5
|
+
We as members, contributors, and leaders pledge to make participation in our
|
|
6
|
+
community a harassment-free experience for everyone, regardless of age, body
|
|
7
|
+
size, visible or invisible disability, ethnicity, sex characteristics, gender
|
|
8
|
+
identity and expression, level of experience, education, socio-economic status,
|
|
9
|
+
nationality, personal appearance, race, caste, color, religion, or sexual
|
|
10
|
+
identity and orientation.
|
|
11
|
+
|
|
12
|
+
We pledge to act and interact in ways that contribute to an open, welcoming,
|
|
13
|
+
diverse, inclusive, and healthy community.
|
|
14
|
+
|
|
15
|
+
## Our Standards
|
|
16
|
+
|
|
17
|
+
Examples of behavior that contributes to a positive environment for our
|
|
18
|
+
community include:
|
|
19
|
+
|
|
20
|
+
* Demonstrating empathy and kindness toward other people
|
|
21
|
+
* Being respectful of differing opinions, viewpoints, and experiences
|
|
22
|
+
* Giving and gracefully accepting constructive feedback
|
|
23
|
+
* Accepting responsibility and apologizing to those affected by our mistakes,
|
|
24
|
+
and learning from the experience
|
|
25
|
+
* Focusing on what is best not just for us as individuals, but for the overall
|
|
26
|
+
community
|
|
27
|
+
|
|
28
|
+
Examples of unacceptable behavior include:
|
|
29
|
+
|
|
30
|
+
* The use of sexualized language or imagery, and sexual attention or advances of
|
|
31
|
+
any kind
|
|
32
|
+
* Trolling, insulting or derogatory comments, and personal or political attacks
|
|
33
|
+
* Public or private harassment
|
|
34
|
+
* Publishing others' private information, such as a physical or email address,
|
|
35
|
+
without their explicit permission
|
|
36
|
+
* Other conduct which could reasonably be considered inappropriate in a
|
|
37
|
+
professional setting
|
|
38
|
+
|
|
39
|
+
## Enforcement Responsibilities
|
|
40
|
+
|
|
41
|
+
Community leaders are responsible for clarifying and enforcing our standards of
|
|
42
|
+
acceptable behavior and will take appropriate and fair corrective action in
|
|
43
|
+
response to any behavior that they deem inappropriate, threatening, offensive,
|
|
44
|
+
or harmful.
|
|
45
|
+
|
|
46
|
+
Community leaders have the right and responsibility to remove, edit, or reject
|
|
47
|
+
comments, commits, code, wiki edits, issues, and other contributions that are
|
|
48
|
+
not aligned to this Code of Conduct, and will communicate reasons for moderation
|
|
49
|
+
decisions when appropriate.
|
|
50
|
+
|
|
51
|
+
## Scope
|
|
52
|
+
|
|
53
|
+
This Code of Conduct applies within all community spaces, and also applies when
|
|
54
|
+
an individual is officially representing the community in public spaces.
|
|
55
|
+
Examples of representing our community include using an official e-mail address,
|
|
56
|
+
posting via an official social media account, or acting as an appointed
|
|
57
|
+
representative at an online or offline event.
|
|
58
|
+
|
|
59
|
+
## Enforcement
|
|
60
|
+
|
|
61
|
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
|
62
|
+
reported to the community leaders responsible for enforcement at
|
|
63
|
+
<marco@marcoespinosa.com>.
|
|
64
|
+
All complaints will be reviewed and investigated promptly and fairly.
|
|
65
|
+
|
|
66
|
+
All community leaders are obligated to respect the privacy and security of the
|
|
67
|
+
reporter of any incident.
|
|
68
|
+
|
|
69
|
+
## Enforcement Guidelines
|
|
70
|
+
|
|
71
|
+
Community leaders will follow these Community Impact Guidelines in determining
|
|
72
|
+
the consequences for any action they deem in violation of this Code of Conduct:
|
|
73
|
+
|
|
74
|
+
### 1. Correction
|
|
75
|
+
|
|
76
|
+
**Community Impact**: Use of inappropriate language or other behavior deemed
|
|
77
|
+
unprofessional or unwelcome in the community.
|
|
78
|
+
|
|
79
|
+
**Consequence**: A private, written warning from community leaders, providing
|
|
80
|
+
clarity around the nature of the violation and an explanation of why the
|
|
81
|
+
behavior was inappropriate. A public apology may be requested.
|
|
82
|
+
|
|
83
|
+
### 2. Warning
|
|
84
|
+
|
|
85
|
+
**Community Impact**: A violation through a single incident or series of
|
|
86
|
+
actions.
|
|
87
|
+
|
|
88
|
+
**Consequence**: A warning with consequences for continued behavior. No
|
|
89
|
+
interaction with the people involved, including unsolicited interaction with
|
|
90
|
+
those enforcing the Code of Conduct, for a specified period of time. This
|
|
91
|
+
includes avoiding interactions in community spaces as well as external channels
|
|
92
|
+
like social media. Violating these terms may lead to a temporary or permanent
|
|
93
|
+
ban.
|
|
94
|
+
|
|
95
|
+
### 3. Temporary Ban
|
|
96
|
+
|
|
97
|
+
**Community Impact**: A serious violation of community standards, including
|
|
98
|
+
sustained inappropriate behavior.
|
|
99
|
+
|
|
100
|
+
**Consequence**: A temporary ban from any sort of interaction or public
|
|
101
|
+
communication with the community for a specified period of time. No public or
|
|
102
|
+
private interaction with the people involved, including unsolicited interaction
|
|
103
|
+
with those enforcing the Code of Conduct, is allowed during this period.
|
|
104
|
+
Violating these terms may lead to a permanent ban.
|
|
105
|
+
|
|
106
|
+
### 4. Permanent Ban
|
|
107
|
+
|
|
108
|
+
**Community Impact**: Demonstrating a pattern of violation of community
|
|
109
|
+
standards, including sustained inappropriate behavior, harassment of an
|
|
110
|
+
individual, or aggression toward or disparagement of classes of individuals.
|
|
111
|
+
|
|
112
|
+
**Consequence**: A permanent ban from any sort of public interaction within the
|
|
113
|
+
community.
|
|
114
|
+
|
|
115
|
+
## Attribution
|
|
116
|
+
|
|
117
|
+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
|
|
118
|
+
version 2.1, available at
|
|
119
|
+
[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
|
|
120
|
+
|
|
121
|
+
Community Impact Guidelines were inspired by
|
|
122
|
+
[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
|
|
123
|
+
|
|
124
|
+
For answers to common questions about this code of conduct, see the FAQ at
|
|
125
|
+
[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
|
|
126
|
+
[https://www.contributor-covenant.org/translations][translations].
|
|
127
|
+
|
|
128
|
+
[homepage]: https://www.contributor-covenant.org
|
|
129
|
+
[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
|
|
130
|
+
[Mozilla CoC]: https://github.com/mozilla/diversity
|
|
131
|
+
[FAQ]: https://www.contributor-covenant.org/faq
|
|
132
|
+
[translations]: https://www.contributor-covenant.org/translations
|
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
# Contributing
|
|
2
|
+
|
|
3
|
+
When contributing to this repository, please first discuss the change you wish to make via issue,
|
|
4
|
+
email, or any other method with the participants of this repository before making a change.
|
|
5
|
+
|
|
6
|
+
Please note we have a code of conduct [here](https://github.com/maekind/flake8-ic/blob/main/.github/CODE_OF_CONDUCT.md), please follow it in all your interactions with the project.
|
|
7
|
+
|
|
8
|
+
## Issue process
|
|
9
|
+
|
|
10
|
+
1. Create an issue from one of the existing templates (bug or feature).
|
|
11
|
+
2. Create a new branch and link it to the issue.
|
|
12
|
+
- Naming rule: the name of the new branch must be [the type of the issue]/[issue number]_short_PR_description. **Remember that the type of the issue only can be *bugfix* or *feature*.**
|
|
13
|
+
|
|
14
|
+
## Pull Request Process
|
|
15
|
+
|
|
16
|
+
1. Create the pull request and select at least one participant as reviewer.
|
|
17
|
+
2. You may merge the Pull Request once you have the sign-off of the reviewer, or if you
|
|
18
|
+
do not have permission to do that, you may request the participants to merge it for you.
|
|
19
|
+
|
|
20
|
+
This document could evolve in the future.
|
|
@@ -0,0 +1,25 @@
|
|
|
1
|
+
name: 🪲 Bug report
|
|
2
|
+
description: File a bug report here
|
|
3
|
+
title: "[BUG]: "
|
|
4
|
+
labels: ["bug"]
|
|
5
|
+
body:
|
|
6
|
+
- type: markdown
|
|
7
|
+
attributes:
|
|
8
|
+
value: |
|
|
9
|
+
Thanks for taking the time to fill out this bug report 🤗
|
|
10
|
+
Make sure there aren't any open/closed issues for this topic 😃
|
|
11
|
+
|
|
12
|
+
- type: textarea
|
|
13
|
+
id: bug-description
|
|
14
|
+
attributes:
|
|
15
|
+
label: Description of the bug
|
|
16
|
+
description: Give us a brief description of what happened and what should have happened
|
|
17
|
+
validations:
|
|
18
|
+
required: true
|
|
19
|
+
|
|
20
|
+
- type: textarea
|
|
21
|
+
id: additional-information
|
|
22
|
+
attributes:
|
|
23
|
+
label: Additional Information
|
|
24
|
+
description: |
|
|
25
|
+
Provide any additional information such as logs, screenshots, likes, scenarios in which the bug occurs so that it facilitates resolving the issue.
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
name: ✨ Feature Request
|
|
2
|
+
description: Request a new feature or improvement
|
|
3
|
+
labels: ["feature"]
|
|
4
|
+
title: "[FEATURE]: "
|
|
5
|
+
body:
|
|
6
|
+
- type: markdown
|
|
7
|
+
attributes:
|
|
8
|
+
value: |
|
|
9
|
+
Please make sure this feature request hasn't been already submitted by someone else by looking through other open/closed issues
|
|
10
|
+
|
|
11
|
+
- type: textarea
|
|
12
|
+
id: description
|
|
13
|
+
attributes:
|
|
14
|
+
label: Description
|
|
15
|
+
description: Give us a brief description of the feature or enhancement you would like
|
|
16
|
+
validations:
|
|
17
|
+
required: true
|
|
18
|
+
|
|
19
|
+
- type: textarea
|
|
20
|
+
id: additional-information
|
|
21
|
+
attributes:
|
|
22
|
+
label: Additional Information
|
|
23
|
+
description: Give us some additional information on the feature request like proposed solutions, links, screenshots, etc.
|
|
@@ -0,0 +1,93 @@
|
|
|
1
|
+
name: Create Release ✨ and Publish Python 🐍 distribution 📦 to PyPI
|
|
2
|
+
|
|
3
|
+
on:
|
|
4
|
+
push:
|
|
5
|
+
branches:
|
|
6
|
+
- main
|
|
7
|
+
paths-ignore:
|
|
8
|
+
- '**/README.md'
|
|
9
|
+
|
|
10
|
+
jobs:
|
|
11
|
+
bump-version:
|
|
12
|
+
name: Bump Version
|
|
13
|
+
runs-on: ubuntu-latest
|
|
14
|
+
outputs:
|
|
15
|
+
new_version: ${{ steps.bump-version-step.outputs.new_version }}
|
|
16
|
+
# Ignore version bump commits to avoid a loop
|
|
17
|
+
if: ${{ !contains(github.event.head_commit.message, '[skip ci]') }}
|
|
18
|
+
permissions:
|
|
19
|
+
contents: write # Required to modify the input file
|
|
20
|
+
steps:
|
|
21
|
+
- name: Bump version in pyproject.toml
|
|
22
|
+
id: bump-version-step
|
|
23
|
+
uses: maekind/github-actions/.github/actions/bump-version@main
|
|
24
|
+
with:
|
|
25
|
+
file: pyproject.toml
|
|
26
|
+
gh_token: ${{ secrets.GH_TOKEN }}
|
|
27
|
+
|
|
28
|
+
create-tag:
|
|
29
|
+
name: Create Tag
|
|
30
|
+
needs: bump-version
|
|
31
|
+
runs-on: ubuntu-latest
|
|
32
|
+
# Skip if the version was not bumped yet
|
|
33
|
+
if: ${{ always() && needs.bump-version.result == 'success' && github.ref_name == 'main' }}
|
|
34
|
+
permissions:
|
|
35
|
+
contents: write
|
|
36
|
+
steps:
|
|
37
|
+
- name: Create Git Tag
|
|
38
|
+
uses: maekind/github-actions/.github/actions/create-tag@main
|
|
39
|
+
with:
|
|
40
|
+
tag_name: v${{ needs.bump-version.outputs.new_version }}
|
|
41
|
+
title: ${{ github.event.head_commit.message }}
|
|
42
|
+
emoji: "🚀✨"
|
|
43
|
+
|
|
44
|
+
create-release:
|
|
45
|
+
name: Create Release
|
|
46
|
+
needs: [bump-version, create-tag]
|
|
47
|
+
runs-on: ubuntu-latest
|
|
48
|
+
# Skip if the version was not bumped yet
|
|
49
|
+
if: ${{ always() && needs.bump-version.result == 'success' && github.ref_name == 'main' }}
|
|
50
|
+
permissions:
|
|
51
|
+
contents: write # Required for creating a release
|
|
52
|
+
steps:
|
|
53
|
+
- name: Create GitHub Release
|
|
54
|
+
uses: maekind/github-actions/.github/actions/create-release@main
|
|
55
|
+
with:
|
|
56
|
+
tag_name: v${{ needs.bump-version.outputs.new_version }}
|
|
57
|
+
|
|
58
|
+
build-and-publish:
|
|
59
|
+
name: Build and Publish to PyPI
|
|
60
|
+
needs: create-release
|
|
61
|
+
runs-on: ubuntu-latest
|
|
62
|
+
# Skip if the release was not created yet
|
|
63
|
+
if: ${{ always() && needs.create-release.result == 'success' && github.ref_name == 'main' }}
|
|
64
|
+
permissions:
|
|
65
|
+
contents: read # Required to read the code for building the distribution
|
|
66
|
+
id-token: write # Required for publishing to PyPI
|
|
67
|
+
steps:
|
|
68
|
+
- name: Build Python 🐍 Distributions 📦
|
|
69
|
+
uses: maekind/github-actions/.github/actions/build-python-distribution@main
|
|
70
|
+
with:
|
|
71
|
+
python_version: "3.11"
|
|
72
|
+
|
|
73
|
+
- name: Publish distribution 📦 to PyPI
|
|
74
|
+
uses: maekind/github-actions/.github/actions/publish-to-pypi-with-uv@main
|
|
75
|
+
with:
|
|
76
|
+
python_version: "3.11"
|
|
77
|
+
|
|
78
|
+
github-release:
|
|
79
|
+
name: Sign and Upload to GitHub Release
|
|
80
|
+
needs: [bump-version, build-and-publish]
|
|
81
|
+
runs-on: ubuntu-latest
|
|
82
|
+
# Skip if the build and publish job failed
|
|
83
|
+
if: ${{ always() && needs.build-and-publish.result == 'success' && github.ref_name == 'main' }}
|
|
84
|
+
permissions:
|
|
85
|
+
contents: write # Required to upload artifacts to the release
|
|
86
|
+
id-token: write # Required for signing with Sigstore
|
|
87
|
+
steps:
|
|
88
|
+
- name: >-
|
|
89
|
+
Sign the Python 🐍 distribution 📦 with Sigstore
|
|
90
|
+
and upload them to GitHub Release
|
|
91
|
+
uses: maekind/github-actions/.github/actions/github-release@main
|
|
92
|
+
with:
|
|
93
|
+
tag_name: v${{ needs.bump-version.outputs.new_version }}
|
|
@@ -0,0 +1,28 @@
|
|
|
1
|
+
name: flake8-ic testing 🧪 and coverage report generation 📝
|
|
2
|
+
|
|
3
|
+
on:
|
|
4
|
+
- push
|
|
5
|
+
|
|
6
|
+
jobs:
|
|
7
|
+
testing:
|
|
8
|
+
name: Test
|
|
9
|
+
runs-on: ubuntu-latest
|
|
10
|
+
strategy:
|
|
11
|
+
matrix:
|
|
12
|
+
python-version: ["3.11", "3.12", "3.13"]
|
|
13
|
+
steps:
|
|
14
|
+
- name: Run Python Tests
|
|
15
|
+
uses: maekind/github-actions/.github/actions/python-testing-and-coverage@main
|
|
16
|
+
with:
|
|
17
|
+
python_version: ${{ matrix.python-version }}
|
|
18
|
+
coverage_path: "./src"
|
|
19
|
+
|
|
20
|
+
upload-coverage:
|
|
21
|
+
name: Upload Coverage
|
|
22
|
+
needs: testing
|
|
23
|
+
runs-on: ubuntu-latest
|
|
24
|
+
steps:
|
|
25
|
+
- name: Upload Code Coverage
|
|
26
|
+
uses: maekind/github-actions/.github/actions/upload-codecov-coverage@main
|
|
27
|
+
with:
|
|
28
|
+
codecov_token: ${{ secrets.CODECOV_GH_FLAKE8_IC }}
|
|
@@ -0,0 +1,159 @@
|
|
|
1
|
+
# Coverage
|
|
2
|
+
.coverage
|
|
3
|
+
coverage.xml
|
|
4
|
+
|
|
5
|
+
# Byte-compiled / optimized / DLL files
|
|
6
|
+
__pycache__/
|
|
7
|
+
*.py[cod]
|
|
8
|
+
*$py.class
|
|
9
|
+
|
|
10
|
+
# C extensions
|
|
11
|
+
*.so
|
|
12
|
+
|
|
13
|
+
# Distribution / packaging
|
|
14
|
+
.Python
|
|
15
|
+
build/
|
|
16
|
+
develop-eggs/
|
|
17
|
+
dist/
|
|
18
|
+
downloads/
|
|
19
|
+
eggs/
|
|
20
|
+
.eggs/
|
|
21
|
+
lib/
|
|
22
|
+
lib64/
|
|
23
|
+
parts/
|
|
24
|
+
sdist/
|
|
25
|
+
var/
|
|
26
|
+
wheels/
|
|
27
|
+
share/python-wheels/
|
|
28
|
+
*.egg-info/
|
|
29
|
+
.installed.cfg
|
|
30
|
+
*.egg
|
|
31
|
+
MANIFEST
|
|
32
|
+
|
|
33
|
+
# PyInstaller
|
|
34
|
+
# Usually these files are written by a python script from a template
|
|
35
|
+
# before PyInstaller builds the exe, so as to inject date/other infos into it.
|
|
36
|
+
*.manifest
|
|
37
|
+
*.spec
|
|
38
|
+
|
|
39
|
+
# Installer logs
|
|
40
|
+
pip-log.txt
|
|
41
|
+
pip-delete-this-directory.txt
|
|
42
|
+
|
|
43
|
+
# Unit test / coverage reports
|
|
44
|
+
htmlcov/
|
|
45
|
+
.tox/
|
|
46
|
+
.nox/
|
|
47
|
+
.coverage
|
|
48
|
+
.coverage.*
|
|
49
|
+
.cache
|
|
50
|
+
nosetests.xml
|
|
51
|
+
coverage.xml
|
|
52
|
+
*.cover
|
|
53
|
+
*.py,cover
|
|
54
|
+
.hypothesis/
|
|
55
|
+
.pytest_cache/
|
|
56
|
+
cover/
|
|
57
|
+
|
|
58
|
+
# Translations
|
|
59
|
+
*.mo
|
|
60
|
+
*.pot
|
|
61
|
+
|
|
62
|
+
# Django stuff:
|
|
63
|
+
*.log
|
|
64
|
+
local_settings.py
|
|
65
|
+
db.sqlite3
|
|
66
|
+
db.sqlite3-journal
|
|
67
|
+
|
|
68
|
+
# Flask stuff:
|
|
69
|
+
instance/
|
|
70
|
+
.webassets-cache
|
|
71
|
+
|
|
72
|
+
# Scrapy stuff:
|
|
73
|
+
.scrapy
|
|
74
|
+
|
|
75
|
+
# Sphinx documentation
|
|
76
|
+
docs/_build/
|
|
77
|
+
|
|
78
|
+
# PyBuilder
|
|
79
|
+
.pybuilder/
|
|
80
|
+
target/
|
|
81
|
+
|
|
82
|
+
# Jupyter Notebook
|
|
83
|
+
.ipynb_checkpoints
|
|
84
|
+
|
|
85
|
+
# IPython
|
|
86
|
+
profile_default/
|
|
87
|
+
ipython_config.py
|
|
88
|
+
|
|
89
|
+
# pyenv
|
|
90
|
+
# For a library or package, you might want to ignore these files since the code is
|
|
91
|
+
# intended to run in multiple environments; otherwise, check them in:
|
|
92
|
+
# .python-version
|
|
93
|
+
|
|
94
|
+
# pipenv
|
|
95
|
+
# According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
|
|
96
|
+
# However, in case of collaboration, if having platform-specific dependencies or dependencies
|
|
97
|
+
# having no cross-platform support, pipenv may install dependencies that don't work, or not
|
|
98
|
+
# install all needed dependencies.
|
|
99
|
+
#Pipfile.lock
|
|
100
|
+
|
|
101
|
+
# poetry
|
|
102
|
+
# Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
|
|
103
|
+
# This is especially recommended for binary packages to ensure reproducibility, and is more
|
|
104
|
+
# commonly ignored for libraries.
|
|
105
|
+
# https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
|
|
106
|
+
#poetry.lock
|
|
107
|
+
|
|
108
|
+
# pdm
|
|
109
|
+
# Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
|
|
110
|
+
#pdm.lock
|
|
111
|
+
# pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
|
|
112
|
+
# in version control.
|
|
113
|
+
# https://pdm.fming.dev/latest/usage/project/#working-with-version-control
|
|
114
|
+
.pdm.toml
|
|
115
|
+
.pdm-python
|
|
116
|
+
.pdm-build/
|
|
117
|
+
|
|
118
|
+
# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
|
|
119
|
+
__pypackages__/
|
|
120
|
+
|
|
121
|
+
# Celery stuff
|
|
122
|
+
celerybeat-schedule
|
|
123
|
+
celerybeat.pid
|
|
124
|
+
|
|
125
|
+
# SageMath parsed files
|
|
126
|
+
*.sage.py
|
|
127
|
+
|
|
128
|
+
# Environments
|
|
129
|
+
.env
|
|
130
|
+
.venv
|
|
131
|
+
env/
|
|
132
|
+
venv/
|
|
133
|
+
ENV/
|
|
134
|
+
env.bak/
|
|
135
|
+
venv.bak/
|
|
136
|
+
|
|
137
|
+
# Spyder project settings
|
|
138
|
+
.spyderproject
|
|
139
|
+
.spyproject
|
|
140
|
+
|
|
141
|
+
# Rope project settings
|
|
142
|
+
.ropeproject
|
|
143
|
+
|
|
144
|
+
# mkdocs documentation
|
|
145
|
+
/site
|
|
146
|
+
|
|
147
|
+
# mypy
|
|
148
|
+
.mypy_cache/
|
|
149
|
+
.dmypy.json
|
|
150
|
+
dmypy.json
|
|
151
|
+
|
|
152
|
+
# Pyre type checker
|
|
153
|
+
.pyre/
|
|
154
|
+
|
|
155
|
+
# pytype static type analyzer
|
|
156
|
+
.pytype/
|
|
157
|
+
|
|
158
|
+
# Cython debug symbols
|
|
159
|
+
cython_debug/
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
3.11
|
flake8_ic-0.1.0/LICENSE
ADDED
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2025 Marco Espinosa
|
|
4
|
+
|
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
+
in the Software without restriction, including without limitation the rights
|
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
+
furnished to do so, subject to the following conditions:
|
|
11
|
+
|
|
12
|
+
The above copyright notice and this permission notice shall be included in all
|
|
13
|
+
copies or substantial portions of the Software.
|
|
14
|
+
|
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
21
|
+
SOFTWARE.
|
flake8_ic-0.1.0/PKG-INFO
ADDED
|
@@ -0,0 +1,93 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: flake8-ic
|
|
3
|
+
Version: 0.1.0
|
|
4
|
+
Summary: This package provides a plugin for flake8 that checks the usage of ic() function from icecream package.
|
|
5
|
+
Author-email: Marco Espinosa <marco@marcoespinosa.com>
|
|
6
|
+
License: MIT License
|
|
7
|
+
|
|
8
|
+
Copyright (c) 2025 Marco Espinosa
|
|
9
|
+
|
|
10
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
11
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
12
|
+
in the Software without restriction, including without limitation the rights
|
|
13
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
14
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
15
|
+
furnished to do so, subject to the following conditions:
|
|
16
|
+
|
|
17
|
+
The above copyright notice and this permission notice shall be included in all
|
|
18
|
+
copies or substantial portions of the Software.
|
|
19
|
+
|
|
20
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
21
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
22
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
23
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
24
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
25
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
26
|
+
SOFTWARE.
|
|
27
|
+
License-File: LICENSE
|
|
28
|
+
Keywords: code quality,debugging,flake8,ic,icecream,linting,plugin
|
|
29
|
+
Classifier: Development Status :: 3 - Alpha
|
|
30
|
+
Classifier: Environment :: Console
|
|
31
|
+
Classifier: Intended Audience :: Developers
|
|
32
|
+
Classifier: License :: OSI Approved :: MIT License
|
|
33
|
+
Classifier: Operating System :: OS Independent
|
|
34
|
+
Classifier: Programming Language :: Python
|
|
35
|
+
Classifier: Programming Language :: Python :: 3
|
|
36
|
+
Classifier: Programming Language :: Python :: 3.11
|
|
37
|
+
Classifier: Programming Language :: Python :: 3.12
|
|
38
|
+
Classifier: Programming Language :: Python :: 3.13
|
|
39
|
+
Classifier: Topic :: Software Development :: Libraries :: Python Modules
|
|
40
|
+
Classifier: Topic :: Software Development :: Quality Assurance
|
|
41
|
+
Classifier: Topic :: Software Development :: Testing
|
|
42
|
+
Requires-Python: >=3.11
|
|
43
|
+
Requires-Dist: flake8>=7.1.1
|
|
44
|
+
Requires-Dist: toml>=0.10.2
|
|
45
|
+
Description-Content-Type: text/markdown
|
|
46
|
+
|
|
47
|
+
<!-- Shields -->
|
|
48
|
+
<p align="center">
|
|
49
|
+
<a href="https://github.com/maekind/flake8-ic"><img src="https://img.shields.io/github/actions/workflow/status/maekind/flake8-ic/.github%2Fworkflows%2Ftesting.yaml?label=tests&color=green" hspace="5"></a>
|
|
50
|
+
<a href="https://codecov.io/gh/maekind/flake8-ic"><img src="https://codecov.io/gh/maekind/flake8-ic/graph/badge.svg?token=JcGna50uJL" hspace="5"/></a>
|
|
51
|
+
<a href="https://github.com/maekind/flake8-ic/releases"><img src="https://img.shields.io/github/actions/workflow/status/maekind/flake8-ic/.github%2Fworkflows%2Frelease.yaml?label=build package&color=green" hspace="5"></a>
|
|
52
|
+
<a href="https://pypi.org/project/flake8-ic"><img src="https://img.shields.io/github/v/release/maekind/flake8-ic?color=blue&label=pypi latest" hspace="5"></a>
|
|
53
|
+
<br>
|
|
54
|
+
<a href="https://github.com/maekind/flake8-ic/blob/main/LICENSE"><img src="https://img.shields.io/badge/License-MIT-orange.svg" hspace="5"></a>
|
|
55
|
+
<a href="https://github.com/maekind/flake8-ic"><img src="https://img.shields.io/github/repo-size/maekind/flake8-ic?color=red" hspace="5"></a>
|
|
56
|
+
<a href="https://github.com/maekind/flake8-ic"><img src="https://img.shields.io/github/last-commit/maekind/flake8-ic?color=black" hspace="5"></a>
|
|
57
|
+
<a href="https://www.python.org/downloads/"><img src="https://img.shields.io/github/languages/top/maekind/flake8-ic?color=darkgreen" hspace="5"></a>
|
|
58
|
+
<a href="https://www.python.org/downloads/"><img src="https://img.shields.io/badge/python%20version-%3E3.11-lightblue" hspace="5"></a>
|
|
59
|
+
</p>
|
|
60
|
+
|
|
61
|
+
# flake8-ic
|
|
62
|
+
|
|
63
|
+
## Description
|
|
64
|
+
|
|
65
|
+
This package provides a plugin for `flake8` to check the usage of the `ic()` function from the `icecream` package in your codebase.
|
|
66
|
+
|
|
67
|
+
## Installation
|
|
68
|
+
|
|
69
|
+
You can install this package using pip:
|
|
70
|
+
|
|
71
|
+
```bash
|
|
72
|
+
pip install flake8-ic
|
|
73
|
+
```
|
|
74
|
+
|
|
75
|
+
## Check installation
|
|
76
|
+
|
|
77
|
+
You can check the installation by running the following command:
|
|
78
|
+
|
|
79
|
+
```bash
|
|
80
|
+
flake8 --version
|
|
81
|
+
```
|
|
82
|
+
|
|
83
|
+
You should see the installed version of `flake8` and the installed plugins, including `flake8-ic`.
|
|
84
|
+
|
|
85
|
+
## Contributors
|
|
86
|
+
|
|
87
|
+
<a href="https://github.com/maekind/flake8-ic/graphs/contributors">
|
|
88
|
+
<img src="https://contrib.rocks/image?repo=maekind/flake8-ic" />
|
|
89
|
+
</a>
|
|
90
|
+
<br/>
|
|
91
|
+
<br/>
|
|
92
|
+
|
|
93
|
+
(c) <a href="mailto:marco@marcoespinosa.com">Marco Espinosa</a>, 2024
|