flake_master
flake_master is a manager for flake8 plugins and configuration.
If you have multiple projects with rich flake8 setup, you know how painful it could be to keep flake8 setup in all projects up to date and synced. This is what flake master does.
This library is inspired by eslint and does pretty much the same as flakehell. I'm bored.
Installation
pip install flake_master
Usage
Flake master can help with flake8 set setup and upgrade.
Setup
flake_master setup <preset name or path> <dir to do the setup>
This will do the following:
- download preset with all plugins versions and project setup (from Github);
- add required packages to
requirements.txt; - add plugins configuration to
setup.cfg; - create
.flake_masterfile with current preset version (add the file to vsc).
Upgrade
flake_master upgrade <dir with .flake_master>
This command will fetch last version of preset from .flake_master and apply
it to requirements.txt and setup.py.
Beware, it can overwrite some data, that was updated by flake_master and
then manually updated.
1 maintainer
Metadata
1 maintainer
Release files for flake-master 0.0.1
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 | |
|---|---|---|---|---|
| flake_master-0.0.1.tar.gz | 5.2 kB | Without provenance | Details |
Release files / flake_master-0.0.1.tar.gz
| Download URL | flake_master-0.0.1.tar.gz |
|---|---|
| Size | 5.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7987f64407ef5042e0a868092e9f3773d9ed6c67139b4e630057a09b5f48014b
|
|
BLAKE2b-256 checksum How to use checksums |
06867a5fd28f6416d1d8bdede5dfc46a1ef273df83b1100eeba1fdc26ae912cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.1.3 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.7.3
|
Security for flake-master 0.0.1
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.
