You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My question is whether there should be a mixed-type column instead of automatically deciding what data type the column is. In this case, “tabulate” would try to identify the data type for each cell in that column and treat it as such rather than the overall type of the column.
Quick comment
In GitHub, you could add the discussion feature: https://github.com/features/discussions. With this feature, your community can create a discussion, if a specific discussion is relevant, it could move to the issues section.
Not all the final users (community) use the discussion feature, instead the repositories or projects have enabled. But, the discussion feature appears to be useful in terms of administration.
Context
I noticed that “tabulate” reviews all the rows for each column and automatically assigns a type of column. It is fabulous, but I am concerned when the rows in the column are mixed.
In the mixed cases, I discovered that the order is as follows:
If one row in the column contains one or more strings, it is considered a string.
Otherwise, if at least one float is detected, the column will be a float type.
Finally, if the column contains only integers, the type is the same.
Evidence
All the results were taken, adding debug lines for the function _format(). It prints the val type and the valtype value to compare both.
Then, in the logic for the _format() function, we can check that it is mixed and take the real value for the val to perform all the actions for formatting.
Solution 2
Always ignore the valtype and take the type of the val. Except if some parameter was passed which indicates that the user specified the format of the column. Something like this: tabulate([[82000.38], ["abcd"], [92165]], coltypes=(int), tablefmt="plain"); which will treat all the cells in the column as integers.
Final note
I arrived to this package because I was using the Pandas package, specific to the function “to_markdown”. Maybe, could be a good idea to add the Pandas people to see this discussion and have additional feedback.
By the way, Pandas wraps a limited version of tabulate for the function to_markdown. Outside this discussion, it could be nice to Pandas wrap the full parameters and functionality of tabulate.
The text was updated successfully, but these errors were encountered:
Discussion: data types of the columns
Discussion
My question is whether there should be a mixed-type column instead of automatically deciding what data type the column is. In this case, “tabulate” would try to identify the data type for each cell in that column and treat it as such rather than the overall type of the column.
Quick comment
In GitHub, you could add the discussion feature: https://github.com/features/discussions. With this feature, your community can create a discussion, if a specific discussion is relevant, it could move to the issues section.
Not all the final users (community) use the discussion feature, instead the repositories or projects have enabled. But, the discussion feature appears to be useful in terms of administration.
Context
I noticed that “tabulate” reviews all the rows for each column and automatically assigns a type of column. It is fabulous, but I am concerned when the rows in the column are mixed.
In the mixed cases, I discovered that the order is as follows:
Evidence
All the results were taken, adding debug lines for the function
_format()
. It prints theval
type and thevaltype
value to compare both.For this instruction:
tabulate([[82000.38], ["abcd"], [92165]], tablefmt="plain")
thevaltype
is<class 'str'>
.The result is below.
For this instruction:
tabulate([[12013], [210], [15.24], [92165]], tablefmt="plain")
thevaltype
is<class 'float'>
.The result is below.
For this instruction:
tabulate([[12013], [210], [92165]], tablefmt="plain")
thevaltype
is<class 'int'>
.The result is below.
Expectation
Based on this discussion, I expected this output for the
_format()
function.Solution 1
For this instruction:
tabulate([[82000.38], ["abcd"], [92165]], tablefmt="plain")
thevaltype
should beMixed
or something like this.The result is below.
Then, in the logic for the
_format()
function, we can check that it is mixed and take the real value for theval
to perform all the actions for formatting.Solution 2
Always ignore the
valtype
and take the type of theval
. Except if some parameter was passed which indicates that the user specified the format of the column. Something like this:tabulate([[82000.38], ["abcd"], [92165]], coltypes=(int), tablefmt="plain")
; which will treat all the cells in the column as integers.Final note
I arrived to this package because I was using the Pandas package, specific to the function “to_markdown”. Maybe, could be a good idea to add the Pandas people to see this discussion and have additional feedback.
By the way, Pandas wraps a limited version of
tabulate
for the functionto_markdown
. Outside this discussion, it could be nice to Pandas wrap the full parameters and functionality oftabulate
.The text was updated successfully, but these errors were encountered: