Saravanan666/pypi-org huggingface dataset:
Package: pylint-boxwisemaatwerk
#pylint-boxwisemaatwerk maintainer READMEBuild and dist are the files that are literally getting uploaded to PyPi. Its preferable that you make an account on PyPi to make updates. Most custom checkers are in in the checkers folders. Made a small monkeypatch to alter pylint default functionality. The files the checkers use are mostly made in the stub generator folder.how to create:note: make version 0.0.1 higher in the setup.py and delete the build and dist folder before executing the following code.“python setup.py sdist bdist_wheel”“python -m twine upload dist/* –verbose”login:*password:*To install:execute “pip install pylint_boxwisemaatwerk” in command promptsources:https://packaging.python.org/tutorials/packaging-projects/Changelog
=========Version 0.0.1 (17 June 2019)Version 0.0.5 (24 July 2019)changed addreferenchecker to use a json file as listVersion 0.0.6
Monkeypatched typechecker to use linterstorage. Now gives hints based on changelist file.
Turned assemblylist-paths to linterstorage_path; is now also a string instead of a csv
Package: pylint-codeclimate
pylint code climate(deprecated, unmaintained)A quick and dirty helper script to report pylint results in a json file that will be accepted by GitLab CI.Installation from PyPIYou can install the latest version from PyPI package repository.python3-mpipinstall-Upylint-codeclimateGitLab CI UsageSample gitlab-ci.yml snippet for coverage:coverage:script:-python3 -m pylint  --recursive y --output-format=codeclimate:pylint.json myprojectartifacts:when:alwaysreports:codequality:pylint.jsonLicenseThis project is licensed under the MIT License - see theLICENSEfile for details.LocationsGitLab:https://gitlab.com/jlecomte/projects/python/pylint-codeclimatePyPi:https://pypi.org/project/pylint-codeclimate
Package: pylintconfig
pylintconfigpylint is a great linter, which thoroughly analyses your code. Running it for the first time on an existing codebase can be intimidating though, because it outputs hundreds of errors! Through all the errors, you don't see the important ones and skip pylint alltogether.pylintconfig is a small cli which makes it easier to implement pylint in an existing codebase. It helps creating a configuration file which checks the errors you find important and skips the rest.Installpip install pylintconfigBasic usagepylintconfig disable MODULES_OR_PACKAGESOr when you want to immediately save the config:pylintconfig disable MODULES_OR_PACKAGES > .pylintrcFuture plansAdd testsLoad current pylintrc fileAdd ignore command, which make it easy to ignore specific files
Package: pylint-elasticsearch-dsl
pylint-elasticsearch-dslpylintplugin for theelasticsearch-dslpackageThis plugin is needed to helppylintunderstand the types of some objects of theelasticsearch-dslpackage.Installationpip install pylint-elasticsearch-dslScopeCurrently, this plugin only patches the false positiveinvalid-unary-operand-typeerror
that is triggered when writing for example:fromelasticsearch_dslimportQ~Q("exists",field="foo")Seethis issuefor more details.ContributingTo work on this project, install the development requirements by running:make installThe tests can be run with:make test
Package: pylint-enums
Pylint-EnumsInstallation:$ pip install pylint_enums     # a conventional option
$ pipenv install pylint_enums  # a more modern optionUsage:Follow instructions to addpylint_enumsas part of your loaded plugins.Option 1 (.pylintrc)Addload-plugins=pylint_enumsto your.pylintrc.Use pylint normally, i.e.,$ pylint [filepath]Option 2 (command line option)$ pylint [filepath] --load-plugins=pylint_enumsWhat this is:This is a tiny pylint plugin that adds a checker for Enum subclasses.  It warns you when you haven't provided a typed annotation for thevalueattribute and when a__str__method has not been defined for the Enum when the type annotation isn't part of a finite list of simple types.__str__declaration is not enforced for the following types:strintdecimalfloatWhy this is helpful:Typically, the value of an enum doesn't matter.from enum import Enum

