tahoe-lafs/integration/vectors/__init__.py

__all__ = [
    "DATA_PATH",
    "CURRENT_VERSION",
    "MAX_SHARES",

    "Case",
    "Sample",
    "SeedParam",
    "encode_bytes",
    "save_capabilities",

    "capabilities",
]

from .vectors import (
    DATA_PATH,
    CURRENT_VERSION,

    Case,
    Sample,
    SeedParam,
    encode_bytes,
    save_capabilities,

    capabilities,
)

from .parameters import (
    MAX_SHARES,
)
Some flake fixes 2023-01-17 08:41:10 -05:00			`__all__ = [`
			`"DATA_PATH",`
			`"CURRENT_VERSION",`
			`"MAX_SHARES",`

			`"Case",`
			`"Sample",`
			`"SeedParam",`
			`"encode_bytes",`
advertise all the names 2023-01-20 19:50:57 -05:00			`"save_capabilities",`
Some flake fixes 2023-01-17 08:41:10 -05:00
			`"capabilities",`
			`]`

Move some more pieces into the subdirectory 2023-01-16 16:01:11 -05:00			`from .vectors import (`
			`DATA_PATH,`
			`CURRENT_VERSION,`

			`Case,`
			`Sample,`
			`SeedParam,`
			`encode_bytes,`
expose the persistence api 2023-01-20 16:27:05 -05:00			`save_capabilities,`
Move some more pieces into the subdirectory 2023-01-16 16:01:11 -05:00
			`capabilities,`
			`)`
Factor more infrastructure code out of the test module Test vector saving implementation can go near loading implementation. Also we can separate out some simple types from the more complex logic. Initially this was to resolve a circular dependency but that ended up being resolved mostly by treatming SEGMENT_SIZE more like a parameter than a global. Still, smaller modules are okay... 2023-01-18 13:52:11 -05:00
			`from .parameters import (`
			`MAX_SHARES,`
			`)`