artm.version() sometimes returns wrong version number

[bt2901]

I have a long sequence of installs and reinstalls on my Windows machine (into different Anaconda virtual environments). It seems that some global system variable has stuck at "0.8.0" and haven't updated.

After following the instructions described at http://bigartm.readthedocs.io/en/v0.9.0/devguide/dev_build_windows.html I have this strange situation:

python -c "import artm; print(artm.version())"
0.8.0
python -c "import pkg_resources; version = pkg_resources.require('bigartm')[0].version; print(version)"
0.9.0
python -c "from artm import SmoothTimeInTopicsPhiRegularizer; print(SmoothTimeInTopicsPhiRegularizer)"
<class 'artm.regularizers.SmoothTimeInTopicsPhiRegularizer'>

So, artm thinks its version is 0.8.0, but in reality I had version 0.9.0 installed (and 0.9.0-exclusive functionality is available to me)

[JeanPaulShapo]

@bt2901
Actually, there are two version numbers, which you may encounter running BigARTM:

• In first case, artm.version() calls ArtmGetVersion function from C interface. This version is defined here;
• In the second case, AFAIK you get actual Python API version, which is defined there

I found it very strange to see 0.8.0 version in output, becase we have some other minor versions between 0.8.0 and 0.9.0. Could you check that you don't use outdated artm.dll?