azure-pylint-guidelines-checker

v0.0.8

A pylint plugin which enforces azure sdk guidelines. For more information about how to use this package see README

Latest version published 2 years ago

License: MIT

PyPI

GitHub

Package Health Score

69 / 100

security
No known security issues
popularity
Small
maintenance
Inactive
community
Active

Popularity

Small

GitHub Stars: 4.63K
Forks: 2.83K
Contributors: 410

Direct Usage Popularity

Based on project statistics from the GitHub repository for the PyPI package azure-pylint-guidelines-checker, we found that it has been starred 4,626 times.

Security

No known security issues

Security and license risk for latest version

Release Date: Mar 31, 2023
Direct Vulnerabilities: 0
C
0
H
0
M
0
L
Indirect Vulnerabilities: 0
C
0
H
0
M
0
L
License Risk: 0
H
0
M
0
L

All security vulnerabilities belong to production dependencies of direct and indirect packages.

License

MIT

Security Policy

Yes

You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

Open Issues: 791
Open PR: 150
Last Release: 2 years ago
Last Commit: 10 days ago

Further analysis of the maintenance status of azure-pylint-guidelines-checker based on released PyPI versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for azure-pylint-guidelines-checker is that it hasn't seen any new versions released to PyPI in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Community

Active

Readme: Yes
Contributing.md: Yes
Code of Conduct: Yes
Contributors: 410
Funding: No

A good and healthy external contribution signal for azure-pylint-guidelines-checker project, which invites more than one hundred open source maintainers to collaborate on the repository.

Embed Package Health Score Badge

Keep your project healthy

Check your requirements.txt

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Python Versions Compatibility: >=3.7

Age: 2 years
Latest Release: 2 years ago
Dependencies: N/A
Versions: 1
Maintainers: 2
Wheels: OS Independent

Readme

Linting the Guidelines

The code presented in this repository is a lift-and-shift of code originally written by @kristapratico

Running guidelines checks in Azure/azure-sdk-for-python repository

In order to lint for the guidelines, you must make sure you are enabling the pylint-guidelines-checker in your pylint invocation. Using the rcfile at the root of the repo will ensure that the plugin is properly activated

It is recommended you run pylint at the library package level to be consistent with how the CI runs pylint.

Check that you are running pylint version >=2.14.5 and astroid version >=2.12.0.

Install the pylint checker from the azure-sdk development feed.

pip install --index-url="https://pkgs.dev.azure.com/azure-sdk/public/_packaging/azure-sdk-for-python/pypi/simple/" pylint-guidelines-checker

Run pylint at the root of the repo and it will automatically find the pylintrc:
```
C:\azure-sdk-for-python>pylint sdk/storage/azure-storage-blob/azure
```
Add the --rcfile command line argument with a relative path to the pylintrc from your current directory:
```
C:\azure-sdk-for-python\sdk\storage>pylint --rcfile="../../pylintrc" azure-storage-blob
```

Set the environment variable PYLINTRC to the absolute path of the pylintrc file:

set PYLINTRC=C:\azure-sdk-for-python\pylintrc

Run pylint:

C:\azure-sdk-for-python\sdk\storage>pylint azure-storage-blob

Run pylint at the package level using tox and it will find the pylintrc file:

pip install tox tox-monorepo
C:\azure-sdk-for-python\sdk\storage\azure-storage-blob>tox -e lint -c ../../../eng/tox/tox.ini

If you use the pylint extension for VS code or Pycharm it should find the pylintrc automatically.

How to disable a pylint error

# pylint:disable=connection-string-should-not-be-constructor-param

The pylint custom checkers for SDK guidelines fall into messages range C4717 - C4738. You will know you came across a custom checker if it contains a link to the guidelines.

In the case of a false positive, use the disable command to remove the pylint error.

Rules List

FAQs

What is azure-pylint-guidelines-checker?

A pylint plugin which enforces azure sdk guidelines. Visit Snyk Advisor to see a full health score report for azure-pylint-guidelines-checker, including popularity, security, maintenance & community analysis.

Is azure-pylint-guidelines-checker popular?

The python package azure-pylint-guidelines-checker receives a total of 856 weekly downloads. As such, azure-pylint-guidelines-checker popularity was classified as small. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is azure-pylint-guidelines-checker well maintained?

We found indications that azure-pylint-guidelines-checker is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is azure-pylint-guidelines-checker safe to use?

