version up: setuptools 44.0.0

surykatka 0.4.2 requires setuptools>40.5.0

This version is also the last one to be compatible with Python 2.

stack/slapos.cfg

@@ -100,7 +100,7 @@ eggs =
   slapos.libnetworkcache
 
 [versions]
-setuptools = 40.4.3
+setuptools = 44.0.0
 # Use SlapOS patched zc.buildout
 zc.buildout = 2.7.1+slapos001
 # Use SlapOS patched zc.recipe.egg (zc.recipe.egg 2.x is for Buildout 2)

[Julien Muchembled]

It seems to break some doctests. For example slapos.recipe.template:

File "slapos/recipe/template/README.jinja2.txt", line 507, in README.jinja2.txt
Failed example:
    run_buildout() # doctest: +ELLIPSIS
Expected:
    Uninstalling template.
    Uninstalling sample.
    Getting distribution for 'samplerecipe'.
    Got samplerecipe 0.0.0.
    Installing template.
    The template install returned None.  A path or iterable os paths should be returned.
    warning: install_lib: '...' does not exist -- no Python modules to install
    <BLANKLINE>
    zip_safe flag not set; analyzing archive contents...
Got:
    Uninstalling template.
    Uninstalling sample.
    Getting distribution for 'samplerecipe'.
    Got samplerecipe 0.0.0.
    Installing template.
    The template install returned None.  A path or iterable os paths should be returned.
    WARNING: The easy_install command is deprecated and will be removed in a future version.
    warning: install_lib: 'build/lib' does not exist -- no Python modules to install
    <BLANKLINE>
    zip_safe flag not set; analyzing archive contents...

Changing what's Expected does not look a good idea.

/cc @jerome @kazuhiko

[Jérome Perrin]

buildout doctests usually define some replacement regex to apply on actual output before checking it matches expected (for example zc.recipe.egg tests ).

We could introduce something to replace "WARNING: The easy_install command is deprecated and will be removed in a future version." by ""

[Jérome Perrin]

I just committed slapos.recipe.template@065564b0 to fix that doctest failure, using the approach I suggested.

This deprecation will impact buildout I guess, there's an issue at https://github.com/buildout/buildout/issues/493 ( I did not check this issue )