diff options
| author | Silvan Mosberger <contact@infinisil.com> | 2023-08-10 06:25:29 +0200 |
|---|---|---|
| committer | Silvan Mosberger <contact@infinisil.com> | 2023-08-10 06:25:29 +0200 |
| commit | 040b0ad3ed13cfe1dfec4f05d7e9c92c84dd6928 (patch) | |
| tree | d189312c1182de730e37bc153816ae0b4c408b07 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | ec8866254a2a4296cd11cedc109f728ac6539a8e (diff) | |
Revert "lib.types.string: Deprecation error instead of warning"
This reverts commit c59c6b1c57da542b6b4af5d2ac27d1b99e7f0c5e.
This was a bit too ambitious, because no warnings were previously
triggered when `string` was nested e.g. `attrsOf string`, `nullOr
string`, etc.
Support for nested type deprecation warnings was introduced in
4b54aedee5e05aaf2838f6d951508b83e33d2baa, but had to be reverted in
a36e6760e9be0ec260b637a06d751d39e2a78e4e because it caused infinite
recursion for some users, and I couldn't remember that it was reverted.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions