CHANGES
v0.5.0 - 2012-09-10
Managing binary files (#2)
v0.4.0 - 2012-09-05
Add files param to check and diff commands
v0.3.3 - 2012-09-03
Fix getting files for git1.5
v0.3.2 - 2012-09-02
Managing right untracked files
v0.3.1 - 2012-09-02
Checking local untracked files if they are in remote branch.
v0.3.0 - 2012-09-02
Let get_diff without arguments. Gets all current diff.
Adding fetch, checkout, merge, apply_diff, apply_patch to git object.
Adding header_diff, write_tmp_patches and write_tmp_patch to diff module.
Fix newline for chunks in get_chunks()
v0.2.0 - 2012-08-28
- Added –diff option to check command. By default check command only will
print the files ok or failed. If –diff flag is enabled it will show the diff.
Added diff command to get the diff of files that doesn’t apply for use when merge is done.
Metadata
Release files for cutools 0.5.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 |
|---|---|---|---|---|
| cutools-0.5.0.tar.gz | 5.2 kB | Without provenance | Details for cutools-0.5.0.tar.gz |
Release files / cutools-0.5.0.tar.gz
| Download URL | cutools-0.5.0.tar.gz |
|---|---|
| Size | 5.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9b951808a6086634a980d504dbca5e5d37a4bae55d6c8dc107000a596792ff05
|
|
BLAKE2b-256 checksum How to use checksums |
2dcce1e6e1c4f8a653c3a0d6477642d204769de7d546e6a987a02bc5b2916401
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for cutools 0.5.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.