434 quick-fixes #433, but @fgrunewald raised the good point that the true solution is to have all writers accept a file handle rather than a path. This way you could even have martinize2 write your pdb/itp/whatevers to stdout, network, or tar.
I'd argue that at the same point we want the same for all readers/parsers. Having different APIs for readers and writer is a needless complication, plus, you'd be able to do clever things with compressed files.
434 quick-fixes #433, but @fgrunewald raised the good point that the true solution is to have all writers accept a file handle rather than a path. This way you could even have martinize2 write your pdb/itp/whatevers to stdout, network, or tar.
I'd argue that at the same point we want the same for all readers/parsers. Having different APIs for readers and writer is a needless complication, plus, you'd be able to do clever things with compressed files.