Repository navigation
Require pyTooling 10 for the example project - #332
Conversation
pyTooling 10.0.0 is released. The example packages 'myPackage' and 'myFramework.Extension' now require 'pyTooling >= 10.0.0, < 11.0' at runtime (requirements.txt) and for building (pyproject.toml's build-system), so the pipelines exercise the reusable workflows against the current pyTooling major version. 'setup.py' needs no change: it passes 'description' by name, and its extras contain no direct reference. Co-Authored-By: Patrick Lehmann <Paebbels@gmail.com>
doc/requirements.txt stopped including '../requirements.txt' because pyTooling.Sphinx requires pyTooling 10, which conflicted with the example's former 'pyTooling ~= 8.17'. Both require pyTooling 10 now, so the documentation installs the package's requirements again, like every other repository's doc/requirements.txt. Co-Authored-By: Patrick Lehmann <Paebbels@gmail.com>
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
| Duplication | 0 |
🟢 Coverage ∅ diff coverage
Metric Results Coverage variation Report missing for 3099dfc1 Diff coverage ✅ ∅ diff coverage Coverage variation details
Coverable lines Covered lines Coverage Common ancestor commit (3099dfc) Report Missing Report Missing Report Missing Head commit (d2b61a5) 41 38 92.68% Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch:
<coverage of head commit> - <coverage of common ancestor commit>Diff coverage details
Coverable lines Covered lines Diff coverage Pull request (#332) 0 0 ∅ (not applicable) Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified:
<covered lines added or modified>/<coverable lines added or modified> * 100%1 Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct.
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## dev #332 +/- ##
=======================================
Coverage 85.36% 85.36%
=======================================
Files 1 1
Lines 41 41
Branches 7 7
=======================================
Hits 35 35
Misses 3 3
Partials 3 3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Changes
myPackage,myFramework.Extension:requirements.txt) ispyTooling >= 10.0.0, < 11.0instead ofpyTooling ~= 8.17.pyproject.toml,[build-system] requires) ispyTooling >= 10.0.0, < 11.0instead ofpyTooling ~= 8.17, sosetup.pyis evaluated by pyTooling 10'sDescribePythonPackageHostedOnGitHub.setup.pyis unchanged: it passesdescriptionby name, and its only extra (test) contains no direct reference, so none of the v10pyTooling.Packagingbreaking changes applies.Documentation
doc/requirements.txtincludes../requirements.txtagain. It was dropped becausepyTooling.Sphinxrequires pyTooling 10, which conflicted with the formerpyTooling ~= 8.17. The comment explaining the conflict is removed.Others
artifact=myPackageandartifact=myFramework.Extension,python -m build --wheel --no-isolation); their metadata carriesRequires-Dist: pyTooling<11.0,>=10.0.0andLicense: Apache-2.0.tests/unit: 1 passed.tests/app(against the installedmyPackagewheel): 1 passed, 1 skipped (noartifacts_patternoutside a pipeline).tests/platform: 1 passed, 6 skipped (Windows only).pypiinComputePacboyPackagesstays: pyTooling 10.0.0 has nopypiextra (it isdependencies), butpyTooling.Sphinxstill requirespyTooling[pypi].Related Issues and Pull-Requests