pep518 venvs¶

drain_swamp.pep518_venvs.DC_SLOTS: dict[str, bool]¶: Allows dataclasses.dataclass __slots__ support from py310

drain_swamp.pep518_venvs.TOML_SECTION_VENVS: str = "venvs"¶: pyproject.toml section excluding tool. prefix

drain_swamp.pep518_venvs.DICT_SEARCH_KEY: str = "venv_base_path"¶: In pyproject.toml section, key name. The value contains the venv relative path

class drain_swamp.pep518_venvs.VenvMap(loader, check_suffixes=('.in', '.unlock', '.lock'))¶

From pyproject.toml, read [[tool.venvs]] array of tables.

Each virtual environment should have a list of requirement files which maybe can recreate it.

The venv relative path and the requirements files relative paths are both posix. The top level requirements file paths are w/o suffix.

Complete example venvs and respective list of requirement files

[[tool.venvs]]
venv_base_path = '.doc/.venv'
in_folder = 'docs'
reqs = [
    'docs/pip-tools',
    'docs/requirements',
]
[[tool.venvs]]
venv_base_path = '.venv'
in_folder = 'requirements'
reqs = [
    'requirements/pip-tools',
    'requirements/pip',
    'requirements/prod.shared',
    'requirements/kit',
    'requirements/tox',
    'requirements/mypy',
    'requirements/manage',
    'requirements/dev',
]

In TOML format, paths MUST be single quoted.
Note lack of suffix.

There are three suffix per requirements: .in, .unlock, and .lock.
The venv folder should already exist.

The focus is on the requirements files, not what’s install within the virtual environment.
The requirements files should already exist.

As long as the .in files exist, to recreate .lock – pipenv-unlock lock .unlock – pipenv-unlock unlock

Variables:

_loader (drain_swamp.pep518_venvs.VenvMapLoader) – Contains some paths and loaded unparsed mappings
check_suffixes (tuple[str, ...]) – Default (“.in”, “.unlock”, “.lock”). Suffixes of requirements file to check exists and is file

_iter: collections.abc.Iterator[drain_swamp.pep518_venvs.VenvReq]¶: Package base folder absolute path

_venvs: list[drain_swamp.pep518_venvs.VenvReq]¶

key is virtual environment absolute path as_posix. Value is a list of absolute path to top level .in requirement files

To change suffix, use drain_swamp._safe_path.replace_suffixes()

_missing¶: Make missing requirements available. Then at a convenient time can provide feedback on missing requirements files

__slots__ = ("_loader", "_venvs", "_iter", "_missing")¶: Reduce memory footprint. Enhance performance

Raises:

TypeError – pyproject.toml file reverse search start path expecting Path
FileNotFoundError – pyproject.toml not found
LookupError – no [[tools.venvs]] TOML array of tables
NotADirectoryError – venv relative paths do not correspond to actual venv folders

ensure_abspath(key)¶

Convenience wrapper around VenvMapLoader method of the same name.

Parameters:: key¶ (str | pathlib.Path) – A relative or absolute path
Returns:: Absolute path
Return type:: pathlib.Path

property missing¶

During each iteration, check that requirement files exists is performed. The results are stored rather than raising exceptions.

Checks for existance of .in, .unlock and .lock files.

Does not check for .lnk

Returns:: venv
Return type:: list[str]

reqs(key)¶

For one venv, get requirements (.in).

Parameters:

key¶ (Any) – venv relative or absolute path

Returns:

One venv, VenvReq items

Return type:

list[drain_swamp.pep518_venvs.VenvReq]

Raises:

TypeError – venv relative path (as_posix) is a str key. Unsupported type
KeyError – No such venv found

class drain_swamp.pep518_venvs.VenvMapLoader(pyproject_toml_base_path: dataclasses.InitVar[str])¶

Load the pyproject.toml [[tool.venvs]] section

Variables:: pyproject_toml_base_path – Start path for the reverse search to find pyproject.toml file
Vartype:: str

