metaist / attrbox Goto Github PK

Currently AttrDict.set cannot support traversal across a list. Also AttrList should support a .get and .set with the same semantics.

Use .get with a sentinel object as default to detect if the key exists.

• .github/workflows/ci.yaml
• .github/workflows/codeql.yml
• .github/workflows/pypi.yaml
• .github/FUNDING.yml
• docs
• .cspell.json
• .editorconfig
• .gitattributes
• .gitignore
• CHANGELOG.md
• CONTRIBUTING.md
• LICENSE.md
• pyproject.toml
• README.md
• mascot

I thought I disagreed with the advice from PEP 8, but turns out I don't.

This would allow ${section.key} expansions for {"section": {"key": 5}}.

This is increasingly necessary for, e.g., #12

@Pugio has often talked about having a nice functional wrapper (ala ruby) in a python context. My first attempt at this failed because I was trying to stick to the existing type system. Let's see if we can do better by just making a wrapper object.

constructors

• __init__
• copy
• wrap
• fromkeys

contents

• __repr__
• __len__
• __contains__
• __iter__
• __eq__
• keys
• values
• items
• attr
• count
• get

select

• first
• last
• take
• drop
• uniq
• filter
• index

apply

• map
• reduce
• each
• group

format

• sort
• reverse
• compact
• flatten
• zip
• join

add

• push
• append
• concat
• extend
• insert
• setdefault
• __add__
• __iadd__

remove

• pop
• popitem
• delete
• remove
• clear

modify

• update
• __imul__
• __rmul__

I only want the most-used classes and functions at the top-most level. Everything else can be accessed more directly, if needed, but I don't want to pollute the namespace.

Currently, config values are loaded before CLI arguments (argv), which is correct. Except that CLI arguments also include default values. Which means that default values are superseding config values.

The order I'd like (later values winning):

• default values
• config values
• CLI arguments

But this implies that we need to know which of the docopt values are default and which happen to have the same value as the default.