diff options
| author | Robert Hensing <robert@roberthensing.nl> | 2025-05-16 11:34:39 +0200 |
|---|---|---|
| committer | Robert Hensing <robert@roberthensing.nl> | 2025-05-16 11:52:36 +0200 |
| commit | 3dd811c4b9f7963a66a6cb17b4dbac5a7ce68a26 (patch) | |
| tree | 078c97a9ef0529a5c4043f28f844147569fe50e7 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 2f214a60411c2696033d64d8e4e6b757357c3519 (diff) | |
lib.types.attrNamesToTrue: unpublish temporarily
Thank you for making this change.
Unfortunately, and I take blame for this, this change to the module
system was not reviewed and approved by the module system maintainers.
I'm supportive of this change, but extending it on the staging-next
branch is not the right place.
This commit is also here to make sure that we don't run into conflicts
or other git trouble with the staging workflow.
Review:
It looks alright, but it didn't have tests yet, and it should be
considered in a broader context where the existence of this type
creates an incentive to be used in cases where the `<attr> = false;`
case is undesirable. I'd like to complement this with an type that
has `<attr> = {};` only.
My apologies for the lack of a timely and clear review. Often we
recommend to define the type outside the module system until
approved. This commit puts us back in that state.
attrNamesToTrue was introduced in 98652f9a901aac50c1d7780ea3507439803a3408
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions