INSTALLATION
Example install, using VirtualEnv:
# install/use python virtual environment virtualenv ~/virtenv_scratch --no-site-packages # activate the virtual environment source ~/virtenv_scratch/bin/activate # upgrade pip in the new virtenv pip install -U pip setuptools # install this package in DEVELOPMENT mode python setup.py develop # or simply install # python setup.py install
CONFIGURATION
Example configuration, eg at ~/.members:
mailman2:
base_url: http://some.domain.com/mailman2
lists:
announce-list:
user: bla@bla.com
password: asdfvi5f211
memo-list:
user: bla@bla.com
password: dasdf458@1j
dept-list:
github:
user: kejbaly2
token: FGIOUSODIUGSDGJ
# password: ********
user_attrs: [email, bio, url]
orgchart:
base_url: http://some.domain.com/orgchart3
USAGE
Mailman2
Example usage, for Mailman2:
members mailman2 dept-list
Overriding username and password:
members mailman2 dept-list -u other -p SoM3P@Ss!
OrgChart 3
Example usage, for OrgChart 3:
members orgchart3 teamlead cward
BUILD DOCS
Example scenario for building docs with sphinx:
cd docs make html
TESTING
Testing is py.test based. Run with:
py.test tests/ -v
DEVELOPMENT
Install the supplied githooks; eg,
ln -s ~/repos/members/_githooks/commit-msg ~/repos/members/.git/hooks/commit-msg ln -s ~/repos/members/_githooks/pre-commit ~/repos/members/.git/hooks/pre-commit
Metadata
Release files for members 0.0.5
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 | |
|---|---|---|---|---|
| members-0.0.5.tar.gz | 10.1 kB | Without provenance | Details |
Release files / members-0.0.5.tar.gz
| Download URL | members-0.0.5.tar.gz |
|---|---|
| Size | 10.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
06d79912a4eea739f818f6c26715ff5c9c8f11078b75e8d764d2e86321baa235
|
|
BLAKE2b-256 checksum How to use checksums |
fb823c5ac735234de20528617182ae3d2685d1df2c0427f8e9ebf094837a232e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for members 0.0.5
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.