Skip to main content
Join the official 2020 Python Developers SurveyStart the survey!

Windows Management Infrastructure API for Python.

Project description

This project provides a Python native module wrapper over the Windows Management Infrastructure (MI) API [1].

Works with Python 2.7 and 3.x on any Windows version which supports the MI API, both x86 and x64.

It includes also a drop-in replacement for the Python WMI [2] module, proving much faster execution times and no dependency on pywin32.

Installation

Pip is the preferred way to install PyMI. Pre-compiled binary wheels are available on Pypi [3]:

pip install PyMI

Usage

This project can be used either with a lower level interface that reflects the underlying MI API structure or with the higher level (and slightly slower) WMI module replacement.

MI module basic usage

Here’s a simple example which enumerates all processes and kills any instance of “KillerRabbitOfCaerbannog.exe”.

import mi

with mi.Application() as a:
    with a.create_session(protocol=mi.PROTOCOL_WMIDCOM) as s:
        proc_name = u'notepad.exe'
        with s.exec_query(
                u"root\\cimv2", u"select * from Win32_Process") as q:
            i = q.get_next_instance()
            while i is not None:
                if i[u'name'].lower() == u"KillerRabbitOfCaerbannog.exe":
                    cls = i.get_class()
                    # Prepare parameters
                    params = a.create_method_params(cls, u"Terminate")
                    # Exit code
                    params['reason'] = 10
                    # Invoke method
                    with s.invoke_method(i, u"Terminate", params) as op:
                        op.get_next_instance()
                i = q.get_next_instance()

WMI module basic usage

And here’s the same example written using the WMI module replacement, which provides a simpler and higher level interface over the mi API:

import wmi

conn = wmi.WMI()
for p in conn.Win32_Process():
    if p.Name == u"KillerRabbitOfCaerbannog.exe":
        p.Terminate(reason=10)

Build

Use the following to build Python 3 wheels. Those will be copied to the build dir.

python setup.py bdist_wheel

The best way to build PyMI for Python 2.7 or 3.4 and below is to use the Visual Studio solution (described below). This will statically link the vc140 runtime, which is required by PyMI.

Custom VS env vars

distutils will automatically locate your Visual Studio and Windows SDK installation. If you’d like to call vcvarsall.bat yourself and use a specific version, use the following:

function SetVCVars($vcvarsdir, $platform="amd64")
{
    pushd $vcvarsdir
    try
    {
        cmd /c "vcvarsall.bat $platform & set" |
        foreach {
          if ($_ -match "=") {
            $v = $_.split("="); set-item -force -path "ENV:\$($v[0])"  -value "$($v[1])"
          }
        }
    }
    finally
    {
        popd
    }
}

# Replace this folder with the one in which the vcvarsall.bat script is
# located (the exact location depends on the Visual Studio version).
# SetVCVars "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build"
SetVCVars "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC"

$env:DISTUTILS_USE_SDK=1
$env:MSSdk=1

python setup.py bdist_wheel

Make sure to use the Visual Studio toolset that matches the Python version that you’re targetting: https://wiki.python.org/moin/WindowsCompilers.

By default, we’re statically linking the VC runtime. To enable dynamic linking, set $env:PYMI_VCRUNTIME_DYNAMIC_LINKING="y".

Debug builds

The easiest way to do a debug build is to set the following in setup.cfg:

[build]
debug = 1

This will be honored regardless of the build type (e.g. stdist, wheel, etc).

To enable distutils debug logging, you may set the following:

$env:DISTUTILS_DEBUG = 1

Before doing a debug build, you may wish to clean the build dir.

Using the Visual Studio Solution

Open the provided PyMI.sln solution in Visual Studio 2015 [4], choose your target Python version / platform and build. Wheel packages are automatically generated in the dist folder for release builds.

Note: the target Python version must be present. The Python path can be customized by setting the corresponding PythonDir* user macro, e.g. PythonDir_34_x64. The wheel and GitPython packages are required during the build process:

pip install wheel
pip install GitPython

As an alternative, you can use the MSBuild CLI tool:

$env:MSBuildEmitSolution="TRUE"
MSBuild.exe .\PyMI.sln /p:Configuration="Release (Python 3.7)"

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Files for PyMI, version 1.0.6
Filename, size File type Python version Upload date Hashes
Filename, size PyMI-1.0.6-cp35-cp35m-win32.whl (176.9 kB) File type Wheel Python version cp35 Upload date Hashes View
Filename, size PyMI-1.0.6-cp35-cp35m-win_amd64.whl (217.5 kB) File type Wheel Python version cp35 Upload date Hashes View
Filename, size PyMI-1.0.6-cp36-cp36m-win32.whl (176.9 kB) File type Wheel Python version cp36 Upload date Hashes View
Filename, size PyMI-1.0.6-cp36-cp36m-win_amd64.whl (217.5 kB) File type Wheel Python version cp36 Upload date Hashes View
Filename, size PyMI-1.0.6-cp37-cp37m-win32.whl (261.2 kB) File type Wheel Python version cp37 Upload date Hashes View
Filename, size PyMI-1.0.6-cp37-cp37m-win_amd64.whl (317.9 kB) File type Wheel Python version cp37 Upload date Hashes View
Filename, size PyMI-1.0.6-cp38-cp38-win32.whl (260.8 kB) File type Wheel Python version cp38 Upload date Hashes View
Filename, size PyMI-1.0.6-cp38-cp38-win_amd64.whl (317.5 kB) File type Wheel Python version cp38 Upload date Hashes View
Filename, size PyMI-1.0.6.tar.gz (63.9 kB) File type Source Python version None Upload date Hashes View

Supported by

Pingdom Pingdom Monitoring Google Google Object Storage and Download Analytics Sentry Sentry Error logging AWS AWS Cloud computing DataDog DataDog Monitoring Fastly Fastly CDN DigiCert DigiCert EV certificate StatusPage StatusPage Status page