class Foo(Enum):
    FIRST = 'these'
    SECOND = 'usually'
    THIRD = 'don\'t'
    FOURTH = 'matter'However, in certain applications and/or use-cases, you actually do care about the value of each enum member.  Specifically, you may use them as averbose_nameor apretty_namefor displaying to the user, or you may want to assign it a stateful value and use its contents later.from enum import Enum
from typing import NamedTuple

class FooMember(NamedTuple):
    label: str
    rank: int

class Foo(Enum):
    FIRST = FooMember(label='first', rank=1)
    SECOND = FooMember(label='second', rank=2)
    THIRD = FooMember(label='third', rank=3)
    FOURTH = FooMember(label='fourth', rank=4)

    def __str__(self) -> str:
        return self.value.labelAs of this writing,mypy==0.600is unable to infer the types of the member values. They resolve to'Any':reveal_type(Foo)             # 'def (value: Any) -> foo.Foo'
reveal_type(Foo.FIRST)       # 'foo.Foo'
reveal_type(Foo.FIRST.value) # 'Any'This can be problematic formypyusers that rely on type hints to maintain their code base.  When you write a function that returnsFoo.FIRST.value, our tooling is unable to help us figure out whether this value is astr, aNamedTuple, or some other value.  Ideally, we would add additional type hints to the Enum:class Foo(Enum):
    value: FooMember
    FIRST = FooMember(label='first', rank=1)
    ...But alas, this requires developer vigilance to remember to do.  If you're maintaining many enums across multiple files, it could be annoying to make sure that they and all future defined Enums are adequately typed.This pylint plugin will raise errors whenvalueis not typed and when the value is typed to something complex and the Enum is missing a__str__method.AuthorChristopher Sabater Cordero
Package: pylint-exception-var-name-plugin
Plugin for pylint which allows defining and checking variable name for exception (likeeorexcor other)Install:pipinstallpylint-exception-var-name-pluginUsage:pylint--load-pluginspylint_exception_var_name_pluginFILES_TO_CHECKAdd topylintrcfile to setALLOWED_VAR_NAME:[VARIABLES]exception-var-name=ALLOWED_VAR_NAME
Package: pylint-fail-under
Pylint wrapper that verifies code reaches a minimum quality score.Quick StartExecute thepylint-fail-undercommand with the same arguments as apylintcall. In addition,
specify the minimum Pylint quality score with the--fail_underargument.If the Pylint score is greater than the fail under value, the script exits successfully with an
exit code of zero. For example:$ pylint-fail-under --fail_under 9.0 my_package
************* Module my_package
my_package\__init__.py:1:0: C0111: Missing module docstring (missing-docstring)
### Pylint output removed for documentation conciseness! ###
my_package\tests\test_my_pkg.py:328:0: C0303: Trailing whitespace (trailing-whitespace)

------------------------------------------------------------------
Your code has been rated at 9.49/10 (previous run: 9.49/10, +0.00)Otherwise, if the Pylint score is under the minimum, the script exits with a non-zero exit code. For
example:$ pylint-fail-under --fail_under 9.75 my_package
************* Module my_package
my_package\__init__.py:1:0: C0111: Missing module docstring (missing-docstring)
### Pylint output removed for documentation conciseness! ###
my_package\tests\test_my_pkg.py:328:0: C0303: Trailing whitespace (trailing-whitespace)

------------------------------------------------------------------
Your code has been rated at 9.49/10 (previous run: 9.49/10, +0.00)

