pyphosphor - OpenBMC Phosphor Python integration

	Commit message (Collapse)	Author	Age	Files	Lines
*	Remove mapper bindings	Brad Bishop	2016-07-20	1	-162/+0
\| \| \| \| \| \| \|	Move mapper bindings back to the phosphor-objmgr project. Change-Id: I9fd614bb74d7607da08a8ffb118ca41441b7b904 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
*	Use standard DBUS naming conventions	Brad Bishop	2016-06-06	1	-5/+4
\| \| \| \| \| \| \| \| \| \|	The existing service/iface/object path names were out-of-spec. busname: org.openbmc.ObjectMapper iface: org.openbmc.ObjectMapper path: /org/openbmc/ObjectMapper Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
*	Move common code from REST server	Brad Bishop	2016-04-29	1	-0/+120
\| \| \| \| \|	Moving a bunch of code with common utility out of the rest server. No new functionality provided.
*	Introducing pyobmc	Brad Bishop	2016-04-15	1	-0/+43
	We have openbmc python utilities scattered all over the place. To facilitate reuse, bring them together in a single python package. None of this is new code, it was all simply ported and re-arranged from other projects. Ran everything through pep8.