Stefan Behnel schrieb am 21.09.2018 um 09:38:
> There are two parts of
> information here, so maybe we should actually split them internally (in
> "Main.Context.set_language_level() ?) and keep the language_level = 3 but
> just avoid the "unicode_literals" part.
I thought about this some more. The
John Ehresman schrieb am 25.09.2018 um 16:27:
> On 9/25/18 1:24 AM, Stefan Behnel wrote:
>> I started off with "unicode_literals=False", and then renamed it because
>> this name didn't cover the change of "str" to "unicode" (i.e. renaming the
>> usages of the builtin type internally, so that "str(x
Daniele Nicolodi schrieb am 25.09.2018 um 00:28:
> On 24-09-2018 14:05, Stefan Behnel wrote:
>> I added a new directive "str_is_str=True" which can be combined with
>> "language_level=3" to get the desired behaviour. It keeps the 'str' builtin
>> type as it is (it would otherwise become 'unicode' w
On 24-09-2018 14:05, Stefan Behnel wrote:
> I added a new directive "str_is_str=True" which can be combined with
> "language_level=3" to get the desired behaviour. It keeps the 'str' builtin
> type as it is (it would otherwise become 'unicode' with level 3) and keeps
> unprefixed string literals as
Stefan Behnel schrieb am 21.09.2018 um 17:46:
> Robert Bradshaw schrieb am 21.09.2018 um 17:30:
>> I agree that this doesn't really feel like a language-level thing.
>>
>> There seem three desired behaviors here:
>>
>> language_level=2 where currently "abc" is always a bytes object
>> langauge_leve
Jeroen Demeyer schrieb am 20.09.2018 um 10:59:
> On 2018-09-20 10:15, Jeroen Demeyer wrote:
>> On 2018-09-20 07:55, Stefan Behnel wrote:
>>> I can see that this would be helpful. It's unfortunate, though, that this
>>> would introduce a temporary option that complicates the current integer
>>> "lan