ERROR: score 9.4921875 is less than fail-under value 9.75
Package: pylint-fields
A pylint plugin forpython-fields. It makes pylint
understand what fields are going to be present in the resulting class and what fields are required
by the default __init__ method.Free software: BSD licenseInstallationpip install pylint-fieldsUsageAdd this to your pylint conf:[MASTER]
load-plugins=pylint_fieldsDocumentationhttps://pylint-fields.readthedocs.org/DevelopmentTo run the all tests run:toxChangelog0.2.0 (2014-10-25)First release on PyPI.
Package: pylintfileheader
pylint-file-headerPylint plugin to enforce consistent file/module header.InstallationYou can install the package withpipfrompypi:pip install pylintfileheaderConfigurationGenerate a.pylintrcfile by executingpylint --generate-rcfile.
Then addpylintfileheaderto the plugins to load and set thefile-headeroption to theregular expressionthat the file header should match.When thefile-headersetting is omitted, pylint will pass.Optionsfile-headeris a regexp representing the file header that should be on top of a file.file-header-pathis the path to the file that contains the header. This is useful in case of long, multi-line headers, such as copyrights.file-header-ignore-empty-filesturns on the mode of ignoring the empty files, like__init__.py. The default value isFalse.If both optionsfile-headerandfile-header-pathare set, thenfile-headerwill be used and thefile-header-pathis ignored.ExampleSetup.pylintrc:[MASTER]
load-plugins=pylintfileheader

file-header=# -----------\n#[ \w]*\n# -----------valid_example.py:# -----------# lorem ipsum# -----------print('I am a valid example')invalid_example.py:# lorem ipsumprint('I am an invalid example')Evaluationpylint valid_example.pyevaluates to:Using config file /path/to/your/.pylintrc

------------------------------------
Your code has been rated at 10.00/10pylint invalid_example.pyevaluates to:Using config file /path/to/your/.pylintrc
************* Module invalid_example
C:  1, 0: File header should match regex "# -----------\n#[ \w]*\n# -----------" (invalid-file-header)

-----------------------------------
Your code has been rated at 8.57/10ContributionIf you found a bug or are missing a feature do not hesitate tofile an issue.Pull Requests are welcome!SupportWhen you like this package make sure tostar the repository. I am always looking for new ideas and feedback.In addition, it is possible todonate via paypal.
Package: pylint-fixme-info
Pylint fixme infoA pylint plugin that emits info rather than warning for FIXME, TODO, and the like.UsageTo use this plugin, either run pylint with--load-plugins=pylint_fixme_info --disable=fixme, or add the following to your pylintrc[MASTER]load-plugins=pylint_fixme_info[MESSAGES CONTROL]disable=fixmeConfigurationThe following options are supported:notes-info: List of note tags to take in consideration, separated by a comma. Default: FIXME,XXX,TODO
notes-info-rgx: Regular expression of note tags to take in consideration.
Package: pylint-flask-sqlalchemy
pylint_flask_sqlalchemyAboutpylint_flask_sqlalchemy is aPylintplugin for improving code
analysis withFlask-SQLAlchemy.UsageUsing a simple flask app"""app.py"""# pylint: disable=missing-docstring,too-few-public-methods,invalid-namefromflaskimportFlaskfromflask_sqlalchemyimportSQLAlchemyapp=Flask(__name__)app.config["SQLALCHEMY_DATABASE_URI"]="sqlite:////tmp/test.db"db=SQLAlchemy(app)classGroup(db.Model):id=db.Column(db.Integer,primary_key=True)name=db.Column(db.String(80),unique=True,nullable=False)def__repr__(self):return"<User%r>"%self.usernameclassUser(db.Model):id=db.Column(db.Integer,primary_key=True)username=db.Column(db.String(80),unique=True,nullable=False)group=db.relationship(Group)def__repr__(self):return"<User%r>"%self.usernameuser=User(username="test")db.session.add(user)db.session.commit()Without the plugin:pylint app.pyapp.py:11:9: E1101: Instance of 'SQLAlchemy' has no 'Column' member (no-member)
app.py:11:19: E1101: Instance of 'SQLAlchemy' has no 'Integer' member (no-member)
app.py:12:11: E1101: Instance of 'SQLAlchemy' has no 'Column' member (no-member)
app.py:12:21: E1101: Instance of 'SQLAlchemy' has no 'String' member (no-member)
app.py:19:9: E1101: Instance of 'SQLAlchemy' has no 'Column' member (no-member)
app.py:19:19: E1101: Instance of 'SQLAlchemy' has no 'Integer' member (no-member)
app.py:20:15: E1101: Instance of 'SQLAlchemy' has no 'Column' member (no-member)
app.py:20:25: E1101: Instance of 'SQLAlchemy' has no 'String' member (no-member)
app.py:21:12: E1101: Instance of 'SQLAlchemy' has no 'relationship' member (no-member)
app.py:28:0: E1101: Instance of 'scoped_session' has no 'add' member (no-member)
app.py:29:0: E1101: Instance of 'scoped_session' has no 'commit' member (no-member)

