Or, how I learned not to rewrite bower in Python.
To answer the first, obvious question:
To allow Python developers/users access to bower components without requiring a node.js / npm infrastructure.
Very basic usage is implemented:
bower.py install <package> [version]
No dependencies are handled. Versions must be pinned.
This will work, preferably installed into a virtualenv:
pip install bower.py bower.py <command>
This is even more self-contained:
pip install vex vex -m bower pip install bower.py vex bower bower.py <command>
Copyright 2015, Richard Jones <email@example.com> and Rackspace, US, Inc.
Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
TODO: Figure out how to actually get changelog content.
Changelog content for this version goes here.
TODO: Brief introduction on what you do with files - including link to relevant help section.
|File Name & Checksum SHA256 Checksum Help||Version||File Type||Upload Date|
|bower.py-1.0-py2-none-any.whl (8.4 kB) Copy SHA256 Checksum SHA256||2.7||Wheel||Feb 4, 2015|
|bower.py-1.0.tar.gz (4.0 kB) Copy SHA256 Checksum SHA256||–||Source||Feb 4, 2015|