“py.test”与“pytest”命令

The py.test在我的例子中，命令失败了，而pytest运行完全正常。

我使用 pytest-flask 插件：

platform linux -- Python 3.5.2, pytest-3.0.2, py-1.4.31, pluggy-0.3.1
rootdir: /home/sebastian/develop/py/flask-rest-template, inifile: 
plugins: flask-0.10.0

当我调用$ py.test我收到以下错误：

Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/_pytest/config.py", line 301, in _getconftestmodules
    return self._path2confmods[path]
KeyError: local('/home/sebastian/develop/py/flask-rest-template')

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/_pytest/config.py", line 332, in _importconftest
    return self._conftestpath2mod[conftestpath]
KeyError: local('/home/sebastian/develop/py/flask-rest-template/conftest.py')

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/_pytest/config.py", line 338, in _importconftest
    mod = conftestpath.pyimport()
  File "/usr/local/lib/python3.5/dist-packages/py/_path/local.py", line 650, in pyimport
    __import__(modname)
  File "/usr/local/lib/python3.5/dist-packages/_pytest/assertion/rewrite.py", line 207, in load_module
    py.builtin.exec_(co, mod.__dict__)
  File "/home/sebastian/develop/py/flask-rest-template/conftest.py", line 2, in <module>
    from app.app import create_app
  File "/home/sebastian/develop/py/flask-rest-template/app/app.py", line 1, in <module>
    from flask import Flask
ImportError: No module named 'flask'
ERROR: could not load /home/sebastian/develop/py/flask-rest-template/conftest.py

这是我的实际情况conftest.py file:

import pytest
from app.app import create_app

@pytest.fixture
def app():
    app = create_app()
    return app

我的项目结构如下：

.
├── app
│   ├── __init__.py
│   ├── app.py
│   └── config.py   # flask configuration objects
├── conftest.py     # pytest configruation
├── requirements.txt
├── ...
└── tests
    └── ...

那么，这两个命令有什么区别呢？为什么一个失败而另一个没有？

update 1

1）我必须改变我的相对进口from .config import Config or from config import Config绝对的像from app.config import Config

2) 运行烧瓶python3 -m app.app

3) now pytest and py.test工作正常

非常感谢各位的帮助！

update 2

这变得很奇怪......当使用绝对导入时，使用以下命令运行 python-m选项和烧瓶debug=True那么werkzeug库没有按预期重新加载源：

http://chase-seibert.github.io/blog/2015/06/12/flask-werkzeug-reloader-python-dash-m.html http://chase-seibert.github.io/blog/2015/06/12/flask-werkzeug-reloader-python-dash-m.html

https://github.com/pallets/werkzeug/issues/461 https://github.com/pallets/werkzeug/issues/461

https://github.com/pallets/flask/issues/1246 https://github.com/pallets/flask/issues/1246

这帮助了我app/app.py:

if __name__ == '__main__':
    app.run(debug=True, use_reloader=False)

Then python -m app.app工作正常。

更详细地回答有关实际命令（意味着在命令行上调用该工具）的问题：

The py.test调用是旧的且已损坏的接头。pytest是新的热点（自 3.0 起）。py.test and pytest我猜调用将共存很长一段时间，但在某些时候py.test可能会被弃用。所以我会推荐#dropthedot https://twitter.com/davehunt82/status/756080181085872129.

[...]因此从 pytest 3.0 开始，我们将支持并推荐使用 pytest 作为主命令，而不是 py.test。将来我们可能会弃用 py.test 甚至可能将其删除。

-- 戴夫·亨特 https://github.com/pytest-dev/pytest/issues/1629#issue-161422224

向后兼容性对于 pytest 社区来说是一个非常重要的问题，因此旧的方式可能永远不会消失，而且无论如何保留它也不会造成太大的维护负担（它只是被定义为一个不同的入口点）setup.py https://github.com/pytest-dev/pytest/blob/3.0.0/setup.py#L73).