Updating development branch with publishing fixes - #40
Conversation
Sorry, something went wrong.
| @@ -0,0 +1,9 @@ | |||
| #!/usr/bin/env bash | |||
There was a problem hiding this comment.
This won't work for a standard Windows world -- maybe that's ok but there are some cross platform options if we want to start adding build/test/doc scripts. A lot of projects use http://www.pyinvoke.org/ which is a rake-like system.
Not blocking, just a thought
Sorry, something went wrong.
There was a problem hiding this comment.
Good point @t8y8 though I'm hesitant to take a dependency on an external module just for making our job of pushing to pypi easier.
Eventually, I'd like to automate publishing to pypi when we create the release tag.
Sorry, something went wrong.
There was a problem hiding this comment.
Yeah, we probably won't hit the inflection point of needing something like that for a while.
Changes LGTM
Sorry, something went wrong.
This was done originally on master to just make things easier, but needs to be brought into development.
This change also adds the publish.sh script used for publishing to pypi.