Skip to content
This repository has been archived by the owner on Sep 22, 2021. It is now read-only.

do not use ^M carriage returns in training data #50

Merged
merged 1 commit into from
Nov 27, 2017
Merged

do not use ^M carriage returns in training data #50

merged 1 commit into from
Nov 27, 2017

Conversation

stevemar
Copy link
Contributor

It's not very unix friendly to use ^M, so remove it and actually use new lines. Currently, when cat'ing the file it will only produce one line of content.

It's not very unix friendly to use ^M, so remove it and actually use new lines. Currently, when cat'ing the file it will only produce one line of content.
@stevemar
Copy link
Contributor Author

to the reviewers, note that i haven't actually tested that this still works, but i'm assuming the API services normalizes the csv content. if it's smart enough to handle ^M's, as it does today, then it should handle this format, too.

@germanattanasio germanattanasio merged commit cdcf103 into watson-developer-cloud:master Nov 27, 2017
@germanattanasio
Copy link
Contributor

Thanks @stevemart

@watson-github-bot
Copy link
Member

🎉 This PR is included in version 1.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Successfully merging this pull request may close these issues.

4 participants