Closed jeromekelleher closed 2 years ago
Aha! Figured it out. The viterbi
package was conflicting with the viterbi function. Took me ages to figure that one out!
That should be the main API surface picked out now, so how about we make an alpha package for pypi and push it up there?
Some updates here
Hopefully this will get the build completing successfully on CI.
How's it looking @astheeggeggs? I'm assuming a lot of this stuff came from cookiecutter and you didn't hand craft these configs?
Yep, you're exactly right - lots of this stuff is from cookiecutter and I left well alone!
Aha! Figured it out. The
viterbi
package was conflicting with the viterbi function. Took me ages to figure that one out!That should be the main API surface picked out now, so how about we make an alpha package for pypi and push it up there?
oh, whoa - sorry about the viterbi pain!
Here's a first pass at cleaning up the public API so we can push a release to pypi @astheeggeggs
The idea is that users won't need (or shouldn't have access to, really) the internal namespace and will just use the functions
lshmm.forward()
etc.All seems to be working OK, except for the viterbi sub-package. Can't get that to work, but have to go now. I'll pick this up again when I get a chance.
Did you hit issues like this?