rez.package_filter#

class rez.package_filter.PackageFilter#

A package filter.

A package filter is a set of rules that hides some packages but leaves others visible. For example, a package filter might be used to hide all packages whos version ends in the string ‘.beta’. A package filter might also be used simply to act as a blacklist, hiding some specific packages that are known to be problematic.

Rules can be added as ‘exclusion’ or ‘inclusion’ rules. A package is only excluded iff it matches one or more exclusion rules, and does not match any inclusion rules.

__init__()#

excludes(package)#

Determine if the filter excludes the given package.

Parameters:: package (Package) – Package to filter.
Returns:: Rule object that excludes the package, or None if the package was not excluded.

add_exclusion(rule)#

Add an exclusion rule.

Parameters:: rule (Rule) – Rule to exclude on.

add_inclusion(rule)#

Add an inclusion rule.

Parameters:: rule (Rule) – Rule to include on.

copy()#

Return a shallow copy of the filter.

Adding rules to the copy will not alter the source.

cost()#

Get the approximate cost of this filter.

Cost is the total cost of the exclusion rules in this filter. The cost of family-specific filters is divided by 10.

Returns:: The approximate cost of the filter.
Return type:: float

classmethod from_pod(data)#: Convert from POD types to equivalent package filter.

to_pod()#: Convert to POD type, suitable for storing in an rxt file.

class rez.package_filter.PackageFilterList#

A list of package filters.

A package is excluded by a filter list iff any filter within the list excludes it.

__init__()#

add_filter(package_filter)#

Add a filter to the list.

Parameters:: package_filter (PackageFilter) – Filter to add.

add_exclusion(rule)#

Add an exclusion rule.

Parameters:: rule (Rule) – Rule to exclude on.

add_inclusion(rule)#: Note

Adding an inclusion to a filter list applies that inclusion across all filters.

excludes(package)#

Determine if the filter excludes the given package.

Parameters:: package (Package) – Package to filter.
Returns:: Rule object that excludes the package, or None if the package was not excluded.

copy()#

Return a copy of the filter list.

Adding rules to the copy will not alter the source.

classmethod from_pod(data)#: Convert from POD types to equivalent package filter.

to_pod()#: Convert to POD type, suitable for storing in an rxt file.

class rez.package_filter.RegexRule#

A rule that matches a package if its qualified name matches a regex string.

For example, the package ‘foo-1.beta’ would match the regex rule ‘.*.beta$’.

name = 'regex'#: Relative cost of rule - cheaper rules are checked first.

__init__(s)#

Create a regex rule.

Parameters:: s (str) – Regex pattern. Eg ‘.*.beta$’.

class rez.package_filter.GlobRule#

A rule that matches a package if its qualified name matches a glob string.

For example, the package ‘foo-1.2’ would match the glob rule ‘foo-*’.

name = 'glob'#: Relative cost of rule - cheaper rules are checked first.

__init__(s)#

Create a glob rule.

Parameters:: s (str) – Glob pattern. Eg ‘foo.*’, ‘*.beta’.

class rez.package_filter.RangeRule#

A rule that matches a package if that package does not conflict with a given requirement.

For example, the package ‘foo-1.2’ would match the requirement rule ‘foo<10’.

name = 'range'#: Relative cost of rule - cheaper rules are checked first.

__init__(requirement)#

match(package)#

Apply the rule to the package.

Parameters:: package (Package) – Package to filter.
Returns:: True if the package matches the filter, False otherwise.
Return type:: bool

cost()#: Relative cost of filter. Cheaper filters are applied first.

class rez.package_filter.TimestampRule#

A rule that matches a package if that package was released before the given timestamp.

Note

The ‘timestamp’ argument used for resolves is ANDed with any package filters - providing a filter containing timestamp rules does not override the value of ‘timestamp’.

Note

Do NOT use a timestamp rule to mimic what the ‘timestamp’ resolve argument does. ‘timestamp’ is treated differently - the memcache caching system is aware of it, so timestamped resolves get cached. Non-timestamped resolves also get cached, but their cache entries are invalidated more often (when new packages are released).

There is still a legitimate case to use a global timestamp rule though. You might want to ignore all packages released after time X, except for some specific packages that you want to let through. To do this you would create a package filter containing a timestamp rule with family=None, and other family-specific timestamp rules to override that.

name = 'timestamp'#: Relative cost of rule - cheaper rules are checked first.

__init__(timestamp, family=None, reverse=False, match_untimestamped=False)#

Create a timestamp rule.

Parameters:

timestamp (int) – Epoch time.
family (str) – Package family to apply the rule to.
reverse (bool) – If True, reverse the logic so that packages released after the timestamp are matched.
match_untimestamped (bool) – Defines behaviour on non-timestamped packages.

match(package)#

Apply the rule to the package.

Parameters:: package (Package) – Package to filter.
Returns:: True if the package matches the filter, False otherwise.
Return type:: bool

cost()#: Relative cost of filter. Cheaper filters are applied first.