-
Notifications
You must be signed in to change notification settings - Fork 163
Pydot considers dotted strings like "1.4.0" to be numeric #438
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
ferdnyc
added a commit
to ferdnyc/pydot
that referenced
this issue
Nov 27, 2024
The `re_all_numeric` check used to allow any number of decimal points in the value, which isn't correct for numerics; at most one can be allowed. Rename to `re_numeric`, and use a more complex RE that allows a maximum of one decimal point, but fails on strings like "1.4.0". Fixes pydot#438
ferdnyc
added a commit
to ferdnyc/pydot
that referenced
this issue
Nov 28, 2024
The `re_all_numeric` check used to allow any number of decimal points in the value, which isn't correct for numerics; at most one can be allowed. Rename to `re_numeric`, and use a more complex RE that allows a maximum of one decimal point, but fails on strings like "1.4.0". Fixes pydot#438
lkk7
pushed a commit
that referenced
this issue
Nov 28, 2024
* Fix numeric-value regular expression The `re_all_numeric` check used to allow any number of decimal points in the value, which isn't correct for numerics; at most one can be allowed. Rename to `re_numeric`, and use a more complex RE that allows a maximum of one decimal point, but fails on strings like "1.4.0". Fixes #438 * Add tests for re_numeric quoting behavior
Nice, thanks a lot :-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@pktpls wrote:
Ooh, that's a different problem. The regular expression used to detect numeric values accepts periods (because, decimal points), but really it should only accept a SINGLE period at most. We'll have to change that from
to something like...
Originally posted by @ferdnyc in #178 (comment)
The text was updated successfully, but these errors were encountered: