[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Newline handling
From: |
Bruno Haible |
Subject: |
Re: Newline handling |
Date: |
Thu, 28 Mar 2024 04:45:25 +0100 |
Collin Funk wrote:
> I can go through all the open() and codec.open() calls and turn them
> into:
>
> with open(file_name, 'r', encoding='utf-8', newline='\n') as file:
> # do something
>
> and
>
> with open(file_name, 'w', encoding='utf-8', newline='\n') as file:
> # do something
>
> in that case. I think that should make everything work correctly.
> Would that be good?
This would be reasonable (*), but is low priority (because the average
gnulib-tool user will not see any effect from this). I've added it
to the gnulib-tool.py.TODO file.
(*) Although I'm not sure encoding='utf-8' is the right thing in all
circumstances...
Bruno
- [PATCH] gnulib-tool.py: Inline 'sed' invocations used on library files., Collin Funk, 2024/03/27
- Re: [PATCH] gnulib-tool.py: Inline 'sed' invocations used on library files., Collin Funk, 2024/03/27
- Re: [PATCH] gnulib-tool.py: Inline 'sed' invocations used on library files., Bruno Haible, 2024/03/27
- Re: [PATCH] gnulib-tool.py: Inline 'sed' invocations used on library files., Bruno Haible, 2024/03/27
- Re: [PATCH] gnulib-tool.py: Inline 'sed' invocations used on library files., Collin Funk, 2024/03/27
- Re: [PATCH] gnulib-tool.py: Inline 'sed' invocations used on library files., Collin Funk, 2024/03/27
- Re: [PATCH] gnulib-tool.py: Inline 'sed' invocations used on library files., Bruno Haible, 2024/03/27
- Newline handling, Collin Funk, 2024/03/27
- Re: Newline handling,
Bruno Haible <=
- Re: Newline handling, Collin Funk, 2024/03/28