Snippety generates code inside your code from your code.
Sometime end up with code like below (You could solve this particular example with getattr() and setattr() because it's Python, but this is just an illustration. Snippety works on any text files)
def __init__(self, dataRow):
self._name = dataRow.name
# Evil duplication...
self._age = dataRow.age
self._height = dataRow.height
self._weight = dataRow.weight
print "created ", self.name
With Snippety, you place a directive (in a comment) on the line you want to repeat:
def __init__(self, dataRow):
self._name = dataRow.name #sn_i [name] age height weight
print "created ", self.name
Pass your file to Snippety, and it regenerates it with this:
def __init__(self, dataRow):
self._name = dataRow.name #sn_i [name] age height weight
self._age = dataRow.age #generated_code
self._height = dataRow.height #generated_code
self._weight = dataRow.weight #generated_code
print "created ", self.name
Most IDEs load your buffer when the file is changed externally, so it refreshes like magic.
The #generated_code comments are for Snippety to track which lines it generated, so that if you change the directive or source line, it wipes and rebuilds those.
Because generating code is cool. Generating code from directives inside your code is even cooler, especially if it can treat your code as text.
Snippety uses existing lines of source/text as template, and replicates them with transformations, which is very powerful.
There are tools like cog which is far more flexible but also more clunky, and don't let you easily use the existing source code next to your directive.
- There's an easy enumeration [0, 1, 2...] feature
- There's intelligent capitalsation handling
- These come from Snippety's directives and you can easily subclass and create your own.
- Snippety regenerates the lines each time it is run, so you only need to change the original snippet.
- You can have multi-line snippet, and even nested chunks within those!
- You can direct the output to another file.
- You can use collections defined in a config file instead of typing out each item in the directive
- You can apply conditional statements (repeat for all elements if)
=======
The #generated_code comments are for Snippety to track which lines it generated, so that if you change the directive or source line, it wipes and rebuilds those.
Because generating code is cool. Generating code from directives inside your code is even cooler, especially if it can treat your code as text.
Snippety uses existing lines of source/text as template, and replicates them with transformations, which is very powerful.
There are tools like cog which is far more flexible but also more clunky, and don't let you easily use the existing source code next to your directive.
- Snippety can be run as a tool, or imported into a python script.
- There's an easy enumeration [0, 1, 2...] feature
- There's intelligent capitalsation handling
- These come from Snippety's directives and you can easily subclass and create your own.
- Snippety regenerates the lines each time it is run, so you only need to change the original snippet.
- You can have multi-line snippet, and even nested chunks within those!
- You can direct the output to another file.
- You can use collections defined in a config file instead of typing out each item in the directive
- You can apply conditional statements (repeat for all elements if)
Here's an example using enumeration, and showing a directive with start (sn_s) and end (sn_e) directives as opposed to the inline (sn_i) shown above.
def __init__(self, dataRow):
#sn_s [name, 0*1] age height weight
self.name = dataRow[0]
#sn_e
self._age = dataRow[1] #generated_code
self._height = dataRow[2] #generated_code
self._weight = dataRow[3] #generated_code
print "created ", self.name
##Important information:
Snippety replaces the contents of the file you're actually working on, so make sure your Editor/IDE tells you when the underlying file contents have changed (most do).
YOU MUST REMEMBER TO SAVE YOUR FILES BEFORE RUNNING SNIPPETY OVER THEM!
Alternatively you can tell Snippety to output to a different location, leaving your source files untouched.
Here's a simple example you can run with minimal setup:
Create a source file (let's call it test.txt) with this:
I'm a cat #sn_i [cat] dog squirrel piggy
And a python file called regen.py in the same directory:
from sys import argv
from snippety import Snippety
sn = Snippety()
sn.process_file(argv[1])
In the terminal, run:
>>> python regen.py test.txt**
And test.txt should become:
I'm a cat #sn_i [cat] dog squirrel piggy
I'm a dog #generated code
I'm a squirrel #generated code
I'm a piggy #generated code
There is more you can do, such as:
# process_dir catches all the files in a directory.
# can be passed include and exclude lists, see docstrings in source
sn.process_dir('.')
Look into the source code and unit tests to get an idea of what directives are working and available.
Remember, Snippety overwrites files, so make sure you understand what you are doing.
- Snippety uses pytest for it's unit tests, and there's a fair amount of test that pass, but could do with more edge-case testing.
- Stick to Python Style Guide
- Make sure the code is compatible with Python 2.7.
Email me at andyhasit@gmail.com.