- 05 Aug, 2020 1 commit
-
-
moto authored
We have been running unit test with editable installation. (i.e. `python setup.py develop`), with which we missed issues like #842. This CC makes installation in CI non-editable, and change test directory structure so that the source code will not shadow the installed version of `torchaudio`. With simple `pytest test`, `pytest` modifies `sys.path` and prepend checked out repository, which shadows the installed version. To remedy this, the whole test suites has been moved from `./test` to `./test/torchaudio_unittest`. This adds nice module structure to our test code and we can do absolute import in each test module, which makes it possible again to run test with `python -m unittest torchaudio_unittest/XXX.py` This change does not affect the regular development process (`python setup.py develop` && `pytest test`)
-
- 01 Jul, 2020 1 commit
-
-
moto authored
-
- 19 Jun, 2020 1 commit
-
-
moto authored
This is a part of PRs to add new "sox_io" backend #726, and depends on #718. This PR adds `info` function to "sox_io" backend, which allows users to fetch some metadata of an audio file. At this moment, the information retrieved are; - Number of samples in the audio file - Sampling rate - Number of channels
-
- 18 Jun, 2020 1 commit
-
-
moto authored
* Make tests backend aware by introducing TorchaudioTestCase and reset backend for each TestCase. * Set backends for the test cases that require specific backend.
-
- 16 Jun, 2020 1 commit
-
-
moto authored
* Refactor backend switching 1. Do not rely on global variables for backend switch So that load/save/info/load_wav functions will be torchscript-able 2. Add no_backend module to for the case there is no backend module available [bonus] This allows the whole codebase importable on systems that do not have torchaudio C++ extension nor soundfile.
-