Skip to content
A place for community contributed samples for the pyVmomi library.
Python
Branch: master
Clone or download

Latest commit

jm66 and pgbidkar Fixes #520: Py3 compatibility and printing username and ipAddress (#613)
* Fixes #520: Py3 compatibility and printing username and ipAddress

* Fixes #520: Py3 compatibility and printing username and ipAddress
- replace %s substitution with string.format() method
Latest commit bc14f63 Oct 15, 2019

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.vscode Retrieves Port Group (#596) Sep 26, 2019
samples Fixes #520: Py3 compatibility and printing username and ipAddress (#613) Oct 15, 2019
.gitignore [sample] vcrpy as flight recorder Oct 3, 2014
.travis.yml Update .travis.yml and fix some format error May 19, 2017
LICENSE Copyright VMware Jun 26, 2014
README.md README.md - add travis-ci build badge Jul 29, 2014
requirements.txt update suds requirement Aug 9, 2017
setup.py feat: Include submodules of "samples" Sep 14, 2016
test-requirements.txt project requirements May 8, 2014

README.md

Build Status

pyvmomi-community-samples

Community contributed samples for the pyVmomi library.

The pyVmomi library itself is hosted here: https://github.com/vmware/pyvmomi/

The community samples website is here: http://vmware.github.io/pyvmomi-community-samples/

The samples contained here in are provided as-is from contributors around the pyVmomi community. They are intended as learning tools and may vary in quality. Any developer may contribute, enhance, or alter the samples. Ownership of any submitted sample reverts to the project itself

Philosophy

  • Sample Ownership and Copyright Licenses

    • the community creates the samples and the project retains ownership of the samples
    • the community curates the samples and licenses the samples under the project license
      • all samples are distributed under the root project license
      • A copyright line may be added if you contribute a change of more than 10 lines
  • Writing good samples:

    • A good sample shows how to do one thing and only one thing at a time.
    • A good sample follows good and consistent code style see: pep8.
    • When arbitrary choices are made, a good sample chooses the simplest default.
    • Samples must be willing to teach programming as well as the API!

Code Style

Please conform to pep8 standards. Check your code by running the pep8 tool. https://pypi.python.org/pypi/pep8

Contribution Process

  • Follow the GitHub process
    • please use one branch per sample or change-set
    • please use one commit and pull request per sample
    • if you include a license with your sample, use the project license
You can’t perform that action at this time.