Skip to main content

Typical: Take Typing Further.

Project description

Typical: Take Typing Further. :duck:

image

image image image image Test & Lint Coverage Code style: black Netlify Status

Take Typing Further with Typical. Make your annotations work for you.

Quickstart

In order to install, simply pip3 install typical and annotate to your heart's content! :duck:

Or, if you're building an application, you should use Poetry: poetry add typical

Updates

See the Changelog.

Documentation

See the full documentation Here.

Motivations

In the world of web-services development, type-safety becomes necessary for the sanity of your code and your fellow developers. This is not to say that static-typing is the solution - When it comes to the external entrypoints to your code, not even a compiler is going to help you.

With Python3, type annotations were introduced. With Python3.7, the library was completely re-written for performance and ease-of-use. Type annotations are here to stay and I couldn't be happier about it.

However, there is one place where annotations fall down. There is no provided path for ensuring the type-safety of your methods, functions, and classes. This means if you're receiving data from an external source, (such as with a web service) you still need to do this work yourself.

Until now.

Automatic, Guaranteed Duck-Typing

Behold, the power of Typical:

>>> import typic
>>>
>>> @typic.al
>>> def multi(a: int, b: int):
...    return a * b
...
>>> multi('2', '3')
6

Take it further...

>>> import dataclasses
>>> import enum
>>> import typic
>>>
>>> class DuckType(str, enum.Enum):
...     MAL = 'mallard'
...     BLK = 'black'
...     WHT = 'white'
... 
>>> @typic.al
... @dataclasses.dataclass
... class Duck:
...     type: DuckType
...     name: str
...
>>> donald = Duck('white', 'Donald')
>>> donald.type
<DuckType.WHT: 'white'>

This is all fine and dandy, but can we go... further? :thinking:

>>> class DuckRegistry:
...     """A Registry for all the ducks"""
...     
...     @typic.al
...     def __init__(self, *duck: Duck):
...         self._reg = {x.name: x for x in duck}
... 
...     @typic.al
...     def add(self, duck: Duck):
...         self._reg[duck.name] = duck
... 
...     @typic.al
...     def find(self, name: str):
...         """Try to find a duck by its name. Otherwise, try with type."""
...         if name not in self._reg:
...             matches = [x for x in self._reg.values() if x.type == name]
...             if matches:
...                 return matches[-1] if len(matches) == 1 else matches
...         return self._reg[name]
... 
>>> registry = DuckRegistry({'type': 'black', 'name': 'Daffy'})
>>> registry.find('Daffy')
Duck(type=<DuckType.BLK: 'black'>, name='Daffy')
>>> registry.add({'type': 'white', 'name': 'Donald'})
>>> registry.find('Donald')
Duck(type=<DuckType.WHT: 'white'>, name='Donald')

>>> registry.add({'type': 'goose', 'name': 'Maynard'})
Traceback (most recent call last):
 ...
ValueError: 'goose' is not a valid DuckType

What Just Happended Here?

When we wrap a callable with @typic.al, the wrapper reads the signature of the callable and automatically coerces the incoming data to the type which is annotated. This includes varargs (*args and **kwargs). This means that you no longer need to do the work of converting incoming data yourself. You just need to signal what you expect the data to be with an annotation and Typical will do the rest.

The ValueError we see in the last operation is what we can expect when attempting to supply an invalid value for the Enum class we used above. Rather than have to write code to cast this data and handle stuff that's invalid, you can rest easy in the guarantee that the data you expect is the data you'll get.

What's Supported?

As of this version, Typical can parse the following inputs into valid Python types and classes:

  • JSON
  • Python literals (via ast.literal_eval)
  • Date-strings and Unix Timestamps (via pendulum)
  • Custom NewType declarations.
  • and so much more...

Limitations

Forward Refs

A "forward reference" is a reference to a type which has either not yet been defined, or is not available within the module which the annotation lives. This is noted by encapsulating the annotation in quotes, e.g.: foo: 'str' = 'bar'. Beware of using such syntax in combination with Typical. Typical makes use of typing.get_type_hints, which scans the namespace(s) available to the given object to resolve annotations. If the annotation is unavailable, a NameError will be raised. This behavior is considered valid. If you wish to make use of Typical for type-coercion, make sure the annotated type is in the namespace of the object you're wrapping and avoid Forward References if at all possible.

Special Forms

There is a subset of type annotations which are 'suscriptable' - meaning you can specify what other types this annotation may resolve to. In a few of those cases, the intended type for the incoming data is too ambiguous to resolve. The following annotations are special forms which cannot be resolved:

  • Union
  • Any

Because these signal an unclear resolution, Typical will ignore this flavor of annotation, leaving it to the developer to determine the appropriate action.

How to Contribute

  1. This project is packaged and distributed with Poetry
  2. Check for open issues or open a fresh issue to start a discussion around a feature idea or a bug.
  3. Create a branch on Github for your issue or fork the repository on GitHub to start making your changes to the master branch.
  4. Write a test which shows that the bug was fixed or that the feature works as expected.
  5. Send a pull request and bug the maintainer until it gets merged and published. :)

Happy Typing :duck:

Project details


Release history Release notifications | RSS feed

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

typical-2.0.0b18.tar.gz (64.3 kB view details)

Uploaded Source

Built Distribution

typical-2.0.0b18-py3-none-any.whl (80.4 kB view details)

Uploaded Python 3

File details

Details for the file typical-2.0.0b18.tar.gz.

File metadata

  • Download URL: typical-2.0.0b18.tar.gz
  • Upload date:
  • Size: 64.3 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: poetry/1.0.2 CPython/3.7.6 Darwin/19.3.0

File hashes

Hashes for typical-2.0.0b18.tar.gz
Algorithm Hash digest
SHA256 fcf6a2011f0a1a0213450ee250106f20e92db223b8ad8c3a6083bc732be9a6d3
MD5 85f2409531c018d56ae7eef082219b4a
BLAKE2b-256 1dbae90640f3f33ab0a52c4ffd1bd7c28d53f45bcd734bf1c0a356c7fb80110b

See more details on using hashes here.

File details

Details for the file typical-2.0.0b18-py3-none-any.whl.

File metadata

  • Download URL: typical-2.0.0b18-py3-none-any.whl
  • Upload date:
  • Size: 80.4 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: poetry/1.0.2 CPython/3.7.6 Darwin/19.3.0

File hashes

Hashes for typical-2.0.0b18-py3-none-any.whl
Algorithm Hash digest
SHA256 c96d43a00d03583b6ee052a37c73c1f94dc0d4815a5874dd0671caa696838eeb
MD5 0baeb1294c8452297428c8eea2e045e2
BLAKE2b-256 c7906d244cf65611131307a856b998bd90c8c3e582967b6815208216264c0959

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page