----------------------------------------------------------------------
Your code has been rated at -18.95/10 (previous run: 10.00/10, -28.95)😓With pylint_flask_sqlalchemy:pylint --load-plugins pylint_flask_sqlalchemy app.py----------------------------------------------------------------------
Yourcodehasbeenratedat10.00/10(previousrun:-13.08/10,+23.08)🥳Installationpip install pylint_flask_sqlalchemyand tell pylint to--load-plugins pylint_flask_sqlalchemywhen you launch it.ChangelogCurrent versionNewHandle scoped_session has no * member.0.1.0 (2019-07-18)NewHandle scoped_session has no * member.Handle scoped_session has no * member.ChangesUdpate readme.0.0.3 (2019-07-13)ChangesUpdate readme.0.0.2 (2019-07-13)NewFirst draft of the plugin.FixesPackaging.
Package: pylint-forbidden-imports
How does it work?This plugin inspects import statements for configured packages. Both checkers are using powerful AST analysis techniques, standard for pylint.StatusThis emerged as a standalone experimentation during development ofthe Clean Architecture example projectWhy?To enforce certain conventions project-wide in an automatic way, without having to watch for it during code review. For example: “we do not import anything fromfooinbar.” or “we must not import anything from guts of the packagebaz, only what’s kept in it’s top-level __init__.py__all__list”.How to use it?After installing a package just runpylint, appendingpylint_forbidden_importsto your–load-pluginsoption.An example:pylint my_cool_project --load-plugins=pylint_forbidden_importsor append it to yourpylintrcfile:[MASTER]
load-plugins=pylint_forbidden_importsThen, you have to configure the plugin. Example for.pylintrc:[ARBITRARY-SECTION-NAME]
encapsulated-modules=auctions,payments
encapsulated-modules-friendships=auctions_infrastructure->auctions
allowed-modules-dependencies=auctions_infrastructure->auctions,
                             main->*,
                             *->foundation,All settings are comma-separated.encapsulated-modules- checks whether we import from it only things kept in top-level __init__.py.encapsulated-modules-friendships- allows for creating exceptions to that rule for “friend” packages.allowed-modules-dependencies- defines which packages are allowed to be imported from certain packages. Asterisk (*) is a wildcard -main->*means main package can import anything while*->foundationmeans that any package can import from foundation.
