spaCy/spacy/tests/website/conftest.py

from __future__ import unicode_literals
import pytest
import os


@pytest.fixture(scope='session')
def nlp():
    from spacy.en import English
    if os.environ.get('SPACY_DATA'):
        data_path = os.environ.get('SPACY_DATA')
    else:
        data_path = None
    return English(data_dir=data_path)


@pytest.fixture()
def doc(nlp):
    return nlp('Hello, world. Here are two sentences.')
add doctests for website 'api'-section 2015-09-28 15:22:13 +03:00			`from __future__ import unicode_literals`
			`import pytest`
* Allow SPACY_DATA environment variable in website tests 2015-10-10 09:58:57 +03:00			`import os`
add doctests for website 'api'-section 2015-09-28 15:22:13 +03:00

			`@pytest.fixture(scope='session')`
			`def nlp():`
access model via sputnik 2015-12-07 08:01:28 +03:00			`from spacy.en import English`
Use util.Package class for io Previous Sputnik integration caused API change: Vocab, Tagger, etc were loaded via a from_package classmethod, that required a sputnik.Package instance. This forced users to first create a sputnik.Sputnik() instance, in order to acquire a Package via sp.pool(). Instead I've created a small file-system shim, util.Package, which allows classes to have a .load() classmethod, that accepts either util.Package objects, or strings. We can later gut the internals of this and make it a proxy for Sputnik if we need more functionality that should live in the Sputnik library. Sputnik is now only used to download and install the data, in spacy.en.download 2015-12-29 20:00:48 +03:00			`if os.environ.get('SPACY_DATA'):`
			`data_path = os.environ.get('SPACY_DATA')`
			`else:`
			`data_path = None`
			`return English(data_dir=data_path)`
add doctests for website 'api'-section 2015-09-28 15:22:13 +03:00

			`@pytest.fixture()`
			`def doc(nlp):`
			`return nlp('Hello, world. Here are two sentences.')`