-
-
Notifications
You must be signed in to change notification settings - Fork 19.3k
CLN: use integer parsing functions from stdlib #62658
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
Changes from 47 commits
c3cc4a1
2459313
d8a454e
87789e6
2287944
2bea3c2
fb38679
f9ede5c
798c263
2f06f19
280b55e
d85aaf0
9046ecc
a4e2fb8
ef82cf4
5afeb11
0ef47a7
c840ef0
132342b
e6977cc
8120eea
1f5d506
479a2ab
c37c355
7d55283
ffe50ce
af5ad71
9211704
d026b01
d76ff5f
b523a19
6265172
abed6c1
8616f9f
c4e0e25
0b19208
29d74f7
b5b8f3b
803a8bf
31f26cf
171b553
30f6bdc
554675b
7ea4454
82dc037
627df4c
1b3eba0
e1667fa
bee776a
d693345
593c614
ff4d48b
e3a88d3
b135738
ba8c9b3
818921f
3e067f7
c0ed83c
cb60adb
5117e89
e1e327a
ffcb7c2
47b87f9
cd536fb
1ef9259
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -23,10 +23,15 @@ GitHub. See Python Software Foundation License and BSD licenses for these. | |||||||||||||||||||||||||
| #include <float.h> | ||||||||||||||||||||||||||
| #include <math.h> | ||||||||||||||||||||||||||
| #include <stdbool.h> | ||||||||||||||||||||||||||
| #include <stdlib.h> | ||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||
| #include "pandas/portable.h" | ||||||||||||||||||||||||||
| #include "pandas/vendored/klib/khash.h" // for kh_int64_t, kh_destroy_int64 | ||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||
| // Arrow256 allows up to 76 decimal digits. | ||||||||||||||||||||||||||
| // We rounded up to the next power of 2. | ||||||||||||||||||||||||||
| #define PROCESSED_WORD_CAPACITY 128 | ||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||
| void coliter_setup(coliter_t *self, parser_t *parser, int64_t i, | ||||||||||||||||||||||||||
| int64_t start) { | ||||||||||||||||||||||||||
| // column i, starting at 0 | ||||||||||||||||||||||||||
|
|
@@ -1834,201 +1839,196 @@ int uint64_conflict(uint_state *self) { | |||||||||||||||||||||||||
| return self->seen_uint && (self->seen_sint || self->seen_null); | ||||||||||||||||||||||||||
| } | ||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||
| /** | ||||||||||||||||||||||||||
| * @brief Check if the character in the pointer indicates a number. | ||||||||||||||||||||||||||
| * It expects that you consumed all leading whitespace. | ||||||||||||||||||||||||||
| * | ||||||||||||||||||||||||||
| * @param p_item Pointer to verify | ||||||||||||||||||||||||||
| * @return Non-zero integer indicating that has a digit 0 otherwise. | ||||||||||||||||||||||||||
| */ | ||||||||||||||||||||||||||
| static inline bool has_digit_int(const char *str) { | ||||||||||||||||||||||||||
|
||||||||||||||||||||||||||
| if (!str || *str == '\0') { | ||||||||||||||||||||||||||
| return false; | ||||||||||||||||||||||||||
| } | ||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||
| switch (*str) { | ||||||||||||||||||||||||||
| case '0': | ||||||||||||||||||||||||||
| case '1': | ||||||||||||||||||||||||||
| case '2': | ||||||||||||||||||||||||||
| case '3': | ||||||||||||||||||||||||||
| case '4': | ||||||||||||||||||||||||||
| case '5': | ||||||||||||||||||||||||||
| case '6': | ||||||||||||||||||||||||||
| case '7': | ||||||||||||||||||||||||||
| case '8': | ||||||||||||||||||||||||||
| case '9': | ||||||||||||||||||||||||||
| return true; | ||||||||||||||||||||||||||
| case '+': | ||||||||||||||||||||||||||
| case '-': | ||||||||||||||||||||||||||
| return str[1] != '\0' && isdigit_ascii(str[1]); | ||||||||||||||||||||||||||
|
||||||||||||||||||||||||||
| const bool isneg = *p == '-' ? true : false; | |
| // Handle sign. | |
| if (isneg || (*p == '+')) { | |
| p++; | |
| } | |
| // Check that there is a first digit. | |
| if (!isdigit_ascii(*p)) { | |
| // Error... | |
| *error = ERROR_NO_DIGITS; | |
| return 0; | |
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah that's right - my mistake
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps this function complicates the diff too much. If you want, I can remove this function and perform the verification at the start of the str_to_int64.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm now that this function has changed the possibility for an address violation is back.
Yea I think whatever keeps the diff minimal is best for now; there are enough moving parts as is :-)
WillAyd marked this conversation as resolved.
Show resolved
Hide resolved
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since right is only used inside of the loop you can move this therein (to the initial definition)
WillAyd marked this conversation as resolved.
Show resolved
Hide resolved
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| size_t remaining_bytes_to_read = end_ptr - left; | |
| const size_t remaining_bytes_to_read = end_ptr - left; |
Always best to add const unless there's a reason for mutability
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| size_t chunk_size = right - left; | |
| const size_t chunk_size = right - left; |
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the comments here and beyond are all superfluous, i.e. they add no value on top of what the code itself is showing
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it necessary to add this? I don't think we should be special-casing behavior for null or the null byte; I expect the former is undefined (since its not a string) and the latter would be handled naturally by the rest of the logic (?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed, not necessary. The null byte is already handled below.
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is lost in a refactor right? I don't think errno will be set by anything preceding this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed, I forgot to remove it.
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| char *endptr = NULL; | |
| char *endptr; |
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As a matter of convention need to check errno and "raise" if its set before clearing it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By "raise" you mean printing to stderr?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By "raise" I mean follow whatever exception handling is implemented. In this particular function, it looks like you should set the error variable and return 0 when an exception is encountered
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You might want to give the CPython error handling doc a read, which most of the extensions base their methodology off of:
https://docs.python.org/3/c-api/exceptions.html#exception-handling
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am now resetting errno after handling the overflow error
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suppose this is unrelated to your PR but why does this function accept int_max and int_min as arguments? Assuming those are actually set to INT64_MAX and INT64_MIN this is a no-op, and potentially waste of cycles if the compiler can't optimize it away
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed, it's unnecessary. It's set to INT64_MAX and INT64_MIN.
pandas/pandas/_libs/parsers.pyx
Lines 1930 to 1931 in 066a4f7
| data[i] = str_to_int64(word, INT64_MIN, INT64_MAX, | |
| &error, parser.thousands) |
Should I just check errno or I should also change the function signature?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changing the function signature is fine (let's do as a separate PR)
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you removed the const char *p = p_item assignment as a cleanup and not for any type of functionality, but if that's true its inflating the diff. Should move cleanup items like that to a separate PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've made several changes that complicate a lot the diff. I'll put back the const char *p assignment, and also remove the need for some auxiliary functions created.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great - thanks!
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -72,13 +72,23 @@ def test_read_csv_local(all_parsers, csv1): | |
| tm.assert_frame_equal(result, expected) | ||
|
|
||
|
|
||
| def test_1000_sep(all_parsers): | ||
| @pytest.mark.parametrize( | ||
| "number_csv, expected_number", | ||
| [ | ||
| ("2,334", 2334), | ||
| ("-2,334", -2334), | ||
| ("-2,334,", -2334), | ||
| ("2,,,,,,,,,,,,,,,5", 25), | ||
WillAyd marked this conversation as resolved.
Show resolved
Hide resolved
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think its good to have this for test coverage but I'm doubtful it was intended even on main. Maybe we can add a comment that this is just to make sure our parser code is sound, but not necessarily to always ensure |
||
| ("2,,3,4,,,,,,,,,,,,5", 2345), | ||
| ], | ||
| ) | ||
| def test_1000_sep(all_parsers, number_csv, expected_number): | ||
| parser = all_parsers | ||
| data = """A|B|C | ||
| 1|2,334|5 | ||
| data = f"""A|B|C | ||
| 1|{number_csv}|5 | ||
| 10|13|10. | ||
| """ | ||
| expected = DataFrame({"A": [1, 10], "B": [2334, 13], "C": [5, 10.0]}) | ||
| expected = DataFrame({"A": [1, 10], "B": [expected_number, 13], "C": [5, 10.0]}) | ||
|
|
||
| if parser.engine == "pyarrow": | ||
| msg = "The 'thousands' option is not supported with the 'pyarrow' engine" | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.