Pyembroidery will always attempt to minimize information loss. A python27 branch is available but that branch was merely forked from when the version was supported. It is highly recommended that you upgrade.
Though previously mandated support for Python 2.7, this support was dropped at the end of life for that version. Further it supports SEQUIN to JUMP operations on the other formats.
SEQUINS work in all supported formats (.dst) that are known to support sequins. It supports all the core commands where that format can use said command as well as FAST and SLOW for. It reads 40 embroidery formats including the mandated ones. It writes 9 embroidery formats including the mandated ones. Pyembroidery fully meets and exceeds all of these requirements. pyembroidery must fully support commands: STITCH, JUMP, TRIM, STOP, END, COLOR_CHANGE, NEEDLE_SET, SEQUIN_MODE and SEQUIN_EJECT. pyembroidery must read and write: PES, DST, EXP, JEF, VP3. Pyembroidery must to be small enough to be finished in short order and big enough to pack a punch. It should be complex enough to go very easily from points to stitches, fine grained enough to let you control everything, and good enough that you shouldn't want to. It should be highly robust with a simple api so as to be reasonable for any python embroidery project. 
If you know an error it does not account for, raise an issue. It includes a lot of higher level and middle level pattern composition abilities, and should accounts for any knowable error. Pyembroidery was coded from the ground up with all projects in mind. Any suggestions or comments please raise an issue on the github.
0 kommentar(er)
