An error occurred fetching the project authors.
- 09 Mar, 2022 1 commit
-
-
HongzheWang authored
-
- 18 Nov, 2021 1 commit
-
-
Jérome Perrin authored
Now that slapos.core on python2 can use softwares on python3, we no longer need to test for python2
-
- 24 Aug, 2021 1 commit
-
-
Lu Xu authored
-
- 10 Aug, 2021 1 commit
-
-
Eric Zheng authored
This change includes a rewrite of the previous component/headless-chromium, which used an outdated version of Chromium. It differs from component/chromium in that: - It only provides a headless shell, rather than the full Chromium browser (though this can be changed). - It compiles from source rather than downloading a binary build. There is also a new software release software/headless-chromium which makes use of the updated component/headless-chromium to expose a remote debugging port. See also nexedi/slapos!1014.
-
- 12 Jul, 2021 1 commit
-
-
Jérome Perrin authored
-
- 30 Jun, 2021 1 commit
-
-
Thomas Gambier authored
-
- 26 Apr, 2021 1 commit
-
-
Julien Muchembled authored
See merge request nexedi/slapos!968
-
- 17 Dec, 2020 1 commit
-
-
Léo-Paul Géneau authored
moves python2 release to component/jupyter-py2 because it is required by ERP5 but not maintained anymore moves to python 3 : - test/test.py - jupyter_notebook_config.py.jinja - ERP5kernel.py modifies custom.js to create a workaround for events issue see (https://github.com/jupyter/notebook/issues/2499) upgrades slapos.cookbook version to 1.0.171 to use zero_knowledge recipe with python 3 adds jupyter partition check in software/erp5/test/test_erp5.py
-
- 02 Dec, 2020 1 commit
-
-
Jérome Perrin authored
The initial intent was to use an interpreter named `python_for_test` and not `python`, so that software do not accidentally pick up this python during compilation. 6033e4fa (software/slapos-sr-testing: fix python3 profile, 2020-12-01) was a quick fix for some python3 compatibility issues discovered after merge, but it was not correct, because by using ${python-interpreter:eggs}, it was installing the default python-interpreter section, which has an interpreter named `python`. This caused issues while building proxysql, which assumes /usr/bin/env python is python2. The fix is to override python-interpreter directly, we don't need another section eggs here.
-
- 27 Nov, 2020 1 commit
-
-
Jérome Perrin authored
Change to run all tests with python -m unittest, which will allow us to remove workaround for the $PYTHONPATH set by setup.py test. For this we use `[python-interpreter]` which uses pygolang.main to behave like a "normal" python interpreter with eggs available, but without the usual problems of interpreters generated by zc.recipe.eggs - it supports all command line flags and have current directory in sys.path. Tests now have an explicit name, that we set to the software name as before, and the special test dynamically checking all profiles json schemas (part of slapos.cookbook egg, at the root of slapos repository),is named json-schemas. It is also changed to run as default tests in python2 and python3, not only in extras for python2.
-
- 02 Nov, 2020 1 commit
-
-
Léo-Paul Géneau authored
-
- 30 Oct, 2020 1 commit
-
-
Léo-Paul Géneau authored
The only change to support python3 in software/plantuml is the move from hexagonit to slapos download recipe in component/tomcat. We also move the test to python3 by using plantuml egg v0.3.0. As this egg doesn't support python2, the test is not done anymore in Python2.
-
- 26 Oct, 2020 1 commit
-
-
Léo-Paul Géneau authored
Changes configuration files to run repman tests in python3.
-
- 16 Oct, 2020 1 commit
-
-
Léo-Paul Géneau authored
-
- 08 Jul, 2020 1 commit
-
-
Bryton Lacquement authored
-
- 24 Apr, 2020 1 commit
-
-
Julien Muchembled authored
TODO: There are still direct references to specific version of Python in: - slapos component - bazel templates - nextcloud & theia SR
-
- 13 Mar, 2020 1 commit
-
-
Bryton Lacquement authored
-
- 10 Mar, 2020 1 commit
-
-
Bryton Lacquement authored
-