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
There's no good reason for returning bytes rather than utf8 unicode strings I think --- it can only lead to bugs in user code and inconsistencies in string handling (anyone remember Python 2???)
This is based on the "example" plink dataset in the test suite
jeromekelleher
changed the title
read_plink returns bytes values for variant_alleles no unicode
read_plink returns bytes for variant_alleles not unicode
Mar 6, 2024
There's no good reason for returning bytes rather than utf8 unicode strings I think --- it can only lead to bugs in user code and inconsistencies in string handling (anyone remember Python 2???)
This is based on the "example" plink dataset in the test suite
Gives
The text was updated successfully, but these errors were encountered: