flakeplus - additional pyflakes
- Version:
1.0.0
- Download:
- Source:
- Keywords:
flakes, development, process
–
Overview
flakeplus detects some additional flakes, part of the release process for Celery, Kombu et.al.
Flakes
All files must import absolute_import from __future__.
If Python 2.5 is a target, any file using the with statement must also import that from __future__
Disabled by options --2.6 and --2.7).
If Python 2.7 is the target --2.7 then all files must also import unicode_literals from __future__.
Code cannot contain debugging print statements
A debugging print statement is any print emitting a string that
optionally starts with any sequence of non-alphanumeric chars
an all-uppercase word followed by a colon,
Examples:
print('CONN: %r' % (connection,)) # DEBUG! print('The connection was lost') # NOT DEBUG print('> STUPID: %r' % (obj,)) # DEBUG! print('>>>>> OMFG: %r !!!!' % (obj,)) # definitely DEBUG!
Example
flakeplus is run from the commandline:
$ flakeplus dir1 .. dirN
If the target version is 2.6 and above, use the 2.6 switch:
$ flakeplus --2.6 dir1 .. dirN
If the target version is 2.7 and above, use the 2.7 switch:
$ flakeplus --2.7 dir1 .. dirN
Installation
You can install flakeplus either via the Python Package Index (PyPI) or from source.
To install using pip,:
$ pip install -U flakeplus
To install using easy_install,:
$ easy_install -U flakeplus
Downloading and installing from source
Download the latest version of flakeplus from http://pypi.python.org/pypi/flakeplus/
You can install it by doing the following,:
$ tar xvfz flakeplus-0.0.0.tar.gz $ cd flakeplus-0.0.0 $ python setup.py build # python setup.py install # as root
Using the development version
You can clone the repository by doing the following:
$ git clone git://github.com/ask/flakeplus.git
Bug tracker
If you have any suggestions, bug reports or annoyances please report them to the issue tracker at http://github.com/ask/flakeplus/issues/
License
This software is licensed under the New BSD License. See the LICENSE file in the top distribution directory for the full license text.
1 maintainer
Metadata
1 maintainer
Release files for flakeplus 1.1.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 |
|---|---|---|---|---|
| flakeplus-1.1.0.tar.gz | 6.8 kB | Without provenance | Details for flakeplus-1.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| flakeplus-1.1.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for flakeplus-1.1.0-py2.py3-none-any.whl |
Total release size: 13.9 kB
Release files / flakeplus-1.1.0.tar.gz
| Download URL | flakeplus-1.1.0.tar.gz |
|---|---|
| Size | 6.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9f0f27d88558aa935a3cb847a3c9a00365eb956e47b77585c00d6c6e067c823a
|
|
BLAKE2b-256 checksum How to use checksums |
ccd3556ca1b608924d7d26a874cffbdafe385f36717b8309c47a00742826732f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / flakeplus-1.1.0-py2.py3-none-any.whl
| Download URL | flakeplus-1.1.0-py2.py3-none-any.whl |
|---|---|
| Size | 7.1 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
98375a58bf20b4bbf66b669621b72bc8e65ecef5b46c3aff4c09dc2cf5a20042
|
|
BLAKE2b-256 checksum How to use checksums |
ea73cb6d7924c5bc6a06206c6a5e30863083f5af55652677cb33c37e0cbb62af
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for flakeplus 1.1.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.
