7 Commity (ba1c2ea78ffce7ac2c08e8b54f834024747d816f)

Autor	SHA1	Wiadomość	Data
Lex Neva	94f391ab42	more pep8 fixes	2018-08-21 20:50:14 -04:00
Lex Neva	038875f876	autopep8	2018-08-21 20:32:50 -04:00
Lex Neva	fe480750c5	Merge pull request #260 from inkstitch/lexelby-windows-output-fix ... fix output extension on windows	2018-08-16 15:53:59 -04:00
Lex Neva	ab4b09531d	useful error message from stub.py	2018-08-05 23:06:24 -04:00
Lex Neva	89e5e5c9db	stub should also open stdout in binary mode	2018-08-03 22:39:52 -04:00
Lex Neva	bb42124a87	Windows fixes (#83) ... * os.execv doesn't replace the process on windows * fix simulate/params crash * pyinstaller windowed mode breaks things? * fix output routing for windows * properly route stderr to inkscape too * don't print unless there's something to print * remove last backup version if necessary * add documentation for Windows build	2018-02-22 23:06:27 -05:00
Lex Neva	8bab858be6	pyinstaller release method (#16) ... pyinstaller packages up all of a python script's dependencies and builds them into standalone executables. It can either do a directory (containing a single executable and a bunch of shared libraries) or a self-contained executable that effectively just contains a compressed version of the directory. The problem is, if you have several scripts like we do, you get several large directories or standalone binaries, and there's a ton of duplication between them. Fortunately it looks like using the directory method and just combining the directories works fine (for this project). This PR runs the above build on any tagged commit and publishes a release in github containing the pyinstall-ified tarball. If the tag is named like "v1.2.3" _and_ the tag is on the master branch, then the github release will be marked as "production". Otherwise, it will be marked as a "pre-release". This means that we can build testable tarballs of the extension in a pull request by tagging a commit.	2018-01-13 20:18:50 -05:00