andy-maier
commented
7 years ago I did some testing, and think it may be related to a mis-built wheel archive.
Please double check which pywbem package and scripts you are invoking:
- the version in the checked out repo
- a version installed into a python env as egg (there is a
pywbem-M.N.U-py2.7.egg-infodirectory insite-packages) - a version installed into a python env as wheel (there is a
pywbem-M.N.U.dist-infodirectory insite-packages)
Also, which version of pywbem did you use.
While investigating this, I found out how the hashbang lines of scripts are treated by the build and install process:
When the wheel archive is built, the hashbang line of the scripts we supply (those listed in the scripts argument of setup()) is modified (just the copy that is in the archive). The corresponding output from the build process is:
running build_scripts
creating build/scripts-2.7
copying and adjusting wbemcli -> build/scripts-2.7
copying and adjusting wbemcli.py -> build/scripts-2.7
copying and adjusting mof_compiler -> build/scripts-2.7
copying wbemcli.bat -> build/scripts-2.7
copying mof_compiler.bat -> build/scripts-2.7I checked all versions of the pywbem wheel archives we have on Pypi, and here are the hashbang lines of the three scripts that are "adjusted" during the build:
- pywbem 0.10.0:
#!/home/maiera/virtualenvs/test_test4/bin/python - pywbem 0.9.1:
#!python - pywbem 0.9.0:
#!python
Before 0.9.0, we did not build wheel archives.
When the wheel archive is installed, the hashbang line of the scripts is again adjusted if it was #!python, to the absolute path of the python that was found in the environment. The absolute path in the hashbang line of 0.10.0 remained unchanged, and of course does not work.
This install adjustment also happens when a package is installed as an egg (e.g. when installing from the source archive with python setup.py install). However, in the source archive, our scripts have the unchanged hashbang line they have in the repo.
I verified that our current (0.11.0-dev) wheel build (on CygWin) produces the #!python hashbang.
Bottom line:
- Please find out whether your wbemcli invocation problem is with 0.10.0 and with wheel install. I suppose the problem would exist independently of CygWin.
- We need to fix the incorrect hashbang lines that somehow made it into the 0.10.0 wheel archive. I created issue #754 for that.
KSchopmeyer
For some reason, on windows with cygwin, when the test_wbemcli.py tests is run calling wbemcli directly it produces and error saying that it cannot find the app wbemcli. When wbemcli .bat is used, the script works.
Andy suggested that we may have an issue with pathing so we need to investigate that.