Typo in io.rst and meta-question about patches workflow
Hello everyone In trunk’s Doc/library/io.rst, a change from IOError to ValueError has left a stray “an”: --- Doc/library/io.rst Sat May 01 14:16:39 2010 +0200 +++ Doc/library/io.rst Sat May 01 15:26:32 2010 +0200 @@ -246,7 +246,7 @@ - (e.g. reading or writing) will raise an :exc:`ValueError`. + (e.g. reading or writing) will raise a :exc:`ValueError`. Is it ok to use the mailing list instead of the bug tracker for such tiny patches? Apart from Georg, are there people with commit power on the list? Do they prefer emails or bug reports? Should we wait until we’ve collected a bunch of typo before reporting them instead of doing it one message per found typo? Regards
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 01.05.2010 20:48, schrieb Éric Araujo:
Hello everyone
In trunk’s Doc/library/io.rst, a change from IOError to ValueError has left a stray “an”:
--- Doc/library/io.rst Sat May 01 14:16:39 2010 +0200 +++ Doc/library/io.rst Sat May 01 15:26:32 2010 +0200 @@ -246,7 +246,7 @@ - (e.g. reading or writing) will raise an :exc:`ValueError`. + (e.g. reading or writing) will raise a :exc:`ValueError`.
Is it ok to use the mailing list instead of the bug tracker for such tiny patches? Apart from Georg, are there people with commit power on the list? Do they prefer emails or bug reports? Should we wait until we’ve collected a bunch of typo before reporting them instead of doing it one message per found typo?
There are a few, but most are inactive. Still, reporting each typo is fine. Georg -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) iEYEARECAAYFAkvof8kACgkQN9GcIYhpnLCzmgCeIiWoSLPX3nA0TTWmK6fuAPMZ 1FEAoKEkYwhwL1glnF8ppbrJRnbETqC8 =JgXw -----END PGP SIGNATURE-----
participants (2)
-
Georg Brandl -
Éric Araujo