skeletonize
Handles skeletonization and deskeletonizaiton of programs. This allows for easily distributing assignments to students that contain skeleton code, and determining which parts of the skeleton they filled in after the fact, extracting blanks.
skeletonization
Skeletonization works by taking in a piece of code with "skeleton markers" as so:
def factorial(x):
if <<<x == 0>>>:
return <<<1>>>
else:
return <<<x>>> * <<<factorial(x - 1)>>>
and converting it into either a skeleton
def factorial(x):
if ______:
return ______
else:
return ______ * ______
or a solution
def factorial(x):
if x == 0:
return 1
else:
return x * factorial(x - 1)
reskeletonization
Reskeletonization works by taking a skeleton:
def factorial(x):
if <<<x == 0>>>:
return <<<1>>>
else:
return <<<x>>> * <<<factorial(x - 1)>>>
and a student solution:
def factorial(x):
if not x:
return 1
else:
return x * factorial(x)
and produces a reskeletonized program
def factorial(x):
if <<<not x>>>:
return <<<1>>>
else:
return <<<x>>> * <<<factorial(x)>>>
Metadata
Release files for skeletonize 2.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| skeletonize-2.8.tar.gz | 6.0 kB | Without provenance | Details for skeletonize-2.8.tar.gz |
Release files / skeletonize-2.8.tar.gz
| Download URL | skeletonize-2.8.tar.gz |
|---|---|
| Size | 6.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
662ea8b56e2505cfb19f4733c1a8709f87fa10104e3ac4ee5529b2abcef2329c
|
|
BLAKE2b-256 checksum How to use checksums |
4b608809ccbb04e816f8ea18b4172bfe907a8144918ca05a4a4b648180a6ff51
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.4.0 requests-toolbelt/0.9.1 tqdm/4.47.0 CPython/3.7.4
|
Security for skeletonize 2.8
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.