project_base: pathlib.Path¶: Package base folder absolute path

pyproject_toml: pathlib.Path¶: pyproject.toml absolute path

l_data: collections.abc.Sequence[drain_swamp.monkey.pyproject_reading.TOML_RESULT]¶: TOML section [[tool.venvs]] are array of tables. Reading this produces a list of Mapping

ensure_abspath(key)¶

Support key being either relative or absolute path

Parameters:

key¶ (str | pathlib.Path) – venv path. Either relative or absolute path

Returns:

venv absolute Path

Return type:

pathlib.Path

Raises:

TypeError – unsupported type expecting str or pathlib.Path

static load_data(pyproject_toml_base_path)¶

From a path do a reverse search to find a pyproject.toml or a .pyproject_toml test file.

The venvs and venv’s requirements won’t change. Possible some files are missing. So the load process needs to only occur once.

Parameters:

pyproject_toml_base_path¶ – Start path for the reverse search to find pyproject.toml file

Type:

str

Returns:

TOML project and one section data along with a few paths

Return type:

tuple[collections.abc.Sequence[drain_swamp.monkey.pyproject_reading.TOML_RESULT], pathlib.Path, pathlib.Path]

Raises:

FileNotFoundError – pyproject.toml file reverse search start path expecting Path or file not found
LookupError – no [[tools.venvs]] TOML array of tables

parse_data(check_suffixes=('.in', '.unlock', '.lock'))¶

Take raw TOML section array of tables and parse.

Each datum is stored along with redundant metadata project_base and in_folder. :param _sphinx_paramlinks_drain_swamp.pep518_venvs.VenvMapLoader.parse_data.check_suffixes:

Default (“.in”, “.unlock”, “.lock”). Suffixes of requirements file to check exists and is file

Returns:

All VenvReq and missing files

Return type:

tuple[list[drain_swamp.pep518_venvs.VenvReq], list[str]]

Raises:

NotADirectoryError – venv relative paths do not correspond to actual venv folders
ValueError – expecting [[tool.venvs]] field reqs to be a sequence

pyproject_toml_base_path: dataclasses.InitVar[str]¶

property venv_relpaths¶

Get venvs’ relative path.

Supplements parse_data

Returns:: venvs’ relative path
Return type:: tuple[pathlib.Path]

class drain_swamp.pep518_venvs.VenvReq(project_base: Path, venv_relpath: str, req_relpath: str, req_folders: tuple[str])¶

Can always apply project_base to get the absolute Path

project_base: pathlib.Path¶: Absolute path to project base folder

venv_relpath: str¶: As sourced from TOML file a str (single quoted) relative path to venv base folder

req_relpath: str¶: As sourced from TOML file a str (single quoted) relative path to requirement file w/o (end) suffix: .in, .unlock, .lock. So a shared (between venv) requirement file, would be written requirements/prod.shared w/o the final suffix e.g. .in.

req_folders: tuple[str]¶: req folders relative path. Requirement files should not be outside these folders. Intentionally, cannot specify additional folders.

property is_req_shared¶

Check if requirement file suffix is .shared. Indicating requirement file is shared with multiple venv. And thus not an ideal place for nudge pins

Returns:: True if requirements file has a .shared suffix
Return type:: bool

property req_abspath¶

Get abspath for requirement. If lacks a .in append it

Stored in TOML file as a relative path (str).

Returns:: venv absolute Path
Return type:: pathlib.Path

reqs_all(suffix='.in')¶

Yields abspath to requirements files. The suffix filters by requirements file type

Parameters:: suffix¶ (str) – Specific requirements file type
Returns:: Generator of absolute path to requirement folders
Return type:: collections.abc.Generator[pathlib.Path, None, None]

property venv_abspath¶

Get abspath for venv.

Stored in TOML file as a relative path (str).

Returns:: venv absolute Path
Return type:: pathlib.Path

pep518 venvs¶

Navigation

Related Topics