====
Simple Individual Line Preprocessor
Blog post about what is SILP and why I want to create it.
- http://blog.yjpark.org/blog/2014/04/12/silp-simple-individual-line-preprocessor/
Notes
=====
following the best practice from this article:
- http://www.jeffknupp.com/blog/2013/08/16/open-sourcing-a-python-project-the-right-way/
Language list for better .md rendering
- https://github.com/github/linguist/blob/master/lib/linguist/languages.yml
0.3.11
------
Bugfix with nested rules' param values
0.3.10
------
Support nested rules inside template.
0.3.9
-----
Bugfix with term refactoring
0.3.8
-----
Bugfix load module from ~/.silp_plugins
Add csproj file
0.3.7
-----
Try load module from ~/.silp_plugins
0.3.6
-----
Remove blessings usage under windows, can work under windows now (only test with git windows' bash)
0.3.5
-----
Put the `.silp_backup` and `.silp_test` folders under `~`, otherwise they may became garbage in project folder
0.3.4
-----
Make sure there is at least one space before the suffix
use " --SILP:" for sql
0.3.3
-----
Add SQL to language list
- Use "/*__SILP__*/" for the generated tag, since in MySql if using
"--__SILP__", then if there is one line without space there is a
corner case that there is no space before it.
https://dev.mysql.com/doc/refman/5.1/en/ansi-diff-comments.html
0.3.2
-----
Use "%" instead of "%%" in erlang language
0.3.1
-----
Add simple plugin support for more complex macro.
- Currently plugins should be put under project's silp_plugins
(Project means the folder holding silp_xx.md)
- plugin macro has format as module:func(param1, param2, ...)
module here is the name of the python plugin, func is the name of
function
- also expose silp.error/info/verbose, then the plugin codes can print
debug information with them.
Add support for Erlang (both erl, and hrl)
0.2.5
-----
Add support for YML launguage
0.2.4
-----
Fix the wrong `import silp` in setup.py which breaks the dependencies installation.
- https://github.com/yjpark/silp/issues/1
- Thanks for lowks for the comment: https://github.com/lowks
0.2.3
-----
### --clean
Add `--clean` parameter to remove silp generated lines, usefel if want
to change the language settings
### include other files in template
The syntax is something like:
```
<<[fish/fish.freshrc]
```
This is following the Marked (a markdown preview app on OS X) rule, so Marked
can show the included file content just fine.
### freshrc support
freshshell is a very nice tool to manage dotfiles, though it doesn't support
include other freshrc at the moment(2014-05-06), so I split my freshrc into
smaller files, and use silp to put them into the main file.
- https://github.com/freshshell/fresh
0.2.2
-----
- Bugfix with the .md files not included in Manifest
0.2.1
-----
- Change name to "Simple Individual Line Preprocessor"
0.2.0
-----
- Better control with the padding spaces to keep all `generated_surfix` aligned
- Skipping files that not using SILP, to prevent the useless files in `.silp_backup`
and `.silp_test` folders
- Can support multiple project setting files with different extentions
- If a subfolder has it's own setting files, won't include them in the parant's `--all` run
0.1.0
-----
First version, can do basic processing
Metadata
Release files for silp 0.3.11
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 |
|---|---|---|---|---|
| silp-0.3.11.tar.gz | 9.2 kB | Without provenance | Details for silp-0.3.11.tar.gz |
Release files / silp-0.3.11.tar.gz
| Download URL | silp-0.3.11.tar.gz |
|---|---|
| Size | 9.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cd7e530b13c7dd6b3a0c80fa536b62e16a1ebcdac53108ef2da302423d2701ee
|
|
BLAKE2b-256 checksum How to use checksums |
60858b2c31622b885b19a5421c81e2189ab3a8f5c185683282a8c11b4adc6c80
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for silp 0.3.11
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.