rename-kicad-project
rename-kicad-project is a nifty tool for renaming or cloning your KiCad (v4, v5) project.
NOTE: From KiCad v6, renaming/cloning has been officially supported. Try File -> Save As....
Install
python3 -m pip install --user rename-kicad-project
Or with pipx,
pipx install rename-kicad-project
Usage
# Show helps
rename-kicad-project --help
# Show helps of `rename` sub-command (see below)
rename-kicad-project rename --help
Or you can invoke this tool by
python3 -m rename_kicad_project --help
rename
In the following example, ../foo/old_project_name{.pro, .sch, ...} will be renamed as ../foo/new_project_name.pro, ..., respectively.
rename-kicad-project rename ../foo new_project_name
# ls ../foo
# new_project_name.pro new_project_name.sch, ...
You may want to run the command above with --dry-run (-n) beforehand;
rename-kicad-project -n rename ../foo new_project_name
# Renaming: /path/to/old_project_name.kicad_pcb as new_project_name.kicad_pcb
# ...
clone
In the following example, ./foo/old_project_name{.pro, .sch, ...} will be cloned into /tmp/bar/new_project_name.pro, ..., respectively.
rename-kicad-project clone ./foo /tmp/bar -p new_project_name
# ls /tmp/bar
# new_project_name.pro new_project_name.sch, ...
You can omit -p to let the tool infer the new project name like /tmp/bar/bar.pro.
rename-kicad-project clone ./foo /tmp/bar
# ls /tmp/bar
# bar.pro bar.sch, ...
Note that /tmp/bar will be automatically created if it doesn't exist.
And as you expected, --dry-run also works with clone.
How it works
For the folks who wouldn't want to rely on someone's script, here is a basic explanation of how this tool works;
- In the given source directory, glob
*.profiles and based on the first found one, determine the current project name. (${PROJECT_NAME}.pro) - Determine target files with globbing
${PROJECT_NAME}.*and including some special files likefp-lib-table. - Rename the target files in place (
rename) or copy the files into the specified destination (clone). That' it!
License
MIT
Alternatives
- https://github.com/bobc/KiRename
- As of 2021-12, it only runs on Python 2.
Metadata
Release files for rename-kicad-project 1.1.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 | |
|---|---|---|---|---|
| rename_kicad_project-1.1.0.tar.gz | 5.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rename_kicad_project-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.0 kB
Release files / rename_kicad_project-1.1.0.tar.gz
| Download URL | rename_kicad_project-1.1.0.tar.gz |
|---|---|
| Size | 5.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f0d925f8fb8b7097b889f709e7fbbe6953278e34addbccaeb15f7faa71b30188
|
|
BLAKE2b-256 checksum How to use checksums |
8a7f3374fe28f1843f94e5200f9470c44e56f7c3daf00a7baf005775c542ebd3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.3.2 CPython/3.7.15 Linux/5.15.0-1031-azure
|
Release files / rename_kicad_project-1.1.0-py3-none-any.whl
| Download URL | rename_kicad_project-1.1.0-py3-none-any.whl |
|---|---|
| Size | 6.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
89b48ef05965efa26f6ebb0419c3c73c6eaafef744dda2801ad74efb80018ec7
|
|
BLAKE2b-256 checksum How to use checksums |
6da82de534f7faedd4532460f722025771c1e96557745f30e3f35db295e2c581
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.3.2 CPython/3.7.15 Linux/5.15.0-1031-azure
|
Security for rename-kicad-project 1.1.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.