Skip to content
Snippets Groups Projects
  1. Jul 21, 2020
  2. Jul 20, 2020
  3. Jul 18, 2020
  4. Jul 19, 2020
  5. Jul 20, 2020
  6. Jul 14, 2020
  7. Jul 17, 2020
  8. Jul 18, 2020
  9. Jul 14, 2020
  10. Jul 09, 2020
  11. Jul 18, 2020
    • Manuel Jacob's avatar
      windows: don’t set `softspace` attribute in `winstdout` · ed58ecd59030
      Manuel Jacob authored
      Python 2 file objects have the `softspace` attribute
      (https://docs.python.org/2/library/stdtypes.html#file.softspace), which is used
      by the print statement to track its internal state. The documentation demands
      from file-like objects only that the attribute is writable and initialized to
      0. Method `file.write()` sets it to 0, but this is not documented.
      Historically, sys.stdout was replaced by an instance of the `winstdout` class,
      so it needed to behave exactly the same (the softspace fix was introduced in
      705278e70457). Nowadays we don’t replace sys.stdout and don’t use the print
      statement on `winstdout` instances, so we can safely drop it.
      ed58ecd59030
  12. Jul 17, 2020
  13. Jul 16, 2020
  14. Jul 14, 2020
  15. Jul 13, 2020
  16. Apr 01, 2020
  17. Jul 17, 2020
    • Manuel Jacob's avatar
      windows: always work around EINVAL in case of broken pipe for stdout / stderr · a37f290a7124
      Manuel Jacob authored
      In 29a905fe23ae, I missed the fact that the `winstdout` class works around two
      unrelated bugs (size limit when writing to consoles and EINVAL in case of
      broken pipe) and that the latter bug happens even when no console is involved.
      When writing a test for this, I realized that the same problem applies to
      stderr, so I applied the workaround for EINVAL to both stdout and stderr.
      
      The size limit is worked around in the same case as before (consoles on Windows
      on Python 2). For that, I changed the `winstdout` class.
      a37f290a7124
  18. Jul 16, 2020
  19. Jul 17, 2020
Loading