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.

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

fix for #104 large file support #105

Closed
wants to merge 0 commits into from
Closed

fix for #104 large file support #105

wants to merge 0 commits into from

Conversation

a-tal
Copy link
Contributor

@a-tal a-tal commented Apr 29, 2015

No description provided.

@sigmavirus24
Copy link
Member

As I mentioned on #104 this does not do what you think it does.

@a-tal
Copy link
Contributor Author

a-tal commented Apr 29, 2015

yeah it see it just delays the issue

data_to_send = []
for key, value in data.items():
if isinstance(value, (list, tuple)):
for item in value:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why does this need to be added?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

otherwise classifiers (and any other list/tuple) was being picked up by this

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay. One other question, why is data_to_send a list instead of a dictionary?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

because currently the same key is sent as many times as it has values, so just to keep the same behavior

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@sigmavirus24
Copy link
Member

Travis isn't going to run the tests because this branch doesn't cleanly merge into master. Are you comfortable rebasing this branch on top of master?

@sigmavirus24
Copy link
Member

@a-tal I didn't mean that you should squash this into one commit. You need to rebase your commit onto master.

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

Successfully merging this pull request may close these issues.

2 participants