If a certain package does not appear at least once, no rules are enforced.DevelopmentInstall dev dependencies: ::pip install -e .[dev]
Package: pylint-gitlab
pylint-gitlabThis project provides pylint formatters for a nice integration with GitLab CI.FormatterDescriptionGitlabCodeClimateReporterMaps the linting result inCode Climate formatGitlabCodeClimateReporterNoHashMaps the linting result inCode Climate formatbut without hashing the fingerprint. Needed to work withnbQA.GitlabPagesHtmlReporterCreates a table in an HTML page with linting results and links to source code.UsageInstall packagepylint-gitlab:pipinstallpylint-gitlabThepylintpackage is a dependency ofpylint-gitlabso it will be installed automatically.Now the formatters can be used by runningpylintcommand and setting custom output formats with parameter--output-format.pylint--exit-zero--output-format=pylint_gitlab.GitlabCodeClimateReporter.>codeclimate.json
pylint--exit-zero--output-format=pylint_gitlab.GitlabPagesHtmlReporter.>pylint.htmlAlternatively, you can load thepylint_gitlabplugin and then use the shortened--output-formatnames:pylint--exit-zero--load-plugins=pylint_gitlab--output-format=gitlab-codeclimate.>codeclimate.json
pylint--exit-zero--load-plugins=pylint_gitlab--output-format=gitlab-pages-html.>pylint.htmlGitLab CI integrationHere is a minimalistic version for a.gitlab-ci.ymlfile:pylint:stage:testimage:python:3.7-slimbefore_script:-mkdir -p public/badges public/lint-echo undefined > public/badges/$CI_JOB_NAME.score-pip install pylint-gitlabscript:-pylint --exit-zero --output-format=text $(find -type f -name "*.py" ! -path "**/.venv/**") | tee /tmp/pylint.txt-sed -n 's/^Your code has been rated at \([-0-9.]*\)\/.*/\1/p' /tmp/pylint.txt > public/badges/$CI_JOB_NAME.score-pylint --exit-zero --output-format=pylint_gitlab.GitlabCodeClimateReporter $(find -type f -name "*.py" ! -path "**/.venv/**") > codeclimate.json-pylint --exit-zero --output-format=pylint_gitlab.GitlabPagesHtmlReporter $(find -type f -name "*.py" ! -path "**/.venv/**") > public/lint/index.htmlafter_script:-anybadge --overwrite --label $CI_JOB_NAME --value=$(cat public/badges/$CI_JOB_NAME.score) --file=public/badges/$CI_JOB_NAME.svg 4=red 6=orange 8=yellow 10=green-|echo "Your score is: $(cat public/badges/$CI_JOB_NAME.score)"artifacts:paths:-publicreports:codequality:codeclimate.jsonwhen:alwayspages:stage:deployimage:alpine:latestscript:-echoartifacts:paths:-publiconly:refs:-masterYou can then use the published badge for linting results.[![pylint](https://<MAIN_GROUP>.gitlab.io/<SUB_GROUP>/<PROJECT>/badges/pylint.svg)](https://<MAIN_GROUP>.gitlab.io/<SUB_GROUP>/<PROJECT>/lint/)
Package: pylint-google-style-guide-imports-enforcing
How it works?It marks importing anything but modules/packages as invalid with a messageonly-importing-modules-is-allowed. This adheres to Google’s Python style guide.An example:from functools import partial  # invalid
import functools  # valid
from some_module.some_subomdule import SomeClass  # invalid
from some_module import some_subomdule  # validWhy?To not force people to manual check if something we imported is a module or not.How to use it?After installing a package just runpylint, appendingpylint_google_style_guide_imports_enforcingto your–load-pluginsoption.An example:pylint my_cool_project --load-plugins=pylint_google_style_guide_imports_enforcingor append it to yourpylintrcfile:[MASTER]
load-plugins=pylint_google_style_guide_imports_enforcing
Package: pylint-grandfather
# pylint-grandfather[![Build Status](https://travis-ci.org/jacob-meacham/pylint-grandfather.svg?branch=develop)](https://travis-ci.org/jacob-meacham/pylint-grandfather)# IntroductionSometimes, you have an old project that you'd like to introduce pylint to. Usually, this is a huge feat, because the old project might have hundreds or thousands (or more!) lint issues. Fixing all of these issues might actually introduce more bugs than it solves, depending on how long the project has been running. pylint-grandfather allows you to grandfather in old code, while still enforcing that all new or changed code is pylint compliant.# Quick Start```pip install pylint-grandfatherpylint my_base_dir | pylint-grandfather --base_dir my_base_dir```Note that this will actually touch all files, so be sure to do this with a clean working directory.# Usage```usage: pylint-grandfather.py [-h] [--base-dir BASE_DIR] [--dry-run DRY_RUN]infilepositional arguments:infile               Output from a pylint runoptional arguments:-h, --help           show this help message and exit--base-dir BASE_DIR  Base directory for pylint run--dry-run DRY_RUN    Output what files will be changed, but do not changethem```# Release Notes* 1.0.0 - Initial version
Package: pylint-json2checkstyle
pylint-json2checkstyleA Pylint plugin and command line tool to produce Pylint reports in checkstyle format.This project is partially inspired from thepylint-json2htmlproject.Usage:As a command line toolusage: pylint-json2checkstyle [-h] [-o checkstyle_output_file] [json_input_file]

Convert pylint json report to checkstyle

positional arguments:
  json_input_file       Pylint JSON report input file (or stdin)

optional arguments:
  -h, --help            show this help message and exit
  -o checkstyle_output_file, --output checkstyle_output_file
                        Checkstyle report output file (or stdout)As a Pylint plugin:pylint --load-plugins=pylint_json2checkstyle.checkstyle_reporter --output-format=checkstyle [pylint arguments ... ]Why?Checkstyle is a widely supported report format for code issues, with integrations available in CI environments.For example, theCheckstyle GitHub Actionreads a checkstyle report and adds
annotations to PRs.
Package: pylint-junit
pylint_junitPylint plugin that generates JUnit based report that can be consumed
by CI environments like Jenkins, Azure Devops and such.Why ?At the time of writing, few tools existed that where able to generate
JUnit format from pylint output. Both of these projects where not
handling “empty” results scenario well, eg both cases generated an empty
file and that caused issues in ci as the resulting document was not
proper xml file. Another issue was that issues found by pylint where
marked under single testcase failure and this caused atleast Azure to
report a single item per file even thought there could have been multiple.Thus, pylint_junit was written.InstallationInstall the package withpip install pylint_junitor add it to your requirements.UsageAfter the plugin has been installed there are few options to take it into use.Add following lines into your .pylintrc:[MASTER]
load-plugins=pylint_junit
[REPORTS]
output-format=junitThis does set the default output to junit, so if still want to run pylint and get
normal output, you might want to consider omitting the “output-format=junit”
portion and only when junit format is needed, provide it via command line like this:pylint --output-format=junit src/Or, without making any changes to your pylint configuration, you can just pass the class
as report formatter like this:pylint --output-format=pylint_junit.JUnitReporter src/Dependenciesjunit_xmlBugs / FeedbackUse Github Issues Tracker @https://github.com/rasjani/pylint_junit/issues
Package: pylint-keyword-only-args-plugin
Plugin for pylint which checks that call statements has only keyword argsInstall:pipinstallpylint-keyword-only-args-pluginUsage:pylint--load-pluginspylint_keyword_only_args_pluginFILES_TO_CHECKAdd topylintrcfile to skip desired callable names:[VARIABLES]skip-names-list=callable_name_1,callable_name_1# Comma separated list of callable names to skip
Package: pylint-modularity
pylint-modularityPylint plugin to help enforce separation of concerns.InstallationInstall the module with e.g.poetry add --group dev pylint_modularity.UsageIn your Pylint configuration (e.g. inpyproject.toml) add the following:[tool.pylint.MAIN]
load-plugins = "pylint_modularity"Import restrictionsOnce the plugin is enabled, in your Pylint configuration (e.g. inpyproject.toml) add the following:[tool.pylint.MAIN]
import-restriction = [
    "module_visited->module_import_restriction",
    "module2_visited -> restriction\\..*"
]

The restrictions configured as part of `import-restriction` setting, and as represented above take the following shape - `module_visited -> import_restriction`
- `module_visited`: The module which is presently being looked at. This could be a RegEx in order to capture several modules.
- `->`: The separator denoting the module being investigated (on the left), and the restricted imports (on the right). You can optionally add spaces around it for clarity.
- `import_restriction`: The module which is restricted from being imported within the module being investigated. This could be a RegEx in order to capture several modules.