Cannot handle new 3.12 f-strings, hangs up completely

[eeyorelee]

Cannot handle new 3.12 f-strings, hangs up completely

[EeyoreLee]

@crankedguy - yep, this should be added on the google/yapf side. It's issued here google/yapf. when yapf support this feature, I'll update the bundled yapf.

[EeyoreLee]

The extension didn't hang up. It's still running, and just do nothing modification if yapf package raise a exception for a file. But it will indeed report an error in yapf extension output channel cause I think most of people won‘t look at it unless the extension doesn't work.

[crankedguy]

thanks for the info. great, only open since two months...

[Spitfire1900]

@EeyoreLee The extension should still have error recovery without hanging + report an error to the user w/ stack trace in the Extension's output pane.

[crankedguy]

@EeyoreLee The extension should still have error recovery without hanging + report an error to the user w/ stack trace in the Extension's output pane.

this is one of the main problems that this does not happen
edit : clarification, main problem is that it is simply hanging itself up and ignoring the whole file if such a line occurs

[crankedguy]

@EeyoreLee You are right, I oversaw that in the specific output channel, however it is a bit of a burden that the whole file is affected by this,,, you cannot even disable that with # yapf: disable, yapf is just completely unusable for Python 3.12 at all then as far as I can see, if there is no other solution to circumvent that at least for portions of code