pyscaffold / configupdater

97%

master: 97%

LAST BUILD ON BRANCH cleanup-insert

branch: cleanup-insert

CHANGE BRANCH

x

Reset

• cleanup-insert
• HEAD
• add-adopt-option-test
• add-fallback
• add-missing-type-hint
• add-py-typed
• add-type-hints
• api_token
• attach-container
• badges_template
• clear-remove-all
• 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 # #200

Build Type

push

coveralls-python

Committed by FlorianWilhelm

Commit Message

Add PSF license and not about derivative work

After doing the research for
https://github.com/pyscaffold/pyscaffold/discussions/459,
I came across Django's license files
(https://github.com/django/django/blob/main/LICENSE.python)
that reference parts of Python (I suppose stdlib) being
included/modified in the project.

This commit borrows the same idea (and the variation implemented in
PyScaffold's own repo for the 0BSD templates) in an attempt to clarify
it follows the PSF redistribution requirements.

Run Details

234 of 251 branches covered (93.23%)

Branch coverage included in aggregate %.

686 of 702 relevant lines covered (97.72%)

0.98 hits per line