Python syntax error on humble.py

[mfabbri]

Describe the bug
File "humble.py", line 1144
print(f"\n {get_detail('[args_skipped_unknown]', replace=True)}
^
SyntaxError: f-string expression part cannot include a backslash

To Reproduce
Execute humble.py from command line or docker command

Expected behavior
humble.py should be executed without syntax errors

Desktop (please complete the following information):

• OS: Windows
• Version: 22H2

Additional context
I've fixed the issue with the solution proposed by ChatGPT
def print_unsupported_headers(unsupported_headers):
headers_str = ', '.join(f'"{header}"' for header in unsupported_headers)
print(f"\n {get_detail('[args_skipped_unknown]', replace=True)} ({headers_str})")
sys.exit()
Maybe there is a better way to do it but it worked. Thanks

[rfc-st]

Hi, @mfabbri

Sorry for not answering sooner ... it seems that Github.com has been down for a while in my country :(.

Indeed, in Python versions lower than 3.12 this use of f-string is not possible; the line with the error, based on the most recent version of “humble.py”, is this.

And, even though I regularly use vermin to check the minimum Python version required for “humble” ... it seems that this particular case does not detect it :/.

This Friday I will change it to remove those backslashes so you can test it again.

Thanks for reporting it!!.

Best regards,

[mfabbri]

No hay problema Rafa, thank you for making this useful tool available to the community!

[rfc-st]

Hi, @mfabbri

Please, take a look at e48f839.

Can you confirm that you are no longer reproducing the error with that commit?,

It's a pity that vermin does not have support for rules associated with Python 3.12 and higher versions ... I will restrict the minimum supported version of Python, for using 'humble', to the minimum currently supported, 3.9 (https://devguide.python.org/versions/). I think it is also good practice to use only supported versions.

Regards,

[mfabbri]

Hi @rfc-st , I tested the build process with docker 27.5.1 in Windows and I cannot reproduce the issue.
And yes, it's a good practice to use only supported versions.
Thank you again for your help

[rfc-st]

Hi, @mfabbri

I just want to thank you for reporting this error and that I have included you in the Acknowledgements section :).

Regards,

[netromdk]

@rfc-st Hi there. I just wanted to say that version 1.7.0 has been released 🎉

And, unfortunately, it is still not possible to detect the f-string cases. Maybe in the future, but at least there is 3.13 support now.