use entry_points instead of scripts for CLI

[bollwyvl]

As promised, per #22, this moves bin/pyshacl to pyshacl/cli.py, and uses entry_points for locating it at install time.

Also happy to work up an azure-pipelines.yaml to get some more robotic eyes on this project... though you'd probably have to set up an account: it's a bit awkward, and the docs aren't fantastic, but given it's platform reach, performance, etc. it's hard to beat unless you need fine-grain incremental building.

[ashleysommer]

@bollwyvl
Will this change require documentation changes in the README?
Will users be able to call the cli app in the same way as they currently do?

Regarding azure-pipelines, does Azure offer a free tier for this kind of thing at all?
I've played with Bitbucket-pipelines a bit, maybe I could set that up for more automated testing.

[bollwyvl]

Will this change require documentation changes in the README?

Nope. pyshacl will just keep working. the cli main function itself would now be importable... this can be handy for integrators, but you don't strictly need to advertise it. the first commit went a bridge too far and moved the sys.exits (not fun to catch), but that can be a PR for another day. however, it would certainly be good to test it :P

Regarding azure-pipelines, does Azure offer a free tier for this kind of thing at all?

Yeah, for open source: unlimited jobs up to an hour apiece, up to ten at a time. partially to nip the atlassian digression in the bud, here's what ci could be like:

https://dev.azure.com/nickbollweg/pyshacl/_build/results?buildId=292&view=results

Or if you prefer, right on github:

https://github.com/bollwyvl/pySHACL/pull/1/checks?check_run_id=129123119

i have some ui beefs (especially on mobile) but you can't beat the price.

I already had an account, so it only took a few minutes to get it set up. you'd just need an account over there, and you do have to give the bot push access, i think. you go through the github marketplace.

the syntax is a bit annoying, as it's not real yaml (no anchors, etc) so they kinda force you to use their crazy n pass templating system. but for simple stuff, it's simple enough, and it makes complex stuff possible in a way that other ci systems don't approach until you get into jenkins land.

I've played with Bitbucket-pipelines a bit, maybe I could set that up for more automated testing.

of course, up to you, but... see above. while i certainly mistrust microsoft, i actively dislike atlassian.

[ashleysommer]

Woops, sorry I forgot to merge this.

[bollwyvl]

Cool!

…

On Tue, Jun 4, 2019, 05:46 Ashley Sommer ***@***.***> wrote: Merged #23 <#23> into master. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#23?email_source=notifications&email_token=AAALCRBUGFQ4NES3N6OSM7TPYY2X7A5CNFSM4HMVEFFKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGORZHQ6QA#event-2387545920>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAALCRF5DMCNTDSDXVTM4ODPYY2X7ANCNFSM4HMVEFFA> .