1. 18 Mar, 2018 1 commit
  2. 09 Sep, 2017 1 commit
  3. 25 Jul, 2017 1 commit
  4. 11 Jul, 2017 1 commit
  5. 26 May, 2017 2 commits
  6. 15 Jan, 2017 1 commit
  7. 03 Jan, 2017 1 commit
  8. 28 Dec, 2016 3 commits
  9. 27 Dec, 2016 1 commit
  10. 18 Dec, 2016 1 commit
  11. 15 Aug, 2016 1 commit
  12. 09 Aug, 2016 1 commit
  13. 19 Jan, 2016 1 commit
  14. 15 Dec, 2015 1 commit
  15. 12 Dec, 2015 1 commit
  16. 06 Dec, 2015 2 commits
  17. 05 Dec, 2015 1 commit
    • Jérémy Bobbio's avatar
      Use lazy extraction instead of explicit bracketing · 303aee94
      Jérémy Bobbio authored
      Previously, code requiring access to file content had to be explicitly
      bracketed using get_content() for files to be extracted and then deleted.
      Such construction is problematic for parallel processing as a file might be
      processed be multiple operations currently (e.g. multiple files being extracted
      from a unique archive at the same time).
      
      We thus removes the get_content() context and @needs_content decorator to
      prefer lazy path initialization: actual content will be made available through
      the path property. The extraction will happen then if necessary.
      
      The extracted file should normally be deleted when Python garbage collector
      reclaims the object. As a safety net, we still have a global registry of all
      temporary files and directories and remove them on exit.
      303aee94
  18. 03 Dec, 2015 1 commit
  19. 02 Dec, 2015 1 commit