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

ENH: kwarg names need to be unicode in py3 but may be unicode in py2 #1588

Merged
merged 2 commits into from Sep 19, 2016
Merged

ENH: kwarg names need to be unicode in py3 but may be unicode in py2 #1588

merged 2 commits into from Sep 19, 2016

Conversation

llllllllll
Copy link
Member

when will this nightmare be over?

@llllllllll llllllllll force-pushed the more-py2-3-compat branch 2 times, most recently from 8b55083 to 16f06d3 Compare September 15, 2016 20:48
@llllllllll llllllllll force-pushed the more-py2-3-compat branch 2 times, most recently from d089a5d to 929afbd Compare September 15, 2016 20:59
@coveralls
Copy link

coveralls commented Sep 19, 2016 •
edited

Coverage Status

Coverage decreased (-0.003%) to 89.574% when pulling 929afbd on quantopian:more-py2-3-compat into a1aa9a2 on blaze:master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.003%) to 89.574% when pulling 929afbd on quantopian:more-py2-3-compat into a1aa9a2 on blaze:master.

@llllllllll llllllllll merged commit 729493f into blaze:master Sep 19, 2016
@llllllllll llllllllll deleted the more-py2-3-compat branch September 19, 2016 20:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
server
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@llllllllll @coveralls