1. question: Can wheels support a postinstall script? Background: I'm in the process of setting up a build script for that part of our company's software that is ported to Python 3.4. I am using either wheels built by 'pip wheel' and cache them locally, or, if this doesn't work (numpy and pywin32 for example), convert bdist_wininst installers to wheels with 'wheel convert xxx.exe'. Works fine for numpy and some other stuff, but not for pywin32. pywin32 contains a postinstall script that installs some dlls into the right locations and also does other stuff. Can a wheel run an included postinstall (and preremove) script? 2. question: I am building wheels for py2exe. If the wheel is built with python 3.3, the resulting wheel filename is py2exe-0.9.0.3-py33-none-any.whl. If the wheel is built with python 3.4, the filename is py2exe-0.9.0.3-py34-none-any.whl. Both are (kind-of) pure python distributions. 'pip install' can install the former both for Python 3.3 and Python 3.4, the latter only for Python 3.4. The only reason can be the filename. Does the -py34- part mean that *at least* Python 3.4 is required, and does -py33- mean that *at least* Python 3.3 is required? What would -cp33- or -cp34- mean? Sorry about these questions, but I'm lost what these filenames really mean (and how they are created). Thanks, Thomas