This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Consider using release 26.10.27 instead.
Reason given by maintainers: https://github.com/PyCQA/flake8-bugbear/issues/272
A plugin for flake8 finding likely bugs and design problems in your program. Contains warnings that don’t belong in pyflakes and pep8:
bug·bear (bŭg′bâr′) n. 1. A cause of fear, anxiety, or irritation: *Overcrowding is often a bugbear for train commuters.* 2. A difficult or persistent problem: *"One of the major bugbears of traditional AI is the difficulty of programming computers to recognize that different but similar objects are instances of the same type of thing" (Jack Copeland).* 3. A fearsome imaginary creature, especially one evoked to frighten children.
List of warnings
B001
Do not use bare except:, it also catches unexpected events “ “like memory errors, interrupts, system exit, and so on. Prefer except Exception:. If you’re sure what you’re doing, be explicit and write except BaseException:.
Tests
Just run:
python setup.py test
License
MIT
Change Log
16.4.0
first published version
date-versioned
5 maintainers
Metadata
5 maintainers
Release files for flake8-bugbear 16.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| flake8-bugbear-16.4.0.tar.gz | 3.3 kB | Without provenance | Details for flake8-bugbear-16.4.0.tar.gz |
Release files / flake8-bugbear-16.4.0.tar.gz
| Download URL | flake8-bugbear-16.4.0.tar.gz |
|---|---|
| Size | 3.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f2f7bb101875a6964f173691b8e96da29020a6fe3d613b06364b78d906e686bd
|
|
BLAKE2b-256 checksum How to use checksums |
1db0719f4320ef805241d2c9de72d329630f79235048d6cff97f7447e382f14a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for flake8-bugbear 16.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
