[issue17246] inspect.getargvalues fails if arg name is not bound to a value

2022-03-29 Thread Maciej Górski
Maciej Górski added the comment: In my opinion formatargvalues function is quite useless in current day as ArgInfo provides all the information. I'm however willing to fix this. IMO we should just omit the args/varargs/kwargs that have been deleted, since the values do not exist i

[issue47129] Improve errors messages in f-string syntax errors

2022-03-28 Thread Maciej Górski
Maciej Górski added the comment: Thanks for helping me with my very first python contribution! @eric.smith @lys.nikolaou -- ___ Python tracker <https://bugs.python.org/issue47

[issue47129] Improve errors messages in f-string syntax errors

2022-03-27 Thread Maciej Górski
Maciej Górski added the comment: I agree as well. I will change it to the new version :) Thanks for your input in this. -- ___ Python tracker <https://bugs.python.org/issue47

[issue47129] Improve errors messages in f-string syntax errors

2022-03-26 Thread Maciej Górski
Maciej Górski added the comment: Understandable. In this case I can maybe propose something along the lines of "f-string: empty expression not allowed (Conversion specifier '!' can only follow non-empty expressions)", and so on for each of the specifiers. This way the

[issue47129] Improve errors messages in f-string syntax errors

2022-03-26 Thread Maciej Górski
Change by Maciej Górski : -- keywords: +patch pull_requests: +30206 stage: -> patch review pull_request: https://github.com/python/cpython/pull/32127 ___ Python tracker <https://bugs.python.org/issu

[issue47129] Improve errors messages in f-string syntax errors

2022-03-26 Thread Maciej Górski
New submission from Maciej Górski : When an empty expression is provided in curly brackets inside an f-string we get Syntax Error: "f-string: empty expression not allowed". This is correct, however error with the same message is raised in the following cases: f"{!foo}",