[Python-Dev] Fuzziness in io module specs - PEP update proposition V2
Antoine Pitrou
solipsis at pitrou.net
Sun Sep 27 13:33:03 CEST 2009
More information about the Python-Dev mailing list
Sun Sep 27 13:33:03 CEST 2009
- Previous message: [Python-Dev] Fuzziness in io module specs - PEP update proposition V2
- Next message: [Python-Dev] Fuzziness in io module specs - PEP update proposition V2
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hello, > So here is the proposed semantic, which matches established conventions: > > *IOBase.truncate(n: int = None) -> int* [...] I still don't think there is a sufficient benefit in breaking compatibility. If you want the file pointer to remain the same, you can save it first and restore it afterwards manually. > *Propositions of doc update* Please open tracker issues for these kinds of suggestions. Regards Antoine.
- Previous message: [Python-Dev] Fuzziness in io module specs - PEP update proposition V2
- Next message: [Python-Dev] Fuzziness in io module specs - PEP update proposition V2
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list