pyisotools
python library for working with Gamecube ISOs (GCM)
Features
- Extract and Build ISOs
- Extract individual files/folders from an ISO
- Specifically exclude subfolders/files using glob patterns
- Custom file alignment
- Custom file location
- Custom ISO metadata
Limitations
- Only supports Gamecube ISOs
TODO
- Support Wii ISOs
- ISO Partitions
- Native archive support (U8 and RARC)
- Native yaz0 and yay0 compression
- Cross platform file drag-drop to/from pyisotools
- File System real time search filter
- File System update real time
Usage
GUI
To run the GUI from the cli, simply pass: python -m pyisotools
Extraction
To extract an ISO from the cli, pass: python -m pyisotools <iso> E [--dest path]
Rebuilding
To build a root folder into an iso, pass: python -m pyisotools <root> B [--newinfo] [--dest path]
Configuration (rebuilding from cli)
When an ISO is extracted, a file named .config.json is automatically generated and stored in the sys folder in the root directory. This file contains metadata about the ISO, such as the name of the game, its version, maker code, and so on. Editing this file results in the new data being used if rebuilding with option --newinfo enabled. The fields that need clairification are listed below:
- Alignment: This field of
key,valuepairs defines the alignment of every file that matches the specified glob pattern set as thekey, to be that of thevalue - Location: This field of
key,valuepairs defines the position in the ISO of every file that matches the specified filepath set as thekey, to be that of thevalue - Exclude: This list of glob patterns determines if a file/folder is excluded or not. If a file/folder path matches any of the glob patterns in the list, it will not be built into the ISO
Configuration (GUI)
When a root is loaded, all metadata fields are accessible directly from the main window, and each node can be right clicked on to set the alignment, location, and exclude members
Metadata
Release files for pyisotools 2.4.7
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 |
|---|---|---|---|---|
| pyisotools-2.4.7.tar.gz | 180.6 kB | Without provenance | Details for pyisotools-2.4.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyisotools-2.4.7-py3-none-any.whl | Python 3 | none | any | Details for pyisotools-2.4.7-py3-none-any.whl |
Total release size: 374.5 kB
Release files / pyisotools-2.4.7.tar.gz
| Download URL | pyisotools-2.4.7.tar.gz |
|---|---|
| Size | 180.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2f6dba5ca2004c11eb3b9c4ef3afdab4349beff4195b05fb8dce2a122456a416
|
|
BLAKE2b-256 checksum How to use checksums |
2d336df279d183d4a8bc493df784ea66ad773d2e321076ac78a2ec52678d51b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.12.3
|
Release files / pyisotools-2.4.7-py3-none-any.whl
| Download URL | pyisotools-2.4.7-py3-none-any.whl |
|---|---|
| Size | 193.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
32773d11fe62543dc881be355ac5dd59621aee38215ff8e4635217ff5f0cfa25
|
|
BLAKE2b-256 checksum How to use checksums |
3d4b54d4d7a77356491586ae9c119493f5860e083c6747e9ed88ea6a1d10824b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.12.3
|
Security for pyisotools 2.4.7
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.