1. 08 Oct, 2021 1 commit
  2. 02 Aug, 2021 1 commit
  3. 02 Mar, 2021 1 commit
  4. 24 Feb, 2021 1 commit
  5. 08 Feb, 2021 1 commit
  6. 05 Jan, 2021 6 commits
  7. 30 Dec, 2020 4 commits
  8. 27 Dec, 2020 1 commit
  9. 21 Dec, 2020 1 commit
    • Aziz's avatar
      Remove walk_files (#1111) · 8187dc0a
      Aziz authored
      The use of `walk_files` made it ambiguous who is responsible to locate 
      the correct set of files. (Dataset class? or utility?)
      In fact, just glob-ing everything is not the right problem being solved in implementing
      Dataset, because if you have a specific dataset you consider to access, then
      the directory structure and file locations are determined. No need to do arbitral number of recursions.
      Each Dataset implementation should be glob-ing the right set of files it requires.
      8187dc0a
  10. 18 Dec, 2020 1 commit
  11. 11 Dec, 2020 1 commit
  12. 03 Dec, 2020 1 commit
  13. 18 Nov, 2020 2 commits
  14. 17 Nov, 2020 1 commit
  15. 16 Nov, 2020 2 commits
  16. 13 Nov, 2020 3 commits
  17. 27 Oct, 2020 1 commit
  18. 09 Oct, 2020 2 commits
  19. 15 Sep, 2020 1 commit
  20. 20 Aug, 2020 1 commit
  21. 05 Aug, 2020 1 commit
    • moto's avatar
      [CI] Run unit test with non-editable installation (#845) · 9ba02d5b
      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`)
      9ba02d5b