Skip to content

A
avocado

openeuler / avocado

通知 0
Star 0
Fork 0
A
avocado

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 12 8月, 2016 1 次提交
  3. 13 7月, 2016 1 次提交
  5. 15 6月, 2016 1 次提交
  7. 24 5月, 2016 1 次提交
  9. 16 5月, 2016 1 次提交
  11. 26 4月, 2016 1 次提交
    • C
      Travis: improve cleanup of per-commit environment · a21f1bc7
      由 Cleber Rosa 提交于 
      When running the per-commit checks on CI, the previous environment is
not as clean as it should be.

One example is when a given work introduces a new plugin. First the
HEAD of the branch is tested, which includes the installation of the
new plugin.  Then, the per-commit checks would return to the first
commit in the branch, which doesn't contain the plugin, but the
environment still knows about it.  This is a matter of forcing the
clean up of setuptools entrypoints (or any setuptools generated info
for that matter).

While adding the deeper cleaning, it seemed useful to split the
Makefile "link" target into "develop", which runs "python setup.py
develop" on the Avocado source tree alone.
Signed-off-by: NCleber Rosa <crosa@redhat.com>
      a21f1bc7
  13. 01 3月, 2016 1 次提交
  15. 20 2月, 2016 1 次提交
  17. 19 2月, 2016 2 次提交
  19. 18 2月, 2016 1 次提交
    • H
      Use environment marker for conditional requirements · 03c04b98
      由 Hao Liu 提交于 
      Managing different requirements files for different python version
requires much more efforts when the requirements became too complex.

This issue emerged when a required package `stevedore` decide not
supporting Python 2.6 since version `1.11.0`.

```
>>> import stevedore
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python2.6/site-packages/stevedore/__init__.py", line 23, in <module>
    LOG.addHandler(logging.NullHandler())
AttributeError: 'module' object has no attribute 'NullHandler
```

Pip provides a feature named [Environment
Markers](https://www.python.org/dev/peps/pep-0496/) for requirements
file to include specific packages conditionally which could properly
solve this issue.

This fix:
1. Use environment markers and merge python version specific
requirements files;
2. Remove python version specific requirements files references in
`Makefile` and Travis configuration;
3. Use `pip install -r requirements.txt` to replace per-line package
installation;
4. Restrain package `stevedore` on Python 2.6 to `1.10.0`.
Signed-off-by: NHao Liu <hliu@redhat.com>
      03c04b98
  21. 12 2月, 2016 1 次提交
    • C
      Makefile: cleanup Python compiled files properly · 002790f1
      由 Cleber Rosa 提交于 
      One of the clean steps executed prior to the deletion of the 'pyc' files
calls `$(PYTHON) setup.py develop --uninstall --user`, which ends up
loading modules and creating some of those again. Let's change the order
so that the Python compiled files are really gone after a `make clean`.
Signed-off-by: NCleber Rosa <crosa@redhat.com>
      002790f1
  23. 11 2月, 2016 1 次提交
  25. 10 2月, 2016 1 次提交
  27. 20 1月, 2016 1 次提交
    • L
      Makefile: Call setup.py develop in "make link" · afcb0e5a
      由 Lukáš Doktor 提交于 
      The "make link" target purpose is to help avocado developers to prepare
environment to run avocado from sources including all subprojects.
Nowadays it requires to run "setup.py develop" manually, but let's
assume wast majority of users of "make link" feature use "setup.py
develop --user" and call it automatically for each subproject (if they
support that).

This way simple "make link" prepares the environment to run avocado from
sources. It can also be used when new targets (plugins) are added
without the need to think which subproject needs to be updated.

NOTE: The subprojects are responsible to add the "python setup.py
develop --user" into the "link" and "unlink" targets.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
      afcb0e5a
  29. 09 1月, 2016 1 次提交
  31. 16 12月, 2015 7 次提交
  33. 15 10月, 2015 1 次提交
  35. 09 10月, 2015 2 次提交
  37. 30 9月, 2015 1 次提交
  39. 11 9月, 2015 1 次提交
  41. 10 9月, 2015 1 次提交
  43. 13 8月, 2015 1 次提交
  45. 31 7月, 2015 1 次提交
  47. 30 7月, 2015 2 次提交
  49. 07 7月, 2015 1 次提交
  51. 24 6月, 2015 1 次提交
  53. 23 6月, 2015 2 次提交
  55. 16 6月, 2015 1 次提交
  57. 09 6月, 2015 1 次提交
  59. 06 6月, 2015 1 次提交