cs-deco

Assorted decorator functions.

Function `cached(*da, **dkw)`

Decorator to cache the result of a method and keep a revision counter for changes.

The cached values are stored on the instance (self). The revision counter supports the @revised decorator.

This decorator may be used in 2 modes. Directly:

@cached
def method(self, ...)

or indirectly:

@cached(poll_delay=0.25)
def method(self, ...)

Optional keyword arguments:

attr_name: the basis name for the supporting attributes. Default: the name of the method.
poll_delay: minimum time between polls; after the first access, subsequent accesses before the poll_delay has elapsed will return the cached value. Default: None, meaning no poll delay.
sig_func: a signature function, which should be significantly cheaper than the method. If the signature is unchanged, the cached value will be returned. The signature function expects the instance (self) as its first parameter. Default: None, meaning no signature function; the first computed value will be kept and never updated.
unset_value: the value to return before the method has been called successfully. Default: None.

If the method raises an exception, this will be logged and the method will return the previously cached value, unless there is not yet a cached value in which case the exception will raise.

If the signature function raises an exception then a log message is issued and the signature is considered unchanged.

An example use of this decorator might be to keep a "live" configuration data structure, parsed from a configuration file which might be modified after the program starts. One might provide a signature function which called os.stat() on the file to check for changes before invoking a full read and parse of the file.

Function `decorator(deco)`

Wrapper for decorator functions to support optional keyword arguments.

Examples:

@decorator
def dec(func, **dkw):
  ...
@dec
def func1(...):
  ...
@dec(foo='bah')
def func2(...):
  ...

Function `strable(*da, **dkw)`

Decorator for functions which may accept a str instead of their core type.

Parameters:

func: the function to decorate
open_func: the "open" factory to produce the core type form the string if a string is provided; the default is the builtin "open" function

The usual (and default) example is a function to process an open file, designed to be handed a file object but which may be called with a filename. If the first argument is a str then that file is opened and the function called with the open file.

Examples:

@strable
def count_lines(f):
  return len(line for line in f)

class Recording:
  "Class representing a video recording."
  ...
@strable
def process_video(r, open_func=Recording):
  ... do stuff with `r` as a Recording instance ...

Metadata

Release files for cs-deco 20190309

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for cs-deco 20190309
File	Size	Uploaded	Provenance
cs.deco-20190309.tar.gz	4.6 kB	Mar 9, 2019	Without provenance	Details

Release files / cs.deco-20190309.tar.gz

Download URL	cs.deco-20190309.tar.gz
Size	4.6 kB
Tags	Source
SHA-256 checksum How to use checksums	`c68ad0a7bb8f7625ec9cf9c13de156e1e66e04cbd2c846606074126fe2bffb4a`
BLAKE2b-256 checksum How to use checksums	`cf8d03a1d71448def9d4260ba933a4583b84e201aeebdacb31260952797c1e7e`
Upload date	Mar 9, 2019
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/1.11.0 pkginfo/1.4.2 requests/2.18.4 setuptools/40.0.0 requests-toolbelt/0.8.0 tqdm/4.23.0 CPython/3.6.8`

Security for cs-deco 20190309

Report project as malware

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.