Andreas Maier

SyntaxError: future feature annotations is not defined with version 0.18.4 on Python 3.6

One small correction: Looking at the source code of SFCB, it turns out that SFCB 1.4.5 actually introduced support for pull operations. The SFCB version that was used in the error case was 1.3.11, which explains why it did not support them. Still, this version, and probably any SFCB version before 1.4.5 returns the wrong status code. I di not expect that SFCB fixes the status code in these versions, but this issue can be used by users to understand that they can fix this by upgrading SFCB to 1.4.5...

Invalid CIM status code for pull operations

The latest version I can see on Pypi is the 0.15 version released on 7/21. However, when I do a pip install docutils --upgrade it downloads a docutils-0.15.post1-py2-none-any.whl, wich after installation reports 0.15 (without .post1). That is very strange... I can confirm that the new version solves the original issue, but the strange thing is that it is called version 0.15. So in any given Python environment, I have no way to find out whether it is the broken 0.15 or the fixed 0.15??

The latest version I can see on Pypi is the 0.15 version released on 7/21. However, when I do a pip install docutils --upgrade it downloads a docutils-0.15.post1-py2-none-any.whl, wich after installation reports 0.15 (without .post1). That is very strange...

The latest version I can see on Pypi is the 0.15 version released on 7/21.

We (pywbem package) also ran into the same kind of issue on Python 2.7 (2.7.16 on local MacOS and 2.7.15 on Travis xenial), although on a different line of docutils. I verified that the issue occurs with docutils 0.15, and does not occur with docutils 0.14. We will pin docutils to 0.14 until this issue is fixed. Travis log of the issue: https://travis-ci.org/pywbem/pywbem/jobs/561714372 pywbem issue documenting this: https://github.com/pywbem/pywbem/issues/1788 End of the traceback: File "/home/travis/virtualenv/python2.7.15/lib/python2.7/site-packages/docutils/io.py",...

We also ran into a similar issue in pywbem, although on a different line of docutils. I verified that the issue occurs with docutils 0.15, and does not occur with docutils 0.14. We will pin docutils to 0.14 until this issue is fixed. Travis log of the issue: https://travis-ci.org/pywbem/pywbem/jobs/561714372 pywbem issue documenting this: https://github.com/pywbem/pywbem/issues/1788 End of the traceback: File "/home/travis/virtualenv/python2.7.15/lib/python2.7/site-packages/docutils/io.py", line...