Skip to content
This repository was archived by the owner on Nov 26, 2021. It is now read-only.

Conversation

@credp
Copy link
Contributor

@credp credp commented Nov 1, 2018

When we load the files from trace-cmd output, we explicitly choose
to load them using utf-8. This means we may have characters in
our trace which cannot be represented in ascii, which makes pandas
upset when we try to store the parsed dataframes in the csv cache.

This is not an issue for Python3 versions, as the to_csv method
defaults to utf-8, whilst the Python2 to_csv method defaults to
ascii.

Signed-off-by: Chris Redpath chris.redpath@arm.com

When we load the files from trace-cmd output, we explicitly choose
to load them using utf-8. This means we may have characters in
our trace which cannot be represented in ascii, which makes pandas
upset when we try to store the parsed dataframes in the csv cache.

This is not an issue for Python3 versions, as the to_csv method
defaults to utf-8, whilst the Python2 to_csv method defaults to
ascii.

Signed-off-by: Chris Redpath <chris.redpath@arm.com>
@valschneider
Copy link
Contributor

valschneider commented Nov 5, 2018

Travis doesn't seem to like it, can you have a look as to why?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants