pyscaffold / configupdater

96%

master: 97%

LAST BUILD ON BRANCH clear-remove-all

branch: clear-remove-all

CHANGE BRANCH

x

Reset

• clear-remove-all
• HEAD
• add-adopt-option-test
• add-fallback
• add-missing-type-hint
• add-py-typed
• add-type-hints
• api_token
• attach-container
• badges_template
• cleanup-insert
• deepcopy-option
• deepcopy-section
• deepcopy-toplevel
• dev
• fix-type-errors
• fix15
• fix_liskov
• fix_option
• fix_retval
• fix_setitem_in_document
• fix_type_errors
• improve-errors
• improve-optionxform-issue
• improve-validation-consistency
• issue-10
• issue-31
• issue-55
• issue-68
• link-missing
• main
• make-add-line-protected
• markdown-everywhere
• master
• mention-deepcopy-docs
• ml-comments
• modify-multiline-values
• pre-commit-ci-update-config
• psf-license
• pyscaffold-update
• pyscaffold-v4
• reorganise
• section_comment
• simplify-coverage
• type-improvements
• update-ci
• v0.1
• v0.1.1
• v0.2
• v0.3
• v0.3.1
• v0.3.2
• v0.3.2rc2
• v1.0
• v3.0
• v3.0.1
• v3.0rc1
• v3.0rc2
• v3.1
• v3.1.1
• v3.2
• v3.2b1
• work-on-optionxform
• workaround

Build # #218

Build Type

push

coveralls-python

Committed by abravalheri

Commit Message

Detach blocks when cleaning containers

Blocks hold a reference to their containers, so if someone for some
reason is keeping a reference to a block, it would be nice (for the sake
of consistency) to guarantee that block does not hold a reference to its
former container if that container is emptied via `.clear()`

There is another aspect: Python GC is based on reference counter... I
don't know if keeping references around in the blocks might interfere
with that also.

Run Details

243 of 261 branches covered (93.1%)

Branch coverage included in aggregate %.

708 of 725 relevant lines covered (97.66%)

0.98 hits per line