Whiskers stores package and version data from buildouts.
“Vibrissae (singular: vibrissa), or whiskers, are specialized hairs (or, in certain bird species, specialized feathers) usually employed for tactile sensation.” - Wikipedia
Reason behind Whiskers
Why? Shortly to automate your workflow.
Think an environment where you’re managing tens or hundereds of buildouts - say Plone instances. Most of them have probably almost same packages and almost same versions. Now you make an critical fix to some custom package and you need to know which buildouts you have to update. Whikers helps you here by knowing what is required and where.
Installation using virtualenv
virtualenv whiskers --no-site-packages cd whiskers bin/pip install whiskers wget https://github.com/pingviini/whiskers/raw/master/production.ini bin/pserve production.ini
Whiskers is currently just storing buildout information. Future plans involve at least following features:
- Have a buildout history so you can follow what packages have been updated, added or removed.
- Fix issue #1: Not all packages are shown. [markvl]
- Fixed how package versions are sorted. [markvl & pingviini]
- Initial version
Release history Release notifications
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size whiskers-0.2.zip (20.3 kB)||File type Source||Python version None||Upload date||Hashes View hashes|