The python package azure-pylint-guidelines-checker was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 14 November-2024, at 20:48 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

Pylint checker name	How to fix this	How to disable this rule	Link to python guideline
client-method-should-not-use-static-method	Use module level functions instead.	# pylint:disable=client-method-should-not-use-static-method	link
missing-client-constructor-parameter-credential	Add a credential parameter to the client constructor. Do not use plural form "credentials".	# pylint:disable=missing-client-constructor-parameter-credential	link
missing-client-constructor-parameter-kwargs	Add a **kwargs parameter to the client constructor.	# pylint:disable=missing-client-constructor-parameter-kwargs	link
client-method-has-more-than-5-positional-arguments	Use keyword arguments to reduce number of positional arguments.	# pylint:disable=client-method-has-more-than-5-positional-arguments	link
client-method-missing-type-annotations	Check that param/return type comments are present or that param/return type annotations are present. Check that you did not mix type comments with type annotations.	# pylint:disable=client-method-missing-type-annotations	link
client-incorrect-naming-convention	Check that you use... snake_case for variable, function, and method names. Pascal case for types. ALL CAPS for constants.	# pylint:disable=client-incorrect-naming-convention	link
client-method-missing-kwargs	Check that any methods that make network calls have a **kwargs parameter.	# pylint:disable=client-method-missing-kwargs	link
config-missing-kwargs-in-policy	Check that the policies in your configuration function contain a **kwargs parameter.	# pylint:disable=config-missing-kwargs-in-policy	link
async-client-bad-name	Remove "Async" from your service client's name.	# pylint:disable=async-client-bad-name	link
file-needs-copyright-header	Add a copyright header to the top of your file.	# pylint:disable=file-needs-copyright-header	link
client-method-name-no-double-underscore	Don't use method names prefixed with "__".	# pylint:disable=client-method-name-no-double-underscore	link
specify-parameter-names-in-call	Specify the parameter names when calling methods with more than 2 required positional parameters. e.g. self.get_foo(one, two, three=three, four=four, five=five)	# pylint:disable=specify-parameter-names-in-call	link
connection-string-should-not-be-constructor-param	Remove connection string parameter from client constructor. Create a method that creates the client using a connection string.	# pylint:disable=connection-string-should-not-be-constructor-param	link
package-name-incorrect	Change your distribution package name to only include dashes, e.g. azure-storage-file-share	# pylint:disable=package-name-incorrect	link
client-suffix-needed	Service client types should use a "Client" suffix, e.g. BlobClient.	# pylint:disable=client-suffix-needed	link
docstring-admonition-needs-newline	Add a blank newline above the .. literalinclude statement.	# pylint:disable=docstring-admonition-needs-newline	No guideline, just helps our docs get built correctly for microsoft docs.
naming-mismatch	Do not alias models imported from the generated code.	# pylint:disable=naming-mismatch	link
client-accepts-api-version-keyword	Ensure that the client constructor accepts a keyword-only api_version argument.	# pylint:disable=client-accepts-api-version-keyword	link
enum-must-be-uppercase	The enum name must be all uppercase.	# pylint:disable=enum-must-be-uppercase	link
enum-must-inherit-case-insensitive-enum-meta	The enum should inherit from CaseInsensitiveEnumMeta.	# pylint:disable=enum-must-inherit-case-insensitive-enum-meta	link
networking-import-outside-azure-core-transport	This import is only allowed in azure.core.pipeline.transport.	# pylint:disable=networking-import-outside-azure-core-transport	link
non-abstract-transport-import	Only import abstract transports. Let core or end-user decide which transport to use.	# pylint:disable=non-abstract-transport-import	link
no-raise-with-traceback	Check that raise_with_traceback from azure-core is replaced with python 3 'raise from' syntax.	# pylint:disable=no-raise-with-traceback	link
name-too-long	Check that the length of class names, function names, and variable names are under 40 characters.	# pylint:disable=name-too-long	link
delete-operation-wrong-return-type	Check that delete* or begin_delete* methods return None or LROPoller[None].	# pylint:disable=delete-operation-wrong-return-type	link
client-method-missing-tracing-decorator	pylint:disable=client-method-missing-tracing-decorator	Check that sync client methods that make network calls have the sync distributed tracing decorator.	link
client-method-missing-tracing-decorator-async	pylint:disable=client-method-missing-tracing-decorator-async	Check that async client methods that make network calls have the async distributed tracing decorator.	link