Python 3 project development tools. Looks like a turtle, tastes like chicken.
Chicken Turtle Project (CTP) provides CLI tools for developing Python 3 projects. It makes it easier to make quality commits and releases, through automating what can be automated and by verifying manual work against quality requirements.
Chicken Turtle Project is alpha. The interface may change in the future, but has gained some stability.
Links
Changelist
v2.3.0
Fixed:
ct-mkvenv did not upgrade pip, wheel and setuptools
git pre-commit hook did not enter venv properly when running tests
added missing numpy requirement, an optional dependency of networkx
`requirements.in`: dependencies on extra requires (e.g. dependency[extra]) failed
Optimised:
ct-mkvenv reruns are faster
Added or enhanced:
when CT_NO_MKPROJECT environment variable is set, ct-mkproject will exit immediately when called.
–debug option: more detailed messages on stdout.
minimise changes in setup.py and requirements.txt (by sorting any lists)
Changed:
Terser and more readable messages on stdout
Generate API using autosummary_generate instead of sphinx-apidoc.
if pip, wheel or setuptools is mentioned in a requirements.in file, it will also appear in requirements.txt, for the rare cases where you need to constrain one of them.
ct-mkvenv: dependencies no longer installed in the order they are specified in requirements.txt
Removed:
ct-mkvenv --no-mkproject: instead, use CT_NO_MKPROJECT=y ct-mkvenv.
v2.2.0
Changed: user friendlier error messages
Added:
project.py::python_version: allows specifying which Python version to use for the venv and testing
ct-mkvenv --no-mkproject: run without first calling ct-mkproject
Fixed: the project’s package was missing from venv after each commit. The venv wasn’t restored properly after a pre-commit.
v2.1.2
Changed: expect tests in your_pkg.tests instead of your_pkg.test
Added:
project.py::package_name: allows package name and PyPI/index name to be different
project.py::pre_commit_no_ignore: files not to ignore in precommit checks, despite them not being tracked by git.
v2.0.4
No changelist
1 maintainer
Metadata
1 maintainer
Release files for chicken_turtle_project 2.3.0
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 |
|---|---|---|---|---|
| chicken_turtle_project-2.3.0.tar.gz | 47.0 kB | Without provenance | Details for chicken_turtle_project-2.3.0.tar.gz |
Release files / chicken_turtle_project-2.3.0.tar.gz
| Download URL | chicken_turtle_project-2.3.0.tar.gz |
|---|---|
| Size | 47.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
685cf806f5ad3042da1085a1a347e9f6df81327c9266adcaa91c58221c78ba46
|
|
BLAKE2b-256 checksum How to use checksums |
db695ec0982027c323309b9ebbc88716b72ed3c5f14be07fa846e336dd8e4b3c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for chicken_turtle_project 2.3.0
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.
