allure.environment is missing in allure.py

[//]: # (
. Note: for support questions, please use Stackoverflow or Gitter**.
. This repository's issues are reserved for feature requests and bug reports.
.
. In case of any problems with Allure Jenkins plugin** please use the following repository
. to create an issue: https://github.com/jenkinsci/allure-plugin/issues
.
. Make sure you have a clear name for your issue. The name should start with a capital
. letter and no dot is required in the end of the sentence. An example of good issue names:
.
. - The report is broken in IE11
. - Add an ability to disable default plugins
. - Support emoji in test descriptions
)

#### I'm submitting a ...
- [x] bug report
- [ ] feature request
- [ ] support request => Please do not submit support request here, see note at the top of this template.

#### What is the current behavior?
Based on documentation [here](https://github.com/allure-framework/allure-pytest) to apply some environment configurations we should use allure.environment(report='Allure report', browser=u'Я.Браузер') syntax. But in allure.py environment is missing. Before we have to use some environment.properties file in report folder to apply variables to the report. New functionality is missing.
Content of allure.py:
```
from allure_commons._allure import label
from allure_commons._allure import severity
from allure_commons._allure import tag
from allure_commons._allure import epic, feature, story
from allure_commons._allure import link
from allure_commons._allure import issue, testcase
from allure_commons._allure import Dynamic as dynamic
from allure_commons._allure import step
from allure_commons._allure import attach
from allure_commons.types import Severity as severity_level
from allure_commons.types import AttachmentType as attachment_type

__all__ = [
'label',
'severity',
'tag',
'epic'
'feature',
'story',

'link',
'issue',
'testcase',

'step'

'dynamic'

'severity_level',

'attach',
'attachment_type'
]

```

#### If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

#### What is the expected behavior?

#### What is the motivation / use case for changing the behavior?

#### Please tell us about your environment:

- Allure version: 2.2.1
- Test framework: pytest@3.5
- Allure adaptor: allure-pytest@2.1.0b1

#### Other information

[//]: # (
. e.g. detailed explanation, stacktraces, related issues, suggestions
. how to fix, links for us to have more context, eg. Stackoverflow, Gitter etc
)

Beginne mit allure.py und vergleiche dessen exportierte API mit der im Issue verlinkten Dokumentation zu allure-pytest, wobei du dich auf die dokumentierte allure.environment-Syntax konzentrierst. Prüfe die bestehende Issue-Diskussion als Kontext und ermittle die erwartete öffentliche API; abgeschlossen bedeutet, dass die dokumentierte Umgebungskonfiguration über allure.py verfügbar ist und sich wie beschrieben verhält.

Vom Indexierungsmodell aus dem Issue-Text verfasst.