build_commands
This package provides common setuptools command utilities if you need to initialize your package with npm, bower or gulp commands.
Usage
You are supposed to create in your own package a Yeoman like project folder (for example: your_package/templates).
Add the build_commands dependency to your pretend your_package.
Update your setup.cfg adding the following:
[aliases] npm = npm -i your_package/templates bower = bower gulp = gulp -i your_package/templates -g gulpfile.babel.js
If you are using bower you can add a .bowerrc file to your package root (where your setup.cfg file lives) with the following (see http://bower.io/docs/config/#cwd):
{
"directory": "bower_components",
"cwd": "./your_package/templates/"
}
And update your setup.py entry points distutils commands:
entry_points="""\ [distutils.commands] npm = build_commands:NpmCommand bower = build_commands:BowerCommand gulp = build_commands:GulpCommand """,
This way once installed your your_package you can initialize your Yeoman project with:
$ python setup.py install/develop $ python setup.py npm $ python setup.py bower $ python setup.py gulp
And all your frontend stuff will be processed automatically (SASS, minification, uglyfication, etc).
Metadata
Release files for build_commands 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 | Actions |
|---|---|---|---|---|
| build_commands-0.0.1.tar.gz | 5.4 kB | Without provenance | Details for build_commands-0.0.1.tar.gz |
Release files / build_commands-0.0.1.tar.gz
| Download URL | build_commands-0.0.1.tar.gz |
|---|---|
| Size | 5.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9421d2794336fa1196e67a92c8b44cb9e6e6d703259301b1a14c1e0956f94003
|
|
BLAKE2b-256 checksum How to use checksums |
f06d3ac2e1d4c153cde4a547bb5d6490994555ccf87451ee7eae0a0f60d16a3a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for build_commands 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.