Skip to content

The ValueError for converting an all-whitespace string to a float misleadingly displays it as the empty string #95605

Closed

Description

@Zeturic

Bug report

Actual behavior:

>>> float('\n')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ValueError: could not convert string to float: ''

Expected behavior:

>>> float('\n')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ValueError: could not convert string to float: '\n'

As long as the string isn't completely whitespace, it does display properly. For example:

>>> float('\nn')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ValueError: could not convert string to float: '\nn'

In addition to newlines, the same thing can be observed with tabs and carriage returns, or any combination of the three. I didn't test any additional whitespace characters, though they would likely behave the same way.

Your environment

  • CPython versions tested on: 3.10.5
  • Operating system and architecture: Windows 10 (64-bit)

Activity

  1. added
    type-bugAn unexpected behavior, bug, or error
    on Aug 3, 2022
  2. mdickinson commented on Aug 4, 2022

    @mdickinson
    Member

    Thanks for the report. This is caused by an unfortunate interaction between float_from_string_inner and PyOS_string_to_double. (The PyOS_string_to_double API leaves something to be desired, with its multi-channel reporting of errors, but it's part of the limited API so we can't change it.)

    Specifically, after the PyOS_string_to_double call, if end == last in float_from_string_inner, then either the parse was successful, or the string being parsed was empty; conversely, if the parse was successful then end == last. So when we raise on end != last, we catch only parse failures on nonempty strings. The parse failure on an empty string just propagates the ValueError already raised in PyOS_string_to_double, which has an inferior error message.

    #95665 should fix this.

  3. added a commit that references this issue on Aug 10, 2022
  4. added 2 commits that reference this issue on Aug 10, 2022
  5. added 2 commits that reference this issue on Aug 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    3.10 (EOL)end of life3.11only security fixes3.12only security fixestype-bugAn unexpected behavior, bug, or error

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions