diff options
| author | Silvan Mosberger <contact@infinisil.com> | 2020-09-04 13:18:22 +0200 |
|---|---|---|
| committer | Silvan Mosberger <contact@infinisil.com> | 2020-09-15 21:01:07 +0200 |
| commit | 67551f46fbc20b3b96ff27503b659a8f3fedb421 (patch) | |
| tree | 7c9727af4b245ab77eb83ec5025c7c532a246271 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 6e7bc2c6c90335e7bb7d7ca8cef77c58f0e37444 (diff) | |
lib/types: Introduce types.anything
This new type has unsurprising merge behavior: Only attribute sets are
merged together (recursively), and only if they don't conflict.
This is in contrast to the existing types:
- types.attrs is problematic because later definitions completely
override attributes of earlier definitions, and it doesn't support
mkIf and co.
- types.unspecified is very similar to types.attrs, but it has smart
merging behavior that often doesn't make sense, and it doesn't support
all types
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions