Skip to content

Conversation

@csukuangfj
Copy link
Contributor

Now everything lives in the kaldi package and the user
does not need to use kaldi_pybind any more.

Now everything lives in the `kaldi` package and the user
does not need to use `kaldi_pybind` any more.
@csukuangfj
Copy link
Contributor Author

@danpovey @naxingyu
please have a review.

sys.path.insert(0, os.path.dirname(__file__))

from kaldi_pybind import *

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suppose there are going to be a lot of decisions about which things to put in the global kaldi namespace. But it's OK.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are lots of classes in kaldi_pybind and it is a pain to list each one explicitly.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, that's OK; kaldi is just a thin wrapper for kaldi_pybind. I was actually talking about the lines below, where you import things like Matrix. But as I said, it's OK.

@danpovey
Copy link
Contributor

danpovey commented Jan 6, 2020

anyway this looks fine; merging.

@danpovey danpovey merged commit df970aa into kaldi-asr:pybind11 Jan 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants