Release 1.2.3
niessner@elysium:~/Projects/DAWGIE$ cat /tmp/t.t
issue 25: PyPI script (#26)
Author: al-niessner
Date: Sun, 28 Jul 2019 16:19:21 -0700
- .ci/pypi.sh
While not part of continuous integration, it is a helper script for me to take a release, build it, then install it at PyPI for those using DAWGIE.
Issue 23: fix up setup.py (#24)
Author: al-niessner
Date: Sun, 28 Jul 2019 15:57:52 -0700
- add a little more stuff to delivery and try using a patched version of pydot3.
Added README.md and LICENSE to the egg data directory just because. Seems better to have it all around than to not have it at all. Might be misguided.
Built a patched version of pydot3 in my fork of it then pushed it to PyPI as dawgie-pydot3. Once built and deployed, then changed this setup.py to depend upon it.
- fix vulnerability
Issue 21: start PyPI (#22)
Author: al-niessner
Date: Sat, 27 Jul 2019 13:44:57 -0700
- update setup.py
Following the PyPI documentation, try building the package for distribution on PyPI. Will need a parent script to do more work than this.
- start of deploying via PyPI
An instiall script to build the a deployment. Right now the script builds this directory rather than collecting a released version from github.com. It will come with time, but here the mechanics of how to build the artifact for PyPI and deliver it is complete. The script is left in safe mode where it will deploy to test.pypi instead of pypi.
Updated the setup.py to work correctly with PyPI. It does a description (poorly) but does one. It has a license and describes it nicely on the website. All inall, it looks like the setup.py is sufficient.
update utility for making release notes
Author: Al Niessner
Date: Tue, 23 Jul 2019 14:02:29 -0700