Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Should we add an encoding argument to all import_* functions? #48

Open
cimentadaj opened this issue Nov 19, 2020 · 0 comments
Open

Should we add an encoding argument to all import_* functions? #48

cimentadaj opened this issue Nov 19, 2020 · 0 comments

Comments

@cimentadaj
Copy link
Contributor

Perhaps we should add an encoding argument to all import_* functions that redirects to the actual haven call and users can experiment which encoding to use when foreign is used as fall back. See #45.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cimentadaj