Welcome to spuring documentation
Spuring creates predefined folder setups. It is mainly mend to be a project folder scaffolder for python projects, but thanks to the template ans plugin system you can customize it for your needs.
Install
py -m pip install spruing
How to use it
Help
spruing -h
shows a list commands
List Templates
spruing -l
list all templates that are in your template folder (more later)
Create a Template
spruing -t default -o MyProject
Creates the content of the default template in the folder MyProject.
This will create the following folder tree
│─── README.md
│─── requirements-dev.txt
├─── .venv
├─── MyProject
│ __init__.py
└─── test
TestMyproject.py
You only can just start the virtual environment and start coding. All the packages in the requirements-dev.txt already downloaded and ready to use.
Find the template folder
As i said, you can customize your own template.
First thinks first. Lets locate the template folder.
Type the following in you terminal
spuring -tp
The result should be on windows like that
C:\Users\%user%\AppData\Local\Programs\Python\Python3%$\Lib\site-packages\spuring\templates
For later - You will found the plugin folder (here named "scripts") on the parent directory.
C:\Users\%user%\AppData\Local\Programs\Python\Python3%$\Lib\site-packages\spuring\scripts
Create a simple template
There are 4 main sections for a template. Lets create a toml file and lets right the "head" section.
# The name for your template
name = "my_template"
# a short description.
description = "A project setup that i like"
# In the narrative you can write a little bit more, so that you know late what going on.
narrative = "I use a src folder. It's much better!"
That was the first part. Now lets dive in the second section. Its the folder section.
# Here can you list all folders
# now we start with the folder flag. That wasn't needed in the first section
[folders]
# the name of the key isn't important
src = "src"
# you can create multi layers
test = "test/test-reports"
Just start the section with [folders].
After that choose any key, it is not important for the creation of the project file. Only double occurrence play a role. This could be important if you work with more advance stuff. But now low go forward to the files. Now it will be interesting.
Metadata
Release files for spuring 0.0.4
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 |
|---|---|---|---|---|
| spuring-0.0.4.tar.gz | 8.5 kB | Without provenance | Details for spuring-0.0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| spuring-0.0.4-py3-none-any.whl | Python 3 | none | any | Details for spuring-0.0.4-py3-none-any.whl |
Total release size: 17.3 kB
Release files / spuring-0.0.4.tar.gz
| Download URL | spuring-0.0.4.tar.gz |
|---|---|
| Size | 8.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ec32b1da13df62e659ff57966c9ef03ef1769194390e8eb72a313b0f091f68b7
|
|
BLAKE2b-256 checksum How to use checksums |
cacd745a5dc9d335c966d68edb6dc9658ce1b7def8e589aa6740ad2ef4f9a14d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.0
|
Release files / spuring-0.0.4-py3-none-any.whl
| Download URL | spuring-0.0.4-py3-none-any.whl |
|---|---|
| Size | 8.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
df9ade0784cb3db49b0991ecd693962e51b6f53c6fd150ecfef9f923fa597005
|
|
BLAKE2b-256 checksum How to use checksums |
338128815dd577829eb048ca493a196c7106b0720710f196913a20cb7ecefebc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.0
|
Security for spuring 0.0.4
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.