I would add that this seems to me like something you need.
So be all means write it, document it, maybe publish it on PyPi, and then, if it does seem to be generally useful, propose it for the stdlib.
In fact, if something like this were to be included in the stdlib, we’d probably want a back-port on PyPi anyway.
Meanwhile, a few thoughts:
1) it likely makes sense to support Mappings and Iterables, rather than specific types. Though special casing strings, as they are usually treated at atomic in this context.
2) you talk about a use case of flattening to be subset checking. This strikes me as a special case that will require a custom class ( or functions) In particular, how do you deal with dict ordering?
3) is there really no existing JSON-LD lib for Python? Or not a good one? If so, then that’s clearly a package for PyPi, and maybe you’ll discover whether this flattening function is generally useful after it’s been battle tested.
I for one, am interested. I’ve got a system built of nested Dataclasses that serialize to/from JSON compatible nested dicts and lists.
This traversing/flattening functionality could be quite useful.
Maybe your examples aren't making it clear what you're suggesting,
then. I'm in agreement with Chris, your "nested iteration tool" sounds
like something that would have so many configuration options and
parameters that it would be harder to use than traversing "by hand".
But maybe you imagine something simpler than I do. Again, can I
suggest you post what you imagine the user documentation for the
function would look like, and then we'll be able to stop
misunderstanding each other?
On Wed, 21 Jul 2021 at 16:29, Sven Voigt <email@example.com> wrote:
> I could say the same thing about JSON dumps then and most itertools functions. The proposed functionality is in line with existing functionality and extends it to the case of nested data structures.
> On Wed, Jul 21, 2021 at 11:25 AM Chris Angelico <firstname.lastname@example.org> wrote:
>> On Thu, Jul 22, 2021 at 1:14 AM Sven Voigt <email@example.com> wrote:
>> > Paul,
>> > I agree that the mapping to a flat data structure might have limited use cases. However, like you said it is only one example. What I am proposing is a nested iteration tool that can map both keys and values to new keys and new values. It only considers nesting in dictionaries, lists, and tuples by default, but allows users to pass another function to continue searching for pointers in other types.
>> This sounds like the sort of thing that's best coded up specifically
>> to your purposes. There'll be myriad small variants of this kind of
>> traversal, so it's easiest to just write the thing you want, rather
>> than try to get the standard library to support every variant.
>> Python-ideas mailing list -- firstname.lastname@example.org
>> To unsubscribe send an email to email@example.com
>> Message archived at https://firstname.lastname@example.org/message/2IOA23Z33434YWPTQWDPMA5RGJBCPCRZ/
>> Code of Conduct: http://python.org/psf/codeofconduct/
> Python-ideas mailing list -- email@example.com
> To unsubscribe send an email to firstname.lastname@example.org
> Message archived at https://email@example.com/message/BRWPYXYXOFJAY7FKEGTFZO5T7XKBSCZ3/
> Code of Conduct: http://python.org/psf/codeofconduct/
Python-ideas mailing list -- firstname.lastname@example.org
To unsubscribe send an email to email@example.com
Message archived at https://firstname.lastname@example.org/message/UR52XKA2I6AWKCELIDODF5IVBHMHBBW7/
Code of Conduct: http://python.org/psf/codeofconduct/
Christopher Barker, PhD (Chris)
Python Language Consulting
- Scientific Software Development
- Desktop GUI and Web Development
- wxPython, numpy, scipy, Cython